One of the FAQ series blog was a post I did on Active Upgrade. The last year was an unbelievable year from a work commitment perspective so my blogging went to zero and did little bit here and there. So i wanted to repost the post i sent over.
This terminology is a little confusing. The “Active” was added in 4.x and referred to the fact that we could add and begin serving an updated version while the current version was still actively in use. The RTSP, HTTP, FILE (SMB) protocols all allow this functionality.
However with RTSP, an App-V Management Server or Streaming Server sits between the client and the content (the SFT file containing the application). Clients never need to be told that there is an update because the server is checking every launch and streams the updated SFT. The client requests a Package GUID not a specific file.
An RTSP streaming client will get an update the next time they launch the app – no refresh is required. There is an exception here – all instances of an application running on Terminal Servers or Remote Desktop Servers have be inactive (i.e. no one using it), then the next user to launch the application will trigger the update for everyone else.
The App-V Streaming Server does not even need the updated version to publish. Once the updated package is fully in the Content share and the Package Detection Interval (the configured amount of time that the Streaming Server detects changes in the Content share) kicks in, it is served on next launch.
HTTP/FILE streaming is a little different – there is no middleman so the client makes a direct request for the SFT file. If the HREF is http://websvr/content/Visio/Visio.sft, the client asks specifically for that path even if there happens to be Visio_2.sft (version 2 of the package) in the same directory. The publishing information must be updated on the client by some other means.
An admin would have added the updated SFT and OSDs to Content and on the next Desktop Refresh the updated OSD with HREF=http://websvr/content/Visio/Visio_2.sft would come down and on the next launch the updates will stream. Still an active upgrade, but only after a refresh. NOTE: Streaming is not tied to a publishing method, so a refresh can be:
- App-V Management Server over RTSP
- IIS with ASP over HTTP (rare as you must code your own provisioning logic)
- MSI with MODE=STREAMING via ESD
- SFTMIME commands via ESD
- App-V Application Publishing and Client Interaction
- Methods for Upgrading or Updating Virtualized Applications
- App-V: Sequencing and Deploying Using MSI and Active Upgrade, a video from BriForum 2009
- How to Configure the App-V System for Package Upgrade
- How Do I: Updating and Upgrading a Sequenced Application Using Microsoft App-V?
- TechNet Virtual Lab: Learning App-V Intermediate Skills
- How to Use the Differential SFT File