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.
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.
<span class="pun">(</span><span class="typ">Get</span><span class="pun">-</span><span class="typ">WmiObject</span> <span class="pun">-</span><span class="pln">class </span><span class="typ">Win32_OperatingSystem</span><span class="pun">).</span><span class="typ">Caption</span>
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”
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 Powershell commands
The following App-V Powershell commands are available:
There is one new command: Enable-Appv
We will use this command to Enable the App-V client on this Server 2016 OS.
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:
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.
Add-AppvClientPackage "%AppVShare%\7-Zip_16.04\7-Zip_16.04.appv" | Publish-AppvClientPackage
After publishing the application you can use it like any other application. In this case I can start 7-Zip manager via menu start.
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”
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.
Last week I was installing my Vsphere 6 homelab in VMware Workstation.
Because I didn’t wanted to install the vCenter Server Appliance (VCSA) on my virtual ESXi host I tried to install it directly in VMware Workstation. I am using VMware Workstation 12 PRO.
In this post I will explain how to install VCSA6 in VMware Workstation.
Finally! DSM can now serve as a reverse proxy server. With this build-in feature it is very easy to configure your NAS as a reversed proxy.
In the past you had to rewrite different apache rules with config files
Take a look at this post to see how to configure reverse proxy on the new DSM 6.
I’ve been using my Synology NAS with HTTPS enabled for a while now but with a self-signed certificate it wasn’t all that secure. Today I decided to try the new feature in DSM 6 Beta 2 for installing a SSL certificate to better secure my NAS. Since the release of DSM 6 Beta 2 Let’s Encrypt is integrated.
Check out this post to see a checklist which can be used after installing WIndows Server 2012 R2.
With this policy settings, you can provide a default experience for your users while still allowing each user to customize their theme. For example, if an end-user has already changed their theme, their setting will take precedence over a theme that is applied via Group Policy.
Today I had to change some settings on the HP iLO interface on a server. When I applied the changes I was notified that the settings would take place after the iLO interface was reset, but how do you reset it?