[windows software] KMS Clients stuck looking at an old KMS server

[Marshall_IT]

Hi all,

 

Our KMS server recently died.

 

I have install 2 new KMS servers and have published them to DNS alright.

 

They seem to be activating my Windows server and client machine alright, as well as office 2013.

 

However our Office 2010 keeps looking for the old server.

 

Is there any way to clear this setting remotely? i have around 100 machines to do and i don't want to visit each one.

[DrPerceptron]

You can use VAMT2 (Volume Activation Management Tool) to force the clients to use a different KMS Host to license against.

 

KMS publishing should be in your DNS somewhere [ Configuring DNS ] see if you can find the SRV records for your KMS boxes and make sure they're the only VLMCS SRV records that exist.

[forkies]

You can use VAMT2 but I would recommend starting to look at VAMT3 this works really well and keeps you up to date.

 

Alternatively you can run a script/cmd on the computers having the issue:

 

In cmd run:

cd "C:\Program Files\Microsoft Office\Office14\"

ospp.vbs /sethst:

ospp.vbs /act

 

Also obviously if you are running x64 you need in program files (x86)

 

This should direct the office kms requests to the new server.

[Marshall_IT]

You can use VAMT2 but I would recommend starting to look at VAMT3 this works really well and keeps you up to date.

 

Alternatively you can run a script/cmd on the computers having the issue:

 

In cmd run:

cd "C:\Program Files\Microsoft Office\Office14\"

ospp.vbs /sethst:

ospp.vbs /act

 

Also obviously if you are running x64 you need in program files (x86)

 

This should direct the office kms requests to the new server.

 

Thanks, running VAMT3 fixed the issue.