Profile settings are deleted incorrectly when the same name is used in different cases. This servicing release fixes the following issue: This servicing release fixes the following issue:ĭeadlocks occur in the MBAM cluster databases.
The life cycle of the effective group registry entries are not maintained correctly. This servicing release fixes the following issues:ĭuplicated handles are not managed correctly and cause the virtual application to crash.
CURRENT NEWS FOR SEPTEMBER 2017 UPDATE
Issues that are fixed in this update App-V 5.1 (release version)
We recommend that you apply the latest servicing release. Because the builds are cumulative, each new servicing release contains all the fixes (including security fixes) that were included in the previous update package. We recommend that you test fixes before you deploy them in a production environment. The "in-box" App-V client continues to use the App-V 5.1 Server.įixes that are delivered to the "out-of-box" versions of App-V and UE-V are first delivered for the "in-box" versions of App-V and UE-V in the monthly Windows 10 cumulative updates. The App-V and UE-V Clients are "in-box" starting with the Windows 10 Anniversary Edition (Version 1607). This servicing release contains the latest fixes for the Microsoft Application Virtualization (App-V) 5.1 RTM Client and Remote Desktop Services (RDS), Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 Service Pack 1 (SP1), and Microsoft User Experience Virtualization (UE-V) 2.1 Service Pack 1 (SP1). This article describes the contents of the September 2017 servicing release for Microsoft Desktop Optimization Pack (MDOP).
0 kommentar(er)
