Deploying Microsoft Office 2010 Professional

Follow

Comments

69 comments

  • 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. 

    0
    Comment actions Permalink
  • Shawn Anderson

    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? 

    0
    Comment actions Permalink
  • Shane Corellian

    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.

    0
    Comment actions Permalink
  • Shawn Anderson

    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/thread/1bf5772b-b689-44ee-8eec-a533035a04d9

     

    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.

    0
    Comment actions Permalink
  • Shawn Anderson

    Jeff, use 

    /adminfile custom-setup.msp

    0
    Comment actions Permalink
  • 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.  

    0
    Comment actions Permalink
  • Shawn Anderson

    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

    0
    Comment actions Permalink
  • Shawn Anderson

    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.

    0
    Comment actions Permalink
  • Shawn Anderson

    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.

    0
    Comment actions Permalink
  • 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

     

    0
    Comment actions Permalink
  • yasir rizvi

    Thank you so much for your help!

    0
    Comment actions Permalink
  • 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.  

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • 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. 

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • Shawn Anderson

    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.

    0
    Comment actions Permalink
  • Shawn Anderson

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

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • 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. 

    0
    Comment actions Permalink
  • CHECK24 Admin

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

    Does this help?

     

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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!

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • Ken Ethridge

    We are using 32 bit verison

     

     

    0
    Comment actions Permalink
  • 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

    0
    Comment actions Permalink
  • 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-----------------------------

     

    0
    Comment actions Permalink
  • Shawn Anderson

    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

    0
    Comment actions Permalink
  • John Brines

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

     

    John.

    0
    Comment actions Permalink
  • Shawn Anderson

    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.

    0
    Comment actions Permalink

Article is closed for comments.