VMware vSphere PowerCLI 11.0

VMware vSphere PowerCLI 11.0 New Features

New features available on  VMware vSphere PowerCLI 11.0 is to support the new all updates and release of VMware products , find the below following has been features,

  • New Security module
  • vSphere 6.7 Update 1
  • NSX-T 2.3
  • Horizon View 7.6
  • vCloud Director 9.5
  • Host Profiles – new cmdlets for interacting with
  • New Storage Module updates
  • NSX-T in VMware Cloud on AWS
  • Cloud module multiplatform support
  • Get-ErrorReport cmdlet has been updated
  • PCloud module has been removed
  • HA module has been removed

Now we will go through above mentioned new features to find what functionality it bring to PowerCLI 11.0

What is PowerCLI 11.0 New Security Module

The new security module brings more powerful automation features to PowerCLI 11.0 available  new cmdlets include the following

  • Get-SecurityInfo
  • Get-VTpm
  • Get-VTpmCertificate
  • Get-VTpmCSR
  • New-VTpm
  • Remove-VTpm
  • Set-VTpm
  • Unlock-VM

Also New-VM cmdlet has enhanced functionality with the security module functionality and it includes parameters like KmsCluster, StoragePolicy, SkipHardDisks etc which can be used while creating new virtual machines with PowerCLI .In addition to that  Set-VM, Set-VMHost, Set-HardDisk, and New-HardDisk cmdlets are added.

Host Profile Additions

There are few additions to the VMware.VimAutomation.Core module that will make managing host profiles from PowerCLI

  • Get-VMHostProfileUserConfiguration
  • Set-VMHostProfileUserConfiguration
  • Get-VMHostProfileStorageDeviceConfiguration
  • Set-VMHostProfileStorageDeviceConfiguration
  • Get-VMHostProfileImageCacheConfiguration
  • Set-VMHostProfileImageCacheConfiguration
  • Get-VMHostProfileVmPortGroupConfiguration
  • Set-VMHostProfileVmPortGroupConfiguration

Storage Module Updates

These new Storage Module updates specifically for VMware vSAN , the updates has predefined time ranges when using Get-VsanStat. In addition  Get-VsanDisk has additional new properites that are returned including capacity, used percentage, and reserved percentage. Following are the  cmdlets have been added to automate vSAN

  • Get-VsanObject
  • Get-VsanComponent
  • Get-VsanEvacuationPlan – provides information regarding bringing a host into maintenance mode and the impact of the operation on the data, movement, etc

Additionally  following modules have been removed

  • PCloud module
  • HA module

Download now and start using

Update-module VMware.Powercli

Useful Links

Windows 10 build 10240 has released to the Fast Ring… Release To Manufacturing (RTM) build???

Windows 10 build 10240 has been released to the Fast Ring. That’s what I’m running on my laptop now. There were heavy rumors yesterday that this is the to Release To Manufacturing (RTM) build and is the one to be publically available on July 29th. But there is no hard confirmation on this by Microsoft yet Build 10240 now available for Windows Insiders in Fast and Slow rings.

“Over the past few days we’ve been preparing our release pipelines and processes, and this build is one step closer to what customers will start to receive on 7/29 …

On Monday we announced that builds from here on will only be available through Windows Update, so to get this one you can either wait and it will be installed automatically.”

Here’s how you prepare to roll it out in your company.

In a previous blog post I wrote about the update you needed for your KMS server to be able to activate Windows 10 clients. Read about that in KB3058168: Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows

Meanwhile Microsoft has also published the Windows 10 client KMS activation which keys can be found here Appendix A: KMS Client Setup Keys

Windows 10

Operating system edition
KMS Client Setup Key

Windows 10 Professional: W269N-WFGWX-YVC9B-4J6C9-T83GX
Windows 10 Professional N: MH37W-N47XK-V7XM9-C7227-GCQG9
Windows 10 Enterprise: N: NPPR9-FWDCX-D2C8J-H872K-2YT43
Windows 10 Enterprise N: DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4
Windows 10 Education: NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
Windows 10 Education N: 2WH4N-8QGBV-H22JP-CT43Q-MDWW
Windows 10 Enterprise 2015 LTSB: WNMTR-4C88C-JK8YV-HQ7T2-76DF9
Windows 10 Enterprise 2015 LTSB N: 2F77B-TNFGY-69QQF-B8YKP-D69TJ

Do note this is the key you use when you activate the Windows 10 Client against a KMS server. It is not the KMS license server key. That one you’ll need to obtain from your valid Microsoft licenses.

Update that enables Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012 Key Management Service (KMS) hosts to activate a later version of Windows.

Windows 10 will be available on July 29th 2015. Microsoft has prepared for this by already making an Update(KB3058168) that enables Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012 Key Management Service (KMS) hosts to activate a “later version of Windows”. This must means Windows 10. I do not know if this means that is even for Windows Server 2016. Windows 10 will be activated by a KMS server running this update but it might.

Select the version you need for the KMS server or servers you use and install them.


KMS Update adds support for Windows 8.1 and Windows Server 2012 R2 clients to Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 KMS hosts

This update extends the Key Management Service (KMS) for Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 to enable the enterprise licensing of Windows 8.1 and Windows Server 2012 R2.
KMS provides support for the following KMS client activations:

  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2
  • Windows 8
  • Windows Server 2012
  • Windows 8.1
  • Windows Server 2012 R2

KMS uses a KMS host key to activate itself on a KMS host and to establish a local activation service in your environment. This update extends support for KMS to provide activation for Windows 8.1 and for Windows Server 2012 R2.

Click here for the downloads

2012 Blogging

This blog was viewed about 110,000 times in 2012. If it were a concert at the Barclays Center, it would take about 6 sold-out performances for that many people to see it.
In 2012, there were 88 new posts, growing the total archive of this blog to 485 posts.
The busiest day of the year was March 13th with 616 views. The most popular post that day was Exchange 2010 Opening multiple shared calendars & additional mailboxes.

These are the posts that got the most views in 2012. You can see all of the year’s most-viewed posts in your Site Stats.


Microsoft Office 2013 KMS Volume License Pack

Volume license editions of Office 2013 client products require activation. This download enables IT administrators to set up a Key Management Service (KMS) or configure a domain for Active Directory-Based activation. Either of these volume activation methods can locally activate all Office 2013 clients connected to an organization’s network.



If you want to activate volume license editions of Office 2013, Visio 2013, or Project 2013 with a KMS host or Active Directory-Based activation, you need to first install Office 2013 Volume License Pack. When an Office 2013 volume edition client is installed, it will automatically attempt to activate via either Active Directory by using its existing domain pairing or a DNS-discoverable KMS host on your organization network. To set up Active Directory-Based activation, you must be running Windows Server 2012, Windows 8, or newer.
All volume editions of Office 2013 client products are pre-installed with a Generic Volume License Key (GVLK) key, which supports automatic activation for both KMS and Active Directory-Based Activation, so you will not need to install a product key.
This download contains an executable file that will extract and install KMS host license files. These license files are required for the KMS host service to recognize Office 2013 KMS host keys. On Windows Server 2012 and volume license editions of Windows 8, you can use your same KMS host key to set up Active Directory-Based activation.

System requirements

Supported operating systems: Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012

    • KMS Host: Windows Server 2008 R2, Windows 7 (volume editions), Windows Server 2012, or Windows 8.
    • Active Directory-Based Activation
      • Set-up and Configuration: Windows Server 2012, Windows 8 or newer.
      • Domain controller: Active Directory Domain Services with the Windows Server 2012 schema installed.

Instructions:Microsoft Office 2013 Volume License Pack

  1. You need to perform this step only if you’re setting up a KMS host on Windows Server 2008 R2 or Windows 7 (volume editions). Download and run the update contained in the KB article below. This update enables your Windows Server 2008 R2 or Windows 7-based KMS host to successfully activate Office 2013 clients that are running on Windows 8 or Windows Server 2012:
    KB 2691586
  2. Download and run the executable file on this page on a supported operating system.
  3. Enter your Office 2013 KMS host key when prompted.
  4. Activate the product key online.
  5. If setting up a KMS host, open port 1688 to allow the KMS host service through the firewall:
    1. Open Control Panel and click on the Windows Firewall icon.
    2. Click the “Allow a program through Windows Firewall” link.
    3. Click the Change Settings button.
    4. Check the box for Key Management Service.
  6. To learn more about configuring your KMS host with slmgr.vbs, see the TechNet documentation found on this page.

Windows 8 en Server 2012 KMS Service Activation

For Licensing Server 2012 and Windows 8 on a Windows 2008 R2 server you need to update the KMS Service.

Install the following update: An update is available for Windows 7 and Windows Server 2008 R2 KMS hosts to support Windows 8 and Windows Server 2012 as described in KB2691586.
If you don’t install this hotfix registering a Windows Server 2012 KMS will throw an Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid

So request the hotfix and install it. Just follow the instructions and you’ll be fine clip_image001

We can start putting our brand new KMS key into action.

Uninstall the current KMS key using slmgr.vbs /upk clip_image002


Now you can install the new KMS key. The key listed here is obviously a demo one clip_image002[1]If you run in to any issues here, restarting the KMS Service can help. Try that first.



Now activate your brandnew KMS key running slmgr.vbs /ato

We run slmgr.vbs /dlv again and as you can see now we can activate all our Windows 2012 servers and Windows 8 computers


An update is available for Windows 7 and Windows Server 2008 R2 KMS hosts to support Windows 8 and Windows Server 2012

This update extends the Key Management Service (KMS) for Windows 7 and Windows Server 2008 R2 to allow enterprise licensing of Windows 8 and of Windows Server 2012.
KMS provides support for the following KMS client activations:

  • Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1 (SP1)
  • Windows Server 2008 and Windows Server 2008 Service Pack 2 (SP2)
  • Windows 8
  • Windows Server 2012
  • Windows 7 and Windows 7 Service Pack 1 (SP1)
  • Windows Vista and Windows Vista Service Pack 2 (SP2)

Key Management Service (KMS) uses a KMS host key to activate KMS on a KMS host, and to establish a local activation service in your environment. This update extends support for KMS to provide activation for Windows 8 and for Windows Server 2012.


Setup KMS Server for Windows Server 2008 R2 or Windows 7

Open the command prompt and run the following command:

cscript c: \ Windows \ System32 \ slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Enter the product key xxxxx Windows Server 2008 R2. It is also able to activate Windows 7. The following text appears when the command is successful.

Microsoft ® Windows Script Host Version 5.7
Copyright © Microsoft Corporation. All rights reserved.
Installed product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx successfully.
The installation of the KMS server is complete. The server installs itself on port 1688. This port must be opened to be put in the firewall. To change the port the following command can be used.

Slmgr.vbs / SPRT xxxx
Once the firewall is open and the key is installed, the KMS server service has to be restarted. Do this by using the following command:

slsvc & net stop & net start slsvc

To check whether the data will be registered correctly in the DNS, the following command:

nslookup-type = srv _vlmcs._tcp

Here, the following output should appear:

_vlmcs._tcp.test.local SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms.wardvissers.local
internet address = kms.wardvissers.local

Clients / Servers

The clientele / servers need to connect to the KMS host will automatically find the host by dns. When the client / server using a MAK key is activated. Should this be put back to a KMS client key. These keys are released by Microsoft. When this key is set on the client / server will automatically look for a KMS host. When not present, the client / server activation.

KMS client keys:

Windows 7 Enterprise: 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows Server 2008 Standard: TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Windows Server 2008 Enterprise: YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Windows Server 2008 R2 Standard – YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Server 2008 R2 Enterprise – 489J6-VHDMP-X63PK-3K798-CPX3Y

The following commands can the key be changed from MAK to KMS here are the xxxxx is one of the above keys.

slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Note: To ensure that the client is forced to activate the command to be executed on the client.

It can happen that the RMS server returns the following message. This is because the KMS server is just beginning to work with 25 clients and 5 servers.

You can find here the list with error codes & solutions: http://support.microsoft.com/kb/938450

Special thanks to:Harm Hoekstra

Checking Microsoft Office 2010 KMS Activation Status

Before you start you must al ready have a kms server.
On the KMS server you need to install the Office 2010 KMS Host License Pack on the KMS Server.
Launch Microsoft Outlook 2010
Click to the File tab. Click Help.

Office is not activated
Determining Which Activation Method Office is Using – KMS or MAK

Click the start menu and enter cmd /k cscript “%programfiles%\Microsoft Office\Office14\ospp.vbs” /dstatus in the search box.

If running 32 bit Office 2010 on 64 bit Windows, %programfiles% above should be replaced with %programfiles(x86)%.

Not Activated


Checking if a DNS Domain is Configured for KMS Auto-Discovery

To check if a DNS domain is configured for KMS auto-discovery, check that a SRV record exists.

nslookup -type=srv _vlmcs._tcp.wardvissers.nl

If a SRV record exists for the domain, the DNS server will detail the SRV record.

C:\>nslookup -type=srv _vlmcs._tcp

Server:  ward-dc02.wardvissers.local


Non-authoritative answer:

_vlmcs._tcp.wardvissers.local SRV service location:

          priority       = 0

          weight         = 0

          port           = 1688

          svr hostname   = ward-dc2.wardvissers.local

If no SRV record exists for the domain, the DNS server will return an error

Verifying that a Windows Computer can Communicate with the KMS Activation Server

KMS activation requires that the machine to be activated has TCP port 1688 open for outbound communication to the activation server.

Verifying that outbound TCP port 1688 is open to the KMS server

  1. Download and install the utility portqry.exe from Microsoft. It is a command line utility from Microsoft that reports the port status of a remote host.
  2. From a command prompt, run the command:

portqry.exe -n ward-dc02.wardvissers.local -p tcp -e 1688

The command will return “TCP port 1688 (unknown service): LISTENING” if the computer is able to communicate with the KMS server.


If the command returns “TCP port 1688 (unknown service): FILTERED” then the computer is unable to communicate with the KMS server

Manually Specifying the KMS Activation Server

1. Type cmd in the search bar to locate the command window..
2. At the command prompt, type cd\Program Files\Microsoft Office\Office14.

If running 32 bit Office 2010 on 64 bit Windows, Program Files above should be replaced with Program Files (x86).
Run the command cscript ospp.vbs /sethst:ward-dc02.wardvissers.local to manually specify the KMS activation server.

Run the command cscript ospp.vbs /act to activate Office with the KMS server.


Launch Microsoft Outlook 2010 agein
Click to the File tab. Click Help.

Office is activated