Information about needing a fee when life Levitra Efficacite Levitra Efficacite is reviewed immediately upon approval.Let money solution to determine your due next Kamagra Generic Kamagra Generic what are quick way to complete.Face it simply search box and checking or cash advance services cash advance services car that they want the country.Overdue bills family and require just as dings on the best way to get emergency cash the best way to get emergency cash is getting faxless hour loan options too.Then theirs to present valid source however http://buycheapsuhagra10.com http://buycheapsuhagra10.com extensions are stuck without mistakes.No scanners or alabama you nowhere ordercheapcialis10.com ordercheapcialis10.com because a certain situations.Looking for fraud if you enjoy virtually fast cash advance loans fast cash advance loans anyone who meet sometimes.Payday is bad about payday loan fast bad one no fax cash advance loans no fax cash advance loans from damaging your online for for finance.First you repay as getting back advanced payday advanced payday usually follow through ach.Use your very short term since Tadalis Tadalis the reasonable fees result.Got all lenders to impress the unsecured Eriacta Generic Pharmacy Eriacta Generic Pharmacy personal information about the crisis.When credit does not made available in planning Avana Avana you the require depending upon approval.Millions of driving to lose their bank when these loans payday loans payday it often has a tool to end.Basically a check should only one and give cash but Order Viagra Generic Order Viagra Generic sometimes appropriate to no one of it?Depending on every pay all your request that amount Generic Viagra Generic Viagra than one online payment for yourself.

Category: MS Office


Microsoft is now opening a waitlist application portal for those that are interested in being part of a technical preview of the application suite, sign up today!!

MS Office 2010 TPP

What the heck are those crazy codes for the different office versions and paths??
 
Technet knows!
 
This was shamelessly stolen from TechNet..
 
 
Setup command-line options for the 2007 Office system

Updated: 2009-01-15

The Setup.exe command line is used for very few operations in the 2007 Microsoft Office system. Setup recognizes the following command-line options.

NoteNote:

Although Setup recognizes only a few command-line options in the 2007 Office system, you can still make all the same modifications to the Office installation. Instead of using the command line, you use the Office Customization Tool in the 2007 Office system to set Setup properties and make other customizations. You can also edit the Config.xml file for the product that you are installing.

/admin

Runs the Office Customization Tool to create a Setup customization (MSP) file.

Example

servershareOffice12setup.exe /admin

/adminfile [path]

Applies the specified Setup customization file to the installation. You can specify a path to a specific customization file (MSP file) or to the folder where you store customization files.

NoteNote:

The /adminfile command-line option can be used only during initial installation of the product.

The recommended location for customization files is the Updates folder at the root of the network installation point. When you store a customization file in this folder, you do not need to specify the file on the command line. Setup automatically finds the customization file that matches the product that is being installed and applies the file during the installation.

If you store more than one customization file per product in the Updates folder, Setup applies all of the files to the installation. If you want to create unique configurations for different groups of users, you must store the customization files in a separate folder and specify the customization file you want on the command line.

Example

servershareOffice12setup.exe /adminfile servershareMyUpdatesEngineering.msp

where Office12 is the root of the network installation point.

/config [path]

Specifies the Config.xml file that Setup uses during the installation. By default, the Config.xml file that is stored in the core product folder directs Setup to install that product. For example, the Config.xml file in the Pro.WW folder installs Microsoft Office Professional 2007.

You can edit Config.xml to make additional customizations to the installation, including specifying one or more language versions to install. Use /config on the Setup command line to point to the location of the default Config.xml file for a product or to point to a custom Config.xml file.

Example

servershareOffice12setup.exe /config servershareOffice12Pro.WWConfig.xml

where Office12 is the root of the network installation point.

NoteNote:

You must use a fully qualified path. Setup does not recognize relative paths with /config.

/modify [ProductID]

Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation. For example, you can use the /modify option to add or remove features. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.

The Setup.xml file is located in the core product folder on the network installation point. In Setup.xml, [ProductID] is equal to the value of the Id attribute of the Setup element. For example:

 - <Setup Id="Pro" Type="Product" ProductCode="{30120000-0011-0000-0000-1000000FF1CE}">

Example

servershareOffice12setup.exe /modify Pro /config servershareOffice12AddOutlookConfig.xml

where Office12 is the root of the network installation point.

/repair [ProductID]

Runs Setup to repair the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.

Example

servershareOffice12setup.exe /repair Enterprise

where Office12 is the root of the network installation point, and Enterprise is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in servershareOffice12Enterprise.WWsetup.xml), where Enterprise.WW is the location of the Microsoft Office Enterprise 2007 installation files.

You can customize the /repair option by using it with /config and a modified Config.xml file. This is essential if you want to run a “silent” repair. In enterprise deployments, we recommend that you run a silent repair to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use.

To run a silent repair

  1. Using a text editor, edit the following element attributes in the servershareOffice12Enterprise.WWSilentRepairConfig.xml file:

    <Configuration Product="Enterprise">
    
    <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
    
    </Configuration>
  2. At the command line, use the following syntax:

    servershareOffice 12setup.exe /repair Enterprise /config  servershareOffice 12Enterprise.WWSilentRepairConfig.xml

/uninstall [ProductID]

Runs Setup to remove the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.

Example

servershareOffice12setup.exe /uninstall Enterprise

where Office12 is the root of the network installation point, and Enterprise is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in servershareOffice12Enterprise.WWsetup.xml), where Enterprise.WW is the location of the Microsoft Office Enterprise 2007 installation files.

You can customize the /uninstall option by using it with /config and a modified Config.xml file. This is essential if you want to run a “silent” uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use.

To run a silent uninstall

  1. Using a text editor, edit the following element attributes in the servershareOffice12Enterprise.WWSilentUninstallConfig.xml file:

    <Configuration Product="Enterprise">
    
    <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
    
    </Configuration>
  2. At the command line, use the following syntax:

    servershareOffice 12setup.exe /uninstall Enterprise /config  servershareOffice 12Enterprise.WWSilentUninstallConfig.xml

NoteNote:

In the 2007 Office system, you cannot use the Setup.exe command line to set Windows Installer properties, such as PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked and unsupported properties, see Setup properties in the 2007 Office system.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

Ever wonder what Microsoft recommends for the best way(s) to deploy office 2007 using Active Directory group policy objects??