Manage Hyper-V in a workgroup remotely

Managing  Hyper-V remotely in a workgroup can be challenging to configure. This is still the case for Windows Server 2016. For a testing environment I needed to remotely manage Windows Server 2016 core server with the Hyper-V role enabled from Windows 10 with the Hyper-V manager. I used the following manual configuration:

  • Client with Hyper-V Manager (Windows 10). This client is called win10-01
  • Server with Windows Server 2016 core version with the Hyper-V role enabled. The server is called hv-02
  • Both systems are in the same workgroup called “workgroup”
  • Both systems have the same username and password.

Configuration on the Windows Server 2016  server:

  • Enable Remote Management
Configure-SMRemoting.exe -Enable
  • Open firewall for  Remote Computer Management
Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true -PassThru
Set-NetFirewallRule -DisplayGroup 'Remote Event Log Management' -Enabled true -PassThru
  • Open firewall for ping (ICMPv4)
Set-NetFirewallRule -DisplayName “File and Printer Sharing (Echo Request – ICMPv4-In)” -Enabled True -PassThru
  • Enable Remote Desktop and allow remote connections
cscript.exe c:\Windows\System32\SCregEdit.wsf /AR 0
  • Enable Remote disk management
Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru

 

Configuration on the Windows 10 client:

  • Create a host file with IP address and hostname of the server. Make sure you can ping the hostname

6

  • Make sure that the network type is part of a private network before executing the WINRM command

1 2

  • Enable Remote Management
winrm quickconfig
  • For Managing remote systems
winrm set winrm/config/client @{TrustedHosts="Name of the Server"}
  • Enable remote disk Management (add this command on both systems) firewall rule
Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru
  • Open c:\windows\system32\dcomcnfg.exe and allow ‘anonymous logon’ for local and remote access.

5

After making this settings I was able to manage the Windows Server 2016 server with the following tools remotely:

  • Hyper-V manager
  • Computer Management
  • Disk Management

 

3 4

Test Windows Server 2016 Hyper-V with VMware Workstation

Windows Server 2016 Technical Preview 3 (TP3) is released with some cool new features. An easy way to test Windows Server 2016 TP3 is to use VMware Workstation. Windows Server 2016 can be installed with the Hyper-V role and have some VMs nested with minimal configuration.

For this test i used the following hard-and software:

Hardware: Dell Latitude E6540 with an Intel i5-4310M CPU and 16 GB memory.

Software: As desktop OS Windows 8.1 Enterprise, VMware Workstation 12 PRO and Microsoft Windows Server 2016 TP3.

To install Windows Server 2016 and enable the Hyper-V role and nest VMs use the following steps:

  • Open VMware Workstation
  • Create a new custom Virtual Machine
  • Choose the highest VM hardware compatibility -> Workstation 12.0
  • In the guest Operating System Installation -> browse to the Windows Server 2016 ISO
  • As Guest Operating System choose -> Microsoft Windows and as version -> Hyper-V (unsupported)

1

  • Give the VM one or more CPU’s and 4 GB of memory if you want to install some VMs in Hyper-V
  • Controller -> LSI Logic SAS
  • Virtual disk type -> SCSI
  • Create a new virtual disk of 40 GB of more. (For the best performance use -> Allocate all disk space now)

You’re ready to install Windows Server 2016 you have two options: Windows Server with or without GUI.

3   6

  • After the installation add the Hyper-V role and reboot the server.

7

  • When choosing for the core version install the hyper-v with the following PowerShell command:
powershell
Install–WindowsFeature Hyper-V
  • Open Hyper-V Manager and create one or more VMs

Hyper-V Manager

When having limited hardware resources and want to test Hyper-V in Windows Server 2016, VMware Workstation is a great choice. Without minimal effort it is possible to install Windows Server 2016, add the Hyper-V role and nest some VMs.

The new way to patch the vCenter Server Appliance 6

