PowerCLI Fails To Launch

I encountered a strange issue the other day after installing PowerCLI 5.0, as soon as I launched it, it closed.


Windows Event Logs for Windows PowerShell, Application and System, revealed erm nothing

Checking the properties of the PowerCLI Shortcut its is launched using the target from C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -psc “C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\vim.psc1” -noe -c “. \”C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1\””

and Starts in “C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\”


Trying to run the .ps1 from Powershell resulted in ‘the term’Initialize-PowerCLIEnvironment.ps1’ is not recognized as the term of a cmdlet.


Next, was to go into the Windows Folder C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\ and right click Initialize-PowerCLIEnvironment.ps1 and Run with PowerShell


This time, I received the error message:

‘internal Windows PowerShell error com initialization failed while reading windows PowerShell console file with error 80010106’


Googling the issue, I came across this PowerShell forum post which suggested changing the ‘Number of recent items to display in Jump Lists to 10’


After making this change, I was able to launch PowerCLI!


vCOPS: Unable To Connect To vCenter Server. Details: Connecting to VC at https://vCenter/sdk failed

When installing and configuring vCenter Operations Manager you receive the error message ‘Unable To Connect To vCenter Server. Details: Connecting to VC at https://vCenter/sdk failed’ when trying to enter the FQDN of you vCenter Server



If you enter the IP Address of your vCenter then you are able to continue which means the issue is with DNS.

Go to your IP Pool > DNS and then enter the DNS Domain and an IPv4 DNS Server


Unfortunately, we now have to power the vCOPS vAPP off and power it back again for the new IP Pool settings to take effect.  Once done, go back threw the initial configuration and you will be on the Import Data screen.

vCOPS Working

Windows 8 KMS Activation Error: Event ID 1017 0xC004F050

When configuring a Horizon View environment for Windows 8 activation, I was receiving Event ID 1017 Installation of the Proof of Purchase failed. 0xC004F050


The KMS Server is a Windows 2008 R2 VM which has HotFix KB2757817 installed to allow activation of Windows Server 2012 or Windows 8 on a Server 2008 R2 VM.

When trying to add the Windows 8 KMS key using

slmgr.vbs /ipk <Windows8KMSKey>

Resulted in the error ‘On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xC004F015 to display the error text.

Error: 0xC004F015


This then meant that my Windows 8 VM’s where stuck in the ‘customizing’ state in Horizon View Administrator.


The fix is simple you need to use a Windows Server 2012 KMS license rather than a Windows 8 KMS license.

slmgr.vbs /ipk <Windows2012KMSKey>

Which returns ‘Installed product key XXXXX-XXXXX-XXXXX-XXXXX successfully’


Then last of all run the command

slmrg.vbs /ato

Which will activate the KMS license.

Horizon View 5.2: Resize PCoIP Desktop Black Screen

Today, I had a small issue with a Manual Dedicated Horizon View 5.2 PCoIP Desktop Pool for access to a Management Windows 7 VM and I was scratching my head for a while trying to figure this one out.

Essentially, I could connect without any issues via the View Client to the Windows 7 desktop but only if I can the desktop in Windows -Large or Windows – Small.

If I expanded the desktop beyond a certain size or made it full screen, I had a black background (the pictures below look the same size, but i’m sure you get what I mean).

Large Desktop – Black


Small Desktop

Small Desktop

Troubleshooting Steps – (That Didn’t Work)

  1. Logged into the Windows 7 VM via RDP and rebooted.
  2. Logged into the Windows 7 VM and changed the screen resolution to 1920 x 1080
  3. Uninstalled View Agent & re-installed
  4. Uninstalled the vSGA Driver from Device Manager and the manually installed the driver from C:\Program Files\Common Files\VMware\Drivers\video_wddm

Troubleshooting Steps – (That Worked)

I found KB1018158 Configure PCoIP for use with View Manager which had most of the symptoms.  I knew I had installed the VMTools then View Agent (correct order), and then I read further down the KB and discovered this:

Note: Do not reboot by clicking Shutdown > Restart in the virtual machine. PCoIP is dependent upon the appropriate amount of video memory being allocated to the virtual machine. Because this is a virtual hardware setting (that must be in place before the virtual machine starts up), it is applied as a change in the .vmx file. If the virtual machine has already been started, it is essential that this virtual machine be restarted so that the .vmx file is re-read and the changes are used. Using the Shutdown > Restart option inside the virtual machine does not force the .vmx to be re-read, as this does not cold boot the machine (from the VirtualCenter perspective) to refresh the virtual hardware. Using the Shutdown > Restart option from either VirtualCenter or View Manager (which issues the command via VirtualCenter) is the best way to make sure this file gets read properly.

I quickly ‘Reset’ the Manual Dedicated Windows 7 Desktop using View Administrator and what do you know everything worked!

View Administrator

Lessons Learnt

When creating a manual dedicated desktop, ensure that you reset the desktop using View Administrator otherwise the correct PCoIP settings are not maintained within the .vmx configuration file.

Remove Datastore Call “HostStorageSystem.UnmountVmfsVolume” Error

I was making some changes to the vmfocus.com lab the other day and kept getting a repeated error Call “HostStorageSystem.UnmountVmfsVolume” for object “storageSystem-15” on vCenter Server when I was trying to unmount a VMFS Datastore

Unmount Error 2

When I went to unmount the VMFS Datastore it met all the relevant criteria.

Unmount Error 1


If you are booting from flash device such as a USB or internal SD card, then a VMFS Datastore would have been selected to store your output logs for troubleshooting.

These need to be moved to a VMFS Datastore which you are going to keep.

Note: You will need to make these changes to each ESXi Host

Select ESXi Host > Configuration > Advanced Settings > Syslog > Syslog.global.logDir

Unmount Error 3

Change the paramters to a VMFS Datastore that will remain e.g.

[ESXi01_RAID10_L01_SAS] /scratch/log

Hit OK and then you will have success in unmounting your VMFS Datastore.