I’ve been exploring and testing the Microsoft solution for Application Virtualization (App-V). The latest version of App-V is 5.0 SP2. However, for some reason, the downloadable ISO of MDOP 2013 R2 (Microsoft Desktop Optimization Pack) includes SP2 versions of only App-V Client and Sequencer, not for the App-V Server itself. This leads to some problems with the latest operating systems.
My test lab today consists mainly of VMs running the latest Windows operating systems. That is, Windows Server 2012 R2 and Windows 8.1. The downloadable ISO file of MDOP 2013 R2 includes installers for App-V Server, App-V Client and App-V Sequencer. The client and sequencer are of version 5.0 SP2, but the disc only contains installer for App-V Server 5.0 SP1. When publishing an application with the App-V Server and having a Windows 8.1 machine as a client, problems arise.
The App-V Server logs an Error Event ID 216 as follows. The App-V event log can be found under Applications and Services Logs in Event Viewer.
Log Name: Microsoft-AppV-Server-Publishing/Admin Source: Microsoft-AppV-Server-Publishing Event ID: 216 Level: Error Keywords: Common User: *** Computer: *** Description: The client OS is unknown: WindowsClient_6.3_x64. ...
…and on the client side two Error Events are logged (19203 and 19102) stating that.
Log Name: Microsoft-AppV-Client/Admin Source: Microsoft-AppV-Client Date: 7.1.2014 5:35:45 Event ID: 19203 Task Category: Publishing Refresh Level: Error Keywords: Publishing Refresh User: *** Computer: *** Description: HttpRequest sendRequest failed. URL: http://***:***/ Error code: 0x45500D27 - 0x801901F4
Log Name: Microsoft-AppV-Client/Admin Source: Microsoft-AppV-Client Date: 7.1.2014 5:35:45 Event ID: 19102 Task Category: Publishing Refresh Level: Error Keywords: Publishing Refresh User: *** Computer: *** Description: Getting server publishing data failed. URL: http://***:***/ Error code: 0x45500D27 - 0x801901F4
I guess this is because the server is only 5.0 SP1, it doesn’t recognize or support having a 8.1 machine as a client. Just to let you know, the offline (not streamed) application package runs fine and Windows 8.1 is fully supported in 5.0 SP2.
Fortunately, there is a hotfix available. The hotfix is for the App-V Server (5.0 SP1 only) and it adds (among a few other things) support for Windows 8.1 as a client. There’s a link to it at the end of this article.
After applying the hotfix to the App-V Server, Windows 8.1 started receiving Applications as expected with no errors.
Sources for the matter can be found in:
- The issue is mentioned in the Microsoft App-V Team Blog article, which can be found here.
- The Hotfix Package 2 for Microsoft Application Virtualization 5.0 Service Pack 1 that resolves this issue can be found and requested here.
- There is also a Hotfix Package 3 for Microsoft Application Virtualization 5.0 Service Pack 1 already available, get it here. This is only for the client though and has nothing to do with the above mentioned issue.