Do you have any other idea why this isn't working? Thank you. That tells me it is licensed, with a CSVLK key, and should activate WS2022 servers. So it’s of to the Volume License Servicing Center to get the bits and the keys.
Here is an excerpt from my original post: It’s a great day as Windows Server 2012 R2 and Windows 8.1 bits have gone GA (General Availability). I already have applied and activated that key. Now the Image is ready to deploy and the KMS server will receive different CMID’s from the servers.
I can even enter this command on the 2022 system to manually tell it to use our KMS server (Yes, I joined the 2022 system to our AD domain)ĭoes anyone know if these keys are simply too new? Might there be a patch or MCU required on older Windows Server O/Ss to be able to activate newer versions? I know there was a patch back in the day that 2012 R2 KMS servers needed to install before they could successfully activate 2016 servers. Now set make sure the Skiprearm is set to 0 at the following location: HKEYLOCALMACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform. EDIT: Next time you might add that you use the EVAL (saw it in your reddit post). In Win 8/Server 2012 and later non-EVAL versions there is no such Grace that can be resetted hence the Rearm is deprecated. Something prevented us from communicating with our activation servers. Rearm is only usefull to reset any Initial Grace Period in Win 7 (the 30 days) and the Activation Grace Period in EVAL versions (limitted). This is a problem most users need a solution to if the command is not working in the first-ever attempt on a system. Key Management Service is enabled on this machineĭoes anyone know why WS2022 won't activate yet? This is what I get on my WS2022 systems: Windows Server License Manager Script is a tool based on visual basic library and sometimes the slmgr rearm command may not work due to lack of presence of this library. Name: Windows(R), ServerDatacenter editionĭescription: Windows(R) Operating System, VOLUME_KMS_WS22 channelĮxtended PID: 03612-0433-14393.0000-1972021 We have 2 servers both running Windows Server 2012R2 installed on physical. When I type slmgr.vbs /dlv all, I see this entry:
I like doing posts which shows some cool hacks, and this is exactly this kind of post How To Reset 120 Day RDS Grace Period on 2012 R2 Server. If you are using windows server with trial license and reinstalling windows after every expiry then you don’t need to reinstall in each expiry anymore. Yes, in fact, there is cool hack which allows you to reset the 120 day grace period on Windows Server 2012 R2 RDS, and we'll show you how. I used these commands on our KMS server (running WS2016):īoth commands were successful. Reinstall the server (redeploy the VM) or cheat a bit.