He opened the Volume Activation Tools. He needed to install the —a specific key from Microsoft's Volume Licensing Service Center. The problem: Dave had the VLSC password. And Dave was on his boat, unreachable until Monday.
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
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: He opened the Volume Activation Tools
cscript slmgr.vbs /dli cscript slmgr.vbs /dli all Finally, he forced a test on his own laptop. He opened an elevated Command Prompt on his Windows machine, navigated to Office's installation folder: And Dave was on his boat, unreachable until Monday
The issue wasn't the KMS host itself. The issue was .
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."
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.