I have to package just outlook 2010, and deploy to desktops that already has office on it (that does not have the outlook)

I have the source for the entire office 2010. How do I proceed with it.

Do I need create a .MSP or config files.

Can anyone guide as to how I need to proceed it?

Thanks in advance.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


The way I did this a few months ago was using the office customisation tool for Office 2010. Do a quick google search and I'm sure youll find the KB article about it. [:)]
Answered 01/26/2012 by: Dodgyguy
Senior Yellow Belt

Please log in to comment
You have to use customization tool....

here you go how to customize...


in "set features installation states" select only outlook...

in " remove previous installations" select "remove the following earlier versions of Microsoft Office Programs" -> Mark as Remove None for other office products...

save Output...

Install command : Setup.exe /adminfile <CurrentDirectory>\Updates\outlook.msp

Kindly Rate Post if found Useful
Answered 01/26/2012 by: mahendraKumar
Senior Yellow Belt

Please log in to comment
Thanks a lot you guys :)
Answered 01/30/2012 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
I created the MSP using the customization tool.

Install command : Setup.exe /adminfile <CurrentDirectory>\Updates\outlook.msp

But there is office already there on the systems , so if I do that, it rips of the other office (excel, publisher, access) and then installs the outlook.

And gives an error 1304 errro writing to file : Policy 12.0.office.dll.

so does not install either if there is office previously on the desk

Any suggestions
Answered 01/30/2012 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
I tried msiexec.exe \p "c:\ outlook.msp"
I'm getting the same error.

setup.exe /adminfile \\server\share\outlook.msp

I get the error
The /adminfile command line option can be used only during initial installation of the product

Answered 01/30/2012 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
I think this is the result of how MS license their products.
If I'm not misstaken, You are only "allowed" to install one configuration of Office.
I write "allowed" cause I think it's possible to install two configurations, but then you'd have to do one config w/o Outlook and one config w Outlook.

However, if your up for a license revision, MS might have something to say about it.

I'm not 100% sure about the above statement, so feel free to shoot me down if I'm incorrect.

Answered 01/31/2012 by: andemats
Second Degree Black Belt

Please log in to comment
I'm not 100% sure this will work, but have you tried creating a new config.xml file to add outlook with contents like the following:

<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<OptionState Id="OUTLOOKFiles" State="local" Children="force" />
<Setting Id="SETUP_REBOOT" Value="Never" />

and rerunning the original setup.exe with the following commandline:

<path to>Setup.exe /repair PrjPro /config <path to>outlookconfig.xml

so no /admin option, which indeed only works for initial installs, just an install with a new config file
Not sure if you'd have to add all the settings from the original config.xml to this new one, play around with it abit.

Answered 01/31/2012 by: pjgeutjens
Red Belt

Please log in to comment
Thanks you guys,

It worked now. I did the OCT method.
I have another question, since i'm adding this as a MSP to the office that is already present , and since the office already has the KMS key connected.
Will I have to again give the KMS for the Otlook too?
Answered 02/01/2012 by: shamu99
Fifth Degree Brown Belt

Please log in to comment