none
Windows 7

    Question

  • Hello,
     Windows 7 (which honestly gotta be the worlds best marketing trick... ) is my new toy for testing and what do I do first? Test app-v of course.
    Now I haven't deployed a MSI-enabled APP-V client yet to a clean-machine but all previous installations have been upgrades for 4.2 or 4.5 beta.

    So I installed Windows and tried to install APP-V using the same MSI property as used earlier for MSI-deployment. Uh, that din't work
    Well, after a few corrections (really, the property was good, why skip it?) I think I have it correctly setup.

    I checked the following values;
    HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client\Network\Online = 0
    HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client\Network\LimitDisconnectedOperation = 0
    HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client\Configuration\RequireAuthorizationIfCached = 0
    HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client\Configuration\AllowingStreamingFromFile = 0
    HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client\Permissions\ToggleOfflineMode = 0


    They all seems to be correct...

    But all I get is this;

    [01/11/2009 11:48:16:451 SWAP INF] {hap=4:app=Symantec pcAnywhere 12.5.001:tid=310:usr=Admin}
    Elapsed time for upload: 0.282 seconds


    [01/11/2009 11:48:16:967 SWAP ERR] {hap=4:app=Symantec pcAnywhere 12.5.001:tid=310:usr=Admin}
    The client could not launch C:\Program Files\Symantec\pcAnywhere\Winaw32.exe (rc 1F702639-FFFFFFFE, last error 0).


    [01/11/2009 11:48:17:170 TRAY ERR] {tid=82C:usr=Admin}
    The Application Virtualization Client could not launch Symantec pcAnywhere 12.5.001.

    This error code is invalid.

    Error code: 4505CD-1F702639-FFFFFFFE

    Same error for Adobe Acrobat 9 or symantec pcAnywhere 12.5 (had them laying around sequenced and done...)

    Any thoughts? I hope to dig into this later on...

    Sunday, January 11, 2009 8:12 PM

Answers

  • App-V 4.5 is not currently supported or functional on Win7.  Info on Win7 support will be published soon. 

    Scott Stearns [MSFT]
    App-V Test Manager
    • Marked as answer by znack Monday, January 12, 2009 7:00 PM
    Monday, January 12, 2009 4:45 PM

All replies

  • Hi,

    Are both of those VFS sequences? What I would try is to change that C:\Program Files\Symantec\pcAnywhere\Winaw32.exe to point directly to Q: or using %CSDIL_PROGRAM_FILES%\Symantec\pcAnywhere\Winaw32.exe.

    Just a thought...

    /Kalle
    Monday, January 12, 2009 1:57 PM
    Moderator
  • Heres how it looks originally...;
    <CODEBASE HREF="RTSPS://%SFT_SOFTGRIDSERVER%:322/spca125.001/spca125.001.sft" originalAttribute="HREF" originalPath="RTSPS://%SFT_SOFTGRIDSERVER%:322/spca125.001/spca125.001.sft" GUID="98DAFD49-F566-4D2D-B69B-74E95CE59872" PARAMETERS="" FILENAME="%CSIDL_PROGRAM_FILES%\Symantec\pcAnywhere\Winaw32.exe" SYSGUARDFILE="spca125.001\osguard.cp" SIZE="127591840"/>
    Monday, January 12, 2009 2:03 PM
  • App-V 4.5 is not currently supported or functional on Win7.  Info on Win7 support will be published soon. 

    Scott Stearns [MSFT]
    App-V Test Manager
    • Marked as answer by znack Monday, January 12, 2009 7:00 PM
    Monday, January 12, 2009 4:45 PM
  • And here I thought I was brave.  Shudder!!!!
    Friday, January 23, 2009 7:04 PM
    Moderator
  • Does anyone happen to know the OS VALUE tag for Windows 7 for the 4.5.1.15580 CU1 client?  I've removed all the tags for my testing so far which is going pretty well, but would be nice to know what the proper value is..

    thanks,
    Danny
    Tuesday, March 3, 2009 1:09 PM
  • Hello,

    Value is Win7.

    Cheers!
    Wednesday, March 4, 2009 7:25 AM
  • Just wantet to share my findings on App-V error ..xx-FFFFFFFE, as I couldn't find any info about this error code on the interwebs.

    We had a 32-bit App-V package that didn't work (lots of strange errors, among them WMI didn't work), and got this error code when starting a cmd within the virtual environment (sfttray /exe cmd "ShortcutName 1.0") on 64-bit Windows 7.

    It turned out to be a HKLM\Software\Wow6432Node registry key mistakenly included in the package with Override set to ON. App-V was then unable to merge the local Wow6432Node registry key into the bubble. This caused the bubble-registry to have an almost empty HKLM\Software key.

    The error code could probably also mean lots of other things...

    Friday, February 10, 2012 12:00 PM