We installed Office2019 on Windows Server 2019 and active it by volume license. However, we found we often need reactive the office2019 every two or three months.
Office 2019 often needs reactive on Windows Server 2019 Standard
If you resolved it using our solution, please click "Accept Answer" on a reply to help other community members find the helpful reply quickly.
If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
Office repeatedly prompts you to activate on a new PC
https://support.microsoft.com/en-us/office/office-repeatedly-prompts-you-to-activate-on-a-new-pc-a9a6b05f-f6ce-4d1f-8d49-eb5007b64ba1
Besides, check your KMS server configurations.
https://theitbros.com/ms-office-2016-activation-with-kms/
If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks for your answers. I'd like to clarify our question.
We are using MAK function to active office, so the office don't need active anytime untill reinstall image. However, the office product key often back to KMS every two or three months. We don't know why and how to solve it.
Have you ever configure KMS activation for Office?
If you're using MAK to activate volume licensed versions of Office 2019, you specify the key in the configuration.xml file used by the Office Deployment Tool when you deploy Office 2019 to the users in your organization
https://docs.microsoft.com/en-us/deployoffice/vlactivation/activate-office-by-using-mak
If only one server 2019 client appears office activation issue, try the guide here to install office 2019 and activate it by your MAK.
http://www.chamshantemple.info/blogs/how-to-install-office2019-for-windows-server-by-vlsc-license/
Thanks for your reply.
No, we configured MAK activation for office and specify the key in the configuration.
This issue happened more than one server 2019.
Strange, I suggest to open a support ticket with Microsoft for deep research, due to limited condition, forum can’t reproduce your scenario for test, thanks for understanding.
https://support.serviceshub.microsoft.com/supportforbusiness
7 people are following this question.
