Office 2016 Silent Install with Specops Deploy

In this blog post, I will walkthrough how you can silently install Microsoft Office 2016 on machines on your network using Specops Deploy / App. To get started, you will need to run the Office Customization Tool, and create a new setup customization file for Office 2016, as per the below:

  1. Extract the Office 2016 source files to a share file server or DFS location that can be used with Specops Deploy.
  2. Open a command prompt and navigate to the location containing the Office 2016 source files.
  3. Type setup.exe /admin to launch the Microsoft Office Customization Tool.
    Command Prompt setup.exe admin
  4. Configure Microsoft Office 2016 according to your needs:
    – Select Install location and organization name from the left pane and enter your organization name.
    Install location and organization name
    – Select Licensing and user interface from the left pane, and enter the product key.
    Licensing and user interface
    – Enable the I accept the terms in the License Agreement checkbox.
    – Set the Display level to None if you want the setup to run silently.
    – Enable the Suppress modal checkbox.
    – You may want to modify additional settings and features so I recommend reading through the available options.
    Setup properties
  5. When you have configured the desired settings, save the file in the “Updates” folder of your extracted Office 2016 installation files, and name it custom.msp.
  6. If you want to be able to remotely uninstall office, you will need to configure a SilentUninstall.xml file:
    <Configuration Product="ProPlus"><Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /></Configuration>
  7. Save this SilentUninstall.xml file in the same folder as the Office 2016 setup.exe.
    You now have all the ingredients required to create the Office 2016 Package in Specops Deploy App.
  8. Open the Specops Deploy / App GPMC snap-in.
  9. Select Click here to deploy a package.
  10. Click New Package…
  11. Select Legacy package, and click OK.
  12. Browse to the location of the file, and click Open.
    Note: The path to the source files should be in the UNC format.
  13. Verify that the Package Properties field has automatically been updated, and enter a description for the package in the text field.
    Office 2016 Package
  14. In the navigation pane, select Installation options. If you saved your custom.msp into the Updates folder, then you do not need to specify any additional information here.
    Office 2016 Package Installation options
  15. In the navigation pane, select Uninstallation options.
    Office 2016 Package Uninstalltion package
  16. In the Uninstall command text box, enter %SpecopsDeployExecuteDir%\setup.exe
  17. In the Uninstall command parameters text box, enter:
    /uninstall ProPlus /config silentunistall.xml
    Note: The following SilentUninstall.xml file should be placed in the same folder as the office setup.exe.
  18. Click OK.
  19. In the new dialog box, select Office 2016 package, and click Next.
    Deploy Package Wizard
  20. Select an existing Target from the target drop-box, or click Create a new Target. If you are creating a new target you will need to:
    – Enter a name for the target
    Office 2016 Target
    – In the navigation pane, select Target criteria. Specify the target criteria, and click OK. In the example below, we have based the Target on AD group membership. This is the most common and recommended way to target many applications.
    Office 2016 Target Criteria
  21. Select your Office 2016 Target, and click Next.
    Select Office 2016 Target
  22. On the third page of the Wizard, select:
    Download and install, leave source files in cache
    Uninstall the package if the deployment falls “Out of Scope of Management”
    – Note:
    The second option means that if a computer is removed from the Office 2016 group, Office 2016 will be removed from that computer.
    Deploy Package Installation Type
  23. Click Next to continue.
  24. Select the date/time that Office 2016 should be deployed, and also if it should be deployed as the computer starts or if it should be installed at the next GP refresh after the user has logged in.
    Deploy Package Installation Time
  25. Select your user interaction options.
  26. Click Finish to save your settings.

All you need to do now is add a test computer to the group you specified as the Target, wait for group policy to refresh (or run a gpupdate), and Office 2016 will be installed onto that machine. We would then recommend that you remove that machine from the group, run another GPupdate on the machine, and confirm that Office 2016 is silently removed.

Want to deploy Office 365? See how Specops Deploy can help.

(Last updated on August 9, 2023)

Tags: , ,

darren james

Written by

Darren James

Darren James is a Senior Product Manager at Specops Software, an Outpost24 company. Darren is a seasoned cybersecurity professional with more than 20 years of experience in the IT industry. He has worked as a consultant across various organizations and sectors, including central and local governments, retail and energy. His areas of specialization include identity and access management, Active Directory, and Azure AD. Darren has been with Specops Software for more than 12 years and brings his expertise to the support and development of world-class password security and authentication solutions. 

Back to Blog

Related Articles

  • Deploy Greenshot (open source application) with Specops Deploy / App

    Greenshot is an open source screenshot tool, similar to the Windows Snipping Tool, but with more functionalities – and it’s free. In this blog, I will demonstrate how to install an open source application such as Greenshot with Specops Deploy / App in a simple and standardized way. There are three steps you need to…

    Read More
  • Adobe Reader best practices with App Deploy

    A customer recently asked me: What is the best way to handle all of the numerous Adobe updates?  After the initial install, updates may be required quite frequently.  How do you manage it?  I turned to my colleague Johan and sought his advice on the best practices. If each update is handled separately in Specops…

    Read More