[THIN] Re: OT - App-V newbie issues - App won't launch
- From: Matt Kosht <matt.kosht@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 29 Jan 2010 14:01:57 -0500
According to App-V 4.5SP1 release notes it is. Just not as a client or
sequencer.
***
Support for Windows 7 and Windows Server 2008 R2: App-V 4.5 SP1
provides support for Windows 7 and Windows Server 2008 R2, including
support for Windows 7 features such as the taskbar, AppLocker,
BranchCache, and BitLocker To Go. ***Windows Server 2008 R2 support
is for the Application Virtualization Server only***.
**
On Fri, Jan 29, 2010 at 1:54 PM, Joe Shonk <joe.shonk@xxxxxxxxx> wrote:
> Not sure if 4.5SP1 can be run on Windows 2008 R2.
>
> Joe
>
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
> Of Matt Kosht
> Sent: Friday, January 29, 2010 9:51 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] OT - App-V newbie issues - App won't launch
>
> I had messed with App-V about 6 months ago and got it working OK on a
> testbed. I decided to go ahead with building a new infrastructure. The
> new server is Windows 2008R2 which I am running the App-V 4.5SP1 mgmt
> server component on.
>
> I keep getting these errors in the server log when a client (I have
> tried XP (4.6RC, 4.5SP1), Win 7 x64 (4.6RC), Win 2K3R2 x32 (4.6RC,
> 4.5SP1))
>
> [2010-01-29 10:55:13.998] SDC-APPV-01 4116 4584
> SW_CacheHandle::SW_CacheHandle - "Default Provider" Adm1n43
> Milestn/Milestones.sft 4 41520 "Package file not found:
> \\sdc-appv-01\content\Milestn\Milestones.sft.
>
> On the client I get this event when I launch (which fails)
>
> "The Application Virtualization Client could not connect to stream URL
> 'RTSP://sdc-appv-01:554/Milestn/Milestones.sft' (rc 1690140A-20000194,
> original rc 1690140A-20000194)."
>
> The default content dir is set to \\sdc-appv-01\content and I have
> verified each client can get to this folder and the sft is indeed in
> \\sdc-appv-01\content\Milestn\ folder and named exactly as the error
> indicates.
>
> I can also telnet to port 554 successfully from a client so it does
> appear to have connectivity to the server on that port.
>
> I don't know where else to look for what could be causing this. Any
> ideas would be welcome.
> -Matt
> ************************************************
> For Archives, RSS, to Unsubscribe, Subscribe or
> set Digest or Vacation mode use the below link:
> //www.freelists.org/list/thin
> Follow ThinList on Twitter
> http://twitter.com/thinlist
> Thin List discussion is now available in blog format at:
> http://thinmaillist.blogspot.com
> Thinlist MOBILE Feed
> http://thinlist.net/mobile
> ************************************************
>
> ************************************************
> For Archives, RSS, to Unsubscribe, Subscribe or
> set Digest or Vacation mode use the below link:
> //www.freelists.org/list/thin
> Follow ThinList on Twitter
> http://twitter.com/thinlist
> Thin List discussion is now available in blog format at:
> http://thinmaillist.blogspot.com
> Thinlist MOBILE Feed
> http://thinlist.net/mobile
> ************************************************
>
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
Follow ThinList on Twitter
http://twitter.com/thinlist
Thin List discussion is now available in blog format at:
http://thinmaillist.blogspot.com
Thinlist MOBILE Feed
http://thinlist.net/mobile
************************************************
Other related posts:
