KMS being overruled by Microsoft Activation server
tldr : For some reason the Microsoft activation link is taking precedence over my local KMS. Any ideas? The endpoints at my org have started to downgrade to Windows 10 Pro, sort of. On an effected endpoint, when I run slmgr /dlv, it says the endpoint is reaching out to https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail to activate. It also states that the license is Win10 Pro. However, if I run winver, it still comes up as Win 10 enterprise, which we are licensed for. We have had a KMS for a long time and it is and has been working fine. This just started happening recently. If I force the client to KMS by using slmgr /ipk "KMSKEY", then run /slmgr /ato, it correctly sets back to the kms. However, 4 to 8 hours later, it resets itself to point to https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail Its not group policy, I have run gpupdate /force and the endpoint is still looking at KMS. If I run nslookup -type-srv_vlmcs._tcp it comes back as the local KMS server, so I know my KMS is working ok. For some reason the Microsoft activation link is taking precedence over my local KMS. Any ideas?
Using Azure VM as KMS server
Hello Everyone, I have Azure subscription and have created windows 10 vm on azure. Now I want to configure this vm as KMS host to activate my local windows 10 clients machines. I have KMS host key. Can anyone provide me a guide or something like that? I have all necessary resources to do this but I have no enough experiences on azure. Thanks in advances!
