/build/static/layout/Breadcrumb_cap_w.png

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 34.6k  |  Created: 08/18/2010

Average Rating: 0
Office has 4 inventory records, 205 Questions, 27 Blogs and 36 links. Please help add to this by sharing more!

Deployment Tips (26)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 5 ratings
Most Commonly Reported Deployment Method
Windows Installer Command Line (No MST)

Deployment Tip Summary

The product can be installed by using the /config switch: "setup.exe /adminfile .msp /config Standard.WW\config.xml" And to uninstall this product by using the /config switch: "setup.exe /uninstall STANDARD /config SilentUninstallconfig.xml"
70
Command Line
Command for MSO-2010 STD:

After you create the msp from the .exe file using the command "setup.exe /admin"; you wil have to work on 1 install config file & 1 uninstall config file.
The product can be installed by using the /config switch:
"setup.exe /adminfile .msp /config Standard.WW\config.xml"
And to uninstall this product by using the /config switch:
"setup.exe /uninstall STANDARD /config SilentUninstallconfig.xml"

Note: install config file should be posted to "Updates" folder in the root & uninstall config should be posted to root itself.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
29
Note
Pretty much the same as Office 2007:

Silent Install:

You need to create an MSP file first by running from the Office 2010 folder setup.exe /admin

You can customise the MSP from there. But to make sure you get a complete silent install:

In the "Licensing and User interface" section, tick "I accept the terms in the license agreement", Display level is set to "none", "completion notice" is un-checked, "Suppress model" is ticked.

Once the MSP file has been created you can run a silent install by: setup.exe /adminfile <the .MSP file you created>

I did find that Office 2010 wasn't activated by default so when a user opens office for the first time it would ask to activate. You can do this automatically by adding the following to a batch file:

C:\WINDOWS\system32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /act

The VB script can be found in the Office 2010 folder.


Silent Uninstall:

To silently uninstall Office 2010, you need a xml file. I have used this:

command: setup.exe /uninstall ProPlus /config SilentUninstallconfig.xml

The contents of the xml file I use is:

<Configuration Product="ProPlus">

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

</Configuration>

(Obviously you will need to place the relevant file paths for your location of the Office 2010 setup files / folders)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
23
Note
Office Customization Tool in Office 2010

http://technet.microsoft.com/en-us/library/cc179097(office.14).aspx

The OCT is part of the Setup program and is the recommended tool for most customizations. You run the OCT by typing setup.exe /admin at the command line from the root of the network installation point that contains the Office 2010 source files. For example, use the following: \\server\share\Office14\setup.exe /admin. The OCT is available only with volume licensed versions of Office 2010 and the 2007 Office system. To determine whether an Office 2010 installation is a volume licensed version, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a volume license edition. If the Admin folder does not exist, the disk is a retail edition.

NOTE: The version of Office 2010 that is available for MSDN and TechNet subscribers does not have the Admin folder, and uses a retail key. You will not be able to create a customized installation from this media. Instead, you will need the Volume License media.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
21
Note
When OCT is not included in the media, edit Config.xml file for customization or silent installation:

http://technet.microsoft.com/en-us/library/cc179195%28office.14%29.aspx

In order to disable pop-up window at first launch, add this registry key:

[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\General]
"ShownFirstRunOptin"=dword:00000001

And for activating MS office use this command-line:
cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.vbs" /act
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Hey I need some assistance. I am creating a package using your help. However I still have some issues. I configured my config.xml file with the registry key and script but it doesn't seem to work. The software installs but still ask for activation. I ran that script manually and it said it needs admin privilege. would have to update that script to run as admin ( can you show me what that would look like) Also am I correct in putting the command within the config.xml

    thanks for your help. - femij 12 years ago
18
Note
Disable activation screen users;
run setup.exe /admin
Add installations and run programs
[systemfoder]\cscript.exe
arguments
"c:\program Files\Microsoft Office\Office14\OSPP.VBS" /act
run after install
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
8
Note
There is an awesome Office 2010 uninstaller vbs script that you can download from Microsoft at http://support.microsoft.com/kb/290301/. Find the "Office 2010 suites" section and click the Fixit button to download the msi package. However, when you run the MSI you can grab the offscrub10.vbs script from %temp%\fixit\and use it via the command line to uninstall any of the Office 2010 products.

If you want to uninstall all of the Office products you simple run:

cscript offscrub10.vbs all

Additionally you can run it with no parameters and see the other command line options.

To uninstall just Office 2010 ProPlus you would run:

cscript offscrub10.vbs ProPlus

The tool is provided for people that cannot run the uninstall via Programs and Features in Control Panel. But why bother even doing that when you can uninstall silently via command line!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Have you found a way to get the Officescrub Utility to run silently by pushing it from the KBox? - CEads 10 years ago
  • I have. Type in /quiet in the parameters - itsamurai 9 years ago
8
Virtualization
Very useful article for sequencing Office 2010 BETA (with App-V 4.6):

http://www.softgridblog.com/?p=153
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
7
Command Line
Create your .msp file using the /admin switch, save it in the root of the Office files as custom.msp. Then select all files and create a .zip of the whole installation. Add the below command as a "Configure Manually" in your KBOX.

setup.exe /adminfile custom.msp
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
7
Note

One glaring ommission about creating the MSP file after running "Setup.exe /admin" is that once you create the resulting .MSP file, you save it to the "Updates" subfolder of the network installation point, and any MSP files contained within that folder are automatically applied when Setup.exe is run (including the customisations you've made).

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
5
Terminal Services
As with previous Office versions Office 2010 will not install the OutlookVBScript component as part of an install on an RDS server (http://technet.microsoft.com/en-us/library/ff506202.aspx).

To add it post install run the same command as for the Office 2007 fix

e.g. msiexec /i {GUID} ADDLOCAL=OutlookVBScript /qb

where {GUID} is the GUID for your particular Office installation as found in Windows 2008R2 at either C:\MSOCache\AllUsers\ or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Common\InstalledPackages
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
5
Note
http://support.microsoft.com/kb/976786

To disable "Windows search error "Search cannot return results for this view" in the People Pane" Error Via Wizard. Use the registry key

HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Search
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Note

To suppress the "Outlook is not currently your default mail application" message at first run of Outlook, configure the "Make Outlook the default program for E-mail, Contacts, and Calender" setting in the OCT. This setting can be found under Modify user settings>Microsoft Outlook>Outlook Options>Other.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Note
Procedure to install Language pack(French) for MS-OfficePro 2010

1) Command to Install the Language pack silently
"Setup.exe /config OMUI.fr-fr\config.xml"

edit the config .xml as below.

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

<Setting Id="SETUP_REBOOT" Value="never" />

for more details Please refer http://social.technet.microsoft.com/Forums/en-GB/officesetupdeploy/thread/e3928c58-7027-450f-b302-9a48f1684c8a


For Silent UnInstall:-
use command
"setup.exe /uninstall OMUI.FR-FR /config OMUI.fr-fr\config.xml".
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Note
Outlook Shortcut Behavior:-After Launching shortcut "outlook" for first time self repair was triggering,In admin and user also

Solution:-Found "HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Windows Messaging Subsystem \ CMCDLLNAME32'" Key was missing from Office MUI MSI. Hence it was repairing

you can add this key in MSP while creating using Setup.exe /admin command
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Command Line
To uninstall the MS Office 2010 Powerpoint viewer (installed on systems with older office, best to remove for systems with actual Office 2010 installations) use:

MsiExec.exe /qn /X {95140000-00AF-0409-0000-0000000FF1CE}
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Note
To Uninstall run setup.exe with the following parameters

setup.exe /uninstall <version> /config <path to config file>

The version for Prefessional Plus is ProPlus and the config file would look like this

<Configuration Product="ProPlus">

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

</Configuration>
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Note
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Options\WordMail]
"ATUserAdded"=dword:00000001

Supresses the NormalEmail.dotm error message("Outlook has insufficient memory. Do you want to save NormalEmail.dotm as Rescued template") after closing Outlook, if your templates are on a read-only network drive.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
4
Note
Using config.xml, the configuration file passed as parameter to the setup.exe

The config.xml file contains setup properties in tag format as shown in example below.

<Configuration Product="Standard">

<Display Level="None" CompletionNotice="No" SuppressModal="Yes" AcceptEula="yes" />

<ARP ARPCOMMENTS ="Packaged by Dell" ARPCONTACT ="" ARPURLINFOABOUT =""
ARPURLUPDATEINFO ="" ARPHELPLINK ="" ARPHELPTELEPHONE =""
ARPNOMODIFY="Yes" ARPNOREMOVE="Yes" ARPNOREPAIR="No" />

<Setting Id="SETUP_REBOOT" Value="Never" HIDEUPDATEUI="True"/>

<COMPANYNAME Value="PBL Media" />

<USERNAME Value="PBL Media" />

</Configuration>

The "ARP" properties are not available in MST created through OCT.

How Setup uses Config.xml

Setup looks for a copy of Config.xml in the same folder as Setup.exe. Alternately, one can pass the complete path of the configuration file as parameter to the setup.exe as :- \setup.exe /config {path of configuration file}\config.xml
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
3
Note
To include SP1 for installation at the same time as initial setup, download SP1 (see related links section), and run officesuite2010sp1-kb2460049-x86-fullfile-en-us.exe /extract. From the extracted folder, just copy the .msps to your Updates folder.

