![]() I'm wondering if I need to reach out to MS to issue a new license key? Your feedback is much appreciated. Manually executed the activation from several workstations with no success running ospp.vbs:sethst:"KMSServerName".Performed various tests running the cscript ospp.vbs command tool with no concrete results.Windows slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX slmgr.vbs -skms slmgr.vbs -ato Office cd C:Program FilesMicrosoft OfficeOffice15 cscript ospp.vbs /inpkey:YC7DK-G2NP3-2QQC3-J6H88-GVGXT cscript ospp.vbs /sethst: cscript ospp. Performed connectivity tests from one of the desktops running Office 2010 to the KMS server and confirmed desktop/ server can talk to each other and reach the KMS service Start a Command Prompt as an Administrator.I've confirmed the KMS key is valid and active.Am I running into a compatibility issue here? I've gone up and down the Microsoft KBs and can't find anything documented on this issue. The users allocated to this pool are getting the annoying activation wizard pop up every time they open any of the Office apps. We have a pool of desktops running Office 2010 (soon to be updated) that it is not activating. So far, the Windows Server activations, Win 10 and Office 2016 are activating properly. ![]() The KMS service was previously running on a 2008R2 VM. One of the services migrated to a new 2019 server is KMS. We are in the process of upgrading from Server 2012 and some legacy 2008R2s to Server 2019. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |