11/3/2023 0 Comments Windows server 2019 kms host key![]() ![]() If it answers with FQDN of your KMS host, then it's all working. To check if DNS is present and correct, run (best to test from a box that isn't a DNS server or the KMS host): Then enable this host (which has just installed a KMS key) to activate other hosts, with the MS clearing house, using the normal activation command for activating online:Ĭscript C:\windows\system32\slmgr.vbs /ato (this should also create an SRV DNS record in your zone) If the key you have already installed is wrong for the OSes you are trying to activate, first try:Ĭscript C:\windows\system32\slmgr.vbs /upk (to uninstall OS product keys)Ĭscript C:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (using your KMS key, to activate this single machine) Add a Windows Server 2019 / 2016 key (whatever you are licensed for). If they are split across multiple sites / subnets / VLANs, you will need a workable record in each segment.Ģ) Don't try to add a W10 key (depending on release) into a Windows Sever 2016 KMS host server, although it might work in some instances and version configurations, you need to keep track of what you can and can't activate. Your DNS records will determine where DHCP clients look for activation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |