![]() ![]() The first two scrips come back as expected. I recall an issue a long while back, that the VAtools used a different set of xrms and needed an update, but the script would succeed? KMS Activation in Windows Server 2019 - Microsoft Tech CommunityĪctivate using Active Directory-based activation (Windows 10) - Windows Deployment | Microsoft Docs ![]() You might need to use VAMT (on a PC as a proxy) though, in case you have no access outbound from the DC to the cloud activation service.? Install the new PKEY as ADBA object: cscript slmgr.vbs /ad-activation-online Install the new PKEY on this server: cscript slmgr.vbs /ipk You could try using the old-school slmgr.vbs method instead of the VAtools? (the VAtools are much easier to use though)Ĭheck ADBA objects: cscript slmgr.vbs /ao-listĬheck current server config: cscript slmgr.vbs /dlv ![]() If it was a lack of permissions in AD, you’d get a different error to this, and your test with removing/reading the older PKEY would have failed too. I used to see a lot of this back in the days when WS2012R2 was new, and it was always due to a missing windows update package (update the SLC DLLs and the xrms (PKEY recognition data). This sure looks to me that your server (where you’re trying to process the PKEY) is missing the needed SLC updated DLLs etc. (unless you’re stuck on WS2003 but I think that would block you from adding WS2016 as a DC?) Nope it’s not the DFL or FFL nor Schemaversion or that stuff. Okay, thanks, that error message clarifies nicely. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |