If you are looking at deploying Office 2007 via Group Policy you may have noticed that Microsoft have changed the game. Office 2007 is no longer deployed using transform files; it now uses Windows Installer patches (.MSP) or CONFIG.XML to customise the Office installation.
When you deploy any of the Office 2007 applications, you can add MSP files to the \Updates folder and they will be installed automatically by Office setup. This simplifies updating Office by ensuring updated machines can still use the original network sources files but means that administrative installations are no longer available The change to MSP files for customising Office has implications for deployment - you can’t add an MSP file to an application in the Group Policy object.
Microsoft has recently added a document on TechNet that describes what you’ll need to do to deploy Office 2007 via Group Policy. In this document they give details why software deployment via Group Policy is not scalable for larger customers:
- Unable to schedule installations and controlling bandwidth.
- Limited scalability for concurrent deployment more than 200 concurrent installs could cause issues.
These types of limitations are well known to anyone who has deployed applications via Group Policy, but here’s a few more that are Office 2007 specific:
- MSP files added to the
\Updatesfolder are not installed when deploying Office via Group Policy. This is obviously a big hurdle and Microsoft doesn’t give any reason for this behaviour.
- Office 2007 cannot be advertised or assigned to users. Given that Office is licensed per device, I don’t see the issue with this.
- Challenging to maintain/update. WSUS is a pretty good solution for most customers so again I don’t see the issue here.
The changes Microsoft have made to the Office 2007 Setup routine appear to be aimed at making Office 2007 easier to deploy and maintain for larger customers who generally have tools like SMS for application deployment. So what options do organisations that rely on Group Policy for application deployment have? Here’s the lowdown:
CONFIG.XMLand deploy Office by adding the MSI file to a Group Policy object.
- Create an MSP or customise
CONFIG.XMLand deploy Office via a Group Policy Startup script.
If you want to use the first option you will need to make a copy of Office for each separate installation type e.g. installing Access on some computers but not others. This could require higher maintenance and as using CONFIG.XML is a limited option compared to MSP files, who really wants to use the limited option when there is a nice Office Customisation Tool GUI available?
This leaves you with deploying Office 2007 via a MSP files and a Startup script and I think this will give you the most options. To install via a script use
SETUP /ADMINFILE adminfile.MSP to install Office with the customisations you require (run
SETUP /? to see a fill list of command line options). Microsoft have a page on using Startup scripts, Use Group Policy to Assign Startup Scripts for 2007 Office Deployment, however this page is not available at the moment.
So there we have it the way you used to deploy Office no longer works and you’ll have to do some preparation when it comes to Office 2007. Make sure you check out the page on TechNet for more details.