December 2016 servicing release for Microsoft Desktop Optimization Pack

Issues that are fixed in this update

For App-V 5.1 RTM, this servicing release fixes the following issues:

• Group-specific functionality is incorrectly made available to other groups if the Optional feature is used.

• Using Dynamic Virtualization, file handles are not closed when a shell extension is unloaded. This issue can cause Explorer.exe to keep DLL file handles after a shell extension unloads them. This can block upgrade of the shell extension.

• After the first-time sync of a Connection Group (CG) on the device, newly added packages to the CG are not enabled.

• When you install the App-V Server management database (DB) by using SQL scripts, an SQL error is reported. The workaround that was first documented in App-V 5.0 Service Pack 3 (SP3) is now incorporated into the SQL scripts to eliminate this error.

• The FullVFSWriteMode tag in a Sequencer template is ignored. (This issue is not fixed in the update. However, it is fixed in the latest Sequencer installer. To get the installer, please contact your Microsoft Customer Service and Support representative.)

• On the Server Management console, applying an action to a filtered subset of packages actually applies the action to all packages.

For MBAM 2.5 SP1, this servicing release fixes the following issues:

• A SQL deadlock issue occurs when multiple users from different domains try to access the database at the same time.

• A device that has a mounted, nonencrypted, removable drive (for example, an SD card) can cause increased CPU usage and the inability of the device to enter the low-power state.

Improvements that are made in this update

For App-V 5.1 RTM, this servicing release makes the following improvements:

• The App-V 5.1 server update installer now links to the correct content (Privacy Policy and the "App-V 5.1" page).

• The App-V Client, RDS, and Server now have the same build number.

For MBAM 2.5 SP1, this servicing release Makes the following improvements:

• The GPO description and the Invoke-MbamClientDeployment.ps1 MBAM deployment script for Bitlocker XTS-AES support are updated. The Microsoft Download Center provides the following download and installation instructions:
  

  • The updated GPO: Microsoft Desktop Optimization Pack Group Policy Administrative Templates

  • The updated deployment script: Microsoft BitLocker Administration and Monitoring - Client Deployment Scripts

For more information about the March 2017 Servicing release, go to March 2017 servicing release for Microsoft Desktop Optimization Pack.

Update information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix for APP-V 5.1, you must have APP-V 5.1 RTM or a later App-V 5.1 servicing release installed.

To apply this hotfix for MBAM 2.5 SP1, consider the following scenarios:

If you have the RTM version installed, you can apply this hotfix directly.

If you have HF01 or HF02 installed, you must uninstall the existing server components, install MBAM 2.5 SP1 Server RTM, and then install the server components of this hotfix.

Restart requirements

You must restart the computer after you apply this hotfix.

Replacement information

This hotfix contains HF07 for APP-V 5.1 and HF03 for MBAM 2.5 SP1 RTM.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.