
If you are NOT in United States, at a command prompt, type c:\windows\system32\slui.exe 4, and then select your country/region to get the phone #. If you are in United States, you can dial phone # 88 to input your installation ID. You may have to put dashes after every six characters in the installation ID. You see all the license files that are installed on your KMS server.Ĭopy the activation ID and installation ID into Notepad. Type cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864, and then press Enter. More Informationĭownload and install Microsoft Office 2010 KMS Host License Pack.Īt a command prompt, change the directory to c:\windows\system32. This article describes how to activate the Office 2010 KMS host through telephone when you are in a disconnected environment. VAMT 2.0 allows administrators to automate and centrally manage a range of activities related to Windows client, Windows Server, and Office 2010 activation.This article was written by Eric Ashton, Senior Support Escalation Engineer. Volume Activation Management Tool (VAMT) 2.0 Download Volume Activation Management Tool (VAMT) 2.0 On the KMS Host, using an elevated command prompt type slmgr.vbs /dli to view license information. For more information about the ospp.vbs script, see Tools to configure client computers in Office 2010. To trigger activation manually on the KMS client, run ospp.vbs /act. At that time, if the KMS host has a sufficient count, activation will be successful. If activation fails, the computers will attempt activation two hours later.


If you deploy Office 2010 to more than five computers, their initial activation requests will be used to build up the count. If the KMS host does not receive more than five requests, KMS clients will not be activated. The Office 2010 KMS host must receive activation requests from at least five Office 2010 KMS clients before KMS clients on that network can be activated. When trying to activate Office 2010 with KMS you recieve the error: 0xc004f038 (Unknown Error).Īccording to Microsoft, this occurs when the client activation request count on the KMS host is not high enough for client computers to activate
