Install KMS Host License Pack for Office 2010 on Windows Server 2016

Currently when you try to install the KMS Host License Pack for Office 2010 on a Windows Server 2016 or Windows 10 you receive the following error message:

The cause of this problem relies in the VBS script that is being triggered at the end of the installation. In order to install the KMS Pack on newer operating systems than Windows server 2008R2 you need to perform the following steps:

  1.  Run KeyManagementServiceHost_en-us.exe until the error message appears. Don’t click OK.
  2. Go to the folder “C:\Program Files (x86)\MSECache\OfficeKMS” and copy the folder to somewhere like (C:\Temp\OfficeKMS)
  3. Click OK on the error message and press ENTER to close the program.
  4. Open the folder with the copy (C:\Temp\OfficeKMS) and edit the file kms_host.vbs:
    1. Search for the line 
      If (Ver(0) = "6" And Ver(1) >= "2") Or (Ver(0) >= "7") Then  
    2. And replace it with the line below, this line just says that Windows Server 2016 and Windows 10 (both having version number 10) are also supported:
      If (Ver(0) = "6" And Ver(1) >= "2") Or (Ver(0) >= "7") Or (Ver(0) = "10") Then
    3. Start Command prompt with administrative permissions, run the command below and follow the wizard.
      cd C:\Temp\OfficeKMS cscript.exe kms_host.vbs 
Greetings, Pouyan

Configuration Manager requires a dedicated SQL Server instance

In my lab environment I’m doing quite a lot of ConfigMgr testing. Recently, I was doing some testing on System Center Configuration Manager and Endpoint Protection (current branch – version 1511) and I broke the ConfigMgr primary site server and decided to re install the primary site. Continue reading Configuration Manager requires a dedicated SQL Server instance

Windows Server 2012 Failover Cluster Virtual Fibre Channel Adapter Live Migration Error

I’ve got a multiple  node cluster running Windows Server 2012 with Brocade 415/815 4G/8G FC HBA’s connecting to a VX SAN. I am trying to get the virtual HBA’s working in Hyper-V Guest running Windows 2008 R2 (SQL Cluster). I first created 2 virtual SAN Switches one connected to each port on my physical HBA (each physical port connects to a separate fabric). I add two Virtual HBA’s in my Guest, one to each VSAN Switch. When I go to Zone the HBA’s I only see side A of the virtual HBA’s not both A and B. On each fabric I should see two (A and B) WWPN but I only see one, to solve this you must shut down the Guest OS and twist the address set name (copy Set Address A to  Set Address B  and Set Address B to Set address A) I can add disk and everything works, however when I go to Live migrate I get the following error due to side B not being zoned. Live migration of ‘Virtual Machine Win2012_01’ failed.

Virtual machine migration operation for ‘Win2012_01’ failed at migration destination ‘hv-cl07-c2’. (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

‘Win2012_01’ Synthetic FibreChannel Port: Failed to finish reserving resources with Error ‘Unspecified error’ (0x80004005). (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

‘Win2012_01’ Synthetic FibreChannel Port: Failed to finish reserving resources with Error ‘Unspecified error’ (0x80004005). (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

To solve this problem, I have done the following:

  • Updated my drivers to the latest version (
  • Remember that the Virtual SAN path must be the same, for example when you create 2 paths then the VSAN A should always connect to FiberSwitch 1 and VSAN B should connect 2 Fberswitch 2. This is because when you try to live migrate the guest OS and the VSAN paths are different the fiberSwitch cannot build the connection.
  • My problem was however that I only had created one host on the SAN and configured all the 8 paths under one host, to resolve my problem I created one host for the address set A and one host for the address set B. So I have always one connected and one disconnected host on my SAN and when I am doing a Live migration then the both hosts are online

I hope that this will solve your problem to.

Best Regards,



Install the WSUS 3.0 Administration Console

After installing WSUS 3.0 on a server, you can manage WSUS 3.0 from any computer on your network, as long as the domain of that computer has a trust relationship with the domain of the server. You will need to perform a separate installation, from the same downloaded installation package, on every machine from which you want to run the WSUS 3.0 administration console.

Install the console

To install the WSUS 3.0 administration console, use the same installation package you downloaded to install the WSUS server.

The latest version of the WSUS setup executable is available on the WSUS Web site (

The console-only installation process can be run from the setup UI from the command line. For more information about command-line installation, see Appendix A: Unattended Installations later in this guide.

To install the WSUS 3.0 console only from the UI

  1. Double-click the installer file (WSUSSetup-x86.exe or WSUSSetup-x64.exe).
  2. On the Welcome page, click Next.
  3. On the Installation Mode Selection page, select the Administration Console only check box, and then click Next.
  4. Read the terms of the license agreement carefully. Click I accept the terms of the License Agreement, and then click Next.
  5. The final page of the installation wizard will tell you whether or not the WSUS 3.0 installation was completed successfully. Then click Finish.

To install the WSUS 3.0 console only from the command line

  1. Open a command window.
  2. Navigate to the directory in which you saved the installation executable. (This will be either WSUSSetup-x86.exe or WSUSSetup-x64.exe.)
  3. Type one of the following commands:
    WSUSSetup-x86.exe CONSOLE_INSTALL=1 or WSUSSetup-x64.exe CONSOLE_INSTALL=1
  4. This will bring up the Welcome page of the installation UI. Click Next.
  5. Read the terms of the license agreement carefully. Click I accept the terms of the License Agreement, and then click Next.
  6. Wait for the installation process to finish, and then click Finish.

Access the WSUS administration console

You must be a member of the local Administrators group or the WSUS Administrators security group on the computer on which WSUS is installed in order to use all the features of the WSUS console. Members of the WSUS Reporters security group have read-only access to the console.

To open the WSUS administration console

  1. Click Start, point to Control Panel, point to Administrative Tools, and then click Microsoft Windows Server Update Services 3.0.
  2. If you are bringing up the remote console for the first time, you will see only Update Services in the left pane of the console.
  3. To connect to a WSUS server, in the Actions pane click Connect to Server.
  4. In the Connect To Server dialog box, type the name of the WSUS server and the port on which you would like to connect to it.
  5. If you wish to use SSL to communicate with the WSUS server, select the Use Secure Sockets Layer (SSL) to connect to this server check box.
  6. Click Connect to connect to the WSUS server.
  7. You may connect to as many servers as you need to manage through the console.

Time Synchronize Domain Servers

In a domain the DC with the PDCEmulator FSMO is the time source for all domain member machines, DC sync with that one and all other domain members sync with an available DC. Therefore make sure no firewall is blocking port 123 UDP on all machines.

Time displayed on the computers are for humans, internally all the client computers/member server/domain controllers will follow UTC Timing conventions.

You should understand the hierarchy.
If possible the PDCEmulator should sync to a NOT domain machine or NTP server, this can be configured with:

w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update

With “PEERS” you can set the time source, either DNS name ( or an ip address from a reliable time source.

Here you can find some of them:

To reconfigure the domain members for the domain hierarchie run:

w32tm /config /syncfromflags:domhier /update

After that run:

net stop w32time
net start w32time

Or you should run below command line on problematic system , to reset the time service:

- Type CMD in the run windows
-  Type Net stop w32time to stop the time service
-  Type W32tm /unregister to unregister the time service registry
-  Type W32tm /register to register the time service registry back
-  Type Net start w32time
-  w32tm /monitor and compare the time and check wheater they are in sync or not

The client part can also be scripted and run as startup script.