Software licensing service version: 3.379 C:\Windows\system32>cscript slmgr.vbs /dlv I have uninstalled and re-installed the KMS client setup key just to be sure. In that post the problem is that he had installed a retail key. Maybe it's doing that but I don't see any events for and ADBA attempt. My understanding is that it's supposed to tryĪDBA first and then KMS. How can I tell the server to do an AD activation instead of a KMS one? There's lots of info out there about troubleshooting KMS activation problems but I can't find much about AD based activation. We are keeping it around until we are entirely off Win 7 and don't need a KMS at all any more. That is a KMS server but it doesn't have the 2019 key loaded. The 2019 servers can see the AD objects: C:\Windows\system32>cscript slmgr.vbs /ao-listĪctivation ID: īut when you do an slmgr.vbs /ato they still try and talk to the KMS server rather than AD. I tried to get transferred to support but they wanted $500 for that privilege. I double checked this is a 2019 key in VLSC and even called support and they said it was a valid 2019 KMS key. Microsoft (R) Windows Script Host Version 5.812Ĭopyright (C) Microsoft Corporation. I already have a WindowsĢ019 KMS key loaded in AD and you can see that's what the 2016 and 10 clients are using to activate when you run slmgr.vbs /dlv C:\WINDOWS\system32>cscript slmgr.vbs /dlv We tried out our first Windows 2019 Servers today and they won't activate. It's been working fine for about 5 months. I have AD Based authentication already set up and working for Server 2016 and Windows 10 clients.
0 kommentar(er)
