locked
App-V 5.0 SP2 user applications published via SCCM 2012 to VDI workstations with roaming only RRS feed

  • Question

  • Hi,

    The environment consists of App-V 5.0 SP2 (KB2956985) user based applications published via SCCM 2012 to Windows 7 VDI snapshotted workstations that are reset at user logoff.

    When a user logs on the SCCM 2012 client initiates App-V client package publishing.  After a couple of minutes after logon the shortcuts appear and the user can launch their applications.

    The issue is that at logoff, even with roaming enabled, the publishing information disappears.  This causes the next logon process for that user to repeat, the applications are not available until the SCCM client has completed it's publishing cycle. 

    Roaming profiles are implemented. %APPDATA% is redirected to a UNC path.  The following registry key is set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Integration\PreserveUserIntegrationsOnLogin=1

    U-EV, global publishing of applications, and AppLocker rules are not an option.  Also, I have read this already - http://technet.microsoft.com/en-us/library/dn659478.aspx#BKMK_PE

    I do not want to wait for the SCCM client to kick in prior to the user applications being available.  What do I need to roam or run to create a seamless transition for the user between sessions? 

    Eddie.

    Wednesday, June 18, 2014 5:34 AM

Answers

All replies

  • Hello,

    Since this seems to be a non-persistant Environment and the ConfigMgr client has a two minute delay during logon Before its operational, I would say that whatever you roam - isn't suffice (as the app isn't available...).

    I suggest you raise a ticket with Microsoft regarding the behaviour


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

    Wednesday, June 18, 2014 6:07 AM
  • Thanks for the response.

    I guess what I am after is a way to publish the application at second and consequent user logon without the involvement of the SCCM client.  After the applications are published once I would assume it is just a matter of roaming the right files and potentially running a powershell command on a clean machine.

    Wednesday, June 18, 2014 10:18 AM
  • Hello,

    You can pre-add all applications (using add-appvclientpackage), and then write a script which would publish all the applications.

    Or just setup the native infrastructure.

    Or use the App-V Scheduler

    http://bramwolfs.com/


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

    Wednesday, June 18, 2014 4:34 PM
  • Hi Tywin (bad username considering the last GoT Episode ;))

    If you ask Microsoft, they always recommend using SCCM for deploying App-V packages and reuse your current SCCM infrastructure if that is already in place. Problem is, as you now experience, is that there is some big caveats both in regards to publishing time and to roaming of settings.

    As Nické states I would suggest looking into the Full Infrastructure Model for App-V 5.x, which gives you much better performance in what I call "from no apps" to "being able to click the shortcut" - the add and publishing phase. If you don't have the time/budget/whatever to start looking into that, you could look into some community tools like App-V Scheduler which is developed specific by Citrix guys to ease the publishing and management in a Citrix world.

    Microsoft have a great article about Performance Guidelines, which you have read, but it mostly presumes you work with Full Infrastructure. Have you looked into Steve Thomas' session from TechEd NA? It talks about "implementation trends".


    Senior Consultant at Atea Denmark - http://Atea.dk Atea Technical Evangelist for App-V NoLightPeople - http://NoLightPeople.com Access Director - http://www.nolightpeople.com/index.aspx#accessdirector

    Thursday, June 19, 2014 8:56 PM