Jump to content

Recommended Posts

Posted

Hi

 

I went from my trusty old 2003 KMS server to 2012R2 in the summer. I installed a new KMS server on the 2012, imported all my keys etc. I then stopped the KMS service on the 2003 box, tidied up DNS so only the one KMS server was listed (the new one) and then ran the following on all the workstations:-

 

slmgr.vbs /skms NEW_KMS_SERVER_NAME:1688

slmgr.vbs /ato

 

All the workstations sorted themselves out.

 

I also did the following for Office at the same time:-

 

"C:\Program Files\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"

cscript "c:\Program Files\Microsoft Office 2010\Office14\OSPP.VBS" /sethst:NEW_KMS_SERVER_NAME.domain.local

cscript "c:\Program Files\Microsoft Office 2010\Office14\OSPP.VBS" /act

 

Once all that was done, I installed VMAT on the new KMS server so that I could get a report of all the workstations and their registered state.

 

TBH, probably a much quicker way of doing it, but the above worked for me with 900 workstations.

 

Andrew

  • Thanks 3
Posted

I'd do the first steps from Andrew with regards the install.

 

Then install VAMT and scan AD or the network and do the re-arming from there as normal.

  • Thanks 1
Posted

The reason I went the long way was I couldn't see an option in VMAT to specify which KMS server to register workstations with and the count on the new KMS server wasn't increasing. However, when I used the script the count climbed as I would have expected.

 

Like I said, I may have done something wrong but the long way round got me out of a hole at the time :)

 

Andrew

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...