Beruflich Dokumente
Kultur Dokumente
Microsoft Corporation Published: December 2008 Author: Office IT and Servers User Assistance (o12ITdx@microsoft.com)
Abstract
This book provides technical reference information for the 2007 Microsoft Office system. This includes information about Setup properties and tools, file formats, changes in application functionality, multilingual features, Office Migration Planning Manager settings, messaging file types, and security settings. The audience for this book includes IT generalists, security specialists, IT operations, help desk, and deployment staff, network architects and planners, IT messaging administrators, and consultants. The content in this book is a copy of selected content in the 2007 Office Resource Kit technical library (http://go.microsoft.com/fwlink/?LinkID=84741&clcid=0x409 ) as of the publication date above. For the most current content, see the technical library on the Web.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred. 2008 Microsoft Corporation. All rights reserved. Microsoft, Microsoft, Access, Active Directory, Excel, Groove, InfoPath, Internet Explorer, OneNote, Outlook, PowerPoint, SharePoint, SQL Server, Visio, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
ii
Contents
Technical reference for the 2007 Office release.......................................................................1 Abstract.............................................................................................................................. 1 Contents................................................................................................................................... iii I Setup reference..................................................................................................................... 1 Setup properties in the 2007 Office system..............................................................................1 Property quick reference.......................................................................................................... 1 Available properties.................................................................................................................. 3 Replaced properties................................................................................................................. 4 Blocked Properties................................................................................................................... 6 Setup command-line options for the 2007 Office system..........................................................7 /admin....................................................................................................................................... 7 Example............................................................................................................................. 7 /adminfile [path]........................................................................................................................ 7 Example............................................................................................................................. 7 /config [path]............................................................................................................................. 8 Example............................................................................................................................. 8 /modify [ProductID]................................................................................................................... 8 Example............................................................................................................................. 8 /repair [ProductID].................................................................................................................... 8 Example............................................................................................................................. 9 /uninstall [ProductID]................................................................................................................ 9 Example............................................................................................................................. 9 Config.xml file in the 2007 Office system................................................................................11 Config.xml element quick reference........................................................................................ 11 How it works........................................................................................................................... 13 Config.xml file format.............................................................................................................. 13 Config.xml element reference................................................................................................. 15 Configuration element...................................................................................................... 15 AddLanguage element..................................................................................................... 16 ARP element.................................................................................................................... 18 CCP_DRIVE element....................................................................................................... 19 Command element........................................................................................................... 19 COMPANYNAME element...............................................................................................24 Display element................................................................................................................ 24 DistributionPoint element.................................................................................................27 INSTALLLOCATION element...........................................................................................27 LIS element...................................................................................................................... 28
iii
Logging element............................................................................................................... 29 MinOSRequirement element............................................................................................31 OptionState element........................................................................................................ 32 PIDKEY element.............................................................................................................. 33 RemoveLanguage element..............................................................................................34 Setting element................................................................................................................ 34 SetupUpdates element..................................................................................................... 36 USERINITIALS element................................................................................................... 37 USERNAME element....................................................................................................... 37 Sample Config.xml file..................................................................................................... 38 Office Customization Tool in the 2007 Office system..............................................................40 Setup...................................................................................................................................... 42 Installation location and organization name.....................................................................42 Additional network sources.............................................................................................. 43 Licensing and user interface............................................................................................43 Remove previous installations.......................................................................................... 45 Add installations and run programs..................................................................................45 Office security settings..................................................................................................... 47 Modify Setup properties................................................................................................... 50 Features................................................................................................................................. 51 Modify user settings......................................................................................................... 51 Set feature installation states...........................................................................................52 Additional content................................................................................................................... 55 Add files........................................................................................................................... 55 Remove files.................................................................................................................... 56 Add registry entries.......................................................................................................... 57 Remove registry entries................................................................................................... 58 Configure shortcuts.......................................................................................................... 59 Outlook................................................................................................................................... 64 Outlook Profile.................................................................................................................. 64 Specify Exchange Settings............................................................................................... 65 Add Accounts................................................................................................................... 68 Remove Accounts and Export Settings............................................................................69 Specify Send/Receive Groups.........................................................................................69 Config.xml file OptionState Id values......................................................................................73 OptionState Id values............................................................................................................. 73 II File format reference.......................................................................................................... 81 Overview of the XML file formats in the 2007 Office system...................................................81 Benefits of the new XML file formats......................................................................................81 Structure of the new XML file formats.....................................................................................82 Start part.......................................................................................................................... 82 XML parts......................................................................................................................... 82
iv
Non-XML parts................................................................................................................. 82 Relationship part.............................................................................................................. 82 ZIP package..................................................................................................................... 83 XML file name extensions in the 2007 Office system.............................................................84 Compatibility mode in the 2007 Office system........................................................................89 Compatibility in Word 2007, Excel 2007, and PowerPoint 2007.............................................90 Excel................................................................................................................................ 90 PowerPoint....................................................................................................................... 90 Word................................................................................................................................. 91 Enabling compatibility mode............................................................................................. 91 Compatibility checker............................................................................................................. 92 Feature refresh....................................................................................................................... 92 Features impacted by compatibility mode...............................................................................92 Word 2007........................................................................................................................ 93 Excel 2007....................................................................................................................... 96 PowerPoint ...................................................................................................................... 99 III Migration reference.......................................................................................................... 103 Changes in the 2007 Office system......................................................................................103 Administrative installation images......................................................................................... 103 Clip Organizer: Autoimport.................................................................................................... 103 Document life cycle: Check in and check out.......................................................................103 File Search........................................................................................................................... 104 Help: Detect and Repair.................................................................................................... 104 Japanese IME: Editing style.................................................................................................104 Japanese IME: Register Entry.............................................................................................. 104 Korean converters................................................................................................................ 104 Matching feature states across versions..............................................................................105 MSI-only install..................................................................................................................... 105 Non-local installation source installations.............................................................................105 Office Program Recovery..................................................................................................... 105 OWC11................................................................................................................................. 105 Proofing tools........................................................................................................................ 106 Registry: Messenger registry key......................................................................................... 106 Registry: Phone registry key................................................................................................. 107 Save Workspace command.................................................................................................. 107 Setup.exe: Local Installation Source....................................................................................107 Setup.exe: Catalyst.............................................................................................................. 107 Ststpkpl.exe.......................................................................................................................... 107 Changes in Charting............................................................................................................. 108 Charting axes....................................................................................................................... 108 Chart features....................................................................................................................... 108
v
Copy/paste........................................................................................................................... 108 Excel 2007............................................................................................................................ 109 Graph: data storage.............................................................................................................. 109 Graph: legend and title......................................................................................................... 109 Graph: Lotus 1-2-3 files........................................................................................................ 109 Integration............................................................................................................................. 110 Interaction............................................................................................................................. 110 Chart selection...................................................................................................................... 110 User interface: pattern fills.................................................................................................... 110 E-mailing charts as pictures.................................................................................................. 110 Publishing as Web pages..................................................................................................... 110 Resizing................................................................................................................................ 111 Legend.................................................................................................................................. 111 Macros: Chart.Pictures.......................................................................................................... 111 Macros: XLM......................................................................................................................... 111 Programmability: hidden and deprecated objects and properties..........................................111 Programmability: null return values.......................................................................................112 Programmability: chart properties......................................................................................... 112 Programmability: Excel 5.0 object model..............................................................................112 Visual: pattern fills in 3-D charts............................................................................................ 112 Visual: realistic 3-D shading.................................................................................................. 112 Visual: data labels and legend keys......................................................................................113 Visual: scales........................................................................................................................ 113 Visual: default chart colors and formatting............................................................................113 Visual: default chart size....................................................................................................... 113 Visual: text wrapping............................................................................................................. 113 Visual: cylinder and cone charts........................................................................................... 114 Visual: raster and printer fonts.............................................................................................. 114 Visual: negative values in 3-D stacked charts.......................................................................114 Visual: data labels for #N/A values........................................................................................ 114 Visual: negative color inversion............................................................................................. 114 Changes in Access 2007...................................................................................................... 115 Data Access Pages (DAPs).................................................................................................. 115 Import RunCommand............................................................................................................ 115 Snapshot Viewer................................................................................................................... 115 User interface: export and import formats.............................................................................115 GUID-based URLs................................................................................................................ 115 Live mode............................................................................................................................. 115 Changes in CMS 2007.......................................................................................................... 116 Publishing API....................................................................................................................... 116 Changes in Excel 2007......................................................................................................... 117 Whats new........................................................................................................................... 117 New XML file formats..................................................................................................... 117
vi
New user interface and formatting capabilities...............................................................118 Improved usability.......................................................................................................... 118 More rows and columns, and other new limits................................................................119 New OLAP formulas and cube functions........................................................................119 New sharing and collaboration features.........................................................................120 New security features..................................................................................................... 120 Improved troubleshooting features.................................................................................120 Whats changed.................................................................................................................... 121 Analysis ToolPak (ATP): Function results.......................................................................121 AutoOutline command.................................................................................................... 124 BIFF8 records................................................................................................................ 124 Calculation: Multithreaded calculation (MTC).................................................................125 Charting: chart sheets, integration, and programmability...............................................125 Digital signatures ........................................................................................................... 126 Information Rights Management (IRM): Windows Rights Management Client...............126 Filtering.......................................................................................................................... 127 Functions: Subtotal........................................................................................................ 127 HTML Round-Trip........................................................................................................... 127 PivotTable: Autoformat, customizations, GetPivotData, sorting, and versions................128 Query Tables.................................................................................................................. 129 Remove Hidden Data add-in tool...................................................................................129 Send To Mail Recipient................................................................................................... 129 Shared Workbooks......................................................................................................... 130 Tables: Insert row........................................................................................................... 130 Templates....................................................................................................................... 130 Trust Center: Data links, macros....................................................................................130 Versioning...................................................................................................................... 131 Whats removed.................................................................................................................... 131 Charting: Printed Chart Size, Chart Window, charts on dialog sheets, change chart type for multiple charts, and support for XLM constants ....................................................132 Data Retrieval Services.................................................................................................. 132 Natural Language Formulas (NLFs)...............................................................................133 Changes in InfoPath 2007.................................................................................................... 134 InfoPath Tour........................................................................................................................ 134 Changes in Outlook 2007..................................................................................................... 135 ACT! and Schedule Plus....................................................................................................... 135 Attachments.......................................................................................................................... 135 Calendar............................................................................................................................... 135 E-mail: Categories................................................................................................................ 135 Forwarding out-of-date meeting requests.............................................................................136 MAPI DLLs........................................................................................................................... 136 Non-delivery receipt.............................................................................................................. 136 Personal Address Book........................................................................................................ 136
vii
Reply in IRM e-mails............................................................................................................ 137 Scripting agent...................................................................................................................... 137 Security settings................................................................................................................... 137 Show Views in Navigation Pane...........................................................................................137 Changes in OneNote 2007................................................................................................... 138 Deleted Pages...................................................................................................................... 138 Ink Groups............................................................................................................................ 138 Page Header........................................................................................................................ 138 Changes in PowerPoint 2007............................................................................................... 139 What's new........................................................................................................................... 139 New XML file formats..................................................................................................... 139 New user interface, graphics, and formatting capabilities..............................................139 Improved proofing tools.................................................................................................. 140 New sharing and collaboration features.........................................................................140 New security features..................................................................................................... 140 Improved troubleshooting and recovery features...........................................................141 What's changed or removed................................................................................................. 141 AutoContent Wizard....................................................................................................... 141 Broadcast....................................................................................................................... 141 Charts............................................................................................................................ 142 Digital signatures............................................................................................................ 142 Document life cycle........................................................................................................ 142 Information Rights Management (IRM): Windows Rights Management Client...............143 Macro recorder............................................................................................................... 143 Send for Review............................................................................................................. 144 Changes in Project 2007...................................................................................................... 145 DBCleanup: Delete Resource Task Changes.......................................................................145 Earned Value recalculations.................................................................................................145 Filtering: Column headings................................................................................................... 145 Outlook Tasks in Project Web Access timesheet..................................................................145 Project Center....................................................................................................................... 146 Quick Flags........................................................................................................................... 146 Analyze Timescaled Data in Excel COM Add-In...................................................................146 XML Reporting Wizard COM Add-In.....................................................................................146 Status Reports...................................................................................................................... 146 VBA methods for editing custom fields.................................................................................147 Changes in Project Server 2007........................................................................................... 148 Authentication....................................................................................................................... 148 Project versions.................................................................................................................... 148 Project Web Access: Microsoft Software License Terms......................................................148 Project Web Access: MUI..................................................................................................... 148 Publish by Resource............................................................................................................. 148
viii
Restore................................................................................................................................. 149 Site links............................................................................................................................... 149 Update tasks......................................................................................................................... 149 Changes in SharePoint Designer 2007................................................................................150 Design Time Control Support................................................................................................150 Hover Buttons....................................................................................................................... 150 Navigation bars in Word 2007.............................................................................................. 150 Table Eraser tool................................................................................................................... 150 Changes in Office SharePoint Server 2007..........................................................................151 Administration object model.................................................................................................. 151 Areas and Listings................................................................................................................ 151 Controls on administrator pages........................................................................................... 151 Crawl schedules................................................................................................................... 152 Portal Provisioning................................................................................................................ 152 Query object model.............................................................................................................. 152 Search: Area Alerts............................................................................................................... 152 Search: Automatic propagation............................................................................................. 152 Search: More Info link........................................................................................................... 153 Search: MySite Alerts........................................................................................................... 153 Search: TIFF filter................................................................................................................. 153 Search: Web parts................................................................................................................ 153 Shared Services................................................................................................................... 153 Topology Management......................................................................................................... 154 Windows SharePoint Services 3.0 Security Model...............................................................154 Changes in Visio 2007.......................................................................................................... 155 Entry points to NetMeeting and File Search.........................................................................155 Menu changes...................................................................................................................... 155 Organization Chart themes................................................................................................... 155 Styles user interface............................................................................................................. 156 Visio SDK: Visual Studio 6.0 wizards and managed code tutorials.......................................156 Changes in Word 2007......................................................................................................... 157 Whats new........................................................................................................................... 157 New XML file formats..................................................................................................... 157 New user interface, graphics, and formatting capabilities..............................................157 Improved proofing tools.................................................................................................. 158 New sharing and collaboration features.........................................................................158 New security features..................................................................................................... 158 Improved troubleshooting and recovery features...........................................................159 Whats changed.................................................................................................................... 159 Charts............................................................................................................................ 159 Digital signatures ........................................................................................................... 160 Document life cycle........................................................................................................ 160
ix
Information Rights Management (IRM): Windows Rights Management Client...............161 Microsoft Office Document Imaging (MODI) tool............................................................161 Send To Mail Recipient................................................................................................... 161 Whats removed.................................................................................................................... 162 IV International reference.................................................................................................... 165 Mixed language versions of the 2007 Office system.............................................................165 Applications unavailable in some languages........................................................................165 Language Interface Packs.................................................................................................... 167 Language identifiers in the 2007 Office system....................................................................170 Language identifiers............................................................................................................. 170 V Office Migration Planning Manager Reference.................................................................173 Introduction to OMPM........................................................................................................... 173 OMPM contents.................................................................................................................... 174 Installing OMPM................................................................................................................... 174 OMPM requirements............................................................................................................ 174 Client system requirements............................................................................................174 Administrator system requirements................................................................................175 How the OMPM File Scanner works.....................................................................................177 Log and CAB files generated by the OMPM File Scanner....................................................177 Files scanned by the OMPM File Scanner............................................................................179 Sample SMS deployment script for OMPM..........................................................................181 Use IExpress 2.0 to create a distribution package for OMPM..............................................185 OMPM Reports filtering reference........................................................................................ 186 Schema for the OMPM database.........................................................................................188 Schema for the OMPM File Scanner....................................................................................188 OMPM File Scanner schema: scan data........................................................................188 OMPM File Scanner schema: file data...........................................................................190 Schema for OMPM Compatibility Report data......................................................................193 OMPM Compatibility Report data schema: tools, actions, and issues data...................193 OMPM Compatibility Report data schema: file location data..........................................195 Schema for Access data....................................................................................................... 196 VI Messaging reference....................................................................................................... 201 Attachment file types restricted by Outlook 2007..................................................................201 VII Security reference.......................................................................................................... 205 Security policies and settings in the 2007 Office system......................................................205 Trusted locations and trusted publishers settings.................................................................205
x
Trusted locations settings............................................................................................... 205 Trusted publishers settings............................................................................................ 210 ActiveX control settings........................................................................................................ 210 Settings for disabling ActiveX controls...........................................................................210 Settings for changing the way ActiveX controls are initialized........................................211 Add-in settings...................................................................................................................... 221 Settings for disabling add-ins.........................................................................................221 Settings for requiring that add-ins are signed by a trusted publisher..............................223 Settings for disabling notifications for unsigned add-ins.................................................225 VBA macro settings.............................................................................................................. 227 Settings for changing the default behavior of macros....................................................227 Settings for changing VBA............................................................................................. 230 Settings for changing macro behavior in applications that are started programmatically through Automation..................................................................................................... 232 Settings for preventing virus-scanning programs from scanning encrypted macros......234 Document protection settings...............................................................................................235 Global document protection settings..............................................................................235 Application-specific document protection settings..........................................................236 External content settings...................................................................................................... 238 Hyperlink warnings settings............................................................................................ 238 Linked images settings................................................................................................... 240 Internet Explorer feature control settings..............................................................................240 Privacy options..................................................................................................................... 243 Document Inspector options...........................................................................................243 Metadata protection options...........................................................................................243 Office privacy options..................................................................................................... 245 Application-specific privacy options................................................................................247 Block file format settings....................................................................................................... 248
xi
I Setup reference
ADDDEFAULT ADDLOCAL ADDSOURCE ADVERTISE ALLUSERS ARPAUTHORIZEDCDFPREFIX ARPCOMMENTS ARPCONTACTS ARPHELPLINK ARPHELPTELEPHONE ARPINSTALLLOCATION ARPNOMODIFY ARPNOREMOVE ARPNOREPAIR
Replaced Replaced Replaced Replaced Blocked Replaced Replaced Replaced Replaced Replaced Replaced Replaced Replaced Replaced
Property
ARPPRODUCTICON ARPREADME ARPSIZE ARPSYSTEMCOMPONENT ARPURLINFOABOUT ARPURLUPDATEINFO CCP_DRIVE COMPADDLOCAL COMPADDSOURCE COMPANYNAME DISABLEROLLBACK EXECUTEACTION EXECUTEMODE FILEADDDEFAULT FILEADDLOCAL FILEADDSOURCE HIDEUPDATEUI INSTALLLEVEL INSTALLLOCATION LIMITUI LOGACTION MEDIAPACKAGEPATH NOCOMPANYNAME NOUSERNAME PIDKEY PRIMARYFOLDER PROMPTROLLBACKCOST REBOOTPROMPT REINSTALL
Replaced Replaced Replaced Replaced Replaced Replaced Replaced Replaced Replaced Replaced Blocked Blocked Blocked Replaced Replaced Replaced Available Blocked Replaced Replaced Blocked Blocked Replaced Replaced Replaced Available Blocked Blocked Blocked
2
Property
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) COMPANYNAME INSTALLLOCATION TARGETDIR LIMITUI PIDKEY ARPAUTHORIZEDCDFPREFIX ARPCOMMENTS ARPCONTACTS ARPHELPLINK ARPHELPTELEPHONE ARPINSTALLLOCATION ARPNOMODIFY ARPNOREMOVE ARPNOREPAIR ARPPRODUCTICON
Additional network sources Installation location and organization name Installation location and organization name Installation location and organization name Licensing and user interface Licensing and user interface None None None None None None None None None None
Display
ARP ARP ARP ARP ARP ARP ARP ARP ARP ARP
Property
ARPREADME ARPSIZE ARPSYSTEMCOMPONENT ARPURLINFOABOUT ARPURLUPDATEINFO CCP_DRIVE NOCOMPANYNAME NOUSERNAME USERNAME ADDDEFAULT ADDLOCAL ADDSOURCE ADVERTISE COMPADDLOCAL COMPADDSOURCE FILEADDDEFAULT FILEADDLOCAL FILEADDSOURCE REMOVE
None None None None None None None None None Set feature installation states Set feature installation states Set feature installation states Set feature installation states Set feature installation states Set feature installation states Set feature installation states Set feature installation states Set feature installation states Set feature installation states
None None
OPTIONSTATE OPTIONSTATE OPTIONSTATE OPTIONSTATE OPTIONSTATE OPTIONSTATE OPTIONSTATE OPTIONSTATE OPTIONSTATE 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
See Also Office Customization Tool in the 2007 Office system Config.xml file in the 2007 Office system Setup command-line options for the 2007 Office system
/admin
Runs the Office Customization Tool to create a Setup customization (MSP) file.
Example
\\server\share\Office12\setup.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. Note: 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
\\server\share\Office12\setup.exe /adminfile \\server\share\MyUpdates\Engineering.msp where Office12 is the root of the network installation point.
7
/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
\\server\share\Office12\setup.exe /config \\server\share\Office12\Pro.WW\Config.xml where Office12 is the root of the network installation point. Note: 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-00000000-1000000FF1CE}">
Example
\\server\share\Office12\setup.exe /modify Pro /config \\server\share\Office12\AddOutlookConfig.xml where Office12 is the root of the network installation point.
/repair [ProductID]
Runs Setup to repair the specified product from the users computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.
Example
\\server\share\Office12\setup.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 \\server\share\Office12\Enterprise.WW\setup.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 \\server\share\Office12\Enterprise.WW\SilentRepairConfig.xml file: <Configuration Product="Enterprise"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> </Configuration> 2. At the command line, use the following syntax: \\server\share\Office 12\setup.exe /repair Enterprise /config server\share\Office 12\Enterprise.WW\SilentRepairConfig.xml \\
/uninstall [ProductID]
Runs Setup to remove the specified product from the users computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.
Example
\\server\share\Office12\setup.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 \\server\share\Office12\Enterprise.WW\setup.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 \\server\share\Office12\Enterprise.WW\SilentUninstallConfig.xml file: <Configuration Product="Enterprise"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> </Configuration> 2. At the command line, use the following syntax: \\server\share\Office 12\setup.exe /uninstall Enterprise /config \\server\share\Office 12\Enterprise.WW\SilentUninstallConfig.xml Note: 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. See Also Office Customization Tool in the 2007 Office system Config.xml file in the 2007 Office system
10
Customizing Setup options, such as logging and the location of the Setup customization file and software updates. Setting installation options, such as user and company name. Copying the local installation source (LIS) to the user's computer without installing Office. Adding or removing languages from the installation.
The Config.xml is required to customize an installation that you deploy with Group Policy Software Installation. For more information, see Use Group Policy to deploy the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179214.aspx). Important: Use a text editor, such as Notepad, to edit Config.xml. Do not use a general-purpose XML editor, such as Microsoft Office Word 2007.
Top-level element Add a language to the installation Values that control the text and behavior of Add or Remove Programs in Control Panel for the product The fully qualified path to the folder that is searched by RMCCPSEARCH
Command
11
Element
Description
The name of the organization or company of the user on whose computer the product is being installed Display DistributionPoint The level of UI that Setup displays to the user The fully qualified path to the network installation point from which the installation is to run The fully qualified path to the folder on the user's computer in which the product is installed LIS Logging MinOSRequirement OptionState Options for how the local installation source (LIS) is cached on the user's computer Options for the type of logging that Setup performs The minimum supported operating system for this product Options to specify how individual product features are to be handled during installation The 25-character volume license key RemoveLanguage Setting SetupUpdates Remove a language from the installation Values for Windows Installer properties The search path for Setup to use to find Setup customization files The initials of the user on whose computer the product is being installed The name of the user on whose computer the product is being installed
12
How it works
Setup looks for a copy of Config.xml in the same folder as Setup.exe. If a copy is not found there, Setup uses the Config.xml file that resides in the core product folder for the product that you are installing (if there are multiple products in the network installation point, Setup waits until you specify which product to install before it looks for the copy of Config.xml). The copy of Config.xml residing in the product folder identifies the product through the Product attribute of the Configuration element. You can also use the /config Setup command-line option to specify the location of the Config.xml file. For example: \\server\share\setup.exe /config \\server\share\Enterprise.WW\config.xml Note: If you have also created a Setup customization file using the OCT, the customizations you define in Config.xml take precedence over those in the customization file.
13
For example: <Configuration Product="Enterprise"> <PIDKEY Value="1234512345123451234512345" /> <Display Level="none" AcceptEula="Yes"/> </Configuration> Comments can be added anywhere and are delimited by "<!--" and "-->". For example: <!-- Install Office Enterprise 2007 --> <Configuration Product="Enterprise" > <!-- Set the product key --> <PIDKEY Value="1234512345123451234512345" /> <Display <!-- Turn off all Setup UI --> Level="none" <!-- Accept the EULA for the user --> AcceptEula="Yes" /> </Configuration> Each Office product folder contains a default Config.xml file, which consists of a Configuration element with the Product attribute set to the appropriate value for the product. A number of example elements enclosed in comments are included within the Configuration element. Remove the beginning and closing comment marks and enter the appropriate attribute values to activate these elements. For example, you can activate the PIDKEY element by changing this: <!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> --> to this: <PIDKEY Value="1234567890123456789012345" />
14
Configuration element
Top-level element. This element is required, and all other elements must appear within this element.
Syntax
<Configuration [Product="productID"] > ... </Configuration>
Attributes
Attribute Value Description
Product
productID
The value of the ID attribute in the Setup element in the setup.xml file for the product that is being installed
Remarks
The Product attribute identifies the product affected by this Config.xml file. The productID is defined in the Setup.xml file located in the core folder for the product, in the ID attribute of the Setup element. The Product attribute is optional, unless you set the DisplayLevel attribute to "Basic" or "None". In this case, the Product attribute is required. If the product specified by the Product attribute does not exist in the network installation point, Setup ends the installation.
15
Example
The productID for Office Enterprise 2007 is located in Enterprise.WW\Setup.xml in the following line: <Setup Id="Enterprise" Type="Product" ... > You use this productID in Config.xml to specify Office Enterprise 2007 by entering the following: <Configuration Product="Enterprise"> ... </Configuration>
AddLanguage element
Adds the specified language to the installation.
Syntax
<AddLanguage Id="ll-cc" | "match" [ShellTransform="Yes"] />
Attributes
Attribute Value Description
Id
ll-cc
The language identifier. For a complete list of language tags, see Language identifiers in the 2007 Office system. Matches the language of the user's Windows user locale. Specifies the language for the shell user interface. If more than one AddLanguage element is specified, then one (and only one) must specify the ShellTransform element.
16
Remarks
The language must be available on the network installation point. You can have multiple AddLanguage and RemoveLanguage elements. If both RemoveLanguage and AddLanguage elements specify the same language, the AddLanguage element takes precedence and the language is installed. Note: If more than one AddLanguage element is specified, then one (and only one) must specify the ShellTransform element or Setup ends the installation. There are three different language concepts you should know about when installing the 2007 Office system: Setup user interface (UI): the language of the installation. Shell UI: the language of shortcuts, right-click context menus, and tooltips. Office UI: the language of the Office user interface and menus.
When there are multiple Office languages, these three values are determined as follows: By default, the Setup UI is dependent on the set of available resources for installation and the ability to match the user locale. The Setup UI will match the user locale by default. The Shell UI depends on the set of languages being installed and by default it follows the Setup UI. The default Office UI language depends on the user locale and current user settings. The default is to use the Windows user locale set on each user's computer. This means that in the default case, the Setup UI, Shell UI, and Office UI will all be the same. A locale in the Windows operating systems is a set of user preference information related to the user's language, environment, and cultural conventions. This information is represented as a list of values used to determine the correct input language, keyboard layout, sorting order, and the formats used for numbers, dates, currencies, and time. The user locale is a per user setting that determines the formats used by default to display dates, times, currency, and numbers, and the sorting order of text. A user locale is specified for each account created on a computer. If an administrator specifies multiple languages for installation in the Config.xml file, the shell UI language must be chosen from the set of installing languages. To do this, administrators specify the ShellTransform attribute of the AddLanguage element in the Config.xml file. This specifies which language Setup should use for the shell UI. However, this will not necessarily affect the choice of Setup UI or Office UI when installing on the users computer. For instance, if you have an Office image with English, French, German, and Spanish, to specify that Setup install full language support for all these languages and have the Shell UI follow the users default regional options, you add the following elements in the Config.xml file: <AddLanguage Id="match" ShellTransform="yes"/> <AddLanguage Id="enus" /> <AddLanguage Id="fr-fr" /> <AddLanguage Id="de-de" /> <AddLanguage Id="es-es" /> In the preceding example, Setup installs all of the specified languages and the Shell UI matches the language of the user's locale. If there were more languages available in the source image, the
17
match value in the preceding example may install an additional language in the case where the match language does not resolve to one of the other four explicitly called out languages. For instance, if Japanese was also included in the source, this example would install Japanese in addition to the other four languages when installed on a computer with the user locale set to Japanese.
Example
<AddLanguage Id="en-us" ShellTransform="Yes" />
ARP element
Specifies values that control the text and behavior of Add or Remove Programs in Control Panel for the product.
Syntax
<ARP attribute="value" [attribute="value"] ... />
Attributes
Attribute Value Description
ARPCOMMENTS
text
Additional text. Can be up to 255 characters, though all characters might not display. List of technical support contacts. Prevents users from modifying the product installation by making the Change button unavailable. Allows user to modify the product installation. Prevents users from removing the product by making the Remove button unavailable. Allows users to remove the product. URL for the product's home page.
18
ARPCONTACT ARPNOMODIFY
text Yes
Attribute
Value
Description
ARPURLUPDATEINFO ARPHELPLINK
URL URL
URL for information about product updates. URL of a Web site from which users can receive technical support. Phone numbers for technical support.
ARPHELPTELEPHONE
text
CCP_DRIVE element
The fully qualified path to the folder that RMCCPSEARCH is to search. The RMCCPSEARCH action uses file signatures to validate that qualifying products are installed on a system before an upgrade installation is performed.
Syntax
<CCP_DRIVE Value="value" />
Attributes
Attribute Value Description
Value
value
Example
<CCP_DRIVE Value="\\server\office2003" />
Command element
Specifies a command line to run. Tip: The equivalent option in the OCT is Add installations and run programs.
19
Syntax
<Command Path="path" [QuietArg="arguments"] [Args="args"] [ChainPosition="Before" | "After"(default)] [Wait="mseconds"] [QuietWait="mseconds"] [Execute="Install"(default) | "Uninstall"] [Platform="x86"(default) | "x64"] />
Attributes
You can specify double-quotation marks (") in the Path and Args attributes by specifying two double-quotation marks together ("").
Attribute Value Description
Path QuietArg
path string
Fully qualified path to the executable or MSI file. String of arguments to be appended to the command line if you are configuring a quiet installation. For more information about when to use the QuietArg attribute, see the Remarks section, following this table. String of arguments to be passed to the executable. For information about when to use the Arg attribute for chained installations, see the Remarks section, following this table. This command is executed before the primary product installation.
Args
string
ChainPosition
Before
20
Attribute
Value
Description
After (default)
This command is executed after the primary product installation. When you install with the DisplayLevel attribute set to "Full" or "Basic", this is the number of milliseconds to wait after you run the program before you continue the installation. The default is 0 (zero), which indicates no waiting. When you install with the DisplayLevel attribute set to "None", this is the number of milliseconds to wait after you run the program before you continue the installation. The default is 0 (zero), which indicates no waiting. Setup executes this command when the primary product is installed. Setup executes this command when the primary product is uninstalled. Specifies that this program requires the Intel x86 platform. This command runs only if the computer on which the installation is run matches this platform requirement.
Wait
mseconds
QuietWait
mseconds
Execute
Install (default)
Uninstall
Platform
x86 (default)
21
Attribute
Value
Description
x64
Specifies that this program requires a 64-bit processor that supports the x64 extensions to the x86 architecture. This command runs only if the computer on which the installation is run matches this platform requirement.
Remarks
The Command element in Config.xml file and the Add installations and run programs option in the OCT (command-lines entered in the Add Program Entry and Modify Program Entry dialog boxes) are intended to be used only for initial product installs and uninstalls. The Command element commands are processed only during initial installs and uninstalls. If Command element commands are used for customizations after the initial installation, they are ignored. The command line can be specified for a chained installation or an executable that runs when this product is installed. If this is specified for a product in the 2007 Office system, you must specify a command line for Setup.exe rather than a single MSI file. For other products, you can specify an MSI file or an executable file (such as an EXE or BAT file). If you are configuring a chained installation in the Config.xml file that you want to run quietly, you must also specify the QuietArg or Args attributes, which is dependent on whether the main Office product is configured with a Display Level set to None, Basic, or Full. The following examples illustrate when to use the QuietArg versus Args attributes: If the main Office installation is set as Display Level="None", and you want the chained installation to also run without user interaction, you must specify the QuietArg attribute. You can set QuietArg to one of the following values: "/qn", "/qb-", or "/qr". where: /qn means no UI is displayed. /qb- displays basic UI without modal dialog boxes. /qr displays a reduced UI. A modal dialog box is displayed at the end of the installation. For example, use the following to specify no UI display: QuietArg="/qn" Note that if you set the main installation as Display Level="None" and you do not specify a QuietArg="/q", the installation may prompt the user for information or to click to the next dialog box. This might halt the installation if the user is not present to respond to the dialog box prompts.
22
If the main Office installation is set as Display Level="Basic", and you want the chained installation to also run without user interaction, you must use the Args attribute and set it to one of the following values: "/qn", "/qb-", or "/qr". For example, use the following to specify basic UI display: Args="/qb-". If you are using the Command element in the Config.xml file to chain an additional Windows Installer (MSI) based product, you must specify the Wait attribute with a -1 value (Wait="-1"). If you do not specify a -1 value for the Wait attribute, chaining may fail and a message similar to the following will be displayed: "Error 1618 (Another instance of setup is running)." For example, use the following syntax to specify the Wait=-1 value, where %WINDIR is the folder containing the Windows files: <Command Path="%WINDIR%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" Wait="-1" /> Important: Although it is possible to use chaining to install additional Windows Installer-based products, this method is not as reliable as installing each product separately. For example, if you chain two installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation may not complete successfully. The recommended method for installing multiple products together in enterprise environments is to use a deployment management program such as Microsoft Systems Management Server instead of chaining. For more information, see Using Systems Management Server 2003 to deploy the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179198.aspx). If there are two or more Command elements in the Config.xml file, they run in the order in which they are specified in Config.xml. Tip: If the product you are chaining requires a later operating system than the operating system required by the 2007 Office system, use the MinOSRequirement element to specify the minimum operating system required for this installation.
Examples
<Command Path="myscript.exe" Args="/id ""123 abc"" /q" /> <Command Path="\\server\share\setup.exe /config \\server\share\Pro.WW\config.xml" />
23
COMPANYNAME element
The name of the organization or company of the user on whose computer the product is being installed. Tip: The equivalent option in the OCT is the Organization name setting in Installation location and organization name.
Syntax
<COMPANYNAME Value="companyname" />
Attributes
Attribute Value Description
Value
companyname
Example
<COMPANYNAME Value="Microsoft Corporation" />
Display element
The level of UI that Setup displays to the user. Tip: The equivalent option in the OCT is the Display level and license agreement settings in Licensing and user interface.
Syntax
<Display Level="None" | "Basic" | "Full"(default) CompletionNotice="Yes" | "No"(default) SuppressModal="Yes" | "No"(default) NoCancel="Yes" | "No"(default) AcceptEula="Yes" | "No"(default) />
24
Attributes
Attribute Value Description
Level
None Basic
No Setup UI is displayed. Setup displays the Welcome screen, the Product Key (PIDKEY) page (if needed), the End-User License Agreement (EULA) page (if needed), a progress bar, and the completion notice (if allowed). Setup displays all UI to the user. Only applies if Level is set to "Basic" or "None": Setup displays the completion notice. Only applies if Level is set to "Basic": Setup does not display the completion notice. Only applies if Level is set to "Basic": Setup does not display error messages and other dialog boxes that might interrupt the installation. Only applies if Level is set to "Basic": Setup displays errors and other dialog boxes as needed. If Level is set to "Full" or "Basic", disable the cancel button (X in upper-right corner of the progress dialog). If Level is set to "Full" or "Basic", allow the user to cancel the installation from the progress bar.
No (default)
SuppressModal
Yes
No (default)
NoCancel
Yes
No (default)
25
Attribute
Value
Description
AcceptEULA
Yes
The End-User License Agreement is accepted on behalf of the user. Setup does not display the EULA page. If Level is not set to "None", Setup displays the EULA page.
No (default)
Remarks
If this element is not defined, the default settings are used. If an invalid value is specified, Setup ends the installation. If the Level attribute is set to "Basic" or "None" and you supply a product key using the element, Setup assumes that you also accept the license agreement on behalf of the user. Notes In enterprise deployments, it is recommended that you set the Display level value to none to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use. Setting the Display Level value to none assumes that the SuppressModal and CompletionNotice attributes are silenced and that the end-user license agreement (EULA) is accepted. Administrators must also make sure that no Office applications are running during an installation of the 2007 Office system. If you set the Display level value to basic and SuppressModal to yes, users may be prompted if any Office files are in use. Setting Display level to none prevents prompting users in such cases. The SuppressModal attribute does not prevent files in use messages from displaying; only Display level set to none prevents their display. The Display element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, then Setup uses the default display options.
Example
<Display Level="none" AcceptEula="Yes" />
26
DistributionPoint element
Specifies the fully qualified path to the network installation point from which the installation is to run.
Syntax
<DistributionPoint Location="path" />
Attributes
Attribute Value Description
Location
path
The fully qualified path to the network installation point from which the installation is to run
Remarks
If this is not specified, then Setup assumes that the Setup.exe file is located at the root of the network installation point. Note: The DistributionPoint element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, it ignores this element because the network installation point has already been found.
Example
<DistributionPoint Location="\\server1\office" />
INSTALLLOCATION element
Specifies the fully qualified path to the folder on the user's computer in which the product is installed. Tip: The equivalent option in the OCT is the Default installation path setting in Installation location and organization name.
Syntax
<INSTALLLOCATION Value="path" />
27
Attributes
Attribute Value Description
Value
path
The fully qualified path to the folder on the user's computer in which the product is installed.
Remarks
You can use system environment variables in the path. If this element is not specified, Office is installed in %ProgramFiles%\Microsoft Office.
Example
<INSTALLLOCATION VALUE="%ProgramFiles%\MyApps" />
LIS element
Controls how the local installation source (LIS) is cached on the user's computer and specifies the location of one or more network installation points that contain the installation files for the product.
Syntax
<LIS [CACHEACTION="CacheOnly" | "RemoveCacheOnly"] [SOURCELIST="semicolon-delimited-path-list"] />
Attributes
Attribute Value Description
CACHEACTION
CacheOnly
Setup copies the LIS to the user's computer, but does not install the product. If the cache is copied to the user's computer and Office is not installed, Setup removes the LIS from the user's computer but does not install or uninstall the product.
RemoveCacheOnly
28
Attribute
Value
Description
SOURCELIST
semicolon-delimited-path-list
A list, separated by semicolons, of one or more network installation points that contain the installation files for the product. The equivalent option in the OCT is Additional network sources.
Remarks
By default, the LIS is created in the folder \MsoCache\All Users at the root of the drive into which Office is installed. Setup customization files and software updates in the Updates folder in the network installation point are also copied. If you specify , the drive designation in the path is used to determine on what drive the LIS is created. For example, if the path is E:\office\files, the LIS is created on drive E. The sources listed by the SOURCELIST attribute are kept with the installed product and are used by Setup if the local installation source (LIS) on the user's computer is missing or corrupted.
Example
<LIS CACHEACTION="CacheOnly" /> <LIS SOURCELIST="\\server1\office;\\server2\corpdata" />
Logging element
Specifies the type of logging that Setup performs.
Syntax
<Logging Type="Off" | "Standard"(default) | "Verbose" Path="path" Template="filename.txt" />
29
Attributes
Attribute Value Description
Type
Setup does no logging. Setup writes installation information to the log file. Setup writes all installation information to the log file. The fully qualified path to the folder used for the log file. You can use environment variables. Default is %temp%. The name of the log file. If you insert the string * anywhere in the file name, a unique log file is created for each installation performed by Setup.exe (see the explanation below). If * is not included and the file name specified already exists, log information is appended to the existing file. The .txt file extension must be included. The default template is SetupExe(*).log.
Path
path
Template
filename.txt
Remarks
You can specify a * anywhere in the Template value. Setup inserts a string in that location with the following format: YYYYMMDDHHMMSSxxx where: 1. YYYY = Year 2. MM = Month 3. DD = Day 4. HH = Hour
30
5. MM = Minute 6. SS = Seconds 7. xxx = a unique string generated by Setup Note: The Logging element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, then Setup uses the default logging options.
Example
<Logging Type="standard" Path="%temp%" Template="MyLog(*).txt" /> With this example, Setup creates a log file each time it installs the product. Setup uses unique file names such as the following: %temp%\MyLog(20060428110717CFC).txt %temp%\MyLog(20060429113143C70).txt
MinOSRequirement element
Specifies the minimum supported operating system for this product.
Syntax
<MinOSRequirement VersionNT="version" WindowsBuild="number" ServicePackLevel="number" />
Attributes
Attribute Value Description
31
501 502
2600 3790
2 or greater 0 or greater
Remarks
Setup does not proceed with the installation if the user's computer has an operating system with a version earlier than what is specified here (or the Office default if this element is not specified). You cannot specify a version of Microsoft Windows here that is earlier than the version required by the 2007 Office system. For information about system requirements, see System requirements for the 2007 Office release.
OptionState element
Specifies how specific product features are handled during installation. Important: In most situations, it is recommended that you use the OCT to change the installation state of features. The equivalent option in the OCT is Set feature installation states.
Syntax
<OptionState Id="optionID" State="Absent" | "Advertise" | "Default" | "Local" [Children="force"] />
Attributes
Attribute Value Description
Id State
An item that the user can choose to install. The feature is not installed. The feature is installed the first time it is used.
32
Attribute
Value
Description
The feature returns to its default installation state. The feature is installed on the user's computer. All child features of the feature are set to the specified state.
Remarks
A feature is an item that the user can choose to install. The Id value for a feature is defined in the Option element of the Setup.xml file in the core product folder. For a list of OptionState Id Values, see Config.xml file OptionState Id values. For information about modifying the OptionState element in Config.xml, see the Modifying the Config.xml File OptionState element section in Use Group Policy Software Installation to deploy the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179214.aspx).
Example
<OptionState Id="ExcelAddinFiles" State="Absent" Children="force" />
PIDKEY element
The 25-character volume license key. Tip: The equivalent option in the OCT is the Product key setting in Licensing and user interface.
Syntax
<PIDKEY Value="25-character-key" />
Attributes
Attribute Value Description
Value
25-character-key
Remarks
When the PIDKEY value is set, users are not required to enter a product key when they install Office.
Example
<PIDKEY Value="1234512345123451234512345" /> Note: If the Level attribute of the Display element is set to "Basic" or "None" and you supply a product key using the PIDKEY element, Setup assumes that you also accept the license agreement on behalf of the user. In this case, regardless of how you set the AcceptEULA attribute of the Display element, the user is not prompted for the license agreement either during installation or the first time an Office application runs.
RemoveLanguage element
Removes the specified language from the installation.
Syntax
<RemoveLanguage Id="ll-cc" />
Attributes
Attribute Value Description
Id
ll-cc
The language identifier. For a complete list of language tags, see Language identifiers in the 2007 Office system.
Remarks
If the language is not installed on the user's computer, the RemoveLanguage element is ignored. You can have multiple AddLanguage and RemoveLanguage elements. If both RemoveLanguage and AddLanguage elements specify the same language, the AddLanguage element takes precedence and the language is installed.
Example
<RemoveLanguage Id="en-us" />
Setting element
Allows you to specify values for Windows Installer properties.
34
Syntax
<Setting Id="name" Value="value" />
Attributes
Attribute Value Description
Id Value
name value
The name of the Windows Installer property The value to assign to the property
Remarks
Not all Windows Installer properties can be specified in the Setting element. If a blocked property is specified, Setup ends the installation process. If a supported property is specified, Setup passes the property directly to Windows Installer. For a complete list of Windows Installer properties, including an explanation of supported and blocked properties, see Setup properties in the 2007 Office system. The Setting element supports the RemovePrevious setting. This setting removes the specified application from the installation and uses the following syntax: <Setting Id="RemovePrevious" Value="Option Id" /> where Option Id is the identifier value for the 2007 Office system application. To specify multiple applications, use a comma-separated list to indicate the appropriate Option Id values. For a complete list of Option Id values, see Config.xml file OptionState Id values. Note: If you are installing Outlook, a previously installed version of Outlook is always removed, regardless of the users preference. If you specify RemovePrevious with an Option Id value, only the specified applications are removed. If you do not specify RemovePrevious, any previously installed Office applications for which a replacement is being installed are removed. This is the default behavior. If you specify RemovePrevious with a blank value (RemovePrevious=""), no applications are removed. The Setting element also supports the SETUP_REBOOT property. SETUP_REBOOT initiates a reboot after installation and uses the following syntax: <Setting Id="SETUP_REBOOT" Value="value" />
35
where value can be one of the following: 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.
Examples
<Setting Id="SETUP_REBOOT" Value="NEVER" /> <Setting Id="RemovePrevious" Value="WORDFiles" />
SetupUpdates element
Specifies a search path for Setup to use to find Setup customization files.
Syntax
<SetupUpdates [CheckForSUpdates="Yes"(default) | "No"] [SUpdateLocation="path-list"] />
Attributes
Attribute Value Description
CheckForSUpdates
Yes (default)
Setup uses the path list in SUpdateLocation to find Setup customization files. Setup does not search for Setup customization files using the path list in SUpdateLocation. A list of fully qualified paths to folders, separated by semicolons.
No
SUpdateLocation
path-list
Remarks
Setup looks in all the specified folders for Setup customization files that were created for the product that is being installed, and applies them in alphabetical order by file name. If a Setup
36
customization file was specified on the Setup command line, that file is applied first, followed by any files found in the folder specified by this element.
Example
<SetupUpdates CheckForSUpdates="Yes" SUpdateLocation="\\server1\office\updates;\\server2\corpdata\updates" />
USERINITIALS element
The initials of the user on whose computer the product is being installed.
Syntax
<USERINITIALS Value="value" />
Attributes
Attribute Value Description
Value
value
Example
<USERINITIALS Value="JD" />
USERNAME element
The name of the user on whose computer the product is being installed.
Syntax
<USERNAME Value="value" />
37
Attributes
Attribute Value Description
Value
value
Remarks
The Office 2007 Username element data is populated as follows. If the user who is running Office is the same user who installed Office, the Username and Initials supplied during setup are used. The user is not prompted when Office first starts. This case is most popular for home users who install Office themselves. If the user who is running Office is not the same user who installed Office, Office prompts the user to confirm his or her Username and Initials when Office first starts. This case is most popular in a corporate environment, where an administrator installs Office on behalf of the user. The value for the Username element shown to the user at first boot time may be pre-populated with a default value from a previously installed version of Office or from the currently logged on user. Note that the default value is not used unless it is confirmed by the user. If there is a previous version of Office installed on the computer, the registry key created by the previous version of Office is used. For example, if the prior Office installation is Office 2003, the registry key is provided at HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\UserInfo .
Example
<USERNAME Value="John Doe" />
38
<Configuration Product="Enterprise"> <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> <!-- <Logging Type="verbose" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> --> <!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> --> <!-- <USERNAME Value="Customer" /> --> <!-- <COMPANYNAME Value="MyCompany" /> --> <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" />--> <!-- <LIS CACHEACTION="CacheOnly" /> --> <!-- <DistributionPoint Location="\\server\share\Office12" /> --> <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> <!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> --> <!-- <Command Path="%WINDIR%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --> </Configuration> See Also Setup architecture overview for the 2007 Office System Office Customization Tool in the 2007 Office system Setup properties in the 2007 Office system Deploy custom configurations of the 2007 Office system (step-by-step) Best practices for maintaining the 2007 Office system
39
You use the Office Customization Tool (OCT) to customize an installation of the 2007 Microsoft Office system. 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 on the command line. When you run the OCT, you choose to create a new Setup customization (MSP) file or to open an existing MSP file. If you are creating a new file, the OCT displays a list of the products available on the network installation point. You must select a single product that you want to customize. Note: The 2007 Office release requires version 3.1 or later of Windows Installer on all computers running Office, including the computer you use to run the OCT. For more information about Windows Installer 3.1, including where to obtain it, see Microsoft Knowledge Base article 893803. Using the OCT, you customize Office and save your customizations in a Setup customization MSP file. You place the file in the Updates folder on the network installation point. When you install Office, Setup looks for a Setup customization file in the Updates folder and applies the customizations. The Updates folder can only be used for deploying software patches during an initial installation of 2007 Office system. As an alternative to placing the customization MSP file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully-qualified path to the location of the MSP file. For example, type: setup.exe /adminfile \\server\share\mychanges\custom.msp. Note: If you use a folder other than the Updates folder for your customization files, you can specify the folder's location in the config.xml file by using the SUpdateLocation attribute of the SetupUpdates element. For more information, see Config.xml file in the 2007 Office system. You can also use a Setup customization file to change an existing installation. Because a Setup customization file is an expanded form of a Windows Installer MSP file, you apply the customization file to the user's computer just as you would a software update. The user's existing Office installation is updated with your customizations. For example, if you change the installation states of some features to Not Available and apply the resulting customization file to an existing installation of Office, those features are removed from the user's computer. For more information
40
about customizations to existing installations, see Change users' configurations after installing the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179141.aspx ). Important Every time you save a customization file in the OCT, the tool updates the customization files patch sequencing number with the current computer date and time stamp and generates a new patch globally unique identifier (GUID). The OCT MSP files are applied chronologically according to their time stamp. To illustrate the sequencing behavior, let us assume that you have created the following OCT MSP maintenance patches: Some options in the OCT are applicable only on a new installation of Office. These options are identified in the OCT and in the OCT Help file. For example, you can use the Default installation path option to specify the folder where Office is installed on the user's computer; if a customization file is applied to an existing installation, however, the Default installation path option is ignored (you must uninstall and reinstall Office to change the installation location). Select Save on the File menu to save the Setup customization file before you exit the OCT. The OCT includes four sections: Setup, Features, Additional Content, and Outlook. Each section contains several pages of options. When you change an option on a page, the page name in the left pane changes to bold. If you open an existing Setup customization file, the bold page names indicate where options are customized. The options shown in the following table are available in the OCT.
Section Page
Setup Installation location and organization name Additional network sources Licensing and user interface Remove previous installations Add installations and run programs Office security settings Modify Setup properties Features Modify user settings Set feature installation states Additional content Add files
41
Section
Page
Remove files Add registry entries Remove registry entries Configure shortcuts Outlook Outlook profile Specify Exchange settings Add accounts Remove accounts and export settings Specify send receive groups
Setup
Use the Setup section to specify the following: Default installation location Default organization name Additional network installation sources Product key End user license agreement Display level Previous versions of Office to remove Custom programs to run during installation Security settings Setup properties
Organization nameThis name appears in the About box (Help menu) and on the banner pages of Office applications. The name you specify is used as the default company name for all users whose installation includes this customization file.
43
Display levelSelect the user interface displayed to users during installation. The options are: Full - defaultSetup runs interactively, displaying all of the user interface options and messages. BasicSetup displays the Welcome screen, prompts for the product key and license terms (if needed), and displays a progress bar and completion notice. No other options are presented to the user NoneSetup runs silently and displays no user interface. Important In enterprise deployments, it is recommended that you set Display level to None to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use. Setting Display Level to none assumes that the Suppress modal and Completion notice options are silenced and that the EULA is accepted. Administrators must also make sure that no Office applications are running during an installation of the 2007 Office system. If you set Display level to Basic and select the Suppress modal option, users may be prompted if there are any Office files in use. Setting Display level to None prevents prompting users in such cases. The Suppress modal option does not prevent files in use messages from displaying; only Display level set to None prevents their display. Completion noticeSelect this check box if you want Setup to display a message to the user when installation is complete. Suppress modalSelect this check box if you do not want Setup to display error messages and other dialog boxes that might interrupt the installation. If you set Display level to Full, error messages and other dialog boxes display regardless of the state of this check box. No cancelSelect this check box if you want to disable the cancel button (the X in upper-right corner). This setting only applies when Display level is set to Full or Basic. Note: The Setup customization file (MSP) sets the licensing information only during the initial installation. For information about how to change the product key after installation, see KB article 895456, How to change the product key for Office XP, for Office 2003, and for the 2007 Office system (http://go.microsoft.com/fwlink/?LinkId=103928) on the Microsoft Help and Support Web site. The preceding options are identical to the settings in the Config.xml file shown in the following table.
OCT option Config.xml setting
OCT option
Config.xml setting
Level attribute of the Display element CompletionNotice attribute of the Display element SuppressModal attribute of the Display element
Note: If there are multiple products on the network installation point and you do not specify which product Setup is to install, Setup defaults to full display level when it prompts the user for a product, regardless of how you set Display level in the Setup customization file. You use the /config command-line option to specify which product to install. For more information, see Run Setup for the 2007 Office system on users' computers (http://technet.microsoft.com/en-us/library/cc179093.aspx).
45
Notes Do not add a program that requires the computer to restart, unless it is the last program in the list. If a custom program restarts the computer, the Office installation is completed, but custom programs that appear later in this list do not run. Command-lines entered in the Add Program Entry and Modify Program Entry dialog boxes or by using the Command Element in the Config.xml file are intended to be used only for initial product installs and uninstalls. The Command element commands are processed only during initial installs and uninstalls. If Command element commands are used for customizations after the initial installation, they are ignored.
Run this program after the Office product has been installed. The program runs after the Office installation is complete. This is the recommended option. If the program does not terminate normally or if the program restarts the computer, the Office installation is not affected. However, programs further down the list do not run. Run this program before the Office product has been installed. The program runs before the Office installation starts. If the program does not terminate normally or if it restarts the computer, Office is not installed, and programs further down the list do not run. In the Add/Modify Program Entry dialog box, you can include any of the following standard Windows folders in the path of the executable file.
Folder Description
The folder in which Office is installed Windows folder Windows System32 folder Program Files folder Program Files\Common Files folder Windows Desktop folder Windows Start menu Windows Start\Programs menu
46
Trusted Publishers
Manage the list that identifies trusted sources for digitally signed macros, add-ins, Microsoft ActiveX controls, and other executable code used by Office applications. Office applications share a certificate-based trusted sources list with Internet Explorer. Click Add to add a digital certificate (CER file). Adding the default Microsoft CER files ensures that all add-ins and templates are installed on users' computers with Office applications.
47
Setting
Description
Trusted Locations
Manage the list that identifies locations from which any file can be opened without a check by the Trust Center security feature. Click Add to add a new location, enter the following information, and then click OK: ApplicationSelect the Office application that uses this location. This is supported by Microsoft Office Access 2007, Microsoft Office Excel 2007, Microsoft Office PowerPoint 2007, Microsoft Office Visio 2007, and Microsoft Office Word 2007. PathEnter the path of the trusted location. Enter a fully qualified path with drive letter or UNC path. The path can include environment variables. Subfolders of this location are also trustedSelect this check box to include subfolders as trusted locations. DescriptionEnter text to describe the purpose of the location. To remove a trusted location from this list, select the location and click Remove. Note: When you specify one or more trusted locations here, the Trusted Locations list previously defined on the users computer is cleared and replaced by this list.
Clears the Trusted Locations list on the user's computer. Use this check box to clear the Trusted Locations list on the user's computer without adding new locations.
48
Setting
Description
Set default security levels for add-ins, templates, and Office applications. You can set the following options for each Office application: Allow trusted locations options Allow trusted locations that are not on the user's computer Allow Trusted Locations on the User's machine only (application default) Disable all trusted locations. Only files signed by trusted publishers are trusted Application extensions warnings options Disable all application extensions Require that application extensions are signed by a trusted publisher Require that extensions are signed and silently disable unsigned extensions Enable all installed Application Addins (application default) VBA macro warnings options Disable all VBA macros Disable the Trust Bar warning for unsigned VBA macros (unsigned code is disabled) Disable all VBA macros with notification (application default) No security checks for VBA macros (not recommended, code in all documents can run) Add-ins and templates (Microsoft Office Project 2007 only) Trust all installed add-ins and templates Do not trust installed add-ins and templates Security level (Office Project 2007 only)
49
Setting
Description
Determine whether unsigned, and therefore potentially unsafe, ActiveX controls can initialize using persisted data, that is, data that is saved from one instance of the control to the next. The possible values are: <do not configure>Setup does not modify the setting specified on the user's computer. New applications are installed with the default setting, which is Prompt user to use persisted data. Prompt user to use control defaults The user is warned before an application initiates ActiveX controls that might be unsafe. If the user trusts the source of the document, the control is initialized using its default settings. Prompt user to use persisted data The user is warned before an application initiates ActiveX controls that might be unsafe. If the user trusts the source of the document, the control is initialized using persisted data. Do not promptAll unsigned ActiveX controls run without prompting the user. This setting provides the least protection and is not recommended. Do not prompt and disable all controlsAll unsigned ActiveX controls are disabled without prompting the user.
50
Name Value
The property name. Property names must be all uppercase. The value of the property.
Features
Use the Features section to configure user settings and to customize which Office features are installed.
The setting remains as it is. The setting is modified based on your choices in the dialog box. The setting is disabled. Disabling an option may be different from not configuring the option. See the description of the specific option for more details.
Click Show all settings to display all available user settings. Click Show configured settings only to display only those settings that you have configured. Select the Migrate user settings check box to preserve users' custom settings from a previous version of Office. If you modify user settings and also select this check box, Setup first applies the modified settings and then migrates the user's existing custom settings, overwriting any conflicting settings.
51
Note: When you click Enabled to view the options for a setting and click OK,, Previous Setting, or Next Setting, the status changes to Configured, even if you do not change the setting. Inadvertently configuring the setting with an empty hyperlink, path, or file name can cause errors. If you clicked Enabled and want to ignore your changes or avoid configuring the setting, click Cancel. You can also return a setting to the Not Configured state by double-clicking the setting, selecting Not Configured, and clicking OK.
Setup copies files and writes registry entries and shortcuts associated with the feature to the user's hard disk. The application or feature runs locally. Same as Run from My Computer, except all child features that belong to the feature are also set to this state. Setup leaves components for the feature and its child features in the local installation source until the user attempts to use the feature for the first time, at which time the components are installed. This is also known as an advertised feature. The components for the feature and the child features that belong to this feature are not installed on the computer.
Not Available
52
Hidden
Setup does not display the feature in the feature tree during installation if Setup runs interactively. The symbol [H] is prepended to the feature name to indicate the feature is hidden. The installation state you choose for this feature cannot be changed by the user during installation or in maintenance mode after Office is installed. The symbol [L] is prepended to the feature name to indicate the feature is locked. The feature is returned to its default installation state. This is the same as selecting the feature and clicking the Reset Branch button.
Locked
Reset
If you explicitly set a feature to its default state, the symbol [F] is prepended to the feature name to indicate that the feature will be forced into this state. This is useful if you are creating a Setup customization file to modify an existing Office installation. If you do not change the installation state of a feature, Setup does not change the feature on the user's computer. If you specify a change, including setting the feature to its default state, Setup ensures that the feature is set to that state on the user's computer. When you change the installation state of a feature, Setup might change the installation state of a parent or child feature to match the installation state. For example, if you set a parent feature to Installed on First Use, but set a child feature to Run from My Computer, Setup also changes the state of the parent feature to Run from My Computer. Setup does not display hidden features in the feature tree when users run Setup interactively. The feature is installed according to its defined installation state. Child features that belong to the hidden feature are also hidden. Tip: The best use of the Hide setting is to simplify the feature tree for users. For example, you might hide the Office Tools branch of the feature tree so that users do not have to decide which tools they need. Only the tools that you select are installed.
53
Notes If you set the Hidden option for a feature by using the OCT or the Config.xml file during an initial installation of Office 2007, you cannot unhide that feature in the feature tree by using another Config.xml file or applying a second customization MSP file after the initial installation. This means that the feature is not displayed in the feature tree during installation. The feature remains hidden; the feature will not be displayed in Add or Remove Programs (Change or Remove Programs) in Control Panel under the Add or Remove Features option for Microsoft Office 2007 (or under the Programs and Features option in Windows Vista). However, you can unlock the feature to install and run locally later by using an MSP customization file or a Config.xml file. If you set the Locked option for a feature by using the OCT or the Config.xml during initial installation, that feature can be unlocked and installed locally by using an MSP customization file or a Config.xml file. For example, you can customize the Config.xml file to modify the OptionState element and add the following line to install the feature (Access in this case) on the user's computer and set child features of the feature to the specified state: <OptionState Id=ACCESSFiles State=Local Children=force /> You can also use the OCT to create an MSP customization file to unlock the feature by setting the feature installation state to Run All from My Computer in the Set feature installation states screen. For information about the OptionState element, see Config.xml file in the 2007 Office system. If you set a feature to Not Available and hide the feature in the feature tree, users can still change the setting and install the feature by installing the parent feature or by running Setup in maintenance mode. For example, if you set the Name Smart Tag Plugin feature to Not Available and Hidden, users can still install the feature by setting the parent Smart Tags Plugins feature to Run All from My Computer. If you want to help prevent users from installing hidden features, select the Not Available, Hidden, and Locked installation state. In this case, the feature or application is not installed and is not available in maintenance mode. Users cannot install the feature by changing the state of the parent feature. The only way to reverse the Not Available, Hidden, and Locked installation state after Office is installed is to use the OCT to create a Setup customization file that is configured to change the installation state of the feature. You then apply the customization file to the user's computer.
54
Additional content
Use this section to add or remove custom files, registry entries, and shortcuts during the installation.
Add files
Add files to users' computers when Office is installed. To create a list of files to add to the user's computer during installation, click Add, select the file you want to add to the list, and click Add again. To change the destination path of a file, select the file in the Add custom files list and click Modify. To remove a file from the list, select the file and click Remove. You can use the SHIFT and CTRL keys to select multiple files at one time. When you add files to an Office installation, note the following: Files are copied into the Setup customization file when you save the customization file and exit the OCT. Large files increase the size of the customization file and the amount of time it takes to create the file. If you revise a file that is currently included in the customization file, you must open the customization file with the OCT, remove the file from the Add files list, add the revised version, and save the customization file. If the user removes, repairs, or reinstalls Office, the custom files are removed or reinstalled along with Office. Setup does not reinstall a custom file if the file has changed since installation.
The folder in which Office is installed The local disk drive with the most free space Program Files folder Program Files\Common Files folder Windows folder Windows System32 folder The user's My Documents folder
55
Folder
Description
[AppDataFolder] [NetHoodFolder]
The user's Application Data folder The user's My Network Places folder
Remove files
Remove files from users' computers when Office is installed. To create a list of files to remove from the user's computer during installation, click Add. To modify the path or name of a file, select the file in the Remove files list and click Modify. To remove a file from the list, select the file and click Remove. You can use the SHIFT and CTRL keys to select multiple files at one time. Note: Files listed in the Remove files list are removed from the user's computer before files listed in the Add files list are installed. Therefore, you can delete existing files on a user's computer and replace them with new versions. If the target file on a user's computer is renamed or modified, an added file with the same name does not replace it.
The folder in which Office is installed The local disk drive with the most free space Program Files folder Program Files\Common Files folder Windows folder Windows System32 folder The user's My Documents folder The user's Application Data folder The user's My Network Places folder
56
The supported way to manage registry-based policy keys is to use Group Policy to apply the registry policy settings. Using Group Policy allows you to centrally manage client registry keys; use Group Policy to define configurations once and then rely on the operating system to enforce that state. Administrative Templates files are UNICODE text files that Group Policy uses to describe where registry-based policy settings are stored in the registry. All registry-based policy settings appear and are configured in Group Policy Object Editor under the Administrative Templates nodes. For more information about Group Policy for the 2007 Office system, see Group Policy Overview (http://technet.microsoft.com/en-us/library/cc179176.aspx), Planning for Group Policy for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc178969.aspx), and Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179081.aspx).
57
Root
Select the branch that contains the entries you want to add or modify. Settings are applied once per user (HKEY_CURRENT_USER) or once per computer (HKEY_LOCAL_MACHINE). You cannot add registry entries to the root of HKEY_USERS or HKEY_LOCAL_MACHINE. Select a data type for the registry value. Enter the name of the subkey where the entry is stored. For example, Software\Microsoft\Office\12.0\Common. Select this check box if the registry entry does not contain a value name or value data. Some settings are determined by the presence or absence of the registry entry. Enter a name for the new registry entry. If you include Value data but leave this field blank, the value is assigned the name <Default>. A key can have only one <Default> value name. Enter the data (value) to store in the new registry entry. The data must match the data type.
Value name
Value data
Root Key
Select the branch that contains the entries you want to remove. Enter the full name of the subkey where the entry is stored. For example, Software\Microsoft\Office\12.0\Common. Enter the name of the registry entry that you want to remove. Leave this field blank to remove the entire subkey, including all of its value entries.
Value name
Configure shortcuts
Add shortcuts to files installed with 2007 Office release or files that are already on the user's computer. You can configure shortcuts only when you first install Office on a user's computer. This option is ignored if you apply the Setup customization file to an existing installation. Click Add to add a new shortcut. To modify a shortcut in the list, select the shortcut and click Modify. To remove a shortcut from the list, select the shortcut and click Remove. Shortcuts with Yes in the Installed column are configured during installation. Shortcuts with No in this column are configured if the corresponding product is later installed. Note: If you add a shortcut to a custom application or file, that shortcut is not updated or removed if the user modifies, repairs, reinstalls, or removes Office.
59
Target
Specify the application associated with the shortcut by selecting a predefined application keyword or by entering the name and path of the file to which the shortcut will point. If you select an application keyword, the OCT automatically enters information in the remaining boxes. The names in the list correspond to features that you select on the Set feature installation states page of the OCT, plus any custom files that you add to the installation on the Add files page. If you enter a name and path and the name or path contains a space, you must enclose the entire string in double quotation marks (""). You can add command-line options for the application by using the Arguments field below.
60
Setting
Description
Location
Specify the folder in which the shortcut is created by selecting a predefined folder keyword or entering the name and path to the location of the shortcut. You can specify a subfolder by appending a backslash (\) followed by the subfolder name. For example, to install the Microsoft Office Word 2007 shortcut in the Microsoft Office subfolder in the Programs folder in the Start menu, select [ProgramMenuFolder] and append the subfolder name as follows: [ProgramMenuFolder]\Microsoft Office. You can use the following special folders for Location: [StartMenuFolder]: Windows Start menu. [ProgramMenuFolder]: Windows Start\Programs menu. [StartupFolder]: Startup folder in the Windows Start\Programs menu. [DesktopFolder]: Windows Desktop folder. [INSTALLLOCATION]: The folder in which Office is installed. [FavoritesFolder]: The user's Favorites folder. [AppDataFolder]: The user's Application Data folder. [NetHoodFolder]: The user's My Network Places folder.
Name Start in
Enter any string to specify a name for the shortcut. Enter a path to specify the default starting folder for the application. If you leave this box blank, the default folder is set to the folder where the target file resides. If the path is not valid on a user's computer, the user sees an error message when the user tries to use the shortcut.
61
Setting
Description
Enter optional arguments to pass to the application on the command line. Enter an optional keyboard shortcut for the application or file. The syntax for the shortcut key is: [modifier+]VK_key where modifier is SHIFT, CTRL, ALT, or EXT, and VK_key is a virtual key name (virtual key names, and hexadecimal key codes and descriptions are provided in the following table). The modifier is optional. You may specify more than one, in any order, separated by plus signs (+). If you use a modifier, it must precede the virtual key name. You must enter one virtual key name. Do not use spaces anywhere in the key definition. For example, CTRL+VK_F12 CTRL+SHIFT+VK_A ALT+CTRL+VK_SNAPSHOT Some key combinations, such as CTRL+ALT+VK_DELETE, may be used by the system or other processes. These combinations must not be used to launch the application on the users computer.
Run
Select the type of window in which the application or file should start (Normal window, Minimized, or Maximized). Select a different icon for the shortcut.
Change Icon
The following table lists virtual key names and their corresponding hexadecimal key codes.
Virtual Key Name Key Code (Hex) Description
Description
VK_F1 ... VK_F24 VK_LBUTTON VK_RBUTTON VK_CANCEL VK_MBUTTON VK_BACK VK_CLEAR VK_RETURN VK_PAUSE VK_CAPITAL VK_PRIOR VK_NEXT VK_END VK_HOME VK_LEFT VK_UP VK_RIGHT VK_DOWN VK_SELECT VK_EXECUTE VK_SNAPSHOT VK_INSERT VK_DELETE VK_HELP VK_MULTIPLY VK_ADD VK_SEPARATOR VK_SUBTRACT
70-87 01 02 03 04 08 0C 0D 13 14 21 22 23 24 25 26 27 28 29 2B 2C 2D 2E 2F 6A 6B 6C 6D
Function keys F1-F24 Left mouse button Right mouse button Control-break processing Middle mouse button (threebutton mouse) BACKSPACE key CLEAR key ENTER key PAUSE key CAPS LOCK key PAGE UP key PAGE DOWN key END key HOME key LEFT ARROW key UP ARROW key RIGHT ARROW key DOWN ARROW key SELECT key EXECUTE key PRINT SCREEN key INS key DEL key HELP key Multiply key Add key Separator key Subtract key
63
Description
6E 6F 90 91
Decimal key Divide key NUM LOCK key SCROLL LOCK key
Outlook
Use the Outlook section to customize the default Microsoft Office Outlook 2007 profile and set Office Outlook 2007 and Microsoft Exchange 2007 options.
Outlook Profile
Customize a user's default Outlook profile, which is the set of values in the Windows registry that defines user-specific information. An Outlook profile can contain multiple e-mail accounts. Users can have multiple Outlook profiles, but you can configure only one profile in the Setup customization file.
Setting Description
Use the profile already configured on the users computer, or prompt the user to create a profile the first time Outlook starts. Modify the default profile on the users computer, or define changes to profiles with a name you specify. If no default profile exists or there is no profile by the name that you specify, Outlook creates a profile based on the options you choose in the other Outlook sections of the OCT. Outlook uses the default profile name (custom12.prf) or uses the profile name you specify.
Modify profile
64
Setting
Description
New profile
Create a new profile on the users computer and make it the default profile. Existing profiles are not removed and remain available to users. You must enter a name in the Profile name box. This name appears in the E-mail Accounts dialog box in Outlook. Outlook creates the profile based on the options you choose in the other Outlook sections of the OCT. Import an Outlook profile file (PRF file) to define a new default profile. Selecting this option does not update the OCT with the settings in the PRF file. You can use any profile created for Office Outlook 2007. Enter a name and path for the profile in the Apply the following profile (PRF file) box. If you created a PRF file for a previous version of Outlook, you can import it to Office Outlook 2007 if the profile defines only MAPI services.
Apply PRF
If you install Office on locked-down computers where the users do not have administrative rights, users cannot configure their Outlook profile after Office is installed.
65
Prompt the user for profile and account information the first time Outlook starts, unless a profile already exists on the computer. Configure settings for a new Exchange Server connection or replace the settings in an existing Exchange Server connection. Enter the following information: User NameIdentify the user with a specific value or replaceable parameter. If you specify the default %USERNAME%, Outlook uses the user's exact logon name, rather than prompting the user with possible variations when Outlook starts. Exchange ServerEnter the name of an Exchange server that is likely to be available when users start Outlook. When a user starts Outlook for the first time, Outlook replaces this value with the users correct Exchange server. Provide only a literal server name in this text box; for example, Exch-2-Srvr. Do not include backslashes (\\) or similar syntax. Overwrite existing Exchange settings if an Exchange connection existsSelect this option to replace an existing Exchange Server account in the users profile with this account.
66
By default, Exchange mailboxes are accessible from the Exchange server, rather than being cached on users computers in an Offline Store file (OST file). Create an OST file or use an existing OST file. Users work with a local copy of their Exchange mailbox. If you select Use Cached Exchange Mode, you can configure Cached Exchange Mode for users with the following options: Download only headersDownload copies of headers only from users Exchange mailboxes. Download headers followed by the full itemDownload copies of headers from users Exchange mailboxes and download copies of messages. Download full itemsDownload copies of full messages (headers and message bodies) from users Exchange mailboxes. On slow connections, download only headersWhen a slow network connection is detected, download copies of headers only from users Exchange mailboxes. Download shared non-mail folders Download shared non-mail folders. Download Public Folder Favorites Download the list of Public Folder Favorites.
67
Add Accounts
Include new Outlook e-mail accounts in the users profile. Select the Do not customize Outlook profile and account information option if you do not want to add accounts to a new or modified Outlook profile. Select the Customize additional Outlook profile and account information option to specify new account information in a new or modified Outlook profile. The first time the user starts the application, Outlook creates a profile based on information you specify. Click Add to add a new account to the list. To modify an account in the list, select the account and click Modify. To remove an account from the list, select the account and click Remove. You can also specify the following: Deliver new mail to the following locationWhen you configure an Exchange server or add a Personal Folders file (PST file), select this option to specify a delivery location for new e-mail messages. The default location is the Exchange server, if one is configured; otherwise, the location defaults to the PST file on the users computer. Default e-mail accountSelect the account that is the default e-mail account for users.
Yes No No
Account type
PST Unicode PST Outlook Address Book Personal Address Book LDAP Exchange
File name and path to PST file File name and path to Unicode PST file Existence of account Existence of account Account name Existence of provider
Do not configure settings for Send/Receive groups. Outlook is configured with only the All Accounts group and its default settings. (If users have created additional groups, those groups migrate when users upgrade to Office Outlook 2007.)
69
Option
Description
Configure settings for Send/Receive groups (Exchange accounts and folders only). Click New to create a new group of accounts and folders. Click New to create a new group of accounts and folders. Click Modify to specify or redefine options for a Send/Receive group. Click Rename to change the name of an existing Send/Receive group. Click Remove to remove an existing Send/Receive group.
Send mail items Receive mail items Make folder home pages available offline Synchronize forms
Send mail items from the Outbox when you execute a Send/Receive for this group. Receive mail items when you execute a Send/Receive for this group. Refresh the content in folder home pages when you execute a Send/Receive for this group. Synchronize forms when you execute a Send/Receive for this group.
70
Under Change folder options for this Send/Receive group , select a folder and provide the information shown in the following table.
Option Description
Add this folder to the set of folders that are updated during a Send/Receive for this Send/Receive group, and select from the following options: Download headers onlyDownload only headers for this folder when you update by executing a Send/Receive for this Send/Receive group. Download complete item including attachmentsDownload entire e-mail messages (or other items) for this folder when you update by executing a Send/Receive for this Send/Receive group. Download only headers for items larger thanWhen items are larger than the specified size, download only the header for the item. This setting applies to only this folder when you update by executing a Send/Receive for this Send/Receive group.
72
OptionState Id values
The following table provides the Id values for the applications installed with Office Enterprise 2007.
OptionStateId Application and sub-feature
ACCESSFiles Access_PIA
Microsoft Office Access databases. Primary interoperability assembly that allows Microsoft Office Access programmability with .NET Framework version 1.1 or greater. Barcode Control Help for Microsoft Office Access. Database experts that ask questions about a commonly used item you want to create, and then build the item for you. ActiveX control you can use to create fully programmable calendars in your forms and reports; includes Help files. Database experts that ask questions about a more advanced item you want to create, and then build the item for you.
CalendarControl
DeveloperWizards
73
OptionStateId
AccessTemplatesIntl
Templates are complete Access database applications used to track, store, and report business and personal data. You can store the data within .accdb files or in lists on a Microsoft Windows SharePoint Services Web site. Microsoft Office Excel Primary interoperability assembly that allows Microsoft Office Excel programmability with .NET Framework version 1.1 or greater. Microsoft Office Excel problem-solving tools and utilities. Help for Microsoft Office Excel. Easy-to-use examples for Microsoft Office Excel. Microsoft Office Excel Spreadsheet Templates for expense reports, invoices, timecards, purchase orders, and loan amortization. Microsoft Office Groove Microsoft Office OneNote Typefaces that enable you to type with text that looks like handwriting. Help for Microsoft Office OneNote. Primary interoperability assembly that allows Microsoft Office OneNote programmability with .NET Framework version 1.1 or greater. OneNote integration functionality with other applications. OneNote companion for Windows Mobilepowered devices. Microsoft Office Outlook Primary interoperability assembly that allows Microsoft Office Outlook programmability with .NET Framework version 1.1 or greater. Help for Microsoft Office Outlook.
74
EXCELFiles Excel_PIA
OutlookHelpFiles
OptionStateId
OutlookImportExportFiles
Import from and export to popular e-mail programs, personal information managers, and standard file formats. Outlook Stationery Debugging tool for Visual Basic Scripting Edition. Used to automate Outlook custom forms. Outlook Template Files Outlook Messaging Components Outlook Add-Ins Outlook Mobile Service Microsoft Office PowerPoint Program that can be used to revise a Microsoft Organization Chart OLE object created with previous versions of this program. Primary interoperability assembly that allows Microsoft Office PowerPoint programmability with .NET Framework version 1.1 or greater. Templates and designs that help you create presentations. Help for Microsoft Office PowerPoint. Sounds used for Microsoft Office PowerPoint preset animation effects. Packages the Microsoft Office PowerPoint Viewer and your presentations onto a CD. Microsoft Office Publisher Tools for printing color publications at commercial printing services. Primary interoperability assembly that allows Microsoft Office Publisher programmability with .NET Framework version 1.1 or greater. Tools to change the fonts used throughout your publication. Help for Microsoft Office Publisher.
75
OutlookStationeryFiles OutlookVBScript
PowerPoint_PIA
PublisherFontSchemes PublisherHelpFiles
OptionStateId
Online previews that show PaperDirect designs. Tool that helps you create a particular kind of publication or change an object in a publication. Microsoft Office InterConnect Help for Microsoft Office InterConnect. Microsoft ASP.NET Development Server Microsoft Office Word Primary interoperability assembly that allows Microsoft Office Word programmability with .NET Framework version 1.1 or greater. Files that you can use with the Word Bibliography feature. Provides page borders that can be used to enhance documents. Microsoft Word Calligraphy Add-in Microsoft Word Envelope Wizard Add-in Microsoft Word Genko Add-in Help for Microsoft Office Word. Word Quick Formats theme files. Microsoft Office Word wizards and templates. Microsoft Word Table Wizard Add-in Microsoft Office InfoPath Primary interoperability assembly that allows Microsoft Office InfoPath programmability with .NET Framework version 1.1 or greater. Help for Microsoft Office InfoPath. InfoPath NoShip Automation Support Tool for creating installable form templates Form templates that you can customize to suit your requirements or use immediately. Shared files for use with Microsoft Office.
WordBibliographyFiles WORDBordersFiles WordCalligly WordEnvelopWizard WordGenko WORDHelpFiles WordQuickFormatsFiles WORDDocumentTemplates WordTableWizard XDOCSFiles XDocs_PIA
76
OptionStateId
AceRepl
Installs the Microsoft Office Access Database Replication Conflict Manager, which you can use to resolve conflicts between replicated databases. Collection of popular clip art that can be used to enhance Microsoft Office documents. Microsoft Office IME (Chinese Traditional) Microsoft Office IME (Japanese) Microsoft Office IME (Korean) Microsoft Office Pinyin IME File converters and graphics filters. Files for international support. Set of coordinated design elements, including colors, fonts, fills, and effects that can be used within Microsoft Office documents. Digital certificate for signing a Visual Basic for Applications project. Allows you to avoid unnecessary security warnings. Fonts for International languages. Start menu shortcuts for creating and opening Microsoft Office documents. Tools for proofreading Office documents. Extra fonts for greater design flexibility. ActiveX control that allows Microsoft Office clip art and templates to be downloaded from Microsoft Office Online and to be opened automatically in the associated programs. Set of coordinated design elements, including body and heading styles, background images, bullets, and horizontal lines. Components to support creating, editing and executing VBA macros in Office applications. Applications and support files for use with Microsoft Office.
77
OfficeDigitalSFiles
THEMESFiles
VBAFiles TOOLSFiles
OptionStateId
DocServicesFiles
Document Update Utility that keeps documents on your computer up-to-date with copies of those documents in document workspaces. Inserts mathematical symbols and equations into documents. Primary interoperability assembly that allows Microsoft Forms 2.0 programmability with .NET Framework version 1.1 or greater. Creates charts from Microsoft Office Word, PowerPoint, and Access data. HTML source editor for HTML authoring of Office documents. Troubleshooting tool that gathers system and program configuration information. Enables you to easily scan, perform optical character recognition (OCR), search through, extract text from, and view image documents. Provides intelligent recognition of data types within Microsoft Office Excel and Word, and useful actions for working with the data types. Microsoft Office Picture Manager is installed with the selected options. Document publishing tools and collaboration tools for use with SharePoint Services or FrontPage Server Extensions, and an Office List component for use with Windows SharePoint Services. Provides direct database connectivity to analyze data in Microsoft Office Excel. Enables you to use the Research tool and its collection of information services from Windows Internet Explorer. Sets language options for all Office programs. Primary interoperability assembly that allows smart tag programmability with .NET Framework version 1.1 or greater.
78
EquationEditorFiles Forms_PIA
MSTagPluginsFiles
OISFiles OSESupp
QueryFiles RefIEBarFiles
SetLanguageFiles SmartTag_PIA
OptionStateId
WebDriveFiles
The following tables provide OptionState Id values for Microsoft Office Project and SharePoint Designer.
OptionStateId Application and sub-feature
PROJECTFiles Project_PIA
Microsoft Office Project is installed with only the selected options. Primary interoperability assembly that allows Microsoft Office Project programmability with .NET Framework version 1.1 or greater. Microsoft Office Project end-user documentation and language reference, including Microsoft Visual Basic(R), ActiveX Data Objects (ADO), and Data Access Objects (DAO). Enables migration of projects and other Project Server data from Microsoft Office Project Server 2003 to Microsoft Office Project Server 2007. Note: This tool is intended for Microsoft Office Project Server Administrators only.
ProjectHelpFiles
PROJECTP12Upgrade
ProjectStdHelpFiles
Microsoft Office Project end-user documentation and language reference, including Microsoft Visual Basic(R), ActiveX Data Objects (ADO), and Data Access Objects (DAO). Collection of templates that includes Project templates to create new projects and Microsoft Office Excel templates to use with the Visual Reports feature. Resource substitution wizard is used to automatically staff enterprise projects according to outline codes associated with the task's project, outline codes associated with resources, and the availability of those resources.
79
ProjectTemplates
ProjectWebProj
OptionStateId
Microsoft Office SharePoint Designer Help for Microsoft Office SharePoint Designer. Coordinated design elements, including body and heading styles, background images, bullets, and horizontal lines. Additional coordinated design elements, including body and heading styles, background images, bullets, and horizontal lines. Primary interoperability assembly that allows Microsoft Office SharePoint Designer programmability with .NET Framework version 1.1 or greater.
WAC_ThemesAdditional_SPD
WAC_PIA_SPD
See Also Use Group Policy Software Installation to deploy the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179214.aspx) Config.xml file in the 2007 Office system
80
II File format reference Overview of the XML file formats in the 2007 Office system
The 2007 Microsoft Office system introduces new XML file formats that are robust and based on open standards. The new XML file formats enable rapid creation of documents from disparate data sources, accelerating document assembly, data mining, and content reuse. The formats simplify exchanging data between applications in the 2007 Office system and enterprise business systems. You can create a document in the new XML formats with any standard tool and technologythe 2007 Office system is not required. Users can improve productivity by publishing, searching, and reusing information more quickly and accurately in the environment they choose. The new XML formats are based on industry-standard XML and ZIP technologies, support full integration by any technology provider, and are available via a royalty-free license. The XML file format specification will be published and made available under the same royalty-free license that exists for the Microsoft Office 2003 Reference Schemas, and is openly offered and available for broad industry use.
Relationship part. A type of part that generally points to other parts to define the relational hierarchy of the part structure. ZIP package. Bundles parts into a single file.
Start part
The start part, an XML part that is a relationship part and could be considered the highest order part, determines the file type. For example, if the name of the core container is WordDoc, the file name extension is .docx.
XML parts
When an Office XML formatted file is saved in the 2007 Office system, the file is divided into a set of logical parts that describes the entire file. For Office Word 2007, dividing the file into these parts enables the file to be easily queried or modified outside of the original Office application. For example, it is easier for a developer to remove document properties from a file because the properties are placed in a single part, and the part can be deleted from within the document container by deleting the part. With WordprocessingML (provided as an optional XML file format in Microsoft Office 2003), removing comments involved parsing the entire file to find and remove the XML representing the contents of the comment. With the new file format, feature-related data is divided into parts. Comments, links, headers, footers, and other data are in separate parts that can be removed. You do not need to parse the entire Word document.
Non-XML parts
Non-XML parts are generally images and OLE objects. Any file type that uses binary content or does not use XML is identified as non-XML. A non-XML part is most commonly a file attached to or embedded within a document. The Office Word 2007 XML format schema documentation explains the literal relationship and schema hierarchy used by Word for files of this type.
Relationship part
A relationship part is an XML part that points to other parts and defines the relational hierarchy of the parts. Most high-level XML parts are relationship parts. XML parts that contain data and do not point to other parts are also referred to as primitives, and usually have a content type of application/xml.
82
ZIP package
Using a ZIP package provides the following benefits in all applications: Open standard. The ZIP compression algorithm is a well-defined open standard. Reduced file size. Files are generally smaller than an equivalent binary file. On average, Office Word 2007 files are 75% smaller than their binary counterparts, depending on the number of images. Increased robustness. Files are more robust and less sensitive to potential errors in the file. Previous files required the file to be completely intact to function correctly. Although use of a ZIP package means the file is binary, the WinFX application programmer interface (API) set provides native support for the package format in the System.IO.Packaging name space. This enables developers to create tools that process the format and work directly against the logical model (the parts) without having to consider expansion or compression of the package.
83
Office Word 2007 XML document Office Word 2007 XML macro-enabled document
.docx
The default Office Word 2007 file format. Cannot store VBA macro code. Uses the same basic XML format as the Office Word 2007 XML document format, but can store VBA macro code. This file type is created when VBA macro code is present in the file. The default format for a Word template. Created when document styles and formatting are saved. Cannot store VBA macro code.
.docm
.dotx
84
Application
Extension
Description
.dotm
Stores macro code for use with other Word documents. Does not always contain macro code, but is configured to support macro code storage. Word documents created from a macro-enabled template do not inherit the VBAProject part of the template. By default, documents are saved as .docx files even when they are created from a Office Word 2007 XML macro-enabled template. The default Office Excel 2007 file format. Cannot store VBA macro code or Microsoft Excel 4.0 macro sheets (.xlm files in Excel 4.0). Uses the same basic XML format as the Office Excel 2007 XML Workbook, but can store VBA macro code. Users saving an Office Excel 2007 XML workbook that has VBA code or Excel 4.0 macro sheets (.xlm files in Excel 4.0) are prompted to use this file format.
.xlsx
.xlsm
85
Application
Extension
Description
.xltx
The default file format for an Excel template. Cannot store VBA macro code or Excel 4.0 macro sheets (.xlm files in Excel 4.0). Can contain a VBAProject part or Excel 4.0 macro sheets (.xlm files in Excel 4.0). Workbooks created from this template inherit the VBAProject part or Excel 4.0 macro sheets that exist in the template. A fast load-and-save file format for users who need the fastest way possible to load a data file. Supports the use of VBA projects, Excel 4.0 macro sheets, and all the new features used in Office Excel 2007. However, this is not an XML file format, and therefore is not optimal for accessing and manipulating content without the use of Office Excel 2007 and the object model. Also, it does not use ZIP compression and is subject to the same security concerns as the previous Excel BIFF8 binary file format.
.xltm
.xlsb
86
Application
Extension
Description
.xlam
A supplemental program designed to run additional code. Excel add-ins use the new XML file format to store data. Excel XML add-ins support the use of VBA projects and Excel 4.0 macro sheets. The default PowerPoint XML format. Cannot contain a VBAProject part (the part that stores VBA macro code) or Action settings. The same basic XML format as the Office PowerPoint 2007 XML presentation format, but can store VBA macro code. Users saving a Office PowerPoint 2007 XML presentation file that contains VBA macro code are prompted to use this file type. An XML-based PowerPoint template. Created when a presentation does not have a VBAProject and does not use Action settings.
.pptm
.potx
87
Application
Extension
Description
.potm
Users saving a Office PowerPoint 2007 XML template that contains VBA macro code are prompted to use this file type. Presentations created from this template do not inherit the VBA project or Action settings. An XML-based PowerPoint presentation designed to be executed as a supplemental program. All PowerPoint add-ins are macroenabled. An XML-based PowerPoint autorunning slide show. Cannot contain a VBAProject part. An XML-based PowerPoint slide show file that contains a VBAProject part. Created when the autorunning slide show includes VBA macro code.
.ppam
.ppsx
.ppsm
88
The 2007 Microsoft Office system contains a new feature, compatibility mode, to offset compatibility issues between the 2007 Office system and previous versions of Office. Compatibility mode ensures that content created in the 2007 Office system can be converted or downgraded to a form that can be used by previous versions of Office. For example, when a user selects "Insert SmartArt" in compatibility mode in Microsoft Office Word 2007, the diagramming tool from Office 2003 appears. This ensures that the diagram added to the file can be fully edited in Word 2003. When not in compatibility mode, the new SmartArt diagramming tool for the 2007 Office system appears, and the object that is created will not be fully editable in Word 2003. Compatibility mode helps users collaborate with those using previous versions of Word, Excel, and PowerPoint. A file created in previous versions of Office, such as .doc, .xls, and .ppt, are fully functional in compatibility mode in the 2007 Office system. Compatibility mode ensures that the 2007 Office system can open and save files in from previous versions of Office without converting them to the new file formats in the 2007 Office system. In compatibility mode, some features of the 2007 Office system are limited in order to be consistent with the features in previous versions of Office. Compatibility mode is documentspecific, and is automatically enabled when files from Office 2003 and earlier are edited in the 2007 Office system. Compatibility mode is available in Office Word 2007, Microsoft Office Excel 2007, and Microsoft Office PowerPoint 2007. Each program provides visual cues to alert users that they are in compatibility mode for a particular file. For example, the words "Compatibility Mode" are added to the programs title bar. Enhanced ScreenTips provide additional detail for specific features that are enabled in compatibility mode. Users can also convert a document from compatibility mode to full functionality. By selecting Convert from the Office Start Button, users can convert the document to the 2007 Office system, and add content using the new features available in the 2007 Office system.
89
Excel
In Office Excel 2007, compatibility mode prevents new features in Office Excel 2007 from being saved to a file that will be edited in a previous version of Excel. For example, previous versions of Excel support a maximum of 65,536 rows in a worksheet. Office Excel 2007 removes this limitation. Upon opening a worksheet with 100,000 rows of data, previous versions of Excel must truncate rows beyond 65,536. To minimize disruption to users who are collaborating between different versions of Excel, new features like this in Office Excel 2007 are limited in compatibility mode. In this case, while working in compatibility mode, users cannot add more than 65,536 rows to an Excel workbook. While working in Office Excel 2007, if a user attempts to paste content that is not supported by previous versions (for example, a chart or diagram created in Office Excel 2007), compatibility mode downgrades the content to a form that is recognizable by previous versions. If edited in a previous version, the image is flattened into a single object, instead of multiple objects. In addition, some colors might render differently in previous versions.
PowerPoint
In Office PowerPoint 2007, compatibility mode disables functionality that cannot be rendered with an adequate level of visual fidelity or editability in previous versions of PowerPoint. This ensures a consistent presentation experience across different versions of PowerPoint. Office PowerPoint 2007 can add many new effects and attributes to content that are not supported in previous releases. For example, Office PowerPoint 2007 provides text effects for shadows, reflections, bevels, and other effects. Because previous versions of PowerPoint cannot render this content, Office PowerPoint 2007 represents these effects as images in compatibility mode. If edited in a previous version, the image is flattened into a single object, instead of multiple objects. In addition, some colors might render differently in previous versions. With the new feature refresh technology in 2007 Office system, even though these effects are saved as images in compatibility mode, they are once again treated as the original text effects when reopened in Office PowerPoint 2007. For more information, see Feature Refresh later in this topic.
90
Word
In Office Word 2007, compatibility mode primarily ensures visual fidelity between different versions. Some features in Office Word 2007 are grayed out and not available in compatibility mode, to prevent the addition of content that is not compatible with previous versions of Word. While working in Office Word 2007, if a user attempts to paste content that is not supported by previous versions (for example, a chart, diagram, equation, or citation created in Office Word 2007), compatibility mode downgrades the content to a form that is recognizable by previous versions. If edited in a previous version, the image is flattened into a single object, instead of multiple objects. In addition, some colors might render differently in previous versions.
Open a file saved in file formats used by previous versions. Convert a file from 2007 Office system to a previous version using Save As.
Set the application X default to save using the file formats from previous versions of Office. Create a new document based on a .dot template (available in previous versions of Office).
91
Compatibility checker
Office Word 2007, Office Excel 2007, and Office PowerPoint 2007 contain a compatibility checker to detect any features that are not recognized by previous versions. This helps users who need to share documents between different versions of Office. For example, if a user attempts to save an Office Excel 2007 file that contains 800,000 rows to the .xls format, the compatibility checker will prompt the user with a warning that data will be lost. The compatibility checker displays a list of any content in the document that may not appear the same or be fully editable when the current new file format (for example, .pptx) is saved to a previous file (in this case, .ppt). The compatibility checker is launched either when a user downgrades a file by saving one of the new file formats to a previous file format, or when the user clicks Compatibility Checker on the Office Button Finish menu.
Feature refresh
The feature refresh technology in the 2007 Office system provides the next step in compatibility between the 2007 Office system and previous versions of Office. It allows features that have been altered by compatibility mode to be made available again when a file is re-opened in Office Word 2007, Office Excel 2007, or Office PowerPoint 2007. For example, a chart that was created in Office Word 2007 and that is altered by compatibility mode to be an uneditable image in a previous version of Word will be fully editable again when re-opened in Office Word 2007. Important: Not all content can be refreshed in the 2007 Office system after it has been downgraded to a previous version. For a list of features that are affected by compatibility mode, with notes on those that can be refreshed when re-opened in the 2007 Office system, see Features impacted by compatibility mode, below.
92
Word 2007
Name Description Compatibility Mode Behavior
Math
Equations are represented as non-editable images. These images are refreshed when the document is converted. The Equations UI is disabled in compatibility mode. Themes are permanently converted to styles. The Themes UI is disabled in compatibility mode. Themes are permanently converted to styles. The Themes UI is disabled in compatibility mode. Themes are permanently converted to styles. The Themes UI is disabled in compatibility mode. Themes are permanently converted to styles. The Themes UI is disabled in compatibility mode. Content controls are permanently converted to static text. The Content Controls UI is disabled in compatibility mode. Tracked moves are permanently converted to "Insert" and "Delete." Major and minor fonts are permanently converted to static formatting.
Themes
Content Controls
Tracked Moves
Tracked moves are new to Office Word 2007. Major/minor fonts are new to Office Word 2007.
Major/Minor Fonts
93
Name
Description
The ability to set the position of Relative positioning of text a text box relative to some part boxes is permanently converted of a document. Relative text to absolute positioning. boxes are new to Office Word 2007. Margin tabs are new to Office Word 2007. New to Office Word 2007. New to Office Word 2007. New to Office Word 2007.. Office Art engine is improved upon in the 2007 Office system. Margin tabs are permanently converted to absolutely defined tabs. Bibiliographies are permanently converted to static text. Citations are permanently converted to static text. Placeholder text is permanently converted to static text. All Office Art 2007 objects are converted to Office 972003 objects. These objects are refreshed when the document is converted. When a user selects SmartArt in Office Word 2007, the Diagram Gallery from Word 2003 appears. Diagrams in the 2007 Office system are converted to noneditable images. When the document is converted, these images are refreshed to 2007 Office system again. When a user selects SmartArt in Office Word 2007, the Diagram Gallery from Word 2003 appears.
Margin Tabs
SmartArt Diagram
94
Name
Description
New to the Open XML Formats, custom-defined XML information can be stored as a separate component within the Open XML Formats, to help organizations include content from their own data sources, using their own languages. Vertical text box alignment of center or bottom are new to Office Word 2007. Charts can now exist as native objects in Office Word 2007.
The XML data store is removed during conversion, and XML data and content within XML bindings are permanently converted to text.
Vertical text box alignment of center or bottom is permanently converted to top vertical text box alignment. Office charts are converted to Excel OLE objects. These objects are refreshed when the document is converted back to 2007 full functionality mode. When a user selects Charts in Office Word 2007, the Diagram Gallery from Word 2003 appears.
Office Charts
ActiveX
Active X controls can be added Disabled ActiveX controls are to Word documents to deliver converted to their image enhanced functionality. representation when saved to a downlevel file type or opened in a downlevel application verison through the converter.
95
Excel 2007
Name Description Compatibility Mode Behavior
Excel 20002003 allows up to 65,472 cross-sheet array formulas. Excel 2007 removes this limitation. Excel 20002003 allows up to 1800 bytes in BIFF8 internal representation. Excel 2007 allows up to 16,384 bytes. Excel 20002003 allows up to 7 levels of nesting. Excel 2007 allows up to 255 levels of nesting. Excel 20002003 allows up to 30 arguments. Excel 2007 allows up to 255 arguments. Excel 20002003 allows up to 40 operands. Excel 2007 allows up to 1024 operands. Excel 20002003 hides levels all the way up to the top. Excel 2007 allows hiding just an intermediate level.
Formulas over the Excel 20002003 limit return #VALUE. Formulas over the Excel 20002003 limit return #VALUE. Formulas over the Excel 20002003 limit return #VALUE. Formulas over the Excel 20002003 limit return #VALUE. Formulas over the Excel 20002003 limit return #VALUE. Pivot saved as static data.
Cell with a formula that exceeds limit for arguments in a function Cell formula contains more than 40 operands. PivotTable with only intermediate levels hidden
Workbook contains cells with data outside 256 x 65,536. Cell with more than 3 conditional formats Cell with a data bar, color scale, or icon set condition type.
Excel 20002003 grid size is 256 x 65,536. Excel 2007 grid size is 18,278 x 1,048,576. Excel 20002003 allows 3 conditions per cell. Excel 2007 allows 20 conditions per cell. Excel 20002003 has no data bar, color scale, or icon set conditions. Excel 2007 has these conditions.
Data outside the the Excel 20002003 grid size is truncated. Conditions exceeding the Excel 20002003 limit are not displayed. Unsupported conditions are not displayed.
96
Name
Description
Excel 20002003 always stops Stop after first true condition. after a condition is true. Excel 2007 does not stop when StopIfTrue = False. Excel 20002003 does not allow cross-sheet cell references in conditional expressions. Excel 2007 allows this. Excel 20002003 has no option to perform multiple calculations per Pivot block. Excel 2007 offers these options. Excel 20002003 allows up to 4050 unique cell formats/styles. Excel 2007 allows up to 64k unique cell formats/styles. Condition is not evaluated.
Workbook contains more than 4050 unique cell formats. Note: This check looks at the whole workbook, not just the formats used in the 256 x 65,536 range. List contains a Total Row with a custom formula.
Unique formats exceeding the Excel 20002003 limit are not persisted.
Excel 20002003 Total Rows must contain one of a list of predefined functions. Excel 2007 Total Rows allow userdefined formulas.
Excel 20002003 allows up to Pivot saved as static data. 32,500 unique items in a Pivot field. Excel 2007 increases this limit to 1,048,576. Excel 20002003 allows item string length (MDX name in OLAP) up to 255 characters. Excel 2007 increases this limit to 32,767. Excel 20002003 refedits allow up to 255 characters. Excel 2007 refedits allow between 2k and 8k characters. Pivot saved as static data.
In some cases, refedit works but user cannot see whole formula. In other cases, the feature does not work.
97
Name
Description
Excel 20002003 does not allow column references (returns #NUM). Excel 2007 allows column references. Excel 20002003 only supports 3 sort levels. Excel 2007 supports 64 sort levels. Excel 20002003 only supports one custom list filter on the first column only. Excel 2007 supports many custom list sorts on any column. Excel 20002003 only allows sorting on values. Excel 2007 also allows sorting on cell background color, cell foreground color, and cell icons. Excel 20002003 only supports value filters. Excel 2007 supports dynamic filters for items such as today and last month. Excel 20002003 only supports value filters. Excel 2007 supports filtering by cell background color, cell foreground color, and cell icon. Excel 20002003 only supports filtering by 2 conditions. Excel 2007 allows the user to check multiple items from a list view control, which creates multiple sort conditions.
Sort state with more than 3 sort levels User has a custom list sort.
Filters will not be viewable, but the filtered rows will remain hidden.
Filters will not be viewable, but the filtered rows will remain hidden.
Filters will not be viewable, but the filtered rows will remain hidden.
98
PowerPoint
Name Description Compatibility Mode Behavior
Converted to a picture. Since these features were not available in previous versions, any text containing this type of formatting is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for strikerthrough, double strikethrough, and text underline is disabled in compatibility mode. Converted to a picture. Since this feature was not available in previous versions, any text containing this type of formatting is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode. Character spacing on text will not display in Office 2003.
Text Warping
The ability to morph the shape of a character or a run of text to a specified shape.
Character Spacing
The ability to either condense or expand the space that appears between consecutive characters.
99
Name
Description
Columns
The ability to have text reflow into multiple columns within a single text body.
Converted to a picture. Since this feature was not available in previous versions, any text organized into columns is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for columns is disabled in compatibility mode. New soft shadows will be converted into an equivalent hard-edged shadow when the presentation is opened in a prior release of PowerPoint. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode.
Shadow
The ability to add a dropshadow effect to a shape or object in the presentation. Soft shadows create the illusion of depth.
See Bevel Gallery. The ability to add depth to a shape using 3D Effects. Converted to a picture. The Bevel Gallery is introduced into PowerPoint for the first time with this release. Any shapes using a Bevel Effect are converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode.
100
Name
Description
3D Rotation
The ability to add a perspective effect that makes an object appear to be tilted or rotated in 3-dimensional space.
Converted to a picture. Since this feature was not available in previous versions, any object using this type of formatting is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode. Converted to a picture. Since this feature was not available in previous versions, any object using this type of formatting is converted into a static picture when opened in a previous version. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode. Converted to a picture. Since this feature was not available in previous versions, any object using this type of formatting is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode.
Soft Edges
The ability to add a soft edges effect that gradually fades the boundaries of a graphic outward. This is a new effect in the 2007 Office system.
Glow
The ability to add a glow effect that adds a vibrant colored edge to graphics. This is a new effect in the 2007 Office system.
101
Name
Description
Reflection
The ability to add a mirror Converted to a picture. Since reflection of an object. This is a this feature was not available in new effect in Office 2007. previous versions, any object using this type of formatting is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode. The ability to lay out characters in a languagespecific configuration, such as vertically stacked. Converted to a picture. Since this feature was not available in previous versions, any text using this type of formatting is converted into a static picture when opened in a prior release. This ensures that the file looks the same in both releases, so that no intended meaning is lost in conversion. The UI for shape styles, 3D effects, and text effects is disabled in compatibility mode.
Text Direction
102
103
File Search
Description: File search is removed from the user interface in several programs. Users no longer click File Search on the File menu to open the File Search task pane. Users do not access this feature from the Tools menu in the File Open dialog box. Users now use the search capability in Windows XP, or use MSN Desktop Search. Reason for change: This feature was rarely used. Native operating system search functionality and MSN Desktop Search provide more functionality. The search feature in Microsoft Office Outlook 2007 and in the 2007 Office system enables users to search e-mail more quickly than the File Search feature. Migration path: In 2007 Office system, users can search more quickly in Office Outlook 2007 as a replacement for searching e-mail, and can use the operating systems native search functionality or MSN Desktop Search to find other types of files.
Korean converters
Description: Korean converters, including GS32.CNV, HANA32.CNV, and TGWP32.CNF, are removed. Reason for change: This was a low-use or no-use feature.
104
MSI-only install
Description: It is impossible to install 2007 Office system without running setup.exe. More than just the .msi file is required to complete an installation. For more information, see Evaluating the new Setup architecture (http://technet.microsoft.com/en-us/library/cc179189.aspx).
OWC11
Description: OWC11 is removed from the 2007 Office system and now ships only with Microsoft Office Project 2007. The DataFinder functionality in OWC11 is also removed. This affects solutions that use the spreadsheet, chart, pivot table, and data source control functionality of OWC11 in a Web page or client program that requires installation of this ActiveX control on the user's computer. The user experience varies depending upon the host container of the OWC11 ActiveX control. For Web pages, users might see a broken icon or a notification that OWC is required. For client programs, users might receive a runtime error or other notification. In these situations, users download OWC11 from the Microsoft Download Center. The notification message generated by Office programs provides a link to the download location for OWC11. Neither Microsoft Office Excel 2007 nor SharePoint Designer 2007 now generate Web pages that use OWC. Reason for change: New technologies such as Windows SharePoint Services 3.0 with Excel server side capabilities and the new charting component in the 2007 Office system replace some features of OWC11.
105
Migration path: When the 2007 Office system is installed, previous versions of Office are removed by default. This prevents software conflicts and ensures that you have the latest versions of shared components. As a result, OWC installed with previous versions of Office is removed. If you have documents or solutions that depend on OWC, these solutions do not function properly if the correct version of OWC is not installed on the client machine. There are three primary courses of action: 1. Install the correct version of OWC on the appropriate client computers. The installation can be performed in the following ways: If there is wide usage of OWC throughout your corporation, OWC can be chained into the installation of the 2007 Office system using the Office Customization Tool. You can obtain the necessary version of OWC (OWC10 or OWC11) from the Microsoft Download Center at Office XP Tool: Web Components (for OWC10) or Office 2003 Add-in: Office Web Components (for OWC11). If there is small or localized use of OWC in your corporation, you could allow users to download OWC from the Microsoft Download Center on an as-needed basis. If OWC is not found on the client computer when the Web page displays, pages authored with Excel 2003, FrontPage 2003, and Access 2003 that require OWC display a link to the OWC download location. For custom solutions that use OWC, follow this same process of checking for OWC and displaying a download link if OWC is not installed. 2. Migrate OWC-based documents and solutions to a comparable technology, such as Excel Services. This option largely depends on the importance of the documents or solutions, the length of time they will be in service, and the degree to which OWC solves your business issues. 3. Discontinue the use of documents or solutions if they are no longer needed.
Proofing tools
Description: The Spelling Options user interface is changed in all programs. The object model also contains changes. Reason for change: Users now see the same Spelling Options user interface in all Office programs, instead of a different user interface in each program.
106
Setup.exe: Catalyst
Description: Setup.exe supports fully qualified paths for chained executable files. Reason for change: This change makes chaining more robust. Migration path: Replace all relative paths with fully qualified paths.
Ststpkpl.exe
Description: Ststpkpl.exe is no longer downloaded for the 2007 Office system. The following functionalities are no longer available: PivotView Web Part, Spreadsheet Web Part, QuickQuote Web Part, WebClipper Web Part, Great Plains DSP, Great Plains solutions, SQL DSP, InfoPath templates, Rich Issues List. Reason for change: OWC, which represents the main set of Web parts in this download, is deprecated. In addition, the Great Plains solutions are superseded by offerings from Microsoft Business Solutions. Migration path: There is no migration path for OWC. For Great Plains solutions, use the Microsoft Business Solutions Center. For the QuickQuote Web Part, use the MSNBC quote Web part.
107
Changes in Charting
This article lists the changes in Charting from Microsoft Office 2003 to 2007 Microsoft Office system.
Charting axes
Description: The default tick-mark position is outside the axis. In previous versions, it was inside the axis for East Asian languages, but outside the axis for all other languages. Reason for change: The new behavior is more consistent, and matches what East Asian customers prefer. Migration path: Set the tick-mark position to inside the axis.
Chart features
Description: Some chart features have been removed from 2007 Microsoft Office system. Charts that used these features look different in 2007 Office system. Code that accesses the object model properties might not work in the same way. The removed features include: 2-D walls and gridlines on 3-D charts, Excel-specific shape properties on shapes in charts, and locked form controls that do not size with charts. Reason for change: This change results in charts that are more robust for the future addition of features.
Copy/paste
Description: If a user copies a chart from Microsoft Office PowerPoint 2007 or Microsoft Office Word 2007 and pastes the chart into a program other than Office PowerPoint 2007, Office Word 2007, or Microsoft Office Excel 2007, the chart is pasted as a picture. If the chart is copied from Office Excel 2007, this is not an issue. Reason for change: Charts are now integrated with OfficeArt, and must be hosted in an OfficeArt program. With Office Excel 2007, users can copy and paste the entire file from Office Excel 2007 into another program. This is not possible with Office PowerPoint 2007 and Office Word 2007. Migration path: Paste the chart into Office Excel 2007, and copy the chart from Office Excel 2007 into the other program.
108
Excel 2007
Description: Charting in 2007 Office system requires Office Excel 2007 to be advertised. If Office Excel 2007 is not advertised, the Insert Chart button is disabled. The Show Data and Data Source buttons in the Chart contextual experience are disabled. Users who do not have Office Excel 2007 cannot create a new chart or edit data in an existing chart. In most cases, users can change formatting on existing charts. Microsoft Graph still exists, but the entry points are removed. Reason for change: Integrating charting by using Office Excel 2007 provides a consistent charting experience across 2007 Office system. Integrated charting is a native feature of Office PowerPoint 2007 and Office Word 2007, but the data for the chart resides in Office Excel 2007. Migration path: Charts opened in Office PowerPoint 2007 or Office Word 2007 with Office Excel 2007 installed are automatically upgraded. If Office Excel 2007 is not installed, the charts are not upgraded. To enable charting, switch from stand-alone Office PowerPoint 2007 or Office Word 2007 to 2007 Office system.
109
Integration
Description: When a 3-D chart is ungrouped, the entire plot area continues to exist as a single group. Reason for change: Charts are now drawn in realistic 3-D, and it is not possible to ungroup a realistic 3-D drawing into a set of 2-D shapes. Migration path: Users often ungrouped charts to apply features that existed in OfficeArt, but not in Chart. Many of those features can now be applied directly in Chart. Alternatively, you can use Microsoft Graph.
Interaction
Description: The user interface for charts is redesigned. Reason for change: Charts are integrated with OfficeArt, so as much as possible the user interface is consistent with OfficeArt. The user interface for Office Excel 2007, Office PowerPoint 2007, and Office Word 2007 changed, and charts changed to match the user interface. Migration path: See Help for mapping of previous topics to new topics. You may need to rewrite macros that used Dialog.Show for some chart dialogs.
Chart selection
Description: Charts no longer automatically come to the front when they are selected. Reason for change: This new behavior is consistent with the rest of OfficeArt.
110
Resizing
Description: Resizing a chart that contains shapes works differently than it did in Office 2003. Reason for change: Charts are now integrated with OfficeArt, and it was not possible to reimplement the Office 2003 behavior for charts.
Legend
Description: Series within charts that have not been assigned names show the series names in the legend as "Series1," "Series2," and so forth. Reason for change: Charts used different texts for series names in varying places on the chart and in the user interface. These texts are now consistent. Migration path: Set the names of series if they appear in the legend or elsewhere on the chart.
Macros: Chart.Pictures
Description: Macros using the Chart.Pictures collection might not run. Reason for change: This feature is redundant with the Chart.Shapes collection. Migration path: Use the Chart.Shapes collection instead.
Macros: XLM
Description: XLM macros are no longer supported. Reason for change: XLM is deprecated, but not yet removed. Migration path: Rewrite XLM macros in VBA.
111
112
Visual: scales
Description: Charts that have the scale on the value (y) axis set to Automatic might have changed scales in 2007 Office system. Reason for change: Charts now use OfficeArt text, and information about text size and wrapping is used to identify the axis scaling. Migration path: Set the scaling to a fixed value.
113
Migration path: Charts are drawn in 2007 Office system to match Office 2003 versions as closely as possible. Macros that rely on chart layout being precise to the pixel might produce slightly different results than before.
Import RunCommand
Description: The DoCmd.RunCommand acCmdImport object model call and the Import RunCommand macro are no longer supported. An error message appears when this object model call or the macro RunCommand call is made. They have been replaced by more specific ImportAttach commands.
Snapshot Viewer
Description: The Snapshot Viewer is no longer included in Office Access 2007. Migration path: You can still download the Snapshot Viewer from Office Online.
GUID-based URLs
Description: GUID-based (unique ID-based) URLs are no longer available. Use hierarchical (or "friendly") URLs instead.
Live mode
Description: An anonymous user can no longer view the site in Live Mode. The user views the site according to his or her permissions on the site. To see a more restricted view, the user must log in as a user who has those permissions.
115
116
This article lists the changes in Microsoft Office Excel 2007 from Microsoft Office 2003.
Whats new
New XML file formats New user interface and formatting capabilities Improved usability More rows and columns, and other new limits New OLAP formulas and cube functions New sharing and collaboration features New security features Improved troubleshooting features
For more information about new file formats in the 2007 Microsoft Office system, see File format reference. For more information about how to migrate files to new file formats, or for coexisting with different versions of Excel, see Planning for migration (http://technet.microsoft.com/enus/library/cc179048.aspx) and Migrating to the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303380.aspx).
Improved usability
The following improvements make formula writing much easier in Office Excel 2007: Resizable formula bar: The formula bar automatically resizes to accommodate long, complex formulas, which prevents the formulas from covering other data in a worksheet. You can also write longer formulas that have more levels of nesting than you could in earlier versions of Excel. Formula AutoComplete: You can quickly write the correct formula syntax with Formula AutoComplete. Structured references: In addition to cell references, such as A1 and R1C1, Office Excel 2007 provides structured references that reference named ranges and tables in a formula. Easy access to named ranges: By using the Office Excel 2007 name manager, you can organize, update, and manage multiple named ranges in a central location, which helps anyone who must work on your worksheet interpret its formulas and data.
118
In Office Excel 2007, PivotTables are much easier to use than in earlier versions of Excel. PivotTables are easier to create and there are many other new or improved features to summarize, analyze, and format your PivotTable data. Users can easily make connections to external data without having to know the server or database names of corporate data sources. In addition to the Normal view and Page Break Preview view, Office Excel 2007 provides a Page Layout View for a better printing experience. Improved sorting and filtering that lets you filter data by color or by dates, display more than 1,000 items in the AutoFilter drop-down list, select multiple items to filter, and filter data in PivotTables. For more information about the usability improvements in Office Excel 2007, see What's new in Microsoft Office Excel 2007 (http://go.microsoft.com/fwlink/?linkid=120390).
119
120
Whats changed
Analysis ToolPak (ATP): Function results AutoOutline command BIFF8 records Calculation: Multithreaded calculation (MTC) Charting: chart sheets, integration, and programmability Digital signatures Information Rights Management (IRM): Windows Rights Management Client Filtering Functions: Subtotal HTML Round-Trip PivotTable: Autoformat, customizations, GetPivotData, sorting, and versions Query Tables Remove Hidden Data add-in tool Send To Mail Recipient Shared Workbooks Tables: Insert row Templates Trust Center: Data links, macros Versioning
IMPOWER- also affected by the formatting for imaginary numbers change IMSIN - also affected by the formatting for imaginary numbers change IMSQRT - also affected by the formatting for imaginary numbers change
Formatting for imaginary numbers Functions that return imaginary numbers now use the same rules to employ scientific notation as those used in the rest of Office Excel 2007. For example, the formula =IMSUM({"3.23+1.02i";"1";"-i"}) returns 2.23+0.02i instead of 2.23+2E-002i. This change affects the following functions: IMAGINARY IMARGUMENT IMCONJUGATE IMCOS - also affected by the sin/cos change IMDIV IMEXP - also affected by the sin/cos change IMLN IMLOG2 IMLOG10 IMPOWER - also affected by the sin/cos change IMPRODUCT IMREAL IMSIN - also affected by the sin/cos change IMSQRT - also affected by the sin/cos change IMSUB IMSUM
Gamma calculation The ERF and ERFC functions now use the internal calculations for gamma, which might cause a change in the fifteenth decimal place. For example, =ERFC(0.2) returns 0.777297410872743 when it used to return 0.777297410872742. ERF ERFC
Power calculation Functions that calculate exponents now use internal routines, and might return slightly different results in the last decimal place. For example, the formula =EFFECT(0.055,199) now returns one less decimal place in the result. This change affects the following functions: BIN2DEC BIN2HEX BIN2OCT CUMIPMT CUMPRINC
122
DURATION EFFECT HEX2BIN HEX2DEC HEX2OCT IMPOWER MDURATION NOMINAL OCT2BIN OCT2DEC OCT2HEX ODDFPRICE ODDFYIELD PRICE SERIESSUM TBILLEQ TBILLPRICE TBILLYIELD WEEKNUM XIRR XNPV YIELD
Financial functions The following functions return a #NUM error when the basis parameter is very large: ACCRINT ACCRINTM AMORDEGRC AMORLINC COUPDAYBS COUPDAYS COUPDAYSNC COUPNCD COUPNUM COUPPCD DISC DURATION INTRATE
123
MDURATION ODDFPRICE ODDFYIELD ODDLPRICE ODDLYIELD PRICE PRICEDISC PRICEMAT RECEIVED YEARFRAC YIELD YIELDDISC YIELDMAT
Other function changes The EDATE function returns a #NUM error when the months parameter is greater than 1e21. The ERF and ERFC functions return 1 and 0, respectively, for parameters above 1. This change fixes the problem of the functions returning a #NUM error for parameters above 27. The MULTINOMIAL function now returns correct results when a number is passed in as text. This change fixes the problem of the function returning incorrect results when a number other than the first number is passed in as text.
AutoOutline command
Because the AutoOutline command was a low-use feature, it has been removed from the user interface. However, it can be added to the Quick Access Toolbar from the Customized tab in Excel Options. The Subtotal command can be used instead.
BIFF8 records
Description: Some features that could be saved in the Excel 97-2003 file format cannot be saved in the new Office Excel 2007 file formats. The mail envelope header (the information in the To, Cc, and Subject lines that appears when the Send To feature is used) is not saved. While the Send To feature continues to work in Office Excel 2007, this information is not saved with the workbook. If you close the workbook, the information is lost. Macintosh-specific records cannot be saved in the new file format. Macintosh Excel saves a few Macintosh-specific records into the BIFF8 format, but these records are not used by Office Excel 2007, and Office Excel 2007 cannot save them into the new format. A user of Office Excel 2007 will not notice a change.
124
125
Programmability: Excel 4 macros (XLM) that showed chart dialog boxes are no longer supported. XLM macros will still work in Office Excel 2007. However, we recommend that XLM macros are rewritten in Visual Basic for Applications (VBA). Setting properties that make references (such as Series.Name or Series.Values) to invalid references will be treated as an invalid reference, rather than causing a run-time error. The Creator property now causes a runtime error. This Macintosh-only method is not supported on Windows. Use the xlCreatorCode constant instead.
For information about all the chart feature changes, see Changes in Charting.
Digital signatures
Description: The digital signature feature has the following changes: The signature format in the 2007 Office system is XMLDSig. The digital signature entry point is moved from Tools, Options, Security, Digital Signatures to the Microsoft Office Button, Prepare, Add a Digital Signature and, for signed workbooks, to the Signature task pane. Invalid signatures are no longer automatically removed. The object model is extended to support the new model and to support existing solutions. Third parties can create their own signing providers. Users can access the previous functionality through a more visible and intuitive route.
Reason for change: The digital signatures feature in the 2007 Office system is more visible and intuitive. Users can view when signature verification is performed, and who has signed the document. Third parties can create custom signing solutions.
126
Filtering
Description: In Office Excel 2003, macros checked the AutoFilterMode property if the selection was in a list (table) to determine whether Autofilters was turned on in that list. In Office Excel 2007, the AutoFilterMode property works in connection with worksheet AutoFilters, and does not work in connection with AutoFilters that are part of a table. Office Excel 2007 gives each table its own AutoFilter object, which in turn uses tables to enable multiple AutoFilters in each worksheet. Migration path: Code in an Office Excel 2003 workbook that has macros that check the AutoFilterMode property in a list might not work correctly. This issue does not affect a document or macro that was created in a version earlier than Office Excel 2003. Instead of checking the AutoFilterMode property, the macro should be changed to check the tables AutoFilter object.
Functions: Subtotal
Description: The location of subtotals and grand totals when the Subtotal feature is invoked is updated to address issues of user expectations and backward compatibility. Users who use the Subtotal feature might find that the location of their subtotals is different than it was in versions earlier than Excel 2000, but otherwise the feature works as expected. Calculations are correct, and the correct subtotals and grand totals are created. Only the location has changed.
HTML Round-Trip
Description: The Save As HTML feature is used to create HTML files viewed in a Web browser that does not require Office Excel 2007 to view the file. When a user updates the contents of the file, he or she most likely opens the .xls file, edits the file, and resaves it as HTML. Most users do not open those HTML files for further editing in Office Excel 2007. Office Excel 2007 no longer stores Excel-only feature information in HTML file formats. Office Excel 2007 continues to use the Save As HTML feature to publish workbooks viewed in a Web browser. In earlier versions of Excel, the Save As HTML feature saved HTML tags to view in the browser. It also saved a set of Excel-specific tags that were not viewed in the browser in the HTML file. Although the Web browser does not use these Excel-specific tags, the Excel program uses the tags when it opens the HTML file to preserve the features that were used when the file was saved. Office Excel 2007 no longer saves these Excel-specific feature tags in HTML files, and therefore these tags do not exist in the HTML file. The overall result is that HTML files cannot be used by Office Excel 2007 to preserve feature information. Instead, HTML files are used by Office Excel 2007 to publish static HTML views of a workbook. For example, if a workbook contains PivotTables, formulas, and charts, and the workbook is saved as HTML, the following actions occur: A view of the PivotTable is saved in the HTML file, but the PivotTable is not saved. Calculated results of the formulas and cell formatting are saved in the HTML file, but the formulas are not saved. A picture of the chart is saved in the HTML file, but the chart feature is not saved.
127
If the HTML file is opened by using any version of Excel, you see: Cells that look similar to a PivotTable, but the PivotTable is no longer active. Numbers in cells, but no formulas. A picture of a chart, but no ability to work with the picture as a chart feature.
Office Excel 2007 can still open HTML files, and can still open Excel-specific features that are contained in HTML files. However, to make and save changes to the file while preserving all of the features in that file, you must save the file in a format that supports Excel features. The best format for this is the new XML file format. Reason for change: Most users use Save As HTML to publish HTML for a browser to render, not to open the file again in Excel. Migration path: Office Excel 2007 workbooks can be published as HTML. You should use the workbook (.xls, .xlsx) as your main copy. Always open the main copy, make changes, save the main copy, and save as HTML. There are no Excel-specific features saved into the HTML file. HTML workbooks can open HTML workbooks. However, to ensure all the Excel features in the file work correctly, you should use the new XML format (.xlsx) to save a copy of the workbook and use that copy as your main copy. This change will not force most users to change the way they work. Instead, this change reflects the way most users use the Save As HTML feature.
128
Sorting: In Office Excel 2007, PivotTables support AutoSort scoped to a specific row or column of values. In Office Excel 2003, AutoSort could only be applied based on the values in the grand total row or column. The new sorting options are available for any PivotTable version in Office Excel 2007. Versions: PivotTables in Office Excel 2007 cannot be made interactive in earlier versions of Excel, and Office Excel 2007 does not downgrade the PivotTable version when earlierversion file formats are saved. Earlier-version PivotTables do not support the following new features: label filtering; value filtering (except for top 10 filters, which are supported); hiding intermediate hierarchy levels in OLAP data sources; and manual exclusive filtering. If it is necessary to author the same PivotTable collaboratively in both Office Excel 2007 and earlier versions of Excel, users should not save the workbook in an Office Excel 2007 file format. For more information, see Working with different PivotTable formats in Office Excel (http://go.microsoft.com/fwlink/?linkid=121919).
Query Tables
Description: Query Tables are now merged with the List feature, which is now called Tables. Reason for change: This change improves functionality and provides a more consistent user experience.
interface, but can be added to the Quick Access Toolbar from the Customized tab in Word Options. The object-model entry points also remain. Reason for change: The Send To Mail Recipient (for Review) feature is superseded by the group collaboration features in Windows SharePoint Services 3.0. The collaboration features in Windows SharePoint Services 3.0 provide a more robust workflow. Users can continue to use the object model for Send for Review, and add the option to the Quick Access Toolbar, but they should consider migrating to the SharePoint document life cycle workflow offering. The Send for Review feature uses client-only programs. Users can write an add-in to use this feature's object model while they migrate to a Windows SharePoint Services 3.0 environment. Alternatively, users can send the document to reviewers in an e-mail message. Reviewers can comment on the document by using the Comments feature located on the Review tab. For more information about the Comments feature, see Insert or delete a comment (http://go.microsoft.com/fwlink/? linkId=118656).
Shared Workbooks
Description: Shared Workbooks, a feature since Excel 95, enable multiple users to work on the same copy of a workbook. The shared workbook manages all changes so that the copies can eventually be merged. In Office Excel 2003, this feature is only supported in the BIFF8 file (XLS) format. However, not all Excel features are supported in Shared Workbooks. Office Excel 2007 supports Shared Workbooks in the BIFF12 (XLSB) format and the XML12 (XLSX) format. Migration path: If users will be editing a shared workbook in Office Excel 2007 and a previous version of Excel, keep the workbook in the Biff8 file (XLS) format. Changing the file format to the new BIFF12 (XLSB) or XML12 (XLSX) formats will discard the revision history.
Templates
Description: The available set of templates in Office Excel 2007 has changed. Reason for change: The new templates use new features available in Office Excel 2007, and they provide a more modern look for users. Migration path: The templates in earlier versions of Excel are still available as downloads from Office Online.
Data links: When opening a workbook in Office Excel 2007, all connections are disabled by default, and there are no modal prompts for Refresh on open and Periodic refresh. Instead, Office Excel 2007 displays the trust bar. Clicking the trust bar displays the enable/disable options for the connections in that workbook. This change primarily addresses a user education issue that relates to the trust bar. Placing a workbook in a trusted location enables the workbook to automatically refresh without prompts. Macros: Office Excel 2007 no longer saves VBA code that includes nothing but comments and declaration statements. Excel VBA code that is attached to a workbook and that contains nothing but comments and declaration statements is neither loaded nor saved with the file. Very few workbooks are affected by this change. Users can work around this issue by adding a subroutine or function to the Excel VBA code.
Versioning
Description: The stand-alone versioning feature has been removed in Office Excel 2007. A more robust versioning feature that stores the information for each version separately is provided with document libraries on Windows SharePoint Services 3.0 sites and Microsoft Office SharePoint Server 2007 sites. Reason for change: The versioning feature in Windows SharePoint Services 3.0 document libraries provides a more robust workflow than what is available with Office Excel 2003. Migration path: Install the 2007 Office system and migrate to a Windows SharePoint Services 3.0 environment. Organizations that used the versioning feature can use the Version Extraction Tool (VET) in the Office Migration Planning Manager (OMPM) to extract versions of a document into multiple files. For more information, see Migrate Word, Excel, and PowerPoint files to the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179019.aspx ).
Whats removed
Charting: Printed Chart Size, Chart Window, charts on dialog sheets, change chart type for multiple charts, and support for XLM constants Data Retrieval Services Natural Language Formulas (NLFs)
131
Charting: Printed Chart Size, Chart Window, charts on dialog sheets, change chart type for multiple charts, and support for XLM constants
The following Charting features have been removed: Printed Chart Size: The Printed Chart Size option has been removed from the Chart tab in the Page Setup dialog box. The PageSetup.ChartSize property is hidden and has no functionality. The new behavior matches the Custom setting in Office Excel 2003. Charts are now integrated with OfficeArt, and it was not possible to reimplement this command for charts. Macros that use the PageSetup.ChartSize property can resize the chart. Chart Window: The Chart Window command has been removed from the View menu. The Chart.ShowWindow property is hidden, and has no functionality. Charts are now integrated with OfficeArt, and it was not possible to reimplement this command for charts. Macros that use the Chart.ShowWindow property can show another window on the sheet and scroll within that window to show only the chart. Change chart type for multiple charts: In Office 2003, you can select multiple charts and change the chart type for all of the selected charts simultaneously. This behavior is not available in the 2007 Microsoft Office system. Charts are now integrated with OfficeArt, and it was not possible to reimplement this command for charts. You can change the chart type for each chart individually. Alternatively, save one chart as a template, and apply the template to the other charts. Charts on dialog sheets: Charts are not allowed on dialog sheets. It was not possible to implement this feature for the 2007 Office system. Support for Excel 4 macro (XLM) constants: Macros that were converted from XLM might have retained the XLM constants for certain parameters. These constants are no longer supported, and the documented constants should be the only constants used. Change VBA calls that use numeric values for enumerations to those that use appropriately named constants. For information about all the chart feature changes, see Changes in Charting.
132
Office 2003 shipped the following DRS adapters. DRS adapters function only when they are installed on a server running Windows SharePoint Services 3.0 or Office SharePoint Server 2007. WSS adapterexposes Windows SharePoint Services 3.0 data by using the DRS protocol. Shipped with Windows SharePoint Services 3.0. OLEDB adapterexposes data from OLEDB sources by using the DRS protocol. Shipped with Windows SharePoint Services 3.0. SQL adapterexposes data from a SQL Server database by using the DRS protocol. Web Parts and Components add-on pack (Ststpkpl.msi). Shipped as part of the Office 2003 add-in. Microsoft Business Solutions (MBS) adapterexposes data from Great Plains and Solomon by using the DRS protocol. Reason for change: DRS is addressed in other products. Migration path: For the general DRS entry point, SQL Server and Windows SharePoint Services 3.0 data is available through other ways that also existed in Office Excel 2003.
133
134
Attachments
Description: The Attachments feature has a new user interface and enhanced functionality. Reason for change: Customers can now preview attachments.
Calendar
Description: The Calendar feature has the following changes in Office Outlook 2007: The Week view is replaced by a new Week view. The Free/Busy bar does not show on Calendar items if the item is Busy. The Meeting icon is removed from Calendar items. The default detail level of the Month view is changed.
Reason for change: This change simplifies the Calendar user interface and allows more text to appear on Calendar items.
E-mail: Categories
Description: In previous versions of Outlook, categories could arrive on incoming mail and were automatically reapplied on replies and forwards to categorized mail. Categories are no longer assigned to incoming mail, and are not automatically reassigned to replies and forwards. Reason for change: The new Colored Categories feature makes categories visually louder. Most users do not want to receive categorized mail, which they perceive as spam.
135
MAPI DLLs
Description: The user interface and functionality for MAPI DLLs are separated. The functional DLL is installed into a language-agnostic folder under OfficeVer. This change has no effect on end users. ISVs must use LoadLibrary and the default search path to load the Outlook MAPI Provider. If they do not, the ISV is broken. Reason for change: This change results in smaller Language Interface Pack (LIP) downloads. Migration path: Use LoadLibrary and the default search path to load the Outlook MAPI Provider.
Non-delivery receipt
Description: When a mailbox is full, submission fails on the client side instead of on the server side. The recipient still receives a message stating that their mailbox is over the message limit. Reason for change: This change was made in response to customer feedback.
136
Scripting agent
Description: Using Outlook to administer Exchange Server scripts is possible only by downloading the Scrptxtn.dll file from the Microsoft Download Center. Reason for change: Most customers do not use this feature. Migration path: Download and install Scrptxtn.dll from the Microsoft Download Center.
Security settings
Description: Security settings from Tools, Options are moved into the Trust Center. Reason for change: This change creates a more consistent environment by aggregating security settings in a single location.
137
Deleted Pages
Description: The Deleted Pages feature is removed. When you delete a page in Office OneNote 2007, it is placed in the Deleted Pages folder. Reason for change: Most users did not use this feature to restore deleted pages.
Ink Groups
Description: The Show Ink Groups feature on the Tools menu is removed. Entry points to the feature are also removed. Office OneNote 2007 no longer shows users the structure it identifies for their ink as they write. Reason for change: This was a low-use feature with only moderate satisfaction. Removing the feature simplifies the user interface. The feature is also no longer needed due to the more intelligent and context-aware parsing engine.
Page Header
Description: The title area in Office OneNote 2007 is removed. Reason for change: The title area was not commonly used. Migration path: This change is made automatically during upgrade. See Also Differences in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179054.aspx) Changes in the 2007 Office system
138
This article lists what is new and what has been changed or removed in Microsoft Office PowerPoint 2007 from Microsoft Office 2003.
What's new
New XML file formats New user interface, graphics, and formatting capabilities Improved proofing tools New sharing and collaboration features New security features Improved troubleshooting and recovery features
Use tables and charts that have been redesigned to be much easier to edit and work with. For more information on chart feature changes, see Changes in Charting. Uniformly format your presentations with one click by using Document Themes. For more information about the new user interface, graphics, and formatting capabilities, see What's new in Microsoft Office PowerPoint 2007 (http://go.microsoft.com/fwlink/?linkid=111043).
139
An exclusion dictionary is automatically created for a language the first time that language is used. The spelling checker can find and highlight some contextual spelling errors. For more information about the proofing tools improvements, see What's new in Microsoft Office PowerPoint 2007 (http://go.microsoft.com/fwlink/?linkid=111043). For information about deploying multiple sets of proofing tools, see Deploy Proofing Tools for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179042.aspx ).
140
AutoContent Wizard
Description: The AutoContent Wizard feature is removed from Office PowerPoint 2007. Reason for change: Templates provide a more consistent and predictable user experience when inserting content into a slide. Migration path: Create presentations by using Office PowerPoint 2007 templates.
Broadcast
Description: The Broadcast feature is removed from Office PowerPoint 2007. Reason for change: This feature was rarely used. Migration path: Microsoft Office Live Meeting can help users collaborate online and share presentations with individuals or large groups in different locations. For more information about Microsoft Office Live Meeting, see Office Online Microsoft Office Live Meeting (http://go.microsoft.com/fwlink/?linkId=110484).
141
Charts
Description: Some changes to the chart feature are: The user interface for charts is redesigned. The data for a graph in Office PowerPoint 2007 or Microsoft Office Word 2007 is stored in Microsoft Office Excel 2007, rather than in the graph datasheet. Charts no longer automatically come to the front when they are selected. If a user copies a chart from Office PowerPoint 2007 or Office Word 2007 and pastes the chart into a program other than Office PowerPoint 2007, Office Word 2007, or Office Excel 2007, the chart is pasted as a picture. A graph in Office PowerPoint 2007 or Office Word 2007 that does not contain data does not show its title or legend. 3-D charts have appropriate lighting and shading, and colors might not precisely match previous versions. For information on all the chart feature changes, see Changes in Charting.
Digital signatures
Description: The digital signature feature has the following changes: The signature format in the 2007 Office system is XMLDSig. The digital signature entry point is moved from Tools, Options, Security, Digital Signatures to the Microsoft Office Button, Prepare, Add a Digital Signature and, for signed documents, to the Signature task pane. Invalid signatures are no longer automatically removed. The object model is extended to support the new model and to support existing solutions. Third parties can create their own signing providers. Users can access the previous functionality through a more visible and intuitive route.
Reason for change: The digital signatures feature is more visible and intuitive. Users can view when signature verification is performed, and who has signed the document. Third parties can create custom signing solutions.
142
Minor versioning is included in the 2007 Office system. Previous versioning could only be enabled or disabled. Versioning numbers can now be represented by decimals to represent minor versioning; for example, 2.2 in addition to 2. Reason for changes: The Document Inspector provides Remove Hidden Data add-in functionality in the 2007 Office system and is more discoverable. Users do not have to download the Remove Hidden Data add-in tool separately. The same versioning functionality in Windows SharePoint Services 3.0 now exists in the 2007 Office system. Migration path: Install the 2007 Office system.
Macro recorder
Description: The macro recorder feature is removed from Office PowerPoint 2007. Migration path: Use Microsoft Visual Basic for Applications (VBA) to create or edit macros.
143
144
145
Project Center
Description: Redundant fields are removed from Project Center. Reason for change: The user interface is simplified.
Quick Flags
Description: Quick Flags are replaced by task flags and categories. If in the past a user flagged an item to show that the item was important or that it belonged to a particular group, the user should now mark the item with a category color of their choice. If they formerly used flags to show when they planned to perform tasks, they should now use task flags. Reason for change: By flagging a task, a user enters an item in the overall task management system. This enables the user to see their tasks in the To-Do Bar, in the task well, and in the task module. By categorizing items, the user can easily scan their Inbox for the items, the same way that they may formerly have scanned their Inbox for flagged items. The user can also find their categorized items in category search folders. These changes enable integration with the Time Management System and allow users to name their colors.
Status Reports
Description: The ability to delete Miscellaneous and Archive Status Reports responses is removed. Users should send a request to the administrator to manage responses clean-up. Reason for change: This enables administrators to have more control over what is deleted.
146
147
Authentication
Description: Project Server authentication is replaced by Forms authentication. This requires setting up a forms virtual server. Users will not be able to set up the equivalent of Project Server authentication without a forms virtual server. Reason for change: This enables users to authenticate against any data store that supports Forms authentication, not just Office Project Server 2007. Migration path: Users of Project Server authentication will be migrated during the upgrade to Office Project Server 2007. Administrators can use the PJFormsAuthUpgrade tool to add users to a membership store.
Project versions
Description: The creation of Project versions codes and the ability to save multiple versions of a project with the same name is removed. Reason for change: This was a low-use feature, and this change, along with the new alternate routes to obtaining version functionality, provides greater simplicity for customers.
Publish by Resource
Description: Publishing new and changed assignments for a selected group of resources is removed. Reason for change: This was a low-use and low-awareness feature. This change simplifies the user interface and decreases functional complexity.
148
Restore
Description: A command line tool that restored project-level data from a restored copy of the Project Server database is removed. Migration path: Backup and restore now occurs from a user interface that is supplemented with a new command line tool, stsadm.exe, which enables automation outside the user interface.
Site links
Description: The code that supports the up to <site> link in Project workspaces is removed. Reason for change: The architecture has changed, so the Web pages now fall back on the root site to support this feature. Migration path: Upgrade removes the SharePoint site URL.
Update tasks
Description: Updating tasks from Office Project Server 2007 to Microsoft Office Project 2007 is changed from client/server to all server-side. Customers can update project plans based on data submitted using Office Project Web Access. In Project 2003, customers could move updates from Project Server into Project Professional, view or modify the updates, and then decide whether to save the changes. In Office Project 2007, users can preview their changes in Office Project Web Access, but in Web client preview they have fewer tools to use in examining the results than they had in the Project 2003 Professional preview. Reason for change: This change was based on customer feedback. Customers wanted the ability to update projects by working on the server only. This change significantly improves the performance of the update process. It also enables customers to create custom business processes to automate the update process. Migration path: As part of the migration process, customers must update all project plans before the data migration process begins. See Also Differences in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179054.aspx) Changes in the 2007 Office system Changes in Project 2007
149
Hover Buttons
Description: Hover buttons are removed from Office SharePoint Designer 2007. Reason for change: Prevents confusion between hover buttons and interactive buttons.
150
151
Crawl schedules
Description: Crawl schedules could previously be created and maintained in their own list. Crawl schedules are now completely associated with content sources. You cannot define a crawl schedule outside of a content source. Users no longer have a page on which to manage their crawl schedules. Instead, they must specify crawl schedules on the content source page. Reason for change: This change reduces the confusion caused by creating content sources in one location and linking the sources to schedules in another location.
Portal Provisioning
Description: The user interface and object model for the provisioning feature are changed. The area creation user interface is replaced by the WSS Web creation user interface. Migration path: If users have customized SharePoint Portal Server 2003 provisioning, their code continues to work after upgrade. However, it is recommended that users rework the code to use the Windows SharePoint Services 3.0 object model.
152
Shared Services
Description: In SharePoint Portal Server 2003, each portal that was created had its own set of resource-intensive, high-value services. This condition severely restricted scale, so a feature was introduced that allowed all portals located within a single farm to share the same set of services. A second introduced feature allowed all portals located within a remote SharePoint Portal Server 2003 farm to also consume services from a parent farm. In both cases, the change was a substantial and a one-way switch: if the shared services option was chosen, all portals in the affected farms had to participate in the shared services; and once service sharing was turned on, there was no way to turn it off again. In the 2007 Microsoft Office system, the ability to share services turns on by default. It is flexible so that more than one set of services is available within and between farms, and portals move easily between sets of shared services. Reason for change: This change improves scale, performance, and farm usability. SharePoint Portal Server 2003 was restricted to 15 portals per farm. Users can now host many more sites on a single set of hardware. Service level administration can now be delegated to power users. Users can configure their systems to reflect the system's current state. For example, they can move Web programs between sets of shared services to reflect organizational and political changes. Migration path: Auto migrated as part of the server upgrades collection.
153
Topology Management
Description: The Topology Management user interface is replaced by a new management feature. Reason for change: The inclusion of four additional products in Windows SharePoint Services 3.0 requires a new method to manage the services on servers for ease of use. With the new feature, users can uniformly manage all services and servers for the Office Server products.
154
Menu changes
Description: Several menus are changed in Office Visio 2007, resulting in the elimination of the following entry points for commands: The View sub-menu is removed from shape RMA. The Shape sub-menu is removed from page RMA. Special on the Format menu is hidden, except in developer mode. Custom Properties Set is removed from the Tools menu.
Reason for change: These changes provide a more streamlined user interface that makes it easier for users to access important features. Migration path: Items accessed through RMA are still available from top-level menus. Items hidden from menus can be made available by enabling developer mode. Users must choose different entry points for the commands.
155
Visio SDK: Visual Studio 6.0 wizards and managed code tutorials
Description: Visual Studio 6.0 Wizards and managed code tutorials are removed from the Visio SDK. Reason for change: The new focus is on .NET technologies. Migration path: To use the former wizards and tutorials, customers can download the previous and the new Visio SDKs.
156
This article lists the changes in Microsoft Office Word 2007 from Microsoft Office 2003.
Whats new
New XML file formats New user interface, graphics, and formatting capabilities Improved proofing tools New sharing and collaboration features New security features Improved troubleshooting and recovery features
157
Change the appearance of text, tables, and graphics throughout your document to match your preferred style or color scheme by using new Quick Styles and Document Themes. Create your own Document Theme to consistently apply the fonts and colors that reflect your companys branding. Use new charting and diagramming features that include three-dimensional shapes, transparency, drop shadows, and other effects.
An exclusion dictionary is automatically created for a language the first time that language is used. Exclusion dictionaries let you force the spelling checker to flag words that you want to avoid using; for example, obscene words or words that do not match your company's style guidelines. For more information about improvements to the proofing tools, see Whats new in Microsoft Office Word 2007 (http://go.microsoft.com/fwlink/?linkid=115216). For information about deploying multiple sets of proofing tools, see Deploy Proofing Tools for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179042.aspx ).
158
Assign permissions that prevent others from copying, printing, or editing your document by using the 2007 Office system with Microsoft Windows Rights Management Services for Windows Server 2003. Manage document properties in the Document Information Panel. Detect documents that contain embedded macros by looking at the separate file format (.docm) for macro-enabled documents. Documents that have the file format .docx cannot contain macros. For more information about the new security features, see Whats new with Microsoft Office Word 2007 (http://go.microsoft.com/fwlink/?linkid=115216). For information about how to configure security settings for macros, see Security policies and settings in the 2007 Office system.
Whats changed
Charts Digital signatures Document life cycle Information Rights Management Microsoft Office Document Imaging (MODI) tool Send To Mail Recipient
Charts
Description: The chart feature has the following changes: The user interface for charts is redesigned. The data for a graph in Microsoft Office PowerPoint 2007 or Office Word 2007 is stored in Microsoft Office Excel 2007, rather than in the graph datasheet. Charts no longer automatically come to the front when they are selected. If a user copies a chart from Office PowerPoint 2007 or Office Word 2007 and pastes the chart into a program other than Office PowerPoint 2007, Office Word 2007, or Office Excel 2007, the chart is pasted as a picture. A graph in Office PowerPoint 2007 or Office Word 2007 that does not contain data does not show its title or legend.
159
Three-dimensional (3-D) charts have appropriate lighting and shading, and colors might not precisely match earlier versions. For information about all of the chart feature changes, see Changes in Charting.
Digital signatures
Description: The digital signature feature has the following changes: The signature format in the 2007 Office system is XMLDSig. The digital signature entry point is moved from Tools, Options, Security, Digital Signatures to the Microsoft Office Button, Prepare, Add a Digital Signature and, for signed documents, to the Signature task pane. Invalid signatures are no longer automatically removed. The object model is extended to support the new model and to support existing solutions. Third parties can create their own signing providers. Users can access the previous functionality through a more visible and intuitive route.
Reason for change: The digital signatures feature is more visible and intuitive. Users can view when signature verification is performed, and who has signed the document. Third parties can create custom signing solutions.
160
document into multiple files. For more information, see Migrate Word, Excel, and PowerPoint files to the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179019.aspx).
document by using the Comments feature located on the Review tab. For more information about the Comments feature, see Insert or delete a comment (http://go.microsoft.com/fwlink/? linkId=118656).
Whats removed
Autosummarize command: The AutoSummarize control is removed from the user interface, but can be added to the Quick Access Toolbar from the Customized tab in Word Options. This was a low-use feature. AutoComplete for AutoText: The AutoComplete tip functionality that displays after typing the first few characters of the AutoText entry has been removed. However, AutoComplete is still available for the current system date, months, and days of the week. Converters: mswrd832.cnv: The new converter provided in has improved functionality. wrd6er32.cnv: This converter saved Word 97-2003 files as RTF with a .doc extension so the files could be read by Word 95. To create documents that can be read by Word 95, save the documents as RTF files. Download the Office File Converter Pack to enable Word 95 to open these files. Outdated Korean-specific converters (GSR32.CNV, HANA32.CNV, TGWP32.CNV): These converters supported three word processing programs that are no longer in use. Personal Address Book (PAB): Users can no longer use a PAB file as a source for mail merge documents. This feature is replaced by Contacts in Outlook. Users should use Contacts instead of PAB files. Wpequ532.dll: This was used to render equations when WordPerfect 5.0 and 6.0 files were opened in Word. This change increases security by removing legacy code that is no longer used. If needed, Wpequ532.dll is available in the Office File Converter Pack from the Microsoft Download Center. Diagram object model: For more information, see Changes in Charting. Fonts, Text, and Format themes: Eastern European Font add-in: This add-in is only useful for files with font-mapping issues that were created on previous systems. There have been no code-page dependencies for more than five years. If needed, download the Word Font Repair Macro from the Microsoft Download Center. Fix broken text for Word 6.0 documents: This is a low-use feature for a legacy issue. If needed, download the Word Font Repair Macro from the Microsoft Download Center. Font Text Effects: This is a low-use feature that is no longer useful in Web site design. To remove the Text Effects formatting for older documents opened in Office Word 2007, use the Clear Formatting option on the Home tab in the Font group. Format themes dialog for choosing HTML/CSS themes: The new Themes architecture replaces this feature.
162
File Search: This is a low-use feature that is redundant with other search mechanisms.
Ietag.dll browser helper object (BHO): The ietag.dll provides OOUI/Action Menu functionality when a document with recognized smart tags opens within Internet Explorer. With changes in Word Mail, this feature is no longer necessary. Mail merge bar codes: Users can no longer insert a bar code into a mail merge. Mergeable address lists: This was a low-use set of templates. The mergeable address list templates from Word 2003 are still available on Office Online. Microsoft Script Editor (MSE): The removal of this low-use feature increases security. Documents that contain scripts and that are upgraded to the new file formats will lose the scripts without warning. Save As Web Page option: Saving as a Web page is now performed by using Save As on the Microsoft Office Button. Click the Microsoft Office Button, Save As, Other Formats, Save as type, and then select Web page (*.htm;*html). Send to Routing Recipient: Removal of this low-use feature from the user interface improves the user experience. Third-party OCX controls: Customers can no longer use the Web Tools toolbar to insert movies, sound, or scrolling text (marquees).These controls are disabled because of security updates. Insert Web Components for Office XP: This is a low-use feature. Web discussions: Entry points to Web discussions are removed. Wizards: Agenda wizard Envelope wizard Fax wizard Letter wizard Memo wizard Pleading wizard Resume wizard
These wizards are replaced by more modern templates available on Office Online.
163
WordPerfect usability: WordPerfect navigation: This functionality is removed, including Help for WordPerfect users and navigation keys that match WordPerfect. This is legacy functionality that has very low usage. Set the width of a space like WordPerfect 5.x. Blue background with white text option: This feature, included in earlier versions of Word to emulate legacy versions of WordPerfect, is no longer used.
See Also Differences in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179054.aspx) Changes in the 2007 Office system
164
The Hindi language version also installs Microsoft Office Access 2007 in English. Microsoft Office Project 2007, Microsoft Office Visio 2007, and Microsoft Office SharePoint Designer 2007 are available in a subset of languages, as shown in the following table.
Language Project 2007 Visio 2007 SharePoint Designer 2007
165
Language
Project 2007
Visio 2007
Czech Danish Dutch English Finnish French German Greek Hebrew Hungarian Italian Japanese Korean Norwegian Polish Portuguese (European) Russian Spanish Swedish Thai Turkish
yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes no yes
yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes no yes
yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes
166
The rest of the applications appear in the primary Office installation language. The following table lists the recommended base language for each LIP language.
LIP language
Afrikaans Albanian Amharic Armenian Assamese Azeri Basque Bengali - Bangladesh Bengali - India Bosnian - Cyrillic Bosnian - Latin Byelorussian Filipino Galician Georgian Gujarati Hausa
English English English English English or Hindi English or Russian Spanish or French English English or Hindi Serbian Latin, English, or Croatian Serbian Latin, English, or Croatian Russian English Spanish English English or Hindi English
167
LIP language
Igbo Icelandic Indonesian Bahasa Inuktitut Irish - Gaelic isiXhosa isiZulu Kannada Kazakh Khmer Ki'che Kinyarwanda Kyrgyz Kiswahili Konkani Lao Luxembourgish Macedonian (FYROM) Malay Malay - Brunei Malayalam Maltese Maori Marathi Nepali Norwegian - Nynorsk Oriya Pashto Persian
English English English English English English English English or Hindi Russian or English English Spanish English or French Russian English English or Hindi English or Thai German, English, or French English English English English or Hindi English English English or Hindi English or Hindi Norwegian English or Hindi English English
168
LIP language
Punjabi Quechua Setswana Sesotho sa Leboa Sinhalese Tamil Tatar Telugu Urdu Uzbek - Latin Vietnamese Welsh Wolof Yoruba
English or Hindi Spanish English English English English or Hindi Russian English or Hindi English English or Russian English English French English
See Also Customize and deploy multiple language versions of the 2007 Office system (http://technet.microsoft.com/en-us/library/dd162397.aspx)
169
Language identifiers
The 2007 Office system offers localized versions in all the languages listed in the following table. Folders for the language-specific components are identified by the language tag shown in the table. The Windows operating system uses locale identifiers (LCIDs) to identify languages in the Windows registry. Notes In addition to the fully localized languages listed here, Office provides language interface packs (LIPs), which contain a subset of language-specific components and are designed to be installed with a logical parent language. Elements that are not localized in the LIP language appear in the parent language.
Language Geographic area Language tag (ll-cc) LCID
Saudi Arabia Bulgaria People's Republic of China Hong Kong SAR Taiwanese
Language
Geographic area
LCID
Croatian Czech Danish Dutch English Estonian Finnish French German Greek Hebrew Hindi Hungarian Italian Japanese Kazakh Korean Latvian Lithuanian Norwegian (Bokml) Polish Portuguese Portuguese Romanian Russian Serbian (Latin) Slovak Slovenian Spanish
Croatia Czech Republic Denmark Netherlands United States Estonia Finland France Germany Greece Israel India Hungary Italy Japan Kazakhstan Korea Latvia Lithuania Norway Poland Brazil Portugal Romania Russia Serbia Slovakia Slovenia Spain
hr-hr cs-cz da-dk nl-nl en-us et-ee fi-fi fr-fr de-de el-gr he-il hi-in hu-hu it-it ja-jp kk-kh ko-kr lv-lv lt-lt nb-no pl-pl pt-br pt-pt ro-ro ru-ru sr-sp-latn sk-sk sl-si es-es
1050 1029 1030 1043 1033 1061 1035 1036 1031 1032 1037 1081 1038 1040 1041 1087 1042 1062 1063 1044 1045 1046 2070 1048 1049 2074 1051 1060 3082
171
Language
Geographic area
LCID
See Also Simplified design for multiple languages in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179020.aspx) Customize and deploy multiple language versions of the 2007 Office system (http://technet.microsoft.com/en-us/library/dd162397.aspx )
172
173
OMPM contents
OMPM is contained in a self-extracting executable file, MigrationPlanningManager.exe. OMPM Components are contained in redistributable subfolders: Scan: The folder containing the OMPM File Scanner. Report: The folder containing OMPM Reports. To export file lists from OMPM Reports, the database folder and related components must also be available. Database: The folder containing scripts to provision and populate the OMPM database. Tools: The folder containing tools such as the Office File Converter and Version Extraction Tool.
Installing OMPM
To install OMPM, type the following at a command prompt: MigrationPlanningManager /extract:c:\ompm For help with OMPM, type the following at a command prompt: MigrationPlanningManager /?
OMPM requirements
The following lists the requirements for running OMPM, both for the client systems that it scans and the administrator system from which it runs.
The following system components must exist on all computers running the OMPM File Scanner. If these files do not exist, install the files with a separate distribution job before you run the OMPM File Scanner. Data Access Objects 3.5 or higher (dao350.dll/dao360.dll). These files are included in Microsoft Access 97, Microsoft Windows 98, Microsoft Windows NT 4.0 Option Pack, and Windows NT 4.0 Service Pack 4. Microsoft Scripting Runtime (sccrun.dll). This file is included in Microsoft Access 2000, Windows NT 4.0 Option Pack, Windows NT 4.0 Service Pack 5, and Microsoft Windows Scripting Host. Visual C Runtime (msvcrt.dll). Kernel32.dll. Msjet40.dll.
174
All computers that contain files to convert are required by the Office File Converter (OFC) to install the Microsoft Office Compatibility Pack. For more information, see Deploying the Microsoft Office Compatibility Pack (http://technet.microsoft.com/en-us/library/cc179023.aspx). The Version Extraction Tool (VET) requires installation of Microsoft .NET Framework Version 2.0 Redistributable Package (x86) (http://go.microsoft.com/fwlink/?LinkId=81886) and Microsoft Word 2003.
175
SQLXML 3.0 SP3. SQLXML enables XML support for your SQL Server 2005 database. This module allows XML files that are collected by the OMPM File Scanner to be imported efficiently into a database server. SQLXML is a free download available at SQLXML 3.0 Service Pack 3 (SP3) (http://go.microsoft.com/fwlink?linkid=52919). Note: We recommend using the English editions of SQL Server 2005 or SQL Server 2005 Express Edition to use OMPM. While there are no known issues involving international editions, only the English edition is supported for these tools at this time. File share A file share is required to stage the XML log files collected by the OMPM File Scanner before the log files are imported into the database. The file share should have a minimum of 1 GB available space. Any account that is operating the import scripts requires read/write/create access to the file share. Note: For performance reasons, it is optimal to have the import tools, log file share, and database on the same server. If this is not possible, the log file share and the database server should be on the same subnet to reduce network traffic. Other OMPM Reports requires the installation of Microsoft Access 2007 on the client computer from which the data will be examined. To export file lists from OMPM Reports, SQL Server Express or SQL Server and SQLXML 3.0 SP3 must be installed on the computer that runs OMPM Reports. To perform a deep scan with the OMPM File Scanner, Access 2002 or later must also be installed on the computer that runs the OMPM File Scanner. Note: Other than the requirement listed above, the OMPM File Scanner does not require the installation of any version of Office on any computer it scans. For scanning document storage systems such as Microsoft SharePoint Services, the OMPM File Scanner requires the Web-based Distributed Authoring and Versioning (WebDAV) interface. For more information about WebDAV, see About WebDAV (IIS 6.0) (http://go.microsoft.com/fwlink/?LinkID=81698). This is the only version of WebDAV that is supported for OMPM. Note: Use either the Windows Vista WebDAV client or a third-party WebDAV client for document libraries that are SSL-enabled. If you use the WebDAV client from previous versions of Windows, the scan of the document library fails.
176
Note: The OMPM File Scanner does not change file properties, except possibly Last Accessed Date. Note: The OMPM File Scanner does not transmit data to Microsoft Corporation.
177
The OMPM File Scanner creates four unique types of log files to record properties about the computer scanned, file scanned, scan summary, and errors. The following table shows a typical set of log files.
File Name Description
Scan log (one per scan) File properties log (one per unique file scanned) Summary log Error log (one per unique error occurrence)
The individual log files are compressed into CAB files to make transport to the SQL Server database more efficient. To maximize disk space on the computer that is scanned, after OMPM File Scanner writes 10,000 log files, adds the log files to a CAB file, and then deletes the log files. Each CAB file contains up to 10,000 log files. When a CAB file reaches 10,000 log files, OMPM File Scanner creates a new CAB file for the next 10,000 files. CAB files use the file name from the ScanID GUID, with an index number appended. Three CAB files generated on the same computer might generate names such as the following: Computer1 {2FA87EDF-4393-4BCF-8829-8776F82DEDD5}00001.cab Computer1 {2FA87EDF-4393-4BCF-8829-8776F82DEDD5}00002.cab Computer1 {2FA87EDF-4393-4BCF-8829-8776F82DEDD5}00003.cab
Creating CAB files can be detrimental to performance if log files are saved across a network. Use the setting CABlogs=1 in the Offscan.ini file to disable the creation of CAB files.
178
Access
.mdb .mde .mdz .adp .ade .mdt .mda .accda .accdb .accdr .accdu .accde .accdt .accdc .xls .xlt .xla .xlm .xlw .htm .html .mhtml .mht .xlc .wk1 .wk3 .wk4 .wj1 .wj2 .wj3 .fj3 .fmt .fm3 .all .wks .wq1 .dbf
Excel
179
PowerPoint
Project
Publisher Visio
.pub .vsd, .vss .vst .vdx .vtx .vsx .doc .dot .wiz
Word
Files from Microsoft Office Outlook, Microsoft Office FrontPage, Microsoft Office OneNote, and Microsoft Office InfoPath are not included in either the light or deep scan. Note: The OMPM File Scanner does not scan documents that are password-protected or IRMprotected. In addition, the OMPM File Scanner does not scan embedded objects within documents, but does report that the document contains embedded objects.
180
'------------g_optFile g_SourcePath
If oFso.FileExists(g_optFile) Then oFso.DeleteFile g_optFile End If g_intReturnCode= oWsh.Run("%comspec% /c " & g_SourcePath & " >> " & g_optFile,0,True) '// Remove this if network copy is not requried CopycabfiletoNetworkLocation
181
Quit() '********************************************************************** ****************************************** 'Sub Name : GenerateMIFMessage() 'Purpose: Generates the MIF message '********************************************************************** ****************************************** Sub GenerateMIFMessage() 'On Error Resume Next Dim l_varGetFile,l_strReadFile,l_strLine, l_oMIFGen, l_strMifMessage If oFso.FileExists(g_optFile) Then Set l_varGetFile = oFso.GetFile(g_optFile) Set l_strReadFile = l_varGetFile.OpenAsTextStream(1,-2) Do While l_strReadFile.AtEndofStream = False l_strLine = l_strReadFile.ReadLine If Not Trim(l_strLine) = "" Then If Instr(lcase(l_strLine),"total time") or Instr(lcase(l_strLine),"total number") Then If Trim(l_strMifMessage) = "" Then l_strMifMessage = g_intReturnCode & ":" & l_strLine Else l_strMifMessage = l_strMifMessage & ";" & l_strLine End If End If If Instr(lcase(l_strLine),"error:") Then If Trim(l_strMifMessage) = "" Then l_strMifMessage = g_intReturnCode & ":" & Split(Split(l_strLine,".") (0),":")(1) Else l_strMifMessage = l_strMifMessage & ";" & Split(Split(l_strLine,".") (0),":")(1) End If
182
End If End If Loop Set l_strReadFile = Nothing Set l_varGetFile Else l_strMifMessage="Output file NOT found" End If Set l_oMIFGen = WScript.CreateObject("ISMIFCOM.InstallStatusMIF") l_oMIFGen.Create "OffScan.MIF", "Microsoft", "Office File Scanner", "1.0", "ENU", 1, l_strMifMessage, 1 End Sub '********************************************************************** *************** ' Sub Name: Quit ' Purpose: Exit '********************************************************************** *************** Sub Quit() 'On Error Resume Next GenerateMIFMessage() Set oWsh = Nothing Set oFso = Nothing Wscript.Quit(0) End Sub '********************************************************************** *************** 'Sub Name : CopycabfiletoNetworkLocation() 'Purpose: Copy the cab file to specified common folder = Nothing
183
'********************************************************************** *************** Sub CopycabfiletoNetworkLocation() 'On Error Resume Next Dim l_strDemoFolder, l_strFile, l_oFileCollection Dim l_offSacnIniPath, l_SourceFolder, l_destinationFolder l_offSacnIniPath="bits\offscan.ini" l_SourceFolder="%temp%\offscan" '%temp%\offscan - this shold be same as in offscan.ini file. '//--------------- Specify the Share name (share name should end with "\" )-------------------l_destinationFolder= "\\server\sharename\"
l_offSacnIniPath
= oFso.BuildPath(g_strRoot,l_offSacnIniPath)
If oFso.FileExists(l_offSacnIniPath) Then l_SourceFolder = oWsh.ExpandEnvironmentStrings(l_SourceFolder) Set l_strDemoFolder = oFso.GetFolder(l_SourceFolder) Set l_oFileCollection = l_strDemoFolder.Files For Each l_strFile in l_oFileCollection oFso.CopyFile l_strFile,l_destinationFolder Next Set l_oFileCollection = Nothing Set l_strDemoFolder = Nothing End If If oFso.FileExists(g_optFile) Then oFso.CopyFile g_optFile,l_destinationFolder End If End Sub
184
9. When you finish adding files, click Next. 10. On the Install Program to Launch page, in the Install Program box, type c:\ompm\offscan.exe. In the Post Install Command box, enter the command you want to use to copy .cab files from the scanned computer to the location where you want to store all .cab files. For example, to copy the .cab files from c:\scan\logs to the logs directory on the computer Server1, enter copy c:\scan\logs\*.* \\Server1\logs. Click Next. 11. On the Show window page, select Hidden and click Next. 12. On the Finished message page, select No message and click Next. 13. On the Package Name and Options page, enter the path and filename that you want for this distribution package. Select the options that you want and click Next. 14. On the Configure restart page, select No restart and click Next. 15. On the Save Self Extraction Directive page, select Save Self Extraction Directive (SED) file:, edit the path and name of the file, and click Next. 16. On the Create package page, click Next. When the package has been created, click Finish to exit.
185
Scanner Run
A list of all run descriptions and their IDs. Filters to all files that were scanned in that scanner run. Note: The data displayed for each file is from the latest scanner run. Filters by type of issue, including Access Error, Scanner Error, Tool Error, and Upgrade Issue. Filters to all files that have that issue. Shows unresolved issues filtered to the specified issue type. Shows issues that have been resolved by user actions, such as converting the file. Filters by the maximum issue level found in a file, including Red, Yellow, and Green. For example, if a file has a red issue and a green issue, it is filtered with a red issue. Filters by file format. You can select individual programs, or you can select Excel/PowerPoint/Word to select all files that can be converted to the new .xml file formats in the 2007 Office release. Filters by file extension. Shows files with a last modified date that is before the date specified. Shows files with a last modified date that is after the date specified. Filters by the file access that the scanner had to each file. For example, if the file is on a drive that is read only for the scanner, the file is listed as read only.
Issue Type
Select Issues of Specified Type Select Resolved Issues and Actions Max Issue Level
File Format
186
Field
Description
Min Size (KB) Domain Computer Name Path Begins With Name Begins With System Folders
Shows files that are the file size specified or bigger. Filters by domain; the string must be an exact match. Filters by computer name; the string must be an exact match. Shows files where the long path name begins with the characters specified. Shows files where the file name begins with the characters specified. Shows files from the selected system folders. The system folder <undefined> filters to files not found in system folders. This is a read-only field showing the most recently applied SQL clause. Click the Customize SQL button to edit the SQL clause. Click Clear SQL Filter to return to editing the filter in the form view. Advanced: When customizing SQL, you can insert filter criteria by using a field in the form view and clicking Add Selected Criteria to insert those criteria into the SQL query.
After you have applied a filter, the Scanned Files and Created Files windows contain the first 1,000 files that were returned. You can sort or filter by any column by using data sheet column headers, but the results will be only for those 1,000 files. For example, if you sort by File Name, OMPM Reports returns the same 1,000 files sorted by File Name. To sort or filter on all of the files in that scanner run, click Open in a new window at the bottom of the Scanned Files or Created Files window.
187
188
The following table provides descriptions for each table for scan data in the OMPM File Scanner schema.
Table Description Fields
osScan
Descriptive information for a scan that will run, including the RunID
ScanID RunID Description DestinationPath ScanMyDocuments ScanDesktop DeepScan ComputerName UserName DNS OS LCID PhysicalMemory ScanDAO AccessScan DisableConvDialog MaxCopyFileSize TempPath
osScanSummary
Scan results
osScanIncludedFolder
Source location for the included folders in a scan search instance Source location for the excluded folders in a scan search instance
osScanExcludedFolder
189
Table
Description
Fields
osScanMappedDrive
osErrorText
ErrorID ErrorDescription
osError
osScanFile
File information gathered during a light scan by the OMPM File Scanner
ScanFileID ScanID FileName FilePath ShortFilePath FileSize FileExtension FileFormatID CreatedDate ModifiedDate FileOwner IsReadOnly HashCode CSIDL
190
Table
Description
Fields
osFileFormat
The types of files found by the OMPM File Scanner Information gathered during a deep scan by the OMPM File Scanner for potential Word issues Information gathered during a deep scan by the OMPM File Scanner for files that contain VBA macros
osWordProperty
osVBAProperty
osPowerPointProperty
Information gathered during a deep scan by the OMPM File Scanner for potential PowerPoint issues
191
Table
Description
Fields
osExcelProperty
Information gathered during a deep scan by the OMPM File Scanner for potential Excel issues
ScanFileID FileOpenNotSupported FileSaveNotSupported WorkspaceFile HTMLSaved OWC9 OWC10 OWC11 FileFormat LastSavedVersion EmbeddedDocs WSSLinkedList MSERedcords ErrorChecking AccessDBConnection SharedWorkBook LinkedContent Charts OfficeArtShapes ELFEnabled StandardList ATP RelationalPivot OLAPPivot CondFormat
osExcelPropertyLinked
Information gathered during a deep scan by the OMPM File Scanner for Excel files that contain linked cells
ScanFileID Link
192
OMPM Compatibility Report data schema: tools, actions, and issues data
The tools, actions, and issues tables in the OMPM Compatibility Report data schema include information about the OMPM tool used, the actions that the administrator performed for a file, and the issues identified by the deep scan function of the OMPM File Scanner. The following table provides descriptions for each table for tools, actions, and issues data in the OMPM Compatibility Report data schema.
Table Description Fields
omIssue
Issues found by OMPM File Scanner, Office File Converter, or Version Extraction Tool.
omIssueLevel
Pre-defined issue levels (red, yellow, and green). Pre-defined issue categories.
omIssueType
omFileIssue
omToolIssue
ToolId IssueId
193
Table
Description
Fields
omTool
Tool definitions.
omAction
Action taken for a file, including whether the file was modified.
omActionFile
Files that were created by an action, such as a .docx file created by the Office File Converter.
omActionIssue
omAccessRatings
FileID RatingId
omAccessIssue
Conversion and other issues that were found in Access files during the scan. The system folder identifier for a file. For more information about CSIDL values, see CSIDL (http://go.microsoft.com/fwlink? linkid=71501).
omCSIDL
194
Table
Description
Fields
omFilter
omFileCategory
The action name (for example, "Upgrade") that created a file in the omActionFile table.
FileCategoryId Description
omFile
File information, including location and modifiers for actions that change the state of the file.
FileId LastScanFileId Name Path ShortPath Extension FileFormatId Size CreatedDate ModifiedDate Owner UserContent ComputerName DNS HashCode CSIDL MaxIssueLevel IsReadOnly
195
Table
Description
Fields
omFileScanFile
Maps entries in FileId omAccessIssue from the ScanFileId corresponding omFile entry to osScanFile, which specifies the FileID needed to get details from the Access tables.
AccessVersionsProperties
Contains information about the version properties in an Access file. Contains information about Access system files. Contains information about Access sample files.
VersionCode Version
AccessSystemFiles
Name
AccessSampleFiles
Name
AccessReservedWords
Contains information Name about reserved words in an Access file. Contains information about the settings of an Access file. Contains information about lookup properties for query types in an Access file. SettingName DateValue TypeID TypeFriendlyName
AccessSettings
AccessQueriesTypeLookupProperties
196
Table
Description
Fields
AccessIssuesProperties
AccessBackupTokens
Name
AccessDatabasesRatingProperties
Contains information RatingID about database rating Rating properties for an Access file. Contains information about lookup properties for field types in an Access file. Contains information about forms in an Access file. Contains information about references in an Access file. FieldType FieldTypeFriendlyName
AccessFieldTypeLookupProperties
AccessForms
FileID FormName FileID ReferenceName GUID FullPath IsBroken Kind Major Minor
AccessReferences
AccessMacros
Contains information about macros in an Access file. Contains information about queries in an Access file.
AccessQueries
Table
Description
Fields
AccessTables
AccessModules
Contains information about modules in an Access file. Contains information about reports in an Access file. Contains information about fields in an Access file.
AccessReports
AccessFields
198
Table
Description
Fields
AccessProperties
Contains information FileID about properties in an ScanID Access file. TableCount QueryCount FormCount ReportCount MacroCount ModuleCount ReferenceCount CollatingOrder Version ReplicaID DesignMasterID ANSIQueryMODE AccessVersion Build ProjVer StartupForm NoConvertDialog DatabaseOwner IsCompiled IsSample IsBackup IsOld IsSystem
See Also Office Migration Planning Manager reference Assessing your environment with the Office Migration Planning Manager (http://technet.microsoft.com/en-us/library/cc178986.aspx) Migrating to the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303380.aspx)
199
Access Project Extension (Microsoft) Access Project (Microsoft) Executable Application Active Server Page BASIC Source Code Batch Processing Internet Security Certificate File Compiled HTML Help
201
File type
File description
.cmd .com .cpl .crt .csh .der .exe .fxp .hlp .hta .inf .ins .isp .its .js .jse .ksh .lnk .mad .maf .mag .mam .maq .mar .mas .mat .mau
DOS CP/M Command File, Command File for Windows NT Command Windows Control Panel Extension (Microsoft) Certificate File csh Script DER Encoded X509 Certificate File Executable File FoxPro Compiled Source (Microsoft) Windows Help File Hypertext Application Information or Setup File IIS Internet Communications Settings (Microsoft) IIS Internet Service Provider Settings (Microsoft) Internet Document Set, International Translation JavaScript Source Code JScript Encoded Script File UNIX Shell Script Windows Shortcut File Access Module Shortcut (Microsoft) Access (Microsoft) Access Diagram Shortcut (Microsoft) Access Macro Shortcut (Microsoft) Access Query Shortcut (Microsoft) Access Report Shortcut (Microsoft) Access Stored Procedures (Microsoft) Access Table Shortcut (Microsoft) Media Attachment Unit
202
File type
File description
.mav .maw .mda .mdb .mde .mdt .mdw .mdz .msc .msh .msh1 .msh2 .mshxml .msh1xml .msh2xml .msi .msp .mst .ops .pcd .pif .plg .prf .prg .ps1 .ps1xml .ps2
Access View Shortcut (Microsoft) Access Data Access Page (Microsoft) Access Add-in (Microsoft), MDA Access 2 Workgroup (Microsoft) Access Application (Microsoft), MDB Access Database (Microsoft) Access MDE Database File (Microsoft) Access Add-in Data (Microsoft) Access Workgroup Information (Microsoft) Access Wizard Template (Microsoft) Microsoft Management Console Snap-in Control File (Microsoft) Windows PowerShell Windows PowerShell Windows PowerShell Windows PowerShell Windows PowerShell Windows PowerShell Windows Installer File (Microsoft) Windows Installer Patch Windows SDK Setup Transform Script Office Profile Settings File Visual Test (Microsoft) Windows Program Information File (Microsoft) Developer Studio Build Log Outlook Profile file Program File Windows PowerShell Windows PowerShell Windows PowerShell
203
File type
File description
.ps2xml .psc1 .psc2 .pst .reg .scf .scr .sct .shb .shs .tmp .url .vb .vbe .vbs .vsmacros .vsw .ws .wsc .wsf .wsh .xnk
Windows PowerShell Windows PowerShell Windows PowerShell MS Exchange Address Book File, Outlook Personal Folder File (Microsoft) Registration Information/Key for W95/98, Registry Data File Windows Explorer Command Windows Screen Saver Windows Script Component, Foxpro Screen (Microsoft) Windows Shortcut into a Document Shell Scrap Object File Temporary File/Folder Internet Location VBScript File or Any VisualBasic Source VBScript Encoded Script File VBScript Script File, Visual Basic for Applications Script Visual Studio .NET Binary-based Macro Project (Microsoft) Visio Workspace File (Microsoft) Windows Script File Windows Script Component Windows Script File Windows Script Host Settings File Exchange Public Folder Shortcut
VII Security reference Security policies and settings in the 2007 Office system
This section provides technical reference information for the security settings and privacy options in the 2007 Microsoft Office system. You can use this information to determine: What a setting does. What the default configuration is for a setting. Which tool to use to configure a setting.
Where to find the setting in the Office Customization Tool (OCT) or the Group Policy Object Editor. Note: To use Group Policy to manage the 2007 Office system, you must load the Office 2007 Administrative Templates (that is, .adm files) into the Group Policy Object Editor. The following security settings and privacy options are discussed in this section: Trusted locations and trusted publishers settings ActiveX control settings Add-in settings Visual Basic for Applications (VBA) macro settings Document protection settings External content settings Internet Explorer feature control settings Privacy options Block file format settings
which apply to all applications; and application-specific settings, which can be configured separately for each application.
By default, a computer can have trusted locations that are created by users through the graphical user interface and trusted locations that are created by administrators through Group Policy or the OCT. Disabling this setting prevents users from creating trusted locations through the graphical user interface and disables all trusted locations that are created by users through the graphical user interface and all trusted locations that are created by administrators through the OCT. This setting enables you to specify trusted locations globally for Office Access 2007, Office Excel 2007, Office PowerPoint 2007, Office Visio 2007, and Office Word 2007. You can configure this setting only through Group Policy; you cannot configure global trusted locations through the OCT.
206
Setting name
Default configuration
Description
If you select this setting, all trusted locations that are specified by the OCT are deleted. This setting can be configured only on the Office security settings page of the OCT. You cannot configure this setting through Group Policy.
Note: Several trusted locations are specified by default during installation. These default trusted locations do not appear in the OCT or in the Group Policy Object Editor. For more information about default trusted locations, see "Default trusted location settings" in Evaluate default security settings and privacy options for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179075.aspx). You can find the Allow mix of policy and user locations setting at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system/Security Settings/Trust Center You can find the Trusted Location #1#n settings and the Allow mix of policy and user locations setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Security Settings/Trust Center
207
Trusted locations that are not on the computer are not allowed.
By default, trusted locations that are network shares are disabled, but users can still select the Allow Trusted Locations on my network check box in the Trust Center graphical user interface. If this setting is set to Disabled and a user attempts to designate a network share as a trusted location, a warning informs the user that the current security settings do not allow the creation of trusted locations with remote paths or network paths. If an administrator designates a network share as a trusted location through Group Policy or by using the OCT and this setting is Disabled, the trusted location is disabled and is not recognized by an application.
208
Setting name
Default configuration
Description
Enabling this setting disables all trusted locations, including trusted locations that are: Created by default during setup. Created by users through the graphical user interface. Deployed through Group Policy. Enabling this setting also prevents users from configuring trusted locations settings in the Trust Center.
This setting allows you to specify trusted locations separately for Office Access 2007, Office Excel 2007, Office PowerPoint 2007, Office Visio 2007, and Office Word 2007. You can configure this setting through the OCT and through Group Policy.
Note: Several trusted locations are specified by default during installation. These default trusted locations do not appear in the OCT or in the Group Policy Object Editor. For more information about default trusted locations, see "Default trusted location settings" in Evaluate default security settings and privacy options for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179075.aspx). You can find these settings at the following locations on the Modify user settings page of the OCT: Microsoft Office Access 2007/Application Settings/Security/Trust Center/Trusted Locations Microsoft Office Excel 2007/Excel Options/Security/Trust Center/Trusted Locations Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center/Trusted Locations Microsoft Office Word 2007/Word Options/Security/Trust Center/Trusted Locations Microsoft Office Visio 2007/Tools|Options/Security/Trust Center You can find these settings at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Access 2007/Security/Trust Center/Trusted Locations
209
Microsoft Office Excel 2007/Excel Options/Security/Trust Center/Trusted Locations Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center/Trusted Locations Microsoft Office Word 2007/Word Options/Security/Trust Center/Trusted Locations Microsoft Office Visio 2007/Tools|Options/Security/Trust Center
HKEY_CURRENT_USER/Software/Microsoft/Office/Common/Security When you use the Group Policy Object Editor to disable ActiveX controls, the DisableAllActiveX registry entry is written to: HKEY_CURRENT_USER/Software/Policies/Microsoft/Office/Common/Security There is one setting for disabling ActiveX controls. This setting is described in the following table.
Setting name Default configuration Description
Disabled
When you enable this setting, all ActiveX controls are disabled and will not initialize when a user opens a file that contains ActiveX controls. Also, when you enable this setting, users are not notified that ActiveX controls are disabled. This setting can be configured in the OCT and with the Group Policy Object Editor. This setting applies only to applications in the 2007 Office system. This setting does not disable ActiveX controls in files that are opened by earlier versions of Office.
You can find the Disable All ActiveX setting at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system/Security Settings You can also find the DisableAllActiveX setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Security Settings Note: You can also disable ActiveX controls by configuring ActiveX control initialization settings. These settings are discussed in the following section.
There are six possible values for the UFIControls registry entry. The values are described in the following table.
UFIControls value Loads SFI controls in safe mode? Initialization behavior when a VBA project is present Initialization behavior when no VBA project is present
No
Initializes SFI and UFI controls with minimal restrictions (that is, persisted values). If persisted values are not available, the controls are initialized with default values by using the InitNew method. Users are not notified that ActiveX controls are enabled. Initializes SFI and UFI controls with minimal restrictions (that is, persisted values). If persisted values are not available, the controls are initialized with default values by using the InitNew method. Users are not notified that ActiveX controls are enabled.
ActiveX controls are initialized the same way that they are when a VBA project is present.
Yes
ActiveX controls are initialized the same way that they are when a VBA project is present.
212
UFIControls value
No
Prompts users to enable or disable controls. If the user enables controls, SFI controls are initialized with minimal restrictions (that is, with persisted values) and UFI controls are initialized with default values by using the InitNew method.
If the file contains only SFI controls, SFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, SFI controls are initialized with default values by using the InitNew method. Users are not prompted to enable SFI controls. If the file contains UFI controls, users are prompted to enable or disable controls. If user enables controls, SFI controls are initialized with minimal restrictions and UFI controls are initialized with default values by using the InitNew method.
213
UFIControls value
Yes
Prompts users to enable or disable controls. If the user enables controls, SFI controls are initialized with minimal restrictions (that is, with persisted values) and UFI controls are initialized with default values by using the InitNew method.
If the file contains only SFI controls, SFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, SFI controls are initialized with default values by using the InitNew method. Users are not prompted to enable SFI controls. If the file contains UFI controls, users are prompted to enable or disable controls. If the user enables controls, SFI controls are initialized with minimal restrictions and UFI controls are initialized with default values by using the InitNew method.
214
UFIControls value
No
Prompts users to enable or disable controls. If the user enables controls, SFI and UFI controls are initialized with minimal restrictions (that is, with persisted values). If persisted values are not available, controls are initialized with default values by using the InitNew method.
If the file contains only SFI controls, SFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, SFI controls are initialized with default values by using the InitNew method. Users are not prompted to enable SFI controls. If the file contains UFI controls, users are prompted to enable or disable controls. If the user enables controls, SFI and UFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, controls are initialized with default values by using the InitNew method.
215
UFIControls value
Yes
Prompts users to enable or disable controls. If the user enables controls, SFI and UFI controls are initialized with minimal restrictions (that is, with persisted values). If persisted values are not available, controls are initialized with default values by using the InitNew method.
If the file contains only SFI controls, SFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, SFI controls are initialized with default values by using the InitNew method. Users are not prompted to enable SFI controls. If the file contains UFI controls, users are prompted to enable or disable controls. If the user enables controls, SFI and UFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, controls are initialized with default values by using the InitNew method.
When you configure the Unsafe ActiveX initialization setting in the OCT, the UFIControls registry entry is written to: HKEY_CURRENT_USER/Software/Microsoft/Office/12.0/Common/Security When you configure the ActiveX Control Initialization setting through Group Policy, the UFIControls registry entry is written to: HKEY_CURRENT_USER/Software/Policies/Microsoft/Office/Common/Security The following table describes the Unsafe ActiveX initialization settings that are in the OCT. You can find the Unsafe ActiveX initialization setting on the Office security settings page of the OCT.
216
Setting
This is the default setting. Initialization behavior is the same as Prompt user to use persisted data. Prompts users to enable or disable controls. If the user enables controls, SFI controls are initialized with minimal restrictions (that is, with persisted values) and UFI controls are initialized with default values by using the InitNew method. SFI controls are initialized in safe mode.
This is the default setting. Initialization behavior is the same as Prompt user to use persisted data. If the file contains only SFI controls, SFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, SFI controls are initialized with default values by using the InitNew method. SFI controls are initialized in safe mode. Users are not prompted to enable SFI controls. If the file contains UFI controls, users are prompted to enable or disable controls. If the user enables controls, SFI controls are initialized with minimal restrictions and UFI controls are initialized with default values by using the InitNew method. SFI controls are initialized in safe mode.
217
Setting
Prompts users to enable or disable controls. If the user enables controls, SFI and UFI controls are initialized with minimal restrictions (that is, with persisted values). If persisted values are not available, controls are initialized with default values by using the InitNew method. SFI controls are initialized in safe mode.
If the file contains only SFI controls, SFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, SFI controls are initialized with default values by using the InitNew method. SFI controls are initialized in safe mode. Users are not prompted to enable SFI controls. If the file contains UFI controls, users are prompted to enable or disable controls. If the user enables controls, SFI and UFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, controls are initialized with default values by using the InitNew method. SFI and UFI controls are initialized with minimal restrictions (that is, persisted values). If persisted values are not available, the controls are initialized with default values by using the InitNew method. Users are not notified that ActiveX controls are enabled. SFI controls are not loaded in safe mode.
Do not prompt
Initializes SFI and UFI controls with minimal restrictions (that is, persisted values). If persisted values are not available, the controls are initialized with default values by using the InitNew method. Users are not notified that ActiveX controls are enabled. SFI controls are not loaded in safe mode.
218
Setting
All ActiveX controls are disabled and will not initialize when a user opens a file that contains ActiveX controls. Users are not notified that ActiveX controls are disabled. This setting applies only to applications in the 2007 Office system. This setting does not disable ActiveX controls in files that are opened by earlier versions of Office.
All ActiveX controls are disabled and will not initialize when a user opens a file that contains ActiveX controls. Users are not notified that ActiveX controls are disabled. This setting applies only to applications in the 2007 Office system. This setting does not disable ActiveX controls in files that are opened by earlier versions of Office.
You can find the ActiveX Control Initialization setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Security Settings You can configure the ActiveX Control Initialization setting with a value from 1 to 6. These values correspond to the values of the UFIControls registry entry that are described in a previous table. The following table shows how the OCT, Group Policy, and Trust Center settings correspond to the values of the UFIControls and DisableAllActiveX registry entries.
Registry values Group Policy settings OCT settings Trust Center settings
UFIControls=1 DisableAllActiveX=0
Enable all controls without restriction and without prompting (not recommended; potentially dangerous controls can run) Safe mode checkbox (not selected)
UFIControls=2 DisableAllActiveX=0
Enable all controls without restriction and without prompting (not recommended; potentially dangerous controls can run) Safe mode checkbox (selected)
219
Registry values
OCT settings
UFIControls=3 DisableAllActiveX=0
Prompt me before enabling Unsafe for Initialization (UFI) controls with additional restrictions and Safe for Initialization (SFI) controls with minimal restrictions Safe mode checkbox (not selected)
UFIControls=4 DisableAllActiveX=0
Unsafe ActiveX initialization dropdown box: Prompt user to use control defaults
Prompt me before enabling Unsafe for Initialization (UFI) controls with additional restrictions and Safe for Initialization (SFI) controls with minimal restrictions Safe mode checkbox (selected)
UFIControls=5 DisableAllActiveX=0
Prompt me before enabling all controls with minimal restrictions Safe mode checkbox (not selected)
UFIControls=6 DisableAllActiveX=0
Unsafe ActiveX initialization dropdown box: Prompt user to use persisted data
Prompt me before enabling all controls with minimal restrictions Safe mode checkbox (selected) Disable all controls without notification Safe mode checkbox (unavailable)
DisableAllActiveX=1
Unsafe ActiveX initialization dropdown box: Do not prompt and disable all controls
220
Add-in settings
There are three main types of security settings for add-ins: Settings for disabling add-ins. Settings for requiring that add-ins are signed by a trusted publisher. Settings for disabling notifications for unsigned add-ins.
221
Disabled
When you enable this setting, all add-ins are disabled and users are not notified that addins are disabled. This setting can be configured in the OCT and in the Group Policy Object Editor. You must configure this setting on a per-application basis. This setting does not exist for Office Publisher 2007. To disable add-ins in Office Publisher 2007, you must use the Application add-ins warnings options setting. When you set this setting to Disable all application extensions, all add-ins are disabled and users are not notified that add-ins are disabled. This setting can be configured only in the OCT. You must configure this setting on a per-application basis.
You can find the Disable all application add-ins setting at the following locations on the Modify user settings page of the OCT: Microsoft Office Access 2007/Application Settings/Security/Trust Center Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center Microsoft Office Visio 2007/Tools|Options/Security/Trust Center You can find the Disable all application add-ins setting at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: User Configuration/Administrative Templates/Microsoft Office Access 2007/Application Settings/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Excel 2007/Excel Options/Security/Trust Center
222
User Configuration/Administrative Templates/Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Publisher 2007/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Visio 2007/Tools| Options/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Word 2007/Word Options/Security/Trust Center You can find the Application add-ins warnings options settings on the Office security settings page of the OCT, under Default security settings.
223
Disabled
When you enable this setting, add-ins that are signed by a publisher that is on the trusted publishers list will run without notification. Unsigned add-ins and add-ins that are signed by a publisher that is not on the trusted publishers list are disabled, but users are prompted to enable or disable the add-ins. This setting can be configured in the OCT and with the Group Policy Object Editor. You must configure this setting on a per-application basis. When you set this setting to Require that application extensions are signed by trusted publisher, add-ins that are signed by a publisher that is on the trusted publishers list will run without notification. Unsigned add-ins and add-ins that are signed by a publisher that is not on the trusted publishers list are disabled, but users are prompted to enable or disable the add-ins. This setting can be configured only in the OCT. You must configure this setting on a per-application basis.
You can find the Require that application add-ins are signed by trusted publisher setting at the following locations on the Modify user settings page of the OCT: Microsoft Office Access 2007/Application Settings/Security/Trust Center Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Publisher 2007/Security/Trust Center
224
Microsoft Office Word 2007/Word Options/Security/Trust Center Microsoft Office Visio 2007/Tools|Options/Security/Trust Center You can find the Require that application add-ins are signed by trusted publisher setting at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: User Configuration/Administrative Templates/Microsoft Office Access 2007/Application Settings/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Excel 2007/Excel Options/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Publisher 2007/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Visio 2007/Tools| Options/Security/Trust Center User Configuration/Administrative Templates/Microsoft Office Word 2007/Word Options/Security/Trust Center You can find the Application add-ins warnings options settings on the Office security settings page of the OCT, under Default security settings.
225
Disabled
This setting must be used in conjunction with the Require that application add-ins are signed by trusted publisher setting. When you enable the Disable trust bar notification for unsigned application addins setting, signed add-ins that are not trusted are disabled, but users are prompted to enable or disable the add-ins. Unsigned add-ins are also disabled, but users are not notified and they are not prompted to enable or disable the unsigned add-ins. This setting can be configured in the OCT and in the Group Policy Object Editor. You must configure this setting on a perapplication basis. When you set this setting to Require that extensions are signed, and silently disable unsigned extensions, signed add-ins that are not trusted are disabled, but users are prompted to enable or disable the add-ins. Unsigned add-ins are also disabled, but users are not notified and they are not prompted to enable or disable the unsigned add-ins. This setting can be configured only in the OCT. You must configure this setting on a per-application basis.
You can find the Disable trust bar notification for unsigned application add-ins setting at the following locations on the Modify user settings page of the OCT:
226
Microsoft Office Access 2007/Application Settings/Security/Trust Center Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Publisher 2007/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center Microsoft Office Visio 2007/Tools|Options/Security/Trust Center You can find the Disable trust bar notification for unsigned application add-ins setting at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Access 2007/Application Settings/Security/Trust Center Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Publisher 2007/Security/Trust Center Microsoft Office Visio 2007/Tools|Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center You can find the Application add-ins warnings options settings on the Office security settings page of the OCT, under Default security settings.
Settings for changing macro behavior in applications that are started programmatically through Automation. Settings for preventing virus-scanning programs from scanning encrypted macros.
Note: You can also change the default macro security settings for Office Outlook 2007. See the Office Outlook 2007 security documentation for more information. The VBA macro warning settings and VBA macro warnings options settings modify a registry entry named VBAWarnings. Each application evaluates this registry to determine how to run macros. There are four possible values for the VBAWarnings registry entry. The values are described in the following table.
VBAWarnings value Description
1 2
Untrusted and trusted macros are allowed to run without notification. All untrusted macros are disabled, but users are notified about untrusted macros and can enable or disable untrusted macros. Trusted macros are allowed to run without notification. This is the default setting. Unsigned macros are disabled without notification. Users are notified about signed macros and can enable or disable signed macros. Trusted macros are allowed to run without notification. Untrusted macros are disabled and users are not notified that untrusted macros are disabled. In addition, users cannot use the Message Bar or any other dialog to enable untrusted macros. Trusted macros are allowed to run without notification.
When you configure the VBA macro warnings options setting in the OCT, the VBAWarnings registry entry is written to: HKEY_CURRENT_USER/Software/Microsoft/Office/12.0/program name/Security Where program name can be any of the following: Access Excel PowerPoint Publisher Visio Word
228
When you configure the VBA macro warning settings setting through Group Policy, the VBAWarnings registry entry is written to: HKEY_CURRENT_USER/Software/Policies/Microsoft/Office/12.0/ program name/Security Where program name can be any of the following: Access Excel PowerPoint Publisher Visio Word The following table shows how the OCT, Group Policy, and Trust Center settings correspond to the values of the VBAWarnings registry entry.
Registry values VBA macro warning settings (Group Policy) VBA macro warnings options (OCT) Macro settings (Trust Center)
VBAWarnings=1
Enabled No security checks for macros (not recommended, code in all documents can run)
No security checks for VBA macros (not recommended, code in all documents can run)
Enable all macros (not recommended; potentially dangerous code can run)
VBAWarnings=2
Disable all VBA macros with notification (application default) Disable Trust Bar warning for unsigned VBA macros (unsigned code will be disabled)
VBAWarnings=3
Enabled Trust Bar warning for digitally signed macros only (unsigned macros will be disabled)
VBAWarnings=4
You can find the VBA macro warnings options setting on the Office security settings page of the OCT, under Default security settings.
229
You can find the VBA macro warning settings setting at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Access 2007/Application Settings/Security/Trust Center Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Publisher 2007/Security/Trust Center Microsoft Office Visio 2007/Tools|Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center
When you enable this setting, Automation clients have programmatic access to VBA projects and can use the VBA object model. When you disable this setting, Automation clients do not have programmatic access to VBA projects. This setting can be configured in the OCT and in the Group Policy Object Editor.
You can find the Trust access to Visual Basic project setting at the following locations on the Modify user settings page of the OCT:
230
Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center You can find the Trust access to Visual Basic project setting at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center
When you enable this setting, VBA will not function and users will not be able to run macros and other programmatic content. This setting can be configured in the OCT and in the Group Policy Object Editor.
You can find the Disable VBA for Office applications setting at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system/Security Settings You can find the Disable VBA for Office applications setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Security Settings
Setting name
Default configuration
Description
VBA is enabled.
Enabling this setting allows VBA to run. Disabling this setting prevents VBA from running, which can prevent some drawing types from having full functionality in Office Visio 2007. Enabling this setting allows Office Visio 2007 to compile VBA projects when you open a file. This enables you to use VBA projects that are saved in earlier Office Visio 2007 file formats. The compiled VBA projects are not saved. Disabling this setting prevents VBA projects from being loaded from text. Enabling this setting allows users to create VBA projects. Disabling this setting prevents users from creating VBA projects in files that do not already have a VBA project.
Load Microsoft Visual Basic for VBA projects are not loaded Applications projects from text from text.
You can find these settings at the following location on the Modify user settings page of the OCT: Microsoft Office Visio 2007/Tools|Options/Security/Macro Security You can find these settings at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Visio 2007/Tools|Options/Security/Macro Security
Settings for changing macro behavior in applications that are started programmatically through Automation
There are two types of Automation security settings: global settings and application-specific settings.
232
Macros are disabled in the 2007 Office system applications that start programmatically through Automation. Users are not notified that macros are disabled and users are not prompted to enable macros. Macros are enabled and run without notification.
Enabled Macros enabled (default) Enabled Use application macro security level
Macros run according to the security settings of the application that is started programmatically through Automation.
You can find this setting at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system/Security Settings You can find this setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Security Settings
Macros are enabled and run without notification in instances of Office Publisher 2007 that are started programmatically through Automation. This is the default configuration state.
233
Configuration state
Description
Enabled By UI (prompted)
Users are prompted whether to enable or disable macros in instances of Office Publisher 2007 that are started programmatically through Automation. Macros are disabled in instances of Office Publisher 2007 that are started programmatically through Automation. Users are not notified that macros are disabled and users are not prompted to enable macros.
You can find the Publisher automation security level setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Publisher 2007/Security
Determine whether to force encrypted macros to be scanned in Microsoft Excel Open XML workbooks
Encrypted macros are scanned by your virus-scanning program when you open an encrypted workbook that contains macros.
Encrypted macros are not scanned by your virusscanning program when you enable this setting, which means that encrypted macros will run according to the macro security settings that you have configured. This setting applies only to Office Excel 2007.
234
Setting name
Default configuration
Description
Determine whether to force encrypted macros to be scanned in Microsoft PowerPoint Open XML presentations
Encrypted macros are scanned by your virus-scanning program when you open an encrypted presentation that contains macros.
Encrypted macros are not scanned by your virusscanning program when you enable this setting, which means that encrypted macros will run according to the macro security settings that you have configured. This setting applies only to Office PowerPoint 2007. Encrypted macros are not scanned by your virusscanning program when you enable this setting, which means that encrypted macros will run according to the macro security settings that you have configured. This setting applies only to Office Word 2007.
Determine whether to force encrypted macros to be scanned in Microsoft Word Open XML documents
Encrypted macros are scanned by your virus-scanning program when you open an encrypted document that contains macros.
You can find these settings at the following locations on the Modify user settings page of the OCT: Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center You can find these settings at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Excel 2007/Excel Options/Security/Trust Center Microsoft Office PowerPoint 2007/PowerPoint Options/Security/Trust Center Microsoft Office Word 2007/Word Options/Security/Trust Center
Setting name
Default configuration
Description
On Microsoft Windows XP operating systems, the default is Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype), AES-128, 128-bit. On Windows Vista operating systems, the default is Microsoft Enhanced RSA and AES Cryptographic Provider, AES128, 128-bit.
Enables you to specify the encryption type for Office Open XML Formats files that are encrypted.
Enables you to specify the encryption type for Office 972003 format files that are encrypted.
You can find these settings at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system/Security Settings You can find these settings at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Security Settings
Add-ins can access sections of text that have been unlocked by a user.
Enabling this setting prevents add-ins from accessing sections of text that have been unlocked by a user.
236
Setting name
Default configuration
Description
Encrypted sections of text are not disabled (that is, users can use the password protection feature to lock and unlock sections of text and change password settings).
When you enable this setting, users cannot: Encrypt new and existing sections of text. Disable encryption on an encrypted section of text. Change the password that is used to encrypt a section of text. When this setting is enabled, users can still enter a password to access sections of text that are encrypted.
Encrypted sections of text remain unlocked for a period of time after a user navigates away from the unlocked text.
Enabling this setting ensures that encrypted sections of text become locked as soon as a user navigates away from the text.
237
Setting name
Default configuration
Description
Lock password protected sections after user hasn't worked on them for a time
Encrypted sections of text remain unlocked for 10 minutes after a user navigates away from the unlocked text or a user stops editing the unlocked text.
You can change the number of minutes that unlocked sections remain unlocked by enabling this setting and choosing a new time in Time interval (minutes) to lock password protected sections. If you do not want unlocked sections of text to automatically lock after a user unlocks them, you can disable this setting or you can enable this setting and clear the Check to lock sections checkbox. In either case, be sure that you do not enable the Lock password protected sections as soon as I navigate away from them setting. Doing so causes unlocked sections to lock as soon as a user navigates away from the sections, regardless of how you have configured the Lock password protected sections after user hasn't worked on them for a time setting.
You can find these settings at the following locations on the Modify user settings page of the OCT: Microsoft Office OneNote 2007/Tools|Options/Password You can find these settings at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office OneNote 2007/Tools|Options/Password
Setting name
Default configuration
Description
By default, users are notified about unsafe hyperlinks. In addition, unsafe hyperlinks are disabled until they are enabled by a user.
Enabling this setting suppresses hyperlink warnings for the following: Hyperlinks that use unsafe protocols, such as msn, nntp, mms, outlook, and stssync. Hyperlinks from a remote file to the local computer.
This setting applies only to the following applications: Office Access 2007 Office Excel 2007 Office InfoPath 2007 Office OneNote 2007 Office Outlook 2007 Microsoft Office Project 2007 Office PowerPoint 2007 Office Publisher 2007 Office Visio 2007 Office Word 2007 You can find this setting at the following location on the Modify user settings page of the OCT: Microsoft Office System 2007/Security Settings You can find this setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office System 2007/Security Settings
239
By default, images that are saved on an external computer do not display in slides.
Enabling this setting allows linked images on external Web sites to download and appear in slides.
You can find this setting at the following location on the Modify user settings page of the OCT: Microsoft Office PowerPoint 2007/PowerPoint Options/Security You can find this setting at the following location in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office PowerPoint 2007/PowerPoint Options/Security
Prevents add-ons disabled by the user or Group Policy from running or installing. Performs additional safety checks when ActiveX controls are initialized. Specifically, prevents the control from being created if the kill bit is set in the registry. Also checks the security settings for the zone of the URL in which the control is instantiated to determine whether the control can be safely initialized. Enables Internet Explorer's default pop-up blocker.
Block pop-ups
240
Description
Checks the following when a file is downloaded: File extension Content Type and Content Disposition in the HTTP header File signature bits Files with inconsistent information may be renamed to a safer file extension. Files that remain mismatched may be blocked from running on the user's system.
Invalidates URL syntax that may include a username and password, such as http://username:password@server/. Shows the default Internet Explorer Information Bar when file download or code installation is restricted. Applies Local Machine Zone settings to all local content. Checks the signature bits of downloaded files to determine the file's type and render the type properly. Blocks navigation to any page with a badly formed URL. Blocks access to objects instantiated and cached from a different security context than the current page. Prevents navigation to a page in the Trusted Sites or My Computer zone if the current page is not already in that zone. Allows applications to opt in to blocking new ActiveX controls and prevents installation of updates for ActiveX controls that are not already installed. Prevents file downloads that are not initiated by the user.
Information Bar
241
Description
Evaluates the saved from URL information for files on a Universal Naming Convention (UNC) share. This feature increases security on UNC paths, but at a performance cost. Forces pop-up windows to remain in the viewable desktop area, display a status bar, and not draw their borders outside the viewable area of the screen. Ensures that browser windows cannot overlay important information in their parent windows, or in system dialogs.
By default, Microsoft Office Groove 2007 (Groove.exe), Office Outlook 2007 (Outlook.exe), and Microsoft Office SharePoint Designer 2007 (Spdesign.exe) are opted in to all 15 feature control settings. Office InfoPath 2007 (Infopath.exe) is also opted in to all 15 feature control settings and the following three Office InfoPath 2007 components: Document Information Panel, Workflow forms, and third-party hosting. Internet Explorer feature control settings for all applications except Office InfoPath 2007 can be found at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system (machine)/Security Settings/IE Settings Internet Explorer feature control settings for all applications except Office InfoPath 2007 can be found at the following location in the Group Policy Object Editor: Computer Configuration/Administrative Templates/Microsoft Office 2007 system (machine)/Security Settings/IE Settings Office InfoPath 2007 is a special case and cannot be configured by using the standard Internet Explorer feature control settings. Instead, you use the Windows Internet Explorer Feature Control Opt-In setting to configure Internet Explorer feature control settings for Office InfoPath 2007. This setting can be configured as follows: None. Opts out Infopath.exe and its associated components (Document Information Panel, Workflow forms, and third-party hosting) from all 15 Internet Explorer feature control settings. Infopath.exe, Document Information Panel, and Workflow forms . Opts-in everything except the third-party hosting component to all 15 Internet Explorer feature control settings. Infopath.exe, Document Information Panel, Workflow forms, and third-party hosting . This is the default setting. Infopath.exe and all three associated components are opted in to all 15 Internet Explorer feature control settings. You can find the Windows Internet Explorer Feature Control Opt-In setting at the following location on the Modify user settings page of the OCT: Microsoft Office InfoPath 2007 (machine)/Security You can find the Windows Internet Explorer Feature Control Opt-In setting at the following location in the Group Policy Object Editor:
242
Privacy options
Privacy options help you protect personal and private information. You can configure four main categories of privacy options in the 2007 Office system. The options can be configured in the OCT and through Group Policy. The four categories of privacy options are discussed below.
Document Inspector
You can disable the Inspector modules that are used by Document Inspector by enabling this option and adding the CLSID for an Inspector to the list of disabled Inspector modules.
You can find the CLSID for an Inspector module by looking at the registry entries that are listed under the following registry keys: HKEY_LOCAL_MACHINE/Software/Microsoft/Office/12.0/Excel/Document Inspectors HKEY_LOCAL_MACHINE/Software/Microsoft/Office/12.0/PowerPoint/Document Inspectors HKEY_LOCAL_MACHINE/Software/Microsoft/Office/12.0/Word/Document Inspectors Note: You cannot disable the Inspector module for Comments, Revisions, Versions, and Annotations, or the Inspector module for Document Properties and Personal Information. That is, there is no CLSID for these Inspector modules. You can find the Document Inspector option at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system (machine)/Miscellaneous You can find the Document Inspector option at the following location in the Group Policy Object Editor: Computer Configuration/Administrative Templates/Microsoft Office 2007 system (machine)/Miscellaneous
Option name
Default configuration
Description
Protect document metadata for rights managed Office Open XML files
Enabling this option encrypts metadata, such as author name, hyperlink references, and number of words, in Office Open XML Formats files that are restricted using IRM. Disabling this option prevents metadata, such as author name, hyperlink references, and number of words, from being encrypted in Office Open XML Formats files that are encrypted.
You can find these options at the following location on the Modify user settings page of the OCT: Microsoft Office 2007 system/Security Settings You can find these options at the following location in the Group Policy Object Editor: User Configuration/Administrative Templates/Microsoft Office 2007 system/Security Settings
244
This option is not enabled (that is, users are not enrolled in the Customer Experience Improvement Program).
Enabling this option opts users in to the Customer Experience Improvement Program (CEIP), which can reveal the IP address of a user's computer to Microsoft. Enabling this option allows a small file to be downloaded that enables Microsoft to provide users with help if they experience an abnormal number of program errors. Enabling this option can also reveal the IP address of a user's computer to Microsoft.
This option is not enabled (that is, users do not automatically receive small updates to improve reliability).
245
Option name
Default configuration
Description
Searches Microsoft Office Online for Help content when a computer is connected to the Internet.
Enabling this option and choosing the Never show online content or entry points setting prevents the Help system from accessing Office Online. It also prevents the Help system from displaying links to content that is on Office Online and prevents the Help system from downloading updated Help content. Enabling this option and choosing the Search only offline content whenever available setting forces the Help system to search only offline Help files, even when a computer is connected to the Internet. Enabling this option and choosing the Search online content whenever available setting enables the Help system to search Office Online for updated Help when a computer is connected to the Internet. This is the default setting. Note: This option is disabled by default in the French, German, and Italian versions of the 2007 Office system.
246
You can find these options at the following locations on the Modify user settings page of the OCT: Microsoft Office 2007 system/Privacy/Trust Center Microsoft Office 2007 system/Tools|Options|General|Services Options/Online Content You can also find these options at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office 2007 system/Privacy/Trust Center Microsoft Office 2007 system/Tools|Options|General|Services Options/Online Content
Enabling this option displays all tracked changes before users open or save documents. Can be configured only for Office PowerPoint 2007 and Office Word 2007. Enabling this option warns about tracked changes (revisions) and comments before users print, send, or save a document. Can be configured only for Office Word 2007. Enabling this option improves the accuracy of merging tracked changes by multiple authors. Can be configured only for Office Word 2007.
Warn before printing, saving, or sending a file that contains tracked changes or comments
No warning is displayed when a user prints or saves a file that contains tracked changes or comments.
You can find these options at the following locations on the Modify user settings page of the OCT: Microsoft Office PowerPoint 2007/PowerPoint Options/Security Microsoft Office Word 2007/Word Options/Security You can find these options at the following locations in User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office PowerPoint 2007/PowerPoint Options/Security Microsoft Office Word 2007/Word Options/Security
247
Block opening of pre-release versions of the file Enabling this setting prevents the opening of formats new to Excel 2007 pre-release (beta) versions of Office Open XML Formats files, such as .xlsb, .xlsx, .xlsm, .xltx, .xltm, and .xlam files. You can configure this setting in the OCT and through Group Policy. Block opening of Open XML file types Enabling this setting prevents the opening of Office Open XML Formats files, such as .xlsx, .slxm, .xltx, .xltm, and .xlam files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of Office 2007 binary format files, such as .xlsb files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of binary format files, such as .xls, .xla, .xlt, .xlm, .xlw, and .xlb files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of HTML and XML file types, such as .mht, .mhtml, .htm, .html, .xml, and .xmlss files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of XML file types, such as .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of DIF and SYLK file types, such as .dif and .slk files. You can configure this setting only through Group Policy.
248
Setting name
Description
Enabling this setting prevents the opening of text file types, such as .txt, .csv, and .prn files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of XLL file types, such as .xll files. You can configure this setting only through Group Policy.
The following table provides a description of each block open setting for Office PowerPoint 2007.
Setting name Description
Block opening of pre-release versions of the file Enabling this setting prevents the opening of formats new to PowerPoint 2007 pre-release (beta) versions of Office Open XML Formats files, such as .pptx, .pptm, .potx, .potm, .ppsx, and .ppsm files. You can configure this setting in the OCT and through Group Policy. Block opening of Open XML file types Enabling this setting prevents the opening of Office Open XML Formats files, such as .pptx, .pptm, .potx, .potm, .ppsx, .ppsm, .ppam, .thmx, and .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of Office binary file types, such as .ppt, .pot, .pps, and .ppa files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of HTML file types, such as .htm, .html, .mht, and .mhtml files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of files as outlines, such as .rtf, .txt, .doc, .wpd, .docx, .docm, and .wps files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of files that have a format that is previous to the PowerPoint 97 format, such as .ppt, .pot, .pps, and .ppa files. You can configure this setting only through Group Policy.
249
The following table provides a description of each block open setting for Office Word 2007.
Setting name Description
Block opening of pre-release versions of the file Enabling this setting prevents the opening of formats new to Word 2007 pre-release (beta) versions of Office Open XML Formats files, such as .docx, .docm, .dotx, and .dotm files. You can configure this setting in the OCT and through Group Policy. Block opening of Open XML file types Enabling this setting prevents the opening of Office Open XML Formats files, such as .docx, .dotx, .docm, .dotm, and .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of Office binary file types, such as .doc and .dot files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of HTML file types, such as .htm, .html, .mht, and .mhtml files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of Office 2003 XML file types, such as .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of RTF file types, such as .rtf files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of files through external converters, such as those for WordPerfect, that are installed with the 2007 Office system. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of TXT file types, such as .txt files. You can configure this setting only through Group Policy. Enabling this setting prevents the opening of pre-release binary format files. You can configure this setting only through Group Policy.
250
Setting name
Description
Enabling this setting enables you to prevent file formats that are older than a specific Office release from opening. You can configure this setting only through Group Policy.
The following table provides a description of each block save setting for Office Excel 2007.
Setting name Description
Enabling this setting prevents the saving of Office Open XML Formats files, such as .xlsx, .xlsm, .xltx, .xltm, and .xlam files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of Office 2007 binary file types, such as .xlsb files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of Office binary file types, such as .xls, .xla, .xlt, .xlm, .xlw, and .xlb files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of HTML and XML files types, such as .mht, .mhtml, .htm, .html, .xml, and .xmlss files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of XML file types, such as .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of DIF and SYLK file types, such as .dif and .slk files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of text file types, such as .txt, .csv, and .prn files. You can configure this setting only through Group Policy.
The following table provides a description of each block save setting for Office PowerPoint 2007.
251
Setting name
Description
Enabling this setting prevents the saving of Office Open XML Formats files, such as .pptx, .pptm, .potx, .potm, .ppsx, .ppsm, .ppam, .thmx, and .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of Office binary file types, such as .ppt, .pot, .pps, and .ppa files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of HTML file types, such as .htm, .html, .mht, and .mhtml files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of files as outlines, such .rtf, .txt, .doc, .wpd, .docx, .docm, and .wps files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of graphic file types, such as .jpg, .png, .tif, .bmp, .wmf, and .emf files. You can configure this setting only through Group Policy.
The following table provides a description of each block save setting for Office Word 2007.
Setting name Description
Enabling this setting prevents the saving of Office Open XML Formats files, such as .docx, .dotx, .docm, .dotm, and .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of Office binary file types, such as .doc and .dot files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of HTML file types, such as .htm, .html, .mht, and .mhtml files. You can configure this setting only through Group Policy.
252
Setting name
Description
Enabling this setting prevents the saving of Office 2003 XML format files, such as .xml files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of RTF file formats, such as .rtf files. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of files through converters, such as the WordPerfect converter that is included in the 2007 Office system. You can configure this setting only through Group Policy. Enabling this setting prevents the saving of TXT file types, such as .txt files. You can configure this setting only through Group Policy.
By default, users cannot open files that have been saved in a format previous to the Word 6.0 format. Files that have been saved using a beta version of Word 6.0 are considered to be previous to the Word 6.0 format and cannot be opened by default. You can find these settings at the following locations on the Modify user settings page of the OCT: Microsoft Office Excel 2007/Block file formats Microsoft Office PowerPoint 2007/Block file formats Microsoft Office Word 2007/Block file formats You can find these settings at the following locations in the User Configuration/Administrative Templates node of the Group Policy Object Editor: Microsoft Office Word 2007/Block file formats Microsoft Office PowerPoint 2007/Block file formats Microsoft Office Word 2007/Block file formats
253