If the computers the organisation wants to activate using KMS are using any of these operating systems and the network allows DNS auto-discovery, no further configuration is needed. Configuring KMS Clientsīy default, Volume Licensing edition of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 are KMS clients. Note I add cscript to the front of the command so that the output stays within the command window, this lets me output/scroll if there is a lot of data where as the usual vbs dialog crops the output. So the most common command that i used were:ĭisplays license information (KMS Activation Count)įor Office specific information you can run the below command to get the info wanted:Ĭscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864 Note to execute changes you will need elevated command prompt. ![]() To see all the commands simply run slmgr from the command prompt. Once its running there is no real reason to keep going in and checking up on it.Īll functions to view settings and make changes are done through the already used VBS script slmgr.vbs. Now i will go into administering the KMS server, which will be quite brief as there is not much to it, and is really only there to aid in troubleshooting, and to have a sticky beak when implementing it. I take it now you want to see whether it works and if clients can be activated. To help monitor this, please refer the the section below. Now you are ready to activate Office 2010 with KMS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |