Menu Close

Windows Virtual Desktop LAB on Hyper-V (on-premises)

First let me explain what the new hype is all about. Microsoft Windows Virtual Desktop is an Azure-powered service that lets users access a multi-session Windows 10 experience from anywhere. The service comes with Office 365 ProPlus integration for enterprise customers, as well as support for Windows Server Remote Desktop Services. The idea is that businesses can easily deploy and scale their Windows desktops and apps quickly and easily through the power of Azure.

Enabling built-in App-V client in Windows Server 2016

Microsoft has integrated their application virtualization technology named Microsoft App-V within Windows 10 and Windows Server 2016. In this post I will explain how to enable the integrated client and how to use it.

To demonstrate the built-in App-V client in Windows Server 2016 I will use a clean installed Virtual Machines running on VMware Workstation 12 Pro.

With the following powershell command you will get the Windows version.

Windows version

The binaries

Without enabling the App-v Client in Server 2016 there are already files for App-V present on the system. These binaries are located in “C:\Windows\System32”

App-V files

Also the Microsoft App-V Client Services is by default installed. The service is disabled by default, you cannot start this services without enabling App-V.

App-V service

App-V Powershell commands

The following App-V Powershell commands are available:

App-V commands

There is one new command: Enable-Appv
We will use this command to Enable the App-V client on this Server 2016 OS.

Enable App-V

After enabling App-V you can use the App-V powershell commands like you always do.

You can show the configuration in powershell with the following command:

Get-AppVClientconfiguration

Publish App-V package

To demonstrate the function of the App-V client I will publish an App-V package on Server 2016.

For publishing an App-V package you first need to add it to the client, after adding it you can publish it. Here an oneliner to accomplish this.

Import App-V package 7-Zip

After publishing the application you can use it like any other application. In this case I can start 7-Zip manager via menu start.

7-zip App-V

During the publishing of the application the App-V client will create a cache of the files needed to run the App-V package. Default these cached files are located in “C:\ProgramData\AppV”

App-V cache

Updating vCenter Server Appliance 6.0 to Update 2

In this post I will go through the proces of updating your VCSA 6.0.0 with update 2.

For all the new Features and Release notes see VMware vCenter Server 6.0 Update 2 Release Notes

In my environment I have the VCSA Appliance running with embedded Platform Services Controller [PSC]. If you deployed an external PSC separately from vCenter then this post will still work for you! The upgrade procedure is the exact same on both the vCenter and PSC just upgrade the PSC first before vCenter.