He saved the PowerShell script, documented the steps, and added a calendar reminder for 170 days from now: "Check KMS activation count."
Alex had a choice: push internet-based activation to 200 laptops over VPN (slow, unreliable, and half the users were already offline for the weekend)… or find a workaround. Office 365 Kms Activation
Alex smiled, leaned back, and replied: "Just refreshed the KMS host. Have a good weekend." He saved the PowerShell script, documented the steps,
(his laptop). Then 4/25 . Then 12/25 . Other users, still online, were automatically reactivating as their Office clients performed their next background check-in. Then 4/25
cscript slmgr.vbs /ipk <New-Office365-KMS-Key> cscript slmgr.vbs /dli cscript slmgr.vbs /ato The first two commands worked. The third—activation against Microsoft's servers—failed. "Error: 0xC004F074. No KMS key found."
Carmen laughed. "You don't convert, Alex. You add. KMS can host multiple product keys. Just install the new Office 365 KMS host key alongside the old one. Then enable DNS publishing."
He then enabled DNS auto-discovery so Office 365 clients would find the new KMS host: