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.
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:
Six months ago, Alex had migrated the company from Office 2016 (perpetual, KMS-friendly) to Microsoft 365 Apps for enterprise (subscription-based, designed for cloud activation). He'd assumed the old KMS server would just handle the new clients. It did not. Office 365 Kms Activation
Alex refreshed the KMS dashboard.
He saved the PowerShell script, documented the steps, and added a calendar reminder for 170 days from now: "Check KMS activation count." He opened the Volume Activation Tools
He RDP'd into the KMS server—a quiet Windows Server 2019 VM humming in the corner of their data center. He opened PowerShell.
"Of course," Alex muttered. "They changed the product activation type." 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."
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.
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:
Six months ago, Alex had migrated the company from Office 2016 (perpetual, KMS-friendly) to Microsoft 365 Apps for enterprise (subscription-based, designed for cloud activation). He'd assumed the old KMS server would just handle the new clients. It did not.
Alex refreshed the KMS dashboard.
He saved the PowerShell script, documented the steps, and added a calendar reminder for 170 days from now: "Check KMS activation count."
He RDP'd into the KMS server—a quiet Windows Server 2019 VM humming in the corner of their data center. He opened PowerShell.
"Of course," Alex muttered. "They changed the product activation type."
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."
