

What's the best way to see if our folks are actually using the record meeting option on teams? Have you checked your KMS Host server is resolvable via DNS from a client machine? Run this from command line, the bottom line of the output should be the FQDN of your KMS Host: Then as long as the correct server KMS key is installed on the KMS host (a key for a version of Windows Server that will activate the client version you are trying to activate, generally the server version would be released at the same time as the client, or the server version would be newer) and you have followed all that was stated already, that's it. As long as your dns SRV record is correct and your clients are using that same DNS server, that's all you need for the clients to ask for activation. You can run slmgr /ato from a client machine if you want to force it to ask for activation now but again, you don't need to. Forget about the Windows 10 keys, you don't need them at all. You just need to let the clients request activation from the KMS Host server.

You don't need to run slmgr /ipk from a client. I am already activating office 2010 from this host kms server. It shows installed product key in it but it shows error, when i run slmgr /dlv and slmgr /dli Then,I went on Windows 10 client and put following command: I added windows server 2016 kms host in KMS host server. 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.
