Discussion Forums/PDQ Deploy/Deploy - Knowledge Base

Deploying Microsoft Office 2010 Professional

Shawn Anderson
posted this on August 02, 2010 13:50

Step 1: Extract administrative files from Office installations disk

 

Locate the setup.exe for Office and run the following:

setup.exe /admin

This will extract the Microsoft Office Professional 2010 files that you will need to modify to perform silent installations as well as providing license key information. The Office Customization Tool will start automatically.

Microsoft_Office_Customization_Tool.png

Make your modifications at this time. One area of importance is the Licensing and User Interface section, which allows you to auto accept the Microsoft Office EULA as well as set the interface level for the installation. This is also the page where you will enter your product key (if you don't use volume licensing). It's not as clear cut as I'd like it to be, but it's intuitive enough.

Microsoft_Office_Customization_Tool-2.png

For silent deployments select None in the Display Level (see image).

Make any additional changes or configurations and select File > Save. This will create your .MSP file. I suggest saving this file in the same directory as your setup.exe.

To deploy Office 2010, open PDQ Deploy and browse to setup.exe in the Installer File to Deploy field. Be sure to select "Include Entire Directory". In the parameters field enter the following:

/adminfile admin_file

Office_Customization_Tool_-3.png

 

Comments

User photo
Kurt Schmitt

I've followed this instructions step by step, but now have the problem, that in the Deployment Console, the job never ends. The installation itself is running fine, but the status remains on "installing".

Whats wrong here - how can I debug?

 

Thanks

April 20, 2011 06:53
User photo
Shawn Anderson
Basic Subscription

Hi Kurt, There could be a couple of reasons for this issue, including using a retail copy of Office vs. volume version, or installing slightly different products. I'd like to get a copy of your .msp file that you created. I'll open a separate support ticket so that we can resolve this issue. Thanks for commenting.

~Shawn

April 20, 2011 09:13
User photo
Filip Ruymen

I'm having the exact same problem as Kurt at the moment.

I haven't found a solution yet.

May 13, 2011 06:58
User photo
Shawn Anderson
Basic Subscription

Filip, Kurt discovered that by turning off his completion notice it worked. Will you open your admin file and see what you have the completion notice set to. It's in the same section as running the installation silent, etc. Please let us know if it works. If you still have issues we will open a support ticket and see what we can find.

Thanks,

Shawn Anderson

May 13, 2011 14:29
User photo
Jeff Bolden

Also, if you want to have the installation auto-activate so the users don't get the activation dialog on first use, do the following:

In OCT, under Modify Setup Properties, click the Add button. In the name Field, put in the following:

AUTO_ACTIVATE

In the Value field, put in the following:

1

Hit OK and you are done. This will auto-activate in the background with no user interaction required. The only downside to this is every time you run an install it will use up another MAK, so if you push out a new install over an old one, it will not reuse the key.

Hope this helps. PDQ Deploy rocks! Just bought the pro version and am using it heavily the past week. I own a Managed IT Service shop and this tool is saving me tons of time with my clients. =)

June 01, 2011 11:38
User photo
Matthew Aghedo

Is anyone having a problem with pushing it to windows 7? The install seems to hang. I can see that the files copy to the local win 7 machine but thats it. I also see the service running but it isnt doing anything

June 07, 2011 10:30
User photo
Shawn Anderson
Basic Subscription

Matthew, I've pushed to Windows 7, Vista, and XP. If you'd like I'd be happy to look at your MSP file (assuming that you created a custom MSP). Please send it to support@adminarsenal.com and I'll see if it hangs in our lab.

June 09, 2011 09:47
User photo
Dan Manzella

After we create the .msp, where should this be placed? Same folder as the setup.exe?

I am not sure if the .msp is getting read since I have it set to not restart after finishing installing, but once the setup is done, the user says the computer restarts.

August 30, 2011 09:19
User photo
Shawn Anderson
Basic Subscription

Dan, I usually keep my msp next to setup.exe (same level). I've had spotty success when keeping it in \admin.

Will you please export your office installer (in PDQ Deploy)  and send it to support@adminarsenal.com. We'll take a look and see if something stands out.

August 30, 2011 10:29
User photo
Dan Manzella

Shawn-

Thanks for the reply. I have it in the same level as the setup.exe. It isnt place in the \admin.

I have tired to send the .msp but i keep getting a bounce back that it doesnt like the file type. I have tried to zip it aswell.

August 30, 2011 10:33
User photo
Shawn Anderson
Basic Subscription

Please try and attach it here. I can remove it from the forum after I download it.

August 30, 2011 10:40
User photo
Shawn Anderson
Basic Subscription

Also, did you say that you don't have an admin directory? If so, then we need to find out where your office cd came from. If there is no \admin directory then the admin tool likely will not work.

August 30, 2011 10:41
User photo
Shane Corellian
Admin Arsenal

Thanks, Dan. We have your office_x32.msp file. We will check it out and get back to you. I have removed the file attachment from this forum.

August 30, 2011 11:46
User photo
Paula Riddle

I know this is going to sound like a completely unintelligent question, but why does the MSP file need to be moved from the updates folder?  Will the deployment not work?  I'm just learning to play around with the OCT and did a successful customization- including automatic activation and removal of a couple of unwanted programs.  I've only tested it on a couple of machines so far (navigating to the share on the server and starting the install), but they've come out exactly as I had wanted. It was my understanding from reading the Microsoft documentation that the installer would process whatever was in the updates folder.  Does PDQ interfere with, or prevent that?    Thanks so much for any and all help.

October 04, 2011 14:55
User photo
Shawn Anderson
Basic Subscription

Microsoft's documentation indicates that the MSP can reside in the \admin, \updates, or root folder. I've seen instances in \admin where the msp didn't take, but my most consistent behavior is in root. The \updates is also fine, especially when you will be applying service packs or patches.

PDQ Deploy runs the application as though you were doing so manually from a command line, it simply passes (albeit in the background) the setup.exe /adminfile <file> parameter as specified. There shouldn't be any changes to the intended MS installation.

October 04, 2011 15:33
User photo
JayR Arroyo

Hello Support Team,

Mind if I ask if there's a way to auto activate MS Office 2010 just thru OCT? Tried Jeff's produre (AUTO_ACTIVATE, set value to 1) but its still prompting me to activate the account right after the installation.

Much appreciated.

November 14, 2011 18:54
User photo
Shawn Anderson
Basic Subscription

Jay, Office 2010 has joined the ranks of Win7 and Server 2008 in requiring volume license customers to activate using the Microsoft KMS (Key Management Services). This is an application that you install on a server or workstation on your network and your Office applications hit it to activate. The KMS keeps a tally of your license entitlement from Microsoft.

Here is a link with more information.

http://www.microsoft.com/licensing/existing-customers/product-activ...

 

The days of the volume license that has already been activated ended with Office 2007 and Vista. :(

November 15, 2011 10:02
User photo
Jen

Im trying out PDQ for the first time... I have the installation working, the only thing I cant figure out (I am very green at scripting) is how to prevent a reboot at the end. I tested it out on a 7 box where the user had a prior version of office and left it open. I wanted to see what it was capable of during the deployment to determine user interference. Do you know how I would suppress the reboot at the end of the install or at least something to say, "hey, can you restart me in order to use office"?

November 22, 2011 14:26
User photo
Jen

nevermind. Following these instructions worked! No reboot now.

 

http://support.adminarsenal.com/entries/20623341-install-never-comp...

November 23, 2011 10:31
User photo
Jen

hmm. Nevermind again. Worked on test 1 and not test 2. Any ideas on supressing the reboot?

November 23, 2011 10:49
User photo
Shane Corellian
Admin Arsenal

Hi Jen,

You need to open your Office Customization tool. Go to "Modify Setup properties" and click Add. 
Enter the name SETUP_REBOOT and the value Never. 

custom-settings.png

This should do the trick.

November 23, 2011 12:35
User photo
Adrian Salas

Newbie to PDQ, just wanted to say thanks to all who posted here.  This thread plus PDQ helped me deploy Office 2010.  While everything worked great,  I got the following error when I opened one of the applications, in this case MS Word.  After clicking OK, the software works just fine, but thought I would post it here.   

January 28, 2012 16:46
User photo
Shawn Anderson
Basic Subscription
Adrian, this can happen due to different issues. Sometimes it's due to a previous office installation. Did you move from 2003 to 2010? Will you post a screen shot of the error? We'd like to look at his a little deeper.
January 28, 2012 20:29
User photo
Adrian Salas

Hi Shawn, there is a screen shot of the error attached to my original post.  We are moving from office 2007 to 2010.  The error came up on a clean install (no previous version of Office) and on an install where Office 2007 was currently installed.  But like I mentioned before, both installs worked just fine, the error comes up on first launching one of the Office applications, but not on subsequent launches.

January 28, 2012 23:04
User photo
Shawn Anderson
Basic Subscription

Adrian, sorry about not seeing the earlier image. I was reading the post from my cell phone and I guess the images don't show up there. I did a little searching and it seems that this is a somewhat common error that happens when a word template becomes corrupt. Here are some links that might shed some more light on this.

http://michal.jakou.be/2011/02/08/ms-word-2010-startup-issue/

http://social.technet.microsoft.com/Forums/ar/officesetupdeploy/thr...

 

The first link is from Michal Jakoube, who incidentally has been using our products for many years. Other online topics discuss corrupted Add-ins and to disable them by starting Word in safe mode (run > winword /safe and disabling the Add-ins. 

It seems like this is a one-time issue, right? Some of posts I read were experiencing this every time they opened Word.

January 30, 2012 12:03
User photo
Larry Coe

Read all the posts, followed advice above, created my msp file and attempted to deploy. Failed due to timeout and have it set to 3 hours and deployed to my test PC that has Office 2007 installed.

To test my msp file I then ran it from the run prompt and it installed 100 % save for this error (see pic) which I think could be caused by google calendar sync that was active but did not stop the install.

 

Why work manually and time out from PDQ ?

I also see you have include files ticked but no files specified, why ?

attached my xml from PDQ

 

October 12, 2012 00:56
User photo
Jeffery Collier

Hello: I am new to PDQ Deploy and so far it has been a great time saver and the most used tool in my tool box. I am having an issue pushing Office 2010Pro. I followed the guide to the letter but when I push the installer hangs. I have attached my .MSP file for your over view. Any help would be greatly appreciated.

October 16, 2012 06:50
User photo
Larry Coe

Jeffery

got mine to work at last, by not doing the 2010 that includes the update /SP1

Ensure include directory is ticked , reason why mine failed to start with.

see settings above.

does not auto license with MAK key so has to be done after install.

also try to run the setup manually on the PC with the msp file in use and note where it fails

October 16, 2012 07:38
User photo
Jeffery Collier

Can you take a look at this and tell me what I am doing wrong.

October 16, 2012 12:16
User photo
Shawn Anderson
Basic Subscription

Jeff, use 

/adminfile custom-setup.msp

October 16, 2012 13:21
User photo
TonsOFun

Larry, 

You can auto license with MAK as I have mine set to do this after the deployment. 

I used a batch file for mine, or you can add an additional step (assuming you're running pro edition), just add a line at the very end (or last step):

  • cscript "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act

Obviously, force reboot should not be on after the completion of the installation. 

and the above is the installation path of Office. 

If you're installing 32bit then you would only need to change (x86) on a 64-Bit OS. 

Hope this helps. 

October 17, 2012 11:21
User photo
TonsOFun

Jeff, 

Try the following if MSP is not working for you still. 

I had to follow this documentation in order to deploy. 

I too had the hanging issue using MSP. 

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

This utilizes the config.xml file. A little more tedious, but the benefits of course outweighs. 

If you're interested, i can provide a screenshot of my config.xml to use as a sample. 

October 17, 2012 11:39
User photo
Andrew Berryman

I've got the deployment and activating working just fine, for the most part. If a client uses a proxy for IE, the activation won't work. Does anyone have the steps to add to my deployment to turn off the proxy, then activate, then turn the proxy back on?

January 24, 2013 08:59
User photo
Larry Coe

Andrew

attached file will remove proxy, and restart PC

reverse the del reg to a addregg to add

January 24, 2013 09:11
User photo
Andrew Berryman

Larry, thanks for the file. I need something to do it without rebooting the PC unfortunately. We have boot passwords on our PC's and when I do a mass deployment, I'm trying to avoid going to each PC as it reboots to put in the boot password.

January 24, 2013 09:19
User photo
Andrew Berryman

Actually, do we know what website the activation tries to contact? I can add that to the list of proxy exceptions within IE through Group Policy.

January 24, 2013 09:22
User photo
Andrew Berryman

I wish I could edit my posts. Anyway, Google has helped me out with this. URL's to whitelist for proxy activation issues. http://support.microsoft.com/kb/921471

January 24, 2013 09:27
User photo
yasir rizvi

Hi Support Team,

I tried following using OCT and when user launched office it saying user needs to be admin on the pc.

 

In OCT, under Modify Setup Properties, click the Add button. In the name Field, put in the following:

AUTO_ACTIVATE

In the Value field, put in the following:

1

Please help out!

February 21, 2013 10:39
User photo
TonsOFun

Hi Yasir, 

Just to clarify, you're saying that you ran OCT, however, when the user logs in, they are still getting a prompt to activate the product? Is this correct? Hence the message about being admin on the pc. Only administrators can activate the product. 

So, the assumption then, is that OCT is not activating the product. 

A troubleshooting step you can take, is to make sure that the product key that was entered, is entered correctly. Do this by logging into a test machine with admin privileges and simply activating the product. If it does not activate, then the product key is either wrong, or you have used up your activations. 

If however, the activation goes through as an administrator, then there is something wrong with the package. Are you able to run the OCT on the local workstation not using deploy? Make sure that it works. 

If you are still having issues. i have a script that i use just to activate the product assuming the product key is entered correctly. Just add another command line step to the package to activate the product. 

------Start of command---------

cscript "c:\Program Files\Microsoft Office\Office14\ospp.vbs" /act

-----End of command---------

This assumes the installation is not 32bit on a 64bit OS, otherwise, change the "Program Files" to "Program Files (x86)"

Hope this helps

February 21, 2013 10:56
User photo
yasir rizvi

when the user logs in, they are still getting a prompt to activate the product? Is this correct? Hence the message about being admin on the pc. Only administrators can activate the product. (Yes)

This is error i get when i manually run the vb file.....

C:\>cscript "c:\Program Files\Microsoft Office\Office14\ospp.vbs" /act Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved.

---Processing-------------------------- --------------------------------------- Installed product key detected - attempting to activate the following product: SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7 LICENSE NAME: Office 14, OfficeProPlus-MAK edition LICENSE DESCRIPTION: Office 14, RETAIL channel Last 5 characters of installed product key: 64JFP ERROR CODE: 0xC004F025 ERROR DESCRIPTION: The Software Licensing Service reported that the action requi res administrator privilege. --------------------------------------- --------------------------------------- ---Exiting-----------------------------

 

February 21, 2013 11:19
User photo
TonsOFun

Yasir, 

Is the account you are using to push the command have administrative rights? 

Make sure the service account you are using has the correct permissions on the target machine.  

February 21, 2013 11:23
User photo
yasir rizvi

i was hoping i could have user run cscript file without admin permissions.

So i tried using same command using account with domain admin permissions....i get below....

U:\>cscript "c:\Program Files\Microsoft Office\Office14\ospp.vbs" /act Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved.

---Processing-------------------------- ---------------------------------------

Installed product key detected - attempting to activate the following product: SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7 LICENSE NAME: Office 14, OfficeProPlus-MAK edition LICENSE DESCRIPTION: Office 14, RETAIL channel Last 5 characters of installed product key: 64JFP ERROR CODE: 0x80072EFD --------------------------------------- --------------------------------------- ---Exiting-----------------------------

February 21, 2013 11:33
User photo
TonsOFun

Hi Yasir, 

You can not activate the product unless the user is an administrator of the target machine. 

However, you might have a different error altogether. 

What type of license do you own? It looks like it's a retail? are you sure you haven't used all the licenses? does it work if you activate it manually as an administrator? (not using the command script)

February 21, 2013 11:47
User photo
yasir rizvi

well 95% of users are not admin on their local machine.

Nope, this is not retail version. It's MAK (volume license key) I am not sure if we used up all licenses.

I can activate it over the internet using same key with OCT, but in this case i had to make sure a local admin temp. so i can test.

February 21, 2013 12:20
User photo
TonsOFun

Yasir, 

This is what makes PDQ deploy powerful sir. 

Allows you to use a service account that has admin privileges without having to visit or have user interaction. 

as for the original problem. Not sure what's up at this point. Maybe try running windows update to make sure everything's up to par, then try again? 

sorry i couldn't be of any more help. 

February 21, 2013 12:32
User photo
yasir rizvi

Thank you so much for your help!

February 21, 2013 12:37
User photo
CHECK24 Admin

Does someone know a way how to deploy Office 2007 or 2010 in a retail/OEM version?

I was told that there should be a way how to handle it although you need for each version a single licence key. But until now I do not found any solution for it except with the MAK.

February 22, 2013 09:13
User photo
Shawn Anderson
Basic Subscription

The challenge with the retail version is that you are not able to utilize the OCT (Office Customization Tool). To see if the retail version will allow silent installs, open a command window and drag the office setup.exe into the window. Then type a space followed by /?

setup.exe /?

Hit enter. Does a window appear giving you silent install options? If you did this on the non-retail version it would give you a window that listed the /admin parameter to open the OCT. 

February 22, 2013 09:25
User photo
CHECK24 Admin

It looks like that the program is giving some responce (see attached - sorry, but it is in german ;-) )

Does this help?

 

February 25, 2013 01:15
User photo
CHECK24 Admin

For MS Office 2007 we managed it that it works. We can deploy the MS Office Package and while MS Office is started for the first time it ask for the regular key (OEM-Key) which we had bought.

With Office 2010 it does not work in the same way. We never have tried it for testing purposal just putting in a MAK Key, deploying the package and then change the key to the regular bought OEM Key.

The question is:
- Do I need the MAK Key just for deploying  OR/AND
- will the MAK Key online validated while I am deploying the package and
- will it recognized by MS how offen the key is in use

If it is not recognized by MS and not against any legal statements from MS may this could be a solution for people who bought legal OEM Office Packages and wants to deploy this packages in a easier way.

February 26, 2013 02:07
User photo
Chau Nguyen

Hey guys, I hope someone can help me.  I am testing PDQ deployment with Project 2010 to get ready for our Office 2013 deployment.  I created a custom.msp file and copied it in the MS Project 2010 directory, in three places - the main folder, the x86 folder, and the x64 folder.  We run a KMS server.  When I run PDQ Deploy, the files transfer to the client perfectly and return as a Successful installation, however nothing happens on the client end beyond the transfer.  I have also tried using a config.xml file, but no luck either.  

However, when I run the Project 2010 setup locally on my machine using the setup.exe /adminfile custom.msp extension, the silent installation works perfectly.  What am I missing?  I have included both my MSP and config.xml files, and a screencap of my PDQ Deploy configuration for that package.  Thanks in advance for your help!

March 05, 2013 07:40
User photo
Shawn Anderson
Basic Subscription

Is your custom.msp sitting at the same directory level as your setup.exe, or is it sitting somewhere else, like in the Admin directory? 

March 05, 2013 08:32
User photo
Chau Nguyen

It is on the same directory level as my setup.exe.  basically, the file structure looks like this on our server:

\\server\share\Microsoft\Project\2010\CD\setup.exe

Inside that CD folder, there are also two folders, x64 and x86 which each contain setup.exe as well.  I have a copy of the custom.msp in all three folders, the base CD as well as the x86 and x64.  

March 05, 2013 08:38
User photo
Shawn Anderson
Basic Subscription

Are you expecting the setup.exe for the individual files to be called for x86 or x64? In PDQ only the setup.exe that you specify will be called. In PDQ, will you please select your Office package, and then go to File > Export and attach the XML file that is created? I can then load this in our lab and take a look.

March 05, 2013 08:45
User photo
Chau Nguyen

Shawn, 

Our initial Office 2010 setup was x86 so that would be the setup file which would be called.  Given your advice, I went ahead and pointed PDQ only to transfer the x86 folder with the custom.msp file in there, and sure enough everything is working properly.  From my understanding, deploying 2013 would not be any different than this, correct?  If that is the case, looks like I am good to go - thank you for your help!

March 05, 2013 09:13
User photo
Shawn Anderson
Basic Subscription

You can call different setup.exe's using our conditionals in PDQ Deploy 2.2. That may be an option if you do have mixed set. You would simply create a new step and point to the 64bit version. Set the conditional to ONLY run on 64bit systems. 

Conditionals are a pro mode feature. Not sure if you are using free or pro, but it is an option if you need it.

Shawn

March 05, 2013 09:18
User photo
John Brines

I have done all this and my install copies the files to the computer, then starts the install, setup.exe is on the task manager but it doesn't seem to be doing anything.

March 14, 2013 06:51
User photo
John Brines

Got it working, the admin_file had a space, as soon as I removed it it worked :)

 

John.

March 14, 2013 08:29
User photo
Jason Johnson

For me, I found that in your MSP file you have to have the accept the terms box checked, turn off the completion notice (this is what hangs it), check "suppress modal", and change the display level to none. Once I did all of those, it deployed just fine. Any other settings it seemed to hang at installing.

June 03, 2013 09:12
User photo
Steve

Hello, I'm having a problem getting Office 2010 standard to deploy. I've followed the instructions in the original post and made my .msp file and placed it in the same directory as setup.exe on the server share. 

I deploy the package to a test machine and after roughly 2 minutes, I get a "Successful" notification. But upon checking the target machine, Office has not been installed. Checking the c:\windows directory, I see that a folder named PDQDeployRunner has been created, the directory structure is: C:\Windows\PDQDeployRunner\1\exec\x86. Inside the x86 folder I can see the setup.exe and a folder named standard.WW that contains a file named oesetup.dll. So some files are getting copied to the target (but not the whole 1+gb). Any idea what's going on here and how I can fix it? Target machine is win7 pro with SP1. Thanks in advance.

September 06, 2013 10:13
User photo
Steve

Disregard my last. I switched the package to "Run as local system" and it worked. 

September 06, 2013 17:18
User photo
Ken Ethridge

NOTE:  I have been corresponding with Brandon at Admin Arsenal

We have approx. 210 computers running Win 7 and XP that have to be upgraded to Office Pro 2010.

I have attempted using PDQ Deploy.

STATUS:  I get multiple errors.  (See "ErrorCode-PrintScreen")

"Step1-ScreenPrint" Shows my Step 1 settings

The "custom-office.MSP" is the file I'm using.

 

Can someone look at my MSP please?

 

November 06, 2013 10:21
User photo
Brandon Rewis
Admin Arsenal

Ken,

Can you go to one of the machines and run the setup.exe from the UNC path with the /adminfile custom-office.msp and tell me if it installs without any errors?

-Brandon

 

November 06, 2013 11:34
User photo
TonsOFun

Hi Ken, 

Sorry to hear you're having issues with this. 

I too had issues with the MSP for 2010, but had no problems with 2013. 

I had to use the XML version of the deployment in order to pdq deploy correctly. 

If you're in a hurry to get office deployed, you can try to use my method. 

I used a batch file with the following in PDQ Deploy. 

---------------------Start of Batch file codes------------

"\\SERVERNAME\sccm\software_package\office 2010 Pro Plus 64 bit\setup" /config "\\SERVERNAME\sccm\software_package\office 2010 pro plus 64 bit\proplus.ww\config.xml"
cscript "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act

------------------------------ End of code--------------------

The above commands is 2 lines only. The cscript has its own line (activates the product).

The first line uses a UNC path to call the setup program, which calls upon a config file. This config file will need to be modified and is there in the above directory by default. You just need to edit it in notepad. Open the config.xml file in your install folder (proplus.ww) and enter the following lines. 

The lines in BOLD is where you'll need to modify or remove if desired. 

---------------------- Start of Config.XML------------------

<Configuration Product="ProPlus">

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

<PIDKEY Value="<ENTER PRODUCT KEY HERE WITHOUT DASHES>" />

<OptionState Id="ACCESSFiles" State="local" Children="force" />

<OptionState Id="EXCELFiles" State="local" Children="force" />

<OptionState Id="GrooveFiles" State="local" Children="force" />

<OptionState Id="OUTLOOKFiles" State="local" Children="force" />

<OptionState Id="PPTFiles" State="local" Children="force" />

<OptionState Id="PROJECTFiles" State="local" Children="force" />

<OptionState Id="PubPrimary" State="local" Children="force" />

<OptionState Id="QueryFiles" State="local" Children="force" />

<OptionState Id="VISIOFiles" State="local" Children="force" />

<OptionState Id="WORDFiles" State="local" Children="force" />

<OptionState Id="XDOCSFiles" State="local" Children="force" />

<Setting Id="AUTO_ACTIVATE" Value="1" />

<Command Path="\\SERVERNAME\sccm\Software_Package\Office 2010 Pro Plus 64 bit\activateoffice2010.bat" QuietArg="/quiet" ChainPosition="after" Execute="install" />

<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> -->

<!-- <USERNAME Value="Customer" /> -->

<!-- <COMPANYNAME Value="MyCompany" /> -->

<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

<!-- <LIS CACHEACTION="CacheOnly" /> -->

<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->

<!-- <DistributionPoint Location="\\server\share\Office" /> -->

<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

<!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> -->

<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>

--------- end of Config.XML--------------

This works for upgrades, as well as fresh installs. And the above is for MAK licensing. 

 

If you need further help, let me know. 

November 06, 2013 11:36
User photo
Ken Ethridge

We are using 32 bit verison

 

 

November 06, 2013 12:44
User photo
Ken Ethridge

UPDATE:  I successfully manually loaded the above attached .MSP file.  So, I assume this file is correct.

However, I just retried pushing the file to to XP Boxes and I received ERROR CODE 2203 for both.

Any ideas?

November 06, 2013 12:54
User photo
Ken Ethridge

 

This is the event log from one of the boxes that failed to load...can someone shed light on this?

 

November 06, 2013 13:26
User photo
Ken Ethridge

This is the logs from another box the update failed on.

THANKS FOR ANY/ALL Help.

 

Ken Ethridge, USAF-Retired,

Meridian, MS

November 06, 2013 14:08