Using the App-V client integrated with Windows 10 (build 1607) [Full Guide]


App-V_ban


In a previous article, I you spoke of another new Windows 10, being able to access to Linux / Ubuntu commands from your PC Windows 10 … Today, I propose to review another interesting novelty this anniversary update Windows 10, it is integrating App-V client directly in the heart of the operating system.


Explanation


to understand the interest of Microsoft App-V (Application Virtualization) it is important to view 4 large layers in a computer,


  • the equipment (at the bottom): your motherboard, hard drive, etc.

  • the system (operating or English for OS operating system) . It can be Windows, Linux, Mac OSX.

  • The application layer that is to say, all the software you install on your computer.

  • The data or documents and content that you generated with the use of all previous layers.

The advantage of App-V (as ThinApp, VMware) is that its functioning lies in application layer and will therefore allow it to virtualize while allowing you to isolate one or more applications while preserving the integrity of the user station. This application management method will allow you to more easily deploy and manage the compatibility between different applications as they will run in independent virtual application bubbles of the OS and its parameters .


the advantage here is that in Windows 10 (Enterprise version) the App-V client will now be integrated directly into the operating system and the changes will be managed by the publisher .


I therefore propose to test the integration of app-V client in Windows 10 (build 1607)


customer Test app-V. – Publish application


First step you need to enable the features that are related to App-V. To do this, open a PowerShell prompt (with administrator rights) and run the following command:


Enable-APPV

You will have in return:


App-V was successfully enabled.

When it’s good, we can possibly to review the list of CmdLet PowerShell that are available with the App-V client using the following command:


Get-Command -Module AppvClient

appv1


Once it is good to test an application using App-V we need a package or an application was packaged to the App-V format. You’re offering 2 for download above. There is no specific or technical nature in the package since I chose two basic applications: NotePad ++ and PuTTY


Pick one package and. unzip it somewhere on your computer. In the example below, I’ll take PuTTY and it will be in my case in the following location: C: Users Thibault Desktop PuTTY PuTTY.appv


I will perform the following CmdLet to add then publish on my app-V client and make the application available on my post:


Add-AppvClientPackage PuTTY.appv. | Publish-AppvClientPackage

appv2


If you used the same package I’ve provided an example, it is configured to automatically create a desktop icon. You should therefore, after publication, have emerged a new application icon PuTTY directly accessible on your desktop and named SSH, Telnet and Rlogin customer . If you look at the properties of the icon, you will see that it is your App-V application (notice the non-traditional and own paths to the App-V client).


appv3


from there, you can test and use the application without any problems. The latter can even be performed with PuTTY application installed as standard on your job because working in a virtual bubble.


Clear / De-publish your application


now have to see how to delete or rather un-publish your app-V application. To do this, it is very simple, run the following PowerShell CmdLet:


Get-AppvClientPackage -Name "PuTTY" | Unpublish-AppvClientPackage | Remove-AppvClientPackage

appv4


After a few seconds, the icon disappears from your desktop, the application is no longer available. 🙂


No comments:

Powered by Blogger.