Deployment for the 2007 Office release

Microsoft Corporation Published: June 2009 Author: Microsoft Office System and Servers Team (o12ITdx@microsoft.com)

Abstract
This book provides how-to information: the recommended steps to execute specific deployment tasks, such as customizing the installation, installing 2007 Microsoft Office system on users' computers, implementing the deployment in many languages, and migrating to the new file format. Microsoft Office Outlook 2007 deployment tasks are also included in this book. The audiences for this book are IT professionals who plan, implement, and maintain Office installations in their organizations. The content in this book is a copy of selected content in the 2007 Office release technical library (http://go.microsoft.com/fwlink/?LinkId=84741) as of the 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 document 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, e-mail address, logo, person, place or event is intended or should be inferred. 2009 Microsoft Corporation. All rights reserved. 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.

iii

Contents
Deployment for the 2007 Office release...................................................................................1 Abstract.......................................................................................................................1 Contents..................................................................................................................................iv Getting Help...........................................................................................................................xiii I Configuring the installation....................................................................................................1 Create a network installation point for the 2007 Office system.................................................2 Replicate the network installation point..............................................................................3 Secure the network installation point..................................................................................4 Customize the 2007 Office system...........................................................................................5 Customize Setup before installing the 2007 Office system.......................................................7 Installing Office quietly.......................................................................................................8 Configure feature installation states of the 2007 Office system..............................................10 Configure a silent installation of the 2007 Office system by using Config.xml........................14 Modifying the Config.xml file to configure a silent installation...........................................14 Configure user settings for the 2007 Office system................................................................16 Create different configurations of the 2007 Office system for different groups of users..........18 Configure Outlook 2007..........................................................................................................20 Customize Outlook profiles by using an Outlook Profile (PRF) file.........................................21 PRF file features in Office Outlook 2007..........................................................................21 Using Outlook 98 and Outlook 2000 PRF files.................................................................21 Creating and updating PRF files......................................................................................22 Creating PRF files by using the Office Customization Tool........................................22 Manually editing PRF files.........................................................................................22 Applying Outlook user profiles by using a PRF file...........................................................24 Configure Outlook with Exchange Server...............................................................................25 Configure Cached Exchange Mode in Outlook 2007..............................................................26 Configure Cached Exchange Mode settings by using the Office Customization Tool.......27 Configure Cached Exchange Mode settings by using Group Policy................................28 Configure Exchange Server send/receive settings in Outlook 2007.......................................32 More about configuring send/receive settings..................................................................33 iv

Defining custom Send/Receive groups......................................................................33 Configuring Send/Receive settings for a Send/Receive group..................................34 Configuring Offline Address Book download options.................................................34 Configure Outlook Anywhere in Outlook 2007........................................................................35 More about configuring Outlook Anywhere......................................................................38 Software requirements...............................................................................................38 Understanding Outlook Anywhere configuration settings...........................................38 Deploying Outlook Anywhere after deploying Outlook...............................................39 Outlook Anywhere configuration with Exchange 2007...............................................39 Configure Outlook for information sharing and integration.....................................................40 Configure Internet Calendars in Outlook 2007........................................................................41 More information about configuring Internet Calendars...................................................42 Disabling Internet Calendar subscriptions.................................................................42 Providing Internet Calendar subscriptions to users....................................................43 Synchronization interval for Internet Calendars.........................................................43 Configure Really Simple Syndication (RSS) in Outlook 2007.................................................44 More information about configuring RSS.........................................................................46 About RSS.................................................................................................................46 Disable RSS integration.............................................................................................46 Provide RSS Feeds to users.....................................................................................46 Customize the RSS synchronization interval.............................................................47 Disable RSS roaming................................................................................................47 RSS folder home pages.............................................................................................47 Creating a custom RSS folder home page..........................................................................47 Configure Instant Messaging integration options in Outlook 2007..........................................49 More information about Instant Messaging settings.........................................................50 Configure Meeting Workspace options in Outlook 2007.........................................................51 Using policies to define server lists and other user options..............................................52 Configuring server list behavior for meeting organizers.............................................52 Specifying a list of servers and default templates......................................................53 Configuring Meeting Workspace integration when using a POP Server...........................54 More about TNEF support.........................................................................................55 Ensuring that rich transport is used...........................................................................55 Set Rich Text Format...........................................................................................................56 Do not send an iCalendar attachment.................................................................................56 Viewing error message logs.............................................................................................56 Configure general Outlook features........................................................................................58 Configure Instant Search options in Outlook 2007.................................................................59 More information about configuring Instant Search..........................................................60 v

Configure categories in Outlook 2007....................................................................................62 Categories and flags migration.........................................................................................62 Configure Search Folder options in Outlook 2007..................................................................64 More information about configuring Search Folders.........................................................65 Disable the Group By feature for e-mail messages in Outlook 2007......................................66 Configure Navigation Pane options in Outlook 2007..............................................................67 Options you can configure for Navigation Pane modules.................................................67 Configure notification area messages in Outlook 2007..........................................................70 More information about notification area messages.........................................................70 Configure retention settings and AutoArchive in Outlook 2007...............................................72 Configuring retention settings...........................................................................................72 Configuring AutoArchive settings.....................................................................................73 How AutoArchive works in Outlook..................................................................................74 Scheduling automatic archiving.................................................................................74 Archive folder location...............................................................................................75 How retention settings work in Outlook............................................................................75 Working with Outlook archiving and Exchange document management..........................75 Configure Unicode options in Outlook 2007...........................................................................77 More information about configuring Unicode....................................................................78 Choosing between Unicode or non-Unicode mode....................................................78 Coordinating Cached Exchange Mode and Unicode deployment..............................79 Facilitating usage of Unicode mode by Outlook.........................................................79 Enforcing Unicode mode for Outlook users...............................................................80 Using Unicode format for Outlook messages dragged to the desktop.......................81 Configure automatic message encoding options in Outlook 2007..........................................82 More information about automatic messaging encoding in Outlook.................................83 How automatic message encoding works..................................................................83 Setting default encoding for outbound messages......................................................84 Outlook encoding support..........................................................................................84 Configure LDAP options in Outlook 2007...............................................................................87 Configuring LDAP directory browsing..............................................................................87 Disabling directory browsing......................................................................................87 More information about LDAP directory browsing......................................................87 Default and customized check names filters....................................................................88 Default LDAP filters...................................................................................................88 Defining customized LDAP filters...............................................................................89 Mapping server LDAP properties to Outlook MAPI properties...................................90 Example: Defining LDAP options in a custom PRF file....................................................91 Configure Outlook security and protection features................................................................93 vi

Set consistent Outlook 2007 cryptography options for an organization..................................94 More information about setting Outlook cryptography options.........................................96 Outlook security policy settings..................................................................................96 Security policy settings for general cryptography.....................................................100 Security policy settings for KMS-issued certificates.................................................101 Specify the method Outlook uses to manage virus prevention features...............................102 More information about managing virus prevention settings..........................................102 Migrating to Group Policy settings...........................................................................103 Updated Object Model Guard..................................................................................103 Customize attachment settings in Outlook 2007...................................................................104 Add or remove Level 1 file types....................................................................................105 Add or remove Level 2 file types....................................................................................106 Additional attachment security settings..........................................................................107 Customize programmatic settings in Outlook 2007..............................................................109 Customize ActiveX and custom forms security settings in Outlook 2007..............................112 Customizing how ActiveX controls behave in one-off forms...........................................112 Customizing custom forms security settings...................................................................113 Manage trusted add-ins for Outlook 2007.............................................................................115 Working with Outlook COM add-ins................................................................................116 Configure security for Outlook 2007 folder home pages.......................................................117 More information about Outlook folder home pages.......................................................117 Configure junk e-mail settings in Outlook 2007.....................................................................118 Configuring the Junk E-mail Filter..................................................................................118 Configuring automatic picture download........................................................................120 More about automatic picture download..................................................................121 Configure Information Rights Management in Outlook 2007................................................122 Disable IRM....................................................................................................................123 Configure automatic license caching..............................................................................123 Enforce e-mail expiration...............................................................................................123 Do not use Outlook for e-mail address validation...........................................................124 Configure Information Rights Management..........................................................................125 Configuring IRM Group Policy settings..........................................................................125 Configuring IRM registry key options.............................................................................127 II Installing on client computers...........................................................................................132 Run Setup for the 2007 Office system on users' computers.................................................133 Deploy the 2007 Office system to users who are not administrators....................................134 Logging on as an administrator......................................................................................134 vii

Assigning Office to the computer...................................................................................135 Deploying Office with Group Policy computer startup scripts.........................................135 Using a software management tool................................................................................135 Precache the local installation source for the 2007 Office system........................................137 Run Setup from the local installation source to install the 2007 Office system.....................139 Office product download codes......................................................................................140 Sequentially install multiple products of the 2007 Office system..........................................143 How it works...................................................................................................................145 Stage deployment of applications in the 2007 Office system................................................147 How it works...................................................................................................................148 Deploy the 2007 Office system on a Terminal Services-enabled computer..........................149 Planning the Terminal Services environment.................................................................149 Evaluating licensing requirements...........................................................................149 Evaluating software requirements............................................................................149 Server requirements.........................................................................................................150 Client requirements...........................................................................................................150 Evaluating recommended guidelines and best practices.........................................151 Single point of failure........................................................................................................151 Terminal server hardware..................................................................................................151 Office Outlook 2007..........................................................................................................151 Terminal Services installation requirements......................................................................151 Stop the Microsoft Office Button from blinking..................................................................152 Customizing the 2007 Office release.............................................................................152 Installing the 2007 Office release onto a Terminal Services-enabled computer.............153 Manually install the 2007 Office release..................................................................154 Perform an automated installation of the 2007 Office release.................................154 Removing the default user name...................................................................................155 Deploy custom templates in the 2007 Office system............................................................157 Create and save custom templates................................................................................158 Creating thumbnail and preview files.............................................................................158 Create a custom XML file that describes the custom templates.....................................159 Configure Office to use the custom templates................................................................160 Sample XML text............................................................................................................161 Validating your XML file for custom templates................................................................162 Deploy Access 2007 applications.........................................................................................167 Separating data and logic..............................................................................................167 Using Access 2007 Runtime..........................................................................................168 Deciding which file format to use....................................................................................169 Packaging an application...............................................................................................170 Package a split database.........................................................................................171 viii

Package and sign an Office Access 2007 database................................................171 Apply an Outlook Profile (PRF) File to configure Outlook profiles........................................173 Distribute Electronic Business Cards in Outlook 2007..........................................................175 Options for adding employee contact information to cards............................................175 Obtain sample solutions for distributing Electronic Business Cards...............................178 Sample solution packages.......................................................................................178 Working with the SharePoint sample solution: overview..........................................180 Working with the .NET sample solution: overview...................................................182 Templates for Electronic Business Cards.......................................................................184 Creating a business card in a new Outlook contact.................................................184 Saving an Electronic Business Card template on a Web server..............................184 Creating a preview image of the Electronic Business Card.....................................185 Using a SharePoint site for distributing business cards.................................................185 Create a C# Class Library project............................................................................186 Sign the assembly with a strong name key..............................................................187 Specify options for your customized solution...........................................................189 Add required references..........................................................................................189 Retrieve contact information by accessing SharePoint User Profiles......................190 Use site templates for a consistent look..................................................................191 Host the new page in your SharePoint site..............................................................192 Copy the solution to the Global Assembly Cache....................................................192 Using a .NET 2.0 internal Web site for distributing business cards................................192 Opening a current Web site in Visual Studio............................................................193 Specify options for your customized solution...........................................................193 Add required references..........................................................................................194 Connect to Active Directory.....................................................................................194 Query Active Directory for employee contact information........................................195 Access contact information in Active Directory query results...................................195 Create and deploy Junk E-mail Filter lists in Outlook 2007...................................................197 Create the lists...............................................................................................................197 Deploy the lists...............................................................................................................198 III Deploying internationally..................................................................................................200 Customize and deploy multiple language versions of the 2007 Office system.....................201 Understanding the Setup logic for Shell UI language.....................................................203 Deploy a default language version of Office...................................................................203 Specify which languages to install..................................................................................204 Deploy different languages to different groups of users.................................................206 Identify installed languages............................................................................................207 Customize language settings for the 2007 Office system.....................................................208 Methods of customizing language settings....................................................................208 Use policies to enforce language settings...............................................................208 ix

Use a Setup customization file to specify default language settings........................209 Use the Language Settings tool to modify language settings..................................210 Customize language-specific settings related to user locale..........................................211 Deploy proofing tools for the 2007 Office system.................................................................213 Determining the method for deploying Proofing Tools....................................................213 Deploying the Office Proofing Tools Kit 2007.................................................................214 Customizing an installation of the Office Proofing Tools Kit 2007............................214 Syntax...............................................................................................................................214 Attributes...........................................................................................................................214 Proofing Tools Config.xml OptionState Id values..............................................................215 Example Config.xml file for Office Proofing Tools Kit 2007...............................................217 Installing the Office Proofing Tools Kit 2007 on an individual computer...................220 Precaching the local installation source for the Office Proofing Tools Kit 2007........221 Identifying companion languages...................................................................................221 Add or remove languages after deploying the 2007 Office system.......................................224 Deploy language packs..................................................................................................224 Remove language packs................................................................................................226 Identify installed languages............................................................................................227 IV Using enterprise deployment tools..................................................................................229 Use Group Policy to assign computer startup scripts for 2007 Office deployment...............230 Group Policy Scripts Extension Overview......................................................................230 Advantages of using computer startup scripts for deploying 2007 Office.......................230 Assigning computer startup scripts................................................................................232 Example...................................................................................................................233 Specifying Silent Install Options in Config.xml File..................................................235 Deploying Computer Startup Scripts........................................................................235 Specifying maximum time for startup scripts to run.................................................236 Deploy the 2007 Office system by using System Center Essentials 2007............................238 What this article includes...............................................................................................238 Preparing to deploy the 2007 Office system by using System Center Essentials..........239 System Center Essentials tasks you must complete before you deploy the 2007 Office system........................................................................................................239 2007 Office customization tasks you must complete before you deploy the 2007 Office system by using System Center Essentials...............................................240 Deploying the 2007 Office system by using System Center Essentials.........................241 Deploy the 2007 Office system by using System Center Configuration Manager 2007........244 Overview........................................................................................................................244 Audience..................................................................................................................244 Prerequisites............................................................................................................244 Introduction to the deployment process.........................................................................245 Deploying the 2007 Office system in a test environment................................................245 x

Network environment...............................................................................................246 Procedural steps for deploying the 2007 Office system by using Configuration Manager 2007...............................................................................................................................246 Resources for deploying the infrastructure.....................................................................251 Active Directory, DNS, DHCP..................................................................................252 SQL Server 2008.....................................................................................................252 System Center Configuration Manager 2007 R2 (Management Point, Distribution Point)....................................................................................................................252 Windows Vista Enterprise, System Center Configuration Manager client................252 Using Systems Management Server 2003 to deploy the 2007 Office system......................253 Use Group Policy Software Installation to deploy the 2007 Office system............................254 Overview of Group Policy Software Installation..............................................................254 Deploying 2007 Office with Group Policy Software Installation......................................254 Deployment considerations............................................................................................255 Using Group Policy Software Installation.......................................................................256 Deploying new installations of Office.......................................................................257 Upgrading previous versions of Office.....................................................................258 How it works...................................................................................................................259 Applying customizations to the Office installation...........................................................259 Modifying the Config.xml file OptionState element..................................................260 OptionState Syntax...........................................................................................................260 OptionState Id Values.......................................................................................................261 Config.xml file OptionState Id values....................................................................................263 OptionState Id values.....................................................................................................263 V Migrating to the 2007 Office system.................................................................................271 Migrate Word, Excel, and PowerPoint files to the 2007 Office system.................................272 Convert files in bulk with OMPM....................................................................................272 Ofc.ini Settings.........................................................................................................273 Example 1.........................................................................................................................278 Example 2.........................................................................................................................278 Use VET for extracting versions of Word files................................................................279 VET error messages................................................................................................280 Using Group Policy to set default file save options...............................................................281 Deploying the Microsoft Office Compatibility Pack...............................................................284 Microsoft Office Compatibility Pack deployment............................................................284 VI Deployment Strategies for the 2007 Office release.........................................................285 Step-by-step guides..............................................................................................................286 Configure the 2007 Office system for a hard disk image (step-by-step)...............................287 xi

How it works...................................................................................................................288 Next step........................................................................................................................288 More information............................................................................................................288 Deploy the 2007 Office system with limited network capacity...............................................290 Recommended solution.................................................................................................290 How it works...................................................................................................................290 Deploy multiple customization patches (step-by-step)..........................................................292 Deploy customizations of the 2007 Office system to users in the field (step-by-step)..........296 Update calendars to match 2007 daylight saving time rules (step-by-step)..........................300 Options for updating mailboxes......................................................................................301 Deploy custom configurations of the 2007 Office system (step-by-step)..............................304 Config.xml example........................................................................................................314

xii

Getting Help
Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at: http://technet.microsoft.com/office If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at: o12ITdx@microsoft.com If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at: http://support.microsoft.com

xiii

I Configuring the installation

Create a network installation point for the 2007 Office system

Typically, the first step in a corporate deployment of the 2007 Microsoft Office system is to create a network installation point. To do this, you copy all the source files from your Office CD to a shared location on the network. Users run Setup from the network installation point, or you use the installation point as a starting place to create a hard-disk image or a custom CD or to distribute Office by using a deployment tool such as Microsoft Systems Management Server. To create a network installation point 1. Create a folder for the Office source files at an accessible location on the network server. For example: \\server\share\Office12 Note: Do not create the network installation point at the root of the server. 2. Insert the Office CD into your CD drive. 3. In Windows Explorer, select all the files and folders on the CD. Copy the CD contents to the folder on the network. This location becomes your network installation point. 4. If you are deploying multiple language versions of Office, copy each language pack you want from the source media to the installation point. When you are prompted to overwrite duplicate Setup files, click No. In the 2007 Office system, core Setup files are shared among all Office products and language packs. Because these files are identical, there is no reason to overwrite the files. Additionally, by not overwriting Setup files, the network installation point remains online and available to users while you add files. 5. If you are deploying multiple Office products, copy those files from the CD to the installation point. When you are prompted to overwrite duplicate Setup files, click No. 6. If you create a Setup customization file (MSP file) for the installation, store the file in the Updates folder at the root of the installation point. Alternatively, you can use the /adminfile option to specify a Setup customization file on the command line. 7. If users are installing Office after product updates are released, store those MSP files in the Updates folder.

The amount of space required on the network installation point varies by product and by language. The following table shows space requirements for English versions of the 2007 Office system suites that are typically installed in enterprise organizations. These figures account for both the installed product and the installation files stored in the local installation source. Microsoft Office Standard 2007 Microsoft Office Professional Plus 2007 Microsoft Office Enterprise 2007 660 MB 980 MB 1 GB

The installation point contains only one copy of the language-neutral core product. Each language that you add requires additional space only for the language-specific components. For example, the U.S. English and the French versions of Office Enterprise 2007 require approximately 1 GB of space each on the servermore than 2 GB in total. Because the language-neutral components are not duplicated, however, a network installation point that includes both languages requires only about 1.75 GB of space. The amount of disk space that you save increases as you add more languages. For detailed system requirements for all the products in the 2007 Office system, see 2007 Microsoft Office release system requirements (http://go.microsoft.com/fwlink/?LinkId=78026). Note Unlike previous versions of Microsoft Office products, in the 2007 Office system you do not create an administrative installation point by running Setup with the /a command-line option to extract compressed source files. In the 2007 Office system, all installations occur from the compressed source.

Replicate the network installation point

In most enterprise organizations, the network installation point is the location from which users initially install Office. After Office is installed, users do not typically need to rely on the network source for tasks such as updating, modifying, or reinstalling Office. Setup automatically creates a local installation source on each user's computer. If the local source is corrupted or deleted, however, Setup returns to the original network source to recreate the local source on the user's computer. Replicating the network source to multiple locations is recommended for the following reasons: Availability. Creating multiple network installation points (which may or may not be in the same physical location) helps ensure that users always have access to a network source. Ideally, the duplicate network installation points are managed by Distributed File System (DFS) technologies and are transparent to users. Proximity to users. Many companies have high-speed LAN networks that are connected to other subsidiaries or branch offices by much slower WAN connections. Setting up a duplicate network installation point at the remote locations means that Office source files 3

travel over the slow network connection only once; thereafter, users have access to a network source closer to them. Consistency. By creating one network installation point with all the customizations you want and then duplicating that installation point as needed, you help ensure that the same configuration is deployed throughout your organization. Flexibility. If the primary network installation point installs a standard corporate configuration of Office, regional offices can apply additional customizations to the replicated network installation points and customize Office for their unique region-specific requirements. To specify additional network sources 1. Start the Office Customization Tool (OCT) by running Setup with the /admin command-line option. 2. On the Additional Network Sources page, click Add. Enter the path to the location to which you plan to copy the network installation point. You can add as many additional source locations as you need. 3. Save the Setup customization file (MSP file) generated by the OCT in the Updates folder at the root of the network installation point. 4. Copy the entire folder structure of the network installation point to the locations you specified in the Setup customization file. Users who install Office from any of these network installation points have access to the backup network sources. Setup checks these sources automatically when an alternate source is required.

Secure the network installation point

Follow these recommended best practices to help make the network installation point for Office secure: Make sure that access to source files is read-only. The Setup.xml and Package.xml files are digitally signed and cannot be modified. Save all customization files that you create, including Setup customization files and custom Config.xml files, as read-only. If you are centralizing log files on the network, make sure that users have read/write access to that location. Make sure that all users have administrative rights before installing Office; you can accomplish this by using your existing software deployment infrastructure.

Customize the 2007 Office system

After you create a network installation point, but before you install the 2007 Microsoft Office system, you can use the Office Customization Tool (OCT) to create a Setup customization file to configure the installation for your users. You can use the OCT to alter the way that Setup performs the installation and to configure Office applications on the user's computer. Using the OCT to customize Office 1. From the root of the network installation point, run the following command line to start the Office Customization Tool: \\server\share\setup.exe /admin. 2. In the Select Product dialog box, select a single product that you want to customize, and click OK. 3. In the left pane, select an area of customization and customize the options available in the right pane. For example, to configure Setup to run quietly, select Licensing and user interface in the left pane, and choose None for Display level in the right pane. 4. When you finish making your customizations, select Save As... in the File menu. 5. Specify a unique name for the file and save the file in the Updates folder of the network installation point. 6. Click Save. When you run Setup.exe from the network installation point, Setup looks in the Updates folder for Setup customization files for the product that you are installing. Setup then applies your customizations to the installation. The following topics offer more information on how to customize specific aspects of the installation: To customize the default behavior of Setup during installation, see Customize Setup before installing the 2007 Office system. To customize which Office features are installed on the user's computer, see Configure feature installation states of the 2007 Office system. To customize the user's default environment during installation, see Configure user settings for the 2007 Office system. For complete information about the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). The following customizations can only be made using the Config.xml file: Specifying the path to the network installation point Selecting which product to install

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 5

Copying the local installation source (LIS) to the user's computer without installing Office Adding or removing languages from the installation

For more information on how to use the Config.xml file, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx) Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx)

Customize Setup before installing the 2007 Office system

In the 2007 Microsoft Office system, Setup controls the entire installation, including processes that Windows Installer handled in previous Office versions. Customizing the default behavior of Setup allows you to control the process for example, to run the installation without user interaction, to handle the product key and the Microsoft Software License Terms on behalf of users, and to specify an organization name or a different installation location. To customize the way Setup manages the installation process, use the Office Customization Tool (OCT) to create a Setup customization file (MSP file). Setup applies this file when users install Office on their computers. To customize Office Setup 1. Create a network installation point by copying all the files and folders from the Office CD to a folder on the network. 2. From the root of the network installation point, run the following command line to start the Office Customization Tool: setup.exe /admin 3. Select the product that you want to configure, and then click OK. 4. In the left pane, click Installation location and organization name. 5. In the Default installation path box, enter the path to a default installation location on users' computers; you can enter a relative path that includes the folder keyword [ProgramFilesFolder]. 6. In the Organization name box, enter a default organization name for all users who install Office with this customization file. 7. In the left pane, click Additional network sources, and then click Add. 8. In the Network server box, enter the path to any backup sources that you have created on the network. If neither the user's local installation source nor the original network installation point is available, Setup uses one of these replicated installation points for operations that require the source; you can add as many sources as you need. 9. In the left pane, click Licensing and user interface. 10. In the Product Key box, enter a valid 25-character volume license key, and then select the I accept the terms in the License Agreement check box. When you provide this information in a Setup customization file, users are not prompted for a product key or Microsoft Software License Terms during the installation or the first time they start an Office application. 11. In the right pane, set the Display Level to Basic or None to install Office quietly (without user interaction). More information about display settings is provided later in this 7

topic. Notes 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 Microsoft Software License Terms 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 any Office files are 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. 12. Make any additional customizations, then click Save on the File menu and save the Setup customization file in the Updates folder at the root of the network installation point. Your customizations apply to any language version of the specified product that is available on the network installation point. Most customizations apply to the language-neutral core product. However, the feature tree in the tool also includes a subset of language-specific features. Customizations to language-specific features are applied when a user installs that language; otherwise, they are ignored. Note: Typically, you do not need to customize logging options. By default, Setup creates a standard log file and saves it as a text file in the %Temp% folder on the user's computer. If an installation fails, Setup creates a verbose log file, starting with the package that caused the failure, in the same location. To change logging options, open the Config.xml file in Notepad and modify the <Logging> element. For more information, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

Installing Office quietly

When you deploy Office throughout an organization, you determine how much of the Setup user interface is displayed to users. By default, Setup runs interactively and presents users with choices during the installation. If you are distributing a customized configuration, it is recommended that you limit how much users interact with Setup. The installation proceeds with fewer interruptions, and your customizations are set by default for all users. For more information about display options, see Licensing and user interface in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). If you are using a deployment tool such as Microsoft Systems Management Server to deploy Office while users are not logged on to the network, set the display level to None, which installs Office without any Setup user interface.

Note: When you install Office quietly, you must enter a valid product key. If the product key is missing, Setup logs an error and exits. If you do not accept the license terms on behalf of users, Setup does complete the installation; however, by installing Office quietly, you have implicitly accepted the license terms. The Windows Installer properties DISPLAY and PIDKEY do not work in the 2007 Office system; instead, you customize Setup directly by specifying a display setting and entering a product key in the OCT, as described earlier in this topic. Because Setup plays a more significant role in controlling the installation, many Windows Installer properties are no longer needed. In fact, some Windows Installer properties are blocked and generate an error if you try to set them using the Office Customization Tool. For a complete list of the Setup properties you can use with the 2007 Office system, as well as a list of blocked or unsupported properties and their corresponding new mechanisms, see Setup properties in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179018.aspx). To chain additional Office product installations to your primary installation, edit the Config.xml file to run additional instances of Setup. Chaining also requires a quiet display level (the Basic or None display setting). For more information, see Sequentially install multiple products of the 2007 Office system.

Configure feature installation states of the 2007 Office system

After you create a network installation point but before you install the 2007 Microsoft Office system, you can use the Office Customization Tool (OCT) to create a Setup customization file to configure the installation for your users. You can use the OCT to change the default way that Office features are installed, setting some to be installed on the user's computer, some to be installed only on first use, and some not to be installed. You can even hide or lock features so that a user running Setup interactively cannot change what you have configured. To configure Office feature installation states 1. From the root of the network installation point, run the following command line to start the Office Customization Tool: setup.exe /admin. 2. Select the product that you want to configure, and then click OK. 3. In the left pane, under Features, click Set feature installation states. 4. In the right pane, expand the tree and select the feature that you want to customize. For example, to not install the Equation Editor, expand Microsoft Office and Office Tools, and then for Equation Editor select the installation options Not Available, Hidden, and Locked. Setup does not install the Equation Editor and, if Setup is run interactively, this feature is not visible and the user cannot install it. 5. On the File menu, click Save As. 6. Specify a path and file name for the Setup customization file, and then click Save. 7. On the File menu, click Exit. 8. Copy the Setup customization file to the Updates folder in the network installation point. When you run Setup to install Office, it uses the customization file it finds in the Updates folder and configures Office features according to your customizations.

10

The following table describes the available installation options:

Option Description

Run from My Computer

Setup copies files and writes registry entries and shortcuts associated with the feature to the user's hard disk, and the feature (or application) runs on the user's computer. Same as Run from My Computer, except that all child features belonging to the feature are also set to this state. Setup leaves components for the feature and all its child features in the local installation source until the user first attempts to use the feature, at which time the components are copied to the Office program folder on the user's local hard disk. Some features do not support Installed on First Use; this option is not available for these features in the OCT. The components for the feature, and all of the child features belonging to that feature, are not installed on the user's computer.

Run all from My Computer Installed on First Use

Not Available

11

Option

Description

Hidden

The feature and all of its child features do not appear in the feature tree when Setup runs interactively. Setup uses the default installation state, or the state specified in the customization file, to determine how to install the feature. Notes If you set the Hidden option for a specific feature by using the OCT or the Config.xml file during an initial installation of the 2007 Office system, you cannot unhide that feature in the feature tree by using another Config.xml file or applying a second MSP customization 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 uninstall 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=Absent Children=force /> You can also use the OCT to create an MSP customization file to install the feature later by setting the feature installation state to Run All from My Computer on the Set feature installation states screen.

12

Option

Description

Locked

The feature cannot be changed by the user during interactive Setup or maintenance mode.

When you change the installation state of a feature, Setup might change the installation state of a parent or child feature to match. For more information, see Set feature installation states in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). See Also Create a network installation point for the 2007 Office system Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)

13

Configure a silent installation of the 2007 Office system by using Config.xml

The Config.xml file is used to configure installation tasks and is used only while running Setup. It is not installed or cached on users' computers. You can edit the Config.xml file to customize the installation. By default, the Config.xml file that is stored in the core product folders (core_product_folder_name.WW folder, for example, Enterprise.WW or Pro.WW) directs Setup to install that product. For example, the Config.xml file in the Pro.WW folder installs Microsoft Office Professional 2007.

Modifying the Config.xml file to configure a silent installation

To configure a silent installation (unattended installation) of a 2007 Microsoft Office system product that requires no user interaction, modify the Config.xml file for the product you are installing and set the Display element's Level attribute to "none" (Display Level="none"), and then save the Config.xml file, as shown in the following procedure. The Display element specifies the level of user interface that Setup displays to users. Specify silent installation options in Config.xml 1. Open the Config.xml file for the Office product (such as Office Professional 2007) that you are installing by using a text editor tool such as Notepad. 2. Locate the line that contains the Display element, as shown in the following example: <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> 3. Modify the Display element entry with the silent options that you want to use. For example, use the following syntax: <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> These options will direct Setup to run silently, prevent prompting users to enter information, and prevent the installation from waiting for any user interaction. For more information about the syntax and Config.xml, see Display element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). 4. Save the Config.xml file. Make sure that no Office applications are running when you install the 2007 Office system. For example, to install Office Professional 2007 after you modify the Config.xml file to specify silent install options, use the following command: \\server\share\setup.exe /config \\server\share\Pro.WW\config.xml 14

where: \\server\share is the path to the Office Professional 2007 source files /config is a Setup command-line option that specifies the location of the Config.xml file. See Setup command-line options for the 2007 Office system (http://technet.microsoft.com/enus/library/cc178956.aspx). \\server\share\Pro.WW\config.xml is the location of your modified Config.xml file for Office Professional 2007. For information about customizing your Office installation, see Deploy custom configurations of the 2007 Office system (step-by-step). You can also set silent install options by using the Office Customization Tool (OCT). For information, see the Display level and license agreement settings in Licensing and user interface in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx).

15

Configure user settings for the 2007 Office system

After you create a network installation point but before you install the 2007 Microsoft Office system, you can use the Office Customization Tool (OCT) to create a Setup customization file. There are many user settings that you can configure in the OCT to customize the user's environment. For example, using the OCT, you can configure the default settings for several AutoCorrect options in Microsoft Office Word 2007. When you configure a user setting, that setting is in place when the user first runs an Office application. Note: Configuring a user setting in this way is not necessarily permanent; it just establishes the initial default value for the setting. The user can modify most settings after Office is installed. To enforce a user setting, use Group Policy. For more information, see Enforce settings by policy in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179081.aspx). To configure user settings 1. From the root of the network installation point, run the following command line to start the Office Customization Tool: setup.exe /admin. 2. Select the product that you want to configure, and then click OK. 3. In the left pane, click Modify user settings. 4. In the right pane, expand the tree, double-click the user setting that you want to configure, and select a value. For example, to set the default format in which you want users to save Office Word 2007 files, expand Microsoft Office Word 2007, expand Word Options, click Save, and then double-click Save files in this format under Setting. Click Enabled, select the format under Save files in this format, and then click OK. 5. If you want to preserve user settings from previous versions of Office, except for those settings you explicitly customize in the OCT, select Migrate user settings. 6. On the File menu, click Save As. 7. Specify a path and file name for the Setup customization file, and then click Save. 8. On the File menu, click Exit. 9. Copy the Setup customization file to the Updates folder in the network installation point. When you run Setup to install Office, it uses the Setup customization file in the Updates folder and configures user settings.

16

See Also Create a network installation point for the 2007 Office system Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)

17

Create different configurations of the 2007 Office system for different groups of users
If you have groups of users with different needs, you can create unique configurations of the 2007 Microsoft Office system for each group by using the Office Customization Tool (OCT) to create a unique Setup customization file for each group. You then install Office for the users by specifying the customization file on the Setup command line.
Steps Reference

Create a network installation point for Office. In the root of the network installation point, create a folder for your Setup customization files. Do not put your customization files in the Updates folder. Setup automatically applies customization files it finds in this folder during installation. Instead, you direct Setup to use only the customization file you specify on the command line, as described later in this procedure.

Create a network installation point for the 2007 Office system

Start the OCT by running Setup from the network Office Customization Tool in the installation point. Specify the /admin command-line 2007 Office system option; for example, \\server\share\setup.exe /admin. (http://technet.microsoft.com/enus/library/cc179097.aspx) Make customizations you need for the first group of users. Click Save on the File menu. Specify a unique name for the Setup customization file. Save the file in the folder you created. Repeat the process to create a unique Setup customization file for each group of users. Run Setup for the users within each group. Specify the appropriate Setup customization file by using the /adminfile command-line option. For example, to install Office for users in the Accounting department, run \\server\share\setup.exe /adminfile \\server\share\custom\accounting.msp. Run Setup for the 2007 Office system on users' computers

18

Notes For an alternate method, see Create a custom configuration for a group of users by using a separate installation folder. You can also use the Config.xml file to customize your Office installation. For more information, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx)

19

Configure Outlook 2007

In this section: Customize Outlook profiles by using an Outlook Profile (PRF) file Configure Outlook with Exchange Server Configure Outlook for information sharing and integration Configure general Outlook features Configure Outlook security and protection features Configure Information Rights Management in Outlook 2007

20

Customize Outlook profiles by using an Outlook Profile (PRF) file

The Microsoft Office Outlook 2007 profile file (PRF file) allows you to quickly create MAPI profiles for users. By using a PRF file, you can set up new profiles for users or modify existing profiles without affecting other aspects of your installation. You can also manually edit a PRF file to customize Office Outlook 2007 to include Office Outlook 2007 settings or MAPI services that are not included in the Office Customization Tool (OCT) user interface.

PRF file features in Office Outlook 2007

As in earlier versions of Outlook, you can continue to use the PRF file to provide options for specifying additional Outlook settings or MAPI services and to verify account settings. The Office Outlook 2007 PRF file format is the same as the PRF file format for Outlook 2003 and Outlook 2002. This file format combines the features included in two previous PRF file formats (used with Outlook 2000 and earlier). One format was designed for the Outlook tool Newprof.exe. The other format worked with the Modprof.exe tool for Outlook 2000. Note: The Outlook tools Newprof.exe and Modprof.exe are no longer required. The tools do not work with Office Outlook 2007, Outlook 2003, or Outlook 2002. You can use the Office Customization Tool to quickly modify profile settings and create a new PRF file that includes those settings. When Outlook processes the PRF file, Outlook verifies that services that should be unique are not added more than once, and that services that cannot be duplicated have unique account names. Most MAPI services and accounts can be added only once to a profile. The exceptions to this rule include mail server and directory service providers for POP, IMAP, PST (personal store folder), and LDAP.

Using Outlook 98 and Outlook 2000 PRF files

You might already have a PRF file from an earlier version of Outlook (before Outlook 2002) that you want to update and use with Office Outlook 2007. If you have a PRF file from Outlook 98 or Outlook 2000 that includes Corporate or Workgroup settings only, you can specify the file by using the Office Customization Tool, and the Outlook profile settings will be included in your Setup customization file. If your earlier PRF file specifies Internet Mode Only (IMO) settings, create a new PRF file by using the Office Customization Tool, and then export the settings to a PRF file. The new PRF file can be used to configure profile settings in your transform, or to customize Outlook profiles through other methods (such as starting the file directly on a user's computer).

21

Creating and updating PRF files

To create an Office Outlook 2007 PRF file, you can configure profile settings by using the Office Customization Tool, and then export the settings to a PRF file. This process creates a new Office Outlook 2007 PRF file with your specifications. You can also specify profile settings by editing an existing PRF file manually with a text editor. This existing PRF file might be one that you created by using the Office Customization Tool, or a PRF file from a previous version of Outlook.

Creating PRF files by using the Office Customization Tool

A straightforward way to create a PRF file with Office Outlook 2007 profile settings is to customize the settings by using the Office Customization Tool, and then export the settings to a PRF file. To create a PRF file by using the Office Customization Tool 1. In the Office Customization Tool, on the Outlook: Customize Default User Profile page, select how you want to customize profiles for your users. To specify settings to be included in a PRF file, choose Modify Profile or New Profile, and click Next. 2. On the next three pages, customize profile information such as configuring Microsoft Exchange server connections and adding accounts. 3. On the Outlook: Remove Accounts and Export Settings page, click Export Profile Settings, and when prompted, enter (or browse to) a file name and location.

Manually editing PRF files

If your organization requires special modifications to Outlook profilesfor example, if you want to add a new service that is not included in the Office Customization Toolyou can edit the PRF file. Use a text editor such as Notepad to edit your older PRF file, or a new PRF file created with the Office Customization Tool. Make your changes or additions, and save the file. The main functional areas in the Outlook PRF file include: A section specifying actions to take, such as creating new profiles, modifying existing profiles, and overwriting existing profiles. Sections with organization-specific customizations, including server names and configurations to deploy. Sections that map information specified in earlier parts of the file to registry key settings. The PRF file includes detailed comments for each section that describe existing settings and options for modifying the file with your updates. The file includes seven sections: 22 Section 1: Profile defaults Section 2: List of MAPI services to be added to the profile Section 3: List of Internet accounts to be created Section 4: Default values for each service Section 5: Settings values for each Internet account Section 6: Mapping for profile properties

Section 7: Mapping for Internet account properties

To allow each service definition to be customized individually, you can duplicate default variables and values in Section 4 under the separate headings (Service1, Service2, and so on) for each service in the profile. Section 6 also groups variables under each service definition. For example, some services can be defined as unique (UniqueService is Yes) while others cannot (UniqueService is No). You typically do not modify existing entries in sections 6 and 7. These sections define mappings for information that is defined elsewhere in the file to registry key settings. However, if you define new services in the PRF file, you must add the appropriate mappings for those services to sections 6 and 7. The following table lists accounts that are unique, and how Outlook determines if a new account of the same type can be added. Keep this information in mind when you add providers in the PRF file. Outlook verifies that unique services are not added more than once, and that other services do not conflict (for example, that all POP accounts have unique names).
Account Unique account? Method for determining conflicts when adding new account

POP IMAP Hotmail/HTTP PST Outlook Address Book Personal Address Book LDAP Exchange

No No No No Yes Yes No Yes

Account name Account name Account name Full path to PST (including file name) Existence of account Existence of account Account name Existence of provider

By manually editing the PRF file, you can add any MAPI service that is supported by Office Outlook 2007. The following services were supported in earlier versions of Outlook, and should not be added: MS Mail Symantec WinFax Lite AW Fax

You can also remove services that are listed in the PRF file. Note: When you manually change a text file, you can introduce errors that cause Outlook to behave incorrectly. You should not edit and deploy a manually modified PRF file unless 23

you have no other way to update user profiles. If possible, you should use the Office Customization Tool to create and deploy PRF files.

Applying Outlook user profiles by using a PRF file

You can apply a PRF file in several ways to update Outlook profiles: Import the PRF file in the Office Customization Tool to specify profile settings in a transform, and then include the transform when you deploy or update Outlook. Specify the PRF file as a command-line option for Outlook.exe to import a PRF file without prompting the user. Example: outlook.exe /importprf \\server1\share\outlook.prf. Specify the PRF file as a command-line option for Outlook.exe, but prompt the user before importing the PRF file. Example: outlook.exe /promptimportprf \\localfolder\outlook.prf. If you put the specified PRF file in a shared folder on a network, the settings might not be applied if the file is not found or is not available when Outlook runs. Configure the registry to trigger Outlook to import the PRF file when Outlook starts up. You can use the Add/Modify Registry Entry page in OCT to deploy these registry key options to your users. You can also use the OCT to distribute the PRF file to users by using the Add/Remove Files page. a. Delete the following registry key values: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Setup\First-Run HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Setup\FirstRun b. In the HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Setup subkey, set the value of ImportPRF to a string value that specifies the name and path of the PRF file. For example, set ImportPRF to \\server1\share\outlook.prf. See Also Configuring Outlook Profiles by Using a PRF File Outlook (http://technet.microsoft.com/en-us/library/cc179097.aspx#Outlook) Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)

24

Configure Outlook with Exchange Server

In this section: Configure Cached Exchange Mode in Outlook 2007 Configure Exchange Server send/receive settings in Outlook 2007 Configure Outlook Anywhere in Outlook 2007

25

Configure Cached Exchange Mode in Outlook 2007

In this article: Configure Cached Exchange Mode settings by using the Office Customization Tool Configure Cached Exchange Mode settings by using Group Policy

When a Microsoft Office Outlook 2007 account is configured to use Cached Exchange Mode, Office Outlook 2007 works from a local copy of a user's Exchange mailbox stored in an Offline Folder file (OST file) on the user's computer, and with the Offline Address Book (OAB). The cached mailbox and OAB are updated periodically from the Exchange server. Cached Exchange Mode can only be configured for Microsoft Exchange Server e-mail accounts. Although Cached Exchange Mode is supported on Microsoft Exchange Server 2000 and later, we recommend that this feature be used with Exchange Server 2003 or later. If you do not configure Cached Exchange Mode options, the current state of Cached Exchange Mode does not change for existing profiles when Outlook upgrades to a new version. If a user account was configured to use Cached Exchange Mode in Outlook 2003, for example, Cached Exchange Mode is still enabled when the user upgrades to Office Outlook 2007. The location for new OST or OAB files is the default location: for Windows XP, the location is %userprofile%\Local Settings\Application Data\Microsoft\Outlook; for Windows Vista, the location is %userprofile %\AppData\Local\Microsoft\Outlook. When you consider whether to change Cached Exchange Mode settings for synchronization with Exchange servers, be aware that timing for Office Outlook 2007 has improved so that e-mail updates faster than in Outlook 2003. However, there might be circumstances when you need to modify the default synchronization values. You can configure a number of options for Cached Exchange Mode, including the default OST file location for users in your organization that do not already have OST files for Cached Exchange Mode and offline use. If you do not specify a different OST location, Outlook creates an OST file in the default location when users start Outlook in Cached Exchange Mode. You can lock down the settings to customize Cached Exchange Mode by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings.

26

Configure Cached Exchange Mode settings by using the Office Customization Tool
Configure Cached Exchange Mode settings by using the Office Customization Tool 1. In the Office Customization Tool, in the Outlook section, click the Specify Exchange Settings page, and then click Configure an Exchange Server connection. Note: You must choose Modify Profile or New Profile on the Outlook Profile page to configure Exchange Server settings. 2. To specify a new location for users' OST files, click More Settings, and then click Enable offline use. Enter a folder path and file name for the OST file location. You can also enter a path in the Directory path to store the Offline Address Book files box, and then click OK. 3. To enable or disable Cached Exchange mode, or to specify default download behavior when Cached Exchange Mode is enabled, click Configure Cached Exchange Mode on the Specify Exchange Settings page. 4. Select the Use Cached Exchange Mode check box to enable Cached Exchange Mode for users. By default, Cached Exchange Mode is disabled if you do not select the check box but you do select Configure Cached Exchange Mode. 5. Select a default download option if you enabled Cached Exchange Mode in step 4: Download only headers. Users see header information and the beginning of the message or item body (a 256-KB plain-text buffer of information). Full items are downloaded by double-clicking to open the message or by clicking Download the rest of this message now at the bottom of the Reading Pane. Download headers followed by the full item. All headers are downloaded first, and then full items are downloaded. The download order might not be chronological. Outlook downloads headers followed by full items in the folder that the user is currently accessing, and then downloads headers followed by full items in folders that the user has recently viewed. Download full items. Full items are downloaded. The download order might not be chronological. Outlook downloads full items in the folder that the user is currently accessing, and then downloads full items in folders that the user has recently viewed. 6. To turn off Headers Only mode, clear the On slow connections, download only headers check box. Downloading only headers is the default behavior when users have slow connections. There are scenarios in which Outlook perceives that users have slow connections when users' data throughput is fast, or vice versa. In these situations, you might want to set or clear this option. 7. Choose to disable the downloading of shared non-mail folders as part of Cached Exchange Mode synchronizations to users' OST files. By default, shared non-mail folders are downloaded. Downloading Public Folder Favorites might cause users' OST files if they use 27

non-Unicode OSTs to increase past the 2-GB size limit. This results in errors when Outlook synchronizes. 8. Choose to download Public Folder Favorites as part of Cached Exchange Mode synchronizations to users' OST files. By default, Public Folder Favorites are not downloaded. Downloading Public Folder Favorites might cause users' OST files if they use non-Unicode OSTs to increase past the 2-GB size limit. This results in errors when Outlook synchronizes. Also, synchronizing Public Folder Favorites causes extra network traffic that might be unwelcome for users who have slow connections.

Configure Cached Exchange Mode settings by using Group Policy

Customize Cached Exchange Mode options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize Cached Exchange Mode options, under the following paths, double-click the policy that you want to set. For example, double-click Use Cached Exchange Mode for new and existing Outlook profiles. User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\Exchange\Cached Exchange Mode User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\Exchange: The two Cached Exchange Mode options are Synchronizing data in shared folders and Cached Exchange low bandwidth threshold. 3. Click Enabled and choose an option (if appropriate). 4. Click OK. You can configure the settings shown in the following table for Cached Exchange Mode under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\Exchange\Cached Exchange Mode.
Cached Exchange Mode option Description

Use Cached Exchange Mode for new and existing Outlook profiles

By default, users can choose to configure Cached Exchange Mode or use Online mode. By enabling this setting, new and existing Outlook profiles are configured to use Cached Exchange Mode. Disabling this setting configures new and existing Outlook profiles to use Online mode.

28

Cached Exchange Mode option

Description

Do not sync in Cached Exchange mode when users click Send/Receive or F9

By default, when users click Send/Receive or press F9 for Cached Exchange Mode accounts, Outlook synchronizes with the Exchange server. When this setting is enabled, clicking Send/Receive and pressing F9 does not synchronize with Exchange unless only one folder is being synchronized. Users can continue to use shift-F9 to synchronize the current folder. Specifies the number of seconds to wait before uploading changes to the Exchange server. Specifies the number of seconds to wait before downloading changes from the Exchange server. Specifies the number of seconds to wait before synchronizing changes with the Exchange server. Specifies the default Cached Exchange Mode for new profiles and disables the download options in the Cached Exchange Mode command submenu in the File menu. This applies only to Microsoft Exchange Server 2003 or later. Disables the download option Download Full Items in the Cached Exchange Mode download options menu. This applies only to Microsoft Exchange Server 2003 or later. Disables the download option Download Headers and then Full Items in the Cached Exchange Mode download options menu. This applies only to Microsoft Exchange Server 2003 or later. Disables the download option Download Headers in the Cached Exchange Mode download options menu. This applies only to Microsoft Exchange Server 2003 or later.

Enter seconds to wait to upload changes to server Enter seconds to wait to download changes from server Enter maximum seconds to wait to sync changes Cached Exchange Mode (File | Cached Exchange Mode)

Disallow Download Full Items (File | Cached Exchange Mode)

Disallow Download Headers then Full Items (File | Cached Exchange Mode)

Disallow Download Headers (File | Cached Exchange Mode)

29

Cached Exchange Mode option

Description

Disallow On Slow Connections Only Download Headers (File | Cached Exchange Mode)

Disables the download option On Slow Connections Only Download Headers in the Cached Exchange Mode download options menu. This applies only to Microsoft Exchange Server 2003 or later. Public Folder Favorites are synchronized to users' OST files. By default, most shared folders that users access in other mailboxes are automatically downloaded and cached in the users' local OST files when Cached Exchange Mode is enabled. Only shared Mail folders are not cached. You can use this setting to change this behavior so that non-mail folders are not downloaded automatically.

Download Public Folder Favorites Download shared non-mail folders

You can configure the settings shown in the following table for Cached Exchange Mode under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\Exchange.
Cached Exchange Mode option in Exchange area Description

Synchronizing data in shared folders

Controls the number of days that elapse without a user accessing an Outlook folder before Outlook stops synchronizing the folder with Exchange. Specify the bit rate threshold value below which Outlook will identify the network connection as a 'slow' connection.

Cached Exchange low bandwidth threshold

If users in your organization do not already have OST files, you might choose to configure a default OST file location for Cached Exchange Mode and offline use. If you do not specify a different OST location, Outlook creates an OST in the default location when users start Outlook in Cached Exchange Mode. Configure a default OST location by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To configure a default OST location, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Miscellaneous\PST Settings, double-click Default location for OST files. 3. Click Enabled to enable the policy setting. 30

4. In the text box, enter the default location for OST files. For example: %userprofile%\Local Settings\Application Data\Microsoft\newfolder. 5. Click OK. You can define a new default location for both PST and OST files by using the setting Default location for PST and OST files. If the Exchange Server version and settings support Unicode, you can require that new Outlook files are Unicode. For example, this can be helpful if users will require OST files with additional space to support large Exchange mailboxes when those users are configured to use Cached Exchange Mode. For more information about how to configure users in this scenario, see Plan a Cached Exchange Mode deployment in Outlook 2007 (http://technet.microsoft.com/enus/library/cc179067.aspx). Specify Unicode for new Outlook files 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Miscellaneous, double-click Preferred PST Mode (Unicode/ANSI). 3. Select Enabled. 4. In the drop-down list under Choose a default format for new PSTs, select Enforce Unicode PST. 5. Click OK.

See Also Planning for Cached Exchange Mode deployment in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179067.aspx) Configure Unicode options in Outlook 2007

31

Configure Exchange Server send/receive settings in Outlook 2007

As part of your Microsoft Office Outlook 2007 deployment, you can define Send/Receive groups for users' Microsoft Exchange Server accounts and folders and specify tasks that are performed on each group during a Send/Receive action in Outlook. Note: This topic is for Outlook administrators. To configure Outlook send/receive settings on your computer, see Using send/receive groups (http://go.microsoft.com/fwlink/? LinkId=81363). You configure these settings in the Office Customization Tool (OCT). You cannot configure the settings by using Group Policy. To create and configure Send/Receive groups for Exchange accounts and folders 1. In the OCT, in the Outlook area, on the Specify Send/Receive Groups (Exchange Only) page, click New. 2. In the New Group Name box, enter a name for the group and click OK. 3. Click Modify. 4. In the Modify Group dialog box, select options for the group, such as synchronizing forms during a Send/Receive action. 5. In the Change folder options section, select a folder and select Include this folder in Send/Receive. 6. Choose download options for the folder. This option is only relevant for folders that have the concept of headers, such as Inbox, Outbox, Deleted Items, Sent Items, and Drafts: Download only headers Download complete item including attachments Download only headers for items larger than n KB 7. Enter a size limit in kilobytes (KB). This setting only applies for accounts set up to use Exchange Server 2003, or later versions of Exchange Server. 8. Click another folder to include the folder in this Send/Receive group, and choose a download option. 9. Add all the folders that you want to include in this group, then click OK. 10. Click a group in the Group Name list. 11. Select the options available in this dialog box to specify Send/Receive behaviors for the group. 12. In the Exchange Address Book section, select Download offline address book to synchronize the Offline Address Book (OAB) when this Send/Receive group is synchronized. This setting is configured for each Send/Receive group. 32

13. Click Address Book Settings. 14. Select options in Modify Address Book Settings dialog box. These settings apply to all Send/Receive groups in this profile. 15. Click OK.

More about configuring send/receive settings

Send/Receive groups contain one or more user e-mail accounts or folders in Microsoft Outlook. The Send/Receive group All Accounts is preconfigured and is included with Outlook by default. Users can specify different behaviors for each group, such as the frequency with which Outlook connects to the server to send and receive messages for the server, or how messages are processed when Outlook is online or offline. You can configure and deploy Send/Receive settings for users' Exchange accounts. For example, you can specify the types of synchronization that will be performed on specific folders or the OAB when a Send/Receive operation is executed. You can also specify when a Send/Receive action for each Send/Receive group will normally be performed and when the action will be performed when users are offline. For example, a Send/Receive group can be configured to synchronize every 10 minutes normally and every 30 minutes when users are offline. You can also configure download options for the OAB, such as whether to only download updates to the OAB since the last OAB download.

Defining custom Send/Receive groups

You can define one or more custom Send/Receive groups for your organization that include the accounts and folders you want Outlook to synchronize for users under different circumstances. For example, you might define a new Send/Receive group to deploy to your users for offline synchronization and you might modify the default All Accounts group not to be scheduled for automatic synchronization when users are offline. The new offline Send/Receive group would include a subset of users' accounts and folders configured to automatically update at specific intervals when users work offline. By configuring only critical accounts and folders to update when users work remotely, users can still access current data that is important to their work but they will spend less time waiting for large downloads over slow dial-up lines. Note: Using Cached Exchange Mode in Outlook improves the user experience when users work remotely over a low-bandwidth connection. For more information about planning deployments when you use this feature, see Plan a Cached Exchange Mode deployment in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179067.aspx).

33

Configuring Send/Receive settings for a Send/Receive group

After you create a custom Send/Receive group, you might want to specify Send/Receive behavior for the groupfor example, to execute a Send/Receive action for this group every 10 minutes. You can also specify separate settings for how Send/Receive works when users are offline.

Configuring Offline Address Book download options

In addition to configuring Send/Receive behavior for each Send/Receive group, you can also specify whether or not to download the OAB for each group. For example, if the Send/Receive group is designed for users who work offline and the group connects periodically over slow connections, you might choose to configure the OAB not to download. Note: The Offline Address Book options (the Full Details or No Details OABs and synchronization choices) apply to a specific profile. They cannot be specified differently for different Send/Receive Groups. Consider the following factors when you decide whether to download the Full Details OAB or a No Details OAB: A Full Details OAB is required if you plan to deploy Cached Exchange Mode. If a No Details OAB is already on a user's computer, the No Details OAB is overwritten when Outlook creates a Full Details OAB for Cached Exchange Mode. For more information, see Setting Up Outlook 2003 Cached Exchange Mode Accounts. You cannot configure the information that is included in a No Details OAB.

34

Configure Outlook Anywhere in Outlook 2007

If you are an IT professional and use TechNet or the Office Resource Kit, take a look at our Online Survey (http://go.microsoft.com/fwlink/?LinkId=132189). Let us know how we can best meet your documentation needs. You can read more about our work to improve documentation on the Office Resource Kit Blog (http://go.microsoft.com/fwlink/?LinkID=125627&clcid=0x409). You can configure user accounts in Microsoft Office Outlook 2007 to connect to Microsoft Exchange Server 2003 or later over the Internet without using virtual private network (VPN) connections. This featureconnecting to an Exchange account by using Outlook Anywhere enables Outlook users to access their Exchange Server accounts from the Internet when they are traveling or are working outside their organization's firewall. Note: This article describes the requirements and options for you to configure a group of Outlook users to use Outlook Anywhere. If you want to configure this feature on your individual computer, see the Outlook user Help topic Use Outlook Anywhere to connect to your Exchange server without VPN (http://office.microsoft.com/enus/outlook/HP101024441033.aspx?pid=CH101395531033). To configure Office Outlook 2007 with Outlook Anywhere as part of your Outlook deployment, you enable the option in the Office Customization Tool (OCT) and (optionally) specify additional settingssuch as security-level requirements for communication with the Exchange server. After you specify these options, you save the settings with other configurations in the Setup customization file you use to deploy Outlook to your users. You can also lock down some Outlook Anywhere settings by using Group Policy. For more information about Outlook Anywhere Group Policy settings, see the procedure "To lock down Outlook Anywhere settings in the user interface by using Group Policy" later in this article. Note: Outlook Anywhere was referred to as RPC over HTTP in earlier versions of Outlook. References in Group Policy and OCT settings will be updated to reflect the new nomenclature. Until the name is updated, you might find settings that reference RPC over HTTP instead of Outlook Anywhere. To configure Outlook Anywhere by using the OCT 1. In the OCT, in the Outlook area, on the Specify Exchange Settings page, select Configure settings for a new Exchange Server connection or replace the settings in an existing Exchange Server connection. 2. If you are defining a new Exchange server for users, enter a value or replaceable parameter in User name. For instance, you might specify =%UserName% to use the exact logon name for each user. This helps prevent user prompts when Outlook asks users to choose between several variations. 35

3. If you are defining a new Exchange server, for Exchange Server, enter the name of the Exchange server. You can skip steps 2 and 3 if you are configuring Outlook Anywhere for existing Exchange users who are not moving to a new Exchange server. 4. Click More Settings. 5. Select the Connect to Exchange Mailbox using HTTP check box. 6. Type the server name for the Outlook Anywhere proxy server. Do not enter http:// or https:// as part of the name. The appropriate entry (http:// or https://) is included automatically in the box after you enter the name, based on the authentication settings you choose. 7. Choose whether or not to reverse default behavior for how Outlook chooses which connection type to try to use first, LAN or Outlook Anywhere. 8. Select an authentication method. The default method is Password Authentication (NTLM). 9. Click OK to return to the Specify Exchange Settings page. 10. Complete other Outlook or Office configurations and click Finish to create the customization file that you can deploy to your users. Note: We recommend that the user accounts that you configure for Outlook Anywhere use Cached Exchange Mode. For more information about Cached Exchange Mode in Outlook, see Planning for Cached Exchange Mode deployment in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179067.aspx). The following table explains the Outlook Anywhere options for configuring connection type and authentication method. Outlook uses default values for these options that are likely to provide a good experience for your users and to help provide secure connections to your network. These configuration options cannot be locked down by using Group Policy.
Outlook Anywhere option Description

On a fast network, connect using HTTP first, then connect using TCP/IP. On a slow network, connect using HTTP first, then connect using TCP/IP. Password Authentication (NTLM).

By default on a fast network, Outlook attempts to connect by using the LAN connection first. This option is cleared by default. By default, on a slow network, Outlook attempts to connect by using HTTP first. This option is set by default. The default authentication method. We recommend that you specify this optiontogether with Connect with SSL only and Mutually authenticate the session when connecting with SSL.

36

Outlook Anywhere option

Description

Basic Password Authentication.

With this option, users are prompted for a password each time a connection is made to the Exchange server. In addition, if users are not using Secure Sockets Layer (SSL), the password is sent in clear text. This can pose a security risk.

You can provide increased security by using Group Policy to disable the user interface for Outlook Anywhere settings, so users cannot change the options. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To lock down Outlook Anywhere settings in the user interface by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize Cached Exchange Mode options, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\Exchange, double-click the policy that you want to set. For example, double-click Configure RPC over HTTP user interface options. 3. Click Enabled. 4. Select an option from the Choose UI State when OS can support feature drop-down list. 5. Click OK. The settings you can configure for controlling the Outlook Anywhere user interface are shown below.
Option Description

Hidden All config UI enabled Enable only On/Off control but not config Enable config UI when settings are predeployed Disable but show all config UI

User interface options are not displayed. All Outlook Anywhere configuration options are displayed. Users can enable or disable Outlook Anywhere but cannot change other settings. When Outlook Anywhere has been configured for users, settings are configurable by using the user interface. Outlook Anywhere configuration settings are displayed but dimmed and disabled.

37

More about configuring Outlook Anywhere

In a local area network (LAN), Outlook communicates with Exchange servers using direct network (TCP/IP) access, also known as RPC over TCP/IP. This method provides quick, efficient access to a corporate network. Remote users who are accessing Exchange need a VPN connection, which allows users to go through the corporate firewall and login to the corporate network. A VPN is more complex and enables access to more network services than those that are required for just e-mail access. Office Outlook 2007 offers a simpler alternative to VPN connections: Outlook Anywhere. With this feature, users can have security-enhanced access to their Exchange Server accounts from the Internet when they are working outside your organization's firewall. Users do not need special connections or hardware, such as smart cards and security tokens. They can still access their Exchange accounts, even if the Exchange server and client computer behind the firewall are on different networks. Outlook Anywhere works by having an Exchange Server front-end computer configured as an RPC proxy server. This RPC proxy server then specifies which ports to use to communicate with the network's domain controller, global catalog (GC) servers, and all Exchange servers that the client user requires. The Exchange group in your organization must first deploy Outlook Anywhere for the Exchange servers you use, and then you can configure user accounts that access those Exchange servers to use Outlook Anywhere.

Software requirements
There are several requirements for this feature: Microsoft Windows Vista, or Windows XP with Service Pack 1 and the Q331320 hotfix (or a later service pack) installed on users' computers Office Outlook 2007 or Outlook 2003 Microsoft Exchange Server 2003 or later e-mail accounts Microsoft Windows Server 2003 or later (required for server components only)

Note: We highly recommend that this feature is used with Outlook user profiles configured to use Cached Exchange Mode.

Understanding Outlook Anywhere configuration settings

Before you configure Outlook Anywhere for Outlook, you need the URL for the Exchange proxy server that is configured for Outlook Anywhere. This URL should be available from your organization's Exchange administrator. There are additional settings for Outlook Anywhere in the OCT for configuring the connection type and the authentication method described earlier. If necessary, you can change these settings to fit special circumstances in your organization. However, the default values for these options are likely to provide a good experience for users and to help provide secure connections to your network. We recommend that you do not change the options. 38

In addition, we recommend that you lock down these options by disabling the Outlook Anywhere settings in the Outlook user interface.

Deploying Outlook Anywhere after deploying Outlook

You can update an Outlook installation to configure Outlook Anywhere or make changes to an existing Outlook Anywhere installation by using the OCT. Run the OCT and configure the changes you want to make to your Outlook installation, then save the customization file and deploy it to your users. For more information about updating settings in existing Outlook installations, see Update an Outlook 2007 configuration by using the Office Customization Tool (http://technet.microsoft.com/en-us/library/cc179041.aspx).

Outlook Anywhere configuration with Exchange 2007

If your messaging server is Microsoft Exchange Server 2007, you can use the Office Outlook 2007 AutoDiscover feature to automatically configure Outlook Anywhere. For more information about automatic account configuration, see Whitepaper: Outlook Automatic Account Configuration (http://office.microsoft.com/search/redir.aspx?AssetID=AM102105061033).

See Also Exchange Server 2003 RPC over HTTP Deployment Scenarios (http://go.microsoft.com/fwlink/? LinkId=124051) Deploying Outlook Anywhere (http://go.microsoft.com/fwlink/?LinkId=124053)

39

Configure Outlook for information sharing and integration

In this section: Configure Internet Calendars in Outlook 2007 Configure Really Simple Syndication (RSS) in Outlook 2007 Configure Instant Messaging integration options in Outlook 2007 Configure Meeting Workspace options in Outlook 2007

40

Configure Internet Calendars in Outlook 2007

In Microsoft Office Outlook 2007, you can customize Internet Calendar features. Users can send and receive Internet Calendar files as well as subscribe to third-party calendars. You can set up subscriptions for a specific project and then make the calendar available on an internal server. For example, you could set up subscriptions to a calendar that shows project deadlines. Users can set up subscriptions as well. For example, a user might send an Internet Calendar soccer schedule to team parents. Or a user might sign up for an Internet Calendar subscription for a professional baseball team schedule, where the schedule is updated on the team's Web site and sent to the subscriber. Note: This topic is for Outlook administrators. To customize Internet Calendar options on your computer, see Sharing your calendar (http://go.microsoft.com/fwlink/?LinkId=81362). You can lock down the settings to customize Internet Calendar features by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To deploy Internet Calendar subscriptions by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Accounts\Internet Calendar Subscriptions, double-click Default Internet Calendar subscriptions. 3. Click Enabled. 4. Click Show. 5. In the Show Contents dialog box, click Add to add a Value Name and Value pair for each subscription. 6. In the Add Item dialog box, enter the Value Name and the Value in the text boxes. The Value Name is for your reference only. The Value is the URL of the WebCal subscription, specified as: webcal://url of subscription. 7. Click OK to add the subscription to the list. 8. Click Add if you want to enter another subscription. 9. When you finish entering subscriptions, click OK to exit the Show Contents dialog box. 10. Click OK.

41

To configure Internet Calendar options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Accounts\Internet Calendar Subscriptions. 2. Double-click the option that you want to configure. For example, to disallow roaming for subscriptions, double-click Disable roaming of Internet Calendar subscriptions 3. Click Enabled. 4. Click OK. The settings you can configure for Internet Calendars are as follows.
Internet Calendars options Description

Override published sync interval Disable roaming of Internet Calendars

Prevent users from overriding the sync interval published by Internet Calendar providers. Disable roaming so that Internet Calendars are available only on the client that originally linked them. Automatically download enclosures (such as graphics) on Internet Calendar appointments. Disable all Internet Calendar functionality in Outlook. The URLs listed are added to each user's profile as an Internet Calendar subscription.

Automatically download enclosures Disable Internet Calendar Integration Default Internet Calendar subscriptions

More information about configuring Internet Calendars

More information about configuration options is included in the following sections.

Disabling Internet Calendar subscriptions

You can disable Internet Calendar subscriptions in Office Outlook 2007 if, for example, you are concerned about bandwidth usage and want to delay introducing Internet Calendar subscriptions. By default, Internet Calendar subscriptions are enabled. When you disable Internet Calendar subscriptions, the Internet Calendar heading does not appear in the Calendars folder hierarchy, and the Internet Calendar tab does not appear in the Outlook Account Manager dialog box.

42

Providing Internet Calendar subscriptions to users

You can deploy Internet Calendar subscriptions as default subscriptions that users can change or delete. Or you can lock down Internet Calendar subscriptions so that users cannot make changes or remove them. Users can add new Internet Calendar subscriptions, however. By default, there are no Internet Calendar subscriptions, but users can add and remove them.

Synchronization interval for Internet Calendars

Outlook sets the synchronization interval so that each Internet Calendar subscription is updated at the publisher's recommended interval. Users can override the default interval unless you disallow that option. However, if users set the update frequency to a short interval, it can cause performance problems. By enabling the option in Group Policy, you can enforce the use of the publisher's update intervals, so users cannot change the intervals. This setting is used for all Internet Calendar subscriptions; you cannot set this option differently for different subscriptions.

43

Configure Really Simple Syndication (RSS) in Outlook 2007

Really Simple Syndication (RSS) is a way for Web sites to make new contentfor example on news sites or blogsavailable to users. Microsoft Office Outlook 2007 includes features for subscribing to RSS content, reviewing and managing RSS items, and managing subscriptions, called RSS Feeds. Note: This topic is for Outlook administrators. To learn about using Outlook RSS options on your computer, see Introduction to RSS (http://go.microsoft.com/fwlink/?LinkId=81373). The topic includes links to more information about adding an RSS Feed, changing settings for RSS Feeds, and so on. You can provide internal and external RSS Feeds to users. For example, you might want to set up user subscriptions to information about software updates available on an internal server. Users can also individually subscribe to content, such as a news headline service, or change the frequency with which Outlook checks for new content on a site. You can lock down the settings to customize RSS by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To deploy default RSS Feeds by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\RSS Feeds, double-click Default RSS Feeds. 3. Click Enabled. 4. Click Show. 5. In the Show Contents dialog box, click Add to add a Value Name and Value pair for each subscription. 6. In the Add item dialog box, in the Enter the name of the item to be added field, type a name for the RSS subscription. 7. In the Enter the value of the item to be added field, type or paste the URL of the RSS Feed. Provide the URL in the format: feed://subscription URL, where feed:// replaces http://. This ensures that the URL is parsed as an RSS XML file by Outlook; for example, feed://www.contoso.com/main/rss.xml. 8. Click OK to exit the Add item dialog box. 44

9. To enter another RSS feed, click Add. 10. Click OK to exit the Show contents dialog box. 11. Click OK. To configure RSS integration options in Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings\RSS Feeds. 2. Double-click the option that you want to configure. For example, to disallow roaming for subscriptions, double-click Do not roam users' RSS Feeds. 3. Click Enabled. 4. Click OK. The settings you can configure for RSS Feeds in the RSS Subscriptions area are as follows:
RSS option Description

Run rules on RSS items Do not roam users' RSS Feeds

Cause rules to run on RSS items. Disable roaming so that RSS Feeds are available only on the client that originally linked them. Disable all RSS functionality in Outlook. Automatically download enclosures (such as graphics) on RSS posts. Prevent users from overriding the sync interval published by RSS publishers. Automatically download the full text of RSS posts as HTML attachments on the posts. The URLs listed are added to each user's profile as an RSS Feed. Automatically subscribe to RSS Feeds that are added in Windows Internet Explorer, and do not sync Outlook RSS Feeds to the Common Feed List (so they would be available in IE).

Turn off RSS feature Automatically download enclosures Override published sync interval Download full text of articles as HTML attachments Default RSS Feeds Synchronize Outlook RSS Feeds with Common Feed List

In addition, you can configure or disable the RSS Folder Home Page in Outlook. This setting is located in User Configuration\Administrative Template\Microsoft Office Outlook 2007\Folder Home Pages for Outlook Special Folders. For more information about defining an RSS folder home page, see "Creating a custom RSS folder home page" in the RSS folder home pages later in this topic.

45

RSS option

Description

RSS Folder Home Page

Provide URL for custom RSS home page or disable RSS folder home page feature.

More information about configuring RSS

More information about RSS and RSS configuration options is included in the following sections.

About RSS
RSS is a way to notify people that there is new information on a Web site. By signing up for Web content that has been syndicated by using RSS, people can browse through a list of new content. Typically, they can click on a URL (included with most entries) to go to a corresponding page on the Web site for details. For example, a news site might use RSS to syndicate headlines. Users who subscribe to the service on that news site receive an e-mail message regularly with the latest headlines. The frequency of RSS updates can be set by the user, but precedence is given to limits set by a provider on how frequently a subscriber can request updates from their site. This helps avoid overloading the provider's server with excessive update requests. To create RSS syndication on a Web site, the owner of the content creates an RSS file that follows a standardized XML-based format. The file lists items such as news headlines or Web log entries. In the RSS file, the content is encoded so that it can be read by a news aggregator or news reader programfor example, by using the RSS features in Office Outlook 2007. Using news reader programs, users can scan through headlines or other content from the Web sites they have subscribed to, allowing them to review updates from many aggregated Web sites at once.

Disable RSS integration

You can disable RSS integration in Outlook, if, for example, you are concerned about bandwidth usage and want to delay introducing RSS integration. By default, RSS integration is enabled. When you disable RSS integration, the RSS Subscriptions root folder does not appear in the folder hierarchy in the Outlook navigation pane, and the RSS Subscriptions tab does not appear in the Outlook Account Manager dialog box.

Provide RSS Feeds to users

Users can subscribe to RSS Feeds, and you can provide internal and external RSS Feeds to users. For example, you might want to set up user subscriptions to information about new software updates available on an internal server. You can deploy RSS Feeds as default subscriptions that users can change or delete. Or, you can lock down RSS Feeds so that users cannot make changes or remove them. By default, there are no RSS Feeds, and users can add and remove their own new RSS Feeds. 46

You specify RSS Feeds by entering in Group Policy a name for a feed, paired with the corresponding URL. The name that you enter is for your reference; users see the name of the RSS Feed given by the RSS provider.

Customize the RSS synchronization interval

Outlook sets the synchronization interval so that each RSS feed is updated at the feed publisher's recommended interval. Users can override the default interval unless you disallow that option. However, if users use a short interval, it can cause performance problems. You can enforce the use of the publishers' update intervals, so users cannot change them. This setting is used for all RSS Feeds; you cannot set this option differently for different RSS Feeds.

Disable RSS roaming

By default, RSS Feeds roam with users from one computer to another. You can prevent this by setting an option in the Office Customization Tool or by using Group Policy. This setting is used for all RSS Feeds; you cannot set this option differently for different Feeds.

RSS folder home pages

The RSS folder home page is set by default to a page listing an introductory group of RSS Feeds. You can change this to use another home page on which you include your own list of RSS Feeds, or you can disable the home page feature for the RSS folder.

Creating a custom RSS folder home page

You can use the default RSS folder home page provided with Office Outlook 2007 , or you can create one tailored to your organization. Whether you use the default home page or provide a custom one, users must be connected to the network to view the home page. With both default and custom RSS home pages, you can take steps to ensure that the offline experience is not confusing to your users. When users are offline and switch to the RSS folder, an error message appears, stating that the page is not found. For users to have a good offline experience, Outlook displays a message explaining the problem instead of simply returning the standard "Page not found" error when it determines that a folder home page is being loaded. When users are offline, there are two requirements for Outlook to display the explanatory message instead of a standard error: A string must be included at the end of the title on the page used for the folder home page. The folder must be created with a new Outlook folder type. To meet the first requirement, you add the following string to the end of the title of the custom RSS home page you create: (Outlook Homepage). The string and anything after that string is not displayed in the title of the page. When a user is offline, the explanatory message is displayed. When a user is online, the folder home page is displayed with the string removed so users do not see the string in the title. 47

The second requirementa new Outlook folder typeensures that the explanatory message for the RSS folder home page is not displayed for other folder home pages when users are offline. The standard Outlook folder type is IPM.Folder. The new folder type for RSS folders is IPM.Folder.OutlookHomepage. Note: If you want to have other folders with folder home pages work for offline users the same way that the RSS folder home page does, you can change the file type for the folder when you create user profiles.

48

Configure Instant Messaging integration options in Outlook 2007

Instant Messaging is a feature of Microsoft Windows Messenger, Microsoft MSN Messenger, and the Microsoft Exchange Instant Messaging Service. With Instant Messaging, users can communicate with each other in real time. Note: This topic is for Outlook administrators. To configure Instant Messaging in Outlook on your computer, see Use instant messaging services with Outlook (http://go.microsoft.com/fwlink/?LinkId=81361). You can lock down the settings to customize Outlook Instant Messaging features by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. Note: You can also configure Instant Messaging settings for the 2007 Microsoft Office system in Group Policy or by using the OCT. You can lock down the settings using the Office Group Policy template (Office12.adm). Instant Messaging settings for Office are under User Configuration\Administrative Templates\Microsoft Office 2007 system\Instant Messaging Integration. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To use Group Policy to configure Outlook Instant Messaging options 1. In Group Policy, load the Microsoft Office Outlook 2007 template (Outlk12.adm). 2. To configure Instant Messaging settings, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options...\Other\Person Names, double-click one of the Instant Messaging settings. 3. Click Enabled. 4. Select the option you want to configure, and then click OK.

49

The settings you can configure for Instant Messaging in Outlook are as follows.
Instant Messaging options Description

Set maximum level of online status on a person name

Choose where to display presence information: do not display presence anywhere; display presence everywhere; or display presence everywhere except on the To and CC fields (default). Disable roaming so that Internet Calendars are available only on the client that originally linked them. Automatically download enclosures (such as graphics) on Internet Calendar appointments.

Display online status on a person name

Turn off Enable the Person Names Smart Tag option

More information about Instant Messaging settings

When a user opens a message or views it in the Reading Pane in Office Outlook 2007, the Person Names Smart Tag is displayed beside the sender's name. This smart tag also appears in other places in Outlook, including in Contacts (when users rest the pointer on an e-mail address) and in new meeting requests (when users rest the pointer on an attendee's name). Users can right-click the smart tag to see a menu of information and options, such as a person's free/busy status. Deciding whether to change the default settings depends on your organization's size and needs. For example, here are two recommendations to consider, if they apply to your organization: If your organization has fewer than 50 users, you might choose to allow users to see Instant Messaging presence for person names everywhere in Outlook. To do this, configure Allow everywhere for the Outlook setting Set maximum level of online status on a person's name. If your organization has users who have specified Query Exchange IM Server or Query Messenger Contacts list only for allowing Instant Messaging status queries, this setting will be migrated to Office Outlook 2007 by default. If you want to require using Live Communications Server instead, configure Query Live Communications Server for the Office setting Allow IM status queries for people not on the Messenger Contacts list.

50

Configure Meeting Workspace options in Outlook 2007

In this article: Using policies to define server lists and other user options Configuring Meeting Workspace integration when using a POP Server Viewing error message logs

A Meeting Workspace is a Web site for centralizing meeting information and materials. Before the meeting, you use a workspace to publish the agenda, attendee list, and documents you plan to discuss. After the meeting, you use the workspace to publish the meeting results and track tasks. You send a Microsoft Outlook meeting request to invite people to the meeting. In the message, you include a hyperlink that points to the workspace where invitees can learn details and see the meeting materials. Note: This topic is for Outlook administrators. You can configure a number of options to set up and manage your Meeting Workspace deployment with Microsoft Office Outlook 2007. You can manage how users choose Meeting Workspace servers and other options when they create workspaces to include in Outlook meeting requests. You can configure Meeting Workspaces when you use a POP server as your messaging server. You can also view Meeting Workspace error messages in a log file to troubleshoot issues with Meeting Workspace configurations. Note: By default, a Microsoft Exchange server must be configured as your messaging server when you use Meeting Workspaces with Outlook. A Meeting Workspace is a special type of Microsoft Windows SharePoint Services Web site created under a top-level SharePoint site. Help for the Meeting Workspace and general SharePoint Help is available from the workspace. Note: If Windows SharePoint Services is installed on your network, users within your company can invite other users who share the same Microsoft Windows NT forest to a workspace. For more information about domains and forests, see information on Active Directory in Windows Help.

51

Using policies to define server lists and other user options

You can configure options when you use policies to enforce Meeting Workspace settings for groups of users in your organization. For example, you can define the list of Meeting Workspace servers that users can choose. You can disable Meeting Workspace access if you do not want users to use this feature. In a server list, you can specify how to prepopulate the drop-down lists that users see when they work with Meeting Workspaces in Outlook. You access the Meeting Workspace feature by clicking Meeting Workspace on an Outlook meeting request. On the Meeting Workspace task pane, click Change settings. On the next Meeting Workspace task pane, choose a server from the Select a location: drop-down list. On the same pane, you can create a new workspace by choosing a template language and a template type from drop-down lists. You can also link to an existing workspace by choosing a workspace from the Select a workspace drop-down list. You use Group Policy to configure the lists and settings you want for Meeting Workspace. When you load the Microsoft Office 12 system ADM files into Group Policy, policies related to Meeting Workspace are located under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Meeting Workspace. This is also the location where you create a new policy to list Meeting Workspace servers and other items in the Meeting Workspace task pane drop-down lists.

Configuring server list behavior for meeting organizers

You can configure how Meeting Workspace server lists are presented to meeting organizers in Outlook. For example, server lists can show a most recently used (MRU) list, and the list of servers and templates can be repopulated from the default list each time a workspace is created. You can also help to prevent Meeting Workspace access by disabling the Meeting Workspace option for Outlook meeting requests. When you specify the list of servers, you can ensure that the server list is repopulated with default servers and default templates. You can also help to control whether users can access servers other than those that are specified. You remove the Meeting Workspace button from Outlook meeting requests with the Disable Meeting Workspace button policy. Double-click the policy to open the Properties dialog and select Enabled. Then select the Check to disable Meeting Workspace button. You configure options for the Meeting Workspace. Select a location drop-down list with the Disable user entries to server list policy. Double-click the policy to open the Properties dialog and select Enabled. In the Check to disable users from adding entries to server list dropdown list, select one of the following: Publish default, allow othersYou specify a list of default servers that appears in the drop-down list. Users can use the Other workspace server pop-out dialog to specify other servers. In addition, other Windows SharePoint Services sites and document workspace sites that users visit appear on the server list. No user MRU list is created with this setting. 52

 Publish default, disallow othersThe default server list you specify is locked down for users. Users cannot access the Other workspace server pop-out dialog to specify servers that are not on the provided list. With this setting, no user MRU list is created.

Specifying a list of servers and default templates

You can configure the list of servers and corresponding Meeting Workspace templates that appear in a drop-down list when a user clicks Meeting Workspace in a meeting request. A single registry key or policy stores all the Meeting Workspace server list entries. Note: You can use the Office Customization Tool (OCT) to deploy the registry key that specifies the list of Meeting Workspace servers to your users. For more information about using the OCT, see Configure user settings for the 2007 Office system. For details on deploying registry keys by using the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). The server list policy has a specific format that must be followed. Server names are separated from each other by vertical pipes (|) without carriage returns (CRs) or line feeds (LFs). There are six fields per record, as described below. There are from one to five records in the policy. This is an MRU list. The first server record (for example, Server1) is the most recently used server and the 5th server record (for example, Server5) is the oldest server reference. The OrganizerName field is ignored when you use a policy to specify the server list. The other fields should always have valid content. Notes You can examine the following registry key to see the current server list settings on any computer that has been used to create Meeting Workspaces: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Meetings\Profile\MRUInternal You specify the server list for the Meeting Workspace with the Default servers and data for Meeting Workspaces policy. Because the policy string is complex, you should first type the entries into a text editor (such as Notepad), and then paste the entire string into the policy. When you create the server list string following the syntax described below, double-click the policy to open the Properties dialog and select Enabled. In the Default field, paste the server list string you have created. The syntax for the server list string is outlined below: http://Server1 |Friendly name for server 1|TemplateLCID|TemplateID| TemplateName|OrganizerName|http://Server2 |Friendly name for server 2| TemplateLCID|TemplateID|TemplateName|OrganizerName|http://Server3 | Friendly name for server| The list continues with the same structure, with an entry for each server you want to include. There are six fields in each record: 53

Field 1: Server URL Field 2: Server friendly name Field 3: TemplateLCID Field 4: TemplateID Field 5: TemplateName Field 6: OrganizerName

Each field is separated from the next field with a vertical pipe (|). Each complete record is separated from the next record with a vertical pipe (|) after the last field (OrganizerName). There is a total of six vertical pipes in each record included in the setting. For the field TemplateLCID, specify a decimal value that identifies the language for the template, such as 1033 (representing English). For the other template fields, you can choose a template name and the corresponding TemplateID from the following table of default templates.
TemplateName TemplateID

Basic Meeting Workspace Blank Meeting Workspace Decision Meeting Workspace Social Meeting Workspace Multipage Meeting Workspace Note:

Mps#0 Mps#1 Mps#2 Mps#3 Mps#4

You cannot use a custom template for Outlook Meeting Workspaces with Windows SharePoint Services. The following is an example of a server list entry (OrganizerName is blank): http://server1/sites/design_team|The Juniper Project|1033|MPS#4| Multipage Meeting

Configuring Meeting Workspace integration when using a POP Server

You can configure Meeting Workspace integration for Outlook when you use a POP server as your messaging server. The POP server configuration enables Outlook to transport and persist Meeting Workspace properties for meeting organizers and meeting attendees who use a POP server. Note: The use of Outlook delegates with Meeting Workspace is not supported in POP server configurations. 54

This section provides a pointer to reference information that can help you configure your POP server to use TNEF. This section also includes steps that meeting organizers must take to help ensure that meeting requests are sent by using rich transport. The following is required to use Meeting Workspaces with a POP server: The POP server must be configured to support Transport-Neutral Encapsulation Format (TNEF). Outlook meeting requests must be sent by using rich transport. The following scenario describes the user experience when Meeting Workspaces are included in meeting requests and Outlook is used with a POP server. 1. The meeting organizer initiates a meeting request in Outlook and creates or links to a Meeting Workspace in the request. 2. The attendee receives the meeting request and sees a Meeting Workspace table in the message body. The correct format of the table should include a link to the Meeting Workspace. 3. The Meeting Workspace properties are persisted to the attendee's calendar. 4. The attendee's response is sent to the Meeting Workspace server.

More about TNEF support

TNEF is a format for converting a set of MAPI propertiesa MAPI messageinto a serial data stream. The TNEF functions are primarily used by transport providers that need to encode MAPI message properties for transmission through a messaging system that does not directly support those properties. For example, an SMTP-based transport uses TNEF to encode properties, such as PR_SENT_REPRESENTING, which do not have direct representations in the structure of an SMTP message. For more information about using TNEF, see the Transport-Neutral Encapsulation Format (TNEF) appendix (http://go.microsoft.com/fwlink/?LinkId=79773) in the Messaging API SDK on TechNet. TNEF must be enabled for Meeting Workspaces to work properly in Outlook meeting requests when a POP server is used as the messaging server. The Meeting Workspace properties are stored in a MAPI property associated with the meeting request form. TNEF is required to transport the properties from the meeting organizer to the meeting attendee. When the meeting attendee receives the Meeting Workspace properties (after the properties are transported by using TNEF), Outlook stores the properties in the attendee's client meeting request.

Ensuring that rich transport is used

Meeting organizers who want to use Meeting Workspace with POP messaging servers must ensure that rich transportrather than plain text transportis used to send the meeting request to recipients. Rich transport means ensuring that Rich Text Format attributes and iCalendar information are included together in the transport. This ensures that the Meeting Workspace properties attached to the meeting request persist in the e-mail transport from organizer to attendee. The meeting organizer must take the following steps to help ensure that rich transport is used for the meeting request: 55

Use Rich Text Format (RTF) when the meeting request is sent.

Do not attach an iCalendar (iCal) to the meeting request. (The iCalendar format is a common format for Internet calendars.) These are only requirements if POP is the messaging server. If the organizer is using an Exchange server, these options are not needed.

Set Rich Text Format

Rich Text Format for meeting requests in Outlook can be set per meeting request or as the default for all Outlook messages, including meeting requests. To set Rich Text Format for one meeting request 1. In the meeting request, in the To box, double-click the user name. 2. In the E-mail properties dialog, under Internet format, click Send using Outlook Rich Text format. You can also configure Outlook to use RTF for all Internet messages, including meeting requests. To set Rich Text Format as the default for all Internet messages 1. In Outlook, on the Tools menu, click Tools and click the Mail format tab. 2. Click Internet Format. 3. In the drop-down list in the Outlook Rich Text options section, select Send using Outlook Rich Text format.

Do not send an iCalendar attachment

To specify that an iCalendar attachment is not sent with a meeting request, clear Send as iCalendar on the Tools menu in the individual meeting request. This forces the iCalendar properties to be transported in the MIME message header. This option is not available if Outlook is used with Exchange server.

Viewing error message logs

Some Meeting Workspace errors are suppressed by default to help avoid user confusion. However, Meeting Workspace errors are written to the Windows Event Log, which can help you find problems when you are troubleshooting. Meeting Workspace users are alerted with an error message if there is a problem when they create a workspace or if a problem with the workspace arises later (for example, if a meeting workspace server fails). If problems occur separately from the process of initiating a meeting and creating a workspace, users might not understand what went wrong and what, if anything, they can do about the problem. Because these errors occur asynchronously, in some cases it might not be obvious that the error was triggered by a meeting update action.

56

When there are steps users can take to fix the problem, error messages about the problem are always shown to users. Error messages that might confuse users are suppressed by default. If you need to debug Meeting Workspace issues, it might be helpful to examine the error content in the Windows event log. You can view the log files by using the Windows Event Viewer. To open Event Viewer, in Control Panel, double-click Administrative Tools and double-click Event Viewer. You can see logging information related to Outlook by clicking Application Log in the left pane. See Also SharePoint Administrators Guide 2003 - Managing Meeting Workspaces (http://go.microsoft.com/fwlink/?LinkId=79762)

57

Configure general Outlook features

In this section: Configure Instant Search options in Outlook 2007 Configure categories in Outlook 2007 Configure Search Folder options in Outlook 2007 Disable the Group By feature for e-mail messages in Outlook 2007 Configure Navigation Pane options in Outlook 2007 Configure notification area messages in Outlook 2007 Configure retention settings and AutoArchive in Outlook 2007 Configure automatic message encoding options in Outlook 2007 Configure LDAP options in Outlook 2007

58

Configure Instant Search options in Outlook 2007

In Microsoft Office Outlook 2007, users can use the Instant Search feature to quickly locate an item, such as an e-mail message, a task, or an appointment; items that match the search are highlighted. Users can filter results by typing additional letters (known as wordwheeling). Note: This article is for Outlook administrators. To configure Outlook Instant Search options on your computer, see Find a message or item by using Instant Search (http://go.microsoft.com/fwlink/?LinkId=81358). You can lock down the settings to customize Instant Search by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. To download the Outlook template and other ADM files from the Microsoft Download Center, see 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/? LinkId=78161). To customize Instant Search options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how results are displayed, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Preferences\Search Options, double-click the setting that you want to set. For example, double-click Turn off wordwheel. 3. Click Enabled. For hit highlighting color, choose a color from the Background Color drop-down list. 4. Click OK. The settings you can configure for Instant Search are shown in the following table.
Instant Search option Description

Prevent installation prompts when Windows Desktop Search component is not present

When Outlook starts, prevents prompting users with a dialog box that asks if users want to download Windows Desktop Search (if it is not already installed). Also removes links in Outlook that allow users to download Windows Desktop Search.

59

Instant Search option

Description

Expand scope of searches

By default, Instant Search in Outlook returns results only from the currently selected folder. This setting expands the scope for Instant Search to all folders in the current module (for example, Mail or Calendar) Turns off search hit highlighting. Selects the background color used for highlighting matches in search results (default is yellow). Do not display search results as the user types a search query (turn off Word Wheel functionality).

Do not display hit highlights in search results Change color used to highlight search matches

Do not include Instant Search functionality for searches

More information about configuring Instant Search

Instant Search in Office Outlook 2007 works by accessing indexed content; indexing Outlook content results in quicker search results. By default, the text of all unrestricted Outlook items including attachments is indexed, a process that starts when Office Outlook 2007 runs for the first time. You can turn off full text indexing, or you can turn off just attachments indexing. Indexing takes place in the background and only when there is extra processing capacity available on the user's computer. If you install Office Outlook 2007 on a computer running Windows Vista, you can configure searching indexing options for Outlook. You can choose to index only attachments with certain file types. Or you can choose to not index attachments with certain file types, depending on security or privacy concerns. The following Windows settings determine how Outlook manages search indexing: Software\Policies\Microsoft\Windows\Search\PreventIndexingOutlook Software\Policies\Microsoft\Windows\Search\PreventIndexingEmailAttachments

Encrypted items and items restricted by using Information Rights Management (IRM) are not indexed. Advanced Find, a feature in earlier versions of Outlook, can also be used in Office Outlook 2007. You can modify Advanced Find options independently from Instant Search options. Notes If a users account is changed from Cached Exchange Mode to classic Online mode and if there is a copy of the users mailbox on the users computer, search might not work when the user is working offline. In this scenario, search will only work against folders 60

that have Make This Folder Available Offline selected (Tools | Send/Receive | Send/Receive Settings | Make This Folder Available Offline). Also, there is an issue with Rich Text Format (RTF) file type e-mail messages not being indexed when the following conditions are true: To resolve this issue, see Microsoft Knowledge Base article 927595: You cannot search RTF e-mail messages in Outlook 2007 (http://go.microsoft.com/fwlink/?LinkId=124063).

See Also Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)

61

Configure categories in Outlook 2007

Categories in Microsoft Office Outlook 2007 enable users to personalize and add categories to any type of Outlook information. You can configure several options for how categories work for users. Note: This topic is for Outlook administrators. To configure Outlook categories on your computer, see Configure color categories (http://go.microsoft.com/fwlink/?LinkId=81356). You can lock down the settings to customize categories by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To customize categories options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how results are displayed, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Miscellaneous, double-click the setting you want to set. For example, double-click Add new categories. 3. Click Enabled. 4. Specify the options for this setting and click OK. The settings you can configure for categories are shown below.
Categories option Description

Managing categories during e-mail exchanges

Control how categories are shared as users exchange e-mail messages. For example, specify that categories are not removed for users' incoming e-mail. Append new categories to the user's current list of categories. Deploys text of categories only; colors used for categories repeat as needed.

Add new categories

Categories and flags migration

When you upgrade users to Office Outlook 2007 from an earlier version of Outlook, each user's categories and flags are still available. Earlier versions of Outlook had several types of flags, 62

reminders, and labels that are rolled into categories functionality in Office Outlook 2007. Outlook migrates category and flag information into the new categories structure. Quick flags: When a user starts Office Outlook 2007 for the first time, all existing quick flags migrate to categories. The same color is used, but date information is not retained. If an item has a reminder flag, the reminder is migrated separately. Calendar labels: Labels also migrate when Outlook starts and are added to the user's categories list. Other categories: Categories for non-mail items (such as tasks) migrate to Office Outlook 2007 categories and a random color is assigned to each category. More information about existing categories is included in How categories and calendar labels from earlier versions are updated for Office Outlook 2007 (http://go.microsoft.com/fwlink/? LinkId=79798). More information about how flags are migrated is included in How flags from earlier versions are updated for Outlook 2007 (http://go.microsoft.com/fwlink/?LinkId=79799).

63

Configure Search Folder options in Outlook 2007

Microsoft Office Outlook 2007 folders are where items are stored such as new e-mail messages (Inbox folder), sent e-mail messages (Sent Items folder), or saved e-mail messages (folders that you can create). Messages are not stored in Search Folders. Search Folders are virtual folders that contain views of all e-mail items matching specific search criteria. Note: This topic is for Outlook administrators. To configure Search Folders in Outlook on your computer, see Configure Search Folder options (http://go.microsoft.com/fwlink/? LinkId=81355). You can lock down the settings to customize Search Folders by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To configure Search Folder options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Search Folders, double-click a Search Folders configuration option such as Keep search folders offline. 3. Click Enabled. 4. Select the setting you want, and then click OK. Note: If users use Search Folders with Exchange Server online (using a mailbox on the Exchange server) rather than with Cached Exchange Mode, the number of users that can be supported by the Exchange server might be decreased. The settings you can configure for Search Folders are shown below:
Search Folder option Description

Keep search folders offline Keep search folders in Exchange online

Specifies the number of days to keep a Search Folder active when running in offline mode. Specifies the number of days to keep a Search Folder active when running in online mode.

64

Search Folder option

Description

Default search folders at startup

Specifies whether to create the standard default Search Folders when Outlook starts for the first time. Specifies the maximum number of Search Folders for Exchange. Does not affect the number of Search Folders on a client computer.

Maximum Number of Online Search Folders per Mailbox

More information about configuring Search Folders

Search Folders display the results of previously defined search queries of your Outlook folders. The e-mail messages remain stored in one or more Outlook folders. Each Search Folder is a saved search that is kept up to date, monitoring all Outlook folders for new items that match the criteria of the Search Folder. When users create a Search Folder, they have a number of default Search Folder options to choose from, such as Mail with attachments or Mail from specific people. They can also create custom Search Folders. You can configure how long Search Folders remain active for Cached Exchange Mode accounts and for online Exchange Server accounts. You can specify the number of days after which Search Folders become dormant that is, items listed in the Search Folder are no longer up to date with current searches of Outlook folders. A dormant Search Folder appears in italics in a user's Navigation Pane. When a user opens a dormant Search Folder, the view is refreshed and the elapsed time count begins again. The time period that you specify with this setting begins the last time that a user clicked the Search Folder. You can specify a different number of days for users in Exchange online mode and in Cached Exchange Mode. Separate counts are maintained for each Search Folder for each mode. The default value is 60 days. If you specify zero days, Search Folders in Exchange online mode are always dormant. You can also limit the number of Search Folders allowed in each user mailbox, or you can disable the Search Folders user interface altogether.

65

Disable the Group By feature for e-mail messages in Outlook 2007

By default, Microsoft Office Outlook 2007 applies a grouping feature when displaying e-mail messages in folders. This feature is applied to custom views as well as default views. You can deploy Outlook without the Group By feature by using the Modify user settings page of the Office Customization Tool (OCT). This setting cannot be locked down by using Group Policy. Note: This topic is for Outlook administrators. To configure the Outlook Group By feature on your computer, see Group or ungroup messages in your Inbox (http://go.microsoft.com/fwlink/?LinkId=81354). To configure Group By behavior in the OCT 1. In the OCT, on the Modify user settings page, click the plus sign ( + ) next to Microsoft Office Outlook 2007. 2. Click Miscellaneous, and then double-click Disable Show In Groups and new style arrangements on old views. 3. Select Apply Changes, then select the Check to disable Show In Groups and Applied Arrangements check box. 4. Click OK. Note: The Group By feature can be problematic for upgrades, especially if a user has created a custom view in a folder. For example, a user might have specified a custom view to sort by date or by sender. When Outlook is upgraded to Office Outlook 2007, the Group By feature is applied regardless of existing views, and users have to re-create any custom views. Disabling the feature prevents this behavior.

66

Configure Navigation Pane options in Outlook 2007

You can configure the modules in the Navigation Pane in Microsoft Office Outlook 2007 (such as Calendar, Mail, and so on) to appear in a specific order for users, or to display only certain modules; there are other options as well. You use the Office Customization Tool (OCT) to distribute registry keys that specify how modules are displayed. The Navigation Pane options cannot be locked down by using Group Policy. Note: This topic is for Outlook administrators. To configure Navigation Pane options on your computer, see Configure Navigation Pane options (http://go.microsoft.com/fwlink/? LinkId=81353). To set Navigation Pane options by using the Office Customization Tool 1. In the OCT, click Add/Modify Registry Entry. 2. In the dialog box, enter the information for each Navigation Pane registry entry that you want to configure. For example, to display four large buttons on the Navigation Pane for users, enter the following information: Root: HKEY_CURRENT_USER Data type: REG_SZ Key: Software\Microsoft\Office\12.0\Outlook\Preferences Value name: NumBigModules Value data: 4 3. Click OK. 4. When you have finished making all of your 2007 Microsoft Office system customizations in the OCT, select Save As... in the File menu. 5. Specify a unique name for the file (with an .msp file extension) and save it in the folder of the network installation point. 6. Click Save. For more information about customizing Office by using the OCT and deploying customized Office with customized settings, see Customize the 2007 Office system and Deploying the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303395.aspx).

Options you can configure for Navigation Pane modules

The following table lists the registry settings you can configure for your custom installation. You add these value entries in the following subkey: 67

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Preferences
Value name Value data (Data type) Default value Description

NumBigModules

REG_SZ

Controls how many large buttons (each representing a Navigation Pane module) appear on the Navigation Pane. The maximum number you can specify to be displayed is 8. Determines the order in which the modules are displayed on the Navigation Pane. The data is an ordered list of indexes, where each position represents a Navigation Pane module, and the number in that position determines where the matching module appears. The index positions match this list: Mail, Calendar, Contacts, Tasks, Notes, Folder List, Shortcuts, Journal. For example, if the user switches Mail to be the third module showing, and Contacts to be the first, the registry value has this data: 3,2,1,4,5,6,7,8

ModuleOrder

REG_SZ

1,2,3,4,5,6,7,8

68

Value name

Value data (Data type)

Default value

Description

ModuleVisible

REG_SZ

1,1,1,1,1,1,1,0

Determines whether a module is visible on the Navigation Pane. (This does not affect the order of items listed in the Go menu.) The values match the positions used in the module ordering list. For example, the first position determines whether Mail is shown. By default, the Journal is not shown in the Navigation Pane. You can choose to not display other modules as well. For example, to not display Contacts, Tasks, Notes, or Shortcuts, set this data: 1,1,0,0,0,1,0,0

69

Configure notification area messages in Outlook 2007

As users work in Microsoft Office Outlook 2007, messages appear in the notification area with information about network and Microsoft Exchange Server availability. You can configure how and when these messages are displayed to users in the notification area by default. Note: This article is for Outlook administrators. To configure the notification area on your computer, see Hide the Outlook icon in the notification area of the taskbar (http://go.microsoft.com/fwlink/?LinkId=81352). You can deploy default settings for these messages by using the Modify user settings page in the Office Customization Tool (OCT). These settings cannot be enforced by using Group Policy. Configure Outlook notification area message behavior 1. In the OCT, on the Modify user settings page, click the plus sign (+) next to Office Outlook 2007. 2. Click the Outlook System Tray icon. 3. Double-click an option (such as Show Network Warnings), and then click Apply Changes. 4. Select the check box for the option displayed (such as the Check to Show Network Warnings check box), and then click OK. 5. When you have finished making all your Office customizations in the OCT, select Save As... in the File menu. 6. Specify a unique name for the file (with an .msp file name extension) and save it in the folder of the network installation point. 7. Click Save. For more information about how to customize Office by using the OCT and how to deploy customized Office with customized settings, see Customize the 2007 Office system and Deploying the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303395.aspx).

More information about notification area messages

The kinds of messages are as follows: Network warnings Example: Network problems are preventing connection to the Microsoft Exchange Server servername.

70

 Exchange Server warnings Example: Outlook is trying to retrieve data from the Microsoft Exchange Server computer. Synchronization messages Example: Outlook is preparing a local copy of your Exchange mailbox. This one-time process may take several minutes to complete. Some of your data might not be shown until the process is complete. Note that there are no configuration options available in the OCT for this message type.

71

Configure retention settings and AutoArchive in Outlook 2007

In this article: Configuring retention settings Configuring AutoArchive settings How AutoArchive works in Outlook How retention settings work in Outlook Working with Outlook archiving and Exchange document management

In Microsoft Office Outlook 2007, retention settings and AutoArchive help determine how e-mail is managed in user mailboxes. You can configure settings for these features for users in your organization, determining, for example, how frequently to run AutoArchive and whether to prompt users before running AutoArchive. If you configure Exchange Server document management settings for users as well as Outlook retention and AutoArchive settings, be aware that the Exchange settings can affect Outlook retention and AutoArchive behavior. See the Working with Outlook archiving and Exchange document management section later in this article. Note: This article is for Outlook administrators. To configure Outlook AutoArchive options on your computer, see Configure AutoArchive settings (http://go.microsoft.com/fwlink/? LinkId=100151).

Configuring retention settings

You can lock down the settings to customize retention settings by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other administrative files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. Use the following procedure to customize retention settings by using Group Policy. Customize retention settings by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how retention settings work, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Other\AutoArchive, double-click Retention Settings. 72

3. Click Enabled, and then configure retention settings options. For example, enable retention settings by selecting Turn Retention Policies On. 4. Click OK. The settings you can configure for retention settings are shown in the following table. Note that retention settings supersede archive settings for folders.
AutoArchive option Description

Turn Retention Policies On Maximum number of days to retain items

Enable retention settings for user mailboxes. Specify the numbers of days to retain items in Inbox, all mail folders excluding Inbox, Calendar items in any folder, and all other folders being AutoArchived. Specify whether to move items to the Deleted Items folder or delete items permanently. Specify a site that describes your organization's retention policies. There is no default URL.

For items not being retained URL with corporate retention policy information

Configuring AutoArchive settings

You can lock down the settings to customize AutoArchive by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. Use the following procedure to customize AutoArchive options by using Group Policy. Customize AutoArchive options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how AutoArchive works, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Other\AutoArchive, double-click AutoArchive Settings. 3. Click Enabled, and then configure AutoArchive options. For example, enable AutoArchive by selecting Turn on AutoArchive and choose an archiving interval by selecting a number in the Run AutoArchive every <x> days box. 4. Click OK. The settings you can configure for AutoArchive are shown in the following table. 73

AutoArchive option

Description

Turn on AutoArchive

Set AutoArchive to run for users, with a frequency specified by the Run AutoArchive every <x> days setting. Specify an AutoArchive interval in numbers of days. Notify users that AutoArchive will run, rather than running silently. Delete expired e-mail messages, rather than moving them to an archive folder. Move Outlook items to the archive file or delete the items. Display the archive folder in the user's Outlook folder list. Specify how long to keep items before archiving or deleting them. Permanently delete items rather than moving them to the Deleted Items folder.

Run AutoArchive every <x> days Prompt before AutoArchive runs Delete expired items (e-mail folders only) Archive or delete old items Show archive folder in folder list Clean out items older than Permanently delete old items

How AutoArchive works in Outlook

Outlook mailboxes grow as users create and receive items. To keep mailboxes manageable, users need another place to store or archive older items that are important but not frequently used. It is typically most convenient to automatically move these older items to the archive folder and to discard items whose content has expired and is no longer valid. AutoArchive manages this process automatically for users.

Scheduling automatic archiving

AutoArchive is on by default and runs automatically at scheduled intervals, removing older and expired items from folders. Older items are those that reach the archiving age a user specifies (the default archiving age varies by the type of Outlook item). Expired items are mail and meeting items whose content is no longer valid after a certain date, such as a mail item set to expire two months ago that still appears in a user's Inbox. Users can specify an expiration date on items in Outlook at the time they create or send the item or at a later date. When the item expires, it is unavailable and shows in a folder list with a strikeout mark through it.

74

Archive folder location

When AutoArchive runs, it can delete items or move items to an archive folder, depending on the settings you specify. The archive file is an Outlook data file (PST file) that appears as Archive Folders in the Outlook folder list. The first time AutoArchive runs, Outlook creates the archive file automatically in the following location: %UserProfile%\Local Settings\Application Data\Microsoft\Outlook\Archive.pst

How retention settings work in Outlook

In addition to the AutoArchive settings, you can also enable retention policy settings for items in user mailboxes. Retention policy settings can help users to follow retention policy guidelines that your company establishes for document retention. Note: Because retention policies settings are part of Outlook's AutoArchive functionality, retention settings only run when AutoArchive is run. Running an archive manually does not trigger retention settings enforcement. Retention Group Policy settings in Outlook can be configured to follow company policies, to encourage users to retain documents and items for only a fixed period of time. Retention settings implementation requires AutoArchive to be enabled, but retention settings take precedence over AutoArchive settings.

Working with Outlook archiving and Exchange document management

If Microsoft Exchange is configured to implement document management features that set e-mail message expiration dates for user mailboxes, make sure that Outlook archiving settings are configured so that item expiration and archiving or deletion work predictably for users. By default, in most configurations, Exchange retention policies override Outlook retention settings. Users who are not aware that Exchange policies take precedence might lose Outlook items. This can happen if users expect their AutoArchive settings to move items to an Outlook data file and instead the items are removed by Exchange document management procedures. To help prevent user confusion this scenario, disable the option to configure manual archiving. Use the following procedure to disable manual archiving by using Group Policy. Disable manual archiving by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Other\AutoArchive, double-click Disable File|Archive. 3. Click Enabled. 75

4. Click OK.

76

Configure Unicode options in Outlook 2007

Microsoft Office Outlook 2007 can provide full Unicode support. Using Outlook in Unicode mode is especially advantageous for organizations with multilingual needs andbecause Outlook Unicode-formatted files have higher storage capacities than non-Unicode filesfor users who need very large Outlook files. Taking advantage of Unicode support in Outlook depends on specific criteria that are checked when users run Outlook. If the criteria for using Unicode are met and users are running in Unicode mode, Unicode is used throughout Outlook when it is used with Exchange Server (for email messages, the Address Book, and so forth). If the criteria for using Unicode are met, you can enforce migrating users to Unicode if that is important in your organization. For an explanation of how Outlook determines whether to use Unicode and recommendations for implementing a migration to Unicode, see Enforcing Unicode mode for Outlook users later in this topic. Unicode format is used for new PST files by default. You can also use a Group Policy setting to enforce Unicode format for new PST files. You can lock down the settings to customize Unicode by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To enforce Unicode format for new PST files by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize the Unicode format, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Miscellaneous, double-click PST Settings. 3. Double-click Preferred PST Mode (Unicode/ANSI). 4. Click Enabled to enable the policy setting. 5. In the Choose a default format for new PSTs drop-down list, select Enforce Unicode PST. 6. Click OK. To enforce Unicode mode in Outlook by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Account Settings, double-click Exchange Settings. 3. Double-click Exchange Unicode Mode Ignore Archive Format. 4. Click the Enabled radio button to enable the policy configuration. 77

5. Select the Ignore existing format of the Archive PST check box, and click OK. 6. Double-click Exchange Unicode Mode Ignore OST Format. 7. Click the Enabled radio button to enable the policy configuration. 8. In the Choose whether existing OST format determines mailbox mode drop-down, select Create new OST if format doesn't match mode. Users are prompted for the file name of the new OST file. or To prompt users with a dialog box that allows them to defer creating a new OST, select Prompt to create new OST if format doesn't match mode. Users are prompted to decide whether to create the new OST file now or later, and then (if they choose to create the file now) for the file name of the new OST file. or To avoid user prompts, select OST Format determines mode. 9. Click OK. The settings you can configure for Instant Search are shown below.

More information about configuring Unicode

More information about Unicode and Unicode configuration options is included in the following sections.

Choosing between Unicode or non-Unicode mode

To determine whether to use Unicode mode or non-Unicode (ANSI) mode, Outlook evaluates a set of requirements and options. One requirement for Unicode mode is that users must have Exchange 2000 or later accounts. Outlook also checks the Unicode or ANSI formats of users' Offline Store (OST) files and the default archive files. Finally, Outlook checks the format of users' PST files that are used as a delivery location (if any). Caution: Switching between Unicode mode and non-Unicode mode (ANSI) can cause data loss in multilingual text fields or prevent text from being readable. For this reason, users who begin using Outlook in Unicode mode should continue to use Unicode mode. If you want to encourage users in your organization to use Unicode for Outlook, you can deploy Outlook so users can run in Unicode mode. One deployment option is to establish an environment in which, for most users, the criteria that Outlook checks to allow Unicode mode are met. Unicode is used by default if the criteria are met, unless you set options to use ANSI. Another option is to require Unicode for Outlook usage (when supported by an appropriate Exchange Server version) by setting options that create new Unicode user files automatically, if that is necessary for Outlook to run in Unicode mode. You can also use a combination of these approaches.

78

Coordinating Cached Exchange Mode and Unicode deployment

If you plan to deploy Cached Exchange Mode with Outlook 2003, you might want to configure and deploy options for migrating users to Unicode mode first. Cached Exchange Mode synchronizes users' OST and Offline Address Book (OAB) files with Exchange Server data. When you deploy Unicode options to users, synchronizing OST and OAB files might also be required. For example, Outlook files are synchronized with Exchange Server in the following Unicode deployment scenarios: When you deploy a new offline Outlook profilefor example, to move current offline users to Unicode modeOutlook synchronizes OST and OAB files, after creating the new files for users as part of the new profile. When Outlook users are moved to an Exchange 2003 server with a Unicode OAB, the new OAB is downloaded. In scenarios like these, you might want to wait to deploy Cached Exchange Mode until after you have deployed Unicode options for your organization. This will help minimize the load on your Exchange servers and the time users spend downloading data to their computers.

Facilitating usage of Unicode mode by Outlook

Using Unicode for messaging and other Outlook features has benefits that you might want your users to take advantage of, without mandating that everyone migrate to Unicode mode directly when Outlook 2003 is installed. To facilitate greater usage of Unicode mode, you can help provide a messaging environment configured to help Outlook run in Unicode mode. Since Outlook uses Unicode mode by default if all criteria it looks for are met, take steps to make sure that the requirements are met, such as the following: Using the Office Customization Tool (OCT), create a new Outlook profile to deploy to users. A new offline profile creates a new OST file for users and a new default archive file by default. Both files use the new Unicode file format. Ensure that in the new Outlook profile, users' Exchange accounts are on Exchange Server 2000 or later. Deploy Outlook to your users. You can deploy Outlook using your organization's standard Office deployment method. It is straightforward to create and customize a new Outlook profile by using the OCT. To create new Outlook offline profiles for users 1. In the OCT, in the Outlook section, on the Customize Default Profile page, click New Profile. 2. In the Profile name box, type a name for the new Outlook profile, and click Next. 3. On the Outlook: Specify Exchange Settings page, click the Configure an Exchange server connection radio button. 4. In the User Name box, leave the default user name system variable, or enter a different variable.

79

5. In the Exchange Server box, enter the name of an Exchange server. (The Exchange server name is replaced with the correct Exchange server when the user starts Outlook for the first time after upgrading.) 6. Click More Settings. 7. On the Microsoft Exchange Server page, select the Enable offline use check box to deploy a new OST file, and click OK. 8. Click Next. 9. After you complete all desired customizations in the OCT, click Finish to create a Setup customization file. 10. Update users' computers with the new profile. 11. For more information about configuring users' computers with the new profile by using the Setup customization file, see Run Setup for the 2007 Office system on users' computers.

Enforcing Unicode mode for Outlook users

There might be scenarios in which it is important that all users in an organization are migrated to use Unicode mode in Outlook when Office Outlook 2007 is installed, without modifying all users' profiles. You can enforce migrating users to Unicode by making sure that the criteria that Outlook uses for determining if users run in Outlook mode are met, or that Outlook takes steps to help ensure that Unicode file formats are used in users' profiles by creating and synchronizing new Outlook files, if necessary. The first criterion for using Unicode mode is that users must use Outlook with Exchange Server 2000 or later. Next, Outlook checks the format of a user's OST file to determine if the file format is Unicode or non-Unicode (ANSI). If the format of the OST file is ANSI, Outlook runs in ANSI mode. However, you can set a policy so that when Outlook checks the file format, if a user has an ANSI OST file, a new Unicode OST file is automatically created and synchronized with Exchange Server. You can define the policy so that users are prompted with a dialog box that notifies them that their new OST file is about to be synchronized with the Exchange server, so users can confirm to proceed with the update at that time. Or you can require that new OST files are created without providing users the option to defer the action. Outlook next checks the file format for the user's default archive file, if one exists. You can also set a policy that automatically creates a new Unicode default archive file. (Users can still access ANSI archive files.) Unlike the policy that manages new Unicode OST files, you cannot provide the option for users to defer creation of a new default archive file. If a user's mail delivery location is a PST file, Outlook checks the delivery PST file to determine if the file format is Unicode. However, you cannot require a new Unicode PST file to be created to replace the existing PST file if Outlook determines that a user has an ANSI PST file. In this scenariowhere Outlook delivers PST files to ANSI and you want to require Unicode mode for usersyou can instead create and deploy new profiles to users with the delivery location set to new PST files, which will be Unicode by default.

80

Pointing Outlook to use a new delivery PST file automaticallywithout users specifying the changemight lead users to believe that their existing mail has vanished. Older mail is still in the original PST file, but that file is no longer in the user's profile and is not accessible by default. Users must manually add the older PST file back to their profile to access the information. Because the PST file being removed from the user profile can be perceived as data loss by users though the data still exists, it is not where users can readily see and access itthe option to automatically switch to a new Unicode PST is not provided. You may want to carefully time the implementation of the policies that might create and populate new Unicode files. When Outlook creates and synchronizes new Unicode OSTs and default archive files, users must wait for server data to download. You should also make sure that users have synchronized with Exchange Server prior to the new policies taking effect. Local changes that are not synchronizedsuch as e-mail messages in a user's Outbox or updates to Contacts informationare lost.

Using Unicode format for Outlook messages dragged to the desktop

When you use the Microsoft Windows drag-and-drop feature to drag an Outlook item to the Windows desktop, the format of the file that is automatically created is Unicode by default. You can configure a default option by using the Office Customization Tool (OCT) to use ANSI for the message format instead of Unicode. You can lock down the settings to customize this option by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool, in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To use Unicode format for message files that are dragged to the desktop from Outlook 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Other\Advanced, double-click Use Unicode format when dragging e-mail message to file system. 3. Click the Disabled radio button to enforce using ANSI format instead of Unicode format for e-mail messages dragged to the file system. 4. Click OK.

81

Configure automatic message encoding options in Outlook 2007

Microsoft Office Outlook 2007 can automatically select an optimal encoding for outgoing e-mail messages. This feature increases the likelihood that when a user sends a message with Outlook, people receiving the message will see all the characters rendered properly, even if they run older e-mail programs. Note: This topic is for Outlook administrators. To configure Outlook message encoding options on your computer, click Tools in the Outlook menu bar, then click Options. On the Mail Format tab, click International Options. Select the options that you prefer in the Encoding Options area, then click OK. Automatic messaging encoding typically results in less configuration work for administrators and a better experience for users. However, you can instead establish a default encoding for outbound e-mail messages. You can lock down the settings to customize message encoding by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To customize message encoding options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how results are displayed, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Mail Format\International Options, double-click the policy setting you want to set. For example, double-click Autoselect encoding for outgoing messages. 3. Click Enabled. Where appropriate, choose an option provided on the Setting tab. 4. Click OK.

82

The settings you can configure for message encoding are shown below:
Message encoding option Description

Auto-select encoding for outgoing messages

Enable the setting to disallow users from turning off automatic message encoding. Disable the setting to turn off automatic message encoding and disallow users from enabling the option. In the drop-down list, choose a preferred encoding for outgoing messages. Choose to ignore the euro character when automatic messaging encoding is enabled, or to convert the message to UTF-8 format.

Encoding for outgoing messages Euro encoding for outgoing messages

More information about automatic messaging encoding in Outlook

The following sections include more information about automatic message encoding and message encoding options.

How automatic message encoding works

Outlook uses automatic message encoding by default, scanning the entire text of the outgoing message to determine a minimal popular encoding for the message. Outlook selects an encoding that is capable of representing all of the characters and that is optimized so the majority of the receiving e-mail programs can interpret and render the content properly. With earlier versions of Outlook, users had to manually overwrite format encoding to choose the most appropriate encoding for an individual message. This is no longer necessary. This table shows examples of how this encoding works.
If the message contains these characters: Outlook selects this encoding:

English (ASCII) text (A-Z, a-z) German (Latin 1) text (A-Z, a-z and Umlauts) Greek text (A-Z, a-z and Greek characters) Japanese text (A-Z, a-z, Hiragana, Katakana, Kanji) Multilingual text (different scripts)

US-ASCII Western European (ISO) Greek (ISO) Japanese (JIS) Unicode (UTF-8)

83

This works for users sending Internet mail through the POP/SMTP or IMAP transport, or for messages sent through Microsoft Exchange Server. Note: To use the automatic message encoding feature, users sending the message must have Microsoft Internet Explorer 5.5 or later installed.

Setting default encoding for outbound messages

You can configure Outlook to use a default encoding for outbound e-mail messages. This encoding is used for all outbound messages if Auto-Select encoding is not enabled. This encoding is also used as the preferred encoding if the Auto-Select encoding algorithm finds multiple suitable encodings for the message. By default, Outlook sets preferred encoding to a popular Internet encoding corresponding to the active Microsoft Windows code page of the user's computer. For example, Outlook specifies Western European (ISO) when it runs on Western European Latin1 Windows code page 1252.

Outlook encoding support

Outlook supports the encodings listed in the table below when sending and receiving e-mail messages. Note: For automatic encoding selection in Outlook to work properly, you must make sure that appropriate international support (NLS files and fonts) is installed on users' computers. For more information about enabling international support, see Preparing users' computers for international use. By default, automatic encoding selection in Outlook considers for detection all encodings marked Yes in the table below.
Name Character set Code page Auto-select?

Arabic (ISO) Arabic (Windows) Baltic (ISO) Baltic (Windows) Central European (ISO) Central European (Windows) Chinese Simplified (GB2312) Chinese Simplified (HZ) 84

ISO-8859-6 Windows-1256 ISO-8859-4 Windows-1257 ISO-8859-2 Windows-1250 GB2312 HZ-GB-2312

28596 1256 23594 1257 28592 1250 936 52936 Yes Yes Yes

Name

Character set

Code page

Auto-select?

Chinese Traditional (Big5) Cyrillic (ISO) Cyrillic (KOI8-R) Cyrillic (KOI8-U) Cyrillic (Windows) Greek (ISO) Greek (Windows) Hebrew (ISO-Logical) Hebrew (Windows) Japanese (EUC) Japanese (JIS) Japanese (JIS-Allow 1 byte Kana) Japanese (Shift-JIS) Korean Korean (EUC) Latin 3 (ISO) Latin 9 (ISO) Thai (Windows) Turkish (ISO) Turkish (Windows) Unicode (UTF-7) Unicode (UTF-8) US-ASCII Vietnamese (Windows) Western European (ISO) Western European (Windows)

Big5 ISO-8859-5 KOI8-R KOI8-U Windows-1251 ISO-8859-7 Windows-1253 ISO-8859-8-I Windows-1255 EUC-JP ISO-2022-JP ISO-2022-JP Shift-JIS KS_C_5601-1987 EUC-KR ISO-8859-3 ISO-8859-15 Windows-874 ISO-8859-9 Windows-1254 UTF-7 UTF-8 US-ASCII Windows-1258 ISO-8859-1 Windows-1252

950 28595 20866 21866 1251 28597 1253 38598 1255 51932 50220 50221 932 949 51949 28593 28605 874 28599 1254 65000 65001 20127 1258 28591 1252

Yes

Yes

Yes Yes

Yes

Yes

Yes

Yes Yes

Yes Yes Yes Yes

85

See Also Configure Unicode options in Outlook 2007

86

Configure LDAP options in Outlook 2007

Lightweight Directory Access Protocol (LDAP) is an Internet protocol that software programs can use to query directory services so users can easily find other e-mail users on the Internet or corporate intranet. Microsoft Exchange Server supports LDAP queries, enabling users to look up address information on the server. LDAP can also be used to search a number of global directories on the Internet, such as Yahoo! Enhanced LDAP support in Microsoft Office Outlook 2007 includes the ability to disable certain searches (directory browsing) by default and the option to create customized filters. You can configure LDAP search behavior by using the Office Customization Tool (OCT) or a Group Policy setting. When you define custom filters, you can provide the filters to users by setting registry keys or by using an Outlook Profile (PRF) file.

Configuring LDAP directory browsing

By default, Office Outlook 2007 directory browsing or Virtual List View (VLV) searches for LDAP are disabled, and users can enable the feature.

Disabling directory browsing

You can prevent users from using directory browsing by configuring a setting in Group Policy. You can lock down the setting to enforce disabling directory browsing by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool, in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To disallow enabling directory browsing for LDAP by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how results are displayed, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007 \Miscellaneous, double-click Turn on VLV Browsing on LDAP servers. 3. Click Disabled. 4. Click OK.

More information about LDAP directory browsing

In Outlook 2003, directory browsing was enabled by default. However, users must work with small LDAP directories when using directory browsing. A new registry key was provided with Outlook 2003 Service Pack 2 to allow VLV searches to be disabled. Office Outlook 2007 uses the same 87

registry keys to regulate this feature. If your environment uses small LDAP directories and requires directory browsing, you can enable the feature by configuring the option in the Office Customization Tool or by setting the registry key (to make it a default option), or by using Group Policy (to enable and lock down the setting). If you do not lock down the setting, users can enable or disable the option by using the check box on the Search tab of the Microsoft LDAP Directory dialog box in Outlook. The existing registry key that managed this LDAP setting in earlier versions of Outlook continues to override server-specific settings that users choose. The registry key is: HKCU\Software\Microsoft\Office\12.0\Outlook\LDAP\DisableVLVBrowsing If this registry key is set to 0, the check box is cleared and dimmed so that users cannot modify it. If this registry key is set to 1, the check box is selected and dimmed so that users cannot modify it.

Default and customized check names filters

Outlook uses the following default LDAP filters if you do not provide a custom check names filter. You can define a custom filtersearch basethat describes the specific query for checking names and returning a list of matching entries from the LDAP directory.

Default LDAP filters

Outlook uses a default filter if the registry key for setting a custom check names filter is empty. The default filter used depends on two criteria: Is Active Directory server used? Is a browse list display requested or is an e-mail name queried?

If the user requests a browse list, the results include items that are not e-mail addresses, such as printers. The following are the default filters for each scenario: For queries using an Active Directory server, where a user queries an e-mail name: (&(mail=*)(|(mail=%s*)(cn=%s*)(sn=%s*)(givenName=%s*)(displayName=%s*)) By including the (mail=*) value, the e-mail name is required by this filter. For queries using an Active Directory server, where a browse list is displayed (which can include items that are not e-mail names): (&(|(mail=%s*)(cn=%s*)(sn=%s*)(givenName=%s*)(displayName=%s*))) For queries using any other server (not Active Directory), with an e-mail name query: For queries using any other server (not Active Directory), with the browse list displayed: (&(mail=*)(|(mail=%s*)(cn=%s*)(sn=%s*)(givenName=%s*)) (&(|(mail=%s*)(cn=%s*)(sn=%s*)(givenName=%s*)))

88

Defining customized LDAP filters

You can provide a custom LDAP filter so that users can query additional information you provide on your LDAP server. You can define a custom filter by using an Outlook Profile (PRF) file, or you can write the custom filter string directly into the Outlook profile in the registry. For example, you might have a CustomerID property, which is not included in the default filter. You could define the following LDAP custom filter to allow users to search on the CustomerID property: (&(mail=*)(|(mail=%s*)(displayName=%s*)(customerID=%s*) Note: The LDAP Request For Comments (RFC) defines the format for creating search filter strings. For more information about constructing LDAP filters, see LDAP Request For Comments (RFC) (http://go.microsoft.com/fwlink/?LinkId=72067). You can also set a blank search base by creating a blank filter. This is useful when you want LDAP to use the default filter specified in the RootDSE. You create a blank filter by clearing the registry entry or by setting the CheckNames property to "" in the Outlook Profile (PRF) file. Define a custom filter by using a PRF file 1. In a text editor (such as Notepad), open the PRF file. You can use the Office Customization Tool to create a default PRF file to edit. For more information, see Outlook in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). 2. In Section 4 (which contains the default values for each service), enter CheckNames= as a new property and type the custom search filter as the value. For example, enter the following: &(mail=*)(|(mail=%s*)(displayName=%s*)(customerID=%s*) 3. In Section 6 (which contains the mapping values for profile properties), define the CheckNames property. In the [LDAP Directory] section, enter the following new entry: CheckNames=PT_STRING8,0x6624 4. Save the file. You can then deploy the PRF file to your users. For more information, see Apply an Outlook Profile (PRF) File to configure Outlook profiles. You can also configure other LDAP options by using a customized PRF file. See Example: Defining LDAP options in a custom PRF file later in this topic. Define a custom filter by using the registry 1. Start the registry editor, and then search for the registry key 001e6604. 2. Define a new LDAP search string as the registry key value, or replace the existing value. 3. Exit the registry editor. In addition to using a custom filter for an e-mail name query, Outlook might use the same filter in a converted form for a browse list query. Outlook uses the custom filter in a converted form when the Enable Browsing check box is selected in the Search tab in the Microsoft LDAP Directory 89

dialog box in Outlook. If you enable the browsing feature, or allow it to be enabled by users, you can help prevent search errors for users by testing the filter for both querying e-mail names and for bringing up a browse list.

Mapping server LDAP properties to Outlook MAPI properties

When you configure custom filters, it can be helpful to know the MAPI property names that correspond to the LDAP display names. MAPI property name PR_USER_CERTIFICATE PR_BUSINESS_TELEPHONE_NUMBER_A PR_GIVEN_NAME_A PR_INITIALS_A PR_STREET_ADDRESS_A PR_LOCALITY_A PR_STATE_OR_PROVINCE_A PR_POSTAL_CODE_A PR_COUNTRY_A PR_TITLE_A PR_COMPANY_NAME_A PR_ASSISTANT_A PR_DEPARTMENT_NAME_A PR_BUSINESS_TELEPHONE_NUMBER_A PR_HOME_TELEPHONE_NUMBER_A PR_BUSINESS2_TELEPHONE_NUMBER_A PR_HOME2_TELEPHONE_NUMBER_A PR_PRIMARY_FAX_NUMBER_A PR_MOBILE_TELEPHONE_NUMBER_A PR_ASSISTANT_TELEPHONE_NUMBER_A PR_PAGER_TELEPHONE_NUMBER_A PR_COMMENT_A PR_EMS_AB_PROXY_ADDRESSES 90 MAPI ID 3a22 3a08 3a06 3a0a 3a29 3a27 3a28 3a2a 3a26 3a17 3a16 3a30 3a18 3a08 3a09 3a1b 3a2f 3a23 3a1c 3a2e 3a21 3004 800f LDAP display name usercert telephonenumber givenName initials streetAddress l st postalCode co title company msExchAssistantName department telephoneNumber homePhone otherTelephone otherHomePhone facsimileTelephoneNumber mobile telephoneAssistant pager info proxyAddresses

PR_USER_X509_CERTIFICATE PR_EMS_AB_X509_CERT

3a70 8c6a

userSMIMECertificate userCertificate

Example: Defining LDAP options in a custom PRF file

You can customize a PRF file to include LDAP options, such as defining a custom names filter or enabling browse list capability. Here is a sample PRF file with several LDAP options configured. Office Customization Tool; ************************************************************** ; Section 1 - Profile Defaults ;************************************************************** [General] Custom=1 DefaultProfile=Yes OverwriteProfile=Append ModifyDefaultProfileIfPresent=TRUE ;************************************************************** ; Section 2 - Services in Profile ;************************************************************** [Service List] Service1=LDAP Directory ;*************************************************************** ; Section 4 - Default values for each service. ;*************************************************************** [Service1] UniqueService=No ServerName=ldap.boeing.com DisplayName=BoeingCorporate ConnectionPort=389 UseSSL=FALSE UseSPA=FALSE EnableBrowsing=1 UserName= SearchBase= SearchTimeout=60 MaxEntriesReturned=100 91

;This is where the value is defined CheckNames=(&(mail=*)(!(mail=%s*)(customerID=%s*))) ;This specifies whether the Custom search base Boolean flag is set DefaultSearch=1 ;*************************************************************** ; Section 6 - Mapping for profile properties ;*************************************************************** [LDAP Directory] ServiceName=EMABLT ServerName=PT_STRING8,0x6600 UserName=PT_STRING8,0x6602 UseSSL=PT_BOOLEAN,0x6613 UseSPA=PT_BOOLEAN,0x6615 DisplayName=PT_STRING8,0x3001 ConnectionPort=PT_STRING8,0x6601 SearchTimeout=PT_STRING8,0x6607 MaxEntriesReturned=PT_STRING8,0x6608 EnableBrowsing=PT_BOOLEAN, 0x6622 SearchBase=PT_STRING8,0x6603 CheckNames=PT_STRING8,0x6624 DefaultSearch=PT_LONG, 0x6623 See Also MS Strategy for Lightweight Directory Access Protocol (LDAP) (http://go.microsoft.com/fwlink/? LinkId=72064) Introduction to Lightweight Directory Access Protocol (LDAP) (http://go.microsoft.com/fwlink/? LinkId=72065)

92

Configure Outlook security and protection features

In this section: Set consistent Outlook 2007 cryptography options for an organization Specify the method Outlook uses to manage virus prevention features Customize attachment settings in Outlook 2007 Customize programmatic settings in Outlook 2007 Customize ActiveX and custom forms security settings in Outlook 2007 Manage trusted add-ins for Outlook 2007 Configure security for Outlook 2007 folder home pages Configure junk e-mail settings in Outlook 2007 Configure Information Rights Management in Outlook 2007

93

Set consistent Outlook 2007 cryptography options for an organization

You can control many aspects of Microsoft Office Outlook 2007 cryptography features to help configure more secure messaging and message encryption for your organization. For example, you can configure a Group Policy setting that requires a security label on all outgoing mail or a setting that disables publishing to the Global Address List. You can lock down the settings to customize cryptography by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To customize cryptographic options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize cryptographic settings, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007 \Security\Cryptography, double-click the policy setting you want to set. For example, double-click Do not display 'Publish to GAL' button. (Some options are included in the Signature Status dialog box folder.) 3. Click Enabled. When appropriate, choose an option that displays on the Setting tab. 4. Click OK. The settings you can configure for cryptography are shown below.
Cryptography option Description

Minimum encryption settings S/MIME interoperability with external clients: Always use Rich Text formatting in S/MIME messages S/MIME password settings Message formats

Set to the minimum key length for an encrypted e-mail message. Specify the behavior for handling S/MIME messages. Always use Rich Text for S/MIME messages instead of the format specified by the user. Specify the default and maximum amount of time that an S/MIME password is valid. Choose message formats to support: S/MIME (default), Exchange, Fortezza, or a combination of formats.

94

Cryptography option

Description

Message when Outlook cannot find the digital ID to decode a message Do not provide Continue option on Encryption warning dialog boxes Run in FIPS compliant mode

Enter a message to display to users. Disable the Continue button on encryption settings warning dialog boxes. Put Outlook into FIPS 140-1 mode.

Do not check e-mail address against address of Do not verify user's e-mail address with address certificates being using (sic) of certificates used for encryption or signing. Encrypt all e-mail messages Sign all e-mail messages Send all signed messages as clear signed messages Request an S/MIME receipt for all S/MIME signed messages URL for S/MIME certificates Encrypt outgoing e-mail messages. Sign outgoing e-mail messages. Use Clear Signed for signed outgoing e-mail messages. Request a security-enhanced receipt for outgoing e-mail messages. Provide a URL at which users can obtain an S/MIME receipt. The URL can contain three variables (%1, %2, and %3), that will be replaced by the user's name, e-mail address, and language, respectively. Require all S/MIME-signed messages to have a security label. Disable the 'Publish to GAL' button on the Email Security page of the Trust Center. Specify an option for when signature warnings display to users. Specify an option for how S/MIME receipt requests are handled. Enter a list of policies allowed in the policies extension of a certificate showing that the certificate is a Fortezza certificate. List policies separated by semi-colons. Use only Suite-B algorithms for S/MIME operations. Display Outlook cryptography icons in the Outlook UI. Specify how Outlook behaves when CRL lists 95

Ensure all S/MIME signed messages have a label Do not display 'Publish to GAL' button Signature Warning S/MIME receipt requests Fortezza certificate policies

Require SUITEB algorithms for S/MIME operations Enable Cryptography Icons Retrieving CRLs (Certificate Revocation Lists)

Cryptography option

Description

are retrieved. Missing CRLs Missing root certificates Specify the Outlook response when a CRL is missing: display error or warning (default). Specify the Outlook response when a root certificate is missing: display error or warning (default). Specify the Outlook response for Level 2 errors: display error or warning (default). Specify a folder path for the Secure Temporary Files Folder. This overrides the default path and is not recommended.

Promote Level 2 errors as errors, not warnings Attachment Secure Temporary Folder

More information about setting Outlook cryptography options

The following sections provide additional information about configuration options for Outlook cryptography.

Outlook security policy settings

The following table lists the Windows registry settings you can configure for your custom installation. The Windows registry settings correspond to the Group Policy settings listed earlier. You add these value entries in the following subkey: HKEY_CURRENT_USER\Software\\Microsoft\Office\12.0\Outlook\Security
Value name

Value data (Data type)

Description

Corresponding UI option

AlwaysEncrypt

0, 1 Set to 1 to encrypt outgoing (DWORD) messages. Default is 0. 0, 1 Set to 1 to sign outgoing messages. (DWORD) Default is 0.

Encrypt contents check box (E-mail Security page). Add digital signature check box (E-mail Security page). Send clear text signed message check box (E-mail

AlwaysSign

ClearSign

0, 1 Set to 1 to use Clear Signed for (DWORD) outgoing messages. Default is 0.

96

Value name

Value data (Data type)

Description

Corresponding UI option

Security page).
RequestSecureReceipt

0, 1 Set to 1 to request security(DWORD) enhanced receipts for outgoing messages. Default is 0. 0, 1 Set to 1 to require a label on (DWORD) outgoing messages. (The registry setting does not specify which label.) Default is 0. ASN encoded BLOB (Binary) This value entry specifies whether a user-defined security label must exist on outgoing signed messages. The string can optionally include label, classification, and category. Default is no security label required.

Request S/MIME receipt check box (E-mail Security page). None

ForceSecurityLabel

ForceSecurityLabelX

None

SigStatusNoCRL

0, 1 Set to 0 to specify that a missing (DWORD) CRL during signature validation is a warning. Set to 1 to specify that a missing CRL is an error. Default is 0. 0, 1, 2 Set to 0 to specify that a No Trust (DWORD) decision is allowed. Set to 1 to specify that a No Trust decision is a warning. Set to 2 to specify that a No Trust decision is an error. Default is 0. 0, 1 Set to 0 to promote Error Level 2 (DWORD) errors as errors. Set to 1 to promote Error Level 2 errors as warnings. Default is 1. 0, 1 Set to 1 to disable the Publish to (DWORD) GALbutton. Default is 0. 0, 1 Set to 1 to put Outlook into FIPS (DWORD) 140-1 mode. Default is 0. 0, 1, 2 Set to 0 to display the Show and

None

SigStatusNoTrustDecision

None

PromoteErrorsAsWarnings

None

PublishtoGalDisabled

Publish to GAL button (E-mail Security page) None Secure E-mail 97

FIPSMode

WarnAboutInvalid

Value name

Value data (Data type)

Description

Corresponding UI option

(DWORD) Ask check box (Secure E-mail Problem pont dialog box). Set to 1 to always show the dialog box. Set to 2 to never show the dialog box. Default is 2.
DisableContinueEncryption

Problem pont dialog box.

0, 1 Set to 0 to show the Continue (DWORD) Encrypting button in the final Encryption Errors dialog box. Set to 1 to hide the button. Default is 0.

Continue Encrypting button on final Encryption Errors dialog box. This dialog box appears when a user tries to send a message to someone who cannot receive encrypted messages. This setting disables the button that allows users to send the message regardless. (The recipient cannot open encrypted mail messages sent by overriding the error.)

RespondtoReceiptRequest

0, 1, 2, 3 Set to 0 to always send a receipt None (DWORD) response and prompt for a password, if needed. Set to 1 to prompt for a password when sending a receipt response. Set to 2 to never send a receipt response. Set to 3 to enforce sending a receipt response. Default is 0. String Displays the specified string when the user tries unsuccessfully to open an encrypted message. Can provide information about where to Default string

NeedEncryptionString

98

Value name

Value data (Data type)

Description

Corresponding UI option

enroll in security. Default string is used, unless the value is set to another string.
Options

0, 1 Set to 0 to show a warning dialog (DWORD) box when a user attempts to read a signed message with an invalid signature. Set to 1 to never show the warning. Default is 0. 40, 64, Set to the minimum key length for 128, 168 an encrypted e-mail message. (DWORD) String

None

MinEncKey

None

RequiredCA

Set to the name of the required None certificate authority (CA). When a value is set, Outlook disallows users from signing e-mail by using a certificate from a different CA. URL for the default certificate authority (internal or external) from which you wish your users to obtain new digital IDs. Note: Set in HKEY_CURRENT_USER\Software\ Microsoft\Office\12.0\Outlook\Securi ty subkey if you do not have administrator rights on the user's computer. Get Digital ID button (E-mail Security page).

EnrollPageURL

String

When you specify a value for PromoteErrorsAsWarnings, potential Error Level 2 conditions include the following: Unknown Signature Algorithm No Signing Certification Found Bad Attribute Sets No Issuer Certificate Found No CRL Found Out of Date CRL Root Trust Problem Out of Date CTL 99

When you specify a value for EnrollPageURL, use the following parameters to send information about the user to the enrollment Web page.
Parameter Placeholder in URL string

User display name SMTP e-mail name User interface language ID

%1 %2 %3

For example, to send user information to the Microsoft enrollment Web page, set the EnrollPageURL entry to the following value, including the parameters: www.microsoft.com/ie/certpage.htm?name=%1&email=%2&helplcid=%3 For example, if the user's name is Jeff Smith, e-mail address is someone@example.com, and user interface language ID is 1033, the placeholders are resolved as follows: www.microsoft.com/ie/certpage.htm?name=Jeff %20Smith&email=someone@example.com&helplcid=1033

Security policy settings for general cryptography

The following table shows additional Windows registry settings that you can use for your custom configuration. These settings are contained in the following subkey: HKEY_CURRENT_USER\Software\Microsoft\Cryptography\SMIME\SecurityPolicies\Default
Value name

Value data (Data type)

Description

Corresponding UI option

ShowWithMultiLabels

0, 1, Set to 0 to attempt to display a (DWORD) message when the signature layer has different labels set in different signatures. Set to 1 to prevent display of message. Default is 0.

None

CertErrorWithLabel

0, 1, 2 Set to 0 to process a message with None (DWORD) a certificate error when the message has a label. Set to 1 to deny access to a message with a certificate error. Set to 2 to ignore the message label and grant access to the message. (The user still sees a certificate error.) Default is 0.

100

Security policy settings for KMS-issued certificates

The values in the following table only apply to certificates issued by Microsoft Exchange Key Management Service (KMS). The table shows additional Windows registry settings that you can use for your custom configuration. These settings are contained in the following subkey: HKEY_CURRENT_USER\Software\Microsoft\Cryptography\Defaults\Provider
Value name Value data (Data type) Description Corresponding UI option

MaxPWDTime

0, number Set to 0 to remove the user's ability (DWORD) to save a password (the user is required to enter a password each time a key set is required). Set to a positive number to specify a maximum password time in minutes. Default is 999. Number Set to the default value for the (DWORD) amount of time a password is saved.

None

DefPWDTime

None

101

Specify the method Outlook uses to manage virus prevention features

With Microsoft Office Outlook 2007, you can use new Group Policy settings to configure security options that help prevent viruses. With previous versions of Outlook, you modified security settings by using the Outlook security template and publishing the settings to a form in a top-level folder in Exchange Server public folders. Users who needed these settings required the HKEY_CURRENT_USER\Software\Policies\Microsoft\Security\CheckAdminSettings registry key to be set on their computers for the settings to apply. The CheckAdminSettings registry key is no longer used to determine users' security settings. Instead, you configure a new Group Policy setting: Outlook Security Mode. The option you choose in this setting determines which security settings are enforced in Outlook: Default security settings in the product Security settings in the Exchange Server security form Group Policy security settings

To configure the method that Outlook uses for security settings 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security Form settings\Microsoft Office Outlook 12.0 Security. 2. Double-click Outlook Security Mode, and click Enabled. 3. In the Outlook Security Policy drop-down list, select the method that you want Outlook to use for enforcing security settings. 4. Click OK. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To continue using the Exchange Server security form for Outlook security settings, you must configure the new Group Policy setting. If you do not configure the setting, Outlook uses default security settings. If you do not enable the Outlook Security Mode setting, default security settings in the product are enforced.

More information about managing virus prevention settings

More information about managing virus prevention settings is included in the following sections.

102

Migrating to Group Policy settings

If you previously used the Exchange Server security form to manage security settings and now choose to use Group Policy with Outlook, you must manually migrate the settings that you configured earlier to the corresponding Group Policy settings for Outlook.

Updated Object Model Guard

Users might receive a warning when an application accesses the Outlook Address Bookfor example, when users synchronize a hand-held device with Outlook on their desktop computer. This feature cannot be modified by using the Exchange Server security form or Group Policy. To prevent the access warning, the application must be coded to interact with Outlook in a trusted manner. The Object Model (OM) Guard that helps prevent viruses from using the Outlook Address Book to propagate themselves has been updated. Outlook now checks for up-to-date antivirus software to help determine when to display address book access warnings and other Outlook security warnings. For more information about coding trusted add-ins, see Important Security Notes for Microsoft Outlook COM Add-in Developers (http://go.microsoft.com/fwlink/?LinkId=74697).

103

Customize attachment settings in Outlook 2007

In Microsoft Office Outlook 2007, you can specify that attachments to Outlook items (such as email messages or appointments) are restricted based on the file type of the attachment. A file type can have either a Level 1 or Level 2 restriction. You can also configure what users can do with attachment restrictions. For example, you might allow users to change the restrictions for a group of attachment file types from Level 1 (user cannot view the file) to Level 2 (user can open the file after saving it to disk). Note: This topic is for Outlook administrators. To learn more about why some Outlook attachments are blocked, see Blocked attachments: The Outlook feature you love to hate (http://go.microsoft.com/fwlink/?LinkId=81268). Or learn how to share files with restricted file types by reading Blocked attachments in Outlook (http://go.microsoft.com/fwlink/? LinkId=81269). You can configure attachment settings by using Group Policy. In Group Policy, load the Outlook template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security\Security Form Settings\Attachment Security. These settings cannot be configured by using the Office Customization Tool. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. Note: To use Group Policy to configure these attachment settings, you must first configure the method that Outlook uses for security settings correctly. For more information about setting the Outlook security settings method, see Plan for configuring security settings in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179095.aspx). The following table describes the Group Policy options for attachments.
Item Description

Display Level 1 attachments

Enables users to access all attachments with Level 1 file types by first saving the attachments to disk, and then opening them (as with Level 2 attachments).

104

Item

Description

Allow users to demote attachments to Level 2

Enables users to create a list of attachment file types to demote from Level 1 to Level 2. The registry key in which users create the list of file types to demote is: HKCU\Software\Microsoft\Office\12.0\Outlook\Security\Level1Remove. In the registry key, users specify the file types (usually three letters) to remove from the Level 1 file list, separated with semicolons. Prevents users from receiving a warning when they send an item containing a Level 1 attachment. This option affects only the warning. Once the item is sent, the user cannot view or gain access to the attachment. If you want users to be able to post items to a public folder without receiving this prompt, you must select both this check box and the Do not prompt about Level 1 attachments when closing an item check box. Prevents users from receiving a warning when they close an e-mail message, appointment, or other item containing a Level 1 attachment. This option affects only the warning. Once the item is closed, the user cannot view or gain access to the attachment. If you want users to be able to post items to a public folder without receiving this prompt, you must select both this check box and the Do not prompt about Level 1 attachments when sending an item check box. Allows users to double-click an embedded object, such as a Microsoft Excel spreadsheet, and open it in the Outlook editor. Displays OLE objects that have been packaged. A package is an icon that represents an embedded or linked OLE object. When you doubleclick the package, the program used to create the object either plays the object (for example, if the object is a sound file) or opens and displays the object. Allowing Outlook to display OLE package objects can be problematic, because the icon can be easily changed and used to disguise malicious files.

Disable the prompt about Level 1 attachments when sending an item

Disable the prompt about Level 1 attachments when closing an item

Allow in-place activation of embedded OLE objects Display OLE package objects

Add or remove Level 1 file types

Level 1 files are hidden from the user. The user cannot open, save, or print a Level 1 attachment. (If you specify that users can demote a Level 1 attachment to a Level 2 attachment, Level 2 restrictions apply to the file.) The InfoBar at the top of the item displays a list of the blocked files. (The InfoBar does not appear on a custom form.) The default list of Level 1 file types is provided in Attachment file types that are restricted by Outlook in the See Also section, which is visible when you are connected to the Internet. 105

When you remove a file type from the Level 1 list, attachments with that file type are no longer blocked. The following table describes how to add or remove Level 1 file types from the default list. You can use Group Policy to configure these settings. In Group Policy, load the Outlook template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security\Security Form Settings\Attachment Security. These settings cannot be configured by using the Office Customization Tool. Note: To use Group Policy to configure these attachment settings, you must first configure the method that Outlook uses for security settings correctly. For more information about setting the Outlook security settings method, see Plan for configuring security settings in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179095.aspx).
Action Description

Add file types to block as Level 1

Specifies the file types (usually three letters) you want to add to the Level 1 file list. Do not enter a period before each file type. If you enter multiple file types, separate them with semicolons. Specifies the file types (usually three letters) you want to remove from the Level 1 file list. Do not enter a period before each file type. If you enter multiple file types, separate them with semicolons.

Remove file types blocked as Level 1

Add or remove Level 2 file types

With a Level 2 file, the user is required to save the file to the hard disk before the file is opened. A Level 2 file cannot be opened directly from an item. When you remove a file type from the Level 2 list, it becomes a regular file type that can be opened, saved, and printed in Outlook. There are no restrictions on the file. The following table describes how to add or remove Level 2 file types from the default list. You can use Group Policy to configure these settings. In Group Policy, load the Outlook template (Outlk12.adm) and go to User Configuration\Administrative Templates\ Microsoft Office Outlook 2007\Security\Security Form Settings\Attachment Security. These settings cannot be configured by using the Office Customization Tool. Note: To use Group Policy to configure these attachment settings, you must first configure the method that Outlook uses for security settings correctly. For more information about

106

setting the Outlook security settings method, see Plan for configuring security settings in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179095.aspx).
Action Description

Add file types to block as Level 2

Specifies the file types (usually three letters) you want to add to the Level 2 file list. Do not enter a period before each file type. If you enter multiple file types, separate them with semicolons. Specifies the file types (usually three letters) you want to remove from the Level 2 file list. Do not enter a period before each file type. If you enter multiple file types, separate them with semicolons.

Remove file types blocked as Level 2

Additional attachment security settings

Several Group Policy settings for attachment security in earlier versions of Outlook are available in Office Outlook 2007. In earlier versions of Outlook, most security settings were managed by using a form published to a Microsoft Exchange public folder, rather than by using Group Policy. In a few scenarios, you could configure Group Policy settings in addition to the settings enforced by the Exchange Server security form. Note: If you are using only Group Policy to manage Outlook security, these options are configured by using new Group Policy settings (described earlier in this topic). If you are using the Exchange Server security form, you might still want to configure these legacy settings. If you are using the Exchange Server security form to manage Outlook security, you can configure these legacy settings in combination with settings on the security form. The following table describes the way legacy Group Policy settings for attachment security interact. To configure these settings, load the Outlook template (Outlk12.adm) in Group Policy. Go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security. These settings cannot be configured by using the Office Customization Tool.
Action Description

Prevent users from customizing attachment security settings

When enabled, users cannot customize the list of file types that are allowed as attachments in Outlook, regardless of how you have configured other Outlook security settings. Specifies the file types (usually three letters) 107

Allow access to e-mail attachments

Action

Description

you want to remove from the Level 1 file list. Do not enter a period before each file type. If you enter multiple file types, separate them with semicolons. If you configure the Allow access to e-mail attachments Group Policy setting, the final list of restricted file types is based on other attachment security settings: If you use the Exchange Server security form to configure security settings, file types on the Level 1 list created by using the Exchange Server security form are still restricted. If you use Group Policy to configure security settings, the list of Level 1 file types you have specified by using the Group Policy setting Add file extensions to block as Level 1 are still restricted. If you use default security settings, all files types listed in this Group Policy setting are no longer restricted.

108

Customize programmatic settings in Outlook 2007

As an administrator of Microsoft Office Outlook 2007, you can configure programmatic security settings to manage restrictions for the following technologies: the Outlook object model, Collaboration Data Object (CDO), and Simple MAPI. These technologies are defined as follows: Outlook object modelThe Outlook object model allows you to programmatically manipulate data stored in Outlook folders. CDOCollaboration Data Object (CDO) libraries are used to implement messaging and collaboration functionality in a custom application. CDO is a COM wrapper of the MAPI library and can be called from any development language that supports Automation. CDO implements most but not all MAPI functionality, but more than Simple MAPI. Simple MAPISimple MAPI enables developers to add basic messaging functionality, such as sending and receiving messages, to their Microsoft Windows-based applications. It is a subset of MAPI, which provides complete access to messaging and information exchange systems. You can use Group Policy to configure programmatic security settings. In Group Policy, load the Outlook template (Outlk12.adm). The attachment options settings are located under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security\Security Form Settings\Programmatic Security. These settings cannot be configured by using the Office Customization Tool. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. Note: To use Group Policy to configure programmatic security settings, you must first configure the method that Outlook uses for security settings correctly. For more information about setting the Outlook security settings method, see Plan for configuring security settings in Outlook 2007 (http://technet.microsoft.com/en-us/library/cc179095.aspx). The following table describes the Group Policy options for programmatic settings. You can choose one of the following settings for each item: Prompt userUsers receive a message allowing them to choose whether to allow or deny the operation. For some prompts, users can choose to allow or deny the operation without prompts for up to 10 minutes. Automatically approveThe operation is allowed and the user does not receive a prompt. Automatically denyThe operation is not allowed and the user does not receive a prompt. 109

Item

Description

Configure Outlook object model prompt when sending mail Configure Simple MAPI sending prompt

Specifies what happens when a program attempts to send mail programmatically by using the Outlook object model. Specifies what happens when a program attempts to send mail programmatically by using Simple MAPI. Specifies what happens when a program attempts to gain access to an address book by using the Outlook object model.

Configure Outlook object model prompt when accessing an address book

Configure Simple MAPI name resolution prompt Specifies what happens when a program attempts to gain access to an address book by using Simple MAPI. Configure Outlook object model prompt when reading address information Configure Simple MAPI message opening prompt Configure Outlook object model prompt when responding to meeting and task requests Specifies what happens when a program attempts to gain access to a recipient field, such as To, by using the Outlook object model. Specifies what happens when a program attempts to gain access to a recipient field, such as To, by using Simple MAPI. Specifies what happens when a program attempts to send mail programmatically by using the Respond method on task requests and meeting requests. This method is similar to the Send method on mail messages. Specifies what happens when a program attempts to programmatically use the Save As command on the File menu to save an item. Once an item has been saved, a malicious program could search the file for e-mail addresses. Specifies what happens when a user adds a Combination or Formula custom field to a custom form and binds it to an Address Information field. By doing this, code can be used to indirectly retrieve the value of the Address Information field by getting the Value property of the field.

Configure Outlook object model prompt when executing Save As

Configure Outlook object model prompt when accessing the Formula property of a UserProperty object

110

Item

Description

Configure Outlook object model prompt when accessing address information via UserProperties.Find

Specifies what happens when a program attempts to search mail folders for address information by using the Outlook object model.

111

Customize ActiveX and custom forms security settings in Outlook 2007

You can specify ActiveX and custom forms security settings for Microsoft Office Outlook 2007 users. Custom forms security settings include options for changing how Office Outlook 2007 restricts scripts, custom controls, and custom actions.

Customizing how ActiveX controls behave in oneoff forms

When Outlook receives a message that contains a form definition, the item is a one-off form. To help prevent unwanted script and controls from running in one-off forms, Outlook does not load ActiveX controls in one-off forms by default. You can lock down the settings to customize ActiveX controls by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To customize ActiveX options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how results are displayed, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security, double-click Allow Active X One Off Forms. 3. Click Enabled. 4. Choose an option from the Sets which ActiveX controls to allow drop-down list. 5. Click OK. Choose one of the options in the following table.
Option Description

Allows all ActiveX Controls Allows only Safe Controls

Allows all ActiveX controls to run without restrictions. Allows only safe ActiveX controls to run. An ActiveX control is safe if it is signed with Authenticode and the signer is listed in the Trusted Publishers List.

112

Option

Description

Load only Outlook Controls

Outlook loads only the following controls. These are the only controls that can be used in one-off forms. Controls from fm20.dll Microsoft Office Outlook Rich Format Control Microsoft Office Outlook Recipient Control Microsoft Office Outlook View Control

If you do not configure any of these options, the default is to load only Outlook controls.

Customizing custom forms security settings

You can lock down the settings to configure security for custom forms by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. To customize customs form security options by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. To customize how results are displayed, under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security\Security Form Settings\Custom Form Security, double-click the setting you want to set. For example, double-click Allow scripts in one-off Outlook forms. 3. Click Enabled. If appropriate, choose option from the drop-down list in the setting. 4. Click OK. Note: To use Group Policy to configure Custom Form Security, you must first configure the method that Outlook uses for security settings correctly. See the following topic for more information about setting this option: Specify the method Outlook uses to manage virus prevention features. The settings you can configure for scripts, custom controls, and custom actions are shown below:
Option Description

Allow scripts in one-off Outlook forms

Run scripts in forms where the script and the layout are contained in the message. If users receive a oneoff form that contains script, users are prompted to ask if they want to run the script. 113

Option

Description

Set Outlook object model Custom Actions execution prompt

Specifies what occurs when a program attempts to run a custom action using the Outlook object model. A custom action can be created to reply to a message and circumvent the programmatic send protections just described. Select one of the following: Prompt user enables the user to receive a message and decide whether to allow programmatic send access. Automatically approve always allows programmatic send access without displaying a message. Automatically deny always denies programmatic send access without displaying a message. Specifies what occurs when a user adds a control to a custom Outlook form and binds that control directly to any of the Address Information fields. This way, code can be used to indirectly retrieve the value of the Address Information field by getting the Value property of the control. Select one of the following: Prompt user enables the user to receive a message and decide whether to allow access to Address Information fields. Automatically approve always allows access to Address Information fields without displaying a message. Automatically deny always denies access to Address Information fields without displaying a message.

Set control ItemProperty prompt

114

Manage trusted add-ins for Outlook 2007

If you use default Microsoft Office Outlook 2007 security settings, all Component Object Model (COM) add-ins installed in Office Outlook 2007 are trusted by default. If you customize security settings by using Group Policy, you can specify COM add-ins that are trusted and that can run without encountering the Outlook object model blocks. To trust a COM add-in, you include the file name for the add-in in a Group Policy setting with a calculated hash value for the file. Before you can specify an add-in as trusted by Outlook, you must install a program to calculate the hash value. To compute the hash value for a trusted add-in 1. Download the hash calculation program - the Outlook 2007 Security Hash Generator Tool - from the Microsoft Office Download Center (http://go.microsoft.com/fwlink/?LinkId=75742). 2. Extract the contents to a local folder (such as C:\hashtool). 3. Run the command prompt for your computer: Click Start, All Programs, Accessories, Command Prompt. Note: On Windows Vista requires an additional step. Right-click Command Prompt, then select Run as administrator. 4. Change directories to the folder where you extracted the hash tool files. 5. Type: createhash.bat /register and press Enter. (This step needs to be completed only once.) 6. Type: createhash.bat filename where filename is the full path and file name of the add-in file you are creating the hash number for. Note that the CreateHash.bat tool will not work if the path to the DLL you are using contains spaces. Copy the DLL to a location (for example, C:\Temp\MyDLL.dll), and use this path to generate the hash number. 7. Press Enter. 8. Copy and save the value that is displayed on the screen to the clipboard. This is the value that you will add to the Group Policy setting (see the following procedure). Specify the add-in as trusted by entering in Group Policy the value generated by the program, paired with the add-in file name. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center.

115

To specify the trusted add-in in Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Security\Security Form Settings\Programmatic Security\Trusted Add-ins. 2. Double-click Configure trusted add-ins, and click Enabled. 3. Click Show. 4. In the Show contents dialog box, click Add. 5. In the Add item dialog box, in the Enter the name of the item to be added field, type the file name of the COM add-in. 6. In the Enter the value to be added field, paste the hash value of the COM add-in that you saved when you ran the hash value calculation program. 7. Click OK three times. The COM add-in can now run without prompts for Office Outlook 2007 users who use this security setting. To remove a file from the list of trusted add-ins, update the Group Policy setting by deleting the entry for the add-in.

Working with Outlook COM add-ins

A COM add-in should be coded so that it takes advantage of the Outlook trust model in order to run without warning messages in Outlook. Users might continue to see warnings when they access Outlook features that use the add-in, such as when they synchronize a hand-held device with Outlook on their desktop computer. However, users are less likely to see warnings in Office Outlook 2007 than in previous versions of Outlook. The Object Model (OM) Guard that helps prevent viruses from using the Outlook Address Book to propagate themselves is updated in Office Outlook 2007. Outlook checks for upto-date antivirus software to help determine when to display address book access warnings and other Outlook security warnings. If the user continues to see security prompts after the add-in is included in the list of trusted addins, you must work with the COM add-in developer to resolve the problem. For more information about coding trusted add-ins, see Important Security Notes for Microsoft Outlook COM Add-in Developers (http://go.microsoft.com/fwlink/?LinkId=74697). If you enforce customized Outlook security settings with the Microsoft Exchange Server security form published in an Exchange Server public folder, you can learn how to trust COM add-ins. Scroll down to the Trusted Code tab section in the Microsoft Office 2003 Resource Kit topic, Outlook Security Template Settings (http://go.microsoft.com/fwlink/?LinkId=75744). Note: To use Group Policy instead of the Exchange security form to configure trusted add-ins, you must first configure the method that Outlook uses for security settings correctly. For more information about setting the Outlook security settings method, see Specify the method Outlook uses to manage virus prevention features. 116

Configure security for Outlook 2007 folder home pages

In Microsoft Office Outlook 2007, you can view Web pages without leaving Outlook. You do this by assigning a Web page as a home page for a folder. You can associate a Web page with any personal or public folder. When you click the folder, Outlook displays the folder home page assigned to it. Although this feature provides the opportunity to create powerful public folder applications, scripts can be included on the Web page that access the Outlook object model. This exposes users to security risks. You can improve security by using Group Policy to disable folder home pages for all of your users. You can lock down this setting (recommended) by using the Outlook Group Policy template (Outlk12.adm). Or you can configure a default setting by using the Office Customization Tool (OCT), in which case users can change the setting. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To disable folder home pages by using Group Policy 1. In Group Policy, load the Microsoft Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Folder Home Pages for Outlook Special Folders\Settings for Disable Folder Home Pages, double-click Do not allow Home Page URL to be set in folder Properties. 3. Click Enabled. 4. Click OK.

More information about Outlook folder home pages

These folder home pages do not follow the Outlook security model. They can run scripts, just as any other Web page can. Access to the Outlook object model allows scripts to manipulate all of the users Outlook information on the computer. From a security perspective, this means that anyone who can create a public folder and set that folder with a home page can include scripts that can manipulate data in users mailboxes when the users go to that public folder. Because of this, be cautious about granting permissions for users to set public folders as home pages.

117

Configure junk e-mail settings in Outlook 2007

Microsoft Office Outlook 2007 provides features that can help users avoid receiving and reading junk e-mail messages, including the Junk E-mail Filter and the disabling of automatic content download from external servers. You can configure settings to deploy these features to meet the needs of your organization. For example, you can configure the Junk E-mail Filter to be more aggressive, though in that case it might catch more legitimate messages as well. Rules that are not part of the junk e-mail management built into the software are not affected. Note: This topic is for Outlook administrators. To learn more about configuring junk e-mail settings in Outlook on your desktop, see Change the level of protection in the Junk E-Mail Filter (http://go.microsoft.com/fwlink/?LinkId=81273).

Configuring the Junk E-mail Filter

You can lock down the settings to customize Junk E-mail Filter options by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. Note: If you decide to configure Junk E-mail Filter settings in the OCT, see the procedure To ensure default Junk E-mail settings are applied using the OCT later in this topic for an additional setting that must be configured. Use the following procedure to configure Junk E-mail Filter options in Outlook. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. To configure Outlook Junk E-mail Filter settings in Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Preferences\Junk E-mail. 2. Double-click the option that you want to configure. For example, double-click Junk Email protection level. 3. Click Enabled. 4. If appropriate, select a radio button for the option you want to set, or choose an 118

option from a drop-down list. 5. Click OK. You can configure the following settings for the Outlook Junk E-mail filter.
Junk E-mail filter option Description

Hide Junk Mail UI Junk E-mail protection level

Disable junk e-mail filtering and hide related settings in Outlook. Select the level of junk e-mail protection for users: No Protection, Low, High, Trusted Lists Only. Permanently delete suspected junk e-mail instead of moving it to the Junk E-mail folder. Trust e-mail addresses included in users' Contacts folders. Automatically add all e-mail recipients to users' Safe Senders Lists. Change default from overwrite Junk Mail Import list to append to the list. Specify a text file containing a list of e-mail addresses to append to or overwrite the Safe Senders list. Specify a text file containing a list of e-mail addresses to append to or overwrite the Safe Recipients list. Specify a text file containing a list of e-mail addresses to append to or overwrite the Blocked Senders list.

Permanently delete Junk E-mail Trust E-mail from Contacts Add e-mail recipients to users' Safe Senders Lists Overwrite or Append Junk Mail Import List Specify path to Safe Senders list

Specify path to Safe Recipients list

Specify path to Blocked Senders list

If you configure default values by using the OCT (rather than using Group Policy to lock down settings), a specific Junk E-mail setting must be configured so the new defaults can be applied. To ensure default Junk E-mail settings are applied using the OCT 1. In the OCT, on the Modify user settings page, under Microsoft Office Outlook 2007\Tools | Options\Preferences\Junk E-mail, double-click Junk Mail Import list. 2. Click Enabled. 3. Click OK.

119

Configuring automatic picture download

To help protect users' privacy and to combat Web beaconsfunctionality embedded within items to detect when recipients have viewed an itemOffice Outlook 2007 is configured by default to not automatically download pictures or other content from external servers on the Internet. You can lock down the settings to customize automatic picture download by using the Outlook Group Policy template (Outlk12.adm). Or you can configure default settings by using the OCT, in which case users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. To configure options for automatic picture download behavior in Outlook 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm). 2. Under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Security, click Automatic Picture Download Settings. 3. Double-click the option that you want to configure. For example, double-click Do not permit download of content from safe zones. 4. Click Enabled. 5. If appropriate, select a radio button for the option you want to set, or choose an option from a drop-down list. 6. Click OK. You can configure the following settings for automatic picture download.
Automatic picture download option Description

Display pictures and external content in HTML e-mail Automatically download content for e-mail from people in Safe Senders and Safe Recipients lists Do not permit download of content from safe zones Block Trusted Zones Include Internet in Safe Zones for Automatic Picture Download Include Intranet in Safe Zones for Automatic Picture Download

Enable this option to automatically display external content in HTML mail. Enable this option to automatically download content when e-mail message is from someone in the user's Safe Senders list or to someone in the user's Safe Recipients list. Disable this option to automatically download content for sites in Safe Zones (as defined by Trusted Zones, Internet, and Intranet settings). Disable this option to include Trusted Zones in the Safe Zones for Automatic Picture Download. Automatically download pictures for all Internet e-mail. Automatically download pictures for all Intranet e-mail

120

More about automatic picture download

Messages in HTML format often include pictures or sounds. Sometimes these pictures or sounds are not included in the message, but are instead downloaded from a Web server when the e-mail message is opened or previewed. This is typically done by legitimate senders to avoid sending extra-large messages. However, junk e-mail senders can use a link to content on external servers to include a Web beacon in e-mail messages, which notifies the Web server when users read or preview the message. The Web beacon notification validates the user's e-mail address to the junk e-mail sender, which can result in more junk e-mail being sent to the user. This feature to not automatically download pictures or other content can also help users to avoid viewing potentially offensive material (for external content linked to the message) and, if they are on a low bandwidth connection, to decide whether an image warrants the time and bandwidth to download it. Users can view the blocked pictures or content in a message by clicking the InfoBar under the message header or by right-clicking the blocked image. By default, Outlook does not download pictures or other content automatically, except when the external content comes from a Web site in the Trusted Sites zone or from an address or domain specified in the Safe Senders List. You can change this behavior so that content from any of the zones (Trusted Sites, Local Intranet, and Internet) will be downloaded automatically or blocked automatically.

See Also Plan for limiting junk e-mail in Outlook 2007 (http://technet.microsoft.com/enus/library/cc178957.aspx) Create and deploy Junk E-mail Filter lists in Outlook 2007

121

Configure Information Rights Management in Outlook 2007

In Microsoft Office Outlook 2007, users can create and send e-mail messages with restricted permission to help prevent messages from being forwarded, printed, or copied and pasted. 2007 Microsoft Office system documents, workbooks, and presentations that are attached to messages with restricted permission are also automatically restricted. Note: This topic is for Outlook administrators. To learn about using IRM to apply permissions to e-mail messages, see Restrict permission to confidential information in e-mail messages (http://go.microsoft.com/fwlink/?LinkId=85929) on Office Online. As an Outlook administrator, you can configure several options for IRM e-mail, such as disabling IRM or configuring local license caching. You can also design custom IRM permissions for users, in addition to the default Do Not Forward permissions group. For more information, see Provide custom Information Rights Management rights policy templates in Office 2007 (http://technet.microsoft.com/en-us/library/cc179227.aspx). The following IRM settings and features can be useful when you configure rights-managed e-mail messaging: Disable IRM in the 2007 Microsoft Office system. Configure automatic license caching for IRM. Help enforce an e-mail message expiration period. Do not use Outlook for validating e-mail addresses for IRM permissions.

You can lock down most settings to customize IRM for Outlook by using the Outlook Group Policy template (Outlk12.adm) or the Office Group Policy template (Office12.adm). Alternatively, you can configure default settings for most options by using the Office Customization Tool (OCT), which enables users to change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. Learn more about using the OCT by visiting Customize the 2007 Office system.

122

Disable IRM
To disable IRM in Office Outlook 2007, you must disable IRM for all Office applications. There is no separate option to disable IRM only in Outlook. To disable IRM in Office 2007 by using Group Policy 1. In Group Policy, load the 2007 Office system template (Office12.adm) and go to User Configuration\Administrative Templates\Microsoft Office 2007 system\Manage Restricted Permissions. 2. Double-click Disable Information Rights Management User Interface. 3. Click Enabled. 4. Click OK.

Configure automatic license caching

A second option that you can configure for Outlook is to automatically download the IRM license for rights-managed e-mail when Outlook synchronizes with Exchange server. To configure automatic license caching for IRM by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Miscellaneous. 2. Double-click Do not download permissions for e-mail during offline Exchange folder sync. 3. Click Enabled. 4. Click OK.

Enforce e-mail expiration

You can also use IRM to help enforce an e-mail expiration period that you configure for Outlook. When a user specifies the number of days before a message expires with IRM enabled, the message cannot be accessed after the expiration period. As an administrator, you can specify an expiration period for all Outlook e-mail messages in your organization. The expiration period is enforced only when users send rights-managed e-mail. To configure an expiration period for e-mail messages by using Group Policy 1. In Group Policy, load the Office Outlook 2007 template (Outlk12.adm) and go to User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Preferences\E-mail options\Advanced E-mail options. 2. Double-click When sending a message. 3. Click Enabled. 4. In the box that follows Messages expire after (days), enter a number of days. 5. Click OK. 123

Do not use Outlook for e-mail address validation

The permissions dialog uses Outlook to validate e-mail addresses that are entered in that dialog. This causes an instance of Outlook to start when permissions are restricted. You can disable this option by using the registry key that is listed in the following table. There is no corresponding Group Policy or OCT setting for this option. The following IRM registry setting is located in HKCU\Software\Microsoft\Office\12.0\Common\DRM. Group Policy settings are located in User Configuration\Microsoft Office 2007 system\Manage Restricted Permissions.
Name of Registry Entry Registry Entry Type Values for Registry Entry Description

DoNotUseOutlookByDefault

DWORD

0 = Outlook is used 1 = Outlook is not used

Disable the option by using this key.

See Also Planning for Information Rights Management (http://technet.microsoft.com/enus/library/cc179103.aspx) Configure Information Rights Management

124

Configure Information Rights Management

Users can restrict permission to content documents and e-mail messages in the 2007 Microsoft Office system by using Information Rights Management (IRM). You can configure IRM options in your organization to encrypt document properties for IRM content, specify the down-level text that appears when users without IRM-enabled software receive content with IRM permissions, and so on. Note: This topic is for Office administrators. To learn about using IRM to apply permissions to Office documents or e-mail messages, see Information Rights Management (http://go.microsoft.com/fwlink/?LinkId=85929) on Office Online.

Configuring IRM Group Policy settings

You can lock down many settings to customize IRM by using the Office Group Policy template (Office12.adm). You can also use the Office Customization Tool (OCT) to configure default settings, which enables users to change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT. In addition, there are IRM configuration options that can only be configured by using registry key settings. For a list of all IRM registry keys, see Configuring IRM registry key options. The Outlook template and other ADM files can be downloaded from 2007 Office System Administrative Templates (ADM) (http://go.microsoft.com/fwlink/?LinkId=78161) on the Microsoft Download Center. Learn more about using the OCT by visiting Customize the 2007 Office system. To configure IRM options in Group Policy 1. In Group Policy, load the 2007 Office system template (Office12.adm) and go to User Configuration\Administrative Templates\Microsoft Office 2007 system\Manage Restricted Permissions. 2. Double-click the option that you want to configure. For example, to prevent users from applying IRM permissions in all Office applications, double-click Disable Information Rights Management User Interface. 3. Click Enabled. 4. Click OK.

125

The settings you can configure for IRM in Group Policy and by using the OCT are listed in the following table.
IRM option Description

Prevent users from changing permission on rights managed content

Users can consume content that already includes IRM permissions, but cannot apply IRM permissions to new content nor edit the rights on a document. Specify the text of the wrapper e-mail message sent with rights-managed e-mail. Provide the path to a folder with document, spreadsheet, and presentation files to be used as templates for an unencrypted wrapper for files with rights-managed content received by users with previous versions of Office. Disable all Rights Management-related options within the user interface of all Office applications. Specify the location where a user can obtain more information about getting access to IRM content. Enable users without the Microsoft Office 2007 system to view rights-managed content by using the Rights Management Add-in for Windows Internet Explorer. Users opening a rights-managed Office document must connect to the Internet or local area network to confirm by Passport or RMS that they have a valid IRM license. Group name is automatically expanded to display all the members of the group when users apply permissions to a document by selecting a group name in the Permissions dialog box. Return an error when users select a group in the Permission dialog box: ''You cannot publish content to Distribution Lists. You may only specify e-mail addresses for individual users.'' Specify the timeout value for querying an Active

Message displayed to users who cannot view a rights-managed e-mail URL for location of document templates displayed when applications do not recognize rights-managed documents

Disable Information Rights Management User Interface Additional permissions request URL

Allow users with earlier versions of Office to read with browsers

Always required users to connect

Always expand groups in Office when restriction permission for documents

Never allow users to specify groups when restricting permission for documents

Active Directory timeout for querying one entry 126

IRM option

Description

for group expansion Disable Microsoft Passport service for content with restricted permission Specify Permission Policy Path Do not allow users to upgrade Information Rights Management configuration

Directory entry when expanding a group. Users cannot open content created by a Passport authenticated account. Display in the Permission dialog box permission policy templates found in the folder specified. Do not allow users to run repair to change their Information Rights Management configuration.

You can also configure several IRM settings for Office Outlook 2007. For more information about configuring IRM for Outlook, see Configure Information Rights Management in Outlook 2007.

Configuring IRM registry key options

IRM settings can be configured by Group Policy, by registry key, or both. The following tables list the IRM registry key settings in 2007 Office system and the corresponding Group Policy settings, when the setting can be locked down by using Group Policy. The following IRM registry settings are located in HKCU\Software\Microsoft\Office\12.0\Common\DRM. Group Policy settings are in User Configuration\Microsoft Office 2007 system\Manage Restricted Permissions.
Name of Reg Entry Reg Entry Type Values for Reg Entry Group Policy setting or description

Disable

DWORD

0 = No functionality impacted by this registry key 1 = All IRM functionality is removed; IRM is disabled

Disable Information Rights Management User Interface

Disable Creation

DWORD

1 (or non-zero) = An Enterprise Install behaves just like a Standard install. Users cannot create IRM content or edit the rights on a doc, but they can consume previously created content. 0 = IRM content creation is allowed when included in the product SKU

Prevent users from changing permissions on rights managed content

Include HTML Downlevel Text

DWORD

1 = Include HTML stream 0 = Do not include HTML stream

Allow Users With Earlier Version of Office to Read With Browsers Message displayed to users who cannot view a 127

String

The text that appears in the wrapper email. The default text is: If you are not

Name of Reg Entry

Reg Entry Type

Values for Reg Entry

Group Policy setting or description

running an e-mail application that rights-managed e-mail supports messages with restricted permission, such as Microsoft Office Outlook 2003 or 2007, you can view this message by downloading the Rights Management Add-on for Microsoft Internet Explorer from http://r.office.microsoft.com/r/rlidRestrict edPermissionViewer?clid=1033. The CLID in the hyperlink is localized to the default language of the sender. Downlevel Template Path String The path to a directory that stores templates. Templates are Office document templates. URL for location of document templates displayed when applications do not recognize rights-managed documents No corresponding Group Policy setting. Typically the AD is used to specify the RMS server. This setting allows you to override the location of the Windows RMS specified in Active Directory for certification. Specify Permission Policy Path

Corp Certification Server

String

URL to corporate certification server

Admin Template Path

String

The path to the RMS templates. All templates should be stored in the same directory. Path can include environment variables: for example, %userprofile %\application data. 0 = No functionality impacted by this reg key 1 = Disable passport

Disable Passport Certification Request Permission URL Require Connection 128

DWORD

Disable Microsoft Passport service for content with restricted permission Additional Permissions Request URL Always require users to connect to verify

String

The URL of the person who can grant additional permissions. For example: mailto:someone@contoso.com. 1 = The box is checked by default and a connection is required.

DWORD

Name of Reg Entry

Reg Entry Type

Values for Reg Entry

Group Policy setting or description

0 = The box is cleared; users do not need a connection. Request Permission DWORD 1 = The box is checked. 0 = The box is cleared.

permissions No corresponding Group Policy setting. This registry key toggles the default value of the "Users can request additional permissions from" check box. No corresponding Group Policy setting. When Outlook downloads an IRM e-mail message, the license to view IRM content is automatically acquired. Never allow users to specify groups when restricting permission for documents

DoNot AcquireDR M License OnSync

DWORD

1 = Outlook will not try to acquire licenses during the message synchronization. 0 = The license is automatically acquired.

NeverAllow DLs

DWORD

0 = Allow distribution lists. 1 = Disable distribution lists.

Cloud Certification Server Cloud License Server DRMPost SetupURL

String

URL to custom cloud certification server No corresponding Group Policy setting. URL of the licensing server No corresponding Group Policy setting. URL where users can download the Windows Rights Management Services client. No corresponding Group Policy setting. The permissions dialog uses Outlook to validate e-mail addresses entered in that dialog. This causes an instance of Outlook to be started when restricting permissions. Disable the option by using this key. 129

String

String

URL of RMS client

DoNotUse OutlookBy Default

DWORD

0 = Outlook is used 1 = Outlook is not used

Name of Reg Entry

Reg Entry Type

Values for Reg Entry

Group Policy setting or description

Disable Repair

DWORD

0 = Repair works normally. 1 = Repair is disabled.

Do not allow users to upgrade Information Rights Management configuration

The following IRM registry setting is located in HKCU\Software\Microsoft\Office\12.0\Common\DRM\AutoExpandDLs. The corresponding Group Policy setting is in User Configuration\Microsoft Office 2007 system\Manage Restricted Permissions.
Name of Reg Entry Reg Entry Type Values for Reg Entry Group Policy setting

AutoExpandDLsEnable

DWORD

0 = Do not expand distribution lists in Permissions dialog 1 = Expand distribution lists in Permissions dialog

Always expand groups in Office when restricting permissions for documents

The following IRM registry setting is located in HKCU\Software\Microsoft\Office\12.0\Common\DRM\LicenseServers. There is no corresponding Group Policy setting.
Name of Reg Entry Reg Entry Type Values for Reg Entry Description

LicenseServers

Key/Hive. Contains DWORD values that have the name of a license server.

Set to the server URL. If the value of the DWORD is 1, then Office will not prompt to acquire a license (it will just get it). If the value is zero or there is no registry entry for that server, Office prompts for a license.

Example: If http://foo/_wmcs/licensing = 1 is a value for this setting, then a user attempting to acquire a license from that server to open a rights-managed document would not be prompted for a license.

130

The following IRM registry setting is located in HKCU\Software\Microsoft\Office\12.0\Common\Security. There is no corresponding Group Policy setting.
Name of Reg Entry Reg Entry Type Values for Reg Entry Description

DRMEncryptProperty

DWORD

1 = The file metadata is encrypted. 0 = The metadata is stored in clear text. The default value is 0.

Specify whether to encrypt all metadata stored inside a rightsmanaged file.

For 2007 Office system Office Open XML file formats (for example, docx, xlsx, pptx, and so on), users can decide to encrypt the Office metadata stored inside a rights-managed file. Users can encrypt all Office metadata, including hyperlink references, or leave content unencrypted so other applications can access the data. Users can opt to encrypt the metadata by setting a registry key. You can set a default option for users by deploying the registry setting. There is no option for encrypting some of the metadata: all metadata is encrypted or none is encrypted. In addition, this registry setting does not determine whether non-Office client metadata storage such as the storage SharePoint createsis encrypted. This encryption choice does not apply to Microsoft Office 2003 or other previous file formats. 2007 Office system handles earlier formats in the same way as Microsoft Office 2003. See Also Planning for Information Rights Management (http://technet.microsoft.com/enus/library/cc179103.aspx) Provide custom Information Rights Management rights policy templates in Office 2007 system (http://technet.microsoft.com/en-us/library/cc179227.aspx)

131

II Installing on client computers

132

Run Setup for the 2007 Office system on users' computers

After you have created a network installation point for the 2007 Microsoft Office system, install Office on a user's computer by running the Setup program. Setup handles all the installation functions for Office, including applying any customizations you have specified. Note: For information about how to create a network installation point, see Create a network installation point for the 2007 Office system. To install an Office product 1. If you have a Setup customization file that you created with the Office Customization Tool (OCT), copy the file to the Updates folder located in the root of the network installation point. 2. If you have any customizations to make to the Config.xml file, edit the copy of Config.xml located in the product folder in the network installation point. For example, the product folder for Microsoft Office Enterprise 2007 is Enterprise.WW. 3. Run Setup.exe from the root of the network installation point. Setup installs the product that resides in the network installation point, applying the customizations you entered in Config.xml and in the Setup customization file. Note: If you have multiple Office products on the network installation point, Setup prompts you to select which product you want to install. You can also identify the product to install by using the /config command-line option to specify the Config.xml file that resides in the core product folder for that product. For example, to install Office Enterprise 2007, run Setup.exe /config \\server\share\Enterprise.WW\Config.xml. Setup installs the product associated with the Config.xml you specify without prompting you to select the product. For information about how to configure Setup to install more than one Office product during a single installation, see Sequentially install multiple products of the 2007 Office system. See Also Create a network installation point for the 2007 Office system Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx)

133

Deploy the 2007 Office system to users who are not administrators
In the Microsoft Windows environments that support the 2007 Microsoft Office system, default users have limited access to system areas of the computer. Because the Office Setup program writes to system areas of the operating system and the Windows registry, a user must have administrative rights on the local computer to install Office. To install Office on computers where users lack administrative rights, you must run Setup in a context that provides it with administrative rights. After Office is installed, users without administrative rights can run all installed features, including installing features on demand. In organizations where users are not the administrators of their computers, administrators can use the following methods of providing Office Setup with the appropriate rights: Log on to the computer as an administrator and install Office 2007. Assign Office 2007 to the computer by using Group Policy Software Installation. Deploy Office 2007 to computers by using Group Policy computer startup scripts.

Use a software management tool, such as Microsoft Systems Management Server or Microsoft System Center Essentials 2007. After the initial installation is performed with administrative rights, all subsequent installations including install on demand and automatic repair of featuresalso run with those rights. Caution: Two general Windows policy settings that have been used to help install previous versions of Office are no longer supported in the 2007 Office system. Setting the Windows Installer policy Always install with elevated privileges allows a user without administrative rights to the computer to install any Windows Installer package. Similarly, setting the policy Enable user to use media source while elevated allows users without administrative rights to install programs from a CD. In both cases, the installation runs with elevated privileges, and the user has unlimited access to system files and the registry. Setting either of these policies leaves the computer highly vulnerable, potentially allowing an attacker to run malicious code on the computer. Using these policies to allow a user who is not an administrator to install Office will not work with the 2007 version of Setup and is not supported in the 2007 Office system.

Logging on as an administrator
You can install the 2007 Office system on a user's computer by logging on to the computer with an administrator account. This provides the administrative rights necessary for Setup to access restricted areas of the user's computer. Once Office is installed, users have no further need for administrative rights to run Office applications.

134

Note: For security reasons, applying a software update (MSP file) to an Office installation always requires administrative rights, even if the original installation was performed with administrative rights. For more information, see Distribute product updates for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc178995.aspx).

Assigning Office to the computer

If you have deployed Active Directory, then you can use Group Policy Software Installation features to assign the 2007 Office system to computers in your organization. The installation is performed with the appropriate administrator rights, and Office is available to all users on that computer. Only the administrator can remove Office in this case. Important: Although Group Policy can be used to install software applications in small-sized organizations with Active Directory installed, there are some limitations, and you must determine whether it is an appropriate solution for your deployment requirements. For more information, see the "Deployment considerations" section of Use Group Policy Software Installation to deploy the 2007 Office system.

Deploying Office with Group Policy computer startup scripts

Administrators can use Group Policy to assign computer startup scripts to deploy the 2007 Microsoft Office system. Scripts can be written in any language that is supported by the client computer. Windows Script Host-supported languages, such as VBScript and Jscript, and command files are the most common. For more information, see Use Group Policy to assign computer startup scripts for 2007 Office deployment.

Using a software management tool

A software management tool, such as Microsoft Systems Management Server, is able to run Office Setup in an administrative context on the user's computer. For more information, see Using Systems Management Server 2003 to deploy the 2007 Office system. Administrators can also use Microsoft System Center Essentials 2007 to deploy the 2007 Office system. System Center Essentials 2007 is a management solution designed for IT system administrators in medium-sized organizations that include up to 30 servers and 500 client computers. For more information, see Deploy the 2007 Office system by using System Center Essentials 2007. See Also Using Systems Management Server 2003 to deploy the 2007 Office system Deploy the 2007 Office system by using System Center Essentials 2007 135

Use Group Policy to assign computer startup scripts for 2007 Office deployment Use Group Policy Software Installation to deploy the 2007 Office system Group Policy Overview (http://technet.microsoft.com/en-us/library/cc179176.aspx)

136

Precache the local installation source for the 2007 Office system
When you deploy the 2007 Microsoft Office system, Setup creates a local installation source on the user's computer a copy of the compressed source files for the Office product that you are installing. Once the files have been copied to the user's computer, Setup completes the installation from the local installation source. You can minimize the load on the network by deploying the local installation source separately, before you deploy Office. To deploy the local installation source by itself 1. On the network installation point, open the Config.xml file in a text editor such as Notepad. By default, Config.xml is located in the core product folder for the Office product that you are installing. For example, if you are installing Microsoft Office Professional 2007, open the Config.xml file in the Pro.WW folder. 2. Find the <LIS> element; uncomment the line by deleting the opening <!-- and closing --> tags. 3. Set the <CACHEACTION> attribute to "CacheOnly". The line in Config.xml should look like the following example. <LIS CACHEACTION="CacheOnly" /> 4. Save the Config.xml file. 5. Run Setup.exe on users' computers; on the Setup command line, specify the path to your modified Config.xml file. Note that you must use a fully qualified path. For 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: If you precache the local installation source on users' computers and then need to remove it, you can set the <CACHEACTION> attribute to "RemoveCacheOnly" and run Setup again. This setting works only if users have not yet installed Office. Precaching allows most of the installation activity to occur on the local computer instead of over the network. Precaching also allows you to coordinate the upgrade to the new version. You can distribute the local installation source to groups of users over time and then schedule a simultaneous installation throughout the organization without over-taxing the network. To take full advantage of precaching the local installation source, use the Setup.exe file from the local cache and only pass in the optional files, the customization patch (MSP file), and the custom Config.xml from a network installation source. You must use the fully qualified path of these files, 137

and if the share names contain spaces, you must use quotation marks around the paths. For example: "C:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\setup.exe" /adminfile "\\server\share\Office 12\mychanges\db_outlookonly.msp" /config "\\server\share\Office 12\Pro.WW\Config.xml" where: /adminfile specifies the location of the customization MSP file. /config specifies the location of the customized Config.xml file. Setup handles the creation and maintenance of the local installation source automatically. The default location is \MSOCache\All Users at the root of the drive on which Office is installed. In addition to installing Office from the local installation source, Setup also uses it to repair, reinstall, or update Office later on. If the local installation source is corrupted or deleted, Setup uses the original source on the network to repair or re-create it. Note: If you set the installation location for Office to another location (for example, by entering a new value for the INSTALLLOCATION attribute in Config.xml), Setup creates the local installation source at that location. Note: For information about how to create a network installation point, see Create a network installation point for the 2007 Office system.

See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Run Setup from the local installation source to install the 2007 Office system Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx)

138

Run Setup from the local installation source to install the 2007 Office system
When you deploy the 2007 Microsoft Office system in your organization, Setup creates a local installation source on each user's computer, and then installs Office from that location. You can reduce the load on your network by separating these two parts of the installation process. First, run Setup to distribute the local installation source to users; later, run Setup again to complete the installation. Because the local installation source also includes a copy of Setup, you can go one step further and run Setup directly from the local installation source, rather than running it over the network. This strategy allows you to minimize the load on the network and still upgrade everyone to the new version at the same time. To run Setup, you must identify the subfolder in MSOCache\All Users that contains the core product that you want to install. Setup.exe is located in the same folder that contains the core product file <product_name>WW.msi, for example, EnterpriseWW.msi or ProPlusWW.msi. For example, for Microsoft Office Enterprise 2007, the core product file is EnterpriseWW.msi, and the folder containing setup.exe is {90120000-0030-0000-0000-0000000FF1CE}-drive, and it includes the following files: EnterpriseWW.msi EnterpriseWW.xml EnterWW.cab ID_00030.DPC Office64WW.msi Office64WW.xml ose.exe osetup.dll OWOW64WW.cab setup.exe Setup.xml

Run Setup from the local installation source 1. Distribute the local installation to users. For information about this step, see Precache the local installation source for the 2007 Office system. 2. In the table in Office product download codes later in this article, find the download code for the Office product that you want to install. 3. Run Setup.exe from the subfolder in MSOCache\All Users that corresponds to the download code. You can use a relative path to point to the location of Setup.exe on each 139

user's computer. For example, if you deployed the local installation source for Microsoft Office Standard 2007 on the C drive, use the following command line: C:\MSOCache\All Users\{90120000-0012-0000-0000-0000000FF1CE}-C \setup.exe You can send the Setup.exe command line to users by whatever means that you want for example, in a log-in file or a batch file. The default location of the local installation source is \MSOCache\All Users at the root of the drive on which Office is installed. Setup copies each package from the network installation point to a separate subfolder under MSOCache\All Users. The subfolder for the core product package includes a copy of Setup.exe that defaults to installing that product. Subfolders under MSOCache\All Users are named according to the download code for each package, rather than the folder naming convention used on the network installation point. The letter appended to the end of each download code (-C in the preceding example) indicates the drive on which the local installation source for that product is installed. If a user has installed multiple Office products on different drives, each drive contains a local installation source in the MSOCache\All Users folder. The drive letter in the download code allows Windows Installer to identify the correct location for the specified product. In the precache scenario only, Setup also copies the Updates folder from the network installation point to the local installation source. You can store both Setup customization files (MSP files) and software updates (MSP files) in the Updates folder and automatically include them in the installation. You gain the benefits of an offline installation without losing any of your customizations.

Office product download codes

Download codes for each Office product can be found in the Setup.xml file in the core product folder. The line in the Setup.xml for Office Standard 2007 is as shown in the following code segment. <LocalCache DownloadCode="{90120000-0012-0000-0000-0000000FF1CE}" SkuComponentDirectory="Standard.WW"> Download codes are also listed in the following table. Drive equals the drive on which \MSOCache is located, which is the drive on which Office is installedtypically the C drive. These product codes represent the initial release of the product.
Office product Core product folder Download code

Microsoft Office Enterprise 2007 Microsoft Office Professional Plus 2007 Microsoft Office Standard 140

Enterprise.WW ProPlus.WW Standard.WW

{90120000-0030-0000-00000000000FF1CE}-drive {90120000-0011-0000-00000000000FF1CE}-drive {90120000-0012-0000-0000-

Office product

Core product folder

Download code

2007 Microsoft Office Professional 2007 Microsoft Office Access 2007 Microsoft Office Excel 2007 Microsoft Groove 2007 Microsoft Office InfoPath 2007 Microsoft Office OneNote 2007 Microsoft Office Outlook 2007 Pro.WW Access.WW Excel.WW Groove.WW InfoPath.WW OneNote.WW Outlook.WW

0000000FF1CE}-drive {90120000-0014-0000-00000000000FF1CE}-drive {90120000-0015-0000-00000000000FF1CE}-drive {90120000-0016-0000-00000000000FF1CE}-drive {90120000-00BA-0000-00000000000FF1CE}-drive {90120000-0044-0000-00000000000FF1CE}-drive {90120000-00A1-0000-00000000000FF1CE}-drive {90120000-001A-0000-00000000000FF1CE}-drive {90120000-0018-0000-00000000000FF1CE}-drive {90120000-003B-0000-00000000000FF1CE}-drive {90120000-003A-0000-00000000000FF1CE}-drive {90120000-0019-0000-00000000000FF1CE}-drive {90120000-0017-0000-00000000000FF1CE}-drive {90120000-0051-0000-00000000000FF1CE}-drive {90120000-0053-0000-00000000000FF1CE}-drive {90120000-001B-0000-00000000000FF1CE}-drive

Microsoft Office PowerPoint PowerPoint.WW 2007 Microsoft Office Project Professional 2007 Microsoft Office Project Standard 2007 Microsoft Office Publisher 2007 Microsoft Office SharePoint Designer 2007 Microsoft Office Visio Professional 2007 Microsoft Office Visio Standard 2007 Microsoft Office Word 2007 PrjPro.WW PrjStd.WW Publisher.WW SharePointDesigner.WW VisPro.WW VisStd.WW Word.WW

For information about the numbering scheme for the 2007 Office system product codes, see Microsoft Knowledge Base article 928516: Description of the numbering scheme for product code

141

GUIDs in 2007 Office suites and programs (http://go.microsoft.com/fwlink/?LinkId=103815) on the Microsoft Help and Support Web site.

142

Sequentially install multiple products of the 2007 Office system

The Setup program for the 2007 Microsoft Office system installs one Office product at a time by default. You can use the chaining feature to customize Setup to install an additional Windows Installer (MSI)-based product. In this process, you customize the primary installation to install an additional productthe chained installation. For example, you can customize the Setup program in Microsoft Office Enterprise 2007 to install Office and then to install Microsoft Office Visio Professional 2007. Caution: While it is possible to use chaining to install additional Windows Installer-based products, this method generally is not as reliable as installing each product separately. For example, if you chain multiple installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation might not complete successfully. The recommended method for installing multiple products together is to use a deployment management program, such as Microsoft Systems Management Server. For more information, see Using Systems Management Server 2003 to deploy the 2007 Office system. For information about Config.xml chained command issues, see KB article 928467, "Chained commands do not run after the installation of a 2007 Office suite or program fails" on the Microsoft Help and Support Web site (http://go.microsoft.com/fwlink/?LinkId=99913). To chain two product installations together, you must customize both the primary and the chained installation. Note: Chaining more than one Windows Installer (MSI)-based product in the OCT is not recommended; chaining might fail and a message about another instance of setup running might be displayed. To chain more than one MSI-based product, you must use the Command element in the Config.xml file and specify the Wait attribute with a -1 value (Wait="-1"). For more information, see How it works. To customize the primary installation 1. Create a network installation point that includes the products you will install. 2. Run the Office Customization Tool (OCT) by running Setup.exe from the root of the network installation point with the /admin command-line option. 3. In the Select Product dialog box, select the product that is the primary installation. 4. In the left pane of the OCT, select Licensing and user interface. In the right pane, set Display level to None, enter the Product key, and select I accept the terms in the License Agreement. 143

5. In the left pane, select Add installations and run programs. In the right pane, click Add. 6. In the Add Program Entry dialog box, perform the following steps for the product that is chained. For Target, enter the fully qualified path of the Setup.exe file in the root of the network installation point. For example, enter \\server\share\setup.exe. For Arguments, enter the /config command-line option with the fully qualified path to the Config.xml file in the core product folder of the product that is chained. For example, if you are chaining Office Visio Professional 2007, enter /config \\server\share\VisPro.WW\config.xml. Note: Command-lines entered in the Add Program Entry and Modify Program Entry dialog boxes are intended to be used only for initial installs and uninstalls. Command-lines are processed only during initial installs and uninstalls. Select Run this program after the Office product has been installed. Click OK.

7. Make other customizations in the OCT as needed. 8. Save the Setup customization file with a unique name in the Updates folder of the network installation point. 9. Exit the OCT. To customize the chained installation 1. Run the OCT. 2. In the Select Product dialog box, select the product that you want to chain. 3. In the left pane of the OCT, select Licensing and user interface. In the right pane, set Display level to None, enter the Product key, and select I accept the terms in the License Agreement. 4. In the left pane, select Modify Setup properties. In the right pane, click Add. 5. In the Add/Modify Property Value dialog box, enter the following: For Name, enter SETUP_REBOOT. For Value, enter Never.

6. Click OK. 7. Make other customizations in the OCT as needed. 8. Save the Setup customization file with a unique name in the Updates folder of the network installation point (create a separate Setup customization file for each product). 9. Exit the OCT. 10. Repeat this procedure for each product that is chained. 144

To install the chained products 1. Run Setup from the root of the network installation point, specifying the Config.xml file for the primary product. For example, if the primary product is Office Enterprise 2007, enter \\server\share\setup.exe /config \\server\share\Enterprise.WW\config.xml. 2. In the Select Product dialog box, select the primary product. After Setup installs the primary product, it installs the chained product that you specified in the OCT. Tip: You can put the customization files you created in a location other than the Updates folder. Just add the /adminfile option to the Setup command lines in the procedures above to specify the customization files to use. For more information about using Setup command-line options, see Setup command-line options for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc178956.aspx).

How it works
The Setup program for the primary product follows the typical installation process. After that installation is complete, Setup runs the program that you specified in the OCT. Setup waits until each program is finished before it runs the next program. There are two important considerations when you chain products in the 2007 Office system, as demonstrated in the preceding procedures: Run the primary Setup quietly. A chained Setup program cannot run if the primary Setup program is running interactively. You must run the primary Setup program with Display level set to Basic or None. It is recommended that chained installations also run with Display level set to None. And because you are running Setup quietly, you must enter the product key for each product in the OCT. Run the chained installation with SETUP_REBOOT set to Never. If a chained installation causes the computer to restart, the primary product is installed, but additional chained installations do not run after the computer restarts. To prevent this, set the SETUP_REBOOT setting to Never for all chained installations. If one of the chained installations might require a computer restart, and you want to force a restart after the primary and chained installations finish, set the SETUP_REBOOT setting of the primary installation to Always. Notes You can also use the Command element of the Config.xml file to chain an additional Windows Installer (MSI)-based product. The Command element in the 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 for 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 145

ignored. For more information about the Command element, see Config.xml in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). If you are using the Command element in the Config.xml file to chain an additional Windows Installer (MSI) 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 might 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"/>. If you are configuring a chained installation in the Config.xml file that you want to run quietly, you must specify 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:

See Also Office Customization Tool (http://technet.microsoft.com/en-us/library/cc179097.aspx) see Config.xml in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx) Run Setup for the 2007 Office system on users' computers

146

Stage deployment of applications in the 2007 Office system

If you are installing a product that contains multiple applications, such as Microsoft Office Enterprise 2007, you might choose not to install all of the applications at the same time. For example, you may prefer to add Microsoft Office Outlook 2007 to user installations of Office Enterprise 2007 in a separate step. You can use the Office Customization Tool (OCT) to select the applications in the product that you do not want to install initially. Later, you use the OCT again to select those applications that you want to add to user installations. This is the recommended way to stage deployment of Office applications, rather than purchasing and installing individual products separately. To prevent Setup from installing specific applications 1. From the root of the network installation point, run the following command line to start the OCT: setup.exe /admin. 2. Select the product that you want to configure 3. Click OK. 4. In the left pane, click Set feature installation states. 5. In the right pane, set the installation option to Not Available for each application that you do not want to install. The application name is set to bold to show that you have changed its installation option. To prevent users from installing this application themselves, select the Hidden and Locked options. The symbols [H] and [L] are added to the application name to show that these options are set. For example, to not install Outlook, expand Microsoft Office and change the installation options for Microsoft Office Outlook to Not Available, Hidden, and Locked. The application name displays as [H] [L] Microsoft Office Outlook. 6. Make other customizations, and on the File menu, click Save As. 7. Specify a path and file name for the Setup customization file, and click Save. 8. On the File menu, click Exit. 9. Copy the Setup customization file to the Updates folder in the network installation point. 10. On the user's computer, run Setup.exe from the root of the network installation point. When you run Setup to install Office, Setup uses the customization file in the Updates folder that you created and installs Office without the applications you set to Not Available. To add applications to the installation 1. Run the OCT as in the previous procedure and select Open an existing Setup customization file. Click OK. 147

2. Find and select the Setup customization file that you created in the previous procedure. 3. Click Open. 4. In the left pane, click Set feature installation states. 5. In the right pane, find the applications that you set to Not Available in the previous procedure. Each application name appears in bold to show that it was changed. For each application that you want to add to the installation, set its installation option to Run all from My Computer or Installed on First Use. For example, to install Outlook, expand Microsoft Office and change the installation option for Microsoft Office Outlook to Run all from My Computer. 6. Make other customizations, and on the File menu, click Save. 7. Click Exit. 8. Deploy and apply the Setup customization file (MSP) to users' computers. Tip: You do not have to modify your original Setup customization file to add applications to an installation. Instead, you can create a new customization file with the appropriate installation options and apply that customization file to the users' computers.

How it works
When you apply the Setup customization file to the user's computer, the existing Office installation is modified to add the specified applications. Because the Setup customization file is a Windows Installer package (MSP), you can apply it to users' computers just as you would a software update, using whatever deployment method you have available. For example, you can use a deployment management program such as Microsoft Systems Management Server. Note: You cannot apply the Setup customization file to existing installations by putting the file in the Updates folder and running Setup again on the user's computer, or by running Setup with the customization file specified in the command line. You must apply the MSP file directly to the user's computer.

See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx) Run Setup for the 2007 Office system on users' computers

148

Deploy the 2007 Office system on a Terminal Services-enabled computer

In this article: Planning the Terminal Services environment Customizing the 2007 Office release Installing the 2007 Office release onto a Terminal Services-enabled computer Removing the default user name

To deploy the 2007 Microsoft Office system on a Terminal Services-enabled computer, you must: Plan the Terminal Services environment. Customize the 2007 Office system. Install the 2007 Office system onto the Terminal Services-enabled computer.

Planning the Terminal Services environment

Use the best practices and recommended guidelines in the following sections to plan an effective Terminal Services environment for the 2007 Office system.

Evaluating licensing requirements

You cannot run all versions of the 2007 Office system on a Terminal Services-enabled computer. Be sure that you understand and meet the following licensing requirements before you deploy the 2007 Office system on a Terminal Services-enabled computer. You can run the 2007 Office system on a Terminal Services-enabled computer only if your version of the 2007 Office system uses a volume license product key and does not require activation. If you install a retail version, pre-installed version (PIPC), or original equipment manufacturer (OEM) version of the 2007 Office system on a Terminal Services-enabled computer, you will see the following error when you try to run a 2007 Office system program: This copy of Microsoft Office cannot be used on Terminal Server. Please contact your local authorized Microsoft retailer for more information. In addition, the program that you try to open will close unexpectedly.

Evaluating software requirements

Be sure that you understand the requirements for the server and the client computer before you install the 2007 Office system on a Terminal Services-enabled computer.

149

Server requirements
You can run the 2007 Office system on Windows Server 2003 with Service Pack (SP) 1 or later. You cannot install or run the 2007 Office system on a server operating system that was released earlier than Windows Server 2003, such as Windows 2000 or Windows NT 4.0. Deploying on Terminal Services requires a review of the design changes within the 2007 Office system, and a review of the server requirements depending on the version of Windows Server (2003 or 2008) that you intend to use. Depending on the current server hardware, which will support multiple concurrent sessions, the performance will be dramatically impacted. Processor and memory requirements will vary depending on the workload. The following table shows the results of some recent tests. Windows Server version 2008 2008 2003 2003 Core processor 32 16 16 (does not support 32) 4 16 GB 150 Memory 256 GB 256 GB Concurrent sessions 1140 860

Terminal Services could be configured to load balance on a terminal server farm depending on the customers deployment needs. As Windows Server 2003 Terminal Server capacity and scaling shows, the number of concurrent sessions depends on many factors, such as workload and configuration. To support thousands of concurrent sessions, a terminal server farm configuration should be used. To view a report that analyzes the recent kernel timer processing and management improvements for Windows Server 2008 Terminal Services, see Kernel Timer Processing and Management Improvements on Windows Server 2008 Terminal Services (Update) (http://go.microsoft.com/fwlink/?LinkId=135707). To view the Windows Server 2008 tuning guide, which now has a reference for general tunings of Terminal Server Knowledge Worker workload (the Office-based workload) on Windows Server 2008, see Performance Tuning Guidelines for Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=135703). To learn about how Microsoft IT deployed Windows Server 2008 Terminal Services at Microsoft, see How MSIT Uses Terminal Services as a Scalable Remote Access Solution (http://go.microsoft.com/fwlink/?LinkId=135705).

Client requirements
One advantage of running the 2007 Office system on a Terminal Services-enabled computer is that older, less robust client computers can access the Terminal Services-enabled computer. Specifically, any computer that supports the Remote Desktop Protocol (RDP) can connect to a 150

Terminal Services-enabled computer. For example, although you cannot install the 2007 Office system on a computer that is running Microsoft Windows 2000 Professional, you can use a computer that is running Windows 2000 Professional to connect to a Terminal Services-enabled computer and run programs in the 2007 Office system if the computer is running RDP.

Evaluating recommended guidelines and best practices

Be sure that you review the following guidelines and best practices to plan an effective deployment of the 2007 Office system in a Terminal Services environment.

Single point of failure

Running the 2007 Office system on a single Terminal Services-enabled computer can create a single point of failure if the Terminal Services-enabled computer becomes unavailable or fails. In this event, all information workers who are connected to the Terminal Services-enabled computer could lose connectivity with their 2007 Office applications and could lose data. You can mitigate this risk by using Windows Clustering, which uses server clusters and Network Load Balancing to help ensure that Terminal Services-enabled computers safely fail over. For example, if you deploy a clustered and load-balanced server farm that consists of four Terminal Services-enabled computers and one of the Terminal Services-enabled computers becomes unavailable, the client connections will fail over to one of the other three Terminal Services-enabled computers.

Terminal server hardware

A Terminal Services-enabled computer requires significantly more memory and processing resources than a typical server. In addition, although Terminal Services is designed to be bandwidth efficient, the amount of data that the client exchanges with the Terminal Servicesenabled computer can be considerable and can affect performance. Consequently, before you roll out the 2007 Office system in a Terminal Services environment, be sure you perform thorough capacity testing to ensure that your terminal servers have sufficient disk space, processing power, memory, and network bandwidth.

Office Outlook 2007

You can deploy Microsoft Office Outlook 2007 on a Terminal Services-enabled computer. However, you must be aware of several considerations. For more information, see Considerations when installing Outlook 2007 in a Terminal Services environment (http://technet.microsoft.com/en-us/library/cc179161.aspx).

Terminal Services installation requirements

You must install the Terminal Server component on your server before you install the 2007 Office system. You must also add every user who logs on to the Terminal Services-enabled computer to the Remote Desktop Users group. Adding users to the Remote Desktop Users group enables the users to use Remote Desktop Connection to connect to the Terminal Services-enabled computer and run the 2007 Office system. If you do not add users to the Remote Desktop Users group, users are denied access to the Terminal Services-enabled computer. For more information about 151

installing and configuring Terminal Services, see Guidelines for Deploying Terminal Server (http://go.microsoft.com/fwlink/?LinkId=88006&clcid=0x409).

Stop the Microsoft Office Button from blinking

By design, the Microsoft Office Button blinks the first time that a user opens an application in the 2007 Office system. The blinking can cause a degradation of performance when users run the 2007 Office system on a Terminal Services-enabled computer. To improve performance, we recommend that users click the Microsoft Office Button the first time that they start an application in the 2007 Office system. This will deactivate the blinking.

Customizing the 2007 Office release

Before you install the 2007 Office system on a Terminal Services-enabled computer, you must be sure that the installation states are configured correctly for the features and applications that you are installing. Changing the installation state for a feature or an application does not require special tools and can be done during a manual installation or through the Office Customization Tool (OCT). When users run the 2007 Office system on a Terminal Services-enabled computer, they cannot install, configure, or uninstall features or applications. This is because the features and applications are installed on the terminal server and not on the client computer, and users do not have administrative rights to install, configure, or uninstall software on the terminal server. Consequently, you must be sure that the installation state for each feature and application is configured as Run from My Computer (that is, fully installed) or Not Available (that is, not installed). If the installation state for a feature or application is configured as Installed on First Use, users will see a warning if they attempt to use the feature or run the application. For example, if you configure the installation state for an application to Installed on First Use, the following error appears when a user tries to run the application: Only administrators have permission to add, remove, or configure server software during a terminal services remote session. Likewise, if you change the installation state for an add-in to Installed on First Use, the following error appears when a user tries to load the add-in: Microsoft Office can't run this add-in. An error occurred and this feature is no longer functioning properly. Please contact your system administrator. The 2007 Office system does not automatically detect that you are performing an installation on a Terminal Services-enabled computer. To prevent users from seeing these kinds of warnings, you must configure installation states for applications and features. You can configure installation states during a manual installation by clicking Customize on the Choose the installation you want page. See the following section for more information about how to perform a manual installation on a Terminal Services-enabled computer. You can also use the OCT to configure installation states during an automated installation. The following procedure describes how to configure installation states in the OCT.

152

Use the OCT to configure feature and application installation states 1. Start the OCT by running the following command at the command prompt: setup /admin 2. In the left pane of the OCT, under Features, click Set feature installation states. 3. In the details pane, click an application or feature and change the installation state to either Run from My Computer or Not Available. 4. Set additional options that you want in the OCT. 5. Save the settings to an .msp file.

Installing the 2007 Office release onto a Terminal Services-enabled computer

There are two ways that you can install the 2007 Office system on a Terminal Services-enabled computer: By running the Setup program and manually stepping through the installation process. By automating the Setup program with the customization (.msp) file, which you create with the OCT. In either case, you must configure the Terminal Services-enabled computer for install mode before you install the 2007 Office system. Install mode ensures that an application's configuration (.ini) files are copied to the system directory so the files can be used as master copies for userspecific .ini files. The first time that a user runs an application on a terminal server, the application searches the root directory for its .ini files. If the .ini files are not found in the root directory, but are found in the system directory, Terminal Services copies the .ini files to the root directory. This ensures that each user has a unique copy of the application's .ini files. The application creates new .ini files in the user's root directory. It is important that each user has a unique copy of the .ini files for an application. This prevents instances where different users might have incompatible application configurations (for example, different default directories or screen resolutions). You can configure a Terminal Services-enabled computer for install mode by running the change user /install command before you run the Setup program for the 2007 Office system, or by using Add or Remove Programs in Control Panel to run the Setup program for the 2007 Office system. If you use the change user /install command, you must also run the change user /execute command when you are finished installing the 2007 Office system. This will configure the Terminal Services-enabled computer for execute mode. You do not need to configure the Terminal Services-enabled computer for execute mode if you run the Setup program by using Add or Remove Programs in Control Panel because the computer will automatically be put into execute mode when the installation is complete. In addition, you must be a member of the Administrators group on the Terminal Services-enabled computer to install the 2007 Office system. Also, we do not recommend that you remotely install the 2007 Office system on a Terminal Services-enabled computer. Instead, you should log on to the terminal server console session locally to install the 2007 Office system. 153

Manually install the 2007 Office release

The following procedure describes how to manually install the 2007 Office system on a Terminal Services-enabled computer. It is assumed that you have installed Terminal Services and that you run the Setup program from a product disc or from a network installation point. Manually install the 2007 Office release on a Terminal Services-enabled computer 1. Click Start, point to Settings, and then click Control Panel. 2. Double-click Add or Remove Programs, click Add New Programs, and then click CD or Floppy. 3. Click Next. 4. Click Browse. 5. Locate the Setup program (Setup.exe) for the 2007 Office system. This can be on a product disc or on a network installation point. 6. Click Setup.exe, and then click Open. The Setup program for the 2007 Office system should open. 7. On the Enter your Product Key page, type your product key, and then click Continue. 8. On the Read the Microsoft Software License Terms page, click the I accept the terms of this agreement check box, and then click Continue. 9. On the Choose the installation you want page, click Customize. 10. On the Install Options tab, click an application or feature and change the installation state to either Run from My Computer or Not Available. 11. If you want to customize other settings, click the File Location tab or the User Information tab, and then make the changes that you want. 12. Click Install Now to start the installation. 13. When the installation is complete, click Close to close the Setup program. 14. On the After Installation page, click Next. 15. On the Finish Admin Install page, click Finish. It is important that you perform the last two steps. These steps configure the Terminal Services-enabled computer for execute mode.

Perform an automated installation of the 2007 Office release

The following procedures show how to perform an automated installation of the 2007 Office system on a Terminal Services-enabled computer. It is assumed that you have created a configuration (.msp) file and have configured the installation states for features and applications as recommended earlier in this article. It is also assumed that you run the Setup program from a network installation point, which you have already created. First, configure the Terminal Services-enabled computer for install mode.

154

Configure the terminal services-enabled computer for install mode 1. Click Start, click Run, type Cmd, and then click OK. 2. At the command prompt, type the following command, and then press ENTER: change user /install Next, run the automated installation exactly as you would on a client computer. For detailed instructions about how to perform an automated installation on a client computer, see Run Setup for the 2007 Office system on users' computers. When the automated installation is complete, configure the Terminal Services-enabled computer for execute mode. Configure the terminal services-enabled computer for execute mode 1. Click Start, click Run, type Cmd, and then click OK. 2. At the command prompt, type the following and press ENTER: change user /execute Note: With Interactive Installations, by default, the username field is populated with the currently logged-on users information. This is also true for the username set in config.xml.

Removing the default user name

Any user name that is provided during setup is written to the registry key HKCU\Software\Microsoft\Office\Common\UserInfo. Terminal Services mirrors this registry key to HKLM\Software\Microsoft\WindowsNT\CurrentVersion\TerminalServer\Install\Software\Micr osoft\Office\Common\UserInfo. Any new users then receive the defaults from the HKLM UserInfo key in their own user profile. Because a user name already exists, any new Terminal Services users will not be prompted to input their own names, and instead they get the default user name of the administrator. To resolve this issue for new users in a current Terminal Services deployment, the administrator on the computer running Terminal Services should remove values from the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\Common\UserInfo. To resolve the issue for all users in a new Terminal Services deployment, the administrator on the computer running Terminal Services should perform one of the following tasks: During installation, select Customize, and then clear the user name and initial values. Use a config.xml file that has the user name and initials set to empty values.

After installation, remove the values from the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\Common\UserInfo. 155

See Also Configure feature installation states of the 2007 Office system Customize the 2007 Office system Considerations when installing Outlook 2007 in a Terminal Services environment (http://technet.microsoft.com/en-us/library/cc179161.aspx)

156

Deploy custom templates in the 2007 Office system

In the 2007 Microsoft Office system, organizations can customize the New Document dialog box on the Office Button for several 2007 Office system applications. You can create and deploy templates for Microsoft Office Word 2007, Microsoft Office PowerPoint 2007, and Microsoft Office Excel 2007 to the New Document dialog box. For example, you can provide custom templates for Office Word 2007 documents that users can choose when they create a new document. This topic explains how to create and provide the custom templates. Note: In the 2007 Office system, object model support for customizing the File menu is replaced with the customization steps that are described in this topic. In the New Document dialog box, custom templates appear under the Custom heading on the left, as shown below. In this example, the custom templates are grouped in the Contoso category.

Follow these steps to provide custom templates in the New Document dialog box: 1. Create and save custom templates for one or more applications. 2. Copy the templates to a network folder or make the templates available on a Web site. 3. Create thumbnail and preview image files for the templates (optional).

157

4. Modify the sample XML text to provide information that is specific to your custom templates. Use the provided XSD text to validate your customized file. See Sample XML text and Validating your XML file for custom templates later in this topic. 5. Save the customized XML file to a network folder. Specify the path to the folder by using a registry key entry or provide the XML file from a Web service.

Create and save custom templates

It is straightforward to create templates for Office system applications. Open a new or existing document in the application and make customizations. Save the document as a template. For example, use the following steps to create a template in Office Word 2007. To create a template in Office Word 2007 1. Open a new or existing document in Office Word 2007. 2. Customize the document. 3. Click the Office Button, point to Save As and click Word Template. 4. In the File name: field, type the name of the template and click OK. An Office Word 2007 template file is saved with a .dotx extension. The file extension for other Office application templates is similar; for example, Microsoft Office Excel templates have an .xltx extension. Copy the template files to a network file server or provide the files on a Web site after you create and save the custom templates your organization needs.

Creating thumbnail and preview files

Create thumbnail and preview files of the custom templates; for example, by using screenshots and an image editor. You specify the image type of the thumbnail and preview files in the XML file. Choose from a variety of image types for the files, as specified in the XSD file. For example, you can use the GIF image type. The approximate dimensions for the files are provided in the following table.
Preview type Width Height

Thumbnail Preview

100 256

120 350

Click a template in the Microsoft Office Online section of the New Document dialog box for examples of thumbnail and preview files. For example, click Agendas in Office Word 2007.

158

Create a custom XML file that describes the custom templates

The 2007 Office system references an XML file to populate the items that are shown in the New Document dialog box. To include custom templates in New Document, you customize and provide an XML file that includes the location of the templates you want to display, together with the location of thumbnail and preview images for the templates. After you complete the configuration, custom templates appear in the New Document dialog box under the heading Custom. To simplify the process of creating the XML file, base your custom XML on the text provided in the Sample XML text section later in this topic. There are separate sections for each template type in the XML (for example, Word templates) and there are sections for each custom template within those sections: TEMPLATE 1, TEMPLATE 2, and so on. The sample XML includes a section for Office Word 2007 templates (application id = "WD"). You can also have sections for Office Excel 2007 templates (application id = "XL") and Office PowerPoint 2007 templates (application id = "PP"). The sample XML file includes four featuredtemplate sections. Delete or add template sections, depending on how many templates you have. Then modify the entries to specify the following for each template section: A friendly name for the template in the title string and the location of the template in the source string. The media type, filename, and location of the thumbnail preview for the template in the next source string. The media type, filename, and location of the large preview for the template in the final source string. You can delete the attribute values for the corresponding source string entries if you have not created a thumbnail preview file or a large preview file. A red X appears for the template in the thumbnail and preview areas of the New Document dialog box if you do not provide an image to display. In the sample XML file, the folder structure for the template entries is: Contoso\Source: template files (for example, .dotx) Contoso\media: thumbnail files Contoso\preview: preview files

Save the modified file in a network folder after you customize the XML file. This location is referenced in a registry key that you deploy to your users. Alternatively, you can create a Web service to provide the XML content. You create a registry key that directs the Office application to the network folder or Web service for the XML file. See the next section, Configure Office to use the custom templates,for details.

159

Configure Office to use the custom templates

After you customize the XML file, you deploy a registry key to users to enable Office 2007 to display your templates in the New Document dialog box in Office 2007 applications. You configure the registry key differently depending on whether the templates are located on a network folder or if they are provided by a Web service. You create the following registry subkey entry to provide the location of the XML file: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Spotlight\Provi ders Create a provider name entry under this registry subkeyfor example, Contosofor the group of templates that you want to provide that are described in the XML file. The provider name must be 30 or fewer characters. The name displays in the New Document dialog box in Office 2007 applications, followed by the list of custom templates. Under the provider name, specify the ServiceURL where the custom XML file you created is located. Optionally, you can list the application for which you are providing templates, as described in the following table.
Value name Value data (Data type) Description

ServiceURL

String

Specify either: 1. The network folder and XML file; for example, \\server\public\templates\Contoso\WordTemplates.xml) -or2. The URL of the Web service where the XML file that you created for deploying custom templates is located; for example, http://www.contoso.com. Details about this option are described below.

Application

String

Optional: Specify WD for Word templates, XL for Excel templates, or PP for PowerPoint templates. Do not include this registry key entry if the group of templates includes templates for more than one application.

The ServiceURL string is the provider to which the Office application sends a request for the XML file when you provide the templates by using a Web service. The Web service responds by providing the XML file. The request from the Office application includes the following parameters: App: the Office application value (XL, WD, or PP). LIDUser: the user language. LIDHelp: the user Help language. LIDUI: the user interface (UI) language.

For example, an Office application request for the XML file might be: 160

http://www.contoso.com?app="XL"&liduser=0409&lidhelp=0409&lidui=0409 You can use the Office Customization Tool (OCT) or other methods to deploy the registry key to users. Information about using the OCT to distribute registry keys is provided in the Add registry entries section of Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx).

Sample XML text

You can copy the following text into a text editor, such as Notepad, and modify the content to simplify creating the XML that is required to deploy custom templates with Office applications. Save the file as an XML file; for example, ContosoTemplates.xml. To validate the XML file, use the text provided in the next section, Validating your XML file for custom templates. <?xml version="1.0" encoding="utf-8"?> <o:featuredcontent lcid="1033" xmlns:o="urn:schemas-microsoftcom:office:office"> <o:application id="WD"> <o:featuredtemplates startdate="2007-01-01" enddate="2009-0302"> <!-- TEMPLATE 1 --> <o:featuredtemplate title="Template 1" source="\\server1\public\templates\Contoso\Source\1.dotx" > <o:media mediatype="gif" filename="1.gif" source="\\server1\public\templates\Contoso\media\1.gif" /> <o:preview filename="1big.gif" source="\\server1\public\templates\Contoso\preview\1.gif" /> </o:featuredtemplate> <!-- TEMPLATE 2 --> <o:featuredtemplate title="Template 2" source="\\server1\public\templates\Contoso\Source\2.dotx" > <o:media mediatype="gif" filename="2.gif" source="\\server1\public\templates\Contoso\media\2.gif" /> <o:preview filename="2big.gif" source="\\server1\public\templates\Contoso\preview\2.gif" /> </o:featuredtemplate>

161

<!-- TEMPLATE 3 --> <o:featuredtemplate title="Template 3" source="\\server1\public\templates\Contoso\Source\3.dotx" > <o:media mediatype="gif" filename="3.gif" source="\\server1\public\templates\Contoso\media\3.gif" /> <o:preview filename="3big.gif" source="\\server1\public\templates\Contoso\preview\3.gif" /> </o:featuredtemplate> <!-- TEMPLATE 4 --> <o:featuredtemplate title="Template 4" source="\\server1\public\templates\Contoso\Source\4.dotx" > <o:media mediatype="gif" filename="4.gif" source="\\server1\public\templates\Contoso\media\4.gif" /> <o:preview filename="4big.gif" source="\\server1\public\templates\Contoso\preview\4.gif" /> </o:featuredtemplate> </o:featuredtemplates> </o:application> </o:featuredcontent>

Validating your XML file for custom templates

Use the text provided in this section to validate your customized XML file for providing custom templates in Office applications. Copy the text into a text editor, such as Notepad, and save the file as an XSD file; for example, OfficeTemplates.xsd. <?xml version="1.0" encoding="utf-8"?> <xs:schema targetNamespace="urn:schemas-microsoft-com:office:office" elementFormDefault="qualified" xmlns="urn:schemas-microsoft-com:office:office" xmlns:o="urn:schemasmicrosoft-com:office:office" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="featuredcontent"> <xs:annotation> <xs:documentation>

162

This is the schema for custom spotlight providers in the new FileNew dialog in Word, Excel, and PowerPoint. Copyright (c) Microsoft Corporation. </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="application" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation> Include one application block for every application you have custom templates for </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="featuredtemplates" minOccurs="0" maxOccurs="1"> <xs:complexType> <xs:sequence> <xs:element name="featuredtemplate" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="media" type="CT_ImageAttributes"> <xs:annotation> <xs:documentation> The media element refers to the thumbnail (small) image for the template </xs:documentation> </xs:annotation> </xs:element> <xs:element name="preview" type="CT_ImageAttributes"> <xs:annotation> <xs:documentation> The preview element refers to the preview (large) image for the template </xs:documentation> </xs:annotation> 163

</xs:element> </xs:sequence> <xs:attribute name="title" type="ST_SpotlightString" /> <xs:attribute name="source" type="xs:anyURI" /> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="startdate" type="ST_Date" use="required" /> <xs:attribute name="enddate" type="ST_Date" use="required" /> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="id" type="ST_Application" use="required" /> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="lcid" type="xs:unsignedShort" use="required" /> </xs:complexType> </xs:element> <xs:simpleType name="ST_Application"> <xs:annotation> <xs:documentation> Specifies the application for which to deliver spotlight content </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="WD" /> <xs:enumeration value="XL" /> <xs:enumeration value="PP" /> </xs:restriction> </xs:simpleType> <xs:complexType name="CT_ImageAttributes"> <xs:sequence /> <xs:attribute name="mediatype" type="ST_MediaType"> 164

</xs:attribute> <xs:attribute name="filename" type="ST_Filename" use="required" /> <xs:attribute name="source" type="xs:anyURI" use="required" /> <xs:attribute name="alttext" type="ST_SpotlightString" use="optional" /> </xs:complexType> <xs:simpleType name="ST_SpotlightString"> <xs:restriction base="xs:string"> <xs:maxLength value="255" /> <xs:minLength value="1" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="ST_MediaType"> <xs:restriction base="xs:string"> <xs:enumeration value="jpg" /> <xs:enumeration value="png" /> <xs:enumeration value="bmp" /> <xs:enumeration value="gif" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="ST_Date"> <xs:annotation> <xs:documentation> Date must be specified in YYYY-MM-DD format </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[0-9]{4}-[0-9]{2}-[0-9]{2}" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="ST_Filename"> <xs:annotation> <xs:documentation> Filename cannot contain \ ? | > : / * " or less-than, must be less than 260 chars, and have a valid extension. Example: image.jpg 165

</xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[^\\\?|&gt;&lt;:/\*&quot;]{1,259}" /> </xs:restriction> </xs:simpleType> </xs:schema>

166

Deploy Access 2007 applications

In this article: Separating data and logic Using Access 2007 Runtime Deciding which file format to use Packaging an application

This article discusses deployment planning for database applications created by using Microsoft Office Access 2007, along with the features of Access 2007 Runtime. To deploy Office Access 2007 applications that can run without an installation of Office Access 2007 on a user's computer, you can distribute them along with Access 2007 Runtime, which you can download at Access 2007 Download: Access Runtime (http://go.microsoft.com/fwlink/?LinkId=120854).

Separating data and logic

You can create an Office Access 2007 application that combines data management and application logic in one file. This is the default application structure in Office Access 2007. Combining data management and application logic in one file provides the simplest deployment method, but this method works best if only one person uses the application at a time, and it involves some risk. For example, a user could cause data loss by unintentionally deleting or damaging the program file. In most cases, you should separate data management and application logic. This helps improve: Security Using a server for data storage can help keep data secure. Performance Using a split database or a database server can help reduce network traffic. Customizability New macro actions for the Navigation Pane can help you control who sees what. You can distribute different application logic files to different users. Portability The Work Offline and Synchronize commands can help users who are not in the office. One way to separate data and logic is by using the Access Database command (on the Database Tools tab, in the Database Tools group). The Access Database command splits the database application into two Office Access 2007 files: one for data and one for logic. When you use the Access Database command, Office Access 2007 creates a file that has "_be" (meaning "backend") appended to the file name. For example, if the original database file name is "Database1.accdb," Office Access 2007 creates a new database file that is named "Database1_be.accdb." Another way to separate data management and application logic is by using a database server program (such as Microsoft SQL Server) for data management, and Office Access 2007 for application logic. 167

To decide whether a single Office Access 2007 file is sufficient for both data management and application logic, consider the following: Data integrity and security Office Access 2007 users must have read/write permissions for the file that contains the application logic. If you combine data and logic in one file, the data is exposed to the same risks as the application logic. An Office Access 2007 application that uses separate logic and data files can help protect data integrity and security by taking advantage of NTFS security features. Because users need explicit read/write permission only to the application logic file, the data file can be made more secure. Your application might require additional security options, such as the ability to control which users have access to particular data. In this case, you should use a server product such as SQL Server or a Windows server operating system featuring Windows SharePoint Services 3.0 to store and manage your application data, and use Office Access 2007 to provide the application logic. Scalability An Office Access 2007 file can have a maximum size of 2 gigabytes (GB). Although 2 GB is a significant amount of text data, it might be insufficient for some applications, especially applications that store attachments in database records. If you separate the data and the logic, your application can accommodate more data. If you expect that users will store a large volume of data, you might consider using more than one Office Access 2007 data file. You should also review the Office Access 2007 program specifications for other scalability information. Network capacity If multiple users will have to use the application at the same time over a network, data corruption is more likely to occur if the data and logic are combined in one file. Moreover, if you combine the data and the logic in one Office Access 2007 file, you cannot optimize the network traffic that Office Access 2007 generates. If multiple users will simultaneously use your application over a network, you should separate the data and the logic, either by using two or more Office Access 2007 files, or by using a database server product for data and Office Access 2007 for application logic.

Using Access 2007 Runtime

If all of your users will have Office Access 2007 installed on their computers, they can open and use the application as they would any database file in Office Access 2007. If some or all of your users will not have Office Access 2007 installed on their computers, you will have to deploy Access 2007 Runtime to those users when you deploy your application. You can download Access 2007 Runtime at Access 2007 Download: Access Runtime (http://go.microsoft.com/fwlink/?LinkId=120854). Access 2007 Runtime is a redistributable program that lets people who do not have Office Access 2007 installed on their computers to use Office Access 2007 database applications. When you open an Office Access 2007 database by using Access 2007 Runtime, the database opens in runtime mode. Runtime mode is an Office Access 2007 operating mode in which certain Office Access 2007 features are not available by default. However, some of these unavailable features can be made available in runtime mode. The following features in Office Access 2007 are not available in runtime mode: 168

 Navigation Pane The Navigation Pane is not available in runtime mode. This helps prevent users from accessing arbitrary objects in the database application. Only those objects that you expose to users for example, by providing a switchboard form can be opened while using runtime mode. You cannot make the Navigation Pane available in runtime mode. The Ribbon By default, the Ribbon is not available in runtime mode. This helps prevent users from creating or modifying database objects, and from performing other potentially harmful actions, such as connecting to new data sources or exporting data in ways that you do not intend. You can create a custom Ribbon, and then associate that Ribbon with a form or report. You cannot expose the default Ribbon tabs in runtime mode. Design view and Layout view Design view and Layout view are not available for any database objects in runtime mode. This helps prevent users from modifying the design of objects in the database application. You cannot enable Design view or Layout view in runtime mode. Help By default, integrated Help is not available in runtime mode. Because you control what functionality is available in your runtime mode application, some of the standard integrated Office Access 2007 Help content might be irrelevant to people who use your application, and could potentially confuse or frustrate them. If you are using the Access 2007 Developer Extensions to package and deploy the database application, you can provide a custom Help file together with your runtime mode application. You can run any Office Access 2007 database in runtime mode on a computer that has the full version of Office Access 2007 installed. To run an Office Access 2007 database in runtime mode, use one of the following methods: Change the file name extension of the database file from .accdb to .accdr. Create a shortcut to the database, and include the /Runtime command-line switch in the shortcut. Although runtime mode limits the availability of navigation and design features, you should not use runtime mode as the primary means of securing a database application. On a computer that has the full version of Office Access 2007 installed, it might be possible for a user to open a runtime database application as a regular database application (that is, with all features available) and then to change the design or perform other unwanted actions. Even if you deploy the database application only on computers that do not have the full version of Office Access 2007 installed, it is still possible for a user to transfer the application to a computer that does have the full version of Office Access 2007 installed, and then open the runtime database application as a regular database application. If you want to distribute an Office Access 2007 application so that users cannot modify the design of forms, reports, or Microsoft Visual Basic for Applications (VBA) modules, consider using a compiled binary file (.accde). For more information about how to use a compiled binary file, see Deciding which file format to use.

Deciding which file format to use

There are four Office Access 2007 file formats that you can use when you deploy an application: 169

 .accdb This is the default file format for Office Access 2007. When you deploy an application in this format, users have the most options to customize and navigate the application in whatever manner they choose. If you want to ensure that users do not change the design of your application, you should use the .accde file format. In addition, a user cannot easily determine whether an .accdb file has been changed after you packaged it. To make this obvious, use the .accdc file format. .accdc This format is also known as an Access Deployment file. An Access Deployment file includes a program file and a digital signature that is associated with that file. This file format assures users that no one has changed the program file after you packaged it. You can apply this format to a default format Office Access 2007 file (.accdb), or to an Office Access 2007 compiled binary file (.accde). You can put only one program file in an Access Deployment file. If your application has separate data and logic files, you can package them separately. For more information about how to use an Access Deployment file, see Package and sign an Access 2007 database. .accde This format is also known as a compiled binary file. In Office Access 2007, a compiled binary file is a database application file that has been saved with all of the VBA code compiled. No VBA source code remains in an Office Access 2007 compiled binary file. You can use Access 2007 Runtime to open an Office Access 2007 compiled binary file. However, by default, the Runtime does not recognize the .accde file name extension. To open a compiled binary file by using Access 2007 Runtime, create a shortcut that points to Access 2007 Runtime, and include the path of the compiled binary file that you want the shortcut to open. Important: If you create a compiled binary file by using Office Access 2007 with Service Pack 1 installed, users cannot open the compiled binary file by using the full version of Office Access 2007 without Service Pack 1 installed. To resolve this issue, users should install Service Pack 1. .accdr This format enables you to deploy an application that opens in runtime mode. Deploying a runtime application can help you control the way that it is used, although it is not a means of securing an application.

Packaging an application
The simplest way to install an application is to provide the database application file to the application users. However, if you plan to deploy an application to a large audience, or to deploy an application more than once, you should consider using a software-packaging utility, such as the Access 2007 Developer Extensions Package Solution Wizard, to package your application into a Windows Installer Package (.msi file). You can then use the package to install the application. You can use the Package Solution Wizard to:

170

 Create a custom shortcut to the application. You can use this feature of the wizard to help make opening a compiled binary file easier for users who run your application by using Access 2007 Runtime. Add the installation folder as a trusted location. Automatically install Access 2007 Runtime on a user's computer, if it is not already installed. Include other files, such as a custom Help file, with your application. Create or modify registry keys. Distribute the Microsoft Software License Terms.

Add information about your application to the list in Add or Remove Programs in Control Panel.

Package a split database

The Access 2007 Developer Extensions Package Solution Wizard does not accommodate multiple installation paths. If your application has separate data and logic components, and you use the Access 2007 Developer Extensions to package your application, you might want to manually install the Office Access 2007 data files in the appropriate location, such as a file server. An application that has separate data and logic components uses linked tables to connect the two components. Because every network is different, it might be impractical to specify the installation path of both components. In most cases, if you use the Package Solution Wizard, you will use the wizard only to package the logic component. If you have enough information about the installation paths of the two components, you might want to create two installation packages by using the Package Solution Wizard so that you can specify the installation path for each component.

Package and sign an Office Access 2007 database

Office Access 2007 makes it easier and faster to sign and distribute a database than in earlier versions of Access. After you create an .accdb file or .accde file, you can package the file, apply a digital signature to the package, and then distribute the signed package to other users. The Package-and-Sign feature puts the database in an Access Deployment (.accdc) file, signs the package, and then puts the code-signed package at a location on the user's computer that you determine. Users can then extract the database from the package and work directly in the database (not in the package file). Note: Although this feature is also known as "packaging," it does not accomplish the same tasks as the Package Solution Wizard of the Access 2007 Developer Extensions. The feature described in this section packages an Office Access 2007 file and applies a digital signature to the package that helps indicate to users that the file is trustworthy. Remember the following as you proceed to create and sign a package:

171

 Packaging a database and signing the package are ways to convey trust. When you or your users receive the package, the signature confirms that the database has not been tampered with. If you trust the author, you can enable the content. The new Package-and-Sign feature applies only to databases saved in the Office Access 2007 file format. Office Access 2007 provides tools from earlier versions of Microsoft Office that you can use to sign and distribute databases that were created in an earlier file format. You cannot use the tools from earlier versions of Office to sign and deploy files that were created in the new Office Access 2007 file formats. You can add only one database file to a package. When you package and sign a database, all of the objects in the database file are codesigned, not just macros or code modules. The packaging and signing process also compresses the package file to help reduce download times. You can extract databases from package files that are located on servers running Windows SharePoint Services 3.0. To create a signed package, open the database that you want to package and sign. Note: To complete these steps, you must have at least one security certificate available. If you do not have a certificate installed on your computer, you can create one by using the SelfCert tool. For information about how to create a private security certificate, see Help secure an Access 2007 database (http://office.microsoft.com/search/redir.aspx? AssetID=HA012301871033&CTT=5&Origin=HA102188641033). Create a signed package 1. Click the Microsoft Office Button, click Publish, and then click Package and Sign. 2. In the Select Certificate dialog box, select a digital certificate, and then click OK. The Create Microsoft Office Access Signed Package dialog box appears. 3. In the Save in list, select a location for your signed database package. 4. Enter a name for the signed package in the File name box, and then click Create. Office Access 2007 creates the .accdc file and puts it in the location that you selected.

172

Apply an Outlook Profile (PRF) File to configure Outlook profiles

You can choose from two main methods if you need to update Microsoft Outlook profile information after you install Microsoft Office Outlook 2007: Update profile information in an Outlook profile file (PRF file), and distribute the file to your users. When Outlook imports the PRF file, user profile settings are updated. Use the Office Customization Tool (OCT) to reconfigure profile settings, save those settings in a configuration maintenance file, and apply that file to your users' installations. Using a PRF file to update users' profiles might be the best choice if one or more of the following circumstances apply: You saved a PRF file with your users' Outlook profile configurations when you installed Outlook. You are making minor changes to the profiles. You do not want to inadvertently modify other Office settings, which cannot be done by using a PRF file. You want to add a service that cannot be configured by using the OCT. This topic describes how to update Outlook profiles by using a PRF file. Note: Using the OCT to update profiles might be the best choice if you are making other changes to Microsoft Office settings at the same time that you want to modify Outlook profile information, or if you are making substantial or complicated changes to Outlook profiles. For more information about updating profiles by using the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). You can update an existing PRF file by editing it in a simple text editor, such as Notepad. The PRF file contains detailed comments to guide you in making appropriate changes. All of the customizations that are available through pages in the OCT can be made manually by editing the file. For example, follow these steps to update the Microsoft Exchange server name for a group of users: 1. In Section 1, in the [General] section, set the value for OverwriteProfile to Append as follows: OverwriteProfile=Append. 2. In Section 4, in the [Service 1] section, set the value of OverwriteExistingService to Yes as follows: OverwriteExistingService=Yes. 3. In Section 4, in the [Service 1] section, set a new string value for the HomeServer field. For example: HomeServer=New-Exchange-Server-Name. 173

After you make changes to the PRF file, you can use the file to update Outlook profiles in several ways. For example, you can provide the file to users by making it available on a network share, or you can distribute the file by using Microsoft Systems Management Server. Note: In previous versions of Outlook, the PRF file was an executable file. Users could update their profiles by double-clicking the file name. The Outlook PRF file is no longer an executable file. You can add custom features to users' Outlook profiles by editing the file. For example, if you need to add a new messaging service for your users that is not provided in the OCT, you can make manual changes to the PRF file to add the service. Note: A fast way to create a PRF file for use in your deployment is to create your preliminary configuration by specifying Outlook options in the OCT and exporting the settings. After you save the file, open it with a text editor and make additional changes. For more information about working with PRF files, see Customize Outlook profiles by using an Outlook Profile (PRF) file.

174

Distribute Electronic Business Cards in Outlook 2007

With Microsoft Office Outlook 2007 Electronic Business Cards, Outlook users can include a graphical view of contact information with a name, address, and logo in a traditional business card format. The information appears in a Contacts item or as part of an e-mail message signature, for example. You can make it easy for people in your organization to use standardized business cards by providing business card templates. The templates can include your company's logo, fax number, and so on, with a unified design and color scheme. Electronic Business Cards can be customized and provided to employees for download from an internal Web site. When a member of your organization downloads an Electronic Business Card from the Web site, you can provide code to automatically customize the card to include the employee's contact information with the standard content for your organization. You can also have employees complete their own information after they download a standardized template.

This topic includes two detailed examples for providing automatically-populated business cards: a Microsoft Office SharePoint Server 2007 solution and a .NET solution. Links are provided for downloading sample code for each solution, which you can customize (see Obtain sample solutions for distributing Electronic Business Cards later in this topic).

Options for adding employee contact information to cards

Example options for providing standardized Electronic Business Cards for users include: Sending business card templates to employees as e-mail message attachments. Providing business card templates on a network folder, for employees to browse and then save the card locally. Setting up a distribution page on an internal Office SharePoint Server 2007 site. Providing a custom .NET solution on an internal Web site.

The first two options require employees to personalize the cards with their contact information. The SharePoint and .NET options automatically populate business cards with employees' personal information.

175

Note: A simple but limited way to provide Electronic Business Cards is to send the template as an e-mail attachment or provide the template on a network folder. The business cards are not automatically personalized; each employee must edit the card locally to add his or her contact information. Include Electronic Business Card templates as e-mail attachments. With this method, you send an e-mail message to employeesto individual departments or to your organizationthat includes instructions and provides your organization's Electronic Business Card templates as vCard attachments. If you offer more than one business card design, you can embed preview images for each template in the body of the e-mail message. Employees can choose the best or most appropriate design to save. Provide Electronic Business Card templates on a network folder. Providing templates and instructions on a public folder that is available to employees in a department or organization is another way to distribute Electronic Business Cards. If branding differs between groups in your organization, you can create multiple shared folders to provide different business cards for different departments. By limiting permission on the shared folder to members of that department or organization, you ensure that employees access only the templates that are appropriate for their role in the organization. Providing a solution that automatically populates business cards with employees' contact information has a number of advantages, though this option involves more setup work than distributing templates for employees to personalize themselves. A significant benefit to using a solution that automatically personalizes the cards is that employees do not need to edit the cards themselves. This saves time and reduces the chance of typographical mistakes and other errors. Also, since employee data is populated automatically, duplicate Contact entries are less likely to be created for the employee's business card when the card is created or updated.

176

Another benefit is that centralized changes to business cards are straightforward to distribute. For example, if the company logo changes or if your organization changes its slogan, you can simply update the business card template and send an e-mail instructing employees to download new versions of their cards. When an employee saves the new card, the updated card includes the employee's information. This helps ensure a smooth transition to the new card format, and reduces the chance of errors from employees editing their own cards. Similarly, when someone receives a new job title or changes office locations, retrieving a new business card automatically reflects the change. There is no need for a manual update of the employee's card. This topic describes two solutions for automatically populating Electronic Business Cards. With both solutions, you provide a Web page that enables employees to preview business card templates and retrieve business cards that are automatically customized with their personal information. The contact information is obtained from SharePoint, Active Directory, or another source of contact information (such as an LDAP directory). The user receives a customized card after he or she chooses a business card template. Using a SharePoint site to distribute business cards The most robust and flexible method of issuing business cards is to provide the business cards on a SharePoint site. The setup work required for this solution is minimal if you already have Office SharePoint Server 2007 implemented in your organization. With the SharePoint solution, user information is already available locally in user profiles. This simplifies the process. However, you might need to make minor configuration changes, such as mapping custom fields from the directory that provides SharePoint with employee data (for example, Active Directory). Writing a custom .NET solution to distribute business cards A .NET solution provides similar functionality to using a SharePoint solution, but requires additional coding. With a .NET solution, code running on the server dynamically retrieves employee contact information from a directory or database. You must use impersonation to obtain user data from a data source (for example, from Active Directory). Instead of being available locally in a profile, as in the SharePoint scenario, the data must be obtained directly using the data sources unique application programming interfaces (APIs). Both methods use templates as the basis for standardized cards, as described in the next section. Following the section are examples of using a SharePoint site or a .NET solution, including code samples. Note: You can download sample solutions and technical information to help you deploy Electronic Business Cards in your organization. The next section provides links to download packages and explains how to use the sample code that is included.

177

Obtain sample solutions for distributing Electronic Business Cards

You can use sample code as a starting point for a customized solution for distributing Electronic Business Cards. Sample solutions are available for a SharePoint solution and for a .NET solution as part of the Outlook 2007 Sample: Distributing Electronic Business Cards download package (http://go.microsoft.com/fwlink/?LinkId=73339) on the Microsoft Download Center. Included in the package are the following items, which can be downloaded individually:
Package name Description

EBCNet.exe EBCSharePoint.exe EBCvCard21Whitepaper.exe EBCWhitepaper.exe

Sample solution using .NET Framework 2.0 Sample solution using Office SharePoint Server 2007 Outlook Extensions to the vCard 2.1 Format (whitepaper) Creating and Using Outlook Electronic Business CardsWhitepaper

You can download the sample solutions package for the deployment platform you use (Office SharePoint Server 2007 or.NET Framework 2.0). Then follow the directions in the next sections.

Sample solution packages

The sample solutions are packaged as IExpress files. When you double-click the IExpress package, you are prompted for a folder location for the files. The sample solution for deploying Electronic Business Cards by using a Office SharePoint Server 2007 site is EBC Templates on SharePoint Deployment Example. The sample solution for deploying business cards by using a .NET solution is EBC Templates on .NET Deployment Example. Note: Technical information about Outlook vCard specifications can be helpful when you customize an Electronic Business Cards distribution solution. To learn more about Outlook vCards, see the whitepaper Outlook Extensions to the vCard 2.1 Format included in the download package. The following files and folders are included in the SharePoint sample solution package (EBCSharePoint.exe):
File/Folder name Description

EBCDeploymentExample.aspx

ASPX page containing the placeholder for the business card templates. This page should be

178

File/Folder name

Description

set as the start page for the project. EBCDeploymentExample.aspx.cs C# file containing the server-side code for this solution. Includes code to load template previews and populates the user-selected template with the users contact information. Visual Studio 2005 C# assembly project for the EBCDeploymentExample solution. Visual Studio 2005 solution file for the example. Visual Studio 2005 user options file for the EBCDeploymentExample solution. Strong Name Key file used for signing the assembly file generated by compiling the EBCDeploymentExample project. Instructions for installing the example solution. Configuration file for this Web site. Includes keys for the location of business card templates, the format of template preview images, and the URL of the SharePoint site containing user profiles used to populate the templates with employee data. Folder containing the compiled assemblies when the EBCDeploymentExample project has been compiled. A compiled assembly can be in either the Debug or Release sub-folder, depending on the configuration when the project is compiled. Folder containing temporary object files when the EBCDeploymentExample project is compiled. Folder containing the AssemblyInfo.cs file (automatically generated for the EBCDeploymentExample project). Folder containing templates and template previews for four example business card designs.

EBCDeploymentExample.csproj EBCDeploymentExample.sln EBCDeploymentExample.suo ExampleAssembly.snk

ReadMe.txt web.config

\bin

\obj

\Properties

\Templates

The following files and folders are included in the .NET sample solution package, EBCNet.exe: 179

File/Folder name

Description

EBCDeploymentExample.aspx

ASPX page containing the placeholder for the business card templates. This page should be set as the start page for the project. C# file containing the server-side code for this solution. Includes code to load template previews and populates the user-selected template with the users contact information. Instructions for installing the example solution. Configuration file for this Web site. Includes keys for the location of business card templates, the format of template preview images, and the URL of the Active Directory used to provide contact data. This configuration file also contains the parameters to perform Windows user impersonation for authentication. Folder containing templates and template previews for four example business card designs.

EBCDeploymentExample.aspx.cs

ReadMe.txt web.config

\Templates

Working with the SharePoint sample solution: overview

The steps for working with the SharePoint sample solution are outlined here. For detailed descriptions that reference the sample code, see Using a SharePoint site for distributing business cards later in this topic. Install and configure the following environment to work with the SharePoint sample solution: Office SharePoint Server 2007 must be installed on a local computer running Microsoft Windows Server 2003 or later. An Office SharePoint Server 2007 site must be available, configured with user profiles. With the requirements in place, follow these steps to install and configure the solution for your organization's environment. First, configure the Web.Config file. 1. Open Web.Config from the download package in an editor and set SiteURL to the URL for your SharePoint site (for example, YourSharePointURL). 2. Open the Web.Config file for your SharePoint site in an editor, and copy the appSettings section of the download package's Web.Config file to the appSettings section of the SharePoint site's Web.Config file. The site's Web.Config file is located in SharePoints home directory. 3. Save the Web.Config files and exit the editors. Follow these directions to locate the Web.Config file for your SharePoint site. 180

To locate the home directory of a SharePoint site 1. In Windows, click the Start menu, and click Administrative Tools. 2. Click Internet Information Services (IIS) Manager and expand the node for your computer. 3. Expand Web Sites, and right-click the appropriate Web application (for example, SharePoint (80)). 4. Click Properties. 5. Click the Home Directory tab. After configuring the Web.Config file, you compile the solution and place required files in the correct folders. To compile the solution 1. Open EBCDeploymentExample.sln in Microsoft Visual Studio 2005. 2. Compile the project. 3. Copy the compiled assembly, located in bin\debug by default or bin\release if you compile in release mode, to the Global Assembly Cache. For more detailed instructions, see Copy the solution to the Global Assembly Cache in the "Using a SharePoint site for distributing business cards" section later in this topic. 4. Copy EBCDeploymentExample.aspx and the Templates folder to <SharePoint Install Drive> \Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS. You might need to change the permissions for EBCDeploymentExample.aspx to copy this file. Navigate to http://YourSharePointURL/_layouts/EBCDeploymentExample.aspx to explore the sample solution.

181

When users click a card image, they see a dialog box similar to the following example:

When users click Open, the business card is added to Contacts in Outlook, and the card is personalized with their contact information.

Working with the .NET sample solution: overview

The steps for working with the .NET sample solution are outlined here. For detailed descriptions that reference the sample code, see Using a .NET 2.0 internal Web site for distributing business cards later in this topic. 182

To work with the .NET sample solution, Microsoft Visual Studio 2005 must be installed on your local computer. It is also helpful to use a local Web site when you work with the sample solution. Configure the environment to use the sample solution. 1. In Visual Studio, open an existing Web site and select the example folder. 2. On the Website menu, click Add Reference..., and select System.DirectoryServices. 3. On the Website menu, click Add Reference..., and select System.Drawing. 4. In Solution Explorer, right-click EBCDeploymentExample.aspx and select Set As Start Page. 5. Edit Web.Config from the download package in an editor and set userName and password to a valid username and password on your domain. Note: Including a plain text username and password in a file is not a secure solution. See the following articles for information about creating a more secure solution: How to use the ASP.NET utility to encrypt credentials and session state connection strings (http://go.microsoft.com/fwlink/?LinkId=73341) and .NET Framework Developer's Guide: ASP.NET Impersonation (http://go.microsoft.com/fwlink/?LinkId=73342). 6. In Web.Config, set ADPath to point to a valid Active Directory on your network. 7. Save the Web.Config file and exit the editor. After you complete these configuration steps, you can see the sample solution by clicking Run to run the Web site in Visual Studio. When users click a card image, they see a dialog box similar to the following example:

When they click Open, the business card is added to Contacts in Outlook, and the card is personalized with their contact information.

183

Templates for Electronic Business Cards

Regardless of the method you choose for distributing Electronic Business Cards to your organization, you can create and provide templates to help ensure standardized Electronic Business Cards. The cards can include information that is common to all business cards in the group or company, and can be designed to fit your corporate branding, including logos, colors, and layouts. To build a template, you create a new contact item in Office Outlook 2007 and design the business card. You save the business card as a file on a Web site. Finally, you capture a screenshot image of the sample card to create a preview of the card.

Creating a business card in a new Outlook contact

The first step in providing an Electronic Business Card for users to download is designing a business card to use as a template. You do this by creating a business card in a new Outlook contact. To create an Electronic Business Card in Outlook 1. On the File menu, point to New, and click Contact. 2. Type a name for the contact (for example, Sample Card). 3. Enter information on the business cards. For example, you might want to include: Full Name Job Title Company Business Phone Business Fax E-mail Address

Include all the items that you want to appear on the business card. Items specific to each person will populate with that person's personal information when the business card downloads. Other items, such as the Business Fax number, might be the same for everyone in the organization. Once the business card is created with sample information, click Business Card in the contact item Ribbon to open the Electronic Business Card (EBC) editor. In the editor, design the business card to include the layout and features. For example, you can import a corporate logo by clicking Change in the Card Design area. Adjust the image layout, area, and alignment until your logo appears in the right place on the card. Adjust the text fields so that text appears in the desired order and is the correct size and color. You can also change the background color. Click Save and Close to save your changes.

Saving an Electronic Business Card template on a Web server

Next you save the card as a file on the Web server that provides the Web site where people preview and download business cards. 184

To save an Electronic Business Card as a file on the Web server 1. Click the contact you created to select it. 2. On the File menu, click Save As. 3. In the Save in list, browse to a folder on your Web server where your templates will reside. 4. In the File name box, type a descriptive name for the file, such as office.vcf. 5. In the Save as type list, click vCard Files.

Creating a preview image of the Electronic Business Card

If you have more than one business card design, you can help people decide which card to download by providing a preview image of the business card templates. To provide a preview image of a business card template 1. In Outlook, open the Contact item that contains the business card you designed and that you want to use as a template. 2. Right-click the business card image in the open Contact item. 3. In the context menu, click Copy Image. 4. In Microsoft Paint, on the Tools menu, click Edit. 5. Click Paste to paste the preview image. 6. On the Tools menu, click File. 7. Click Save and select the folder where you saved your vCard earlier.

Using a SharePoint site for distributing business cards

Once you have created standardized Electronic Business Cards templates as described in the previous section, you can choose from several options how to provide the templates to employees so they can obtain personalized business cards. If you use SharePoint in your organization, a straightforward way to provide the business cards is to create a page on an internal Office SharePoint Server 2007 site with sample images. Then you include code that queries SharePoint for user data to populate business card templates that correspond to the preview images. The steps for working with the SharePoint sample solution are outlined earlier in Working with the SharePoint sample solution: overview. This section includes details about how to work with and customize the example for your organization. In the example provided here, an ASP.NET page supported by code in a C# file facilitates distributing cards on the SharePoint site. You can download the sample SharePoint solution as part of a package designed to help administrators get started with distributing Electronic Business Cards. Download the solution from the Outlook 2007 Sample: Distributing Electronic Business Cards download package (http://go.microsoft.com/fwlink/?LinkId=73339) on the Microsoft Download Center. 185

Create a C# Class Library project

By creating a Class Library, your project is configured to compile to an assembly. The compiled assembly can later be copied to the Global Assembly Cache (GAC). In order for EBCDeploymentExample.aspx and EBCDeploymentExample.aspx.cs to work together in SharePoint, EBCDeploymentExample.aspx must reference an assembly in the GAC that contains the compiled C# code from EBCDeploymentExample.aspx.cs. To create a new C# assembly project in Visual Studio 1. In Visual Studio, in the File menu, click New, and click Project. 2. On the New Project dialog, in the Project types: area, click Visual C#. 3. In the Templates: area, click Class Library. 4. In the Name: field, type a name for the project (for example, EBCDeploymentExample) and specify a location or use the default location. 5. Click OK.

186

Sign the assembly with a strong name key

In order for the compiled assembly to be trusted in SharePoint, it must be signed with a strong name key. You can sign the compiled assembly by using the strong name key provided with the sample solution in the ExampleAssembly.snk file, or you can create your own strong name key. To sign a compiled assembly with the strong name key provided in the sample 1. In Visual Studio, go to Solution Explorer. 2. Right-click EBCDeploymentExample, and click Properties. 3. On the Signing tab, select the Sign the assembly check box. 4. In the Choose a strong name key file: drop-down list, click <Browse...>. 5. In the Open File dialog box, browse to the ExampleAssembly.snk file and click Open. 6. In the File menu, click Save to save the change.

187

For more information about strong name keys and signing assemblies, see the following resources: .NET Framework Developer's Guide: Creating Assemblies 188

(http://go.microsoft.com/fwlink/?LinkId=73345) and .NET Framework Developer's Guide - How to: Sign an Assembly with a Strong Name (http://go.microsoft.com/fwlink/?LinkId=73343).

Specify options for your customized solution

To customize the example solution to work in your environment, you must provide the server code with the following information: The location of the templates to display on the Electronic Business Cards page. The format of the thumbnail images that correspond to each business card. This format is the extension you used when saving the business card previews; for example, .jpg. The URL of the SharePoint site on which this solution will run. The SharePoint Web.Config file is a convenient way to make this information available to the server code. The Web.Config is located in the SharePoint sites Home directory. To find a SharePoint sites Home directory, follow the procedure earlier in this topic, To locate the home directory of a SharePoint site, in the section Working with the SharePoint sample solution: overview. Copy the parameters in the Web.Config file included in the sample solution you downloaded to the appSettings block in your SharePoint Web.Config file. Change the value of siteURL to the URL of your local SharePoint site. If necessary, update values for the templatePath and templateFormat settings. <configuration> ... </appSettings> <add key="templatePath" value="~/_layouts/Templates" /> <add key="templateFormat" value="jpg" /> <add key="siteURL" value="http://example" /> ... </appSettings> ... </configuration>

Add required references

In order for the sample solution to work correctly, you must add certain references to the solution. Add the following references to your solution in Visual Studio by right-clicking the EBCDeploymentExample project and clicking Add reference: System System.Configuration System.Drawing System.Web Microsoft.SharePoint 189

Microsoft.Office.Server

The sample solution uses SharePoint User Profiles as the data source for employee contact information. The following section provides detailed information about using User Profiles in the sample application. Working with User Profiles is more convenient if you include specific references in the code. Add the following to EBCDeploymentExample.aspx.cs: using System; ... using Microsoft.SharePoint; using Microsoft.Office.Server.UserProfiles;

Retrieve contact information by accessing SharePoint User Profiles

SharePoint User Profiles provide a consistent application programming interface (API) for accessing SharePoint user data, regardless of the original data source (for example, Active Directory or an LDAP directory). In the sample solution, User Profiles provide the employee contact information for completing a business card. Perform the following steps to retrieve the employee contact information and populate a business card: 1. Locate the SharePoint User Profile for the employee who has chosen a business card to download. 2. Create properties for each item (name, job title, and so on). 3. Extract the value for each item in the UserProfile. First, find the user's SharePoint profile. See the PopulateCard() function in the sample solution. // Obtain the location of this SharePoint site. String siteURL = ConfigurationManager.AppSettings["siteURL"]; // Create a Profile Manager for this site. UserProfileManager profileManager = newUserProfileManager(Microsoft.Office.Server.ServerContext.GetContext( newSPSite(siteURL))); // Find the identity of the user accessing this page. string sAccount = this.User.Identity.Name; // Get the SharePoint profile for the user with the given identity. UserProfile user = profileManager.GetUserProfile(sAccount); Next, create the properties for each item. UserProfileValueCollection givenName = null; 190

UserProfileValueCollection lastName = null; UserProfileValueCollection jobTitle = null; UserProfileValueCollection email = null; UserProfileValueCollection phone = null; UserProfileValueCollection company = null; Retrieve the values for the properties from the UserProfile. Properties that are not included in UserProfiles by default can be included in UserProfiles when SharePoint synchronizes with the source of the user data. For example, "company" is not a default UserProfile property. In this code sample, "company" is mapped to the Company field in the directory that provides SharePoint with employee contact data. givenName = user[PropertyConstants.FirstName]; lastName = user[PropertyConstants.LastName]; jobTitle = user[PropertyConstants.Title]; email = user[PropertyConstants.WorkEmail]; phone = user[PropertyConstants.WorkPhone]; company = user["company"]; For more information about defining additional SharePoint UserProfile properties, see Personalization Services in SharePoint Products and Technologies (http://go.microsoft.com/fwlink/?LinkId=73346).

Use site templates for a consistent look

It is straightforward to configure new pages hosted on a SharePoint site to follow the look and feel of the site. By specifying a Master Page File and then adding asp:Content sections for the header, footer, and any other panes common to pages on your SharePoint site, the new page fits seamlessly with the rest of the site. Note that in order for a page hosted by SharePoint to access a compiled assembly (such as EBCDeploymentExample.aspx), the page must reference the name, version, and public key token for the assembly. You specify these values by using the Inherits parameter, as shown in the following example. Both the Master Page File and Inherits parameters are set in the Page tag at the top of EBCDeploymentExample.aspx. <%@ Page Language="C#" MasterPageFile="~/_layouts/simple.master" ValidateRequest="False" Inherits="EBCDeployment.Example, EBCDeploymentExample, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0bac7bedd8e30aa1" %> The content sections specify which standard SharePoint components follow a SharePoint site template. The following content section illustrates how you can follow the site template. <asp:Content ID="PageTitle" ContentPlaceHolderId="PlaceHolderPageTitle" runat="server"> 191

<SharePoint:EncodedLiteral ID="EncodedLiteral1" runat="server" text="Electronic Business Cards" EncodeMethod='HtmlEncode'/> </asp:Content>

Host the new page in your SharePoint site

To host the new page in SharePoint, you place the page in the SharePoint LAYOUTS virtual directory. To do this, copy the EBCDeploymentExample.aspx file to the following folder: 1. <SystemDrive> :\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS Now users can access the page at the following location: 2. http:// example /_layouts/EBCDeploymentExample.html. Where example is the name of your SharePoint site.

Copy the solution to the Global Assembly Cache

The last steps in implementing the SharePoint sample solution are to compile the assembly, then copy the assembly to the Global Assembly Cache (GAC), where EBCDeploymentExample is configured to access it. Copy the compiled assemblyEBCDeploymentExample.dllfrom <project folder> \bin\debug to the GAC, which is located in <SystemDrive> :\windows\assembly. If you compile in release mode, the folder will be bin\release instead of \bin\debug. To copy your assembly to the new folder, open both folders in Windows Explorer and drag the .dll file from \debug folder to the GAC folder. Note: You may need to reset Internet Information Services (IIS) before the new SharePoint page can access the assembly and work properly. To reset IIS, open a Windows command window and type iisreset. Now you can navigate to http://YourSharePointURL/_layouts/EBCDeploymentExample.aspx to explore the sample solution.

Using a .NET 2.0 internal Web site for distributing business cards
If you do not have Microsoft Office SharePoint Server 2007 sites in your organization or want more flexibility in how you provide Electronic Business Cards, you can create a custom .NET solution for distributing cards. The steps for working with the .NET sample solution are outlined earlier in Working with the ASP.NET sample solution: overview. This section includes details about how to work with and customize the example for your organization. When you have created standardized Electronic Business Cards templates as described in the previous section, you can customize the .NET sample solution provided as a download to use Active Directory and ASP.NET 2.0 to implement a solution for your organization. Similar to the SharePoint option, you use this solution to provide a page on an internal Web site with preview 192

images and query employee data to populate business card templates that correspond to the preview images. This section provides guidance for understanding the sample solution to developers who are unfamiliar with using Active Directory together with .NET Framework 2.0.

Opening a current Web site in Visual Studio

To begin working with the sample .NET solution provided in the download package, open a local Web site in Microsoft Visual Studio (VS) 5.0 and navigate to the folder that contains the sample solution. When you open an existing Web site in VS, the VS project recognizes the relationship between the EBCDeploymentExample.aspx and EBCDeploymentExample.aspx.cs files. The Web sites configuration is automatically imported from the sample solutions Web.config file. To use an existing Web site with the sample solution in Visual Studio 1. In Visual Studio, on the File menu, click Open, and click Web Site. 2. Browse to the folder that contains the sample solution from the download package. 3. Click OK.

Specify options for your customized solution

To customize the example solution to work in your environment, you must provide the server code with the following information: The location of the templates to display on the Electronic Business Cards page. The format of the thumbnail images that correspond to each business card. This format is the extension you used when saving the business card previews; for example, .jpg. The folder path of the Active Directory that provides the employee data for personalizing the business card templates. The method of authentication; for example, Windows authentication. Credentials for impersonation.

You also might choose to provide assembly references for the Visual Studio compiler. References required for the sample solution are provided in the "Adding required references" instructions in a later section. The Web.Config file of the Web site is a convenient way to make this information available to the server code. Open the Web.Config file in the sample solution to set the parameter values for your configuration. <configuration> <appSettings> <add key="templatePath" value="~/Templates"/> <add key="templateFormat" value="jpg"/>

193

<add key="ADPath" value="LDAP://ServerName.exchange.yourdomain.com/DC=exchange, DC=yourdomain,DC=com "/> </appSettings> <system.web> <authentication mode="Windows"/> <identity impersonate="true" userName="username"password="password"/> </system.web> </configuration> It is important to specify a valid Active Directory for the ADPath parameter. The userName and password parameters represent the username and password for the Web site's service account. A more secure way to provide credentials is to encrypt the values instead of leaving them as clear text. For more information about encrypting credentials, see How to use the ASP.NET utility to encrypt credentials and session state connection strings (http://go.microsoft.com/fwlink/? LinkId=73341).

Add required references

You must add specific references to the solution to enable the sample solution to work correctly. In Visual Studio, right-click EBCDeploymentExample project and click Add reference to add each of the following references to your solution. System System.Configuration System.DirectoryServices System.Web

The System.DirectoryServices reference is required for connecting to and querying Active Directory. Working with Active Directory is more convenient if you include specific references in the code. Add the following reference to EBCDeploymentExample.aspx.cs: ... Using System.DirectoryServices;

Connect to Active Directory

To connect to Active Directory, create a DirectoryEntry parameter that includes the Active Directory path variable ( ADPath ): DirectoryEntry de = new DirectoryEntry(ConfigurationManager.AppSettings["ADPath"]);

194

Query Active Directory for employee contact information

You use the DirectorySearcher function to query Active Directory for employee contact information. Create the function using the DirectoryEntry created in the previous section. DirectorySearcher ds = new DirectorySearcher(de); Next, determine the identity of the user visiting the Web site. Remove the domain from the users identity, and ensure that data for only the user with the correct alias is retrieved. This example assumes that the e-mail address format in your organization is alias@yourdomain.com. string longAlias = this.User.Identity.Name; int start = longAlias.IndexOf("\\"); name. int end = longAlias.Length; alias. ds.Filter = "(mailnickname=" + alias + ")"; Next, specify the properties of the Outlook contact (vCard) that will be retrieved, so it can be updated later. ds.PropertiesToLoad.Add("givenName"); ds.PropertiesToLoad.Add("sn"); ds.PropertiesToLoad.Add("title"); ds.PropertiesToLoad.Add("mail"); ds.PropertiesToLoad.Add("telephoneNumber"); ds.PropertiesToLoad.Add("company"); // Get the given name. // Get the surname. // Get the job title. // Get the email address. // Get the phone number. // Get the company name. // Parse away the domain // Get the length of the

string alias = longAlias.Substring(start + 1, (end - (start + 1)));

Search the directory for the user with the specified alias and store the results in a SearchResultCollection. SearchResultCollection data = ds.FindAll();

Access contact information in Active Directory query results

After you retrieve the contact information from Active Directory, you use the information to personalize the employee business card. To access contact information in Active Directory query results, first create properties for the contact information. PropertyValueCollection givenName = null; PropertyValueCollection lastName = null; PropertyValueCollection jobTitle = null; PropertyValueCollection email = null; PropertyValueCollection phone = null; PropertyValueCollection company = null; Then find the values for the properties in the result set. 195

// In case invalid data was returned, try... try { // Get the properties needed for the EBC. DirectoryEntry resultEntry = data[0].GetDirectoryEntry(); givenName = resultEntry.Properties["givenName"]; lastName = resultEntry.Properties["sn"]; jobTitle = resultEntry.Properties["title"]; email = resultEntry.Properties["mail"]; phone = resultEntry.Properties["telephoneNumber"]; company = resultEntry.Properties["company"]; } catch (Exception) { // Create a writer for error output. StreamWriter sw = new StreamWriter(Response.OutputStream); sw.WriteLine("Error updating template!"); sw.Close(); } When the employee downloads the business card, it is now populated with the employee's contact information.

See Also Outlook 2007 Sample: Distributing Electronic Business Cards download package (http://go.microsoft.com/fwlink/?LinkId=73339)

196

Create and deploy Junk E-mail Filter lists in Outlook 2007

Junk e-mail filtering in Microsoft Office Outlook 2007 includes Junk E-mail Filter lists and technology built into the software that helps determine whether an e-mail message should be treated as junk e-mail. You can create the following initial Junk E-mail Filter lists to deploy to users: lists for Safe Senders, Safe Recipients, and Blocked Senders. The lists you provide are default lists; they cannot be locked down by policy. Users can customize the lists as they use Outlook, to fine-tune the filters to work best for their messaging needs. To deploy the Junk E-mail Filter lists, you create the lists on a test computer and distribute the lists to users. Perform the following steps to create and deploy these lists: 1. Install Office Outlook 2007 on a test computer. 2. Start Outlook and enter the desired entries for each Junk E-mail Filters list: Safe Senders, Safe Recipients, and Blocked Senders. 3. Export each list to a separate text file. 4. In the Office Customization Tool (OCT), on the Add Files page, include the three text files. 5. Also in the OCT, on the Modify user settings page, configure Junk E-mail Filter settings to turn on importing the filter list files and to specify the location of the files. 6. After you save your customizations, deploy the Setup customization file to users.

Create the lists

Install Office Outlook 2007 on a test computer and create the Junk E-mail filter lists. To create default Junk E-mail Filter lists 1. In Office Outlook 2007, on the Tools menu, click Options. 2. On the Preferences tab, click Junk E-mail. 3. On the Safe Senders tab, click Add. 4. Enter an e-mail address or domain name. For example: someone@exchange.example.com 5. Click OK. 6. To add more e-mail addresses or domain names, repeat steps 3 through 5. 7. Click Export to file. 8. Enter a unique file name for the Safe Senders list, and click OK. 9. Repeat steps 3 through 8 with the Safe Recipients tab and the Blocked Senders tab 197

to create Safe Recipients and Blocked Senders lists. Be sure to specify a unique file name for each of the three lists.

Deploy the lists

To distribute the Junk E-mail lists to users, configure the OCT to include the lists, and deploy Outlook. To customize Outlook deployment to install Junk E-mail Filter lists for users 1. In the OCT, on the Add Files page, click Add. 2. In the Add Files to dialog box, select the three Junk E-mail Filter files that you created in the previous procedure. Hold down the CONTROL or SHIFT key to select multiple files. 3. Click Add. 4. In the Destination path on the user's computer dialog box, enter the folder where you want to install the file on users' computers, and click OK. 5. Click OK again. 6. On the Change Office User Settings page, under Microsoft Office Outlook 2007\Tools | Options\Preferences, click Junk Mail. Note: Do not configure the setting as a registry key in the Group Policy tree to lock down this option. Outlook must have read/write access to the registry key so that the value can be reset after the files are imported. 1. Double-click Junk Mail Import List and ensure that the check box clears so that the setting is applied and Junk E-mail Filter lists are imported for users. 2. To overwrite existing Junk E-mail Filter lists with new lists, double-click Overwrite or Append Junk Mail Import List. 3. Click Apply Changes. 4. Select the Check to overwrite list. Uncheck to append. check box. 5. Click OK. 6. To specify a path to each Junk E-mail Filter list, double-click the settings corresponding to each list (for example, Specify path to Trusted Senders list) and enter a path and file name in the box (for example, in the Specify path to Trusted Senders list box). 7. Click OK or click Next setting to specify the path for another Junk E-mail Filter list. After you complete your customizations for Outlook in the OCT, click Finish to create a customization file and deploy Outlook to your organization. You can later change an existing Office Outlook 2007 installation to update the Junk E-mail Filter lists by following the procedure and including more recent Junk E-mail Filter files. 198

For more information about using the Office Customization Tool for configuring an Office installation to deploy files, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx).

See Also Plan for limiting junk e-mail in Outlook 2007 (http://technet.microsoft.com/enus/library/cc178957.aspx) Configure junk e-mail settings in Outlook 2007

199

III Deploying internationally

200

Customize and deploy multiple language versions of the 2007 Office system
In this article: Understanding the Setup logic for Shell UI language Deploy a default language version of Office Specify which languages to install Deploy different languages to different groups of users Identify installed languages

The language-neutral design of the 2007 Microsoft Office system helps simplify the deployment of Office products in multiple languages. Instead of creating a series of installations, you allow Setup to coordinate a single installation of multiple language versions. All language-specific components for a particular language are contained in a single language pack (SLP). Each language pack includes language-specific folders for all 2007 Office system products available in that language. Folders are identified by a language tag appended to the folder name. For a complete list of language tags, see Language identifiers in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179219.aspx). You copy all the language packs you need to a network installation point that contains at least one complete Office product. By default, Setup automatically installs the language version that matches the Windows user locale set on each user's computer. Alternatively, you can override this default behavior and manage the distribution of multiple language versions more precisely. For example, you can: Install more than one language on a single computer. Specify exactly which languages to install on users' computers, regardless of the language of the operating system, which is specified by user locale. Specify custom settings once and then apply them to all language versions that you deploy in your organization. Deploy different languages to different groups of users. Deploy the proofing tools for additional languages.

201

The following diagram identifies which deployment solution is appropriate for a given scenario. Multilanguage deployment flow chart

See full-sized image (http://technet.microsoft.com/en-us/library/cc511505.aspx) To identify which companion languages the single language packs include, see Identifying companion languages in Deploy proofing tools for the 2007 Office system. Each single language pack contains the proofing tools for one or more additional languages. For example, the Danish single language pack contains the proofing tools for English and German, in addition to Danish. All single language packs contain the proofing tools for English. For more information about Proofing Tools, see Deploy proofing tools for the 2007 Office system. Before it installs a language version of an Office product, Setup determines whether the user has the required operating system support for that language. Setup stops the installation if there is no support. For example, if a user has not enabled support for East Asian languages, Setup does not install the Japanese version of Office. It is important to plan the languages at the beginning of your deployment. There are special steps that you must take if you need to change users' configurations after the initial deployment and include additional languages as part of your customizations. For more information, see Add or remove languages after deploying the 2007 Office system.

202

Understanding the Setup logic for Shell UI language

Whenever you deploy the 2007 Office system from a network installation point that contains more than one language version, Setup must determine which language to use for the Setup user interface. By default, Setup uses that same language for the Office installation language and for the shell user interface (Shell UI). The Shell UI includes core elements of Office that register with the operating system, such file name extensions, Tool Tips, and right-click menu items. If your objective is to install only one language version of Office on each client computer and if you do not specify any additional languages in the Config.xml file, Setup uses the following logic to determine which language to use: Setup matches the language of the user locale. If there is not an exact match, Setup looks for a close match. If the user locale is set to English (Canada), for example, Setup might install Office in English (U.S). If there is no close match, Setup looks for a language in the following subkey in the Windows registry: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\12.0\Common\LanguageResourc es If the InstallLanguage entry has not been added to the LanguageResources subkey and set to a particular language (LCID), Setup prompts the user to choose a language (in an interactive installation). or The installation fails (in a quiet installation). If your objective is to install more than one language version of Office on each client computer, you should edit the Config.xml file and set the <AddLanguage> element for each language that you want to include. However, whenever you add more than one language in the Config.xml file, you must explicitly specify which of those languages Setup should use for the Shell UI. If the Shell UI language is not specified, the installation fails. You specify a language for the Shell UI by setting the ShellTransform attribute of the <AddLanguage> element. In this case, the language of the Setup user interface follows the logic described previously, while the languages installed on the computer and the language of the Shell UI are determined by the entries in the Config.xml file. Setup always installs Office in the language of the Shell UI, in addition to any other installation languages. For example, if the Shell UI is set to French, the user can select additional installation languages on the Languages tab, but the user cannot remove French.

Deploy a default language version of Office

If users in your organization work with Office files that are in the same language, or in a language that matches the language of their operating system, you can deploy a default language version of Office. 203

The following steps are the same as the standard steps for deploying the 2007 Office system and included for testing purposes. The only difference in the steps is that you will need to copy the language packs to the same network location as your installation files. To deploy a default language version of Office to every client computer 1. Create a network installation point for your primary 2007 Office system product by copying all the files and folders from source media to a shared network location. 2. Copy all the files and folders from the source media for each language pack to the same network location, and when prompted to overwrite duplicate files, click No. 3. Use the Office Customization Tool to configure the installation to match your organization's requirements. Because the majority of customizations apply to the core product, you do not typically need to customize each language separately. Setup applies your customizations during the installation regardless of the language being installed. For information about how you can customize your language settings, see Customize language settings for the 2007 Office system. Language packs that are acquired through a volume license agreement do not require a unique product key; only one volume license key is required for the entire installation. 4. On the Setup command line, specify the Config.xml file for the primary Office product that you are deploying. For example, the following command line installs Microsoft Office Standard 2007 in any language: \\server\share\Office12\Setup.exe /config \\server\share\Office12\Standard.WW\Config.xml where Office12 is the root of the network installation point. 5. Run Setup from the root of the network installation point. Setup installs only the language-specific elements that are needed for the Office product you are installing. Setup does not install the entire language pack unless you deploy the language pack as a separate product.

Specify which languages to install

If users in your organization work with Office files in more than one language, or if they need an Office language that does not match the language of their operating system, you can install all the languages they need at the same time. The following steps are the same as the standard steps for deploying the 2007 Office system and included for testing purposes. The only difference in the steps is that you will need to copy the language packs to the same network location as your installation files and edit the Config.xml file to specify which languages to install.

204

To specify one or more languages to install on a client computer 1. Create a network installation point for your primary 2007 Office system product by copying all the files and folders from source media to a shared network location. 2. Copy all the files and folders from the source media for each language pack to the same network location, and when prompted to overwrite duplicate files, click No. 3. In the core product folder for the product that you are installing, locate the Config.xml file. For example, if you are installing Office Standard 2007, find the Config.xml file in the Standard.WW folder. 4. Open the Config.xml file by using a text editor, such as Notepad. 5. Find the <AddLanguage> element; uncomment the line by deleting the opening <!-- and closing --> tags. 6. Set the value of the Id attribute to the language tag that corresponds to the language you want to install; you can specify more than one language by including additional <AddLanguage> elements and attributes. 7. Specify which language to use for the Shell UI by setting the <ShellTransform> attribute of the <AddLanguage> element. For example, to specify that Setup install both English and French, with English as the default installation language, add the following elements: <AddLanguage Id="en-us" ShellTransform="yes"/> <AddLanguage Id="fr-fr" /> If you want the default installation language and the Shell UI to match the operating system language, and you also want every user to have Office in both English and French, the code in the Config.xml file looks like this: <AddLanguage Id="match" ShellTransform="yes"/> Id="en-us" /> <AddLanguage Id="fr-fr" /> <AddLanguage

You are required to specify a value for the ShellTransform attribute whenever you add more than one <AddLanguage> element. Skipping this step causes the installation to fail. 8. To specify that Setup also match the language of the user's Windows user locale, add another line in the Config.xml file: <AddLanguage Id="match" /> In this case, Setup installs all specified languages plus the language that matches the user locale, if that language is different. 9. Save the Config.xml file. 10. Use the Office Customization Tool to configure the installation to match your organization's requirements. For information about how to customize your language settings, see Customize language settings for the 2007 Office system. 205

11. Run Setup.exe and specify the path of your modified Config.xml file. Note that you must use a fully qualified path; for example: \\server\share\Office12\setup.exe /config\\server\share\Office12\Standard.WW\Config.xml where Office12 is the root of the network installation point.

Deploy different languages to different groups of users

You can give different groups of users different sets of Office languages. For example, a subsidiary based in Tokyo might need to work with Office Standard 2007 documents in English and Japanese, while users in the European subsidiary need English, French, and German. In this scenario, you create a unique Config.xml file for each group of users. The following steps are the same as the standard steps for deploying the 2007 Office system and included for testing purposes. The only differences in the steps is that you will need to copy the language packs to the same network location as your installation files, create and edit the Config.xml file for each group to specify which languages to install, and then deploy the appropriate Config.xml file to the different groups. To deploy different languages to different groups of users 1. In the core product folder for the product that you are installing, locate the Config.xml file. For example, if you are installing Office Standard 2007, find the Config.xml file in the Standard.WW folder. 2. Open the Config.xml file by using a text editor, such as Notepad. 3. Locate the <AddLanguage> element and specify the set of languages that you want to install for this user group, as described previously. Note: You must also set the <Shell UI> attribute of the <AddLanguage> element, as described previously. 4. Save the Config.xml file with a unique file name. 5. Repeat these steps for the next user group. 6. Use the Office Customization Tool to configure the installation to match your organization's requirements. For information about how to customize your language settings, see Customize language settings for the 2007 Office system. 7. Deploy Office to each group of users separately, and in each case specify the correct Config.xml file on the Setup command line. For example: \\server\share\Office12\setup.exe /config\\server\share\Office12\Standard.WW\SubAConfig.xml 206

or \\server\share\Office12\setup.exe /config\\server\share\Office12\Standard.WW\SubBConfig.xml where Office12 is the root of the network installation point.

Identify installed languages

You can view a list of languages installed for the 2007 Office system either during the initial installation or during a separate installation of a language pack at the following registry key, which displays the LCID for each enabled language: HKCU\Software\Microsoft\Office\12.0\Common\LanguageResources\EnabledLanguages You can view the user interface (UI) language and fallback languages at the following registry key: HKCU\Software\Microsoft\Office\12.0\Common\LanguageResources While all applications in the 2007 Office system use a shared set of registry data to determine their UI language, they do not necessarily all appear in the same UI language. Applications in the 2007 Office system usually appear with the UI language indicated in the UILanguage entry of this registry key, but there are circumstances where this might not be the case. For example, some deployments might have Microsoft Office Word 2007 and Microsoft Office Excel 2007 installed in French, but another Office application installed in a different language. In this case, the other application will look at the UIFallback list in this registry key, and use the first language that works with its installed configuration. See Also Deploy proofing tools for the 2007 Office system Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx) Create different configurations of the 2007 Office system for different groups of users Change users' configurations after installing the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179141.aspx)

207

Customize language settings for the 2007 Office system

When a user starts the 2007 Microsoft Office system application for the first time, Setup applies default settings that match the language installed on the computer and the language specified by the Windows user locale setting. Four main language settings affect the way users work with Office: Primary editing language When more than one language version of Office is installed on the computer, this setting determines the language in which users work with Office applications and documents. Enabled editing languages Users can specify more than one language for editing Office documents. Depending upon the languages chosen, this setting might require that the user has installed additional Proofing Tools. User interface language This setting determines the language in which the user interface (menus and dialog boxes) is displayed. Help language This setting determines the language in which users view Help topics. You can configure these language settings for users in advance. If you specify custom language settings when you install Officeby applying a Setup customization file (MSP) file or by setting policiesthen Office does not overwrite your settings with the default settings when users start the applications for the first time.

Methods of customizing language settings

You configure language settings by using one of the following methods: Group policies Office Customization Tool (OCT) Language Settings tool

Use policies to enforce language settings

Policies enforce default language settings. Users in your organization cannot permanently modify settings managed by policy. The settings are reapplied each time the user logs on. To use policies to manage language settings 1. Copy the 2007 Office system policy template files to your computer. 208

2. Under Computer Configuration or User Configuration in the console tree, rightclick Administrative Templates. 3. Click Add/Remove Templates and then click Add. 4. In the Policy Templates dialog box, click the template that you want to add and then click Open. 5. After you add the templates you want, click Close. 6. Open the Group Policy object (GPO) for which you want to set policy. 7. Double-click Computer Configuration or User Configuration and expand the tree under Administrative Templates. 8. Locate language-related policies in the Microsoft Office 2007 system\Language Settings node. 9. Select the languages you want to use for each setting. 10. Save the GPO. The following policies help you manage language settings in the 2007 Office system: Display menus and dialog boxes in Display help in Located in the Display Language folder. Determines the language of the user interface. Located in the Display Language folder. Determines the language of online Help. If this policy is not configured, the Help language defaults to the user interface language. Enabled Editing Languages Located in the Editing Languages folder. Enables editing languages from the list of languages supported by Office. Primary Editing Language Located in the Enabled Editing Languages folder. Specifies the language in which users work with Office applications and documents when more than one language version is available on the computer. For more information about settings policies for the 2007 Office system, see Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179081.aspx).

Use a Setup customization file to specify default language settings

You use the OCT to create a Setup customization file (MSP file) that Setup applies during the installation. Settings specified in the OCT are the default settings. Users can modify the settings after the installation. To use the OCT to customize language settings 1. Start the OCT by running Setup with the /admin command-line option. 2. On the Modify User Settings page, expand the tree to Microsoft Office 2007 209

system\Language Settings. 3. Open the folder you want in the left pane. Double-click the setting in the right pane, select Enable, and specify a value. 4. Save the Setup customization file in the Updates folder at the root of the network installation point. Setup applies the file automatically when you install Office on users computers. For more information about using the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx).

Use the Language Settings tool to modify language settings

If you are not enforcing language settings by policy, users working in Office applications can use the Language Settings tool to change their language settings. To change language settings by using the Language Settings tool 1. On the Start menu, point to Programs, point to Microsoft Office, and point to Microsoft Office Tools. 2. Click Microsoft Office 2007 Language Settings. 3. Click the Display Language tab. This tab is available only when more than one language version is installed on the computer. 4. In the Display menus and dialogs in box, select the user interface language. 5. In the Display Help in box, select a language for online Help. 6. If you do not specify a language for Help, the online Help language defaults to the user interface language. 7. Click the Editing Languages tab. 8. Select the language you want to be available for editing and click the Add button. Repeat this step for each editing language you want to add. 9. In the Primary editing language box, select the language in which you will most often work with Office applications and documents. Note: Users can enable functionality for working in languages that are not installed on the computer. For example, if you select Korean as an editing language, you enable Asian and Korean features in Word even if Korean Proofing Tools are not installed. You must enable support for that language in the operating system.

210

Customize language-specific settings related to user locale

In addition to using the Primary editing language setting, Office 2007 also configures languagerelated settings, such as number format, to match the user locale of the operating system. This behavior is controlled by the LangTuneUp value entry in the LanguageResources subkey in the Windows registry. If you do not want user locale to affect default settings, you can reset the value of LangTuneUp when you install Office. If the LangTuneUp entry does not exist, Office creates the entry the first time an application starts and sets the value to OfficeCompleted. The LangTuneUp entry can have one of two values: OfficeCompleted Settings based on user locale are not applied to Office as a whole; however, individual applications still check for new input method editors (IMEs) and language scripts, and still apply application settings specific to the user locale. For example, applications ensure that newly installed keyboards have the appropriate editing languages enabled, and Word uses fonts in Normal.dot based on user locale. Prohibited No settings related to user locale are modified by Office or by any individual Office application. In some scenarios, ignoring the user locale setting can help maintain a standard configuration across a multilingual organization. Setting the LangTuneUp value entry to Prohibited ensures that language settings remain consistent and macros are more compatible internationally. For example, if your organization is based in the United States and you want to standardize settings internationally, you can deploy Office with Primary editing language set to en-us (U.S. English) and LangTuneUp set to Prohibited. In this scenario users receive the same default settings, regardless of their user locale. Ignoring user locale is not always the best option. For example, users who read and enter Asian characters in Office documents might not always have the Asian fonts they need to display characters properly. If the installation language on the users computer does not match the language used in the document and LangTuneUp is set to Prohibited, then Office does not display fonts in the non-default language. If your Office installations need to support multiple Asian language user locales, make sure LangTuneUp continues to be set to OfficeCompleted. To help ensure that users do not change the default value, set the corresponding policy. You can disable the Taiwanese date format in Office 2007 by customizing the Disallow Taiwan Calendar setting. In the OCT, change this setting under LanguageSettings on the Modify Office User Settings page. To set the corresponding policy, enable Disallow Taiwanese Calendar in the Group Policy Editor. This policy is located under Current User\Microsoft Office 2007 system\Language SettingsOther. Note In a multilingual environment, users often need to work with multilingual documents that contain text in languages that use different scripts. Unicode, a character-encoding standard developed by the Unicode Consortium, makes it possible for users to work with multilingual documents. Unicode provides a single script that can be used to represent many languages. 211

More information about Unicode is available in the Unicode Support in Office 2003 (http://go.microsoft.com/fwlink/?LinkId=78022) chapter in the Microsoft Office 2003 Resource Kit. See Also Customize and deploy multiple language versions of the 2007 Office system

212

Deploy proofing tools for the 2007 Office system

If you are an IT professional and use TechNet or the Office Resource Kit, take a look at our Online Survey (http://go.microsoft.com/fwlink/?LinkId=132189). Let us know how we can best meet your documentation needs. You can read more about our work to improve documentation on the Office Resource Kit Blog (http://go.microsoft.com/fwlink/?LinkID=125627&clcid=0x409). In this article: Determining the method for deploying Proofing Tools Deploying the Office Proofing Tools Kit 2007 Identifying companion languages

Proofing Tools for the 2007 Microsoft Office system allow users to edit documents in more than 50 languages. Depending on the language, these editing tools might include spelling and grammar checkers, thesauruses, and hyphenators. Proofing Tools might also include languagespecific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect.

Determining the method for deploying Proofing Tools

You can deploy additional Proofing Tools for users who need to edit documents in languages other than those already installed on their computers. You can deploy additional Proofing Tools from either of these sources: Single language pack Use this option if your users need both the user interface and the Proofing Tools for the language. Keep in mind that each language version of the 2007 Office system includes Proofing Tools for a set of companion languages. For example, when you deploy the English version of an Office product, users receive Proofing Tools for both Spanish and French in addition to English. Depending on the number of user interface languages you want to deploy and the included companion languages, single language packs might provide all of the Proofing Tools you need. For a list of companion languages, see Identifying companion languages. If you choose to deploy Proofing Tools from a language pack, see Customize and deploy multiple language versions of the 2007 Office system. Microsoft Office Proofing Tools Kit 2007 This product contains the Proofing Tools for all of the languages available with the 2007 Office system. Use this option if you do not need the user interface for the language and you need Proofing Tools that are not included in the set of companion languages for any languages that you have installed.

213

Note: The Office Proofing Tools Kit 2007 is only available as part of the Microsoft Office Multilanguage Pack 2007. The Office Multilanguage Pack 2007 contains all of the single language packs for the 2007 Office system, in addition to the Office Proofing Tools Kit 2007. The Office Multilanguage Pack 2007 is available for purchase in major retail stores and their Web sites, as well as through Microsoft volume licensing programs. With the Office Multilanguage Pack 2007, Proofing Tools are distributed as a separate product. Hard disk space requirements for Proofing Tools vary by language. For example, Proofing Tools for Spanish require 37 MB of hard disk space; Proofing Tools for Russian require 14 MB. Asian languages also require as much as 230 MB of additional hard disk space to accommodate the necessary fonts and Input Method Editors (IMEs). The overall disk space depends on whether you deploy Proofing Tools from a language pack or from the Office Proofing Tools Kit 2007. As with most products in the 2007 Office system, the entire package is cached to the local installation source (LIS). The total cache size for the Office Proofing Tools Kit 2007 is about 660 MB. Note: Proofing Tools do not include bilingual dictionaries or word breakers. Those tools are part of the language version or language pack.

Deploying the Office Proofing Tools Kit 2007

The Office Proofing Tools Kit 2007 provides a single resource from which you can install any of the Proofing Tools. You can install Proofing Tools on a local computer or deploy tools to a group of users. You can also customize and install the tools for one user or all users in your organization.

Customizing an installation of the Office Proofing Tools Kit 2007

To customize an installation of the Office Proofing Tools Kit 2007, modify the Config.xml file in the ProofKit.WW folder. For each set of Proofing Tools that you do not want to install, set the State attribute to Absent.

Syntax
<OptionState Id="optionID" State="Absent" | "Advertise" | "Default" | "Local" [Children="force"] />

Attributes

214

Attribute

Value

Description

Id State

optionID Absent Advertise Default Local

An item that the user can choose to install. The feature is not installed. The feature is installed the first time it is used. 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.

Children

force

Note: The default value for the State attribute is Local.

Proofing Tools Config.xml OptionState Id values

The following table provides the OptionState Id values for the Office Proofing Tools Kit 2007.
OptionState Id Proofing Tools Language

IMEMain_1028 IMEMain_1041 IMEMain_1042 IMEMain_2052 ProofingTools_1025 ProofingTools_1026 ProofingTools_2052 ProofingTools_3076 ProofingTools_1028 ProofingTools_1050 ProofingTools_1029 ProofingTools_1030 ProofingTools_1043

Chinese Traditional Input Method Editor (IME) Japanese IME Korean IME Pinyin IME Arabic Bulgarian Chinese (People's Republic of China) Chinese (Hong Kong) Chinese (Taiwan) Croatian Czech Danish Dutch 215

OptionState Id

Proofing Tools Language

ProofingTools_1033 ProofingTools_1061 ProofingTools_1035 ProofingTools_1036 ProofingTools_1031 ProofingTools_1032 ProofingTools_1037 ProofingTools_1081 ProofingTools_1038 ProofingTools_1040 ProofingTools_1041 ProofingTools_1087 ProofingTools_1042 ProofingTools_1062 ProofingTools_1063 ProofingTools_1044 ProofingTools_1045 ProofingTools_1046 ProofingTools_2070 ProofingTools_1048 ProofingTools_1049 ProofingTools_2074 ProofingTools_1051 ProofingTools_1060 ProofingTools_3082 ProofingTools_1053 ProofingTools_1054 ProofingTools_1055 ProofingTools_1058 216

English Estonian Finnish French German Greek Hebrew Hindi Hungarian Italian Japanese Kazakh Korean Latvian Lithuanian Norwegian (Bokml) Polish Portuguese (Brazil) Portuguese (Portugal) Romanian Russian Serbian (Latin) Slovak Slovenian Spanish Swedish Thai Turkish Ukrainian

OptionState Id

Proofing Tools Language

ProofingTools_1027 ProofingTools_1056 ProofingTools_1069 ProofingTools_1094 ProofingTools_1095 ProofingTools_1097 ProofingTools_1099 ProofingTools_1102 ProofingTools_1110 ProofingTools_2068 ProofingTools_1098

Catalan Urdu Basque Punjabi Gujarati Tamil Kannada Marathi Galician Norwegian (Nynorsk) Telugu

Example Config.xml file for Office Proofing Tools Kit 2007

The following example Config.xml files shows every language that has the State attribute set to Absent. If you choose to cut and paste this example into the Config.xml file for the Office Proofing Tools Kit 2007, set the State attribute for each set of Proofing Tools you want to deploy to Local (or Default or Advertise, if preferred). <Configuration Product="ProofKit"> <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Proofing Tools Kit Setup(*).txt" /> --> <!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> --> <!-- <USERNAME Value="Customer" /> --> <!-- <COMPANYNAME Value="MyCompany" /> --> <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> --> <!-- <LIS CACHEACTION="CacheOnly" /> --> <!-- <LIS SOURCELIST ="\\server1\share\Office12;\\server2\share\Office12" /> --> <!-- <DistributionPoint Location="\\server\share\Office12" /> --> <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> <OptionState Id="IMEMain_1028" State="Absent" Children="force"/> 217

<OptionState Id="IMEMain_1041" State="Absent" Children="force"/> <OptionState Id="IMEMain_1042" State="Absent" Children="force"/> <OptionState Id="IMEMain_2052" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1025" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1026" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1027" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1028" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1029" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1030" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1031" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1032" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1033" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1035" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1036" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1037" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1038" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1040" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1041" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1042" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1043" State="Absent" Children="force"/> 218

<OptionState Id="ProofingTools_1044" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1045" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1046" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1048" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1049" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1050" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1051" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1053" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1054" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1055" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1056" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1058" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1060" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1061" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1062" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1063" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1069" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1081" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1087" State="Absent" Children="force"/> 219

<OptionState Id="ProofingTools_1094" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1095" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1097" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1099" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1102" State="Absent" Children="force"/> <OptionState Id="ProofingTools_1110" State="Absent" Children="force"/> <OptionState Id="ProofingTools_2052" State="Absent" Children="force"/> <OptionState Id="ProofingTools_2068" State="Absent" Children="force"/> <OptionState Id="ProofingTools_2070" State="Absent" Children="force"/> <OptionState Id="ProofingTools_2074" State="Absent" Children="force"/> <OptionState Id="ProofingTools_3076" State="Absent" Children="force"/> <OptionState Id="ProofingTools_3082" State="Absent" Children="force"/> <!-- <Setting Id="Setup_Reboot" Value="IfNeeded" /> --> <!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --> </Configuration>

Installing the Office Proofing Tools Kit 2007 on an individual computer

If you have one or two users who need Proofing Tools, you can install Proofing Tools from the Office Proofing Tools Kit 2007 to individual computers. Install the Office Proofing Tools Kit 2007 on a single computer 1. On the Office Proofing Tools Kit 2007 CD, run Setup.exe. 2. Read and accept the Microsoft Software License Terms, and then click Continue. 3. To install the Proofing Tools for all available languages, click Install Now. The 220

installation will begin. Otherwise, to install individual languages, click Customize. 4. If you selected Customize, click the File Location and User Information tabs to change the information as needed. On the Installation Options tab, click the node (plus (+) sign) for the languages you want to install and use the drop-down arrows to set the appropriate installation states. 5. Click Install.

Precaching the local installation source for the Office Proofing Tools Kit 2007
When you deploy the Office Proofing Tools Kit 2007, Setup creates a local installation source on the user's computer a copy of the compressed source files for the Office Proofing Tools Kit 2007. Once the files have been copied to the user's computer, Setup completes the installation from the local installation source. You can minimize the load on your network by deploying the local installation source separately, before you deploy the Office Proofing Tools Kit 2007. To precache the local installation source for the Office Proofing Tools Kit 2007, see Precache the local installation source for the 2007 Office system. Use the Setup.exe and Config.xml files from the ProofKit.WW folder on the Office Proofing Tools Kit 2007 CD.

Identifying companion languages

The following table lists companion languages for each language in the 2007 Office system.
Primary language Companion languages

Arabic Brazilian Bulgarian Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Finnish French

English, French English, Spanish English, German, Russian English English English, German, Serbian, Italian English, German, Slovak English, German English, French, German French, Spanish English, German, Russian, Finnish, English, Swedish, German English, German, Dutch, Arabic, Spanish 221

Primary language

Companion languages

German Greek Hebrew Hindi

English, French, Italian English, French, German English, French, Arabic, Russian English, Tamil, Telegu, Marathi, Kannada, Guajarati Punjabi, Malayalam, Bengali, Nepali, Urdu English, German English, French, German English English English English, German, Russian English, German, Russian, Polish English, German, Norwegian (Ny) English, German English, French, Spanish English, French English, Ukrainian, German English, German, French, Croatian English, Czech, Hungarian, German English, German, Italian, Croatian English, French, Basque, Catalan, Galician, Brazilian English, Finnish, German English, French English, French, German English, Russian, German

Hungarian Italian Japanese Kazakh Korean Latvian Lithuanian Norwegian (Bk) Polish Portuguese Romanian Russian Serbian (Latin) Slovak Slovenian Spanish Swedish Thai Turkish Ukrainian

222

See Also Language identifiers in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179219.aspx)

223

Add or remove languages after deploying the 2007 Office system

In this article: Deploy language packs Remove language packs Identify installed languages

Although the most commonly deployed languages for the 2007 Microsoft Office system are released at the same time as the product, many other Single Language Packs (language packs) are released over time. The Multilanguage Pack, which includes all available language packs, is not released until after all the individual language packs are released. If you upgrade your multilingual organization to the 2007 Office system before all the language packs are released, however, you can add or remove languages later. The Multilanguage Pack and Proofing Tools CDs for the 2007 Office system are available for purchase in major retail stores and via their Web sites, and also through Microsoft volume licensing programs. To add languages after you deployed the 2007 Office system, you deploy the language packs as separate products. To do this, there must be at least one 2007 Office system product installed on the computer. This method involves running Setup.exe for the language pack that you want to install, so that the full language pack is installed on the computer. It is important to plan the languages at the beginning of your deployment. If you change users' configurations after the initial deployment and include additional languages as part of your customizations, you must first copy all the Single Language Packs (SLPs) you want to deploy to the network installation point that contains the Office product files; for example, \\server\share\Office12. A static list of the products contained in the installation source is built only during the initial creation of a customization patch. If you later add more languages to the installation source, the existing patch is not updated to reflect this change. Therefore, you must also re-create the customization MSP file that you want to deploy to users after you update the installation source with additional languages. Failure to do this might result in unexpected behavior, because the changes to the customization MSP file will not apply to the added languages. If you do not re-create the MSP file, it is possible that your deployment will test correctly in your lab, but users might not see the new language in their Office applications, or they might see only a subset of the language features. For more information, see Change users' configurations after installing the 2007 Office system (http://technet.microsoft.com/enus/library/cc179141.aspx).

Deploy language packs

If you deployed multiple 2007 Office system release products in your organization and you need to add more language support, you can deploy language packs as separate products. In this

224

case, Setup installs language-specific elements for every product in the 2007 Office system. No matter which products users have installed, users can access the additional language versions. For this deployment method to work, there must be at least one 2007 Office system product installed on the computer that you are deploying to. When you deploy language packs separately, you must consider the amount of disk space that is required on users' computers. For example, the English language pack requires 600 MB for both the language pack and the installation files that are stored in the local installation source. The Japanese language pack requires 1,000 MB. Deploy language packs 1. Copy all the files and folders in the new language pack from the source media to a location on the network. If you are using a Multilanguage Pack, you can copy just the files and folders for the languages that you want to install. When you are prompted to overwrite Setup files, click No. You must complete the following steps for each language that you want to install. 2. In the core product folder for the language pack that you are installing, locate the Config.xml file. For example, if you are installing the Russian language pack, find the Config.xml file in the OMUI.ru-ru folder. 3. Open Config.xml in a text editor, such as Notepad. 4. Find the <Display> element. Uncomment the line by deleting the opening <!-and closing --> tags. 5. Set the value of the Level to basic or none, CompletionNotice to yes, SuppressModal to yes, and AcceptEula to yes. The line should look like this: <Display Level="basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" /> 6. Find the <AddLanguage> element. Uncomment the line by deleting the opening <!-- and closing --> tags. 7. Set the value of the Id attribute to the language tag that corresponds to the language that you want to install. For example, to add the Russian language version, the line should look like this: <AddLanguage Id="ru-ru" /> 8. Save the Config.xml file. Run the language pack Setup from the root of the network installation point for the Multilanguage Pack or Single Language Pack (SLP), and specify the path of your modified Config.xml file on the command line. For example: \\server\share\Office12\SLP\Setup.exe /Config \\server\share\Office12\SLP\RU\OMUI.ru-ru\Config.xml where Office12\SLP is the root of the network installation point for the language packs and RU is the language folder name. 225

You must complete the previous steps for each language that you want to install. Language-specific elements for Microsoft Office Project 2007 and Microsoft Office Visio 2007 are installed separately. In each language pack, the core product folder for Office Project 2007 is PMUI.ll-cc. The core product folder for Office Visio 2007 is VisMUI.ll-cc. For information about how to create a network installation point with multiple languages, see Customize and deploy multiple language versions of the 2007 Office system. For a complete list of language tags, see Language identifiers in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179219.aspx). To deploy these languages for new 2007 Office system installations, see Specify which languages to install and re-create any existing customization MSP files. A static list of the products contained in the installation source is built only during the initial creation of a customization patch. If you later add more languages to the installation source, the existing patch is not updated to reflect this change.

Remove language packs

The steps to remove language packs are similar to the deployment of language packs. Instead of using the <AddLanguage> tag, use the <RemoveLanguage> tag. You must complete the following steps for each language that you want to remove. Remove language packs 1. If the language was deployed with the Office product (not as a separate product), locate the Config.xml file in the core product folder for the product that you are updating. For example, if you are removing languages from an installation of Microsoft Office Standard 2007, find the Config.xml file in the Standard.WW folder. Otherwise, locate the Config.xml file in the core product folder for the language pack that you are removing. For example, if you are removing the Russian language pack, find the Config.xml file in the OMUI.ru-ru folder. 2. Open Config.xml in a text editor, such as Notepad. 3. Find the <Display> element. Uncomment the line by deleting the opening <!-and closing --> tags. 4. Set the value of the Level to basic or none, CompletionNotice to yes, SuppressModal to yes, and AcceptEula to yes. The line should look like this: <Display Level="basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" /> 5. Find the <AddLanguage> element. If it is in the file, comment out the line by adding opening <!-- and closing --> tags around the element. The line should look like this: 226

<!-- <AddLanguage Id="ru-ru" /> --> 6. Add the <RemoveLanguage> element. 7. Set the value of the Id attribute to the language tag that corresponds to the language that you want to remove. For example, to remove the Russian language version, the line should look like this: <RemoveLanguage Id="ru-ru" /> 8. Save the Config.xml file. 9. If you edited the Config.xml file in the core product folder, run Setup.exe and specify the path of your modified Config.xml file. You must use a fully qualified path. For example: \\server\share\Office12\Setup.exe /Config\\server\share\Office12\Standard.WW\Config.xml where Office12 is the root of the network installation point. Otherwise, run the language pack Setup from the root of the network installation point for the Multilanguage Pack or Single Language Pack (SLP), and specify the path of your modified Config.xml file on the command line. For example: \\server\share\Office12\SLP\Setup.exe /Config \\server\share\Office12\SLP\RU\OMUI.ru-ru\Config.xml where Office12\SLP is the root of the network installation point for the language packs and RU is the language folder name. You must complete the previous steps for each language that you want to remove.

Identify installed languages

You can view a list of languages installed for the 2007 Office system either during the initial installation or during a separate installation of a language pack at the following registry key, which displays the LCID for each enabled language: HKCU\Software\Microsoft\Office\12.0\Common\LanguageResources\EnabledLanguages You can view the user interface (UI) language and fallback languages at the following registry key: HKCU\Software\Microsoft\Office\12.0\Common\LanguageResources Although all applications in the 2007 Office system use a shared set of registry data to determine their UI language, they do not necessarily all appear in the same UI language. Applications in the 2007 Office system usually appear with the UI language indicated in the UILanguage value of this registry key, but there are circumstances where this might not be the case. For example, some deployments might have Microsoft Office Word 2007 and Microsoft Office Excel 2007 installed in French, but another Office application installed in a different language. In this case, the other application will look at the UIFallback list in this registry key, and use the first language that works with its installed configuration.

227

See Also Customize and deploy multiple language versions of the 2007 Office system

228

IV Using enterprise deployment tools

229

Use Group Policy to assign computer startup scripts for 2007 Office deployment
Administrators can use Group Policy to assign computer startup scripts to deploy the 2007 Microsoft Office system. A script can be written in any language that is supported by the client computer. Windows Script Host-supported languages, such as VBScript and Jscript, and command files are the most common.

Group Policy Scripts Extension Overview

The Group Policy infrastructure includes a Scripts extension that consists of the following components: A Microsoft Management Console (MMC) server-side extension of the Group Policy Object Editor MMC snap-in that is used for administering and configuring scripts. The administrator uses the scripts extension to specify scripts policy settings in a Group Policy object (GPO), and then links the GPO to the site, domain, or organizational unit to which the administrator wants to assign the scripts. The Group Policy Object Editor snap-in includes two extensions for script deployment: Scripts (Startup/Shutdown). Administrators use this extension to specify scripts that run when the computer starts up or shuts down. These scripts run as Local System. Scripts (Startup/Shutdown) is located under the Computer Configuration\Windows Settings node of Group Policy Object Editor. Scripts (Logon/Logoff). Administrators use this extension to specify scripts that run when the user logs on or logs off the computer. These scripts run as User, not as Administrator. Scripts (Logon/Logoff) is located under the User Configuration\Windows Settings node of Group Policy Object Editor. A client-side extension, which is a dynamic-link library (DLL) on the client computer that interacts with the Group Policy infrastructure and implements Group Policy scripts on the client computer. A separate process called Userinit.exe runs the scripts. For more information about Group Policy Scripts extensions, see the Scripts Extension Technical Reference (http://go.microsoft.com/fwlink/?LinkId=83122) of the Windows Server 2003 Group Policy Technical Reference on the Microsoft TechNet Web site. For information about Windows Script Host, see Windows Script Host (http://go.microsoft.com/fwlink/?LinkId=83247) on the MSDN Web site.

Advantages of using computer startup scripts for deploying 2007 Office

If you have already deployed Active Directory and Group Policy in your organization, using computer startup scripts to deploy the 2007 Office system provides the following benefits: 230

Scripts or batch files for Office 2007 client deployment are relatively simple to create.

Administrators can use a command line to point to their Office Setup customization file (.MSP file) for advanced feature and settings customization. Setup customization files are created when administrators use the Office Customization Tool (OCT) to customize an installation of the 2007 Microsoft Office system. For more information about .MSP files, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). Administrators can use a command line to point to the Config.xml file for adding languages and other customizations. Modifying the Config.xml file is one of the ways in which administrators can make changes to the 2007 Office system installation. For more information about Config.xml files, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx), and the Applying customizations to the Office installation and Modifying the Config.xml File OptionState element sections in Use Group Policy Software Installation to deploy the 2007 Office system. The source files for product installation can be stored on a network share or on each local computer, if the bits are pre-staged. The product installation occurs in the system context, before the users log on. Active Directory handles the elevation of privileges required for application installation. Users can add or remove product features by using Add or Remove Programs in Control Panel. Administrators can use a similar scripting process to apply security updates and service packs for each computer in the domain or organizational unit. Microsoft Windows Server Update Services 3.0 (WSUS 3.0) can be used to manage and deliver product updates. For information about WSUS, see Microsoft Windows Server Update Services 3.0 Overview (http://go.microsoft.com/fwlink/?LinkId=82773) and Step-by-Step Guide to Getting Started with Microsoft Windows Server Update Services 3.0 (http://go.microsoft.com/fwlink/?LinkId=82774) on the Microsoft TechNet Web site. Be sure to consider the following issues if you use computer startup scripts as a deployment method for 2007 Office: The product installation is not managed in the same way as Group Policy Software Installation. Group Policy invokes the script and has limited awareness of the installation state thereafter. If the GPO that contains the script is removed (goes out of scope), Office is not removed. Deploying with scripts requires basic knowledge of valid command-line options for Setup.exe in 2007 Office applications. For information about command-line options, see Setup command-line options for the 2007 Office system (http://technet.microsoft.com/enus/library/cc178956.aspx). Product uninstalls and reinstalls for multiple computers have to be done by using a command line script or batch file.

231

 Automatic product reinstall after a user-initiated uninstall does not work in the same way as when Group Policy Software Installation is used. With Group Policy Software Installation, if a user removes a user-assigned application by using Add or Remove Programs in Control Panel, the Group Policy Software installation extension automatically reapplies the advertisement information after the user logs on or the computer restarts. The software is reinstalled the next time the user selects it or tries to open a file with an associated file name extension. Determining exactly which updates and service packs were applied for each client computer may be difficult. Important Group Policy provides the ability to affect configurations across hundreds and even thousands of computers in an organization. Therefore, it is critical that you rigorously test all new Group Policy configurations or deployments in a non-production environment before you move them into your production environment. For detailed information about staging Group Policy deployments, see Staging Group Policy Deployments (http://technet2.microsoft.com/WindowsServer/en/library/e5288e42-62b8-4f9e-a66595b6e02389a31033.mspx) in the Designing a Managed Environment book of the Microsoft Windows Server 2003 Deployment Kit. By default, the system lets combined sets of scripts run for up to 600 seconds (10 minutes) only. Administrators can use a policy setting to adjust this interval to ensure the startup script completes running. The Maximum wait time for Group Policy scripts policy setting specifies how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, startup, and shutdown scripts applied by Group Policy to finish running. As with any Group Policy deployment, you must fully test your startup scripts in a staging environment before deploying them to your production environment. Testing will help you determine the value to use for the Maximum wait time for Group Policy scripts policy for your particular network environment. Setting this value too low may cause the install to terminate prematurely. There are factors that may affect this value, such as network speed, client computer hardware, and other scripts running on the client computer. By fully testing this policy setting you can determine the appropriate value to use for your specific environment. The Maximum wait time for Group Policy scripts policy setting is available in the Computer Configuration\Administrative Templates\System\Scripts folder in Group Policy Object Editor. For information about configuring this policy setting, see Specifying maximum time for startup scripts to run.

Assigning computer startup scripts

Startup scripts run as Local System and have the full rights required to run as Local System. Notes The following procedures assume you have already installed GPMC. You can download GPMC from the Microsoft Download Center site. See Download Group Policy 232

Management Console (GPMC) (http://go.microsoft.com/fwlink/?LinkId=58541) for more information. If you are using Windows Vista, GPMC is integrated into the operating system. For more information and procedures for using GPMC and working with GPOs, see Group Policy Management Tools (http://technet.microsoft.com/enus/library/cc179081.aspx#GPManagementTools) and Using Group Policy Management Console and Group Policy Object Editor (http://technet.microsoft.com/enus/library/cc179081.aspx#Using_GP_snapin) sections in Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179081.aspx). You must be logged on as a member of the Domain Administrators security group, the Enterprise Administrators security group, or the Group Policy Creator Owners security group to complete these procedures. The following sections provide a sample script and instructions for customizing Config.xml install options and deploying computer startup scripts. The following sample script illustrates how to perform the following tasks: Run Microsoft Office Setup.exe if the product is not already installed Log error or success to a centralized log file

This script example provides flexibility and can be customized for other Office products. The following requirements apply to the sample script: The target computer must be running Windows XP, Windows Server 2003, Windows Vista, or Windows Server 2008. Microsoft Windows Installer (MSI) 3.1 is required if you use a customization patch A Read-only network share containing the Office source files A Read-write network share for storing centralized log files

A custom Config.xml file or customization patch to direct Setup.exe to run quietly. For instructions for modifying the Display element in the Config.xml file, see Specifying Silent Install Options in Config.xml File, and Display Element (http://technet.microsoft.com/enus/library/cc179195.aspx#ElementDisplay) in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

Example
setlocal REM ********************************************************************* REM Environment customization begins here. Modify variables below.

233

REM ********************************************************************* REM Get ProductName from the Office product's core Setup.xml file. set ProductName=Enterprise REM Set DeployServer to a network-accessible location containing the Office source files. set DeployServer=\\server\share\Office12 REM Set ConfigFile to the configuration file to be used for deployment REM (required) set ConfigFile=\\server\share\Office12\Enterprise.WW\config.xml REM Set LogLocation to a central directory to collect log files. set LogLocation=\\server\share\Office12Logs REM ********************************************************************* REM Deployment code begins here. Do not modify anything below this line. REM ********************************************************************* IF NOT "%ProgramFiles(x86)%"=="" SET WOW6432NODE=WOW6432NODE\ reg query HKEY_LOCAL_MACHINE\SOFTWARE\%WOW6432NODE %Microsoft\Windows\CurrentVersion\Uninstall\%ProductName% if %errorlevel%==1 (goto DeployOffice) else (goto End) REM If 1 returned, the product was not found. Run setup here. :DeployOffice start /wait %DeployServer%\setup.exe /config %ConfigFile% echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

234

REM If 0 or other was returned, the product was found or another error occurred. Do nothing. :End Endlocal In this example, script logging information is written to computername.txt file. A return code of 0 in the log file indicates that the installation completed successfully. A return code of 3010 indicates that a reboot is required. For more information about other error codes for Windows Installer processes for Office products, see KB article 290158 (http://go.microsoft.com/fwlink/? LinkId=90981) on the Microsoft Knowledge Base Web site.

Specifying Silent Install Options in Config.xml File

To customize Config.xml to specify silent install options 1. Open the Config.xml file in a text editor tool, such as Notepad. 2. Locate the line that contains the Display element, as shown in the following example: <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> 3. Modify the Display element entry to specify silent install options. For example if you want to specify that no user interface or modal dialog boxes are displayed, use the following syntax: <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> 4. Save the Config.xml file in the same folder that contained this file before you edited it.

Deploying Computer Startup Scripts

To set up scripts on the domain controller Copy the script and dependent files to the Netlogon shared folder or another shared folder on the domain controller from which you want the script to run. Note: The target computer account needs Read permission to the Office source files location, and Read and Write permissions to the log file location. The log file can be stored on the local computer. To assign computer startup scripts 1. Click Start, click Control Panel, click Administrative Tools, and click Group Policy Management. 235

2. In the console tree, double-click Group Policy Objects in the forest and domain that contains the Group Policy object (GPO) that you want to edit. This is located in Forest name/Domains/Domain name/Group Policy Objects. 3. Right-click the GPO you want to use to assign scripts and click Edit. This opens the Group Policy Object Editor console. 4. In Group Policy Object Editor, in the console tree, click Scripts (Startup/Shutdown). This is located in the Computer Configuration\Windows Settings node. 5. In the details pane, double-click Startup. 6. In the Startup Properties dialog box, click Add. 7. In the Add a Script dialog box, do the following: In Script Name, type the path to the script, or click Browse to search for the script file in the Netlogon shared folder on the domain controller. In Script Parameters, type the parameters you want to use as you would type them on the command line. For example, if your script included parameters called //logo (display banner) and //I (interactive mode), type: //logo //I. 8. In the Startup Properties dialog box, specify the options you want to use. The following options are available: Startup Scripts for Group Policy object. Lists all the scripts that are currently assigned to the selected Group Policy object. If you assign multiple scripts, the scripts are processed in the order that you specify. To move a script up in the list, select the script and click Up. To move a script down in the list, select the script and click Down. Add. Opens the Add a Script dialog box, where you can specify additional scripts to use. Edit. Opens the Edit Script dialog box, where you can modify script information, such as name and parameters. Remove. Removes the selected script from the Startup Scripts list. Show Files. Displays the script files that are stored in the selected Group Policy object.

Specifying maximum time for startup scripts to run

To set the maximum time for startup scripts to run 1. Click Start, click Control Panel, click Administrative Tools, and click Group Policy Management. 2. In the console tree, double-click Group Policy Objects in the forest and domain that contains the Group Policy object (GPO) that you want to edit. This is located in Forest name/Domains/Domain name/Group Policy Objects. 3. Right-click the GPO you want to use to assign scripts and click Edit. This opens the Group Policy Object Editor console. 4. In Group Policy Object Editor, in the console tree, navigate to Computer Configuration\Administrative Templates\System\Scripts. 236

5. On the details pane (left side of the console), double-click the Maximum wait time for Group Policy scripts policy setting, click Enabled, enter the value you want to use in the Seconds scroll-down box, and then click OK. Important: Make sure you fully test startup scripts in a staging, non-production environment before you deploy them to your production environment.

See Also Group Policy Overview (http://technet.microsoft.com/en-us/library/cc179176.aspx) Planning for Group Policy (http://technet.microsoft.com/en-us/library/cc179077.aspx) Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179081.aspx) Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx)

237

Deploy the 2007 Office system by using System Center Essentials 2007
In this article: What this article includes Preparing to deploy the 2007 Office system by using System Center Essentials Deploying the 2007 Office system by using System Center Essentials

This article contains information about how to use Microsoft System Center Essentials 2007 to deploy the 2007 Microsoft Office system. System Center Essentials 2007 is a management solution that is designed for IT system administrators in medium-sized organizations that include up to 30 servers and 500 client computers. Administrators can use the System Center Essentials 2007 to help secure, update, monitor, and track their IT environment. With System Center Essentials, you can perform the following tasks: Use the inventory feature to collect and examine computer hardware and software inventory. Use the software deployment feature to centrally deploy software, track deployment progress, and troubleshoot problems. Use the update management feature to centrally manage updates, track installation progress, and troubleshoot problems. Use the rules and monitors in Management Packs Monitor to monitor the health of computers and network devices. Administrators can use System Center Essentials 2007 to deploy the 2007 Office system. For more information about System Center Essentials, see the following resources: To view a training video about how to deploy 2007 Office system, see Deploying Office 2007 with System Center Essentials 2007 (http://go.microsoft.com/fwlink/?linkid=72670). To learn about detailed hardware and software requirements for deploying System Center Essentials 2007, see System Requirements and Supported Platforms for System Center Essentials (http://go.microsoft.com/fwlink/?LinkId=105100). To learn about the topologies supported for System Center Essentials 2007 deployment, see Supported Deployment Topologies (http://go.microsoft.com/fwlink/?LinkId=105099).

What this article includes

This article contains an example of how to use System Center Essentials to create a package to deploy Microsoft Office Professional Plus 2007 and Microsoft Office Project Professional 2007. It provides information about how to use an Office Customization Tool (OCT) Setup customization file (.MSP) and a custom Config.xml file to customize the installation to include additional languages and chain an Office product. The OCT is part of the Setup program and is the 238

recommended tool for most customizations. The OCT saves your choices in a Setup customization MSP file. The Config.xml file is used to perform installation customizations. This article focuses only on deployment of the 2007 Microsoft Office system. System Center Essentials documentation is beyond the scope of this article. For more information about System Center Essentials, refer to the product documentation on the System Center Essentials 2007 TechCenter (http://go.microsoft.com/fwlink/?LinkId=105101).

Preparing to deploy the 2007 Office system by using System Center Essentials
This example assumes that the administrator has basic knowledge about System Center Essentials concepts, especially software deployment. To learn about installing and configuring System Center Essentials 2007, see System Center Essentials Deployment Planning and Installation (http://go.microsoft.com/fwlink/?LinkId=105093). To learn about all functions related to software deployment by using System Center Essentials, see Software Deployment in System Center Essentials (http://go.microsoft.com/fwlink/? LinkId=105094). In preparation for deploying the 2007 Office system by using System Center Essentials, you must complete the tasks described in these sections: System Center Essentials tasks you must complete before you deploy the 2007 Office system 2007 Office customization tasks you must complete before you deploy the 2007 Office system with System Center Essentials

System Center Essentials tasks you must complete before you deploy the 2007 Office system
This example also assumes that the administrator has already performed the following System Center Essentials tasks prior to 2007 Office system deployment: 1. Install System Center Essentials 2007. For more information, see How to Install the System Center Essentials Management Server (http://go.microsoft.com/fwlink/? LinkId=105095). 2. Create groups of computers to which you want to deploy the 2007 Office system. For more information, see How to Create a Computer Group in System Center Essentials (http://go.microsoft.com/fwlink/?LinkId=105096). 3. Install System Center Essentials 2007 Agent on the managed computers. System Center Essentials installs agents automatically during the process of computer discovery. For cases in which a computer is not discoverable, administrators can manually install an agent to manage a specific computer. For more information, see How to Configure a Manually Installed System Center Essentials Agent (http://go.microsoft.com/fwlink/?LinkId=105097).

239

2007 Office customization tasks you must complete before you deploy the 2007 Office system by using System Center Essentials
Before using System Center Essentials to deploy the 2007 Office system, you must perform the following tasks to customize your deployment for a multiple language installation and to configure the installation for users. 1. Create a network installation point for your primary 2007 Office system product. For instructions, see the "To create a network installation point" section of Create a network installation point for the 2007 Office system. 2. Specify the languages to install and any feature and settings customizations that you want to apply. For instructions, see Customize and deploy multiple language versions of the 2007 Office system. Important: Make sure that you copy all the files and folders from the source media for each language pack that you want to install to the same network installation point created in the previous step. For example, copy all the source files to \\server\share\Office12. You use the Office Customization Tool (OCT) to customize an installation of the 2007 Office system and create a new Office setup customization MSP file. You run the OCT by running Setup.exe with the /admin switch from the root of the network installation point; for example, type setup.exe /admin on the command line. After you complete all the customizations that you want to deploy to users, save the MSP file to the Updates folder. This is the recommended location for setup customization MSP files. When Setup runs, it searches the Updates folder on the installation point for a customization file specific to the product that is being installed. If you do not put the customization file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully qualified path of the folder in which you store the custom MSP file. In such cases, you would type the following on the Specify Installation Parameters screen of the New Software Package Wizard in System Center Essentials console: /adminfile \\server\share\myNewUpdatesFolder. For more information, see Deploying the 2007 Office system with System Center Essentials. For more information about the areas that you can customize by using the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx), and Customize the 2007 Office system. To customize the Config.xml file to add languages (or set feature installation states or other customizations), you edit the copy of Config.xml located in the product folder in the network installation point. For example, the product folder for Microsoft Office Professional 2007 is Pro.WW. For more information about the Config.xml file, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). To configure a silent installation of a 2007 Office system product that requires no user interaction, prevents prompting users to enter information, and prevents the installation from

240

waiting for any user interaction, modify the Config.xml file for the product that you are installing as follows. a. Open the Config.xml file for the Office product that you are installing by using a text editor tool such as Notepad. Locate the line that contains the Display element: <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> b. Modify the Display element entry with the following silent options: <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> c. Save the Config.xml file. For more information, see Configure a silent installation of the 2007 Office system by using Config.xml. As with any software deployment, you must confirm your Office customizations in a test environment before you deploy them to users in your organization.

Deploying the 2007 Office system by using System Center Essentials

After you configure your Office customizations, you can create a package to deploy the 2007 Office system by using System Center Essentials. This section provides information about the installation schedule of an approved update and about how to create and deploying a package. Important: You must enable Automatic Updates on the managed computers to enable System Center Essentials to deploy software to the managed computers. To view the status of Automatic Updates on the target computers, open Automatic Updates in Control Panel. You can configure the installation as mandatory (that is, not as published). In this scenario, the installation time depends on how Automatic Updates is configured on the user's computer: If Automatic Updates is configured to automatically download and install at a specific time, the software is installed at that time unless the user has already manually installed it. If Automatic Updates is configured for automatic download and manual installation, the user can install the software at any time. If Automatic Updates is configured to notify users about updates, the software is installed immediately upon the user's approval of the notification message. You can also configure a package as optional by selecting the Publish program(s) to 'Add/Remove Programs' option in the Approve Groups for Deployment screen of the New Software Package Wizard when you create the package (in step 9 in the following procedure). In this case, the software is added to Add or Remove Programs in Control Panel on the managed computer, and the user can install it at any time. A notification icon is displayed in the computer's notification area when the new software becomes available.

241

Note: Users must have administrative credentials on their computers to install applications from Add or Remove Programs in Control Panel. The System Center Essentials Agent on approved managed computers checks for new software deployments every 22 hours. After the administrator approves software for deployment, the next time that the agent runs, it detects that new software is available. The agent determines when the software needs to be installed and displays a notification icon in the computer's notification area. Deploy 2007 Office by using System Center Essentials 1. In the System Center Essentials console, click Software. 2. In the Results pane, in the Actions area, click Create and deploy a new software package to start the New Software Package Wizard. 3. Browse to the network installation point that contains the 2007 Office setup files, choose Setup.exe, and select the Include all files and sub-folders in this location option. 4. Enter Office 2007 as the name of the software package, and specify the description that you want to display to users when the product is being installed. 5. On the Specify Installation Parameters screen, specify the following command to reference your customized Config.xml file: /config \\server\share\Pro.WW\config.xml Notes If you placed the custom MSP file in a location other than the Updates folder, you would use the following command to reference the location of the folder that contains the MSP files: /adminfile \\server\share\myNewUpdatesFolder /config \\server\share\Pro.WW\config.xml 6. Click Next to view a summary and confirm the package name and the command-line parameters that you have specified. 7. Click Next to create the software package. Note that because the Office package is large (greater than 450 MB), it might take up to two hours to complete the packaging and signing process. 8. After the package is created, select the Show deployment options when this wizard closes option, and then click Finish. 9. In the Approve Groups for Deployment dialog box, select the computer groups on which you want to install the Office products, and then click OK. The package is downloaded to target computers within 24 hours. To install an additional application, you can repeat the previous procedure to create and deploy a new package. You must instruct users to install the Office package on their computers if you deployed the package as published through Add or Remove Programs in Control Panel (that is, if you used the Publish program(s) to 'Add/Remove Programs' option in the Approve Groups for 242

Deployment screen), or if Automatic Updates is configured for automatic download and manual install.

See Also Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx) Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx) Setup command-line options for the 2007 Office system (http://technet.microsoft.com/enus/library/cc178956.aspx)

243

Deploy the 2007 Office system by using System Center Configuration Manager 2007
In this article: Overview Introduction to the deployment process Deploying the 2007 Office system in a test environment Resources for deploying the infrastructure

This article provides detailed technical guidance on the processes and procedures when using Microsoft System Center Configuration Manager 2007 to deploy the 2007 Microsoft Office system in a medium to large enterprise corporate environment.

Overview
System Center Configuration Manager 2007 is the solution to comprehensively assess, deploy, and update your servers, clients, and devices across physical, virtual, distributed, and mobile environments. This article provides detailed technical guidance for specifically deploying the 2007 Office system. Although this article illustrates the test network environment used for helping to describe the process of deploying the 2007 Office system by using Configuration Manager 2007, it does not provide information about how to set up the test network infrastructure, such as the Active Directory directory service, Microsoft SQL Server, and System Center Configuration Manager. However, it does provide links for setting up a similar network infrastructure. This information is located in the last section of this article, Resources for deploying the infrastructure.

Audience
The target audience for this article is IT professionals. These IT professionals could include network managers, consultants, and IT managers who work for or with medium to large enterprises.

Prerequisites
Prior knowledge and experience will help users understand and apply the information in this article, particularly experience in the following areas: Microsoft Systems Management Server (SMS) 2003 or System Center Configuration Manager 2007 244 Office Customization Tool (OCT)

2007 Office system, Microsoft Office 2003, or Microsoft Office XP

Introduction to the deployment process

Once you have your supporting infrastructure in place for Configuration Manager 2007, the process for deploying the 2007 Office system involves creating and defining five primary areas: Collections Packages Programs Distribution points Advertisements

Collections Collections are groups of Configuration Manager 2007 resources, such as users, user groups, or computers, against which a software deployment is targeted. For more information about collections, see Collections Overview (http://go.microsoft.com/fwlink/? LinkId=145870). Packages A package is the set of installation source files that Configuration Manager 2007 manages and distributes for software deployment. Some of the information included within the package is the distribution points and programs. For more information about packages, see About Packages (http://go.microsoft.com/fwlink/?LinkId=145871). Programs Programs are part of the package configuration in Configuration Manager 2007. They contain any command-line switches and additional parameters to be run from the designated package source files, such as Setup.exe. For more information about programs, see About Programs (http://go.microsoft.com/fwlink/?LinkId=145872). Distribution points Distribution points are Configuration Manager 2007 site systems that store designated packages for deployment to Configuration Manager 2007 clients. When the Configuration Manager 2007 client receives and processes a relevant advertisement, the client then contacts a distribution point to download the package and start the installation process. For more information about distribution points, see About Distribution Points (http://go.microsoft.com/fwlink/?LinkId=145873). Advertisements Advertisements tie packages and programs together with collections, enabling administrators to target software deployment of specific or customized applications to collections of computers or users. An advertisement specifies a package and program, and the collection to which it will be advertised or deployed. For more information about advertisements, see About Advertisements (http://go.microsoft.com/fwlink/?LinkId=145875).

Deploying the 2007 Office system in a test environment

This section provides a diagram and description of the test network environment for the Configuration Manager 2007 infrastructure. It also includes procedural information of the steps for deploying Microsoft Office Enterprise 2007 by using Configuration Manager 2007. 245

Network environment
The test network environment for this article is shown in the following illustration. Test network environment

All of the servers (A, B, and C) are running Windows Server 2008 and are members of the same domain (CPANDL.COM), including the client computers (D), which are running Windows Vista Enterprise. The applications and roles that each server is running, and the fully qualified domain name (FQDN) for each client computer, are listed as follows: A - Active Directory, DNS, DHCP <DC.CPANDL.COM> B - Microsoft SQL Server 2008<SQLSRV.CPANDL.COM> C - System Center Configuration Manager 2007 R2 (management point, distribution point) <SCCM.CPANDL.COM> D - Windows Vista Enterprise, System Center Configuration Manager 2007 client <WVC01.CPANDL.COM> Although in this simple test network environment the site server is performing multiple site system roles (such as management point and distribution point) simultaneously, this configuration is not recommended for production sites that have large numbers of resources.

Procedural steps for deploying the 2007 Office system by using Configuration Manager 2007
In this example, deployment scenario detailed information is provided for deploying Office Enterprise 2007 in the previously defined Configuration Manager 2007 test environment. By following these steps, you can use Configuration Manager 2007 to deploy a silent installation of the 2007 Office system, where the users do not interact with the installation process. Note: In a production environment to minimize the load on your network, you can use Configuration Manager 2007 to deploy (precache) the local installation source of the 2007 Office system separately, before you deploy Office. Precaching allows most of the installation activity to occur on the local computer instead of over the network. Precaching also allows you to coordinate the upgrade to the new version. You can distribute the local 246

installation source to groups of users over time and then schedule a simultaneous installation throughout the organization without over-taxing the network. For more information, see Precache the local installation source for the 2007 Office system. In this example, the first step is to create a customization file for the silent installation of the 2007 Office system. Create a Setup customization file for the 2007 Office system In the 2007 Office system, Setup controls the entire installation, including processes that Windows Installer handled in previous Office versions. Customizing the default behavior of Setup allows you to control the process. In this example, you customize the installation for a silent installation of the 2007 Office system. The Office Customization Tool (OCT) is used to create a Setup customization file (MSP file). Setup applies this file when Office is installed on the computers. Note: It is also possible to use the Config.xml file to configure a silent installation of the 2007 Office system. For more information about how to use Config.xml, see Configure a silent installation of the 2007 Office system by using Config.xml. 1. To customize Office Setup, use the command line setup.exe /admin to start the Office Customization Tool. In this example (using Configuration Manager 2007 to deploy the 2007 Office system), at a command prompt, run setup.exe /admin from the package source directory, \\SCCM\Office2007\Enterprise. 2. To ensure that the 2007 Office system is silently installed, modify and configure the settings as follows: a. On the Licensing and user interface dialog box, set the Display Level to None, which will then enable the Suppress modal check box. b. Verify that the Completion notice and No Cancel options are not selected. c. Enter a valid 25-character volume license key in the Product Key box located under Licensing and user interface. d. Select the I accept the terms in the License Agreement check box. 3. Save and name the newly created MSP file, and place it in the \Updates folder for the 2007 Office system on the computer that contains the package source directory, which in this example is \\SCCM\Office2007\Enterprise\Updates\CustomFileOffice2007SilentInstall.MSP. Caution: During the initial installation of the 2007 Office system, if you apply updates in addition to the Setup customization file (MSP file) created by using the Office Customization Tool (OCT), you need to ensure that the Setup customization file is the update applied at the beginning of the installation. This is because only one update is applied at the beginning of the installation. All remaining updates in the Updates folder are installed at the end of the installation. To specify the Setup customization file as the update applied at the beginning of the installation, you need to rename the file to ensure it is applied first according to Windows sort order. In this example, you would rename the file 247

CustomFileOffice2007SilentInstall.MSP to 1_CustomFileOffice2007SilentInstall.MSP. For additional information about how to deploy updates during an initial installation of the 2007 Office system, see Distribute product updates for the 2007 Office system. For additional information about how to customize the default behavior of Setup for the 2007 Office system, see Customize Setup before installing the 2007 Office system. Create a collection This section provides the details for using direct membership rules to create a collection in Configuration Manager 2007. This allows for selecting the computer resources of the targeted computers. For more information about the membership rules, including both query and direct, see About Membership Rules (http://go.microsoft.com/fwlink/?LinkId=145884). 1. To create a collection, in the Configuration Manager Console, navigate to System Center Configuration Manager / Site Database / Computer Management / Collections. 2. Right-click Collections, and then click New Collection. On the General dialog box of the New Collection Wizard, enter a name for the collection. In this example, it is named TargetComputers. 3. On the Membership Rules dialog box, click the computer icon, which opens the Create Direct Membership Rule Wizard. Click Next. 4. On the Search for Resources dialog box, click the Resource class drop-down menu and select System Resource. Then, click the Attribute name drop-down menu and select Name. In the Value field enter %, and then click Next. 5. On the Collection Limiting dialog box, click the Browse button, select All Windows Workstation or Professional Systems, click OK, and then click Next. 6. On the Select Resources dialog box, select the check box for each of the targeted computer resources. In this example, TestComputer01 and TestComputer02 were selected. Click Next, and then on the Finished dialog box, click Finish. On the Membership Rules dialog box of the New Collection Wizard, click Next. 7. On the Advertisements dialog box, for now, do not assign an advertisement because it is not yet created. Click Next. On the Security dialog box, accept the defaults, click Next, and then click Close. The next step is to prepare the source directory for the package. For more information about collections, see Collections in Configuration Manager (http://go.microsoft.com/fwlink/?LinkId=145886). Prepare the package source directory The package source folder contains all the files and subdirectories needed to run the programs in a package. In this example, the source directory is \\SCCM\Office2007\Enterprise, which contains a copy of the Office Enterprise 2007 installation CD. Note: It is possible to reduce the size of the package file created by Configuration Manager 2007, by removing any additional files that are not needed (such as other programs within the Office suite that will not be deployed). 248

For information about multiple language deployments, see Customize and deploy multiple language versions of the 2007 Office system. For more information about package source directories, see How to Set Up a Package Source Directory (http://go.microsoft.com/fwlink/?LinkId=145890). Create a package for the 2007 Office system The next step is to create a package, which will contain the specified parameters for installing the program, in this case the 2007 Office system, and the location from where the package will be distributed, known as the distribution point, to the managed Configuration Manager 2007 clients. In this example, the steps are provided for creating a package manually. Once the package has been created, you will create a distribution point for the package and a program that contains the setup and installation parameters for the 2007 Office system. Note: Information for creating a package is included in this article to illustrate the process. Nevertheless, it is possible to import a package definition file such as one for the 2007 Office system, which is Office 2007 SMS package definition file (.sms) (http://go.microsoft.com/fwlink/?LinkId=145893). You can use these files to automatically create the package details. To do so, right-click Packages, click New, and then click Package From Definition. You can then browse to the folder that contains the package definition file and select the relevant .sms file. 1. To create a package, in the Configuration Manager Console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Distribution / Packages. 2. Right-click Packages, point to New, and then click Package. 3. On the General dialog box of the New Package Wizard, enter the Name, Version, Manufacturer, and Language. For example, Office, 2007, Microsoft, English (US). 4. On the Data Source dialog box, select This package contains source files. Click the Set button, and then enter the path for the location of the source files in the Source directory field. For this example, select the source directory location of the local drive, such as C:\Office2007\Enterprise, which contains a copy of the Office Enterprise 2007 installation CD. 5. Click OK, and then continue to click Next and accept the default settings on all of the following dialog boxes: Data Access, Distribution Settings, Reporting, and Security. On the Wizard Completed dialog box, click Close. The package, in this example named Microsoft Office 2007 English (US), is now created. The next step is to create a Configuration Manager 2007 program, which will contain the setup and install parameters for the 2007 Office system. Create a program with setup and install parameters for the 2007 Office system This example provides the steps to create a program for the deployment of a silent installation of the 2007 Office system, where the users do not interact with the installation process. 1. To create a program for the Office 2007 package, right-click Programs, point to New, and then click Program. 249

2. On the General dialog box, enter a name for the package in the Name field, which in this example is named Office 2007 silent installation. In the Command line field, in this example type setup.exe. Because the customization file, CustomFileOffice2007SilentInstall.MSP, was placed in the \Updates folder, a command line option is not needed to reference its location. For more information, see Setup command-line options for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc178956.aspx). In the Run field, click the dropdown menu and select Hidden. In the After running field, verify the default of No action required is selected. Click Next and accept the defaults on the Requirements dialog box. 3. On the Environment dialog box, click the Program can run drop-down box and select Whether or not a user is logged on. This will enable Run with administrative rights for the Run mode. Leave the default for Drive mode to Runs with UNC name, and then click Next. 4. On the Advanced dialog box, select the Suppress program notifications check box, and then click Next. Note: If you want users to be aware of the installation by way of a notification on their desktop computer, do not select Suppress program notifications. 5. On the Windows Installer dialog box, click Import and browse to the directory that contains the EnterpriseWW.msi file, which in this example is \\SCCM\Office2007\Enterprise\Enterprise.WW\EnterpriseWW.msi. After selecting the MSI file, the Windows Installer product code and Windows Installer file fields are populated with the corresponding information associated with the selected MSI file. Click Next and accept the default values on the MOM Maintenance Mode dialog box. 6. To view the Summary dialog box, click Next. To finish the process of creating the new program, click Next, which will then display the Wizard Completed dialog box. To exit from the New Program Wizard, click Close. You will now select a distribution point for the package. Select a distribution point To use a server as a distribution point for providing packages to distribute packages to your client computers, you must first designate a site system as a distribution point. In this example, the single site server, named SCCM, was initially configured as both a management point and a distribution point. 1. To select a distribution point for the newly created package Microsoft Office 2007 English (US), right-click Distribution Points, click New Distribution Points, click Next, and then click the check box for the distribution point (in this example, SCCM). Click Next. 2. Upon completion of the New Distribution Points Wizard, click Close. The next step is to advertise the package, Microsoft Office 2007 English (US), which now contains both the Configuration Manager 2007 distribution point and program information for deploying a silent installation of the 2007 Office system. Before advertising the package, first verify that it was installed on the distribution point. 250

For more information about how to verify the status of a package, see How to View the Status of a Package (http://go.microsoft.com/fwlink/?LinkId=145898). Create an advertisement of the 2007 Office system package This example provides the steps to create an advertisement of the 2007 Office system package. 1. To create an advertisement, right-click Advertisements, point to New, and then click Advertisement. On the General dialog box of the New Advertisement Wizard, in Name field, enter Office 2007. Click the Browse button for the Package field, and click on the package that you want to advertise, which in this example is Microsoft Office 2007 English (US), and then click OK. Click the Browse button for the Collection field, click on the collection, which in this example is Target-Computers, click OK, and then click Next. 2. On the Schedule dialog box, enter the date and time in the Advertisement start time fields for when the advertisement will be available, and then click the asterisk button for Mandatory Assignments. 3. On the Assignment Schedule dialog box, click the Schedule button and enter the same date and time that you previously entered in the Advertisement start time fields on the Schedule dialog box. To return to the Schedule dialog box, click OK. 4. On the Schedule dialog box, select the check boxes for Enable Wake On LAN, Ignore maintenance windows when running program, and Allow system restart outside maintenance windows, and then click Next. Note: In your production environment, there might be policies in place that would require different selections than previously listed for the assignment schedule. For information about these options, see Advertisement Name Properties: Schedule Tab (http://go.microsoft.com/fwlink/?LinkId=145900). 5. Accept the default values on the Distribution Points, Interaction, Security, and Summary dialog boxes. Upon successful completion of the New Advertisement Wizard, click Close on the Wizard Completed dialog box. The package will now be advertised to the targeted collection and the silent installation of the 2007 Office system will begin. For information about how to monitor the status of the advertisement, see How to View the Status of an Advertisement (http://go.microsoft.com/fwlink/?LinkId=145901). For information about Office system installation error codes, see Error codes for 2007 Office system installations (http://technet.microsoft.com/en-us/library/dd347468.aspx).

Resources for deploying the infrastructure

This section includes resources to help you understand and configure an infrastructure to test the deployment of the 2007 Office system by using Configuration Manager 2007.

251

Active Directory, DNS, DHCP

Active Directory Domain Services for Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=145922) Windows Server 2008 Step-by-Step Guide for DNS in Small Networks (http://go.microsoft.com/fwlink/?LinkId=145925) DNS Server (http://go.microsoft.com/fwlink/?LinkId=145928) DHCP Server (http://go.microsoft.com/fwlink/?LinkId=145931)

SQL Server 2008

Installing SQL Server 2008 (SQL Server Video) (http://go.microsoft.com/fwlink/? LinkId=145934) SQL Server 2008 Security Overview for Database Administrators (http://go.microsoft.com/fwlink/?LinkId=145936)

System Center Configuration Manager 2007 R2 (Management Point, Distribution Point)

System Center Configuration Manager (SCCM) 2007 POC Installation Guidelines (http://go.microsoft.com/fwlink/?LinkId=145938) Configuration Manager Single Site Planning and Deployment (http://go.microsoft.com/fwlink/?LinkId=145939)

Windows Vista Enterprise, System Center Configuration Manager client

Planning and Deploying Clients for Configuration Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=145941) Setup reference for the 2007 Office system (http://technet.microsoft.com/enus/library/cc179099.aspx) How to obtain a volume license key for enterprise editions of Office 2007 and Office 2003 (http://go.microsoft.com/fwlink/?LinkId=145948)

252

Using Systems Management Server 2003 to deploy the 2007 Office system
Microsoft Systems Management Server (SMS) 2003 is a remote management tool that enables system administrators to deploy desktops, servers, and devices in medium and large organizations. When combined with the new deployment tools in the 2007 Microsoft Office system, SMS 2003 provides a flexible solution for deploying and managing Office 2007 applications in network environments. Compared to other deployment tools, such as Group Policy Software Installation, SMS provides one of the most flexible means to deploy software on a network. By using SMS, system administrators can target specific users or systems, elevate user rights for installation, specify when an installation can take place, specify user interaction levels, control restarts, and more. You can use SMS 2003 to deploy new versions of the 2007 Office system to users or computers within an organization on a specific basisfor example, initially to a pilot group, and then later to more departments and general users. It is also possible to customize those installations to coexist with previous versions of Microsoft Office. In addition, the Background Intelligent Transfer Service (BITS) within SMS 2003 can significantly reduce the demands on network bandwidth when you install the 2007 Office system. BITS uses spare network capacity to transfer SMS packages to client computers, which the client computers then cache locally for later installation. To learn more about using SMS 2003 to deploy the 2007 Office system, see Deploying the 2007 Microsoft Office System with Microsoft Systems Management Server 2003 R2 (http://go.microsoft.com/fwlink/?LinkId=78542&clcid=0x409) and Deploying the 2007 Office System at Microsoft (http://go.microsoft.com/fwlink/?LinkId=86626&clcid=0x409).

253

Use Group Policy Software Installation to deploy the 2007 Office system
If you are an IT professional and use TechNet or the Office Resource Kit, take a look at our Online Survey (http://go.microsoft.com/fwlink/?LinkId=132189). Let us know how we can best meet your documentation needs. You can read more about our work to improve documentation on the Office Resource Kit Blog (http://go.microsoft.com/fwlink/?LinkID=125627&clcid=0x409). If you use Active Directory in your organization, you can use Group Policy Software Installation with the 2007 Microsoft Office system to assign products to all computers in a group.

Overview of Group Policy Software Installation

Group Policy Software Installation is an extension of the Group Policy Object Editor Microsoft Management Console (MMC) snap-in that administrators can use to manage software. Administrators can assign applications to users or computers, or publish applications for users. Administrators can assign software on a per-user or per-computer basis when an organization does not want to give users the choice to install or remove the software. For example, if a user removes a user-assigned application by using Add or Remove Programs in Control Panel, the Group Policy Software installation extension automatically reapplies the advertisement information after the user logs on or the computer restarts. The software is reinstalled the next time a user selects it or tries to open a file with an associated file name extension. It is not possible for a user to delete a computer-assigned application. In most cases, packages that are assigned to users or computers include applications that are essential, but that do not create network congestion between clients and the software distribution points. Group Policy-based software deployment also enables administrators to publish software for users only. When this method is used, users can install the software from a list of published applications in Add or Remove Programs in Control Panel.

Deploying 2007 Office with Group Policy Software Installation

You can use the Software Installation extension of Group Policy to deploy the 2007 Office system to computers if the following conditions exist: Small organizations that have already deployed and configured Active Directory Organizations or departments that comprise a single geographic area

Organizations with consistent hardware and software configurations on both clients and servers For more information about Group Policy Software Installation, see Group Policy Software Installation (http://go.microsoft.com/fwlink/?LinkId=82911) and Group Policy Software Installation 254

Extension Technical Reference (http://go.microsoft.com/fwlink/?LinkId=82913) on the Microsoft TechNet Web site.

Deployment considerations
Although administrators can use Group Policy Software Installation to deploy the 2007 Office system to computers in small organizations, there are limitations to using this approach. It is important to carefully consider these issues as you determine the deployment method that best meets your deployment requirements. These limitations include: Difficulties with scheduling installation, consistently managing network bandwidth, and providing feedback on the status of the installation. If your organization needs to provide these capabilities, consider using Microsoft Systems Management Server 2003 R2. For more information, see Deploying the 2007 Microsoft Office System with Microsoft Systems Management Server 2003 R2 (http://go.microsoft.com/fwlink/?LinkId=78542&clcid=0x409). Limited scalability. Some difficulties might occur during Group Policy Software Installation deployment of 2007 Office suites to more than 200 computers simultaneously; this depends largely on network bandwidth availability. Limited ability to customize features or user settings before installation of the 2007 Office system. Administrators cannot use a Setup customization file (.MSP) created with the Office Customization Tool (OCT) to apply customizations for initial deployment. These customizations must be made in the Config.xml file. Note: Not all of the customization provided in an .MSP file can be provided with a Config.xml file. Administrators may use a script to apply an .MSP file after initial deployment. Since the installation source cannot be modified, nor can an .MSP file be deployed, administrators must use an alternate method to update the clients for the 2007 Office system service packs or other updates. One possible approach is to use Microsoft Windows Server Update Services 3.0 (WSUS 3.0) for updates. For information about WSUS, see Microsoft Windows Server Update Services 3.0 Overview (http://go.microsoft.com/fwlink/?LinkId=82773) and Step-by-Step Guide to Getting Started with Microsoft Windows Server Update Services 3.0 (http://go.microsoft.com/fwlink/? LinkId=82774) on the Microsoft TechNet Web site. Group Policy Software Installation can only be used for per-computer installations for the 2007 Office system. Challenging to maintain, because updates must be applied to all client computers. This can be done by using a logon script or other delivery method. It is not possible to use the Updates folder to apply security updates or service packs for initial deployment of the Group Policy object (GPO). Important: If you manage large numbers of clients in a complex or rapidly changing environment, Microsoft Systems Management Server is the recommended method for installing and 255

maintaining the 2007 Office system in medium- and large-sized organizations. Microsoft Systems Management Server offers more sophisticated functionality, including inventory, scheduling, and reporting features. For information about using Microsoft Systems Management Server to deploy the 2007 Office system, see Using Systems Management Server 2003 to deploy the 2007 Office system. As an alternative to using Group Policy Software Installation, administrators can also use Group Policy to assign computer startup scripts to deploy the 2007 Office system. For more information, see Use Group Policy to assign computer startup scripts for 2007 Office deployment. In this topic Using Group Policy Software Installation Deploying new installations of Office Upgrading previous versions of Office How it works Applying customizations to the Office installation Modifying the Config.xml File OptionState element

Using Group Policy Software Installation

The following procedures use the Group Policy Object Editor MMC snap-in from the Group Policy Management Console to edit the GPO. The procedures assume you have already installed GPMC. You can download GPMC from the Microsoft Download Center site. See Download Group Policy Management Console (GPMC) (http://go.microsoft.com/fwlink/?LinkId=58541) for more information. If you are using Windows Vista, GPMC is integrated into the operating system. For more information and procedures for using these tools, see the Group Policy Management Tools and Using Group Policy Management Console and Group Policy Object Editor sections in Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179081.aspx). Notes The following procedures assume that you previously created a network installation point for the 2007 Office system on a network server. For more information, see Create a network installation point for the 2007 Office system. Ensure that the user permissions to the network installation point folder that contains the 2007 Office system source files and any customized files are as follows: Read, Read & Execute, and List Folder Contents. To complete the following procedures, you must log on as a member of the Domain Administrators security group, the Enterprise Administrators security group, or the Group Policy Creator Owners security group. To use Group Policy Software Installation, you must create a new GPO or edit an existing GPO for a site, domain, or organizational unit. You must then link the GPO to the site, domain, or organizational unit to which you want to deploy the 2007 Office system. You must fully test this deployment method in a test and staging environment before you deploy applications to computers in your production environment. For more information, see Staging 256

Group Policy Deployments (http://technet2.microsoft.com/WindowsServer/en/library/e5288e4262b8-4f9e-a665-95b6e02389a31033.mspx) in the Designing a Managed Environment book of the Windows Server 2003 Deployment Kit on the Microsoft TechNet Web site.

Deploying new installations of Office

If this is a new installation of the 2007 Office system, you can deploy Office by assigning it to computers within a GPO that is associated with a particular Active Directory container such as a domain or organizational unit. Computer-assigned applications are installed the next time the computer restarts. To deploy Office using Group Policy-based Software Installation 1. Open Group Policy Management console. Click Start, click Control Panel, click Administrative Tools, and then click Group Policy Management. 2. In the console tree, double-click Group Policy Objects in the forest and domain that contain the GPO that you want to edit. This is located in Forest name, Domains, Domain name, Group Policy Objects. 3. Right-click the GPO you want to modify and click Edit. This opens Group Policy Object Editor. 4. In the left pane in Group Policy Object Editor, expand the Computer Configuration tree. 5. In the left pane, expand Software Settings and select Software Installation. 6. Right-click in the right pane, point to New and click Package. 7. In the Open dialog box, browse to the network installation point you created and select the Windows Installer (MSI) file in the main product folder of the Office product that you are installing. For example, for Microsoft Office Enterprise 2007, select Enterprise.WW\EnterpriseWW.msi. 8. Click Open. 9. Select Assigned to use the default options, or select Advanced to customize these options. 10. Close all dialog boxes. Note: If you are deploying 2007 Office in languages other than U.S. English, you should also deploy the ShellUI.MST transform file. Transforms (.mst files) are customizations that are applied to Windows Installer packages (.msi files) at the time of application assignment or publication, not at the time of installation. The following procedure explains how to add the transform to application packages. With the exception of the ShellUI.MST file, transforms are not supported in Office 2007. For information about Office Setup, see Getting started with the 2007 Office system.

257

To add modification to application packages 1. Open Group Policy Software Installation. 2. In the console tree, right-click Software installation, point to New, and then click Package. 3. In the Open dialog box, click the Windows Installer package, and then click Open. 4. In the Deploy Software dialog box, click Advanced, and then click OK. 5. In the properties dialog box for the package, click the Modifications tab. 6. To add modifications, click Add. In the Open dialog box, browse to the transform file (.mst), and then click Open. 7. Click OK. Note: When you click OK, the package is assigned or published immediately. For more information about using Group Policy Software Installation, see Group Policy Software Installation (http://go.microsoft.com/fwlink/?LinkId=82911) on the Microsoft TechNet Web site.

Upgrading previous versions of Office

If you deployed a previous version of Office by assigning it to computers using Group Policybased Software Installation, you can upgrade those installations by editing the associated GPO. Note: The following procedure assumes that you deployed the previous version of Office by using Group Policy Software Installation to assign Office to computers. If you deployed Office by assigning or publishing the application to users, or if you used a deployment method other than Group Policy, the existing version of Office will not be upgraded if you use this procedure. Instead, the previous version of Office remains on the computer when the 2007 Office system is installed. To remove the previous version of Office you must uninstall Office. To upgrade Office using Group Policy-based Software Installation 1. Open Group Policy Management console. Click Start, click Control Panel, click Administrative Tools, and click Group Policy Management. 2. In the console tree, double-click Group Policy Objects in the forest and domain that contain the GPO that you want to edit. This is located in Forest name, Domains, Domain name, Group Policy Objects. 3. Right-click the GPO you want to modify and click Edit. This opens Group Policy Object Editor. 4. In the left pane of Group Policy Object Editor, expand the Computer Configuration tree. 5. In the left pane, expand Software Settings and select Software Installation. 258

6. Right-click in the right pane, point to New and click Package. 7. In the Open dialog box, browse to the network installation point you created and select the Windows Installer (MSI) file in the main product folder of the Office product that you are installing. For example, for Microsoft Office Enterprise 2007, select Enterprise.WW\EnterpriseWW.msi. 8. Click OK. 9. Select Assigned to use the default options, or select Advanced to customize these options. The Published option is disabled because you cannot publish Office to a user. 10. In the details pane, right-click the Windows Installer package that will function as the upgrade (not the package to be upgraded). 11. Click Properties and click the Upgrades tab. 12. Click Add to create or add to the list of packages that are to be upgraded by the current package. 13. Under Choose a package from, click Current Group Policy object (GPO) or A specific GPO as the source of the package to be upgraded. If you click A specific GPO, click Browse, and click the GPO that you want to use. 14. Click the package for the previous version of Office that you want to upgrade. 15. Click Uninstall the existing package, then install the upgrade package. 16. Close all dialog boxes.

How it works
The 2007 Office system consists of a number of MSI files. None of the files by itself represents the complete installation. However, you assign the 2007 Office system by assigning only the main product MSI file. The next time the computer starts, this MSI file is accessed and a Windows Installer Custom Action recognizes that Office is deploying with Group Policy. The additional Office MSI and support files are then retrieved from the network installation point and the complete product is installed. If a previous version of Office is being upgraded, that version of Office is uninstalled before the new installation of the 2007 Office system starts. Applications assigned to a computer are resilient. If an administrator removes an Office application from the computer, Windows reinstalls the application the next time the computer starts. Users can repair Office applications on the computer, but only an administrator can remove applications.

Applying customizations to the Office installation

Because of the way Setup runs when Office is installed, there are some limitations on the number of installation options that you can customize when you deploy the 2007 Office system with Group Policy-based Software Installation. The following limitations apply:

259

 All customizations must be made in the Config.xml file. Setup does not apply Setup customization files that you create using the OCT. For more information about using the Config.xml file, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx). The customized Config.xml file must be located in the main product folder of the product you are installing. Because you cannot specify command-line options for Setup when you assign Office, you cannot specify an alternate location for the Config.xml file. For example, if you are installing Office Enterprise 2007, you customize the Enterprise.WW\config.xml file. You can customize only the Config.xml elements shown in the following table. These options are set when Office is assigned, and they cannot be modified later when Office is fully installed. All other elements in the Config.xml file are ignored.
Option Config.xml element

Installation location Feature installation states Product key Add or remove a language

INSTALLLOCATION OptionState PIDKEY AddLanguage, RemoveLanguage

Modifying the Config.xml file OptionState element

The OptionState element of the Config.xml file specifies how individual product features are handled during installation. Administrators can modify the Config.xml file by configuring attributes for the OptionState element. Administrators can specify the following behaviors: The feature or sub-feature is not installed. The feature or sub-feature is installed the first time it is used by the user. The feature or sub-feature returns to its default installation state. The feature or sub-feature is installed locally on the user's computer. Sub-features of the feature are set to the specified state.

OptionState Syntax
The OptionState element uses the following syntax. The attribute and element names are case sensitive. <OptionState Id="optionID" State="Absent" | "Advertise" | "Default" | "Local"[Children="force"]/> where: optionId is the identifier for a feature or sub-feature to install. Absent specifies that the feature or sub-feature is not installed. Advertise specifies to install the feature or sub-feature on first use. 260

Default returns the feature or sub-feature to its default state. This is the default setting. Local installs the feature or sub-feature on the user's computer. Force sets all features or sub-features to their specified states.

OptionState Id Values
The value for the Id attribute of the OptionState element is located in the Setup.xml file in the product folder of the product you are installing. For example, if you are installing Office Enterprise 2007, the file is Enterprise.WW\setup.xml. For a list of OptionState Id Values, see Config.xml file OptionState Id values. Tip: If you set the installation state of an application in Office to "Absent", the shortcut for that application is not created on the user's computer when Office is assigned. For example, the following element definition in Config.xml prevents the shortcut for Microsoft Office Word 2007 from being created and Word is not installed on the user's computer: <OptionState Id="WORDFiles" State="Absent" /> To modify the OptionState element in Config.xml 1. Open the Config.xml file in a text editor tool, such as Notepad. 2. Locate the line that contains the OptionState element, as shown in the following example: <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> 3. Modify the OptionState element entry with the options you want to use. For example, use the following syntax if you do not want Microsoft Publisher to be installed: <OptionState Id="PubPrimary" State="absent" /> 4. Repeat the preceding step to specify OptionState options for other features and subfeatures you want to modify. 5. Save the Config.xml file in the same folder that contained this file before you edited it. For more information about the OptionState element of the Config.xml file, see the OptionState element section in Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx). See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Create a network installation point for the 2007 Office system Config.xml file OptionState Id values Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx) Using Systems Management Server 2003 to deploy the 2007 Office system 261

Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179081.aspx)

262

Config.xml file OptionState Id values

The OptionState element of the Config.xml file provides options for specifying how individual product features are handled during installation. The value for the Id attribute of the OptionState element is located in the Setup.xml file in the product folder of the product you are installing. For example, if you are installing Office Enterprise 2007, the file is Enterprise.WW\setup.xml. For information about customizing the Config.xml file to modify the OptionState element, see the Modifying the Config.xml File OptionState element section in Use Group Policy Software Installation to deploy the 2007 Office system. For an example of a Config.xml file for a typical installation, see the Sample Config.xml file section in Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx).

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.

AccessBarcodeControl AccessHelpFiles AccessWizards

CalendarControl

DeveloperWizards

263

OptionStateId

Application and sub-feature

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.

EXCELFiles Excel_PIA

ExcelAddinFiles ExcelHelpFiles ExcelSampleFiles ExcelTemplatesFiles

GrooveFiles OneNoteFiles OneNoteHandwritingFonts OneNoteHelpFiles OneNotePIA

OneNoteToAddIns OneNoteMobile OUTLOOKFiles Outlook_PIA

OutlookHelpFiles

264

OptionStateId

Application and sub-feature

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

OutlookStationeryFiles OutlookVBScript

OutlookTemplateFiles OutlookMessaging OutlookAddIns OutlookOms PPTFiles OrgChartFiles

PowerPoint_PIA

PPTPresentationTemplates PPTHelpFiles PPTSoundFiles PPTViewerFiles PubPrimary PubComPrinting Publisher_PIA

PublisherFontSchemes PublisherHelpFiles

OptionStateId

Application and sub-feature

PubPaperDirect PubWizards RMSFiles RMSHelpFiles VisualStudio_PreviewServer_SPD WORDFiles Word_PIA

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. Installs the Microsoft Office Access Database

WordBibliographyFiles WORDBordersFiles WordCalligly WordEnvelopWizard WordGenko WORDHelpFiles WordQuickFormatsFiles WORDDocumentTemplates WordTableWizard XDOCSFiles XDocs_PIA

XDOCSHelpFiles XDOCSNoShipFiles XDocsRegFormFiles XDocsSamples SHAREDFiles AceRepl 266

OptionStateId

Application and sub-feature

Replication Conflict Manager, which you can use to resolve conflicts between replicated databases. CAGFiles IMEMain_1028 IMEMain_1041 IMEMain_1042 IMEMain_2052 ConvertersFiltersFile InternationalSupportFiles OArt_DocTheme 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. Document Update Utility that keeps documents 267

OfficeDigitalSFiles

OffproFonts OsaNonBoot ProofingTools PubFontsSys TCDRegistration

THEMESFiles

VBAFiles TOOLSFiles DocServicesFiles

OptionStateId

Application and sub-feature

on your computer up-to-date with copies of those documents in document workspaces. EquationEditorFiles Forms_PIA 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. Enables you to use Web Folders on Office-

GRAPHFiles HTMLSourceEditing MsInfoFiles MSOfficeDocumentImaging

MSTagPluginsFiles

OISFiles OSESupp

QueryFiles RefIEBarFiles

SetLanguageFiles SmartTag_PIA

WebDriveFiles 268

OptionStateId

Application and sub-feature

compatible Internet service providers. 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.

ProjectTemplates

ProjectWebProj

269

OptionStateId

Application and sub-feature

WAC_SPD WAC_HelpFiles_SPD WAC_ThemesTypical_SPD

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 Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx)

270

V Migrating to the 2007 Office system

271

Migrate Word, Excel, and PowerPoint files to the 2007 Office system
You can convert Word, Excel, and PowerPoint files manually, or you can use the OMPM Office File Converter to convert files in bulk. For information about installing OMPM, see Introduction to OMPM (http://technet.microsoft.com/en-us/library/cc179179.aspx).

Convert files in bulk with OMPM

The Office File Converter (OFC) requires that the Microsoft Office Compatibility Pack be installed on the computers that contain the files you want to convert. For more information, see Deploying the Microsoft Office Compatibility Pack. Before running the Office File Converter, first edit the ofc.ini file to set the appropriate parameters. To convert files 1. At a command prompt, navigate to the folder where OFC is installed. 2. Type: ofc <ofc.ini> The parameter for this command is as follows.
Parameter Description

ofc.ini

The location of the ofc.ini file. If no path is specified, OFC looks in the same directory as the executable. Optional.

Note: If you set FileListFolder and FoldersToConvert to the same set of files, the set of files will be converted twice.

272

Ofc.ini Settings
The following table shows the settings and values in ofc.ini.
Setting Description Possible Values If value is missing If value is not valid

[Run]

Section lists unique ID and description of this conversion. Required. Tracking Must be numeric number for the current Conversion. Use this to group Conversions from different computers in the Reporting Tool. Required. Text used to Free-form text, describe the truncated to 255 current characters conversion run. Optional.

Conversion Error: [Run] section stops with heading invalid or error missing in OFC.INI. message.

RunID

Conversion Error: Invalid or stops with missing RunID value error in OFC.INI. message.

Description

Ignore.

Not applicable.

273

Setting

Description

Possible Values

If value is missing

If value is not valid

LogDestinationPath

Location for the log file. Required.

Physical or mapped drive or UNC. For example: c:\Conversion\logs \\server\vba\logs Environment variables are also supported.

Conversion stops with error message.

Error: Invalid or missing LogDestinationPath value in OFC.INI.

[ConversionOptions]

Section heading for portion of INI file dealing with conversion options. Required, unless there are no conversion options specified in the .ini file. Enables user to specify that applicable files should be fully upgraded on open in respective O12 apps. Optional. Valid values are 1 full upgrade 0 no full upgrade

Conversion stops with error message.

Error: [ConversionOptions] section heading invalid or missing in OFC.INI.

FullUpgradeOnOpen

Default to full upgrade.

Error: FullUpgradeOnOpen value in OFC.INI.

274

Setting

Description

Possible Values

If value is missing

If value is not valid

DoNotCab

Enables users to disable creating CAB files of log files. Optional. Determines if the converter includes any macro projects during conversion. A setting of 1 will cause the OFC to produce macro-free Office 2007 document formats (such as .docx, xlsx, pptx). Macro/VBA code in the original documents will not be migrated. Optional.

Valid values are 1 disables creating CAB files of log files 0 enables CABing of log files Valid values are 1 disregard VBA on conversion 0 match macro state of source document.

Conversion Error: Invalid or stops with missing DoNotCab error value in OFC.INI. message.

MacroControl

Defaults to 0.

Error: Invalid MacroControl value in OFC.INI.

275

Setting

Description

Possible Values

If value is missing

If value is not valid

[FoldersToConvert]

Section lists directories to convert for standalone operation. FileList will be ignored. Optional.

List of folders.

Ignored if input file passed.

Error: [FoldersToConvert] section invalid in OFC.INI.

ConvertSubfolders

If folders are 0 or 1 specified, a setting of 1 causes the OFC to traverse subfolders, converting all Word, XL, & PPT documents. Optional. Section lists input file and destination information. Required. Path to FileList. Optional.

Defaults to 0.

Error: Invalid ConvertSubfolders value in OFC.INI.

[ConversionInfo]

[ConvertedFolders] Conversion stops with error message.

Error: [ConversionInfo] section heading invalid or missing in OFC.INI. Error if not present and [FoldersToConvert] empty.

FileList

276

Setting

Description

Possible Values

If value is missing

If value is not valid

SourcePathTemplate

Used to Any physical or determine mapped drive or location of UNC. * or . converted file. You can use wildcards, so that an asterisk (*) represents a single segment of the path. Optional.

Error: Invalid SourcePathRoot value in OFC.INI.

DestinationPathTemplate Used to Any physical or determine mapped drive or location of UNC. * or . converted file. You can use wildcards, so that an asterisk (*) plus a number represents a single segment of the path. See below for examples. Optional.

Error: Invalid DestinationPathRoot value in OFC.INI.

277

The following examples show how you can use the SourcePathTemplate and DestinationPathTemplate settings.

Example 1
In this example, the source files are located in \\userfiles\<user name>\docs\ and the desired output is to \\newserver\docs\<user name>\. To achieve this result, the SourcePathTemplate and DestinationPathTemplate settings should appear as follows: SourcePathTemplate = *\*\*\ DestinationPathTemplate = \\newserver\*3\*2 In this case, DestinationPathTemplate assigns a number for each directory segment represented by an asterisk in SourcePathTemplate, so that: *1 = userfiles *2 = <user name> *3 = docs The following table shows sample source file locations and the resulting locations for converted files with the above settings.
Source Destination

\\userfiles\Cliff\docs\notes.doc

\\newserver\docs\Cliff\notes.docx

\\userfiles\Bob\docs\Personal\Rept1.doc \\newserver\docs\Bob\Personal\Rept1.docx \\userfiles\James\docs\New Folder\Schedule.doc \\newserver\docs\James\New Folder\Schedule.docx

Example 2
In this example, the source files are located in the My Documents folders on users' local computers. The UNC path is \\<computer name>\<drive letter>$\Documents and Settings\<user name>\My Documents\. The desired output is to \\DocServer\docs\<user name>\. To achieve this result, the SourcePathTemplate and DestinationPathTemplate settings should appear as follows: SourcePathTemplate = *\*\*\*\*\ DestinationPathTemplate = \\DocServer\*4\ In this case, DestinationPathTemplate assigns a number for each directory segment represented by an asterisk in SourcePathTemplate, so that: *1 = <computer name> (for example, DESKTOP3) *2 = <drive letter>$ (for example, c$) 278

*3 = Documents and Settings *4 = <user name> (for example, bobsmith) *5 = My Documents The following table shows sample source file locations and the resulting locations for converted files with the above settings.
Source Destination

\\DESKTOP3\c$\Documents and Settings\bobsmith\My Documents\Plans.doc LPTP4\d$\Documents and Settings\James\My Documents\Reports\q1.xls

\\DocServer\bobsmith\Plans.docx

\\DocServer\James\Reports\q1.xlsx

Use VET for extracting versions of Word files

You can use the Version Extraction Tool (VET) included in OMPM to extract versions of files from Word files created in Office 2000, Office XP, and Office 2003 that contain versioning. With this tool, you can use the list of files generated by the OMPM reporting utility. Note: VET requires Microsoft .NET Framework Version 2.0 Redistributable Package (x86) (http://go.microsoft.com/fwlink/?LinkId=81886) and Microsoft Word 2003. To extract versions from Word files 1. At a command prompt, navigate to the folder where VET is installed. 2. Type: vet <OMPM file list directory> <output directory> The parameters for this command are as follows:
Parameter Description

OMPM file list directory output directory

Location of the file list generated by OMPM. Required. The directory to which you want to copy all of the versions of the Word files. Required.

279

For example, to use file lists contained in the c:\ompm\filelists directory and extract versions to the c:\ompm\output directory, you would type: vet c:\ompm\filelists c:\ompm\output

VET error messages

The following table show the error messages that VET writes both to the log and to the action file.
Error Message Description

IssueID 9090: Could not open document <document name>. IssueID 9096: Could not get the number of versions for document <document name>.

The original document that was flagged as having versions failed to open in Word. VET was not able to query the document for the number of versions in the named document. The object model command Versions.Count failed. An existing versions folder exists for a specific file, and VET was not able to delete it and could not create a new folder for the new version files. VET was not able to create a directory to hold the versions extracted for a specific document. VET was not able to access the version using the Word object model command Versions.Item(i). VET was not able to open the version specified using the Word object model command Versions.Item(i).Open(). VET was not able to save the specified version from the document to the versions folder.

IssueID 9091: Could not delete existing version folder <folder path>. IssueID 9092: Could not create directory to hold versions <directory name>. IssueID 9093: Failed to access version item.

IssueID 9094: Failed to open version <version number> from <file name>. IssueID 9095: Failed to save version <version number> from <file name> to <version folder name>.

See Also Migration considerations by applications (http://technet.microsoft.com/enus/library/cc178972.aspx) Migration reference for the 2007 Office system (http://technet.microsoft.com/enus/library/cc178980.aspx)

280

Using Group Policy to set default file save options

You can use Group Policy to change the default file save options for Microsoft Office Word 2007, Microsoft Office Excel 2007, and Microsoft Office PowerPoint 2007. The administrative templates are available at 2007 Office system (SP2) Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool (http://go.microsoft.com/fwlink/?LinkId=144523) (http://go.microsoft.com/fwlink?linkid=75729). After you download the templates, add them to the Group Policy Management Console. To change default file save options 1. In the left pane of the Group Policy Management Console, double-click User Configuration and double-click Administrative Templates (Classic Administrative Templates (ADM) in Windows Vista). 2. To change default file save options in Office Excel 2007: a. Double-click Microsoft Office Excel 2007, double-click Excel Options, and click Save. b. In the right pane, right-click Save Excel files as, and select Properties. c. In Save files in this format, select Enabled. d. In the drop-down box, select a default file save format. e. Click Apply to save the settings. 3. To change default file save options in Office PowerPoint 2007: a. Double-click Microsoft Office PowerPoint 2007, double-click PowerPoint Options, and click Save. b. In the right pane, right-click Save files in this format, and select Properties. c. In Save files in this format, select Enabled. d. In the drop-down box, select a default file save format. e. Click Apply to save the settings. 4. To change default file save options in Office Word 2007: a. Double-click Microsoft Office Word 2007, double-click Word Options, and click Save. b. In the right pane, right-click Save files in this format, and select Properties. c. In Save files in this format, select Enabled. d. In the drop-down box, select a default file save format. e. Click Apply to save the settings.

281

The following table shows the values that are available for the Save files in this format setting.
ADM file Possible values

Excel12.adm

Office Excel 2007 workbook (.xlsx) Office Excel 2007 macro-enabled workbook (.xlsm) Office Excel 2007 binary workbook (.xlsb) Web page (.htm, .html) Excel 97-2003 workbook (.xls) Excel 5.0/95 workbook (.xls)

Ppt12.adm

Office PowerPoint 2007 presentation (.pptx) Office PowerPoint 2007 macro-enabled presentation (.pptm) PowerPoint 97-2003 presentation (.ppt)

Word12.adm

Office Word 2007 document (.docx) Office Word 2007 macro-enabled document (.docm) Office Word 2007 macro-free template (.dotx) Office Word 2007 macro-enabled template (.dotm) Single file Web page (.mht) Web page (.htm, .html) Filtered Web page (.htm, .html) Rich text format (.rtf) Plain text (.txt) Word 97-2003 document (.doc) Word 97-2003 template (.dot) Flat XML document (.xml) Word 6.0/95 document (.doc) Word 6.0/95 Chinese (simplified) document (.doc) Word 6.0/95 Chinese (traditional) document (.doc) Word 6.0/95 Japanese document (.doc) Word 6.0/95 Korean document (.doc) Word 97-2002 and Word 6.0/95 rich text format (RTF) (.doc) Word 5.1 for Macintosh (.mcw) Word 5.0 for Macintosh (.mcw) Word 2.x for Windows (.doc) Works 4.0 for Windows (.wps) WordPerfect 5.x for Windows (.doc) WordPerfect 5.1 for DOS (.doc)

282

283

Deploying the Microsoft Office Compatibility Pack

To meet the needs of users upgrading to the 2007 Microsoft Office system, Microsoft offers updates and a compatibility pack for Office XP and Office 2003 that enable a user to open and save 2007 Office release XML files.

Microsoft Office Compatibility Pack deployment

For installation instructions for the Microsoft Office Compatibility pack, see Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (http://go.microsoft.com/fwlink?LinkID=77512). This site guides you through installing appropriate updates and the Microsoft Office Compatibility Pack.

284

VI Deployment Strategies for the 2007 Office release

285

Step-by-step guides

286

Configure the 2007 Office system for a hard disk image (step-by-step)
You can deploy the 2007 Microsoft Office system and other software products at the same time to all users. You first install a custom configuration of Office on a clean test computer. Then you capture and distribute an image of the hard disk to users' computers. The first step in this process is to configure Office in preparation for the hard-disk image.
Steps Reference

Copy all files and folders from the Office CD to a folder on the network or on your computer. Copy language packs or additional Office products to the same installation point. When you are prompted to overwrite duplicate Setup files, click No. Start the Office Customization Tool by running Setup with the /admin command-line option. Specify the primary Office product you want to customize. On the Setup pages of the tool, enter the following information: Path to the network installation point from which you are installing Office Default organization name for all users who receive the hard-disk image Path to one or more backup network sources Your 25-character volume license key Acceptance of the License Agreement

Create a network installation point for the 2007 Office system

Customize the 2007 Office system

Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)

In the Display Level box, set the display level for the installation to Basic. If you are including multiple language versions in the hard-disk image, open the Config.mxl file for the product you are deploying and specify all the languages you want to include in the hard-disk image.

Customize Setup before installing the 2007 Office system Customize and deploy multiple language versions of the 2007 Office system

287

Steps

Reference

Run Setup and install Office on the test computer from which you will create the hard disk image. Do not start Office applications on the test computer.

Run Setup for the 2007 Office system on users' computers

How it works
You use the Office Customization Tool to specify the majority of customizations to the Office configuration, which are saved in a Setup customization file (MSP file) that is applied when users install Office. When you save the customization file in the Updates folder on the network installation point, Setup finds and applies the file automatically during the installation. Only a few customizations, such as specifying more than one Office product or language to install, are handled in the Config.xml file. Tip: Consolidate all your customizations in the configuration intended for the hard-disk image, including additional Office products or language packs that you plan to deploy. Then you can more efficiently recreate or repeat the hard-disk image. All the customizations detailed in the preceding table help optimize the process of installing Office through hard disk imaging. You can make additional customizations for your organization by using the methods described here. Note: Setup handles many details of the installation process automatically. For example, you no longer need to set the NOUSERNAME property when you install Office on the test computer. Setup automatically prevents Windows Installer from capturing a user name until a user starts an Office application for the first time. Creation of a local installation source on the client computer also occurs automatically.

Next step
After you install a custom configuration of Office on the test computer, you capture the hard-disk image and then distribute it to users.

More information
For detailed information about the design and behavior of Setup, see the Setup architecture section of the 2007 Office Resource Kit, beginning with Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/en-us/library/dd162398.aspx). For more information about using the deployment tools for 2007 Office release, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en288

us/library/cc179097.aspx) and Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

289

Deploy the 2007 Office system with limited network capacity

If you are deploying 2007 Microsoft Office system in an environment with limited network resources, the Setup architecture in the 2007 Office release allows you to minimize the demand on the network and still ensure that all users install the new version at exactly the same time. For example, perhaps you have distant branch offices that connect to your corporate network over a limited or expensive wide area network (WAN). Or you have a higher capacity corporate network that supports thousands of users. If you distribute Office by using a typical log-on script, and 10,000 users access the network at the same time, they might have to wait too long for 500 MB of installation files to travel across the network. In these types of environments, you can distribute the Office source files to users over time. Once your targeted user groups have a local installation source deployed on their computers, you can schedule a simultaneous installation of Office without overtaxing your corporate network.

Recommended solution
1. Create a network installation point for the 2007 Office system 2. Customize the 2007 Office system 3. Precache the local installation source for the 2007 Office system 4. Run Setup from the local installation source to install the 2007 Office system

How it works
This deployment strategy works because Setup always installs 2007 Office release products in two stages. First, Setup copies all required installation files from the network installation point to a hidden folder on the local computer. Second, Setup calls Windows Installer to perform the installation from each user's local installation source. Separating these two phases of the process allows you to manage the load on the network more efficiently. You configure Office before you distribute the local installation source. To specify most user configuration options, you run the Office Customization Tool to generate a Setup customization file (MSP file). The recommended location in which to store customization files is the Updates folder at the root of the network installation point. For some customizations, such as specifying additional languages, you must edit the Config.xml file for the product you are installing. You also edit the Config.xml to specify that Setup deploy only the local source. When your customizations are complete, you run Setup to distribute the local installation source to one group of users at a time. You can use any distribution method, such as a log-on script, a batch file, or another deployment tool such as Microsoft Systems Management Server. In the 290

precache scenario only, Setup copies the Updates folder from the network installation point to the local source. All your customizations are included in the local source. Setup also includes a copy of itself in the local installation source. After your targeted users have a local installation source on their computers, you can trigger Setup to run from the local source and complete the installation at the scheduled time. The installation, including application of your customizations and software updates, happens locally with no file transfers or any other activity over the network. Note: When Setup installs Office from the local installation source, it does not return to the original network installation point to look for new customization files or software updates. Only the files cached in the local installation source on the users computer are applied. If you make additional customizations or add new software updates to the network installation point after you precache the local source, you must distribute them separately, after Office is installed. See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx)

291

Deploy multiple customization patches (stepby-step)

Administrators can use the Office Customization Tool (OCT) to deploy multiple customization patches (MSP files) to configure the 2007 Microsoft Office system. Administrators can create a basic customization patch (MSP), and this initial MSP can be used to create another customization patch that includes all the settings in the original MSP and additional applications and modified settings, for example. The second MSP can be applied to a new set of users or to existing installations. Using this approach is useful in phased deployments, or in cases where you are deploying a standard core configuration with variations for the various departments in your organization. The following table highlights the process for deploying multiple MSP files.
Steps Reference

Make sure you have copied all files and folders from the Office CD to a folder on the network or on your computer. For example, copy the files to \\server\share\Office12. Copy all language packs or additional Office products to the same installation point. When you are prompted to overwrite duplicate Setup files, click No. Use the OCT to create the basic Setup customization MSP file.

Create a network installation point for the 2007 Office system

Customize Setup before installing the 2007 Office system Customize and deploy multiple language versions of the 2007 Office system Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)

292

Steps
Use the OCT to open the initial MSP and create the second customization patch. If you added additional languages to the network installation point, you must re-create the MSP file. Important When you create the second customization

Reference

Change users' configurations after installing the 2007 Office system (http://technet.microsoft.com/enus/library/cc179141.aspx) Customize and deploy multiple language versions of the 2007 Office system

patch, you can configure the feature installation states that you want to use. To do this select Set feature installation states in the left pane of the OTC. Expand Microsoft Office and change the installation option for the applications. It is not necessary to duplicate the options you used in the initial customization patch if you do not want to modify them. If you set a feature to its default state, the symbol [F] is displayed before the feature name. This forces the feature into this state. If you change a feature's installation state,

the name of the feature and child features are displayed in bold font which indicates that Setup will apply the changes to the installation. Features whose names are not displayed in bold font are not changed. If you are deploying additional languages in

the second MSP, you must first copy all the Single Language Packs (SLPs) you want to deploy to the network installation point you created in the first step. And you must also recreate the customization MSP file you want to deploy to users. Failure to do this may result in unexpected behavior. For example, if the MSP is not re-created, the language pack may not be applied to all of the installed applications. The Modify user settings options set the

default values of Office application settings for users who install Office with the customization file. For the second customization patch, it is not necessary to replicate the settings that you do not want to modify. The settings are set to Not Configured by default.

Deploy the customization patch to users'

Distribute product updates for the 2007 Office 293

Steps

Reference

computers. Notes The Setup customization file is a Windows Installer package (MSP) that you apply to users' computers just as you would apply a software update. To apply the Setup customization file, users can double-click the MSP file. Alternatively, users can run Msiexec.exe at the command prompt with one of the following command-line options to apply the MSP patches: msiexec.exe / p\\server\share\custom.msp msiexec /update\\server\share\Patch1.msp where \\server\share indicates the path to the shared folder containing the MSP files. For information about Windows Installer, see the following resources on the MSDN Web site: Standard Installer Command-Line Options (http://go.microsoft.com/fwlink/? LinkId=111106) Command-Line Options (http://go.microsoft.com/fwlink/? LinkId=111127) What's New in Windows Installer (http://go.microsoft.com/fwlink/? LinkId=111108) Not Supported in Windows Installer 4.0 (http://go.microsoft.com/fwlink/? LinkId=111109) Users can also use Systems Management Server to deploy the MSP.

system (http://technet.microsoft.com/enus/library/cc178995.aspx) Using Systems Management Server 2003 to deploy the 2007 Office system

294

See Also Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx) Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx)

295

Deploy customizations of the 2007 Office system to users in the field (step-by-step)
If you are deploying the 2007 Microsoft Office system in an environment that includes users who work primarily in the field and who have limited access to your organization's network, you can create a customized 2007 Office installation image and make the installation files available on a CD for those users. The installation image can contain multiple languages and Office products. The following table highlights the steps that are required to deploy a customized installation with a CD.
Steps References

Create a network installation point that contains the Office 2007 products that you want to install. Copy the Single Language Packs (SLPs) that you want to use to the network installation point. This allows Setup to coordinate a single installation of multiple language versions of the product. Notes This step also requires modifying the Config.xml file that is in the root of the product folder for the product that you are installing. To modify the Config.xml file, open Config.xml in an editor such as Notepad. Clear the comment for the Display element line by deleting the opening <!-- and closing --> tags. To prevent user intervention during the update process, you can modify the Display element as follows: <Display Level="basic" CompletionNotice="yes" SuppressModal="yes" NoCancel="yes" /> You use the AddLanguage Element of the Config.xml file to add 296

Create a network installation point for the 2007 Office system Customize and deploy multiple language versions of the 2007 Office system Language identifiers in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179219.aspx) Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx)

Steps

References

specific languages to the installation, and specify the Id attribute of the language tag of the language that you want to deploy. For example, you add the following line in Config.xml to add the French language version: <AddLanguage Id="fr-fr" /> You can specify more than one language by including additional <AddLanguage> elements and attributes. If you add more than one language to the installation, you must also set the <ShellTransform> attribute of the <AddLanguage> element of Config.xml to specify the language for the shell user interface. For example, you add the following elements to specify that Setup install full English, French, German, and Spanish language support with the users default regional options language as the default installation language: <AddLanguage Id="match" ShellTransform="yes"/> <AddLanguage Id="en-us " /> <AddLanguage Id="fr-fr " /> <AddLanguage Id="de-de " /> <AddLanguage Id="es-es " /> In this case, Setup installs all of the specified languages plus the language that matches the user's locale, if that language is different and is available in the installation source. Save the Config.xml file in the directory that contains Setup.exe.

297

Steps

References

Use the Office Customization Tool (OCT) for the Customize the 2007 Office system customizations and installation options that you Office Customization Tool in the 2007 Office want to apply. system (http://technet.microsoft.com/enus/library/cc179097.aspx) Notes We recommend that you store the customization files in the Updates folder at the root of the network installation point. Make sure that you enter the product key and accept the Microsoft Software License Terms on behalf of each user who installs Office with the Setup customization file. To do this, use the Licensing and user interface page of the Setup section of the OCT. Copy the entire Office 2007 folder with the source files and your customizations from the network installation point to a CD. Distribute the folder to users.

298

Steps

References

Instruct users to run Setup.exe from the CD that you created. For example, instruct users to type the following at the command prompt: <CD drive_name>:\Office12\setup.exe Notes If you saved the Config.xml file to a location other than the directory that contains Setup.exe, instruct users to provide the path to your customized Config.xml file. For example: <CD drive_name>:\Office12\setup.exe /config <CD drive_name>:\Enterprise.WW\Config. xml If you placed the custom Config.xml on a network share, instruct users to use a fully qualified path. For example: \\server\share\Office12\setup.exe /config \\server\share\Enterprise.WW\Config. xml.

See Also Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx) Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx) Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx)

299

Update calendars to match 2007 daylight saving time rules (step-by-step)

Beginning in 2007, daylight saving time (DST) in the United States and Canada is observed for several additional weeks. This change can impact Outlook calendar items. Note: This topic helps administrators plan how to address the DST change efficiently in their organizations. An Office Online article, Prepare Outlook calendar items for daylight saving time changes in 2007 (http://go.microsoft.com/fwlink/?LinkId=82972), provides detailed information for users about how the DST rules have changed and the impact on users' calendaring environments. The article also includes information about why updating users' computers is required and outlines the effect of the DST changes in different Outlook user scenarios. To help ensure that Outlook calendars work correctly with the new DST rules, you must update Microsoft Windows and other products to reflect the new daylight saving time period. In addition, you can download and run tools that work with Microsoft Outlook and Microsoft Exchange Server to correct calendar information. The steps you should take to update your organization's calendaring environment are listed below.
Step Action How-to instructions

Update Microsoft Windows on servers running Microsoft Exchange Update Microsoft Windows on users' computers Update mobile devices used to create or view calendar items Update Collaboration Data Objects (CDO) on servers running Microsoft Exchange Use options table to determine the best method to update users' calendars Update users' calendars by downloading and running one or both of the Microsoft update tools:

2007 time zone update for Microsoft Windows operating systems (http://go.microsoft.com/fwlink/?LinkId=82988) As above: 2007 time zone update for Microsoft Windows operating systems How to configure daylight saving time on Windows Mobile-based devices (http://go.microsoft.com/fwlink/?LinkId=82989) Update for daylight saving time changes for Exchange 2003 Service Pack 2 (http://go.microsoft.com/fwlink/?LinkId=82990) Options for updating mailboxes

2 3

5 6

300

Step

Action

How-to instructions

a. Download and run the Time Zone Data Update Tool for Outlook b. Download and run the Exchange Calendar Update Tool

How to address daylight saving time by using the Outlook Time Zone Update Tool (http://go.microsoft.com/fwlink/?LinkId=82980) How to address daylight saving time by using the Exchange Calendar Update Tool (http://go.microsoft.com/fwlink/?LinkId=82975)

Options for updating mailboxes

You can update mailboxes by using the Time Zone Data Update Tool for Outlook or the Exchange Calendar Update Tool, or you can use both tools in combination to accomplish a complete update. The best method for your organization depends on several factors, including how many users are configured on each Exchange server and how many meetings must be updated in your calendaring environment. For advice on which update method might be best for your organization, refer to the scenarios and options in the following table.
Option Pros Cons

Distribute the Outlook tool to each user, and then instruct users to update their own mailboxes.

This option avoids the risks and limitations of running the Exchange tool.

It is difficult to guarantee that all users will run the tool correctly and in a timely manner. Users who do not have Outlook will be unable to run the Outlook tool. An additional educational effort is needed to lessen confusion for users. There are issues associated with running the Exchange tool, as described in the Exchange tool limitations table (see table later in this section). The cons of running the Outlook tool are combined with the cons of running the Exchange tool.

Run the Exchange tool against all affected users and servers.

This option provides a streamlined experience for users.

Run the Exchange tool and update only recurring appointments. Let users update single-instance appointments in their own mailboxes by using the Outlook tool.

There is less risk involved when single-instance appointments are incorrectly updated.

301

Option

Pros

Cons

Run neither the Exchange tool nor the Outlook tool. Ask users to examine their calendars and re-book appointments as needed.

This option avoids the issues of running the Exchange tool.

Unless all users re-book all affected appointments, some calendar items will be one hour off during the extended DST period. An additional educational effort is needed to lessen confusion for users. This is not an option if users are running Office Outlook 2007.

Distribute the Outlook tool to each user, and then instruct users to update their own mailboxes. Then, use the Time Zone Extraction Mode of the Exchange tool to determine whether users are running the Outlook tool. If the users are not running the Outlook tool, you can run the Exchange tool.

This option reduces the risk of users not running the tool in a timely manner, and avoids the issues of running the Exchange tool.

302

If the Exchange Calendar Tool is an option you are considering for updating mailboxes, first evaluate the issues described in the following table.
Risk Effect Mitigation

There are many meeting updates.

Server and network performance is decreased while the Exchange tool runs.

First, determine the effect of running the Exchange tool on server and network performance by updating a small batch of users. If the load is disruptive, run the tool during off-peak hours or during dedicated maintenance hours. To speed up the process, divide users into batches, then run instances of the Exchange tool on separate computers to perform the updates.

The tool takes too long to run. The Exchange tool is singlethreaded. If you run the tool in Update Mode for several thousand mailboxes at the same time, the tool might takes hours or possibly days to finish.

See Also Preparing for daylight saving time changes in 2007 (http://go.microsoft.com/fwlink/?LinkId=81418)

303

Deploy custom configurations of the 2007 Office system (step-by-step)

This article describes how to deploy an initial customized installation of the 2007 Microsoft Office system to users in your organization. It also includes an example of a Config.xml file. The following table highlights the process for deploying a custom configuration.
Steps Copy all the files and folders from the 2007 Office system CD to a folder on the network or on your computer. For example, copy the files to \\server\share\Office12. Copy all language packs and additional Office products you want to deploy to the same network installation point. When you are prompted to overwrite duplicate Setup files, click No. To specify installation options, such as the path to the network installation point, the product to install, and custom setup options, and to specify the languages to install, use the Config.xml file that is located in the root of the product folder for the product that you are installing. To edit the Config.xml file, use a text editor such as Notepad. 1. To modify the display options that users see during installation, locate the line in the Config.xml file that contains the Display element: <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> To configure a silent (unattended) install to prevent user intervention during the installation and to specify display options, you can modify the Display element information as shown in the following example: <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> For information, see Display element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx). 2. To specify additional languages to install, use the AddLanguage elements and attributes in the Config.xml file. Notes If you are adding more than one AddLanguage element, you must add the ShellTransform attribute of the AddLanguage element. This attribute specifies the language that Setup uses for Config.xml file in the 2007 Office system (http://technet.microsoft.com/e n-us/library/cc179195.aspx) Customize and deploy multiple language versions of the 2007 Office system References Create a network installation point for the 2007 Office system

304

Steps the shell user interface. For example, to specify that Setup install full English, French, German, and Spanish language support with the users default regional options language as the default installation language, you add the following AddLanguage elements and attributes in the Config.xml file: <AddLanguage Id="match" ShellTransform="yes"/> <AddLanguage Id="en-us" /> <AddLanguage Id="fr-fr" /> <AddLanguage Id="de-de" /> <AddLanguage Id="es-es" /> In the preceding example, Setup installs all of the specified languages plus the language that matches the user's locale, if that language is different and is available in the installation source. For more information, see AddLanguage element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx). You can also use the Config.xml file to configure additional options such as the following: Specify the path to the network installation point. For information, see DistributionPoint element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx). Specify the 25-character volume license key. For information, see PIDKEY element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). Specify the fully qualified path to the folder on users' computers in which the product is installed. For information, see INSTALLLOCATION element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). Specify logging options for Setup. For information, see Logging element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). Specify how the local installation source (LIS) is cached on the user's computer. For more information, see LIS element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). Set the user or company name for the user on whose computer the product is being installed. For information, see USERNAME and COMPANYNAME elements in Config.xml file in

References

305

Steps the 2007 Office system (http://technet.microsoft.com/enus/library/cc179195.aspx). You can use the Config.xml file to customize many of the same options that you can configure with the Office Customization Tool, including a few additional options that are not available in the OCT. For a complete description of the areas you can configure in Config.xml, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). 3. When you complete the Config.xml customizations, save the Config.xml file. You can use the /config Setup command-line option to specify the location of the Config.xml file, as shown in the following example: \\server\share\setup.exe /config \\server\share\Enterprise.WW\config.xml For information about the /config Setup command-line option, see the "/config [path]" section in Setup command-line options for the 2007 Office system (http://technet.microsoft.com/enus/library/cc178956.aspx). To see an example of a custom Config.xml file, see Config.xml Example. Use the Office Customization Tool (OCT) to customize Setup, and configure additional customizations and installation options. This creates a Setup customization file (MSP file). For a complete description of the areas you can configure with the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Important: Office has released OCT updates for the 2007 Office system Service Pack 2 (SP2). To download the updates, see 2007 Office system (SP2) Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool (http://go.microsoft.com/fwlink/? LinkId=144523) This download works with 2007 Office system applications, updated with 2007 Microsoft Office Suite Service Pack 2 (SP2) (http://go.microsoft.com/fwlink/?LinkId=144524). For more information about the OCT updates, see 2007 Office System Administrative Template Files (ADM, ADMX, ADML) and Office Customization Tool Updates (http://technet.microsoft.com/enus/library/cc178992.aspx). 1. From the root of the network installation point you created previously, run the following command-line option to start the OCT: setup.exe /admin.

References

Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/e n-us/library/cc179097.aspx) Customize Setup before installing the 2007 Office system Configure user settings for the 2007 Office system

306

Steps 2. Customize Setup to specify how you want Setup to manage the

References

installation. For information, see Customize Setup before installing the 2007 Office system. 3. Set feature installation states. For information, see Configure feature installation states of the 2007 Office system. For each application that you want to add to the installation, set its installation option to Run all from My Computer or Installed on First Use in the right pane. For example, to install Outlook, expand Microsoft Office and change the installation option for Microsoft Office Outlook to Run all from My Computer. For applications that you do not want to install, set the installation option to Not Available in the right pane. The application name is set to bold to show that you have changed its installation option. To prevent users from installing this application themselves, select the Hidden and Locked options. The symbols [H] and [L] are added to the application name to indicate that these options are set. Important If you set the Hidden option for a specific feature by using the OCT or the Config.xml file during an initial installation of the 2007 Office system, you cannot unhide that feature in the feature tree by using another Config.xml file or applying a second MSP customization file after the initial installation. This means that the feature is not displayed in the feature tree during installation. The feature remains hidden and you cannot reverse this; 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 uninstall 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=Absent Children=force />

307

Steps You can also use the OCT to create an MSP customization

References

file to install the feature later by setting the feature installation state to Run All from My Computer on the Set feature installation states screen. 4. Configure Office security settings if you want to provide an initial configuration of security settings. For information, see Office security settings in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Note: Although you can use the OCT to specify security settings in a Setup customization file (MSP file), users can change the settings after installation. To enforce security settings, use Group Policy. For detailed information about planning for and configuring security settings, see the articles in these sections: Planning for security in the 2007 Office system and Deploying security settings for the 2007 Office system. For information about the security settings and privacy options in the 2007 Office system, see Security policies and settings in the 2007 Office system. Administrators can use the OCT to configure initial security settings for the following areas: 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. See "Trusted Publishers" in the Office security settings section of Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). Trusted Locations. Manage the list that identifies locations from which any file can be opened without being checked by the Trust Center security feature. When you specify one or more trusted locations, the Trusted Locations list previously defined on the users computer is cleared and replaced by this list. See "Trusted Locations" in the Office security settings section of Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Remove all Trusted Locations written by OCT during installation. Clears the Trusted Locations list on the user's computer. Use this check box if you want to clear the Trusted Locations list on the user's computer without adding any new

308

Steps locations. See "Remove all Trusted Locations written by OCT during installation" in the Office security settings section of Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Default Security Settings. Set default security levels for addins, templates, and Office applications. See "Default Security Settings" in the Office security settings section of Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Unsafe ActiveX Initialization. Determine whether unsigned, and therefore potentially unsafe, ActiveX controls can initialize by using persisted data, that is, data that is saved from one instance of the control to the next. See "Unsafe ActiveX Initialization" in the Office security settings section of Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). 5. Specify the user settings you want to apply. For information, see Configure user settings for the 2007 Office system. Use the Modify user settings section to set the default values of Office application settings for users who install Office with this customization file. To configure an option, expand the tree on the left, and click the user interface element you want to configure. The configurable settings associated with that element appear on the right pane. You can specify one of the following options: Not Configured. The setting remains as it is. Enabled. The setting is modified according to the selections you make on the setting's Properties page. Disabled. The setting is disabled. Note that disabling an option may be different from not configuring the option. See the description of the specific option for more details. The 2007 Office system Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool Version 2.0 download (http://go.microsoft.com/fwlink/?LinkId=102314) includes an Office Excel 2007 workbook (Office2007GroupPolicyAndOCTSettings.xls) that provides a listing of all the Office Customization Tool (OPA) settings and Group Policy settings in the 2007 Office system. Note: Using the OCT to configure user settings establishes the initial default values for the settings. Users can modify most of

References

309

Steps the settings after Office is installed. If you want to enforce user settings, use Group Policy. For more information, see Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179081.aspx). You can also use Group Policy settings to mandate settings for Outlook. You can manage the following Outlook areas with Group Policy: Specify the COM add-ins that are trusted. For information, Customize cryptographic options. For information, see Set Configure Outlook Junk E-mail Filter settings. For information, Configure the method that Outlook uses for security settings. see Manage trusted add-ins for Outlook 2007. consistent Outlook 2007 cryptography options for an organization. see Configure junk e-mail settings in Outlook 2007. See Specify the method Outlook uses to manage virus prevention features. Configure attachment settings. For information, see Configure programmatic security settings. For information, Customize ActiveX options and custom forms settings. For Customize attachment settings in Outlook 2007. see Customize programmatic settings in Outlook 2007. information, see Customize ActiveX and custom forms security settings in Outlook 2007. 6. Disable folder home pages. For information, see Configure security for Outlook 2007 folder home pages. You can use the Additional content section of the OCT to Add files to, or remove files from, users' computers when configure the following options: Office is installed. For information, see Add files and Remove files in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Add, modify, or remove registry entries on users' computers when Office is installed. For information, see Add registry entries and Remove registry entries in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). Add shortcuts to files installed with the 2007 Office system or files that are already on the user's computer. For information, see Configure shortcuts in Office Customization Tool in the 2007

References

310

Steps Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). 7. You can use the Outlook section (Outlook in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx)) of the OCT to configure the following Outlook areas: Specify Exchange settings. You can configure users Microsoft Exchange settings in a new or modified Outlook profile. For information, see Specify Exchange settings in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Outlook Profile settings. You can 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. For information, see Outlook profile in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). Include new Outlook e-mail accounts in the users profile. For information, see Add accounts in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). Remove existing e-mail accounts or export settings to an Outlook profile file (PRF file). For information, see Remove accounts and export settings in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/enus/library/cc179097.aspx). Define Send/Receive groups for Exchange accounts and folders, and specify the tasks that are performed on each group during a Send/Receive operation in Outlook. A Send/Receive group contains a collection of Outlook accounts and folders. For information, see Specify send receive groups in Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx). 8. When you complete your customizations, click Save As on the File menu, specify a path and file name for the Setup customization file, and then click Save. It is recommended that you save the custom MSP file in the Updates folder on the network installation point. When Setup runs, it searches the Updates folder on the installation point for a customization file

References

311

Steps specific to the product that is being installed. Notes If you do not put the customization file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully qualified path to the folder in which you store the custom MSP file. For example, setup.exe /adminfile \\server\share\myNewUpdatesFolder. You can also specify the location of the folder that contains your MSP files in the Config.xml file by using the SUpdateLocation attribute of the SetupUpdates element. For more information about SetupUpdates, see the SetupUpdates element section in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx). To install the 2007 Office system on users' computers, you can use one of the following approaches, depending on your particular environment and requirements: 1. Use the precached local installation source to install Office on users' computers. When you deploy the 2007 Office system, Setup creates a local installation source on the user's computer a copy of the compressed source files for the Office product you are installing. After the files are copied to the user's computer, Setup completes the installation from the local installation source. To minimize the load on your network, you can deploy the local installation source to users' computers separately, before you deploy Office. To use this approach, perform the followings tasks: Distribute the local installation source to users. For information, see Precache the local installation source for the 2007 Office system. Run Setup directly from the local installation source. For information, see Run Setup from the local installation source to install the 2007 Office system. 2. On the user's computer, run Setup.exe from the root of the network installation point. For information, see Run Setup for the 2007 Office system on users' computers. 3. To deploy Office to users who are not administrators of their computers, you can use one of the following methods. Log on to the computer as an administrator and install 2007 Office system. For information, see "Logging on as an administrator" in Deploy the 2007 Office system to users who are not administrators.

References

Precache the local installation source for the 2007 Office system Run Setup from the local installation source to install the 2007 Office system Run Setup for the 2007 Office system on users' computers Deploy the 2007 Office system to users who are not administrators Using Systems Management Server 2003 to deploy the 2007 Office system Deploy the 2007 Office system by using System Center Essentials 2007 Use Group Policy to assign computer startup scripts for 2007 Office deployment

312

Steps -orUse an enterprise deployment method such as the following: Use Microsoft Systems Management Server. If you manage large numbers of clients in a complex or rapidly changing environment, Microsoft Systems Management Server is the recommended method for installing and maintaining the 2007 Office system in medium- and large-sized organizations. Microsoft Systems Management Server offers sophisticated functionality, including inventory, scheduling, and reporting features. For information, see Using Systems Management Server 2003 to deploy the 2007 Office system. Use Microsoft System Center Essentials 2007 to deploy the 2007 Office system. System Center Essentials 2007 is a management solution designed for IT system administrators in medium-sized organizations that include up to 30 servers and 500 client computers. For more information, see Deploy the 2007 Office system by using System Center Essentials 2007. If you have deployed Active Directory and Group Policy in your organization, you can use Group Policy to assign computer startup scripts to deploy the 2007 Office system. For more information, see Use Group Policy to assign computer startup scripts for 2007 Office deployment. In an environment with Active Directory installed, you can also use Group Policy Software Installation features to assign the 2007 Office system to computers in your organization. The installation is performed with administrator rights, and Office is available to all users on that computer. Important: Although Group Policy can be used to install software applications in small-sized organizations with Active Directory installed, there are some limitations, and you must determine whether it is an appropriate solution for your deployment requirements. For more information, see the "Deployment considerations" section of Use Group Policy Software Installation to deploy the 2007 Office system.

References

313

Config.xml example
The following example shows a Config.xml file for an installation of Microsoft Office Professional Plus 2007. The following options are used in this example: Display Level is set to turn off the Setup user interface, hide error messages and other dialog boxes, and accept the End-User License Agreement. Verbose logging is turned on, and log files are stored in the AppInst folder. INSTALLLOCATION specifies the fully qualified path to the folder on the user's computer in which the product is installed. LIS SOURCELIST provides a list, separated by semicolons, of the network installation points that contain the installation files for the product. The equivalent option in the OCT is Additional network sources (http://technet.microsoft.com/enus/library/cc179097.aspx#Additional_network_sources). Setting id specifies the suppress reboot option (SETUP_REBOOT value set to NEVER). OptionState element specifies to uninstall the feature (Access in this case) on the user's computer and sets child features of the feature to the same specified state.

314

<Configuration Product="ProPlus"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Logging Type="verbose" Path="%SYSADMINROOT %\Log\AppInst\Office2007" Template="Microsoft Office 2007 Professional Plus Setup(*).txt" />

<INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> <LIS SOURCELIST Value="\\server1\share\Office12;\\server2\share\Office12" /> <Setting Id="SETUP_REBOOT" Value="NEVER" /> <OptionState Id=ACCESSFiles State=absent Children=force /> </Configuration>

See Also Setup architecture overview for the 2007 Office system (http://technet.microsoft.com/enus/library/dd162398.aspx) Change users' configurations after installing the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179141.aspx) Deploy multiple customization patches (step-by-step) Distribute product updates for the 2007 Office system (http://technet.microsoft.com/enus/library/cc178995.aspx) Deploy customizations of the 2007 Office system to users in the field (step-by-step) Enforce settings by using Group Policy in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179081.aspx)

315