Today i want to write a few lines, about how you perform a rearm of your Office Installation using MDT or ConfigMgr / SCCM. Rearming the Office Installation is key, if you put Office in your Reference Image.
Let’s get through the basic, common questions first.
Why do I need to rearm my Office Installation?
As Windows has its SID, so does Office have a unique ID called CMID which is generated as soon as Office gets installed. The CMID must be unique, so that the Volume Activation using KMS works without any issues.
When do I need to rearm my Office Installation?
You need to rearm Office if you include it in your Reference Image. If you deploy Office to existing Devices, you don’t need to perform a rearm as the CMID is already unique. I saw in the past some cases, where a rearm was not necessary for the CMID to be unique, but I haven’t figured out yet why. However, if you want to be 100% sure, you should always rearm office when build a reference image.
How do I rearm my Office Installation?
You can perform a Manual rearm by executing OSPPREARM.EXE, which can be found in your Office 2013 or 2016 Installation Directory. See the Table at the End of the Blog Posts, which contains the path to OSPPREARM.EXE for the different Office Versions.
Does Sysprep rearm the Office Installation?
Simple Answer: No. The normal Sysprep Command does not rearm the Office Installation. However, there is a rearm Functionality in MDT, which is rearming an Office 2010 Installation. More information about that behavior is in the MDT Section below.
How can i view the CMID?
Open an elevated command prompt on a Client where Office is installed, change into your Office Directory and run the following command:
cscript ospp.vbs /dcmid
With the Release of Update 2 for MDT 2013, the Rearm functionality is now present in LTISysprep.wsf, for Office 2013 and for Office 2016. If you already run Update 2, you don’t need to implement my Rearm Script!
If you are using Microsoft Deployment Toolkit to generate your Reference Image, there is a slight chance that you don’t need to do anything. As written above, the normal Sysprep Command does not rearm the Office Installation. However, MDT rearms an Office 2010 Installation (only!) automatically when it reaches the Execute Sysprep Step in your Task-Sequence.
You can verify this by opening the LTISysprep.wsf as below:
Here you can also see the Problem. There is only a rearm Section for Office 2010, but not for Office 2013 and neither Office 2016.
For this reason, I created a script which rearms Office 2013 and Office 2016 which you can find on GitHub.
After downloading the script, follow these steps to create a new MDT Application and embed it in your Reference Build Task-Sequence
Additionally, you can verify this, be executing the above Command on a few deployed Devices. If the CMID is unique, then the cleaning was successful.
ConfigMgr / SCCM
Unlike MDT, Configuration Manager does not perform any rearm action. If you are using Configuration Manager to create Reference Images, you can simply put a new Step in your Build and Capture Task-Sequence. Place the step, as below, before the Prepare Configuration Manager Step.
The step on the Print Screen below rearms an Office 2016 Professional Plus, 32-bit Installation:
I hope this blog post was helpful. If you have any additional notes or questions, let me know in the comments or write me on Twitter.