Click to Rate and Give Feedback
TechNet
TechNet Library
Office
Technical reference
Setup reference
 Setup properties

  Switch on low bandwidth view
Setup properties in the 2007 Office system

Updated: 2009-01-15

In previous versions of Office, you used Windows Installer properties to customize and control Office installation. In the 2007 Microsoft Office system, the Setup process is redesigned and most of these functions are replaced by options in the Office Customization Tool (OCT) or elements in the Config.xml file.

Property quick reference

The following table summarizes the recognized Windows Installer properties that you might have used in previous versions of Office. The table shows if the functionality of that property is blocked and replaced by options in the OCT or Config.xml, or if the property is available for use. More detail is provided in the sections below.

Property Use in the 2007 Office system

ADDDEFAULT

Replaced

ADDLOCAL

Replaced

ADDSOURCE

Replaced

ADVERTISE

Replaced

ALLUSERS

Blocked

ARPAUTHORIZEDCDFPREFIX

Replaced

ARPCOMMENTS

Replaced

ARPCONTACTS

Replaced

ARPHELPLINK

Replaced

ARPHELPTELEPHONE

Replaced

ARPINSTALLLOCATION

Replaced

ARPNOMODIFY

Replaced

ARPNOREMOVE

Replaced

ARPNOREPAIR

Replaced

ARPPRODUCTICON

Replaced

ARPREADME

Replaced

ARPSIZE

Replaced

ARPSYSTEMCOMPONENT

Replaced

ARPURLINFOABOUT

Replaced

ARPURLUPDATEINFO

Replaced

CCP_DRIVE

Replaced

COMPADDLOCAL

Replaced

COMPADDSOURCE

Replaced

COMPANYNAME

Replaced

DISABLEROLLBACK

Blocked

EXECUTEACTION

Blocked

EXECUTEMODE

Blocked

FILEADDDEFAULT

Replaced

FILEADDLOCAL

Replaced

FILEADDSOURCE

Replaced

HIDEUPDATEUI

Available

INSTALLLEVEL

Blocked

INSTALLLOCATION

Replaced

LIMITUI

Replaced

LOGACTION

Blocked

MEDIAPACKAGEPATH

Blocked

NOCOMPANYNAME

Replaced

NOUSERNAME

Replaced

PIDKEY

Replaced

PRIMARYFOLDER

Available

PROMPTROLLBACKCOST

Blocked

REBOOTPROMPT

Blocked

REINSTALL

Blocked

REMOVE

Replaced

ROOTDRIVE

Available

SEQUENCE

Blocked

SETUP_REBOOT

Available

SOURCELIST

Replaced

TARGETDIR

Replaced

UNINSTALL

Blocked

USERNAME

Replaced

Available properties

The following properties can be used when you install the 2007 Office system:

  • HIDEUPDATEUI--If set to True, hides the Check for Updates button on the completion dialog. This property is ignored if the completion dialog is not displayed. The default value is False.

  • PRIMARYFOLDER--Designates a primary folder for the installation.

  • ROOTDRIVE--Specifies the default drive for the destination folder of the installation. The value for this property must end with '\'.

  • SETUP_REBOOT--Determines how Setup restarts the computer after installation. You must use all uppercase letters, SETUP_REBOOT.

    • AutoAlways--Always initiate a reboot. Do not prompt the user.

    • Always--Always prompt for a reboot at the end of setup.

    • IfNeeded--Prompt for a reboot at the end of setup if setup requires a reboot. (Default)

    • AutoIfNeeded--Initiate a reboot if setup requires a reboot. Do not prompt the user.

    • Never--Never initiate or prompt for a reboot.

You set these properties in the Modify Setup properties page of the OCT, or the Setting element in the Config.xml file.

Replaced properties

A number of Windows Installer properties are replaced by options in the OCT or in the Config.xml file. Some properties are not applicable in the 2007 Office system because of Setup design changes in the 2007 version. All of these properties are blocked by Setup. That is, if you specify any of these properties in the OCT Modify Setup properties page, or with the Config.xml Setting element, Setup will end the installation.

The following table lists blocked properties whose functions are replaced by options in the OCT or by elements in the Config.xml file.

Property Replacement OCT option Replacement Config.xml element

SOURCELIST (in LIS element)

Additional network sources

SOURCELIST attribute in LIS element

COMPANYNAME

Installation location and organization name

COMPANYNAME

INSTALLLOCATION

Installation location and organization name

INSTALLLOCATION

TARGETDIR

Installation location and organization name

INSTALLLOCATION

LIMITUI

Licensing and user interface

Display

PIDKEY

Licensing and user interface

