Office 2010 Out of Tolerance
-
Mittwoch, 20. Juni 2012 11:26
We have a network of around 400 desktops and laptops running Windows 7 and Office 2010. 99% of the machines have activated correctly through the KMS server on one of our 2 Domain Controllers (Windows 2008R2). We are using VAMT 2.0 to manage the KMS.
A couple of our Office installations are not activating. Our users are being told they have 22 days to activate. I've checked the KMS Key with the Volume License Service Center and it is correct. In VAMT, if I look under "not licensed" and "out of tolerance grace" I see four machines listed. If I right-click one of the machines and choose "Activate", "Online Activate", "Current Credentials" (I'm logged in as a Domain Admin) the machines status shows:
- Product Name: Office14, OfficeProPlus-KSM_ClientEdition
- Product Key Type: GVLK
- License Status: Out of Tolerence Grace
- Status of Last Action: The Software Licensing Service reported that the computer can not be activated. No Key Management Server (KMS) could be contacted.
There are a further 18 listed under "not licensed", "notifications" as "non genuine".
Yet the rest of the network, connected to the same domain, same dns, same domain controllers, with the same Office 2010 installation, are all licensed correctly?
Can anyone point me in the correct direction to resolve this.
Thank you
Alle Antworten
-
Mittwoch, 20. Juni 2012 21:45
- Product Name: Office14, OfficeProPlus-KSM_ClientEdition
- Product Key Type: GVLK
- License Status: Out of Tolerence Grace
- Status of Last Action: The Software Licensing Service reported that the computer can not be activated. No Key Management Server (KMS) could be contacted.
Hi, this sounds like this client pc is unable to successfully contact your activated KMS.
it may be having difficulty with networking or dns name resolution? or it has an incorrect KMShost name resolved/cached?
is it only the Office installation that is affected on this pc? (i.e. is it Windows7 KMSclient, if so, is that activated/licensed or OOT?)
on the affected client (or remotely from your admin pc), try running these commands:cscript slmgr.vbs affectedpcname /dli all
cscript ospp.vbs affectedpcname /dstatusyou may need to determine of the pc is misconfigured in some (by examining the results from these commands), and then use alternate commands to remove/modify/update/assert the needed settings.
ref: http://technet.microsoft.com/en-us/library/ee624350
Don
- Bearbeitet Don - tesgroupMicrosoft Community Contributor Mittwoch, 20. Juni 2012 21:46
- Als Antwort markiert Max MengMicrosoft Contingent Staff, Moderator Mittwoch, 27. Juni 2012 09:45

