question

DenStorePingvin-2833 avatar image
0 Votes"
DenStorePingvin-2833 asked DenStorePingvin-2833 answered

Non-domain Clients Wont Change KMS Host

Hey all,

I've tried the most of the day to troubleshoot on non-domain joined device that wont change KMS host reference after setup of new KMS server.
Even though the old KMS server have been shutdown and the old SRV record deleted it keeps referencing to the old server.

I've noticed that on some of the non-domain joined devices they do not see any SRV record with nslookup and on some others they do.

The current client i'm testing on have the correct SRV record stored pointing to the new server.
If i do a slmgr /dli the KMS machine name from DNS still points to the old server.
Slmgr /ato fails saying that the KMS is unavailable.

On 2008 domain servers this seems to work without any problems.

I've tried following:

Slmgr.vbs /ckhc to disable KMS caching - and then slmgr /ato but it didn't work

Restart of host prolly 10 times.

Checked registry

89878-image.png




The new KMS server runs on Server 2019 and the test client runs Windows Embedded.

Any ideas?

windows-server
image.png (30.4 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DenStorePingvin-2833 avatar image
0 Votes"
DenStorePingvin-2833 answered

I've discovered the issue.
It was duo to firewall restrictions on the network.
I wanted to do a Test-Netconnection but sadly the PS version didn't support it.
I then asked the network department if they could see anything in the firewall and after they added the KMS host i was able to activate with slmgr /ato

We have different firewall restrictions for the retail environment.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TeemoTang-MSFT avatar image
0 Votes"
TeemoTang-MSFT answered DenStorePingvin-2833 commented

Re-Install GVLK keys to the non-domain clients.
https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

Next, try to use slmgr /skms to manually set the server name. Then use slmgr /ckms to clear it out. That plus an ipconfig /flushdns, should make sure that everything is reset as far as the kms host name.

http://technet.microsoft.com/en-us/library/dn502540.aspx


If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I get this error when applying the product key

91153-image.png



First tried with slmgr /ipk CSVLK key
Then tried with server 2019 GVLK key from the link you provided. Same error.

Also tried slmgr /skms [kms server] and then slmgr /ato but then it says that the KMS is unavailable.

0 Votes 0 ·
image.png (6.7 KiB)