How-to: Deploying Microsoft Office 2016 using SCCM 2012

This Step-by-step guide describes how to prepare and add Microsoft Office Professional Plus 2016 to the Application library of System Center 2012 R2 SP1 Configuration Manager (SCCM), by using the designated functions for doing this in the Configuration Manager Console interface.

 
 
 
 
 
4.1 Star
(14)
22,846 times
Add to favorites
System Center
10/2/2015
E-mail Twitter del.icio.us Digg Facebook
  • Enable the installation progress bar.
    1 Posts | Last post June 03, 2018
    • I have use the silent installation to deploy MS Office 2016 but unfortunately, most of our users come across issue with incomplete installation ( They got both MS office 2013 and Ms Office 2016 component likes both Lync 2013 & Skype for business).
      
      I believe this is because during installation, users is using that office component that make it not totally upgrade to new version. Therefore, I would like to make users is aware during deployment and the installation is visible to user during installation.
      
      I think this is related to Display Level setting when set for OCT.I have change it to use Basic with Supress Modal + No cancelation checked but it failed as its still install without any progress indicator.
      
      Can everyone here help me with that, what I want now is to auto deployment to users but more similar like manual installation that users is aware there is installation is going on and stop of using all MS office component for a while until its complete installation. 
      
      FYI, I have also choose Full Feature with Supress Modal checked and as I monitored at Software Center, its does do the download but its stuck at that point without proceed to install and visible the installation progress bar.
      
      I'm new with SCCM and this is first time that the silent installation is not go as for our plan.Can anyone help me with this issue.
      
      Thanks. 
  • Deployment via SCCM - Old versions not uninstalling
    1 Posts | Last post July 05, 2017
    • Hello, we are deploying via SCCM 2012 and I have configured the Microsoft Office Customization Tool properly for our environment, and it installs as it should. However, the old versions of Office that are already installed (office XP through 2013) do not uninstall automatically. I have tried the settings under Remove Previous Installations set to default, and also I have selected manually all items to remove, but it does not remove them.
      
      So far this has been attempted on Windows 7 and Windows 10 with the same results when deploying to each OS. 
      
      I have read in a few places that the native uninstall option when installing Office 2016 no longer works, and from what I am seeing that appears to be the case. Have you any way to remove these old versions without creating a script to check for each version and remove, repeat, then install Office 2016?
      
      Thank you!
  • Deploying Office 2016 as a Package
    2 Posts | Last post March 14, 2017
    • I am a novice when it comes to Config Mgr. So bare with me. I followed your steps all the way to customizing Office. Instead of creating an application, where it involves user interaction. I would like to deploy Office 2016 ProPlus as a package. 
      
      I know it involves pointing Config Mgr to a install BAT file. 
      
      Here's what I have and please tell me if where I went wrong. 
      
      <Configuration>
        <Add OfficeClientEdition="32" Channel="Current">
          <Product ID="O365ProPlusRetail">
            <Language ID="en-us" />
          </Product>
        </Add>
        <Updates Enabled="TRUE" Channel="Current" />
        <Display Level="None" AcceptEULA="TRUE" />
        <Property Name="AUTOACTIVATE" Value="1" />
        <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
        <Logging Level="Standard" Path="%temp%" />
      </Configuration>
    • Hi Bajanbus,
      
      Do you get any errors if you run setup outside SCCM (manual setup from a command line)?
      If it's not working 100% silent outside SCCM it work inside SCCM.
      
  • OSD Office installs take forever - others run like lightning, but eventually everything works.
    2 Posts | Last post July 04, 2016
    • When we build PCs using SCCM OSD, we're installing Office 2016 ProPlus as a step in the TS. Every time the Office installer runs, there's a ton of drive activity for about 5-7 minutes and then the Office install hangs for the next 4 hours. Eventually it will time out and Office and all other applications install correctly.
      
      I suspect it has something to do with a proxy that is not getting authenticated. How do I get rid of the 4 hour delay? 
    • Normally you don't need Internet/Proxy access when deploying Office 2016.
      It's really hard to guess whats you problem is, but you'll need to check all the TS and Office log files to find out whats causing this problem.
      Also make sure that Office can be installed 100% silent outside SCCM. If you get a final OK prompt, the installation is not silent.
  • OCT issue with 64bit Office 2016?
    2 Posts | Last post October 20, 2015
    • Have you run into any problems getting the OCT to launch with the 64bit edition of Office Pro Plus 2016?  Running setup /admin just doesn't seem to launch anything for me with the 64bit edition however it works just as expected with 32bit.  I'm guessing I can't create a custom installation file with 32bit and copy that into the custom folder in the 64bit source location though I'm in the process of testing that out soon.
    • Hi Scott,
      I've not tested the 64-bit deployment.
      Do you have an "Admin" folder in the office setup folder?
      
      Another question. Why do you want to use a 64-bit version of Office? 
  • Autoactivate of MAK?
    2 Posts | Last post October 05, 2015
    • Using a MAK key... I set auto_activate - 1, but it doesn't work. Even tried "autoactivate". Ideas?
    • To be honest, I haven't tested MAK yet. Only KMS.
      Can you confirm that you can activate Office manuel if you try? Just to verify that the key is valid.