Upgrades in Full Infrastructure Mode

Question

Hi there
I've been considering the Upgrade scenario for an application. To my knowledge this was handled better in App-V 4.6 but I would be very happy to be corrected. My question comes in 2 scenarios. 
Scenario A:
We have an application (EG: Chrome v30). The logged on user (or another user) is using that application in their shared VDI session when I add Chrome v31 to the App-V Management Server and publish it. 
I want to be able to have that user close their app, re-launch the shortcut and have the new version automatically. Is this possible? All of my testing would indicate that they would need to logoff/logon in order for this to happen properly. I can't find any
MS documentation that it is possible. And certainly not without the logoff action. I (The customer) really wants instantaneous upgrades. :)
Scenario B:
I have a shared desktop VDI environment. I publish app-v apps using full App-V infrastrcture. I upgrade an application on the backend. 
- What is the fastsest way of getting the apps to the users? (Ideally it's instantaneous but because of AD replication timing this will be difficult) 
I would need to trigger both a Publishing server refresh (default timeout is 600 seconds so don't want to go beyond that). Should I run a Sync-AppVPublishingServer command on my management server? And then trigger a client refresh by running TaskSched remotely
for all VDI hosts?
(I am *ideally* looking to rid us of the Logoff/Logon action and speed up the delivery)
Thanks
David Murphy

Answer 1

Hi,
Scenario A:
This is possible. From a timing perspective, that mainly depends on the following points:
your Publishing Server refresh interval (when the Publishing Server publishes the new information)
The interval when your Client synchronizes with the Publishing Server. You can enforce that either manually (Sync-AppvPublishingServer), with the App-V Client UI (it's an additional App-V package you can deploy) or you can set a refresh interval so
that Client synchronizes with the Server periodically. Look for UserRefreshInterval
and GlobalRefreshInterval: https://technet.microsoft.com/en-us/library/jj687745.aspx
The old version of the app only gets replaced by the new version when the old version isn't "in use" anymore. You could enforce closing the app by powershell cmdlet.
Scenario B:
You run Sync-AppVPublishingServer on the client and not on the server. This command checks if there is a change required on the client. How do you deploy your apps, globally (per computer) or per user? Note that an application doesn't get updated
when it's still in use. So when you want to update an app, it only gets updated when the older version isn't in use anymore. I'm not sure if it's a good idea to update a version during the day when users work with the app. If that's your use case, then you
could enforce the update by app-v cmdlets (that would enforce closing the app for everyone).
Regards, Michael - http://blog.notmyfault.ch -