He saved the PowerShell script, documented the steps, and added a calendar reminder for 170 days from now: "Check KMS activation count."
Alex realized his server wasn't licensed for the new key. He needed to first. A quick phone call to their Microsoft partner, a rushed $500 license upgrade, and 20 minutes later:
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." Office 365 Kms Activation
The issue wasn't the KMS host itself. The issue was .
Alex refreshed the KMS dashboard.
Alex's fingers flew. He downloaded the correct from Microsoft's admin center (thankfully, his global admin account still worked). In an elevated command prompt:
By 7 PM, the CEO sent a follow-up: "Never mind—Word just unlocked for everyone. What did you do?" He saved the PowerShell script, documented the steps,
slmgr /dli showed the old Office 2016 KMS host key. Fine. But the new Office 365 clients were looking for a different KMS host key—one tied to Microsoft's subscription activation.