Office 2007 and Office 2010

(imported topic written by RosaMartin)

Is there a fixlet available to deploy Office 2007 and / or Office 2010?

(imported comment written by rdamours91)

I can check into work later this weekend and post my code for the installs.

Part of the install was to build a .msp file that has all the info required for the Office install that you would have to enter even if done manually, the keys that you would be prompted for, etc. The job then reads in that file on the fly and does a silent upgrade/install.

You can extract out the large service packs into an upgrade folder I believe and it will even service pack the install at the same time.

(imported comment written by rdamours91)

Here’s the action info…

You’ll need to copy the entire contents of the office 2010 dvd onto a folder called Office2010 or whatever you’d like on your c drive. When I was done creating the .msp file I put it in the updates folder within the Office2010 folder so that the install knows where to find it.

Use the Windows software distribution wizard to pull up the whole office2010 folder on your c: as all the files will be there that are needed to do the install.

You’ll still need to know how to create the .msp file as it is a switch that is run following the setup.exe when you build the file. It’s basically an answer file that is recorded of the settings you input into your install. You can probably just google how to build a .msp file in office 2010. It’s much easier than it used to be :slight_smile:

wait __Download\setup.exe /adminfile “{(pathname of client folder of current site) & “__Download\Updates\Office2010.msp”}”

(imported comment written by JackCoates91)


we’ve just released a new Software Distribution tool which should improve on this process. Please see the forum post here:



(imported comment written by SystemAdmin)

I am having some weird issue with my deployment that I have not been able to resolve. Basically the software installs successfully but when I deploy it I get the Exit Code 1641. The error is basically “The requested operation completed successfully. The system will be restarted so the changes can take effect.”. I have a restart as part of the post install task.

Here are some error log entries that show what is going on. In the console itself the job is listed as “Failed” but below it appears it should be “Fixed”.

At 15:57:50 -0600 - actionsite (http://BESserver:52311/cgi-bin/bfgather.exe/actionsite)

Command succeeded (Exit Code=1641) wait __Download\setup.exe /adminfile “C:\Program Files\BigFix Enterprise\BES Client__BESData\actionsite__Download\Updates\Office2010.msp” (fixlet 35782)

At 16:08:46 -0600 - actionsite (http://BESserver:52311/cgi-bin/bfgather.exe/actionsite)

Fixed - Software Distribution - Deploy: Microsoft Office 2010 (32 bit) (fixlet:8052)

At 16:09:16 -0600 -

Report posted successfully.

At 16:10:17 -0600 - actionsite (http://BESserver:52311/cgi-bin/bfgather.exe/actionsite)

Fixed - Software Distribution - Deploy: Microsoft Office 2010 (2) (fixlet:34970)

anyone else see something similar? We are still running the 7.2 BES infrastructure with plans to upgrade in the next 1-2 months.