VMware Horizon View Optimization Guide for Windows 7 and Windows 8 white paper update

VMware released an updated version of the “VMware Horizon with View Optimization Guide for Windows 7 and Windows 8” whitepaper. This white paper discuss the necessary information for optimizing a Windows 7 or Windows 8 virtual desktop image for VMware Horizon View using the Microsoft Deployment Toolkit (MDT) or use a script-based approach.

The updated (July 15, 2014) “VMware Horizon with View Optimization Guide for Windows 7 and Windows 8” whitepaper can be found here. Link

Changelog scripts:

Removed on 03 June 2014
The following code was removed to fix issues with IE10, IE11, and Adobe Acrobat:
rem reg ADD “HKLM\System\CurrentControlSet\Control\Session Manager\Memory
Management” /v MoveImages /t REG_DWORD /d 0×0 /f

Removed on 11 February 2014
Rem Remove recycling bin
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
policies\Explorer” /v NoRecycleFiles /t REG_DWORD /d 0×1 /f

Veeam v8 is coming

The new version of Veeam is called “Veeam Availability Suite v8”.


The Veeam Availability Suite v8 has improvements in the following areas:

  • High Speed Recovery
  • Data Loss Avoidance
  • Verified Protection
  • Leverage Data
  • Complete Visibility


Enables low recovery time objectives (RTOs) of <15 minutes; enables rapid recovery of the data customers want, in the form that they want it. Features are:

  • Instant VM Recovery
  • Instant File-Level Recovery
  • NEW v8 Veeam Explorer™ for Microsoft Exchange, SharePoint, SQL
  • Server,Active Directory
  • NEW v8 Veeam Explorer for Storage Snapshots (HP and NetApp)


Avoids data loss by enabling low recovery point objectives (RPOs) of < 15 minutes and facilitating offsite data protection. New features v8 are:

  • 2-in-1: backup and replication
  • Built-in WAN Acceleration
  • Native tape support
  • NEW v8 Backup from Storage Snapshots (HP and NetApp)
  • NEW v8 EMC Data Domain Boost
  • NEW v8 Veeam Cloud Connect
  • NEW v8 End-to-end encryption
  • NEW v8 Replication enhancements


Reliably restores files, applications and virtual servers when needed; ensures business resiliency through automated backup and DR testing.

  • SureBackup
  • SureReplica


Eliminates the risks associated with application deployment; allows you to test changes in a production‐like environment before actually deploying them.

  • Virtual Lab


Provides monitoring and alerting tools so that you can discover and be alerted to issues in your IT environment before they have a significant impact.

  • Complete visibility of the Veeam backup infrastructure
  • vSphere Web Client Plug-in
  • vCloud Director integration
  • Centralized management

The Veeam Availability Suite v8 is scheduled for Q3 2014.  More information can be found here, link.

Remove an orphaned VM from SCVMM

During a migration of a VM from a different cluster the job failed in SCVMM.


The status of the VM in SCVMM Virtual Machine State is still “Starting”. 


In SCVMM I was unable to stop, repair or delete the VM. When looking on the Hyper-V host, the VM didn’t exist in Failover Cluster Manager or Hyper-V manager. After some troubleshooting I was able to use the following PowerShell command to remove the orphaned VM in SCVMM:

Import-Module VirtualMachineManager

Get-VM -VMMServer VMMSERVER –Name “VMNAME" | Remove-VM -Force

Replace the VMMSERVER and VMName  in the PowerShell syntax with your own names

Create a VMware Horizon View self signed certificate with makecert

With the command line Windows utility “makecert.exe” it is possible to create quickly a self-signed (private) certificate that can be used with VMware Horizon View. Makecert is part of the Windows Software Deployment Kit (SDK)for Windows 7 and 8.  Below are the steps outlined to create a self-signed certificate using makecert.

  • 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.* utility to the VMware View Connection server
  • Open a elevated command prompt
  • Create the self-signed root certificate, command: makecert -pe -n "CN=ViewRootCA" -ss root -sr LocalMachine -sky signature -r "ViewRootCA.cer"


  • Open certlm.msc and go to “Trusted Root Certification Authorities” and verify if the root certificate generated with makecert.exe exist. The root certificate can copied to all the servers and View Clients. If the clients are domain joined a Group Policy can be used to distribute the root certificate. More information can be found here, link.


  • Create a new self-signed certificate, command: makecert -pe -n "CN=viewcon02.beerens.local,cn=viewcon02" -ss my -sr LocalMachine -sky exchange -in "ViewRootCA" -is root -ir LocalMachine -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 viewcon02.cer


  • The certificate is added to the personal store of the local computer


  • Change the Friendly name of the newly created self-signed certificate to: vdm
  • Remove the already existing self-signed certificate


  • Restart the VMware View Connection Server service
  • In the System Health dashboard the Connection Server system health gets green


Unable to perform a Compliance Scan in SCVMM

In System Center Virtual Machine Manager (SCVMM) an Update (WSUS) Server is added, so VMM can be used to update the hosts with Windows patches.When trying to scan a cluster of hosts for compliance the following error occurred:

Error (24035)

Compliance scan failed with error: 80244017.

Recommended Action:

Ensure the WINHTTP proxy settings are correctly configured for the communications with WSUS. If WSUS is configured to use SSL ensure the WSUS certificate is installed in the trusted Root CA for the machine and then try the operation again.


The cluster consist of several Microsoft Hyper-V Server 2012 R2 hosts. All the hosts are configured with a proxy server during the initial installation. After resetting the proxy server per host,  the SCVMM was able to perform a compliance scan without errors. The following command is used to reset the proxy server configuration on the core version:

netsh winhttp reset proxy