Current as of 29 June 2011, I just applied SP1 to a new installation of Office 2010 Professional Plus and then went to Microsoft Update to see what was outstanding.

I can confirm that SP1 includes all previously released public updates except for the April 2011 junk mail definition update (KB972726).

As a result, my Updates folder only contains the 12 msps from SP1, the customization .msp and outlfltr.msp from KB972726.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
3
Note
A bug exists in the SP1 upgrade to Office 2010. For my organization, we're choosing not to install the "Sharepoint Workspace" feature (formerly known as Groove). I used "Setup.exe /admin" to create an MSP for the Office install that does not install the Sharepoint Workspace files. When SP1 installs however, this feature is re-enabled. It's a bug confirmed by Microsoft:

http://social.technet.microsoft.com/Forums/en/officesetupdeploy/thread/015ea622-0c8f-49b4-8e73-ae4fb4d1c716

I have the SP1 MSPs in the Office 2010 'Updates' folder so that it applies during the installation automatically. To resolve the issue of SP Workspace getting enabled, you have to modify the install of Office. The URL I posted above steps through how to do it, but I'm going to list it here, too. First create a new 'Config.XML' that has a line in it to skip the SP Worksapce files:

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

Then call the Office 2010's "Setup.exe" with a '/Modify' switch.

"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /modify ProPlus /config "<config file location>\NoGroove_config.xml"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
2
Command Line

setup.exe /adminfile office2010.msp

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Note
A Normal.dotm file is created in Word 2010. This file is pushed out to client computers (%appdata%\Microsoft\Templates) manually, by script, or in a custom MSP file that was created by using the Office Customization Tool (OCT).

When Word 2010 is started for the first time, the custom Normal.dotm file is renamed as "NormalOld.dotm." Therefore, customization that is stored in the Normal template is lost.

To resolve this issue, add the following registry key and value before Word is started after the upgrade.


[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Options]
"MigrateNormalOnFirstBoot"=dword:00000001This registry key and value prevent Word 2010 from renaming existing (or custom) Normal.dotm files.

More information:
http://support.microsoft.com/kb/2408845/en-us?fr=1
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Note
Office Professional Plus 2010 doesn't make it obvious if the installation is 32 or 64 bit. You can find the bitness via the registry HKEY_LOCAL_MACHINE\Software\ Microsoft\Office\14.0\Outlook\Bitness key will have a value of x86 or x64. If Outlook is not installed, then you can find the bitness by running the powershell script at https://gist.github.com/2292484 You can also . source the script. What you want out of it is the function Get-BinaryType which you pass the explicit location of word to I.E. "C:\Program Files\Microsoft Office\Office14\WINWORD.EXE" This will return the Bitness as BIT32 or BIT64.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Note

Ever have your install of office want to register for every user? Make these registry changes to stop that

HKCU\Software\MicroSoft\Office\14.0\Execel\Options

HKCU\Software\MicroSoft\Office\14.0\Word\Options

Created DWORD under both                           NoReReg           Value of 1

If creating a master to sysprep and you are copying that user to default this will fix it for all users.

 

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Note

if using KMS for office you can add this post install task to make sure it checks in with the server post image

start /wait cscript "c:\program files\microsoft office\office14\ospp.vbs" /act

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Virtualization
As my above post is a bit outdated... Here's a new one.

Microsoft has made some minor changes in the guide for sequencing the RC and later versions of Office 2010.

The new guide can be found here (it's actually easier now as they removed some steps for messing around with registry keys):
http://support.microsoft.com/kb/983462


The Offvirt.msi which they speak of in the guide is part of the 'Microsoft Office 2010 Deployment Kit for App-V' which can be downloaded here:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=479f12f2-5678-493e-bce1-682b3ece5431&displaylang=en
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (4)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Office

Version

14.0.4763.1024

Uninstall String

MsiExec.exe /X{90140000-1105-0000-0000-0000000FF1CE}

Questions & Answers (205)

Questions & Answers related to Microsoft Office

1
ANSWERS
0
ANSWERS
3
ANSWERS
2
ANSWERS
1
ANSWERS
1
ANSWERS
0
ANSWERS
0
ANSWERS
2
ANSWERS
2
ANSWERED
1
ANSWERS
2
ANSWERS
1
ANSWERS
1
ANSWERS
1
ANSWERS
4
ANSWERED

Blogs (27)

Blog posts related to Microsoft Office

blog
blog
blog
blog

Reviews (0)

Reviews related to Microsoft Office

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