Open a Command Prompt window as an administrator.If so, you (or your administrator) might have to change the proxy settings for Windows HTTP clients. Check whether you're behind a proxy serverĪre you behind a proxy server? If you're not sure, ask your administrator. The Microsoft Support and Recovery Assistant runs on Windows PCs and can help you identify and fix activation issues with Microsoft 365. Identify and fix activation issues by using the Support and Recovery Assistant for Microsoft 365 After each step, check to see whether the issue is fixed. Follow these steps to help troubleshoot the issue. This issue might be caused by one of several circumstances. Please check your network and try again later. Activation fails and you receive one the following error messages: This will rearm the office activation and prevent any pop-ups on first run once the image is deployed.Īs always, if you have questions or would like assistance applying this in your own environment, contact PEI directly at 30.This article discusses how to troubleshoot the activation issues in Microsoft Office from Microsoft 365. To do this, add a command line item to your image capture task sequence (right before the sysprep item) in MDT that runs the following command “%programfiles%Microsoft OfficeOffice15ospprearm.exe”. To fix this, you have to rearm (pronounced re-arm) the Office Activation. What I discovered is that even though the install occurs silently in the build process, Office thinks that it is a new install after the image is applied. To ensure there was no issue with the MSP file, I confirmed the MSP worked by manually testing it on a clean install of Windows 8.1. After the system is imaged, the user is prompted to activate Office at first run.

After the image is created in MDT, I deploy it using SCCM 2012. I have created an MSP file using the Office Customization Tool that activates office and disables all first run pop-ups. I use MDT to build my image, and during the image build process Office 2013 is installed. Recently I came across an issue when attempting to silently deploy Office 2013.

Activating office 2013