I’ll do that on an example Task Sequence, which is deploying Windows 10 Enterprise. Knowing the above commands, you can now start to integrate them into your OSD Task Sequence. When done, you actually need to perform the Activation Request, using the following command: "%WINDIR%\system32\slmgr.vbs" -ato Modifying the ConfigMgr Task Sequence The following is an example, which sets the KMS Server to “” "%WINDIR%\system32\slmgr.vbs" -skms Running this Script with the Parameter “-skms” allows you, to set a static KMS Server and overwrite the value, that was retrieved using DNS. Setting a static KMS Server manuallyįor configuring Volume Activation Tasks on a Windows Operating System, you have to use the Script “slmgr.vbs”, which can be found in “C:\Windows\system32”. However, if you are currently preparing a new KMS Server, you might want to channel your new clients to this dedicated KMS Server only. This works great if your KMS Server is already in Production. Usually, a Client uses a DNS Service Locator to find its KMS Server for sending the Activation Request. This includes Products like Windows or Office, for example. Microsoft’s Key Management Server, better known as KMS, is around for many years and helps Administrators around the world activating Microsoft Products in their Enterprises.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |