But Dave had retired to a fishing boat in Florida, and Alex had inherited the server like a ticking time bomb.
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."
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: Office 365 Kms Activation
He then enabled DNS auto-discovery so Office 365 clients would find the new KMS host:
Alex refreshed the KMS dashboard.
Alex smiled, leaned back, and replied: "Just refreshed the KMS host. Have a good weekend."
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. But Dave had retired to a fishing boat
"Carmen, my KMS host is serving Office 2016 keys. Office 365 clients are getting rejected. Can I convert the host?"