I believe “%ProgramFiles(x86)%\Microsoft Office\Office15\OSPPREARM.EXE” not to work as a sequence command. You can use the “cscript ospp.vbs /dcmid”, to investigate what state the activation is in. Restart the machine and put in the right OU. When you’re testing if you’ve solved the problem don’t assume that the rearm has failed straight away if Office has not activated 2 seconds after the build has finished. Will cause Office to activate received a CMID from the KMS server. You can check for duplicate across child and parent machines. Will identify if Office has received a CMID from the KMS server. If you make your own simplified command task or even call the same code manually, you’ll have more maintenance overhead and in some cases less supported platforms and applications.įor example the following added as a sequence command will work only for Office 2013 on Windows 圆4.: This will give you support for Office 2013 & 2016 on both 32 & 64bit operating systems.
I would recommend solution one and Update MDT.
Update to MDT 2013 Update 2 or higher as Microsoft have improved Office Rearm support.This article from Scott Ladewig covers this well. However this script does not support Microsoft Office 2013 or greater and these versions of Office will not be “Rearmed prior to capture”. MDT 2013 Update 1 has an Office 2010 “Rearm” built into the f script. Office has a very convenient utility “OSPPREARM.EXE” designed to remove this CMID.
This is being copied onto all child machines captured from this image. Office is given a unique ID (CMID) during installation. MDT 2013 Update 1 or Less/Microsoft Office 2013 or Greater Cause: Microsoft Office 2013 (or Higher) is failing to activate via KMS on machines built from MDT with Office pre-installed on the wim image.