Deploying Microsoft Office 2010 Professional

Follow

Comments

69 comments

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

    0
    Comment actions Permalink
  • Larry Coe

    Andrew

    attached file will remove proxy, and restart PC

    reverse the del reg to a addregg to add

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

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

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

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

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

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

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

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

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

    Thank you so much for your help!

    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

    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. 

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

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

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

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

    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

Article is closed for comments.