The topics in this section provide information and instructions to help you administer App-V and its components. This information is for system administrators who manage large installations with many servers and clients, and for support personnel who interact directly with the computers or users. Getting started with App-V. Microsoft Application Virtualization (App-V) Client 5.X Service Pack x; The version that is installed is listed in the Version column. The following list shows the current latest build number for each component: The App-V Client (as of ): 5.1.134.0 (App-V 5.1 March 2018 service release). The App-V Sequencer (as of ): 5.1.129.
It is known that Microsoft is going to integrate their application virtualization technology named Microsoft App-V within Windows 10. The integration is scheduled in the upcoming Redstone release for later this year. In the Insider Preview Windows 10 build 14316 the binaries of App-V are now by default available. This blog post wil take a closer look in the built-in Microsoft App-V Client.
Microsoft App-V binaries
Microsoft Application Virtualization (MS App-V) platform allows applications to be deployed ('streamed') in real-time to any client from a virtual application server. It removes the need for traditional local installation of the applications, although a standalone deployment method is also supported. Microsoft Application Virtualization (sometimes referred to as Microsoft App-V, App-V) was added by jezr in Oct 2012 and the latest update was made in Aug 2017. The list of alternatives was updated May 2019. It's possible to update the information on Microsoft Application.
As you can see on the following screenshot the binaries of Microsoft App-V are located within the directory location: “C:WindowsSystem32'
Also the Microsoft App-V Client Services is by default installed. Please note the services is disabled by default.
It is not clear which version of App-V is integrated in this build of Windows 10. The version can not be detected because the properties of the AppVClient.exe are not set. Within the refistry the client version states 10.0.14316.1000 which is the Windows build version.
App-V PowerShell commands
As expected the App-V PowerShell commands are available.
A new command “Enable-AppV” is added and based on the name we can assume this command can enable the App-V functionality within Windows. When running the command it shows an error.
[Update]: It appears there is a difference between the x86 version of PowerShell and the x64 version. When running the command “Enable-AppV” in the x64 version it works. But as my fellow MVP Aaron Parker explained at this point there no feedback.
As a alternative App-V can be enabled by enabling the App-V Client services. After this an App-V package can be added and should be able to successfully run it.
Publishing server
The built-in App-V client should be compatible with an existing version 5.1 infrastructure but for some reason it could not sync with the publishing server.
At this point I have no idea what is causing this error. I will look into this and hopefully I can share results in an upcoming blog post.
[Update]: Also here using the correct version of PowerShell is important otherwise it will result in an error like above. When using the x64 version you can successfully sync with the publishing server.
Conclusion
Microsoft App V Windows 10
With the integration of App-V Microsoft is enabling all their enterprise customer to use their powerful application virtualization technology out of the box. This was a brief exploration into the App-V integration in Windows 10 but it shows it is not final yet. However I did manage to run a App-V package successfully. If you have comments or question please leave a comment.