The patching process in vCenter Server Appliance (vCSA) version 6 is changed from previous versions. It is not possible anymore to use the Virtual Appliance Management Interface (VAMI) and update the appliance using the User Interface. The new way to patch the vCenter Server Appliance involves the following steps:

  • Download the patch from the VMware Patch Download Center, link.
  • Choose vc and select version 6.x
  • Download the latest patch ISO

1_patch

  • Attach the *.ISO to the vCenter Server Appliance.
  • Open a console session or SSH (SSH must be enabled) to the appliance. In the console session press ALT + F1 and login.

vcsa

  • Stage the ISO using the following command
software-packages stage --iso  --acceptEulas
  • See the staged content
software-packages list --staged
  • Install the staged content
software-packages install --staged
  • Reboot the appliance
shutdown reboot -r
  • After the reboot check the new vCenter Server Appliance build version

vcsa version

The easy updating process that was used in the vCenter Server Appliance 5.x is gone. The new update process involves more manually steps. We hoping that the easy updating will return in further releases of the vCenter Server Appliance.

 

Windows 10 with Horizon View Agent generates BSOD

After installing the VMware Horizon View Agent (6.1.1)  on a Windows 10 (tested with build 10240), it generates a Blue Screen Of Death (BSOD) when pressing Ctrl+Alt+Del/Ins.

PSOD

 

The error is: DRIVER_IRQ_NOT_LESS_OR_EQUAL (kbdclass.sys).

To fix the problem (The solution was found on the Microsoft Community site, link):

  • RDP to the Windows 10 VM
  • Edit HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318}\UpperFilters
  • Put the kbdclass before the vmkbd value
  • Reboot the VM

Upperclasses Uppper2

After changing the UpperFilters value I was able to login the Horizon View desktop without BSOD.

 

 

Manage Azure VMs with System Center Virtual Machine Manager (SCVMM)

With Update Rollup 6 it is possible to add one or more Azure subscriptions to SCVMM 2012 R2. When the Azure subscription is added in SCVMM, it is possible to perform some basic actions such as:

  • Add and Remove one or more Azure subscriptions by using the VMM console.
  • See a list view with details and status of all role instances in all deployments in that subscription.
  • Manually refresh the list of instances.
  • Perform basic actions on the instances:
    • Start
    • Stop
    • Shutdown
    • Restart
    • Connect via RDP

To add the Azure Subscription to SCVMM 2012 R2 UR6 following these steps:

1. Install UR6 to System Center Virtual Machine Manager (SCVMM) 2012 R2, link.

2. Create a self-signed Azure management certificate. The self-signed must have a key length of at least 2048 bits and should reside in the Personal certificate store. To create a self-signed management certificate, the makercert tool is used. Makecert is part of  Windows SDK. The SDK can be downloaded here, link.

Install the SDK and choose as feature to install “Windows Software Deployment”. After the installation copy the makecert tool to the SCVMM server.

3. Create the self-signed certificate with makecert with the following command:

makecert -sky exchange -r -n "CN=<CertificateName>" -pe -a sha1 -len 2048 -ss My "<CertificateName>.cer"

Example:

makecert -sky exchange -r -n "CN=ivobeerensazure" -pe -a sha1 -len 2048 -ss My d:\install\ivobeerensazure.cer

4. The certificate needs to be present in the Current User \ Personal store of the computer running the VMM console.

5. To upload a management certificate to Azure, go to the Settings page in the Management Portal, and then click MANAGEMENT CERTIFICATES.

6. In SVVMM start the Add Azure Subscription Wizard, click the Azure Add Subscription button. The wizard is a single page dialog box:

SCVMM

  • Display Name: Enter the display name
  • Subscription ID: The subscription ID can be found on the Azure website under settings
  • Certificate: Add the self-signed certificate by using the browse button

After the Azure subscription is added, the Azure Virtual Machines are listed in SCVMM:

azure

Basic actions can be performed on the Azure VMs such as:

stopstart

UR6 adds support for managing Azure VMs. The management is very basic. So hopefully on the next releases the management support for Azure VMs will be improved.

Advertisement