Home / server / Questions / 453924
In Process
NickC
Asked: 2012-12-01 08:26:04 +0800 CST

Deploying Office 2013 via GPO

  • 772

Looking at potential ways to deploy Office 2013 via GPO.

First and most obvious way is to run a startup script which calls the Office 2013 setup.exe. Problem here is what happens after it is installed, will that startup script keep re-installing the product every time the machine boots?

Another potential way is to install each Office component separately using the multitude of .msi files which are present, would that work and provide the same thing as a full install of Office? There is actually twenty three separate .msi files. What about officemui.msi is that a wrapper which contains calls to all of the other office components.

group-policy

2 Answers

  1. Installing from the .msi files is not supported. It just plain doesn't work.

    You have to install from a startup script (or logon script, but that's generally a bad idea). You'll want to write the startup script such that it checks for a previous installation.

    Also, it's the exact same process for Office 2010. And you can do some fun stuff like dumping Office, Visio, Project, and Sharepoint Designer all into one installation folder (still have to call setup for each individually, but saves on space)

    • 3

  2. I don't believe that deploying Office 2013 via GPO Software Installation is a supported method of deploying it. Here's a link to deploying it via computer startup scripts:

    http://technet.microsoft.com/en-us/library/ff602181.aspx

    • 3