Hotfix Package 4 for Microsoft Application Virtualization 5.0 SP2 released

Microsoft has released Hotfix Package 4 for App-V 5.0SP2. This release is almost like a whole service pack with the amount of fixes that it incorporates. If you are going to upgrade then test your applications prior to pushing out to users.

Of interest to readers of the SCCMentor blog is the fix for the following issue ‘Unable to unpublish App-V 5 packages with AppData redirected’ raised back in October last year.

I’ve tested unpublishing post install and it’s working like a dream.

Grab the hotfix from here.

So what are the issues addressed in the release?  Straight from the MS KB page it reads:

Issue 1

Enhancements to publishing and refresh performance have been made in all App-V deployment scenarios (RDS, Traditional Desktop, and VDI).

Several targeted fixes to the App-V 5.0 SP2 Client or to the Client for RDS have greatly improved publishing and refresh performance. This requires no additional configuration of the client or the environment by the IT administrator.

Note This issue and its resolution are not directly applicable to customers who are using Configuration Manager or System Center Configuration Manager together with App-V 5.0 SP2. For more information, see the Microsoft TechNet documentation.

Issue 2

Publishing and start performance have been implemented in non-persistent VDI or RDS deployments together with a user environment management (UEM) technology.

Previously, the App-V experience in non-persistent environments went as follows:

User logs in, and all global-targeted (computer-wide) and user-targeted (user or user group) virtual applications need to be preconfigured and published to the user each time that the computer state is reverted. In non-persistent VDI, this occurs every time that the user logs-off.

As noted in Issue 1, publishing and refresh performance has been enhanced. However, by following the practices that are described in the Performance Guidance about configuration of the deployment environment, UEM technology and the App-V 5.0 SP2 Client and Client for RDS (after applying Hotfix Package 4 for Application Virtualization 5.0 SP2), the virtual application start, publishing, and refresh functions are significantly faster.

Learn about Performance Guidance in the Application Virtualization topic on the Microsoft TechNet website.

Issue 3

Package converter has reported low success rates and low detection diagnosis.

Changes to the package converter have improved conversion rates. The package converter raises a new warning for App-V 4.5 and 4.6 packages that contain hard-coded paths to a drive letter, as these cannot be converted correctly.

Issue 4

Virtual application packages that require write access to any files and folders in the virtual environment are incompatible with App-V 5.0.

With this hotfix package, the Application Virtualization 5.0 SP2 contains a new sequencer setting that, when it’s applied to a virtual application package, provisions the package with write access to any files and folders in the virtual environment.

Issue 5

Upgraded versions of virtual application packages cannot be deployed in parallel with the original version of the package on the client.

After you apply this hotfix package, the Application Virtualization 5.0 SP2 sequencer can support saving an upgraded version of a package as a new package. These packages can be deployed in parallel.

Issue 6

Virtual application packages that contain shortcuts to executable (.exe) files on a network share cannot start those executables if the system account does not have access to the network share.

After this hotfix package is applied, user credentials are used to access and start executable (.exe) files.

Issue 7

App-V Deployment configuration does not handle certain registry settings correctly.

When registry values are set by using the App-V Dynamic Configuration, DWORD, QWORD, and multi-string value types are not captured correctly. Therefore, the registry value is set incorrectly.

After this hotfix package is applied, these registry settings are captured and set correctly.

Issue 8

The Windows PowerShell window is listed on the taskbar during App-V Client startup.

When a user logs on to an AppV Client, a minimized PowerShell window appears on the taskbar. This PowerShell window is visible until the App-V start tasks are completed. If the user pre-emptively cancels the PowerShell execution, App-V does not start as expected.

After this hotfix package is applied, the PowerShell window is hidden and runs in the background.

Issue 9

App-V Service crashes when packages are deployed through System Center Configuration Manager.

When the Configuration Manager Distribution Point is located on a separate LAN from the App-V client, the client may crash intermittently during the publishing process.

After this hotfix package is applied, the service no longer crashes in this scenario when packages are deployed through System Center Configuration Manager.’

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s