Archives

Ben-78

KMS activation problems

I part-time manage a branch office IT infrastructure. (More formally, I am developer who has unofficially assumed the IT role.) There are other sites within the company running a common domain. Originally we were not connected  via site-to-site VPN
to other sites, so we created our own separate domain. After a number of years things have changed and we are now connected and are moving our IT infrastructure to the common domain. This has been progressing for a few months, generally fairly smoothly.

We also have two Hyper-V hosts, one running Windows Server 2008 R2 Datacenter. I set it up a number of years back and until now have not had any problems. Recently I noticed one of our VMs that I had moved from the old domain to the new domain a few weeks
back had failed to register its IP in the DNS. Checking the event log indicated KMS failures. I naively tried to re-activate it: slmgr /ipk 74YFP-3QFB3-KQT8W-PMXWJ-7M648. The screen turned black and indicated that Windows is not genuine.

I have checked several of the other VMs, but there does not seem to be any significant issues so far. Please note that the VM host is still in the original domain. Googling around I found this,
I found this indicating to check the SRV record for _vlmcs._tcp. The domain had changed, so this was pointing to the old domain. (Still available if necessary.) I updated it in the new domain DNS. I have also verified that the VM host server is available over
port 1688 via telnet.

I then ran the above slmgr /ipk again. It indicates that the key was successfully applied, but Windows still indicates that the environment is not genuine. I’d appreciate some help in resolving this.

Here is the output for slmgr /dlv on the Hyper-V VM host.

(Please let me know if this contains any keys that I should not post here and I will gladly edit it.)

—————————

Windows Script Host
—————————
Software licensing service version: 6.1.7601.17514

Name: Windows Server(R), ServerDatacenter edition

Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_C channel

Activation ID: 8fe15d04-fc66-40e6-bf34-942481e06fd8

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 55041-00168-305-513198-03-1033-7601.0000-2252011

Installation ID: 017750272912111325448091054514636704605876070861877344

Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342

Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343

Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345

Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344

Partial Product Key: K8W74

License Status: Licensed

Remaining Windows rearm count: 3

Trusted time: 4/25/2019 2:55:52 PM

Key Management Service is enabled on this machine

    Current count: 1

    Listening on Port: 1688

    DNS publishing enabled

    KMS priority: Normal

Key Management Service cumulative requests received from clients

    Total requests received: 2

    Failed requests received: 0

    Requests with License Status Unlicensed: 0

    Requests with License Status Licensed: 0

    Requests with License Status Initial grace period: 0

    Requests with License Status License expired or Hardware out of tolerance: 0

    Requests with License Status Non-genuine grace period: 0

    Requests with License Status Notification: 2

—————————
OK   
—————————

And here is the same output for the problematic VM client.

====================

—————————
Windows Script Host
—————————
Software licensing service version: 6.1.7601.17514

Name: Windows Server(R), ServerDatacenter edition

Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel

Activation ID: 7482e61b-c589-4b7f-8ecc-46d455ac3b87

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 00496-00168-001-000128-03-1041-7601.0000-1152019

Installation ID: 007722422601855746498885195842058945462581432133218512

Partial Product Key: 7M648

License Status: Notification

Notification Reason: 0xC004F056.

Remaining Windows rearm count: 3

Trusted time: 2019/04/25 14:58:42

Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

—————————
OK   
—————————

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3363