KMS Server no longer activated
Hi Experts,
At the start of the year I setup a KMS server on a virtualised 2008R2 server. It was working perfectly for a while, clients activating etc., and then after about 4-5 months some strange activation issues started occuring. It was then I thought something was up with the KMS server so I uninstalled the KMS key (using slmgr.vbc -upk) then re-installed the key and attempted to reactivate which failed with the following;
Activating Windows Server(R), ServerStandard edition (68531fb9-5511-4989-97be-d
Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable
When I Google that error code I only seem to get articles relating to problems acivating Windows 7 and Server 2008R2 against KMS servers installed on 2003/2008 Server which isn't really my problem.
So, now I have a KMS server that won't activate and I have Windows 7 clients which seem to be falling off as well. Happy to provide more details if needed.
At the start of the year I setup a KMS server on a virtualised 2008R2 server. It was working perfectly for a while, clients activating etc., and then after about 4-5 months some strange activation issues started occuring. It was then I thought something was up with the KMS server so I uninstalled the KMS key (using slmgr.vbc -upk) then re-installed the key and attempted to reactivate which failed with the following;
Activating Windows Server(R), ServerStandard edition (68531fb9-5511-4989-97be-d
Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable
When I Google that error code I only seem to get articles relating to problems acivating Windows 7 and Server 2008R2 against KMS servers installed on 2003/2008 Server which isn't really my problem.
So, now I have a KMS server that won't activate and I have Windows 7 clients which seem to be falling off as well. Happy to provide more details if needed.
Dear Schikitar,
did you get any further with this?
Kind regards,
Soren
did you get any further with this?
Kind regards,
Soren
ASKER
Hi Soren,
Thanks for your response!
I've checked DNS and all is well on that front so I don't think there are any issues there - even when we manually specify the KMS server and do a manual activation. I have also been using the Volume Activation Management Tool (VAMT) 2.0 - http://www.microsoft.com/downloads/details.aspx?familyid=EC7156D2-2864-49EE-BFCB-777B898AD582&displaylang=en - which is really helpful.
The other interesting thing is that I am also doing Office 2010 activations on this server and they are working (but not on our wireless network). On ethernet Office will activate on clients but not Windows, on wireless neither Windows nor Office will activate. I think there are two separate problems and I'm sure I can work out the wireless traffic issue but the fact that ethernet Windows clients won't actiavte is the thing that is bothering me most...
Thanks for your response!
I've checked DNS and all is well on that front so I don't think there are any issues there - even when we manually specify the KMS server and do a manual activation. I have also been using the Volume Activation Management Tool (VAMT) 2.0 - http://www.microsoft.com/downloads/details.aspx?familyid=EC7156D2-2864-49EE-BFCB-777B898AD582&displaylang=en - which is really helpful.
The other interesting thing is that I am also doing Office 2010 activations on this server and they are working (but not on our wireless network). On ethernet Office will activate on clients but not Windows, on wireless neither Windows nor Office will activate. I think there are two separate problems and I'm sure I can work out the wireless traffic issue but the fact that ethernet Windows clients won't actiavte is the thing that is bothering me most...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Verify in your DNS that your KMS host exist there in as a KMS service record (_vlmcs._tcp).
You can do this on your computer running the following nslookup towards your DNS server:
nslookup -type=srv _vlmcs._tcp.[your domain]
I.e. if you were working for IBM, you would run:
nslookup -type=srv _vlmcs._tcp.ibm.com
This should return something like:
_vlmcs._tcp.ibm.com SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = myserver.ibm.com
myserver.ibm.com internet address = 192.168.1.2
Verify that the information in DNS correctly match your server in your domain.
Kind regards,
Soren