none
App-V 4.6 Service Pack 1 Hotfix 3 RRS feed

  • General discussion

  • Source; http://blogs.msdn.com/b/sgern/archive/2011/07/19/10187771.aspx

     

    Hi

     after a long wait, it is now sowei, the Hotfix 3 for the client and with a new sequencer is now to have.

     Fixed the following issues:

     - App-V client can not be started, should not the SFT file is available on the HTTP server, even if RquireAuthorizationifCached is set to 0 and the complete package in the cache.

     - The "Save As" functionality has now been restored in the sequencer.

     - In Windows XP and 2003 - should be run executables from a network share, this can not be started

     - If a virtual application, the Windows API calls LoadLibrary during seqencierung, then does this not apply correctly.

     If OSD-files to run from a network share, and DLL's included, there can be up to the error 04-00000020

     - The App-V client service takes a long time to start on some PC's which leads to poor performance spzeill behave in the boat.

     The hotfix can be obtained from today Anfragre at Microsoft.

     KB will be: 2571168

     The base is App-V 4.6 SP1

     I have also updated the App-V 4.6 Tree.

     Greetings

     Sebastian Gernert - Support Escalation Engineer

     


    /Znack
    Tuesday, July 19, 2011 1:18 PM

All replies

  • Wednesday, July 27, 2011 9:11 AM
  • Hello,

     

    Is there a way to slipstream the MSP Hotfix into the standard setup of the app-v client 4.6 SP1 for the new install of the client ?

    I'm using a scripted installation with the Setup.EXE and options in the CMD line like this :

    %install_drive%\setup.exe /s /v"/qn SWIFSDRIVE=\"Q:\" SWIUSERDATA=\"^%APPDATA^%\" MINFREESPACEMB=\"1000\" SWIGLOBALDATA=\"C:\AppVirt\Global\" SWIPUBSVRREFRESH=\"On\" REQUIREAUTHORIZATIONIFCACHED=\"0\" ALLOWINDEPENDENTFILESTREAMING=\"1\" AUTOLOADONLAUNCH=\"1\" AUTOLOADONLOGIN=\"1\" AUTOLOADONREFRESH=\"1\" SWIPUBSVRDISPLAY=\"PRD\" SWIPUBSVRTYPE=\"RTSP\" SWIPUBSVRHOST=\"appv.mydomain.local\" SWIPUBSVRPORT=\"554\" SWIPUBSVRPATH=\"/\""

    So I cannot use the Msiexec combined to MSP to install both at the same time. So integrating MSP to the original MSI would be great, or any other solution ?

     

    Thanks,

    Tuesday, August 30, 2011 9:17 AM
  • Hello,

    Usually I install the patch afterwards using something like;

    msiexec /p <patchfilename.msp> /qb

    and then force a reboot


    /Znack
    Tuesday, August 30, 2011 9:19 AM
  • If it's not possible to slipstream the msp into the msi (and I don't know if that's really possible), this is what I'm going to do, but I fear that on slow and old PC this step will be quite a big overhead for the setup time.

    Tuesday, August 30, 2011 11:14 AM
  • Hello,

    A way to install it in a single run;

    set MSIARG=/i
    set MSIARG=%MSIARG% "%~dp0\setup.msi"
    set MSIARG=%MSIARG% PATCH="%~dp0\AppV4.6SP1-WD-KB2586968-x86.msp"
    set MSIARG=%MSIARG% /qb
    msiexec %MSIARG%

     

    the PATCH-property has to have a absolut-path

    Obviously - all prerequisites has to be fullfilled before-hand


    /Znack
    Thursday, October 13, 2011 1:33 PM
  • I deployed this hotfix via Config Manager after importing it into the WSUS catalogue via SCUP. It has worked rather well.
    Thursday, October 20, 2011 3:48 PM
  • Another deployment choice many still don't know about: Local Update Publisher. Sort of "SCCM Lite", a WSUS add-in that supports MSI, MSP, and EXE installers...and free.

    www.localupdatepublisher.com

    And newbies (like me) should not be fooled (as I was) by claims in AppV 4.6 SP1 HF4 that HF4 replaces HF3. It does not. Download both.
    • Edited by JRV529088 Monday, December 26, 2011 1:17 AM
    Monday, December 26, 2011 12:08 AM
  • HI,

    Do we need to reboot between Main App-V client and the hotfix installation (msiexec /p <patchfilename.msp> /qb)?

    Like:

    1. Install App-V client.

    2 Reboot

    3 . Install App-V client hotfix

    4 Reboot.  

     


    /SaiTech

    Tuesday, June 11, 2013 12:19 PM
  • Hello,

    Yes, you could alternative use msiexec /I <misfile.msi> /qb PATCH=<c:\fullpath\topatch.msp> TRANSFORMS=transform.mst


    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, June 11, 2013 12:35 PM
  • Thanks Nicke,

    I Think I go for this method..

    " msiexec /I <misfile.msi> /qb PATCH=<c:\fullpath\topatch.msp> TRANSFORMS=transform.mst"

    We use SCCM 2012 to deploy Windows and i see that the full path is crucial, but I can put the msp on the box Before App-V setup in c:\windows\temp, or use an cmd with %~dp0 (not my favorite)

    We do use setup.exe to install App-V 4.6 client, but we get to many broken App-V client after installing the msp in an TS step. 


    /SaiTech

    Thursday, August 22, 2013 11:44 AM