PIDKEY

ARPAUTHORIZEDCDFPREFIX

None

ARP

ARPCOMMENTS

None

ARP

ARPCONTACTS

None

ARP

ARPHELPLINK

None

ARP

ARPHELPTELEPHONE

None

ARP

ARPINSTALLLOCATION

None

ARP

ARPNOMODIFY

None

ARP

ARPNOREMOVE

None

ARP

ARPNOREPAIR

None

ARP

ARPPRODUCTICON

None

ARP

ARPREADME

None

ARP

ARPSIZE

None

ARP

ARPSYSTEMCOMPONENT

None

ARP

ARPURLINFOABOUT

None

ARP

ARPURLUPDATEINFO

None

ARP

CCP_DRIVE

None

CCP_DRIVE

NOCOMPANYNAME

None

None

NOUSERNAME

None

None

USERNAME

None

USERNAME

ADDDEFAULT

Set feature installation states

OPTIONSTATE

ADDLOCAL

Set feature installation states

OPTIONSTATE

ADDSOURCE

Set feature installation states

OPTIONSTATE

ADVERTISE

Set feature installation states

OPTIONSTATE

COMPADDLOCAL

Set feature installation states

OPTIONSTATE

COMPADDSOURCE

Set feature installation states

OPTIONSTATE

FILEADDDEFAULT

Set feature installation states

OPTIONSTATE

FILEADDLOCAL

Set feature installation states

OPTIONSTATE

FILEADDSOURCE

Set feature installation states

OPTIONSTATE

REMOVE

Set feature installation states

OPTIONSTATE

The following properties are replaced by Setup command-line options for the 2007 Office system:

  • REINSTALL--Use the Setup /repair command-line option

  • UNINSTALL--Use the Setup /uninstall command-line option

Blocked Properties

The following properties are no longer applicable in the 2007 Office system and are blocked. That is, if you specify these properties in the OCT Modify Setup properties page, or with the Config.xml Setting element, Setup will end the installation.

  • ALLUSERS (all installations of the 2007 Office system are per-machine)

  • DISABLEROLLBACK

  • EXECUTEACTION

  • EXECUTEMODE

  • INSTALLLEVEL

  • LOGACTION

  • MEDIAPACKAGEPATH

  • PROMPTROLLBACKCOST

  • REBOOTPROMPT

  • SEQUENCE

Download this book

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

See Also

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Office 2007 Deployment is a joke...      Craig S_   |   Edit   |   Show History
Really, you guys need to get your act together. This is more trouble than its worth. I think I'll stick to Office 2003. At least I can fully customize the installation and use GPSI. Not every company is Mr. Moneybags that can purchase mucho equipment/servers and deploy an SCCM/SMS server just for Office 2007. GPSI works fine for 90% of the products out there.

Thanks for making my administration tasks a nightmare. I must have wasted 3 hours reading this documentation only to decide that I've already spent enough time on deployment of this product.

Now to get some real work done and exercise my downgrade rights.

You better make Office 2010 deployable via GP or you're going to lose a lot of customers!! Who knows, maybe Office 2007 (and 2010 if not deployable via GPSI) will become the Vista of Office...the version that sucks and just won't get deployed until you come out with something useful like Windows 7.
Tags What's this?: Add a tag
Flag as ContentBug
Office 2007 sucks for the user too      FR1960   |   Edit   |   Show History
Dear Craig S.
Fear not, you are not the only one who's time is wasted. As a user, my employer decided to install 2007 in our office and did not take into account the learning curve.
My gosh. I'm so tired of playing the game "let's see what the programmer translated this function into?".
Really, How does a legacy tool in the developer tab translate into creating forms. Legacy? Really? Maybe it means something to programmers, but not to the English I know as a user.
Large pictures in tabs? Really? It would be fine if we had gone to the school of Hyreoglyphics to learn what they meant, years before installing. Not a very user friendly and when time is of the essense in customer service, this program sure sucks.
I'm just glad I can keep my 2003 at home. I had already installed 2007 once because our office let us get it really cheap, but when I saw what a headache it was, I took it off. Some things are neat, but over all, no.
I was working on a PP presentation for a friend when I installed 2007 at home. I couldn't meet the deadline so I had to uninstall it to finish it in 2003, which you don't require to be a genious to be able to figure it out.
I notice Microsoft does not have a direct e-mail set up for the users because they know they'd never hear the end of it.
Some day, I'll get to be face to face with Mr. Big Shot owner and I'll give him a piece of my brain.
Tags What's this?: 2007 (x) fed (x) friendly (x) not (x) office (x) sucks (x) uer (x) up (x) Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker