Deploying Office 2010 via Customization file...

O.k I have copied the Office 2010 installation media to a server share. I have run the setup /admin command and created a customization file for Office 2010 ProPlus 32Bit and set the display level to none with supress modal enabled as I want this to be a silent install. I then saved the file as Office2010ProPlus.msp into the server share location ...\CustomConfig folder.

I then updated msiexec to ver 4.5 on the test clinet PC...but the install is not happening when I try and run it on the test client PC...

I ran the following from a command prompt on the Client XP machine...setup /adminfile \\servername\...\CustomConfig\Office2010ProPlus.msp

The problem seems to be that it does not recognise the .msp nor the settings contained within it but even if I browse directly via windows to the server share and double click the .msp file it doesn't run I get an error message...?

The update upgrade patch cannot be installed by the wondows installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch

Firstly I am not upgrading...I have set the .msp file to uninstall ALL previous versions of office and install Office 2010 ProPlus...the test client PC already has Office 2007 ProPlus on it...???

Any help on this would be greatly appreciated as I need this .msp file working before I can even think about packaging this and rolling it out via SMS...
Who is Participating?

Improve company productivity with a Business Account.Sign Up

AmnonmConnect With a Mentor Commented:
nhhgictAuthor Commented:
Hi Amnonm...

Yes I saw the .xml route and that does indeed work but I have some other more grainular installation requirments. Basically I want to setup a range of .msp files for different departments who have different requirements.

For example our finance department require different macro and trust center settings to the rest of the organisation which I can pre-configure via the OCT as it is so granular and simply save these settings as an .msp file...then package that as FINANCE OFFICE INSTALL and give the helpdesk visablility and rights to deploy this as is without worrying about the requirement for tweaking after the install...

The following is directly lifted from a technet article...As an alternative to placing the customization .msp file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully-qualified path of the location of the .msp file. For example, type: setup.exe /adminfile \\server\share\mychanges\custom.msp.

So I am not sure why this is not working? The security share permissions on the server share are wide open...???

nhhgictAuthor Commented:
O.k so running the setup.exe /adminfile \\sevrer\share\...\custom.msp from a test client seems to kick in but it is strangely not recognising all the settings in the .msp file.

The install window comes up and asks what version I want to install...i set the radial button to ProPlus and click continue and off it goes...the starnge thing is ithat it picks up the granular changes to macros, and other security features I setup in the .msp file...???

What I am going to try now is configure the ProPlusWW.xml file for silent install and then run the arugment again although I still battle to see how this will trigger an automatic ProPlus install...???
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

nhhgictAuthor Commented:
Rollout via .xml file does work but does not support my requirements of more granular settings to be installed at rollout.
Getting the same error as nhhgict making changes to the config.xml file makes no differnce. Any ideas? The MSP seems to be looking for a previous installation of Office 2010. I just want to remove Office 2007 as part of the Install of Office 2010.
nhhgictAuthor Commented:

I assume you are talking about my very first post when you say you are getting the same error...what I eventually found in an article on TechNet is this...

Setup.exe looks for the "package" version to install in its own folder location when run from a command prompt...

Copy the config.xml file from the package you want to install (i.e. from the ProPlus.WW folder to install Professional Plus) into the root installation folder so it resides in the same location as setup.exe

NOTE: This will mean setup.exe when run from a command prompt will ALWAYS install the "package" version found inside the config.xml file sitting in the root installation folder along side it...

Think of it this way...when you install Office 2010  from the nice looking GUI splash screen the first thing you are asked is which version to install...the setup program is then re-directed back stage to the corresponding folder location to continue from...

I have not tried this but I guess you could copy setup.exe to ALL the "package" folders...that way you can run setup.exe from a command line referencing the folder structure that corresponds to the package you want to be installed and still use the /adminfile argument to call up your OCT customisations.

This means you still only need one network installation folder instead of many if you have many package requirements...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.