Download.microsoft.com
[pic]
Office Resource Kit for
Microsoft Office 2010 Beta
Microsoft Corporation
Published: February 2010
Author: Microsoft Office System and Servers Team (itspdocs@)
Abstract
This document supports a preliminary release of Microsoft Office 2010 Beta. The content in the book covers information about how to plan, configure, deploy, maintain, secure, and troubleshoot installations of Microsoft Office 2010 Beta. The documentation is intended for IT professionals who plan, implement, and maintain Office installations in their organizations.
For current content that supports the released version of Microsoft Office 2010, see Office 2010 Resource Kit technical library ().
[pic]
This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.
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, email address, logo, person, place or event is intended or should be inferred.
© 2010 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, 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.
Contents
Getting help xxix
Product evaluation and getting started with Office 2010 Beta 1
What's new in Office 2010 3
New and updated features in Office 2010 3
Fluent user interface 3
Backstage view 3
Silverlight 3
File formats 4
Edition comparison 4
Differences between Microsoft Office versions 4
What’s new for IT Professionals 6
SharePoint Workspace 2010 overview 7
System requirements for Office 2010 10
Microsoft Office Professional Plus 2010 10
Microsoft Access 2010 12
Microsoft Excel 2010 13
Microsoft InfoPath 2010 14
Microsoft OneNote 2010 16
Microsoft Outlook 2010 17
Microsoft PowerPoint 2010 19
Microsoft Project Professional 2010 20
Microsoft Publisher 2010 22
Microsoft SharePoint Workspace 2010 23
Microsoft Visio 2010 (Premium, Professional, Standard) 24
Microsoft Word 2010 25
Office 2010 suites 27
Comparisons of Office 2010 editions 27
Getting started with the deployment of Office 2010 29
About the Office 2010 Resource Kit 29
What’s new for IT professionals in Office 2010 30
Licensing and volume activation 30
Office 2010 64-bit editions 31
Security changes 31
Office Customization Tool changes 32
Application virtualization 32
Additional resources 33
Setup changes prior to Office 2010 34
Changes introduced in the 2007 Office system 34
Setup architecture 34
Setup features comparison 35
File formats, Security, User Interface, Object Model, and application changes in 2007 Office 38
File format 39
Security 39
User Interface 40
Object model 40
Access 2007 40
Excel 2007 40
Outlook 2007 41
Word 2007, PowerPoint 2007, and OneNote 2007 41
Setup architecture overview for Office 2010 42
Setup process 43
Setup sequence of events 43
Run Setup 43
Check prerequisites 44
Read XML data 45
Build the feature tree 46
Create a local installation source on the user's computer 46
Install Office 47
Apply the customization file 47
Apply software updates 48
Including more than one product on the installation point 48
Running Setup interactively 48
Language-neutral design 49
Language versions of Office 49
Language packs for Office 50
Streamlined customization model 51
Using the Office Customization Tool 51
Customizing a new installation 51
Making changes to an existing Office installation 52
Using the Config.xml file to customize Office 52
Using Setup command-line options 53
Using Group Policy 53
Required local installation source 54
Creating a local installation source on users' computers 55
Deploying the local installation source by itself 55
Consolidated update process 56
Applying Office updates during new installations 56
Updating existing Office installations 57
64-bit editions of Office 2010 58
Supported Windows operating systems 59
Architecture-specific folders and customization tools 59
Supported scenarios 60
Deployment considerations 61
Advantages 61
Disadvantages 62
General feature deprecations 63
Considerations for MAPI applications for Outlook 63
Blocking and nonblocking Office applications in 64-bit installations 64
Applications that block a 64-bit Office 2010 installation 64
Applications that do not block a 64-bit Office 2010 installation 64
Setup process 65
Assessing your current environment for application compatibility 67
Technical diagrams for Office 2010 69
Models 69
Getting help with Office 2010 72
Support options in the Backstage 72
Other support options 72
Planning the deployment of Office 2010 Beta 73
Assess the environment for Office 2010 74
Assessment tools for Office 2010 75
Assessment tools 75
Application compatibility overview for Office 2010 80
Application compatibility and Office 2010 80
Office Environment Assessment Tool 82
Office Code Compatibility Inspector 82
Office Migration Planning Manager 82
Application Compatibility Assessment and Remediation Guide 82
ISV Application Compatibility Visibility Program 83
Application compatibility community resources 83
Application compatibility assessment and remediation guide for Office 2010 84
Office customizations 85
Macros 85
Templates 86
Add-ins 86
Automation 86
Plan for compatibility testing 87
Planning activities 87
Identify stakeholders 88
Assign roles 88
Assessment planning 89
Classification of applications 90
Types of deployments 91
Test planning 91
Remediation planning 91
Assess the environment 92
Preassessment tasks 93
Identify and interview business units 93
Identify systems and servers 94
Scan the environment 94
Office Migration Planning Manager (OMPM) 94
Office Environment Assessment Tool (OEAT) 95
Microsoft Assessment and Planning Toolkit 96
Additional tools 97
Remediate compatibility issues 97
Assess the results 97
Prioritize applications 98
Identify known issues 99
Deprecations 99
Feature changes 99
64-bit vs. 32-bit platforms 99
Test for compatibility issues 101
General LOB application testing 102
Office add-in testing 103
Macros and scripts testing 104
Office automation testing 105
Remediate issues 105
Get updates from vendors 106
Update internal applications 106
Using Microsoft Office Code Compatibility Inspector 106
Using parallel installation or virtualization 107
Test and pilot remediations 108
Lab tests 108
Pilot 109
References and resources 110
Office Environment Assessment Tool (OEAT) quick start guide for Office 2010 111
Steps to configure OEAT 111
Identify users and systems 112
Create the network share 112
Configure OEAT settings 112
Create a script 115
Compile scan results 116
How OEAT works 116
OEAT command-line parameters 117
Office Environment Assessment Tool (OEAT) user's guide for Office 2010 118
Planning an Office deployment by using OEAT 118
Information provided by OEAT 119
Assessing the results 120
Additional reports 120
Steps to configure OEAT 120
Identify users and systems 121
How to identify users and systems to scan 121
Define a significant sample 121
Configure tool prerequisites 121
OEAT required permissions 121
Create the network share 122
Configure OEAT settings 124
Create a script 126
Compile scan results 127
Deployment scenarios 127
Scenario 1 128
Scenario 2 128
Scenario 3 128
View OEAT data 128
Review OEAT data 129
View top 10 add-ins 129
Organize results by application 129
View unknown add-ins 129
Configuration management 130
Charts and pivot tables 130
Microsoft Office Code Compatibility Inspector user's guide 131
About the Inspector 131
Installation 132
Displaying the Developer tab 132
Enable VBA project access 132
Inspecting VBA code 132
Inspecting Visual Studio code 135
Using the Inspector 139
Removing comments in VBA 139
Removing comments in Visual Studio 139
Additional resources 140
Office Migration Planning Manager (OMPM) overview for Office 2010 141
OMPM components 142
Office Migration Planning Manager Table of Requirements 142
Client system requirements 142
How the OMPM File Scanner works 144
Using OMPM tools 145
Plan desktop configurations for Office 2010 146
Planning overview for Outlook 2010 147
Determining an organization’s needs 147
Upgrade or initial installation 147
Migrating data 147
Remote and roaming users 148
Multilingual requirements 148
Client and messaging server platforms 148
Choosing when and how to install Outlook 149
Customizing Outlook settings and profiles 149
Configuring subscriptions and other sharing features 149
Using Outlook with Terminal Services 150
Collaboration Data Objects dependencies 150
AutoArchive 150
Retention policies 151
Security and privacy considerations 151
The Trust Center for Office 151
Limiting viruses and junk e-mail messages for users 151
Configuring cryptographic features 152
Restricting permission on e-mail messages 152
Outlook 2010 and e-mail protocols and servers 152
Upgrading from an earlier version of Outlook 153
Upgrading with Cached Exchange Mode enabled 153
Additional issues to consider when planning an upgrade 153
Upgrading from other mail and scheduling programs 154
Determine when to install Outlook 2010 155
Installing Outlook with Office 155
Installing Outlook before Office 155
Advantages of installing Outlook before Office 156
Disadvantages of installing Outlook before Office 156
Installing Outlook after Office 156
Advantages of installing Outlook after Office 156
Disadvantages of installing Outlook after Office 157
Staging an Outlook deployment 157
Advantages of staging a deployment 157
Disadvantages of staging a deployment 157
Plan a Cached Exchange Mode deployment in Outlook 2010 158
How Cached Exchange Mode can help improve the Outlook user experience 158
Outlook features that can reduce the effectiveness of Cached Exchange Mode 159
Synchronization, disk space, and performance considerations 161
Manual synchronization of Exchange accounts no longer necessary 161
Offline Address Book access advantages 161
Offline folder (.ost file) recommendations 162
Managing performance issues 162
Managing Outlook folder sharing 163
Public Folder Favorites considerations 163
Managing Outlook behavior for perceived slow connections 163
Options for staging a Cached Exchange Mode deployment 164
Upgrading current Cached Exchange Mode users to Outlook 2010 166
Deploying Cached Exchange Mode to users who already have .ost files 167
Using Group Policy to enforce Cached Exchange Mode settings 167
Additional resources 167
Plan for security and protection in Outlook 2010 169
Plan for limiting junk e-mail in Outlook 2010 170
Overview 170
Supported account types 171
Support in Exchange Server 171
Configuring the Junk E-mail Filter user interface 171
Deploying default Junk E-mail Filter lists 173
Configuring Automatic picture download 174
Plan for Project 2010 176
Prerequisites for Project 2010 176
Installing Project 2010 176
Plan for SharePoint Workspace 2010 177
Plan topology for SharePoint Workspace 2010 177
SharePoint Workspace as a SharePoint client only 179
SharePoint Workspace as a peer collaboration client 180
SharePoint Workspace as a SharePoint and peer collaboration client 181
Groove Server and SharePoint Workspace as a managed collaboration system 183
Plan network settings for SharePoint Workspace 2010 184
Plan for capacity 186
Plan for security 186
Plan for authentication 187
Plan for alternate access mapping 187
Plan for performance monitoring and throttling 188
Plan for SharePoint list and library actions and settings 188
Plan for search 188
Plan for SharePoint Workspace backup and recovery 189
Plan security for Office 2010 191
Security overview for Office 2010 193
Layered defense is key 194
A four-layer approach 194
Enhanced hardening countermeasures 196
Integrity countermeasures 196
Confidentiality countermeasures 196
Helping users make better security decisions 197
Giving the administrator full control 200
Migrating security and privacy settings from Office 2003 201
Understand security threats and countermeasures for Office 2010 207
Information security risks 207
Threats to desktop productivity applications 208
Active content threats 208
Unauthorized access threats 209
External content threats 209
Browser threats 210
Zero-day exploit threats 210
Default countermeasures in Office 2010 211
ActiveX control settings 211
Add-in settings 212
Cryptography and encryption settings 212
Data Execution Prevention settings 212
Digital signature settings 212
External content settings 212
File Block settings 212
Office File Validation settings 213
Password complexity settings 213
Privacy options 213
Protected View settings 214
Trusted Documents settings 214
Trusted Locations settings 214
Trusted Publishers settings 214
VBA macro settings 214
Plan Protected View settings for Office 2010 216
About planning Protected View settings 216
Default behavior of Protected View 216
Change Protected View behavior 217
Prevent files from opening in Protected View 217
Force files to open in Protected View 218
Use File Block to force files to open in Protected View 218
Use Office File Validation settings to force files to open in Protected View 218
Add files to the list of unsafe files 219
Plan Office File Validation settings for Office 2010 220
About planning Office File Validation settings 220
Turn off Office File Validation 221
Change document behavior when validation fails 222
Turn off Office File Validation reporting 222
Plan security settings for add-ins for Office 2010 224
About planning add-in settings 224
Disable add-ins on a per-application basis 225
Require that application add-ins are signed by trusted publisher 225
Disable notifications for unsigned add-ins 225
Plan security settings for VBA macros for Office 2010 227
About planning VBA and VBA macro settings 227
Change the security warning settings for VBA macros 228
Disable VBA 229
Change how VBA macros behave in applications that are started programmatically 229
Change how encrypted VBA macros are scanned for viruses 230
Related VBA macro settings 231
Plan privacy options for Office 2010 232
About planning privacy options 232
Suppress the Welcome to Microsoft Office 2010 dialog box 233
Configure privacy options 234
Related privacy options 235
Plan for multilanguage deployment of Office 2010 236
Plan Setup 236
Understanding the Setup logic for Shell UI language 237
Plan customizations 238
Methods of customizing language settings 239
Enable users to view the new language settings on first open 239
Customize language-specific settings related to user locale 240
Plan for proofing tools 240
Determining the method for deploying proofing tools 241
Customizing Setup for Office 2010 Proofing Tools Kit 241
Syntax 242
OptionState attributes 242
Example Config.xml file for Office 2010 Proofing Tools Kit 242
Precaching the local installation source for the Office 2010 Proofing Tools Kit 245
Plan for virtualization 246
Plan a migration and upgrade strategy for Office 2010 247
Plan an upgrade to Office 2010 248
Overview of the upgrade process 248
Compare upgrade options and understand data migration 249
Migrate documents 250
Migrate user data registry keys in Office 2010 251
Microsoft Office 2003 settings 251
Microsoft Office 2007 settings 257
Choose an option for deploying Office 2010 263
Deployment options 263
Network share 263
Group Policy startup scripts 263
Managed deployment 263
Applicationvirtualization 264
Presentationvirtualization 264
Plan for volume activation of Office 2010 265
Volume activation overview for Office 2010 266
Volume Licensing overview 266
Changes in activation policy 266
Why is activation necessary? 267
Privacy 267
Office Activation Technologies 267
Key Management Service (KMS) 267
Office 2010 KMS clients 268
Multiple Activation Key (MAK) 268
KMS activation schedule 269
Volume License product keys 269
Plan volume activation of Office 2010 270
Review activation models 270
Key Management Service (KMS) 271
Multiple Activation Key (MAK) 272
Plan a KMS deployment 273
Plan a MAK activation 274
Configuration and deployment of Office 2010 Beta 275
Configure and deploy volume activation of Office 2010 276
Deploy volume activation of Office 2010 277
Prepare and configure the Office 2010 client for MAK activation 277
Install and configure the KMS host 279
Configure DNS 282
Tools to configure client computers in Office 2010 284
Use KMS for computers running Windows and Office 2010 clients 284
Configure the KMS client 284
Separate KMS hosts for computers running Windows and Office 2010 clients 286
Same KMS host on a computer running Windows Server 2003 286
Same KMS host on a computer running Windows 7 or Windows Server 2008 R2 286
Volume activation quick start guide for Office 2010 288
Differences between Windows and Office activation 288
Scenarios for Office 2010 volume activation 289
Scenario 1: The individual user who wants to activate Office 2010 and get started quickly 289
Scenario 2: The IT professional who wants to deploy Office 2010 to five or fewer computers 290
Scenario 3: The IT professional who wants to try MAK proxy activation through VAMT 2.0 291
Scenario 4: The IT professional who wants to deploy Office 2010 to more than five computers 291
Obtain Office 2010 292
Office 2010 volume activation methods 292
KMS activation 292
MAK activation 292
Deploy Office Activation Technologies 293
Install and configure the KMS host 294
Configure DNS 298
Use KMS for computers running Windows and Office 2010 clients 298
Configure the KMS client 298
Separate KMS hosts for computers running Windows and Office 2010 clients 299
Same KMS host on a computer running Windows Server 2003 300
Same KMS host on a computer running Windows 7 or Windows Server 2008 R2 300
Prepare the infrastructure for Office 2010 301
Create a network installation point for Office 2010 302
Create the network installation point 302
Replicate the network installation point 303
Secure the network installation point 304
Customize the installation for Office 2010 305
Customization overview for Office 2010 306
Office Customization Tool 306
Config.xml file 307
Setup command-line options 308
Configure user and computer settings 309
Configuring user and computer settings by using Group Policy 309
Configuring user and computer settings by using the Office Customization Tool 311
Office 2010 licensing and activation 311
Summary of client customization tasks 312
Customize setup for Office 2010 315
Customize Office 2010 316
Customize Office 316
Customize Setup before installing Office 2010 318
Customize Setup 318
Install Office silently 320
Configure feature installation states for Office 2010 322
Configure installation states 322
Configure user settings for Office 2010 326
Configure user settings 326
Create different configurations of Office 2010 for different groups of users 328
Create custom configurations for a group of users 328
Create a custom configuration for a group of users by using a separate installation folder 328
Import an Office 2010 Setup customization file 331
Overview 331
Import a Setup customization file 332
Import languages to an existing installation 332
Configure a silent installation of Office 2010 by using Config.xml 334
Modify the Config.xml file to configure a silent installation 334
Run arbitrary commands with installations of Office 2010 336
How it works 338
Customize specific features in Office 2010 339
Customize language setup and settings for Office 2010 340
Overview 340
Before you begin 341
Deploy a default language version of Office 341
Specify which languages to install 342
Deploy different languages to different groups of users 343
Identify installed languages 344
Customize language settings 344
Use Group Policy to enforce language settings 344
Use a Setup customization file to specify default language settings 345
Use the Language Preferences tool to modify language settings 345
Customize and install the Office 2010 Proofing Tools Kit 346
Customize the Office 2010 Proofing Tools Kit 346
Installing the Office Proofing Tools Kit 2010 on a single computer 347
Configure Outlook 2010 348
Configure Outlook Anywhere in Outlook 2010 349
Overview 349
Before you begin 349
Use the OCT to configure Outlook Anywhere 350
Use Group Policy to lock down Outlook Anywhere settings 351
Verification 351
Configure Cached Exchange Mode in Outlook 2010 352
Overview 352
Before you begin 353
Configure Cached Exchange Mode 353
Configure Exchange Server send/receive settings in Outlook 2010 357
Overview 357
Before you begin 357
Create and configure Send/Receive groups in Outlook 2010 358
To create and configure Send/Receive groups for Exchange accounts and folders 358
Configure multiple Exchange accounts for Outlook 2010 359
Overview 359
Before you begin 359
Add multiple Exchange accounts to a profile 359
Modify or remove Exchange accounts on a profile 360
Configure security and protection in Outlook 2010 361
Configure junk e-mail settings in Outlook 2010 362
Overview 362
Before you begin 363
Create and deploy Junk E-mail Filter lists 363
Configure the Junk E-mail Filter 364
Configure automatic picture download 365
Customize Outlook profiles by using an Outlook Profile (PRF) file 367
Overview 367
Before you begin 367
Procedures 367
Create a .prf file 368
Manually edit a .prf file 368
Apply a .prf file 372
Configure SharePoint Workspace 2010 373
Configure and customize SharePoint Workspace 2010 374
Before you begin 374
Review customization options for SharePoint Workspace 2010 375
Control use of Groove workspaces 375
Enable IPv6 376
Prefer IPv4 376
Remove legacy files and registry settings 376
Prevent Windows Search crawling for SharePoint Workspace 376
Force Secure Socket Layer protection for external connections 377
Customize SharePoint Workspace in a managed environment 377
Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings 377
Verify installation 379
Test SharePoint Workspace connections 380
Before you begin 380
Test SharePoint Workspace synchronization with SharePoint Server 380
Test Groove workspace synchronization among peer clients 382
Deploy Office 2010 384
Run Setup from a network installation point 386
Install an Office 2010 product 386
Precache the local installation source for Office 2010 388
Deploy the local installation source 388
Run Setup from the local installation source to install Office 2010 390
Run Setup 390
MSOCache folder 391
Office product download codes 391
Deploy Office 2010 to users who are not administrators 392
Logging on as an administrator 393
Deploying Office by using Group Policy computer startup scripts 393
Using a software management tool 393
Using application virtualization 393
Deploy Office 2010 with limited network capacity 394
Recommended solution 394
How this solution works 394
Deploy Microsoft Silverlight with Office 2010 396
Maintaining and updating Office 2010 Beta 397
Apply updates for Office 2010 398
Add or remove languages after deploying Office 2010 399
Overview 399
Before you begin 400
Modify an existing installation 400
Deploy language packs 402
Remove language packs 403
Identify installed languages 404
Manage users' configurations for Office 2010 405
Change users' configurations after installing Office 2010 406
Overview 406
Customize an existing Office installation 407
How customization works 407
Applying Setup customization .msp files to existing installations 408
Setup customization patch sequencing 408
Security and protection for Office 2010 Beta 409
Overview articles 409
Planning articles 409
Configuration articles 410
Troubleshooting for Office 2010 Beta 411
Troubleshoot volume activation for Office 2010 412
Activation error codes 412
General activation 412
Users see notification dialogs to activate 412
Information in the Backstage view is not updated 413
The Office 2010 KMS client does not activate 413
Troubleshoot SharePoint Workspace 2010 416
SharePoint Workspace and SharePoint Server are not synchronizing correctly 416
SharePoint Workspace users receive messages about freeing disk space 416
Technical reference for Office 2010 Beta 417
Setup reference for Office 2010 418
Setup properties in Office 2010 419
Property quick reference 419
Available properties 421
Replaced properties 422
Blocked properties 424
Office activation 424
Setup command-line options for Office 2010 425
/admin 425
Example 425
/adminfile [path] 425
Example 426
/config [path] 426
Example 426
/modify [ProductID] 426
Example 426
/repair [ProductID] 427
Example 427
/uninstall [ProductID] 427
Example 427
Config.xml file in Office 2010 429
Config.xml element quick reference 430
How Setup uses Config.xml 431
Config.xml file format 431
Config.xml element reference 433
Configuration element 433
Syntax 433
Attributes 433
Remarks 433
Example 434
AddLanguage element 434
Syntax 434
Attributes 434
Remarks 435
Example 436
ARP element 436
Syntax 436
Attributes 436
Command element 437
Syntax 437
Attributes 437
Remarks 439
Examples 440
COMPANYNAME element 440
Syntax 440
Attributes 440
Example 441
Display element 441
Syntax 441
Attributes 441
Remarks 442
Example 443
DistributionPoint element 443
Syntax 443
Attributes 443
Remarks 444
Example 444
INSTALLLOCATION element 444
Syntax 444
Attributes 444
Remarks 444
Example 444
LIS element 445
Syntax 445
Attributes 445
Remarks 445
Example 446
Logging element 446
Syntax 446
Attributes 446
Remarks 447
Example 447
MinOSRequirement element 447
Syntax 448
Attributes 448
Remarks 448
OptionState element 448
Syntax 449
Attributes 449
Remarks 449
Example 449
PIDKEY element 450
Syntax 450
Attributes 450
Remarks 450
Example 451
RemoveLanguage element 451
Syntax 451
Attributes 451
Remarks 451
Example 451
Setting element 451
Syntax 452
Attributes 452
Remarks 452
Examples 453
SetupUpdates element 453
Syntax 453
Attributes 453
Remarks 453
Example 454
USERINITIALS element 454
Syntax 454
Attributes 454
Example 454
USERNAME element 454
Syntax 454
Attributes 454
Remarks 454
Example 455
Sample Config.xml file 455
Office Customization Tool in Office 2010 457
Overview of the Office Customization Tool 457
New Office Customization Tool features in Office 2010 460
Architecture-specific versions of the Office Customization Tool 461
Importing Office Customization Tool .msp customization files 461
Configuring Setup, Features, Additional content, and Outlook settings 462
Setup 462
Installation location and organization name 463
Additional network sources 463
Licensing and user interface 464
Remove previous installations 466
Add installations and run programs 466
Office security settings 467
Modify Setup properties 471
Features 471
Modify user settings 471
Set feature installation states 473
Additional content 475
Add files 476
Remove files 477
Add registry entries 477
Remove registry entries 479
Configure shortcuts 480
Outlook 484
Outlook Profile 484
Add Accounts 485
Exchange settings 486
Export Settings 489
Specify Send/Receive Groups 489
International reference for Office 2010 493
Companion proofing languages for Office 2010 494
Identify companion proofing languages 494
Language identifiers and OptionState Id values in Office 2010 496
Language identifiers 496
Proofing Tools Config.xml OptionState Id values 498
Mixed language versions of Office 2010 501
Applications and language availability 501
Language Interface Packs 502
Product and feature changes in Office 2010 506
Changes in Office 2010 508
What’s new 508
What’s changed 508
Insert Clip Art task pane and Clip Organizer 508
HTML editor 508
Legacy brightness and contrast 508
Language Preferences 509
What’s removed 509
Insert Clip Art task pane and Clip Organizer 509
Symbol input add-in: East Asia versions of Office 2010 509
InterConnect 510
Office Startup Assistant 510
Office Diagnostics 510
Document workspaces 510
MSXML5 support 511
Changes in Access 2010 512
What’s new 512
Share a database on the Web 512
Export to .pdf and .xps 512
Connect to a Web service as an external data source 513
Backstage view 513
What’s changed 513
Backward compatibility between Access 2010 and Access 2007 513
Enhanced security 513
Support for SQL Server 2008 data types 513
What’s removed 514
Calendar control (mscal.ocx) 514
Microsoft Replication Conflict Viewer 514
Snapshot file format 514
Data access pages 514
Lotus 1-2-3, Paradox, Jet2.x, and Red2 IISAM 515
Migration considerations 515
VBA settings migration 515
Changes in Excel 2010 516
What’s new 516
In Addressing Customer Needs 516
High performance computing clusters 516
Macro recording support for chart elements 517
XLM/VBA gaps closing 517
UDFs run asynchronously 517
In Business Intelligence 517
Sparklines 518
Slicers 518
Microsoft SQL Server PowerPivot for Excel add-in 518
Calculation feature improvements 518
New version of Solver 518
New Statistical functions 519
In Excel Web App 519
Multiple user editing 519
Excel Services enhancements 519
In Office Suite Changes 520
Backstage view 520
Excel 2010 64-bit Advantages 520
What’s changed 520
In Addressing Customer Needs 520
Compatibility mode tool 521
File loading performance 521
In Business Intelligence 521
PivotTable enhancements 521
Filtering 522
Conditional formatting 522
Icon sets 522
Data bars 522
OfficeArt controls and objects 522
Pattern fills 523
In Strategic Improvements 523
Charting enhancements 523
What’s removed 524
In Addressing Customer Needs 524
Clip Art task pane Search in Box 524
ClipArt task pane Clip Organizer 524
In Calculation features 524
Conditional Sum Wizard 525
Lookup Wizard 525
In Office Suite Changes 525
Smart tags now “Additional actions” 525
Calendar Control 525
Migration considerations 525
MSXML5 525
VBA settings migration 526
Changes in InfoPath 2010 527
What’s removed 527
Data importer framework 527
Data set change tracking 527
InfoPath Form Designer Group Policy template settings 527
Form template exporter 527
Form template samples 527
Human Workflow Services integration 528
Installable form templates 528
Receive and Submit Web service connection 528
Sample data 528
Script code development environment 528
Support for Microsoft XML Parser 5 528
Changes in OneNote 2010 529
What’s new 529
Fluent UI 529
The ribbon 529
Backstage view 529
Language preferences 530
File format 530
Improved access to information 530
Search, Outlook integration, organization, and editing improvements 530
Sharing and collaboration features 531
Support for touch-enabled computers 532
What’s changed 532
Task pane replacements 532
What’s removed 532
Outlining features and body text 533
SimpleImporter API 533
Start Live Session 533
Join Live Session 533
Current Live Session 533
Create Outlook Appointment and Create Outlook Contact 533
Task Panes removed 533
Migration considerations 534
OneNote 2010 availability 534
OneNote 2010 file format 534
Upgrading OneNote 2007 notebooks 535
Upgrading OneNote 2003 notebooks 535
OneNote notebook sharing 535
OneNote user data settings migration 536
Changes in Outlook 2010 537
What’s new 537
64-bit editions 537
Bitness registry key 537
Calendar Preview in meeting requests 538
Conversation actions 538
Quick Steps 538
Multiple Exchange accounts 538
Roaming AutoComplete list 538
The ribbon 538
Features available with Office Communicator 2007 R2, Office Communicator Server 2007 R2, or later versions 538
Features available with Microsoft Exchange Server 2010 539
What’s changed 540
Conversation view 540
Improved IMAP support 540
Faster performance 540
Menu and commands 540
Search tools 541
Improved in Outlook 2010 with Exchange Server 2010 541
What’s removed 542
ANSI offline Outlook data files (.ost) for Exchange synchronization 542
AutoArchive-based retention 542
Calendar rebasing tool 542
Customization of Contact Activity Search folders 542
DAV connectivity for HTTP account types 543
Exchange 2000 connectivity 543
Exchange Message Security feature support 543
Most Recently Used list 543
Outlook integrity check tool (.ost) 543
Photo resize options 544
Postmarking 544
Preview of published Office Online calendars 544
Quick View 544
Remote Mail 544
Search Toolbar add-in 544
Send Link to This Folder 545
Send Options 545
Shade group headings 545
Third-party Exchange client extensions do not load 545
Web browser support 545
Migration considerations 546
Outlook data files (.pst and.ost) 546
Outlook profile file (.prf) 546
Reverting to Office 2007 from Office 2010 546
VBA settings migration 547
Changes in PowerPoint 2010 548
What’s new 548
Fluent UI 548
The ribbon 548
Backstage view 548
File format 549
Protected View 549
Collaboration and sharing features 549
Presentations to live and virtual audiences 549
Working with text and objects 549
What’s changed 550
Arrange Group 550
Insert a shape 550
Selection pane 550
What’s removed 550
Maximum sound file size 550
Save as Web Page 551
Migration considerations 551
PowerPoint Presentation Files (.ppt/.pptx) 551
Storing or sharing files 552
Presentation security 552
PowerPoint Viewer 552
Macro recorder 552
VBA settings migration 553
Changes in Project 2010 554
What’s new 554
Fluent UI 554
Backstage view 554
Team Planner 554
Synchronization with SharePoint lists 555
Manual scheduling 555
Placeholder tasks 555
Inactive tasks 555
Top-down summary 555
Compare projects 555
Timeline 556
Enhanced copy and paste 556
Excel-like features 556
Find commonly used commands quickly 556
The view slider 556
Backwards compatibility 556
What’s changed 557
Application settings 557
What’s removed 557
Custom forms 557
OWC resource availability graphs 557
Add-ins, sample macros, and project guide 557
Save as Excel Pivot Table 558
Migration considerations 558
VBA settings migration 558
Changes in Publisher 2010 560
What’s new 560
The ribbon 560
Backstage view 560
Simplified, cleaner workspace 560
Integrated print and preview experience 561
Save file as .pdf or .xps 561
64-bit edition 561
What’s changed 561
Improved picture technology 561
Object alignment 562
Improved access to templates and building blocks online 562
Catalog merge 562
What’s removed 562
Web mode 562
Outdated application settings 562
Migration considerations 562
VBA settings migration 563
Changes in SharePoint Designer 2010 564
What’s removed 564
Contributor Settings 564
Database features 564
Layout tables 565
Microsoft Script Editor (MSE) 565
Publish, backup, and restore remote Web site 565
Back up a Web site 565
Restore a Web site 566
FTP 566
Import Web site wizard 566
Publish Web site 566
Web package 566
Views 567
Reports view 567
Navigation view 567
Hyperlinks view 567
Changes in SharePoint Workspace 2010 568
What’s new 568
SharePoint integration 568
SharePoint Workspace user interface 568
What’s changed 568
SharePoint Workspace product 568
Tools location 569
Groove logon password and smartcard 569
Logon credentials 569
Workspace Manager 569
What’s removed 569
Alerts on contacts 569
E-mail invitation 570
Groove Forms Designer 570
Groove InfoPath Forms 570
Custom tools 570
Groove Workspace Explorer contact list 570
Groove Workspace Explorer workspace list 570
Lite Chat invitations 571
Connect tool 571
Navigate Together feature 571
Communicator 571
Suspended icon overlay 571
Tooltip information about user entering tool 571
Multiple identities 571
Push-to-talk and voice memos 572
Ink chat 572
Logon-related features 572
Migration considerations 572
Changes in Visio 2010 574
What’s new 574
Fluent UI 574
The ribbon 574
Backstage view 574
ShapeSheet IntelliSense 575
What’s changed 575
Status bar 575
Customize ink pens 575
Color by Value 576
Visual Studio Add-in/Add-on Wizard 576
What’s removed 576
ShapeStudio 576
Status bar 576
Find Shape feature 577
Stencil docking 577
Migration considerations 577
Process Repository 577
Publish a process diagram to a repository 578
Changes in Word 2010 580
What’s new 580
Fluent UI 580
The ribbon 580
Backstage view 580
File format 581
Protected View 581
Collaboration and sharing features 581
Document authoring and graphic enhancements 581
What’s changed? 581
Cut, copy, and paste 582
Document map 582
Print preview 582
RTF file format 583
Smart tags 583
Views 583
What’s removed 583
Person Name removal of smart tag 583
AutoSummary 583
Migrations considerations 584
Migrating Word files 584
Compatibility Checker 585
Embedded Word 2010 objects 585
Equations 585
SmartArt graphics 585
Migration considerations from Office 97-2003 to Office 2010 585
VBA settings migration 586
SharePoint Workspace 2010 reference 587
Group Policy for SharePoint Workspace 2010 588
Office Customization Tool settings for SharePoint Workspace 2010 591
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:
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:
itspdocs@
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:
Product evaluation and getting started with Office 2010 Beta
Microsoft Office 2010 provides features that help IT administrators configure, validate, deploy, and protect Office installations in their organizations. This section introduces some of the new features and improvements in the Microsoft Office 2010 suites that are relevant to IT professionals.
In this section:
|Article |Description |
|What's new in Office 2010 |Describes some of the new features and improvements in Office 2010 |
| |that are relevant to IT professionals. |
|System requirements for Office 2010 |Describes the system requirements for the products in the Microsoft |
| |Office 2010 suites. |
|Office 2010 suites |Describes the editions of the Microsoft Office 2010 suites that are |
| |available, and provides an overview of the licensing requirements. |
|Getting started with the deployment of Office 2010 |Describes the structure of the documentation in the Office Resource |
| |Kit for Office 2010 and also describes the new features and |
| |improvements in the Microsoft Office 2010 suites that are relevant to|
| |IT professionals. |
|Setup architecture overview for Office 2010 |Provides an overview of the Setup architecture for Office 2010, setup|
| |sequence of events, language-neutral design and deployment of |
| |multiple languages, customization methods, required local |
| |installation source, and updates process. |
|64-bit editions of Office 2010 |Provides information about 64-bit versions of Office 2010 products, |
| |including supported scenarios, deployment considerations, and an |
| |overview of the Setup process. |
|Overview of the Office user interface in Office 2010 |Provides information about the Microsoft Office Fluent user interface|
|((UI) in Office 2010, including the ribbon, the Quick Access Toolbar, |
|5ffe2(Office.14).aspx) |and the new Backstage view. |
|Technical diagrams for Office 2010 |Provides visual representations or models of recommended solutions |
| |for deploying Office 2010. |
|Getting help with Office 2010 |Describes some of the support options that are available for the |
| |Office 2010 suites. |
See Also
Product and feature changes in Office 2010
SharePoint Workspace 2010 overview
What's new in Office 2010
Microsoft Office 2010 provides features that help IT administrators configure, validate, deploy, and protect Office installations in their organizations. This article introduces some of the new features and improvements in the Microsoft Office 2010 suites that are relevant to IT professionals.
In this article:
• New and updated features in Office 2010
• File formats
• Edition comparison
• Differences between Microsoft Office versions
• What’s new for IT Professionals
New and updated features in Office 2010
The following are highlights of Office 2010.
Fluent user interface
The Office 2010 Fluent user interface (UI) lets you support users more efficiently. It contains updates to the ribbon and a new Backstage view that displays the details of files and functionalities, even letting you create a custom UI, all within the XML schema.
The ribbon organizes commands in a more usable way by presenting them as a set of tabs. Each contextual tab represents a task area relevant to a particular Office product. The ribbon is improved in Office 2010 and is included in all Office 2010 applications.
Backstage view
The Microsoft Office Backstage view in Office 2010 replaces the Microsoft Office Button of the 2007 Microsoft Office system. The Backstage view enables you to create a custom UI, similar to within the ribbon, and to add elements such as workflow or task information that is specific to an organization’s needs. The Backstage view is available in all Office 2010 applications, and replaces the File menu of earlier Microsoft Office versions.
Silverlight
Microsoft Silverlight is a technology that works in the browser and on the desktops that brings many Microsoft Office experience to life with amazing video, animations, and interactivity. We recommend that you install Silverlight along with Office to improve the information worker user experience with Office 2010. Specifically, Silverlight enables better online experience with , powers the Office 2010 interactive guides (available with Office 2010), improves the user experience of Microsoft SharePoint Server 2010, improves the performance of Office Web Companion applications, and helps with the process of uploading Office documents to cloud services.
File formats
Microsoft Office 2003 introduced a format based on extensible markup language (XML) that enabled you to understand the details of a document. The 2007 Office system made XML the default file format so that you could easily work with your documents. The data that was contained in the XML file listed the content in a document, and the description included any settings that were needed for the document to work within the application. In addition to supporting about 20 different document formats including XML Paper Specification (XPS), Portable Document Format (PDF) 1.5, PDF/A and Open Document Format (ODF) v1.1. Office 2010 continues to support XML.
The XML format provides advantages such as easier data mining and content reuse; faster document creation from different data sources; reduction of the size of Excel, PowerPoint, and Word files; and improved data recovery of corrupted files.
ODF users can save documents in version 1.1 of the ODF for Word, Excel and PowerPoint. Users can open, edit and save files in the OpenDocument Text (*.odt), OpenDocument Spreadsheet (*.ods), and OpenDocument Presentations (*.odp) formats.
Edition comparison
Five editions of Office 2010 suites are available — three user versions and two business versions. For more information, see Office 2010 suites.
Differences between Microsoft Office versions
Within each application, Office 2010 has improved functionality in many areas. When the 2007 Microsoft Office system was released, a significant difference from Office 2003 was the introduction of the ribbon in the user interface (UI) for Microsoft Office Access 2007, Microsoft Office Excel 2007, Microsoft Office PowerPoint 2007, Microsoft Office Word 2007, and parts of Microsoft Office Outlook 2007. The UI changed from a collection of menus and toolbars to a single ribbon mechanism. The Office 2010 suites maintain the ribbon and have some new features.
The ribbon is now available across all products of the Office 2010 suites so moving from one application to another is seamless. In addition to changes in the ribbon, the Office 2010 suites background is now a gray color, by default, whereas the 2007 Office system background was blue.
The following table describes the differences in UI elements between Office 2010, the 2007 Office system, and Office 2003.
|UI element |Office 2010 |Office 2007 |Office 2003 |
|Menus and tabs |The ribbon replaces menus and |The ribbon replaces menus and |Menus and toolbars only are |
| |toolbars across all products of |toolbars in Access 2007, Office |available. |
| |Office 2010 and can be fully |Excel 2007, PowerPoint 2007, Word| |
| |customized. |2007, and parts of Outlook 2007. | |
|Task panes |Groups of commands on the ribbon |Groups of commands on the ribbon |Basic task pane. |
| |and the ability to customize. |and the ability to customize. | |
|Quick Access Toolbar (QAT) |Fully customizable. |Introduced in 2007. |Not available. |
|Backstage view |More tools outside the document |Limited tools that can be |Limited tools on the File menu |
| |viewing window. |accessed through the Microsoft | |
| | |Office Button. | |
|Digital signatures |Found in the Backstage view under |Formatted with XMLDSig, found |Found under Tools / Options / |
| |Information about Document / |under File / Finalize Document / |Security / Digital Signatures |
| |Protect Document. |Signatures. | |
|Smart Art |Improved from the 2007 version. |Design tools available in all |Not available. |
| | |Microsoft Office applications. | |
|Open Formats (*.odt) OpenDocument |Included in this version. |Added in 2007 Office system |Not available. |
|Text | |Service Pack 2 (SP2). | |
|Windows Live Writer integration |Blog posting options available in |Not available. |Not available. |
| |the application. | | |
|Spelling checker |The spelling checker is now |Basic spelling checker. |Basic spelling checker. |
| |integrated with automatic | | |
| |correction. | | |
|Paste Preview |A live preview before you commit |Paste, Undo, Paste. |Basic Paste capabilities. |
| |to Paste. Avoids having to use the| | |
| |Undo button. | | |
|Print |The Backstage combines Print with |Microsoft Office Button, Print |Basic Print option on the File |
| |Print Preview, Page Layout and |with limited printing tools |menu. |
| |other print options. |spread across several commands. | |
|Sparklines |A miniature chart inserted into |Dynamic charts and chart types. |Three-dimensional (3-D) charting.|
| |text or embedded in a spreadsheet | | |
| |cell to summarize data. | | |
|E-mail Essentials |Conversation, Cleanup, Ignore |Not available. |Not available. |
| |Thread, and Mail Tips for when a | | |
| |person is out of the office or if | | |
| |e-mail is sent to a group. | | |
|Photo editing tools |Available in these applications: |Limited functionality. |Limited functionality. |
| |(Word 2010, Excel 2010, PowerPoint| | |
| |2010, Outlook 2010, and Microsoft | | |
| |Publisher 2010). | | |
|Video in Microsoft PowerPoint |Video triggers and controls. |Not available. |Not available. |
What’s new for IT Professionals
To learn about licensing and volume activation, 64-bit editions of Office 2010, application virtualization, security changes, and Office Customization Tool changes in Office 2010, see What’s new for IT professionals in Office 2010 in Getting started with the deployment of Office 2010.
See Also
Getting started with the deployment of Office 2010
System requirements for Office 2010
Deploy Microsoft Silverlight with Office 2010
SharePoint Workspace 2010 overview
SharePoint Workspace 2010 overview
This article describes the key functionality and architecture of Microsoft SharePoint Workspace 2010. SharePoint Workspace 2010 is the new name for and succeeds Microsoft Office Groove 2007. SharePoint Workspace 2010 is a client application that provides fast, any-time interactive access to document libraries and lists on Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010. SharePoint Workspace 2010 also provides options for creating Groove peer workspaces and Shared Folder workspaces. SharePoint Workspace 2010 is more versatile than Microsoft Office Groove 2007 and can be integrated with Microsoft SharePoint Server 2010 or can run independently.
Microsoft SharePoint Workspace 2010 provides a client for Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010 that enables real-time synchronization of desktop content with SharePoint documents and lists. SharePoint Workspace 2010 also provides options for creating Groove collaboration workspaces and synchronized shared folders. By using SharePoint Workspace 2010, information workers can easily synchronize online and offline content with a designated SharePoint site or collaborate with external partners and offsite team members through shared workspaces. SharePoint Workspace 2010 is installed automatically with enterprise versions of Microsoft Office 2010 or it can be installed separately from the Microsoft Download Center ().
Key features of SharePoint Workspace 2010 include the following:
• A choice of workspace types:
• SharePoint workspaces — Provide direct bi-directional synchronization of library and list content between a SharePoint site and a workspace on an individual client computer. Creation of a SharePoint workspace enables individual SharePoint users to check out and check in SharePoint library documents from their local computers, bring SharePoint documents and lists to their computers where they can work online or offline, and synchronize local content with a SharePoint site. When an individual client establishes a connection with a SharePoint server, synchronization occurs at regular intervals when the client is online. When a client cannot connect to a SharePoint site, the user can easily take work offline to make updates. The updated documents are automatically synchronized with SharePoint document libraries and lists when the user reconnects. This interface offers an efficient and satisfying alternative to browser access of SharePoint. Unlike other workspace types, the SharePoint workspace is a personal synchronized copy of a SharePoint site.
• Groove workspaces — Provide a rich and secure peer collaboration environment that supports synchronization of content among peer client computers that host a shared workspace. Creation of a Groove workspace enables SharePoint Workspace users to quickly form teams and automatically synchronize online or offline contributions with fellow team members. A full set of collaboration tools lets team members schedule meetings, hold discussions, and share work with trusted partners around the world. Support for communications under various network conditions and across firewalls facilitates timely and effective collaboration.
• Shared Folder workspaces — Support Windows folder sharing among clients. Creation of a Shared Folder workspace lets information workers share the contents of a common folder in a designated Windows Explorer directory.
• Easy setup Windows users can easily download and run SharePoint Workspace 2010 without IT assistance.
• Offline and online collaboration Information workers can easily synchronize online and offline work, through a SharePoint workspace, Groove workspace, or Shared Folder workspace. Content is synchronized dynamically among online collaboration points and updates are transmitted immediately when an offline client comes back online. When an offline client reconnects, SharePoint Workspace automatically adds offline contributions to the workspace and applies workspace updates to the previously offline client.
• Immediate access to latest document versions Updates to SharePoint workspaces are distributed quickly and automatically to SharePoint Server document libraries and lists. Likewise, document and list updates are automatically synchronized (on a 15-minute schedule) from SharePoint servers to SharePoint workspaces. Updates to Groove workspaces are automatically synchronized among workspace peers.
• Bandwidth usage optimization To minimize workload, update packets, instead of whole files or documents, are transmitted over the network.
• Integration with Windows logon SharePoint Workspace 2010 uses Windows logon credentials to authenticate users so that a separate logon is not necessary.
• Microsoft Communicator integration and built-in workspace messaging SharePoint Workspace 2010 supports Microsoft Communicator contact presence detection and messaging while offering workspace members a choice of messaging types.
• Familiar user interface The user interface presents the ribbon and other technology that is familiar to Office users.
• Searchable content Windows Desktop Search 4.0 can be used to find content in workspaces.
• Common file dialog boxes Windows technology enables Microsoft Office 2010 users to directly open and save files in SharePoint Workspace.
• Safe Mode operation SharePoint Workspace 2010 users who encounter problems can restart in Safe Mode, attempt to resolve the issue, and then restart as usual.
• For Groove workspace users:
• Collaboration tools support document creation and editing, discussions, meeting management, and other tasks.
• The Documents tool enables users to store, organize, and share Word, text, and other documents. This tool replaces the Groove 2007 Files tool.
• The Lists tool provides a custom tool Design environment that uses Microsoft InfoPath 2010. Tool developers import form templates designed in InfoPath into the Lists tool and then perform additional layout, sorting, and filtering tasks in the List Tool Designer. The List tool replaces Groove 2007 Forms and InfoPath Forms tools.
• Built-in security protects user content. SharePoint Workspace 2010 automatically and securely distributes and saves content that Groove workspace members produce during their interactions, transmitting it directly to workspace members for storage on member computers. All communications are private, transmitted only among authenticated members and the content of workspace member transmissions is encrypted over the network. SharePoint Workspace 2010 avoids storing member content on remote servers that might not be secure.
• Standards-based public key infrastructure (PKI) provides a solid framework for securing Groove workspaces.
• Ability to traverse firewalls enables collaboration with trusted partners outside the corporate intranet.
• Compatibility with Office Groove 2007 workspaces simplifies collaboration strategies.
• Onboard Groove workspace backup mechanism.
For more information about SharePoint Workspace functionality, see the SharePoint Workspace product description at Microsoft products online ().
See Also
Plan for SharePoint Workspace 2010
Configure and customize SharePoint Workspace 2010
System requirements for Office 2010
This article describes the system requirements for the Microsoft Office 2010 suites. A hardware upgrade should not be necessary when you upgrade to Office 2010 from Microsoft Office 2003 or the 2007 Microsoft Office system. You might need to upgrade a supporting operating system. If you upgrade to Office 2010 from Microsoft Office 2000 or Microsoft Office XP, you must ensure that the hardware and operating system meet the minimum system requirements for the Office 2010 suites.
[pic]Note
• Office 2010 is supported for both 32-bit and 64-bit client applications.
• We recommend that you install Microsoft Silverlight 3 along with Office 2010 to improve the online experience and to power the Office 2010 interactive guides.
In this article:
• Microsoft Office Professional Plus 2010
• Microsoft Access 2010
• Microsoft Excel 2010
• Microsoft InfoPath 2010
• Microsoft OneNote 2010
• Microsoft Outlook 2010
• Microsoft PowerPoint 2010
• Microsoft Project Professional 2010
• Microsoft Publisher 2010
• Microsoft SharePoint Workspace 2010
• Microsoft Visio 2010 (Premium, Professional, Standard)
• Microsoft Word 2010
When you choose the product suite or individual program to deploy in the environment, evaluate the computer prior to deployment to ensure it meets the minimum operating system requirements.
Microsoft Office Professional Plus 2010
The following table lists the system requirements for Microsoft Office Professional Plus 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) of RAM or higher |
|Hard disk |3 gigabytes (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 768 or higher-resolution monitor; 1024 × 576 or higher for |
| |Excel 2010, OneNote 2010, Outlook 2010, PowerPoint 2010, and Word |
| |2010 |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1 |
| |(32-bit or 64-bit), Windows Server 2003 R2 (32-bit or 64-bit) with |
| |MSXML 6.0 installed, Windows Server 2008 with SP2 (32-bit or 64-bit),|
| |Windows 7 (32-bit or 64-bit). Terminal Server and Windows on Windows |
| |(WOW) (which allows installing 32-bit versions of Office 2010 on |
| |64-bit operating systems) are supported. |
|Additional |Requirements and product functionality can vary based on the system |
| |configuration and operating system. Use of graphics hardware |
| |acceleration requires DirectX 9.0c compatible graphics card with 64 |
| |MB or higher video memory. |
|Other |• Certain inking features require running Windows XP Table PC edition|
| |or later. Speech recognition functionality requires a close-talk |
| |microphone and audio output device. Information Rights Management |
| |features require access to a Windows Server 2003 with SP1 or later |
| |running Windows Rights Management Services. |
| |• Connectivity to Microsoft Exchange 2000 Server or later is required|
| |for certain advanced functionality in Office Outlook 2007. Instant |
| |Search requires Windows Desktop Search 3.0. Dynamic Calendars require|
| |server connectivity. |
| |• Connectivity to Windows Server 2003 with SP1 or later running |
| |Windows SharePoint Services is required for certain advanced |
| |collaboration functionality. Microsoft Office SharePoint Server 2007 |
| |is required for certain advanced functionality. PowerPoint Slide |
| |Library requires Office SharePoint Server 2007. To share data among |
| |multiple computers, the host computer must be running Windows Server |
| |2003 with SP1, Windows XP Professional with SP2 or later. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply) |
| |• 1 gigahertz (GHz) processor or higher and 512 MB of RAM or higher |
| |recommended for Business Contact Manager. Business Contact Manager |
| |not available in all languages. |
| |• 512 MB of RAM or higher recommended for Outlook Instant Search. |
| |Grammar and contextual spelling in Word 2010 is not turned on unless |
| |the computer has 1 GB memory. |
| |• Silverlight plug-in. See Get started with Microsoft Silverlight |
| |(). |
Microsoft Access 2010
The following table lists the system requirements for Microsoft Access 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) OF RAM or higher |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk |
|Display |1024 × 768 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating systems. |
|Other |• Connectivity with Windows Server 2003 with SP1 or later running |
| |Windows SharePoint Services is required for certain advanced |
| |collaboration functionality. Collecting data via e-mail requires |
| |Office Outlook 2007. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Importing data from Excel 2010 or Outlook 2010 requires Excel 2010 |
| |or Outlook 2010. |
| |• Integration with Business Connectivity Services requires Microsoft |
| |.NET Framework 3.5. |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
Microsoft Excel 2010
The following table lists the system requirements for Microsoft Excel 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) OF RAM or higher |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 576 or higher resolution monitor |
| |Video card requirements: Pixel Shader 20 and Vertex Shader 2.0. |
| |Driver date later than Nov. 1, 2004. WHQL certified. |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating systems. |
|Other |• Certain inking features require running Microsoft XP Tablet PC |
| |edition or later. Speech recognition functionality requires a |
| |close-talk microphone and audio output device. Information Rights |
| |Management features require access to a Windows Server 2003 with SP1 |
| |or later running Windows Rights Management Services. |
| |• Connectivity to Windows Server 2003 with SP1 or later running |
| |Windows SharePoint Services is required for certain advanced |
| |collaboration functionality. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Connectivity to a compute cluster is required for running |
| |user-defined functions on a compute cluster. |
| |• Internet Fax is not available on Windows Vista Starter, Windows |
| |Vista Home Basic, or Windows Vista Home Premium. |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
Microsoft InfoPath 2010
The following table lists the system requirements for Microsoft InfoPath 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) OF RAM or higher |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 768 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows 7 or later operating |
| |systems. |
|Other |• Information Rights Management features require access to a Windows |
| |Server 2003 with SP1 or later running Windows Rights Management |
| |Services. |
| |• Connectivity to Windows Server 2003 with SP1 or later running |
| |Windows SharePoint Services is required for certain advanced |
| |collaboration functionality. Outlook 2010 required for e-mail-based |
| |collaboration. Sending forms as e-mail message requires Outlook 2010.|
| |Conversions of Word documents require Word 2010. Conversion of Excel |
| |worksheet requires Excel 2010. Microsoft SharePoint Server 2010 |
| |required for browser-enabled InfoPath forms and additional |
| |collaboration functionality. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Internet Fax is not available on Windows Vista Starter, Windows |
| |Vista Home Basic, or Windows Vista Home Premium. |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
Microsoft OneNote 2010
The following table lists the system requirements for Microsoft OneNote 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) OF RAM or higher |
|Hard disk |1 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 576 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating system. |
|Other |• Some features require Windows Desktop Search 3.0, Windows Media |
| |Player 9.0, Microsoft Active Sync 4.1, microphone, audio output |
| |device, video recording device (such as a webcam), TWAIN-compatible |
| |digital camera or scanner. Sharing notebooks requires that users to |
| |be on the same network. |
| |• WDS 4 preferred, DirectX no longer needed, router with UPnP no |
| |longer needed, Windows Mobile no longer needed. |
| |• OneNote functionality works on both 32-and 64-bit. |
| |• Sharing notebooks requires that users to be on the same network. |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
| |• For the OneNote print driver: Microsoft .NET Framework 3.0 or |
| |higher, Windows XPS features installed on Windows Vista, Windows 7, |
| |Windows Server 2008, Windows Server 2008 R2, XPS features installed |
| |before Office install on operating system. |
| |• 1.2-gigahertz (GHz) processor or higher and 1 GB OF RAM or higher |
| |recommended for OneNote Audio Search. Close-talking microphone |
| |required. Audio Search not available in all languages. |
Microsoft Outlook 2010
The following table lists the system requirements for Microsoft Outlook 2010, along with resources to help evaluate the applications and hardware that you might need to get the most out of Outlook 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |512 megabytes (MB) OF RAM or higher recommended for Outlook Instant |
| |Search, or when accessing large Outlook Data Files, such as files |
| |that are hundreds of megabytes in size or more. |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 576 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit and 64-bit), Windows 7 or later operating system. |
|For integration with Microsoft Exchange Server 2010 (optional) |For a list of some of the new Outlook 2010 features that are enabled |
| |with Microsoft Exchange Server 2010, see Changes in Outlook 2010 and |
| |What's New in Exchange Server 2010 |
| |(). |
| |Exchange 2010 System Requirements |
| |() |
| |Learn more about Microsoft Exchange Server 2010 |
| |() |
|For integration with Microsoft Communicator Server 2007 R2 (optional)|For a list of some of the new Outlook 2010 features that are enabled |
| |with Microsoft Communicator 2007 R2, see Changes in Outlook 2010. |
| |Supported Topologies and Infrastructure Requirements |
| |() |
| |Learn more about Microsoft Office Communications Server 2007 R2 |
| |() |
|Other |• Microsoft Exchange Server 2003 is the earliest version for using |
| |Exchange Server with Outlook 2010. |
| |• Certain inking features require running Windows XP Tablet PC |
| |Edition or later; speech recognition functionality requires a |
| |close-talk microphone and audio output device; Information Rights |
| |Management features require access to a Windows Server 2003 with SP1 |
| |or later running Windows Rights Management Services. |
| |• Connectivity to Windows Server 2003 with SP1 or later running |
| |Windows SharePoint Services is required for certain advanced |
| |collaboration functionality. Connectivity to Office SharePoint Server|
| |2007 is required for certain advanced functionality. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
| |• Grammar and contextual spelling in Outlook is not turned on unless |
| |the computer has 1 GB memory. |
Microsoft PowerPoint 2010
The following table lists the system requirements for Microsoft PowerPoint 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) OF RAM or higher. When embedding video, 512 MB OF |
| |RAM is recommended. |
|Hard disk |1 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 576 or higher resolution monitor |
| |Video card requirements: Pixel Shader 20 and Vertex Shader 2.0. |
| |Driver date later than Nov. 1, 2004. WHQL certified. |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating systems. |
|Other |• Certain inking features require running Windows XP Table PC edition|
| |or later; speech recognition functionality requires a close-talk |
| |microphone and audio output device; Information Rights Management |
| |features require access to a Windows Server 2003 with SP1 or later |
| |running Windows Rights Management Services. |
| |• Connectivity to Windows Server 2003 with SP1 or later running |
| |Windows SharePoint Services is required for certain advanced |
| |collaboration functionality. PowerPoint Slide Libraries require |
| |Office SharePoint Server 2007. |
| |• Internet Explorer 6, 32-bit browser only. Internet functionality |
| |required Internet access (fees might apply). |
| |• User of graphics hardware acceleration requires DirectX 9.0c |
| |compatible graphics card with 64 MB or higher video memory. |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
| |• Internet Fax not available on 64-bit operating system. |
Microsoft Project Professional 2010
The following table lists the system requirements for Microsoft Project Professional 2010.
|Component |Requirement |
|Computer and processor |700-megahertz (MHz) processor or higher |
|Memory |512 megabytes (MB) or higher |
|Hard disk |2.0 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 768 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating systems. |
|Other |• Windows Server 2008 with SP2 (64-bit) or later running Microsoft |
| |SharePoint Server 2010 is required for certain advanced collaboration|
| |functionality. Office Outlook 2003 SP2 or later is required to use |
| |the Import Outlook Tasks feature. Visual Reports require Office Excel|
| |2003 SP2 or later and Microsoft Office Visio Professional 2007 or |
| |later. |
| |• Microsoft Project Server 2010 is required for Enterprise Project, |
| |portfolio, and resource management capabilities. Microsoft Project |
| |Web App and Microsoft Exchange Server 2007 SP1 or later are required |
| |for importing tasks to the Outlook calendar or tasks list. |
| |• SharePoint Server 2010 (installed with Project Server 2010) is |
| |required for publishing projects and Windows Workflow Foundation. |
| |Microsoft .NET Framework version 3.5 is required for the Resource |
| |Substitution Wizard. |
| |• Internet Explorer 7 or later. Internet functionality requires |
| |Internet access (fees might apply). |
| |• To enable the feature that allows synchronizing Project 2010 with a|
| |SharePoint task list, you must install either Microsoft Access 2010 |
| |or Microsoft Visio 2010. |
| |• Before installing Project 2010 to use Visual Reports with Office |
| |2010, you must install Office 2010, Visio 2010 and Microsoft SQL |
| |Server 2008 Analysis Services 10.0 OLE DB Provider (available as a |
| |free download from Microsoft SQL Server 2008 Feature Pack, October |
| |2008 (). |
| |• Certain online functionality requires a Windows Live ™ ID. |
| |Product functionality and graphics may vary based on your system |
| |configuration. |
| |Some features may require additional or advanced hardware or server |
| |connectivity. |
Microsoft Publisher 2010
The following table lists the system requirements for Microsoft Publisher 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) or higher |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is remove from the hard|
| |disk. |
|Display |1024 × 768 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating system. |
|Other |• Certain inking features require running Windows XP Tablet PC |
| |Edition or later; speech recognition functionality requires a |
| |close-talk microphone and audio output device. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
| |• Internet connectivity and a Windows Live ID, to share Templates and|
| |Building Blocks. |
Microsoft SharePoint Workspace 2010
The following table lists the system requirements for Microsoft SharePoint Workspace 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) of RAM or higher; 512 MB of RAM recommended for |
| |co-authoring. |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 576 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating systems. |
|Other |• Integration with SharePoint Services requires connectivity to |
| |Microsoft SharePoint Server 2010. |
| |• No support exists for downgrading or reverting to a previous |
| |version of an Office Groove 2007 account after starting the upgrade |
| |process. |
| |• Internet Explorer 7 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
| |• Each computer will need to be upgraded to SharePoint Workspace 2010|
| |to run SharePoint Workspace accounts on multiple computers. |
Microsoft Visio 2010 (Premium, Professional, Standard)
The following table lists the system requirements for Microsoft Visio Premium 2010, Microsoft Visio Professional 2010, and Microsoft Visio Standard 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) or higher. 512 MB OF RAM recommended for |
| |co-authoring. |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 768 or higher resolution monitor |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating (32-bit and 64-bit) |
| |systems. |
|Other |• Certain advanced collaboration functionality requires connectivity |
| |to Windows Server 2003 with SP1 or later running Windows SharePoint |
| |Services. |
| |• Multi-touch features require Windows 7 and a touch enabled device. |
| |• Certain inking features require running Microsoft XP Table PC |
| |edition or later. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
Microsoft Word 2010
The following table lists the system requirements for Microsoft Word 2010.
|Component |Requirement |
|Computer and processor |500-megahertz (MHz) processor or higher |
|Memory |256 megabytes (MB) of RAM or higher; 512 MB of RAM recommended for |
| |co-authoring. |
|Hard disk |1.5 gigabyte (GB); a portion of this disk space will be freed after |
| |installation if the original download package is removed from the |
| |hard disk. |
|Display |1024 × 576 or higher resolution monitor |
| |Video card requirements: Pixel Shader 20 and Vertex Shader 2.0. |
| |Driver date later than Nov. 1, 2004. WHQL certified. |
|Operating system |Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1,|
| |Windows Server 2003 R2 with MSXML 6.0, Windows Server 2008 with SP2 |
| |(32-bit or 64-bit), Windows 7 or later operating systems. |
|Other |• Certain inking features require running Windows XP Tablet PC |
| |edition or later; speech recognition functionality requires a |
| |close-talk microphone and audio output device. |
| |• Publications can be sent by using Office Outlook 2007, Outlook |
| |Express 6.0, or Windows Live Mail; recipients can view in a variety |
| |of e-mail clients and Web-based services. |
| |• Internet Explorer 6 or later, 32-bit browser only. Internet |
| |functionality requires Internet access (fees might apply). |
| |• Actual requirements and product functionality might vary based on |
| |the system configuration and operating system. See |
| | |
| |(). |
| |• Co-authoring requires Microsoft SharePoint Foundation 2010 or |
| |SkyDrive, and might require more memory. |
| |• Grammar and contextual spelling in Word 2010 is not turned on |
| |unless the computer has 1 GB memory. |
Office 2010 suites
Five editions of the Microsoft Office 2010 suites are available — three user versions and two business versions — depending on an organization’s needs and licensing requirements. These include the following editions:
• Microsoft Office Home and Student 2010
• Microsoft Office Home and Business 2010
• Microsoft Office Standard 2010
• Microsoft Office Professional 2010
• Microsoft Office Professional Plus 2010
[pic]Note:
Microsoft requires activation of all editions of Microsoft Office 2010. This includes those obtained through a Volume Licensing program. Only the volume-licensed version enables organizations to host browser-based versions of the software.
In this article:
• Comparisons of Office 2010 editions
Comparisons of Office 2010 editions
The following table compares Office 2010 suites, products, and features.
|Programs, products, and |Home and Student |Home and Business |Standard |Professional |Professional Plus |
|features | | | | | |
|Microsoft Excel 2010 |Yes |Yes |Yes |Yes |Yes |
|Microsoft OneNote 2010 |Yes |Yes |Yes |Yes |Yes |
|Microsoft PowerPoint 2010 |Yes |Yes |Yes |Yes |Yes |
|Microsoft Word 2010 |Yes |Yes |Yes |Yes |Yes |
|Microsoft Outlook 2010 |No |Yes |Yes |Yes |Yes |
|Microsoft Publisher 2010 |No |No |Yes |Yes |Yes |
|Microsoft Access 2010 |No |No |No |Yes |Yes |
|Microsoft Communicator 2010|No |No |No |No |Yes |
|Microsoft InfoPath 2010 |No |No |No |No |Yes |
|Microsoft SharePoint |No |No |No |No |Yes |
|Workspace 2010 | | | | | |
Office 2010 is available in 32-bit and 64-bit editions. For a list of specific requirements, see System requirements for Office 2010.
See Also
Getting started with the deployment of Office 2010
What's new in Office 2010
Getting started with the deployment of Office 2010
Microsoft Office 2010 provides features that help IT administrators configure, validate, deploy, and protect Office installations in their organizations. This article discusses the structure of the documentation in the Office Resource Kit for Office 2010 and also describes the new features and improvements in the Microsoft Office 2010 suites that are relevant to IT professionals.
In this article:
• About the Office 2010 Resource Kit
• What’s new for IT professionals in Office 2010
• Additional resources
About the Office 2010 Resource Kit
The Microsoft Office 2010 Resource Kit provides information about new features and changes in deployment strategies for Office 2010. The documentation is intended for IT professionals who plan, implement, and maintain Office installations in their organizations. New and updated content will be published on a regular basis.
[pic]Note:
As with the 2007 Microsoft Office system, many of the primary administrative tools for deploying Office 2010 (and the 2007 Office system) are included with the product and are no longer available as a download as in versions of Office earlier than the 2007 Office system. To view the Office Resource Kit for previous versions of Office, see the “Office Resource Kit Versions” section in 2007 Office System Suites and Programs ().
The documentation in the Office 2010 Resource Kit is organized into the following areas:
• Product evaluation and getting started with Office 2010 Beta Provides an overview of Office 2010, and includes information about the Setup architecture, 64-bit Office 2010, system requirements, getting started information, and product comparisons.
• Planning the deployment of Office 2010 Beta Provides information about assessing your current environment, planning for desktop configurations, security, and applications including Microsoft Access 2010, Microsoft Excel 2010, Microsoft Outlook 2010, and Microsoft Project 2010. It also provides planning information for migration and upgrading from previous versions of Office, and also planning for virtualization and Terminal Services.
• Configuration and deployment of Office 2010 Beta Provides how-to information for specific deployment tasks, such as customizing the installation, and installing Office 2010 on users' computers. It also provides information about the new licensing options for Office 2010, including instructions for configuring the infrastructure for volume licensing and activation.
• Maintaining and updating Office 2010 Beta Provides information about how to change users' configurations after installing Office 2010.
• Security and protection for Office 2010 Beta Provides information new security controls in Office 2010, which make it easier for IT professionals to build a robust defense against threats while maintaining information worker productivity.
• Troubleshooting for Office 2010 Beta Provides information and procedures for troubleshooting an installation of Office 2010.
• Technical reference for Office 2010 Beta Provides technical details related to Office 2010 Setup properties and command-line options; describes the Office Customization Tool and Config.xml file; and provides information about product and feature changes in Office 2010 and the following applications: Microsoft Access 2010, Microsoft Excel 2010, Microsoft InfoPath 2010, Microsoft OneNote 2010, Outlook 2010, Microsoft PowerPoint 2010, Project 2010, Microsoft Publisher 2010, Microsoft SharePoint Designer 2010, Microsoft SharePoint Workspace 2010, Microsoft Visio 2010, and Microsoft Word 2010.
What’s new for IT professionals in Office 2010
Office 2010 provides new features and improvements that help IT administrators configure, validate, deploy, and protect their Office installations. The following sections discuss changes in these areas:
• Licensing and volume activation
• Office 2010 64-bit editions
• Security changes
• Office Customization Tool changes
• Application virtualization
The following sections provide information about these changes.
Licensing and volume activation
Microsoft includes product activation technologies in the following products sold through the Volume Licensing channel: Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, and now Office 2010. Product activation is verification with the manufacturer to confirm that software is genuine and that its product key is not compromised. Activation establishes a relationship between the software's product key and a particular installation of that software on a device.
Activation types include retail, volume, and OEM, and most require interactive steps by the user or IT professional, such as entering a product key from the packaging, or contacting a networked server or telephone service center. Activation technologies and tools vary according to the different channels for the software — retail, volume, and OEM.
The Microsoft policy requires the activation of all editions of Office 2010. This includes those obtained through a Volume Licensing program. This requirement applies to Office 2010 running on both physical computers and virtual machines.
You can use the following methods to activate Office 2010 with Office Activation Technologies:
• Key Management Service (KMS). KMS uses a KMS host key to activate a KMS host computer and establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation.
• Multiple Activation Key (MAK). With a MAK, clients activate Office 2010 online with the Microsoft hosted activation servers or by telephone
• A combination of KMS and MAK.
For more information about Office Activation Technologies, see Volume activation overview for Office 2010 and Volume activation quick start guide for Office 2010.
Office 2010 64-bit editions
Processors that are 64-bit are quickly becoming the standard for systems ranging from servers to desktop computers. The 64-bit systems can use more virtual and physical memory than 32-bit processors. This lets users work with much larger data sets than they could previously, to analyze and solve large computational problems. Office 2010 introduces native 64-bit versions of Office products to take advantage of the additional capacity provided by 64-bit processors. This additional capacity is only needed by Office users who require Excel spreadsheets that are larger than 2 GB, for example. The 32-bit version of Office 2010 provides the same functionality and is also compatible with 32-bit add-ins. This is why Office 2010 will install the 32-bit version by default.
For information about the supported operating systems, supported scenarios, setup process, and deployment considerations for 64-bit Office 2010, see 64-bit editions of Office 2010.
Security changes
Fortunately, several new security controls in Office 2010 make it easier for IT professionals to build a robust defense against threats without diminishing information worker productivity. Five of the new controls provide countermeasures for hardening and reducing the attack surface and mitigating exploits. These include the following:
Data Execution Prevention (DEP) support for Office applications A hardware and software technology that helps harden the attack surface by preventing the execution of viruses and worms that exploit buffer overflow vulnerabilities.
Office file validation An Office software component that helps reduce the attack surface by scanning files for file format (file fuzzing) exploits before the files are opened by an application.
Expanded file block settings A suite of Group Policy settings that helps reduce the attack surface by providing more specific control over the kinds of files an applications can access.
Office ActiveX kill bit An Office feature that administrators can use to prevent specific ActiveX controls from running within Office applications.
Protected view A sandbox environment that helps mitigate attacks by enabling users to preview untrusted or potentially harmful files in a secure viewer.
In addition to these new controls, Office 2010 provides several security enhancements that further harden the attack surface by helping to ensure the integrity and confidentiality of data. This includes the following:
• Cryptographic agility for Microsoft Excel 2010, Microsoft PowerPoint 2010, and Microsoft Word 2010.
• Trusted time stamping support for digital signatures.
• Domain-based password complexity checking and enforcement.
• Encryption strengthening enhancements.
• Improvements to the password to modify feature.
• Integrity checking of encrypted files.
Office 2010 also provides several security improvements that have a direct affect on information worker productivity. Improvements in the message bar user interface, a trust model that remembers users’ trust decisions, Trust Center user interface settings, and single identity management are some examples of new features that help make security decisions and actions less intrusive to information workers. In addition, many of the new and enhanced security controls can be managed through Group Policy settings. This makes it easier for you to enforce and maintain your organization’s security architecture.
For more information about security for Office 2010, see Security overview for Office 2010 and Plan security for Office 2010.
Office Customization Tool changes
The Office Customization Tool (OCT) is the main customization tool that is used to customize an installation of Microsoft Office 2010 (and the 2007 Microsoft Office system). The OCT is part of the Setup program and is the recommended tool for most customizations, and is available only with volume licensed versions of Office 2010 and the 2007 Office system. You run the OCT by typing setup.exe /admin at the command line.
For more information about the OCT, see Office Customization Tool in Office 2010.
The Office 2010 release provides the following new features:
• Two architecture-specific versions of the OCT, one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and OPA settings as the 32-bit version. The OCT files are located in the Admin folder under the x86 (32-bit) and x64 (64-bit) folders, respectively.
For information about 64-bit Office 2010, see 64-bit editions of Office 2010.
• Import feature that lets administrators import 32-bit OCT customization (MSP) updates into the 64-bit version of the OCT and 64-bit MSP updates into the 32-bit version of the OCT. This allows administrators of mixed environments (32-bit and 64-bit) to do the Setup customizations one time. For more information, see Import an Office 2010 Setup customization file.
• Support for adding multiple Outlook e-mail accounts.
Application virtualization
Microsoft Application Virtualization (App-V) is another method for deploying Office 2010. Virtualization transforms applications into virtualized, network-available services that are not installed on the users’ computer. Instead, applications can be automatically delivered to the users’ computer as users need them.
By using App-V and Office 2010 together, you can quickly deliver the latest version of Office without having to worry about application conflicts or delays in productivity for users. Deploying Office 2010 with App-V 4.6 (currently in Beta) includes new support for integration with SharePoint Products and Technologies, Outlook Search, and OneNote 2010. App-V 4.6 is scheduled for release in 2010.
App-V significantly reduces regression and application interoperability testing. App-V also minimizes the effect on users during application upgrades, patching, and terminations of user rights to applications because restarts and uninstallations are no longer required.
For more information about Application Virtualization, see Planning and Deployment Guide for the Application Virtualization System ().
Additional resources
To learn about application-specific changes, application compatibility in Office 2010, and tools for preparing to migrate to Office 2010, see the following resources:
• For information about application-specific changes in Office 2010, see Product and feature changes in Office 2010.
• To learn about application compatibility in Office 2010, see Application compatibility overview for Office 2010, Application compatibility assessment and remediation guide for Office 2010, Office Environment Assessment Tool (OEAT) quick start guide for Office 2010, Office Environment Assessment Tool (OEAT) user's guide for Office 2010, and Microsoft Office Code Compatibility Inspector user's guide.
• For information about tools for preparing your environment for migrating to Office 2010, see Office Migration Planning Manager (OMPM) overview for Office 2010.
For information about architecture changes introduced in the 2007 Microsoft Office system for administrators who might not be familiar with that version of the product, see Setup changes prior to Office 2010.
See Also
What's new in Office 2010
Setup architecture overview for Office 2010
Setup changes prior to Office 2010
System requirements for Office 2010
Changes in Office 2010
Plan security for Office 2010
Application compatibility overview for Office 2010
Office Migration Planning Manager (OMPM) overview for Office 2010
Setup changes prior to Office 2010
This article provides a summary of changes in the 2007 Microsoft Office system for administrators who might not be familiar with that version of the product. The 2007 Office system introduced features and improvements that help IT administrators configure, deploy, and maintain their Office installations. These features provided benefits that let administrators work more efficiently and help reduce administrative costs. The changes included the following:
• A Setup architecture that supports a more efficient installation process.
• A language-neutral architecture that simplifies deployment in multiple languages.
• A streamlined customization model to install, customize, and maintain Office.
• XML default file format for Microsoft Office Word 2007, Office Excel 2007, and Microsoft Office PowerPoint 2007. Based on open standards, the XML file format enables users to quickly create documents from different data sources, speeding up document assembly, data mining, and content reuse.
• The 2007 Office system security features, which are designed based on the following principles:
• Make application functionality secure by default.
• Avoid asking questions that users might be unable to answer.
• Maintain user productivity by mitigating threats without limiting application functionality.
• Provide a flexible security model that can be modified to suit specific situations.
• Microsoft Office Fluent user interface, which is designed to make it easier for people to find and use the full range of features these applications provide.
Changes introduced in the 2007 Office system
The following sections provide information about these changes:
• Setup architecture
• Language-neutral architecture
• Customization model
• File formats, Security, User Interface, Object Model, and application changes in 2007 Office
Setup architecture
The Setup program for the 2007 Office system was redesigned to support a more efficient installation process. Most of the tools and procedures were new but the overall objective was the same as it was for any previous deployment of Office: to install the correct configuration on users' computers as efficiently as possible.
In the 2007 Office system release, much of the complexity of this process was absorbed by the new Setup program. Setup handles the most difficult parts for you behind the scenes, and the steps that you take to customize and distribute the product are simpler than in any earlier version. This information also applies to the Office 2010 release of the product because the basic Setup architecture has not changed in this release.
Setup features comparison
The following table compares Setup features that were introduced in the 2007 Office system release to their closest counterparts in previous versions (Microsoft Office 2000, Office XP, and Office 2003). This information also applies to Office 2010.
|Previous version |2007 Office system and Office 2010 release |Function |
|Windows Installer (Msiexec.exe) |Setup program (Setup.exe) |Installation program |
|Administrative installation point |Local installation source (LIS) |Location of stored program files |
|One MSI file per product |Multiple MSI files per product |Windows Installer files |
|Core English version plus MUI Pack |Language-neutral architecture |Deploy multiple languages at the same time |
|Setup.ini file |Config.xml file |Customize installation file |
|Setup command line |Config.xml file |Customize installation file |
|Custom Installation Wizard |Office Customization Tool (OCT) |Customize installation of products |
|Custom Maintenance Wizard |Office Customization Tool |Customize installation of products |
|Office Profile Wizard |Group Policy settings |Group Policy Management Console (GPMC) and |
| | |Group Policy Object Editor Microsoft |
| | |Management Console (MMC) snap-ins are used to|
| | |manage policy settings |
Setup files
In versions of Office earlier than the 2007 Office system, each product consisted of a single Windows Installer package (MSI file). The chief role of Setup.exe was to call Windows Installer (Msiexec.exe) to install the package. Because Setup passed its command line to Windows Installer, it was possible to manage the installation process by setting Windows Installer properties on the command line.
Starting with the 2007 Office system release, a single Office product consists of multiple MSI files. This is the same in the Office 2010 release of the product as the basic Setup architecture has not changed in this release. Setup — not Windows Installer — combines the language-neutral core product package with one or more language-specific packages to create a complete product. No individual MSI file represents a product that anyone can install or use, and Setup is required to assemble the correct set of MSI files and to coordinate the installation process from start to finish.
The Office product that you install is defined in the XML files on the installation point. Setup reads data in these XML files, assembles the required set of MSI files for the product, copies all the necessary files to the local installation source, and only then calls Windows Installer to complete the installation process.
[pic]Note:
You cannot use the Windows Installer command line (Msiexec.exe) to install any product in the 2007 Office system release or in Office 2010, nor can you set Windows Installer properties on the Setup command line. However, you can use the new deployment tools to customize all aspects of the installation process, exactly as you did in previous versions. For more information, see Setup architecture overview for Office 2010.
Language-neutral architecture
If you installed previous versions of Office in an international setting, you first installed the core English version and then deployed one or more Multilingual User Interface (MUI) Packs to provide additional language versions to users. You may have used the Custom Installation Wizard to configure the MUI Pack, and then edited the Setup.ini file to chain the MUI Pack installation to the primary English installation.
The language-neutral architecture that was introduced in the 2007 Office system eliminates the need to chain language packs and condenses the process to a single installation. This also applies to Office 2010 as the language architecture has not changed in this release. After you create your initial network installation point (which always includes a core product), you copy all the additional language folders that you need to the same location. These language folders contain the language-specific packages, or building blocks, that Setup combines with the core product to create a complete product in any language (including English). After you create a network installation point with multiple languages, you can enable Setup to manage the process of assembling the correct language version for each user automatically from the available language options.
When users run Setup for a particular Office product, Setup detects that there is more than one language available and automatically combines the core package with the language that matches the user locale, which is set in Windows. Only one language version is copied to the local installation source; only one product appears in Add or Remove Programs in Control Panel. Without additional steps on your part, other than dragging language folders to the network installation point, you ensure that users in New York get the English language version, users in Tokyo get the Japanese language version, users in Paris get the French language version, and so on.
Customizing a multi-language installation is similarly streamlined. You create only one customization file per product, regardless of the number of languages that you are deploying. Most configuration options apply to the core product. The minority of language-specific customizations — for example, the feature installation state for the Japanese Input Method Editor (IME) — are applied where appropriate and otherwise ignored.
[pic]Note:
When you customize the installation, you can specify that Setup install more than one language on users' computers or that Setup install a particular language regardless of the user locale setting. For more information about the new multi-language architecture, see "Language-neutral design" in Setup architecture overview for Office 2010.
Customization model
In versions of Office products earlier than the 2007 Office system, several tools were required to customize Setup and to manage Office after installation. However, the 2007 Office system introduced a consistent, streamlined customization model. You can use one of several methods to customize the installation, although the best method depends on what you are customizing and whether you want users to be able to change the default configuration. This also applies to Office 2010 as the customization model has not changed in this release.
Choosing a customization tool
The following table summarizes the customization methods introduced in the 2007 Office system and describes the recommended or required scenarios for each method. This also applies to Office 2010.
|Tool or method |Scenarios |Results |
|Use the Office Customization Tool to create a|Recommended for most customizations, |Setup installs a default configuration on all|
|Setup customization file (MSP file). |including: |computers to which this MSP file is applied. |
| |• Accepting License Terms and entering a |Users can modify most settings after the |
| |volume license key |installation. |
| |• Running Setup without user interaction | |
| |• Customizing features and user settings | |
| |• Distributing an Outlook profile | |
|Edit the Config.xml file. |Required for the following customizations: |Setup installs the specified products and |
| |• Specifying the path of the network |languages on all computers installed with |
| |installation point |this Config.xml file. |
| |• Specifying languages to install |Settings specified in Config.xml take |
| |• Pointing Setup to a custom Config.xml or |precedence over duplicate settings in the |
| |Setup customization file |Setup customization file. |
| |• Copying the local installation source to the| |
| |user's computer without installing Office | |
| |• Chaining additional products to the primary | |
| |installation | |
|Add options or properties to the Setup |Available for only the following |Setup applies your customizations when it |
|command line. |customizations: |first installs Office or when it runs in |
| |• Pointing Setup to a custom Config.xml or |maintenance mode. |
| |Setup customization file |You cannot set Windows Installer properties |
| |• Modifying an existing installation |on the command line. |
| |• Repairing the product | |
| |• Uninstalling the product | |
|Use the Group Policy Object Editor Microsoft |Used to configure highly restricted or lightly|Administrators use Group Policy to define |
|Management Console (MMC) snap-in to specify |managed configurations for user and computer |configurations once and then rely on the |
|policy settings. |settings. |operating system to enforce that state. |
| | |Group Policy for computers is applied at |
| | |computer startup and Group Policy for users |
| | |is applied when users log on. Group Policy is|
| | |also applied subsequently in the background |
| | |periodically. |
File formats, Security, User Interface, Object Model, and application changes in 2007 Office
This section summarizes the changes that were introduced in the following areas of the 2007 Office system:
• File format
• Security
• User Interface
• Object model
• Access 2007
• Excel 2007
• Outlook 2007
• Word 2007, PowerPoint 2007, and OneNote 2007
File format
The 2007 Office system release introduced a default file format for Office Word 2007, Office Excel 2007, and Office PowerPoint 2007. The default format was changed to XML in response to customer requests. XML format provides the following benefits:
• Enables more rapid document creation from different data sources
• Enables easier data mining and content reuse
• Reduces the size of Word, Excel, and PowerPoint files
• Improves data recovery in corrupted files
Service Pack 2 (SP2) for the 2007 Office system also added support for the following:
• OpenDocument Format (ODF). SP2 lets you open, edit, and save documents in version 1.1 of the ODF for Word, for Excel, and for PowerPoint. Users of these Office programs can now open, edit, and save files in the OpenDocument Text (*.odt), OpenDocument Spreadsheet (*.ods), and OpenDocument Presentations (*.odp) formats.
Group Policy settings and Office Customization Tool (OCT) settings were added for managing OpenDocument Format and Open XML Formats in the 2007 Office system. For more information, see Group Policy and Office Customization Tool settings that address OpenDocument Format and Open XML Formats in the 2007 Office system ().
• Extensible File Formats: Word, Excel, and PowerPoint now include a converter interface that lets you plug third-party custom file formats into these Office programs. A developer can create a converter for files of a particular extension. When this converter is installed on a user’s computer, the custom file format effectively behaves like a built-in file format. Specifically, users can open files of this format and save them by using the Open or Save UI. They can even set the custom format as their default file format.
• Built-in Save As PDF/XPS support was also added in SP2. PDF/XPS support is built into SP2 for Word, for Excel, and for PowerPoint. Users no longer have to download the add-in separately.
For more information about the file format changes that were introduced in the 2007 Office system, see File format reference for the 2007 Office system ().
Security
The Trust Center was introduced in the 2007 Office system, and hosts all security settings for Office applications in one location. The Trust Center also provides a document menu bar that replaces the security prompts when a file opens. By default, potentially dangerous content is blocked in the file without prompting. Therefore, there are no security decisions when the file opens. If content is blocked, the document menu bar appears and informs the user. Clicking the document menu bar displays a dialog box that has the disabled content and the options to enable or disable the content.
The Trust Center also has new security settings (previously Low, Medium, High, and Very High) that are more descriptive and provide more flexibility.
To learn about security features that were introduced in the 2007 Office system, see the resources in the Security and protection for the 2007 Office release () section.
User Interface
Office Word 2007, Office Excel 2007, Office Access 2007, Office PowerPoint 2007, and Office Outlook 2007 introduced a new ribbon interface (Microsoft Office Fluent user interface) instead of the menu bar in previous versions. The ribbon is an area across the top of the screen that is divided into tabs. Commands are organized within each tab. This change greatly improves the user's ability to use and find features in the 2007 Office system.
Most commands continue to work as before. There is minimal need to edit macros or application code due to the new ribbon interface.
For more information about the Microsoft Office Fluent user interface introduced in the 2007 Office system, see the Microsoft Office Fluent User Interface Resource Center (). In Office 2010, additional applications add the fluent UI.
Object model
Because of improvements introduced in the 2007 Office system, there are differences in the object model. Because of these changes, you should test all applications to ensure they are compatible with the 2007 Office system. Some features of the object model were added, changed, or removed. In some instances, the functionality might still be available, but might be removed in future versions of Office. For more information about object model changes in 2007 Office system, see Differences in the 2007 Office system ().
Access 2007
Office Access 2007 introduced a new file format. Whereas versions of Access earlier than Office Access 2007 used the MDB format, Office Access 2007 saves files in the new ACCDB format. One key feature of the ACCDB format is the ability to store complex data. Storing complex data requires the presence of a new system table, MSysFlattenedMapping, plus a series of built-in schema tables. The MSysFlattenedMapping table and the built-in schema tables are automatically created when a new ACCDB file is created.
Excel 2007
In addition to the new user interface and file format changes, Office Excel 2007 introduced major changes in the following areas:
• Grid size. The grid size for Office Excel 2007 worksheets was greatly expanded to 1,000,000 rows by 16,000 columns (compared to 65,536 rows by 256 columns in Office Excel 2003). This change could result in Range Names that conflict with the new references, and can also affect the ability to save a worksheet to an earlier version.
• Formulas and functions. The Analysis ToolPak was integrated into Office Excel 2007 to improve the installation process. This required that calls to Analysis ToolPak functions are changed so that the syntax is the same as the syntax used for built-in functions. Also, some integrated functions might conflict with user-defined functions. Changes to statistical functions provide more precision. By using multi-threaded calculation, Office Excel 2007 provides increased performance when it runs on computers that have more than one logical processor.
• Charting. Charts created in Office PowerPoint 2007 or Office Word 2007 (not in compatibility mode) are native charts, not Microsoft Graph OLE objects. The data for a Graph in PowerPoint or Word is now in Office Excel 2007, instead of in the Graph datasheet. Macros written to use the Microsoft Graph object model must be changed. Existing macros continue to work in Office Excel 2007, but charts should transition to the new object model.
• Charting. Charts created in Office PowerPoint 2007 or Office Word 2007 (not in compatibility mode) are native charts, not Microsoft Graph OLE objects. The data for a Graph in PowerPoint or Word is now in Office Excel 2007, instead of in the Graph datasheet. Macros written to use the Microsoft Graph object model must be changed. Existing macros continue to work in Office Excel 2007, but charts should transition to the new object model.
Outlook 2007
Office Outlook 2007 introduced improvements in the Calendar, Tasks, and other features. One of the biggest changes was that instead of using the Exchange Security Form (ESF), a custom form for administering Office Outlook 2007 security options when you are connected to a Microsoft Exchange Server mailbox, you use Group Policy. This changes the method that you use to lock down Office Outlook 2007 in a network environment. Some situations still require use of the ESF, because of Group Policy restrictions. For example, hosted Exchange situations still require using the ESF to lock down Office Outlook 2007.
Word 2007, PowerPoint 2007, and OneNote 2007
Office Word 2007, Office PowerPoint 2007, and Office OneNote 2007 introduced changes as follows.
• Word changes included: new XML file formats; new user interface, graphics, and formatting capabilities; improved proofing tools; new sharing and collaboration features; new security features; and improved troubleshooting and recovery features.
• PowerPoint changes included: new XML file formats; new user interface, graphics, and formatting capabilities; improved proofing tools; new sharing and collaboration features; new security features; and improved troubleshooting and recovery features.
• OneNote changes included: Deleted Pages feature was removed; Show Ink Groups feature on the Tools menu was removed; and the title area in Microsoft Office OneNote 2007 was removed
For more information about feature changes that were introduced in the 2007 Office system, see Differences in the 2007 Office system ().
Setup architecture overview for Office 2010
The basic Setup architecture in Microsoft Office 2010 is the same as the architecture introduced in the 2007 Microsoft Office system. The Setup architecture streamlines all aspects of installing, customizing, and maintaining Office. The Setup program unifies and manages the complete installation process. This includes customizing users' Office configuration, deploying multiple languages at the same time, and applying software updates to new installations. This article contains an overview of the Setup architecture, setup sequence of events, language-neutral design and deployment of multiple languages, customization methods, required local installation source, and updates process.
The Setup architecture helps administrators manage areas such as the following more efficiently:
• Deployment process so that Office is installed in the most efficient way for their environment.
• Customization of Office so that users get optimal configuration on their computers.
• Deployment of language-specific features for users who are located in offices around the world.
• Deployment of Office in a way that makes future maintenance, including software updates, as efficient as possible.
In versions of Office earlier than the 2007 Office system, a single Office product such as Microsoft Office Standard was contained in a single Windows Installer (MSI) file. An MSI file is a relational database that Windows Installer uses to install a product. As with the 2007 Office system, the Office 2010 products consist of multiple MSI files, and no single MSI file represents a complete product. A language-neutral core package (MSI file) is combined with one or more language-specific packages to make a complete product. For example, an Office product such as Microsoft Office Professional Plus 2010 consists of the core package plus one or more language-specific packages. Setup assembles the individual packages, orchestrates a seamless installation, and handles customization and maintenance tasks during and after installation of Office on users' computers.
Office 2010 introduces native 64-bit versions of Office products to support 64-bit processors, which are becoming the standard for systems ranging from servers to desktop computers. Office 2010 also provides support for 32-bit Office 2010 applications that run on 64-bit Windows operating systems by using Windows-32-on-Windows-64 (WOW64). WOW64 is the x86 emulator that enables 32-bit Windows-based applications to run seamlessly on 64-bit Windows. Office 2010 lets users continue to use existing third-party Office add-ons, which are primarily 32-bit because no 64-bit versions are available yet for many add-ons. Providing support for 32-bit Office 2010 running on 64-bit operating systems prevents blocking the 32-bit add-ons. For more information about 64-bit editions of Office 2010, see 64-bit editions of Office 2010.
In this article:
• Setup process
• Language-neutral design
• Streamlined customization model
• Required local installation source
• Consolidated update process
Setup process
Typically, the first step in a corporate installation of Office is to create a network installation point — a task as simple as copying all the files and folders from the Office product CD to a shared network location. At a minimum, the network installation point contains the language-neutral core package plus language-specific folders for one language. This installation point serves as the initial source for all users who install Office.
In the simplest scenario, you deploy an Office product from the network installation point with one language version and a single set of customizations for all users. Setup handles this scenario automatically. If you deploy multiple products or languages, you can add them to the same network installation point and specify exactly which products and languages to include in the installation. In all of these scenarios, Setup performs the same tasks to assemble the correct set of MSI files and to complete the installation.
[pic]Note:
The Office 2010 does not let you create an administrative installation point by running Setup with the /a command-line option to extract compressed source files, as was possible with Office versions earlier than the 2007 Office system. All installations now occur from the compressed source.
In this section:
• Setup sequence of events
• Including more than one product on the installation point
• Running Setup interactively
Setup sequence of events
The basic Setup sequence of events is as follows and occurs in the same order in every deployment scenario:
1. Run Setup.
2. Check prerequisites.
3. Read XML data.
4. Build the feature tree.
5. Create a local installation source on the user's computer.
6. Install Office.
7. Apply the customization file.
8. Apply software updates.
Run Setup
Setup.exe is the program that begins all the mechanisms of the installation process. It is located at the root of the network installation point. You run Setup one time for each Office product that you install. When it runs, Setup searches the network installation point for an Office product to install. If the installation point contains more than one Office product, Setup gives the user a choice of products to install.
You can circumvent the selection process and determine which Office product is installed by pointing Setup.exe to the Config.xml file in a core product folder. For example, if you want to install Microsoft Office Professional Plus 2010, you can use the following command line:
\\server\share\Office14ProPlus\setup.exe /config \\server\share\Office14ProPlus\Pro.WW\Config.xml
where Office14ProPlus is the root of the network installation point.
In versions of Office earlier than the 2007 Office system, Setup.exe called Windows Installer (Msiexec.exe) to install Office. Although Setup still uses Windows Installer, Setup bypasses the Windows Installer executable program. The Msiexec.exe command line cannot be used to install the Office 2010 (or the 2007 Office system).
[pic]Note:
This version of Setup.exe recognizes only a few command-line options. For more information, see Setup command-line options for Office 2010.
Check prerequisites
When Setup starts, it checks for several installation prerequisites. This includes minimum operating system requirements and administrative permissions. A user must be an administrator of the client computer to install Office, or you must use a tool such as Microsoft Systems Management Server (SMS) or Microsoft System Center Configuration Manager 2007 to run the installation by using elevated permissions.
When you run Setup.exe from the x64 folder, Setup determines whether there are 32-bit Office applications installed. If Setup detects 32-bit Office applications, it displays an error message that informs users that they must first uninstall all 32-bit Office applications if they want to continue with the installation of Office 2010 64-bit. The error lists the installed 32-bit Office applications. If Setup does not detect 32-bit Office applications, it installs the 64-bit edition of Office 2010.
When you run Setup.exe from the x32 folder, Setup determines whether there are 64-bit Office 2010 applications installed. If Setup detects 64-bit Office 2010, an error message displays and Setup is blocked. If Setup does not detect 64-bit Office 2010, it installs the 32-bit edition of Office 2010. For more information, see 64-bit Setup process in 64-bit editions of Office 2010.
[pic]Note
• To install Office on computers where users lack administrative permissions, you must run Setup in a context that provides it with administrative permissions. After Office is installed, users without administrative permissions can run all installed features. This includes installing features on demand.
• For example, in organizations where users are not the administrators of their computers, administrators can use the following methods of providing Office Setup with the appropriate permissions:
Read XML data
Setup collects information about each package on the installation point, collects default settings for the installation, and incorporates customizations that you specify. Setup collects all this information in the form of XML data from several sources:
• Setup.xml and Package.xml files for each package Each folder on the installation point — both the folder for the language-neutral core package and the folder for each language-specific package — contains a Setup.xml and a Package.xml file (for example, ProPlusWW.xml for Microsoft Office Professional Plus 2010). Information in these files enables Setup to do the following:
• Identify a product and the available languages for that product.
• Match language-neutral and language-specific elements to create complete features.
• Build a consolidated feature tree.
• Collect the set of MSI files that are required for the installation.
[pic]Note:
The Setup.xml and Package.xml files are signed and cannot be modified. Altering these files causes Setup to fail.
• Setup customization file Early in the installation process, Setup determines whether you have specified a Setup customization file (.msp file) for the product that is being installed. A Setup customization .msp file is created when administrators use the Office Customization Tool (OCT) to customize an installation of Office 2010. The OCT is part of the Setup program and is the recommended tool for most customizations. The customization file contains all the modifications that you specify for an installation. This includes customizations that control the installation process.
The OCT is available in volume licensed versions of Office 2010. To determine whether your Office 2010 installation is a volume licensed version, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a volume license edition; otherwise, the disk is a retail edition.
If no customization file is specified on the command line or in the Config.xml file, Setup searches the Updates folder on the installation point for a customization file specific to the product that is being installed. By default, the Updates folder is included on the installation point. In most cases, it is the recommended location in which to store both a Setup customization .msp file and software updates for all the Office products included on the installation point.
[pic]Important
• If you plan to deploy multiple Setup customization files (.msp files), you can place only one customization .msp file for each Office 2010 product that you are installing in the Updates folder for an initial installation. Only one Setup customization .msp file (patch) for each Office 2010 product that you are installing is supported in the Updates folder. You must deploy the rest of the customization .msp files for a product after the Office installation is completed.
• If you are deploying multiple Office 2010 products, such as Microsoft Office Professional Plus 2010 and Microsoft Visio Professional 2010, you can include one customization .msp file for Office Professional Plus 2010 and one customization .msp file for Visio Professional 2010 in the Updates folder. The customization .msp files that you place in the Updates folder will be deployed first. Therefore, they must include any Setup customizations that cannot be changed after the installation, for example, the installation location.
• If you are deploying an initial installation of Office 2010 and you also want to deploy Office 2010 software updates, such as service packs and hotfixes, Setup can apply the product updates as part of the installation process. You can place the Office 2010 product updates in the Updates folder. In scenarios such as this where the Updates folder includes both one Setup customization .msp file and product updates, Setup applies only the Setup customization .msp file with the initial installation and the product updates are applied after the installation is complete.
Setup uses XML data appended to the customization file to determine how to install the product — for example, whether to run quietly or which features to display in the feature tree. Settings in a customization file overwrite default settings contained in the Setup.xml and Package.xml files.
For more information about Setup customization files, see Streamlined customization model. For information about how to use the OCT, see Office Customization Tool in Office 2010.
• Config.xml file Each core product folder contains a Config.xml file that directs Setup to install that product. You can edit Config.xml to customize the installation process. For example, you can use elements in Config.xml to specify which products or languages to include in the installation. Settings in Config.xml take precedence over settings in a customization file and default settings contained in the Setup.xml and Package.xml files.
For more information about how and when to edit Config.xml, see Config.xml file in Office 2010.
Build the feature tree
Setup uses the information that is contained in the XML files to create a single feature tree that includes all the available applications and features in the product. You view the feature tree and specify which applications and features to install on users' computers by using the Office Customization Tool. If you let users run Setup interactively, they view the feature tree with your modifications in the Setup user interface.
For more information about how to specify which Office features to install, see Configure feature installation states for Office 2010.
Create a local installation source on the user's computer
Setup calls a program named Office Source Engine (Ose.exe) to create a required local installation source (LIS) on the user's computer. To create the local installation source, Setup copies files from the installation point to a hidden folder on the user's computer. The default location is \MSOCache\All Users at the root of the drive on which Office is installed. Later, Setup uses Windows Installer to install Office from this local installation source.
The local installation source provides several important benefits:
• After Office is installed, Setup can repair, reinstall, or add Office features by using the local source.
• Users who are applying software updates are less likely to be prompted for a network or CD source because an installation source is available locally.
• You can deploy the local installation source in advance and trigger the installation of Office on users' computers later to reduce the load on the network. In this scenario, you can even run Setup from the local installation source. This lets users complete the Office installation by using no network connection.
For more information about the local installation source, see Required local installation source.
Install Office
When the installation starts, Setup checks for required disk space and feature dependencies, and then calls Windows Installer to install the correct set of packages (MSI files) on the user's computer from the local installation source. Setup uses the XML data described previously to determine which set of MSI files to include. The progress bar that Setup displays to users during the installation takes the whole installation process into account. This includes applying customizations and software updates from the Updates folder.
[pic]Note:
Although Setup uses Windows Installer to install Office, Windows Installer alone cannot install the individual MSI files independent of Setup.
Apply the customization file
During the installation process, Setup applies the customization file to the user's configuration. The result resembles the effect of applying a Windows Installer transform (MST file) in previous versions of Office: your customizations become the default configuration for users. In addition to the XML data that customizes the installation process, the customization file might include default user settings, feature installation states, Microsoft Outlook profiles, and other modifications to the user's configuration.
Customization files are product-specific; Setup applies only those files that are relevant to the product being installed.
[pic]Note:
If you plan to deploy multiple Setup customization .msp patches, you can place only one Setup customization .msp file in the Updates folder for an initial installation. You must deploy the rest of the customization .msp files after the Office installation is complete. As mentioned previously, only one customization patch in the Updates folder is supported. The customization .msp file that you place in the Updates folder will be deployed first so it must include any Setup customizations that cannot be changed after the installation, for example, the installation location.
If you create different configurations for different groups of users, we recommend that you store the customization files in another location and then use the /adminfile option on the Setup command line to specify the file that you want. For example:
\\server\share\Office14\setup.exe /adminfile \\server\share\Office14\MyUpdates\Engineering.msp
where Office14 is the root of the network installation point.
[pic]Note:
When you precache the local installation source, Setup copies the Updates folder from the network installation point to the local installation source. In this manner, your customizations can be included in offline installation scenarios. This is the only circumstance in which Setup caches the customization file on the local computer before the installation. For more information, see Precache the local installation source for Office 2010.
Apply software updates
At the end of the installation process, Setup checks the Updates folder on the installation point for software updates (.msp files). Unlike Setup customization files that you create by using the Office Customization Tool, software updates are distributed by Microsoft to enhance the product.
If you are deploying Office to users and must also have to deploy a set of software updates, Setup can apply the updates as part of the initial installation process. Costing (estimated required disk space) and progress bar indicators all take this step of the installation process into account. From a user's perspective, the complete process is a single event. This model preserves the original installation point and still lets you give new users the most up-to-date version of the product.
[pic]Note:
The Updates folder is used only for initial or new installations of Office 2010. The Updates folder can contain only one Setup customization .msp patch, and multiple service packs and hotfixes that are in .msp format only.
For more information about the software update process, see Consolidated update process.
Including more than one product on the installation point
If the network installation point contains more than one Office 2010 product, Setup searches all folders and subfolders for Config.xml and Setup.xml files and then prompts the user to select a product to install.
If you are installing more than one Office product, it is more efficient to store all the products on the same installation point and then customize Setup to install a specific Office product on users' computers.
[pic]Note:
When you copy multiple Office products to the same installation point, you might be prompted to overwrite shared Setup files. Because these files are duplicated among all Office 2010 products, you do not need to recopy any of the duplicate folders. This efficient design saves space and ensures consistency when you create and replicate network installation points.
Running Setup interactively
You can choose to run the installation quietly so that users see little or none of the process. However, if you let users view the Setup user interface, the choices that you make affect several aspects of Setup behavior. For example:
• If more than one Office product is available on the installation point and a user runs Setup.exe without command-line options, Setup gives the user a choice of products to install.
• If more than one language is available on the installation point, Setup matches the language of Office to the Windows user locale on the user's computer. This is by default. However, if a user selects the Customize installation option, the Languages tab in the Setup interface gives the user a choice of all available languages on the network installation point.
• If you enter a product key and accept the Microsoft Customer License Terms in the customization file or Config.xml, those Setup screens are not displayed to the user during Setup.
• If you use a customization file to hide and lock certain features, those features are not displayed in the feature tree.
To find out more about how to customize display settings, see Customize Setup before installing Office 2010.
Language-neutral design
In Office 2010 (and in the 2007 Office system), an Office product such as Office Professional Plus 2010 is organized as follows:
• Language-neutral elements are grouped in one core package (MSI file).
• Language-specific elements are organized in separate packages by application.
This arrangement of files simplifies international deployments. The most basic installation of an Office product consists of the core package plus one language. Adding more languages is as simple as copying additional Single Language Packs (SLPs) to the network installation point — all work with the core product in exactly the same way. All language versions of Office, including the English language version, are deployed in the same manner. Setup combines the language-neutral core package with the language-specific packages in a seamless installation process.
[pic]Important:
The current Office 2010 release includes English, Chinese, French, German, Japanese, Spanish, and Russian language sources only. Later releases will provide additional languages.
In this section:
• Language versions of Office
• Language packs for Office
Language versions of Office
Every Office product must include at least one set of language-specific packages. You cannot deploy just the core package (MSI file) by itself. On the Office product CD and the network installation point, these language packages are contained in folders. Each folder name includes a language tag, in the form ll-cc (for example, en-us for English U.S.), that identifies the language. Each folder also contains a set of installation files.
For example, the Office Professional Plus 2010 product is spread out among the files in these folders. Elements that are not specific to any language, such as Winword.exe (the executable file for Microsoft Word 2010), reside in the core ProPlus.WW package. Other elements, such as Help and the user interface for Word 2010, reside in the appropriate language-specific package for Word or for shared Office features.
Both language-neutral and language-specific elements are required to make a functionally complete feature. Winword.exe by itself does not represent a Word application that anyone can use. Similarly, the core Office Professional Plus 2010 MSI file in the ProPlus.WW folder does not represent a complete Office product.
Setup assembles all these parts into a whole product. The Package.xml and Setup.xml files in each folder contain information that Setup uses to assemble complete features, build a consolidated feature tree, and collect the correct set of MSI files for the installation. After collecting the XML data and assembling the required MSI files, Setup uses Windows Installer to install Office on the user's computer. From a user's perspective, this process happens automatically and seamlessly.
You cannot deploy an individual application in Office 2010 by detaching the language-specific folder that contains the individual MSI file, such as the Word.en-us folder. However, you can determine which applications and features are installed on users' computers by customizing the installation.
[pic]Note:
None of the MSI files on an Office installation point can be installed independently by using Windows Installer or any other method. Also, none of the digitally signed XML files (Setup.xml and Package.xml) can be edited or altered. In Office 2010, Setup is required to collect the files and installation information and to orchestrate the installation process.
Language packs for Office
Language-specific packages are used in two contexts: in the language version of an Office product, and in the Single Language Pack (SLP) for that language. For example, the French version of Office Professional Plus 2010 will include a language-specific folder for each application and for shared features in Office Professional Plus 2010. The same folders will be included in the French SLP, which will include language-specific folders for other products in Office 2010.
Language packs can be deployed as separate products, or they can be used to deploy an Office product in multiple languages. You are not required to enter a unique product key for language packs, whether you are deploying them separately or as part of the installation of another product.
[pic]Note:
In versions of Office earlier than the 2007 Office system, enterprise customers added languages by deploying Multilanguage User Interface (MUI) packs after a U.S. English version of Office was installed. Localized versions, such as the Japanese version of Office Standard Edition, were not identical to the core version with a Japanese MUI pack. This design was simplified and improved in the 2007 Office system and is the same in Office 2010.
Streamlined customization model
In versions of Microsoft Office earlier than the 2007 Office system, several tools were required to customize Setup and to manage Office after installation. The 2007 Office system introduced a consistent, streamlined model. In Office 2010 (as in the 2007 Office system), administrators can use Setup to install, customize, and manage Office. To enforce specific user and computer settings, administrators can use Group Policy (see Using Group Policy).
In this section:
• Using the Office Customization Tool
• Customizing a new installation
• Making changes to an existing Office installation
• Using the Config.xml file to customize Office
• Using Setup command-line options
• Using Group Policy
Using the Office Customization Tool
You customize an Office installation by using the Office Customization Tool, a component of Setup, which is included in volume licensed versions of Office 2010 client. Start the OCT by running Setup with the /admin command-line option. By using the OCT, create a Setup customization file (.msp file), which you place in the Updates folder in the network installation point. As mentioned previously, the Updates folder is used only for initial or new installations of Office 2010, and only one customization patch in the Updates folder is supported.
A Setup customization file is an expanded form of a Windows Installer .msp file. Each file is configured for a specific product, such as Office Professional Plus 2010 or OneNote 2010. When you run Setup to install an Office product, Setup looks in the Updates folder for a customization file that corresponds to the product that you are installing. As Setup installs the product, it applies the customizations from this file.
You can create more than one Setup customization file to configure Office for different groups of users. When you run Setup, you specify the appropriate customization file to use for each installation by using the Setup command-line option /adminfile, or by using Config.xml (see Using the Config.xml file to customize Office).
For complete details on how to use the OCT to create a Setup customization file, see Office Customization Tool in Office 2010.
Customizing a new installation
By using a Setup customization file that you create with the OCT, you can modify the way Setup installs Office on a user's computer the first time. For example, the OCT lets you customize Office in the following ways:
• Direct Setup to run without user interaction (quietly).
• Predefine the product key and accept the Microsoft Software License Terms on behalf of the user.
• Specify where to install Office files on the user's computer.
• Choose whether to remove previous versions of Office before you install the Office 2010.
• Determine which Office features are installed.
• Specify the default values for a large number of user options, including Microsoft Outlook settings.
[pic]Note:
Office 2010 does not support side-by-side installations of 64-bit and 32-bit Office, including across applications. For example, there is no support for side-by-side installations of the 2007 Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit. You cannot use the Office 2010 customization tools to configure side-by-side installations or customizations of 64-bit and 32-bit Office. For example, you cannot create a custom side-by-side installation by using 64-bit Microsoft Office Professional 2010 and 32-bit Visio 2010 single image. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
For information about how to customize Setup, see Customize Setup before installing Office 2010.
Making changes to an existing Office installation
If you need to make changes to an existing Office installation, use the same tool that you used to customize the original installation: Run the OCT to update a Setup customization file or to create a new one. Then apply the customization file to the user's computer exactly as you would a software update, and the user's existing Office installation is updated with your customizations. This means that the customizations available when you install Office are also available when you modify Office after installation.
[pic]Note:
There are some customizations that Setup applies only when you are installing Office for the first time. These include: specifying where to install Office on the user's computer, defining the product key, and removing previous versions of Office applications. The OCT identifies which customizations apply only to a new installation.
Using the Config.xml file to customize Office
You can use the Config.xml file to make changes to your Office installation. You can customize most of the same options that you can with the Office Customization Tool, including a few additional ones not available in the OCT.
Using the Config.xml file is the recommended method for performing the following installation tasks:
• Instructing Setup to copy the local installation source to the user's computer without installing Office.
• Specifying the path of the network installation point.
• Selecting which product or language to install.
• Changing where Setup looks for Setup customization files and updates.
• Making last-minute or one-off customizations that do not warrant running the OCT to create a new customization file.
If you put the Config.xml file in the same folder as Setup.exe, Setup finds and uses the file. You can also specify the location of the file by using the /config Setup command-line option.
[pic]Note:
If you specify both a Setup customization file and the Config.xml file, the customizations that you define in Config.xml take precedence over the same customizations in the customization file.
For a complete description of the contents and format of the Config.xml file, see Config.xml file in Office 2010.
Using Setup command-line options
Setup recognizes only a few command-line options in the Office 2010. This is the same as for 2007 Office system. The OCT is the primary tool to configure Setup properties and specify other customizations.
You can use Setup.exe commands to perform the following tasks:
• Run the Office Customization Tool to create a Setup customization (.msp) file.
• Apply the specified Setup customization file to the installation. For example, you can specify a path of a specific customization file (.msp file) or to the folder where you store customization files.
• Specify the Config.xml file that Setup uses during the installation.
• Run Setup in maintenance mode and make changes to an existing Office installation.
• Run Setup to repair the specified product from the user's computer.
• Run Setup to remove the specified product from the user's computer.
For more information about the Setup.exe commands, see Setup command-line options for Office 2010. For information about Windows Installer properties that were used in previous versions of Office, and about properties that can be used when you install Office 2010, see Setup properties in Office 2010.
Using Group Policy
Administrators can use Group Policy settings to define and maintain an Office configuration on users' computers. Group Policy is used to configure the Office 2010 policy settings contained in Administrative Templates, and the operating system enforces those policy settings. In an Active Directory environment, administrators can apply policy settings to groups of users and computers in a site, domain, or organizational unit to which a Group Policy object is linked. True policy settings are written to the approved registry keys for policy, and these settings have access control list (ACL) restrictions that prevent non-administrator users from changing them. This allows administrators to create highly restricted or lightly managed configurations.
Administrators can use policy settings for the Office 2010 applications to manage most options that configure the Office user interface, including the following:
• Menu commands and their corresponding toolbar buttons
• Shortcut keys
• Most options in the Options dialog box
[pic]Note:
Most of the Office 2010 policy settings are also available in the OCT (OPA settings). To configure initial default settings in a Setup customization .msp file, administrators can use the OCT. However, users can modify most of the settings after the installation. Use Group Policy if you want to enforce specific configurations. Group Policy settings have precedence over OCT settings.
Required local installation source
In Office 2010, Setup creates a local installation source on the user's computer as part of the default installation process. Setup installs all Office 2010 products in a two-step process. First, Setup copies compressed installation source files to the user's computer. Second, Setup calls Windows Installer to perform the actual installation from the local installation source. After the installation is complete, the local installation source remains available for any Setup operations that require access to an original source. Minimum disk space requirements include the local installation source.
[pic]Note:
In Microsoft Office 2003, large organizations typically installed the product from an administrative installation point; installing from a local installation source was optional. In the Office 2010, however, the administrative installation option no longer exists, and the local installation source is a required part of the design.
The local installation source makes the process of distributing software updates more efficient and reliable. Neither the network installation point nor the user's local installation source is ever updated directly. Users' installations remain synchronized when they apply the client version of software updates.
Additional benefits of having a complete installation source always available on the local computer include the following:
• You can deploy the local installation source to users before they install Office. This minimizes the effect on the network and ensures that all users install the product and begin to use Office 2010 applications at exactly the same time.
• Users can perform maintenance tasks, such as applying software updates, without being prompted for their Office CD or a network source.
• Traveling users, or users who have slow or intermittent network connections, can run Setup without access to the network if they have a local installation source installed in advance.
These benefits come at minimal cost. Although the local installation source does use some hard disk space, creating the local installation source and installing Office takes approximately the same amount of time as installing Office by itself.
In this section:
• Creating a local installation source on users' computers
• Deploying the local installation source by itself
Creating a local installation source on users' computers
When users install Office from the CD or from a network installation point, Setup creates the local installation source by using a program called the Office Source Engine (Ose.exe) to copy required installation files to a hidden folder on the local computer. The default location is \MSOCache\All Users at the root of the drive on which Office is installed.
Each package that comprises an Office product — both the language-neutral core package and one or more language-specific packages — has a separate download code and is cached in the subfolder under MSOCache\All Users. Setup always caches a complete local installation source, which includes all the files associated with the product that is being installed. If the installation point includes multiple languages, Setup caches only the packages for the languages that are installed on the user's computer.
When additional Office products are installed on the user's computer, those products are cached in the same local installation source.
[pic]Note:
If a user installs a second Office product on a different drive, Setup creates a second local installation source at the root of that drive. In this scenario, shared files might be duplicated between the two local installation sources. However, this design ensures that each local installation source is complete and functions correctly.
Users cannot unintentionally delete the local installation source or remove it by using the Setup user interface or the Windows Disk Cleanup Wizard. If the MSOCache folder is deleted or corrupted, Setup automatically re-creates or repairs the folder the next time that a source is required. If users do not have sufficient disk space, they are prompted to free some space. You can rely on the fact that every user has access to a source when you distribute new updates or customizations.
[pic]Note:
Once the local installation source is created, its location on the user's computer is fixed. Unless the user specifies a different drive, additional Office products installed later are always added to the existing MSOCache\All Users folder.
Deploying the local installation source by itself
Because Setup performs the installation of Office from the local installation source, you can minimize the demand on the network by deploying the installation source beforehand. For example by using your usual method for running Setup on users' computers, you can distribute the local installation source to one group of users at a time. Once all users have a precached source, you can have everyone run Setup to install Office at the same time. In this scenario, most of the installation activity occurs on the local computer instead of over the network.
For more information, see Precache the local installation source for Office 2010.
You can also run Setup directly from the local installation source on the local computer. Running Setup locally means that no activity, including loading Setup files and reading metadata, occurs over the network. In this scenario, you must identify the subfolder in MSOCache\All Users that contains the core product that you want to install. Each core product subfolder contains a copy of the Setup program, and running Setup from a specific folder installs that product. This method lets users install Office without relying on a network connection.
For more information, see Run Setup from the local installation source to install Office 2010.
Consolidated update process
In versions of Office earlier than the 2007 Office system, you made a number of choices to ensure that client computers received the latest Office software updates and that client computers did not become out of sync with the administrative installation point. You might have configured Setup to chain software updates with new installations of Office, or you might have applied updates to the administrative installation point and reinstalled Office on all the client computers.
The architecture introduced in the 2007 Office system makes this process much simpler. In Office 2010 (as in the 2007 Office system), you create a network installation point that you never have to update. Instead, a simple copy operation makes software updates available for new installations. You update existing installations independent of the network installation point so you do not have to worry about keeping client computers synchronized with the installation source.
In this section:
• Applying Office updates during new installations
• Updating existing Office installations
Applying Office updates during new installations
When you obtain Office software updates from Microsoft, copy the updates into the Updates folder in the root of the network installation point. The existing files in the network installation point remain the same as when you first copied them from the Office CD.
[pic]Note:
You can use the Updates folder to incorporate the installation of updates with an initial installation of the Office 2010 products. Only Windows Installer update files that are contained in this folder are installed with the initial installation. Therefore, you must extract the updates from Microsoft Self-Extractor packages. You can also place a Setup customization .msp patch in the Updates folder to customize initial installations.
When you run Setup to install Office on a client computer, Setup looks in the Updates folder for software updates and incorporates the updates automatically as it installs Office. If there are multiple updates in the folder, Setup applies only those updates that are targeted at the Office product being installed. If the Updates folder includes both a Setup customization .msp patch and product updates, Setup applies only the Setup customization .msp patch with the initial installation and the product updates are applied after the installation completes. Setup also applies the updates in the correct sequential order. The result is that the user receives the latest updates with the new installation of Office.
[pic]Tip:
To direct Setup to look for software updates in a folder other than the Updates folder, use the SetupUpdates element in the Config.xml file. For more information, see SetupUpdates element in Config.xml file in Office 2010.
Updating existing Office installations
Once Office is installed, you apply software updates directly to the client computer without returning to the network installation point. You do this through a deployment management program such as Microsoft Systems Management Server or System Center Configuration Manager 2007, by using Microsoft Windows Server Update Services, or by updating computers directly from the Internet by using Microsoft Update.
[pic]Note:
After Office is installed on a client computer, reinstalling Office reapplies only those software updates that were applied with the original installation. If you copied new software updates in the Updates folder, they are not applied during the reinstallation.
See Also
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Setup command-line options for Office 2010
Setup properties in Office 2010
Setup changes prior to Office 2010
Customization overview for Office 2010
64-bit editions of Office 2010
Processors that are 64-bit are becoming the standard for systems that range from servers to desktop computers. The 64-bit systems can use more virtual and physical memory than 32-bit systems. This lets users work with much larger data sets than they could previously, and to analyze and solve large computational problems. Microsoft Office 2010 introduces native 64-bit versions of Microsoft Office products to take advantage of this larger capacity. For example, this additional capacity is needed only by those Microsoft Excel users who require Excel spreadsheets that are larger than 2 gigabytes (GB). The 32-bit version of Office 2010 provides the same functionality and is also compatible with 32-bit add-ins. Therefore, the 32-bit version of Office 2010 is installed by default.
Office 2010 also provides support for 32-bit Office 2010 applications that run on 64-bit Windows operating systems by using Windows-32-on-Windows-64 (WOW64). WOW64 is the x86 emulator that enables 32-bit Windows-based applications to run seamlessly on 64-bit Windows systems. Office 2010 lets users continue to use existing Microsoft ActiveX Controls, Component Object Model (COM) add-ins, and Visual Basic for Applications (VBA), which are primarily 32-bit because no 64-bit versions are available yet for many add-ins. Supporting 32-bit Office 2010 applications that run on 64-bit operating systems allows for better compatibility with controls, add-ins, and VBA.
The recommendations for which edition of Office 2010 to install are as follows:
• If users in your organization depend on existing extensions to Office, such as ActiveX controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32-bit versions of programs that interface directly with Office, we recommend that you install 32-bit Office 2010 (the default installation) on computers that are running both 32-bit and 64-bit supported Windows operating systems.
• If some users in your organization are Excel expert users who work with Excel spreadsheets that are larger than 2 gigabytes (GB), they can install the 64-bit edition of Office 2010. In addition, if you have in-house solution developers, we recommend that those developers have access to the 64-bit edition of Office 2010 so that they can test and update your in-house solutions on the 64-bit edition of Office 2010.
This article applies to the current release of Office 2010. For a visual representation of this information, see 64-bit Client Installation of Microsoft Office 2010 (), which includes supported scenarios, deployment considerations, and an overview of the Setup process.
[pic]
In this article:
• Supported Windows operating systems
• Architecture-specific folders and customization tools
• Supported scenarios
• Deployment considerations
• Setup process
• Assessing your current environment for application compatibility
Supported Windows operating systems
The supported Windows operating system editions for 64-bit Office 2010 client include the following:
• 64-bit editions of Windows Vista with SP1
• 64-bit editions of Windows Server 2008 with Service Pack 1
• Windows 7
• Windows Server 2008 R2
The following statements apply:
• The 64-bit Office client can be installed only on 64-bit editions of Windows Vista with SP1, 64-bit editions of Windows Server 2008 with Service Pack 1, Windows 7, and Windows Server 2008 R2.
• The 32-bit Office client is supported as a WOW64 installation. This is the default installation on 64-bit Windows operating systems. The 32-bit Windows-based applications run on 64-bit Windows, which allows for compatibility with 32-bit Office applications and add-ins.
• Office 2010 server products (Microsoft SharePoint Server 2010, Microsoft SharePoint Foundation 2010, and Microsoft Project Server 2010) support the 64-bit edition of Windows Server 2008 with Service Pack 2, and Windows Server 2008 R2. For more information, see the following resources:
• Determine hardware and software requirements (SharePoint Server 2010) ((Office.14).aspx)
• Determine hardware and software requirements (SharePoint Foundation 2010) ((Office.14).aspx)
• Determine hardware and software requirements (Project Server 2010) ((Office.14).aspx)
• For click-to-run scenarios, the supported version is Office 2010 32-bit (WOW64) on computers that run the supported 64-bit editions of Windows operating systems.
Architecture-specific folders and customization tools
Office 2010 includes two architecture-specific folders: one for 32-bit and one for 64-bit.
Each of these folders contains the following:
• A separate Config.xml file and Updates folder.
• An architecture-specific Office Customization Tool (OCT). The OCT files are located in the Admin folder for the x86 (32-bit) and x64 (64-bit) folders, respectively.
The 64-bit version of the OCT provides the same user interface, capabilities, and configurable settings as the 32-bit version. Office 2010 introduces XML versions of OPA files: OPAX files (.opax) for non-language specific resources and OPAL files (.opal) for language-specific resources.
The OCT provides support for importing Setup customization files (.msp files) as follows:
• 64-bit Setup customization files can be imported into 32-bit OCT and can then be used to customize 32-bit Office products.
• 32-bit Setup customization files can be imported into 64-bit OCT and can then be used to customize 64-bit Office products.
A 32-bit Setup customization file that is imported to 64-bit OCT is converted to 64-bit, and a 64-bit customization file that is imported to 32-bit OCT is converted to 32-bit. For more information about how to use the Import feature, see Import an Office 2010 Setup customization file.
[pic]Note:
For the Beta release of Office 2010, administrators can download the 64-bit and the 32-bit editions of Office 2010 from the Office Download pages on the Microsoft TechNet Web site ().
If you have installed Office 2010 including Microsoft Outlook 2010, Outlook sets a registry key named Bitness of type REG_SZ on the computer on which it is installed. The Bitness registry key indicates whether the Outlook 2010 installation is 32-bit or 64-bit. This may be useful to administrators who are interested in auditing computers to determine the installed versions of Office 2010 in their organization.
• Registry path: HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook
• Registry key: Bitness
• Value: either x86 or x64
Supported scenarios
The scenarios that are supported in the Office 2010 64-bit client are as follows.
• Enterprise In enterprise environments, the default is to install Office 2010 32-bit on computers that run either 32-bit or 64-bit editions of Windows operating systems.
We recommend this option.
An alternate approach in enterprise environments is for administrators to do the following:
• Install Office 2010 32-bit on computers that run 32-bit editions of Windows.
• Install Office 2010 64-bit on computers that run 64-bit editions of Windows in order to take advantage of additional memory on the 64-bit computers.
• Retail For users who install Office 2010 from DVDs onto computers that run a supported 64-bit Windows operating system, the installation is by default the 32-bit version of Office 2010 (WOW64).
Retail users who run 64-bit Windows operating systems and do not have 32-bit Office products installed can install the native 64-bit version of Office 2010 from the x64 folder on the DVD.
• Side-by-side installations No support is provided for side-by-side installations of 64-bit and 32-bit editions of Office, including across applications. For example, there is no support for side-by-side installations of the 2007 Microsoft Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit.
• Upgrades The Office client upgrade scenarios are as follows:
• A 2007 Office system 32-bit installation on a computer that runs a 32-bit Windows operating system can be upgraded to an Office 2010 32-bit version.
• A 2007 Office system installation on a computer that runs a 64-bit Windows operating system can be upgraded to an Office 2010 32-bit (WOW64).
• A 2007 Office system installation cannot be upgraded to a native Office 2010 64-bit version.
Deployment considerations
Before you deploy 64-bit editions of Office 2010, you must evaluate the advantages and disadvantages and determine whether it is an appropriate deployment option for your specific environment. The following sections highlight benefits and issues that might affect compatibility, describe Outlook considerations, and list the applications that block and those that do not block a 64-bit Office 2010 installation.
A key consideration is that you cannot install native 64-bit Office 2010 on computers that have 32-bit Office applications and third-party add-ins installed. You must uninstall the 32-bit Office applications and add-ins before you can install 64-bit Office 2010. If you have 32-bit third-party Office applications and add-ins that are required for users, you can install the default option, which is 32-bit Office 2010 (WOW64 installation) on computers that run supported 64-bit editions of Windows. A list of applications that block and those that do not block a 64-bit Office 2010 is included. See Blocking and nonblocking Office applications in 64-bit installations.
In this section:
• Advantages
• Disadvantages
• General feature deprecations
• Considerations for MAPI applications for Outlook
• Blocking and nonblocking Office applications in 64-bit installations
Advantages
Running Office 2010 64-bit provides the following advantages:
• Ability to use additional memory.
• Excel 2010 can load much larger workbooks. Excel 2010 made updates to use 64-bit memory addressing in order to move beyond the 2-GB addressable memory boundary that limits 32-bit applications.
• Microsoft Project 2010 provides improved capacity, especially when you are dealing with many subprojects to a large project.
• Enhanced default security protections through Hardware Data Execution Prevention (DEP).
Disadvantages
The following issues might affect compatibility:
• Microsoft Access MDE/ADE/ACCDE files Databases that have had their source code removed (such as .mde, .ade, and .accde files) cannot be moved between 32-bit and 64-bit editions of Office 2010. Such databases that are created by using 32-bit Office (any version) can be used only with 32-bit Office, and a database that is created on 64-bit Office can be used only on 64-bit Office.
• ActiveX controls and COM add-ins ActiveX controls and add-in (COM) DLLs (dynamic link libraries) that were written for 32-bit Office will not work in a 64-bit process. As a result, Office 2010 64-bit solutions that try to load 32-bit ActiveX controls or DLLs will not work. Installations of 64-bit Office 2010 will run only 64-bit controls. Computers can have 64-bit and 32-bit controls installed, and Office 2010 64-bit can only run the 64-bit versions of the controls. The workaround for resolving these issues is to obtain 64-bit compatible controls and add-ins or to install Office 2010 32-bit (WOW).
In addition to controls that load into Office applications, there are also Web-based solutions that use ActiveX controls in Microsoft Internet Explorer. Office 2010 64-bit editions install some Office 32-bit client-side controls for supporting solutions in a 32-bit browser (the default browser on current 64-bit Windows systems). The Edit in Datasheet view functionality is not supported if you install 64-bit Office 2010. However, the functionality is available if you install 32-bit Office 2010.
• In-place activation The following issues might occur if there is not a match between the bitness of Office 2010 and registered applications:
• An OLE server might not instantiate in place and might fail to open if the application registered is not the same bitness as the version of Office installed. (For example, if the OLE Server application is 32-bit and the version of Office installed is 64-bit.)
• Inserting an object into an Office 2010 application document might fail in cross-bitness scenarios. (For example if you insert a 32-bit object in a 64-bit Office 2010 application document.)
• Graphics rendering There are differences between the 32-bit and 64-bit Graphics Device Interface (GDI) that might have performance implications because of the lack of MMX support on 64-bit. Intel's MMX technology is an extension of the Intel architecture (IA) instruction set. The technology uses a single-instruction, multiple-data (SIMD) technique to speed up multimedia and communications software by processing data elements in parallel.
• Visual Basic for Applications (VBA) VBA code that uses the Declare statement to access the Windows application programming interface (API) or other DLL entry points will see differences between 32-bit and 64-bit versions. The Declare statement must be updated with the PtrSafe attribute after inputs and outputs to the API have been reviewed and updated. Declare statements will not work in 64-bit VBA without the PtrSafe attribute. New data types are added to 64-bit Office 2010 VBA: LongLong and LongPtr. For more information about VBA, see the “64-bit VBA Overview” and “Declare Statement” articles in the Microsoft Visual Basic for Applications online Help in Office applications.
General feature deprecations
The following feature deprecations may affect compatibility:
• Microsoft Access The Replication Conflict Viewer is removed from both the 32-bit and 64-bit installations of Office 2010. This functionality can still be implemented by using the ReplicationConflictFunction Property. ReplicationConflictFunction is a Microsoft Visual Basic for Applications (VBA) routine in the running database that can be used to resolve synchronization conflicts. For more information, see “How to: Set Properties of Data Access Objects in Visual Basic” in Access 2007 Developer Reference ().
• Publisher The Microsoft Works database converter (wdbimp.dll) is removed from both 32-bit and 64-bit installations of Office 2010. This converter was previously used in the Mail Merge functionality to connect to a data source created in Microsoft Works.
• Word Microsoft Office Document Imaging (MODI) and all its components are deprecated for both 32-bit and 64-bit Office 2010.The legacy Equation Editor is not supported on 64-bit Office 2010, but is supported for 32-bit Office 2010 installations (WOW64).
WLL (Word Add-in libraries) WLL files are deprecated for both 32-bit and 64-bit Office 2010. A WLL is an add-in for Microsoft Word that you can build with any compiler that supports building DLLs.
Considerations for MAPI applications for Outlook
If you developed and installed 32-bit Messaging Application Programming Interface (MAPI) applications, there are actions that you should take to change and rebuild 32-bit MAPI applications to run on a 64-bit platform. This also applies for 64-bit applications to run on a 32-bit platform.
Starting with Office 2010, Outlook is available as a 32-bit application and a 64-bit application. The version (bitness) of Outlook that you choose depends on the edition of the Windows operating system (32-bit or 64-bit) and the edition of Office 2010 (32- or 64-bit) that is installed on the computer, if Office is already installed on that computer.
Factors that determine the feasibility of installing a 32-bit or a 64-bit version of Outlook include the following:
• You can install 32-bit Office 2010 and 32-bit Microsoft Outlook 2010 on a supported 32-bit or 64-bit edition of the Windows operating system. You can install the 64-bit version of Office 2010 and 64-bit Outlook 2010 only on a supported 64-bit operating system.
• The default installation of Office 2010 on a 64-bit edition of the Windows operating system is 32-bit Office 2010.
• The bitness of an installed version of Outlook is always the same as the bitness of Office 2010, if Office is installed on the same computer. That is, a 32-bit version of Outlook 2010 cannot be installed on the same computer on which 64-bit versions of other Office 2010 applications are already installed, such as 64-bit Microsoft Word 2010 or 64-bit Microsoft Excel 2010. Similarly, a 64-bit version of Outlook 2010 cannot be installed on the same computer on which 32-bit versions of other Office applications are already installed.
MAPI applications include stand-alone applications such as Microsoft Communicator and MFCMAPI, and service providers such as address book, store, and transport providers. For MAPI method and function calls to work in a MAPI application (except for one Simple MAPI function, MAPISendMail), the bitness of the MAPI application must be the same as the bitness of the MAPI subsystem on the computer on which the application is targeted to run. The bitness of the MAPI subsystem, in turn, is determined by and is always the same as the bitness of the installed version of Outlook. For information about how to prepare MAPI applications for 32-bit and 64-bit platforms, see Building MAPI Applications on 32-bit and 64-bit Platforms ().
Blocking and nonblocking Office applications in 64-bit installations
If 32-bit Office applications are installed on a computer, a 64-bit Office 2010 installation is blocked by default. The following section (Applications that block a 64-bit Office 2010 installation) lists the applications that block a 64-bit Office 2010 installation. The next section (Applications that do not block a 64-bit Office 2010 installation) lists exceptions; that is, applications that do not block the installation. In such cases, installation of 64-bit Office proceeds even if the listed 32-bit applications are installed on the computer.
Applications that block a 64-bit Office 2010 installation
The following applications block a 64-bit Office 2010 installation:
• Microsoft Excel 2010 Viewer
• Access database engine of Microsoft Access 2010
• Microsoft Office 2010 (Click-to-run)
• Compatibility Pack for the 2007 Office system
Applications that do not block a 64-bit Office 2010 installation
The following applications do not block a 64-bit Office 2010 installation:
• Microsoft Visual Studio Web Authoring Component 2007
• 2007 Microsoft Office system 64-bit components
• Microsoft Office 2010 (OEM pre-installation)
• Microsoft Office 2003 Web Components
• Expressions Web Designer
• Microsoft Office XP Web Components
• Microsoft Expression Web 1
• Microsoft Expression Web 1 Language Packs
• Microsoft Expression Web 2
• Microsoft Expression Web 2 Language Packs
• Visual Basic for Applications 6.4 SDK
• Visual Basic for Applications 6.4 SDK International Components
Setup process
This section describes the Setup sequence for a 64-bit Office client installation.
The Office 2010 installation DVD contains both the 32-bit and 64-bit versions of Office 2010 with two architecture-specific folders: one for 32-bit and one for 64-bit, as noted previously. Each of the architecture folders contains a Setup.exe file for the specific platform. There is also a Setup.exe file at the root folder. This is referred to as the platform chooser. The following figure shows the folder structure.
[pic]
The Setup sequence is the same as for a standard 32-bit Office client installation with the addition of specific checks that are performed for 64-bit Office 2010.
The following figure shows the checks that Setup performs for 64-bit installations.
[pic]
The following figure shows how Setup determines whether to install the 32-bit or 64-bit version of Office 2010 when Setup is run from the root of the media source (DVD) that contains both the 32-bit and 64-bit versions of Office 2010.
[pic]
The following section summarizes the Setup sequence of events.
1. Setup checks for 64-bit Office 2010 prerequisites.
When you run Setup.exe from the x64 folder, Setup determines whether 32-bit Office applications are installed. If Setup detects 32-bit Office applications, it displays an error message that informs users that they must first uninstall all 32-bit Office applications if they want to continue with the installation of Office 2010 64-bit. The error message lists the installed 32-bit Office applications. If Setup does not detect 32-bit Office applications, it installs the 64-bit edition of Office 2010.
[pic]Note
• When you run Setup.exe from the x86 folder, Setup determines whether there are 64-bit Office 2010 applications installed. If Setup detects 64-bit Office 2010, an error message is displayed and Setup is blocked. If Setup does not detect 64-bit Office 2010, it installs the 32-bit edition of Office 2010.
• Office Professional Plus 2010 and Microsoft Office Professional 2010 will also be available as a combination release (DVD media) that includes both the 32-bit and 64-bit editions of Office 2010. If Setup is run from the root folder of the Office 2010 DVD that contains both 32-bit and 64-bit Office 2010, Setup performs the installation as follows:
2. Setup reads XML data.
3. Setup builds the feature tree.
4. Setup creates the local installation source.
5. Setup installs Office 2010.
6. Setup applies the 64-bit OCT customization .msp file.
7. Setup applies software updates.
For more information about the Setup sequence, see Setup process in Setup architecture overview for Office 2010.
Assessing your current environment for application compatibility
Office 2010 provides the following new application compatibility tools to help IT professionals evaluate application compatibility issues:
• Office Environment Assessment Tool (OEAT) A tool that you can use to assess your existing environment before you deploy Office 2010. OEAT is designed to help you determine the kinds of add-ins and the extent to which add-ins for Microsoft Office applications are used in your environment. OEAT collects and reports add-in information about Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. It also determines the applications that interact with Office 2010 (by using COM) and provides a summary of the general state of the systems that are scanned. For more information, see Office Environment Assessment Tool (OEAT) user's guide for Office 2010 and Office Environment Assessment Tool (OEAT) quick start guide for Office 2010.
• Microsoft Office Code Compatibility Inspector A tool that you can use in Excel 2010, PowerPoint 2010, Word 2010, and Microsoft Visual Studio 2008 to troubleshoot issues with Microsoft Visual Basic for Application (VBA) macros and add-ins. The tool scans your code for known compatibility issues, and then notifies you if it finds items in the code from the object model that have changed in some way or have been removed. The code inspector tools find code that is incompatible because of changes and deprecations in the Office 2010 object model. The inspector tools can be used to scan code for Declare statements and can update the statements so that they are compatible with the 64-bit version of Office 2010. For more information, see Microsoft Office Code Compatibility Inspector user's guide.
• Office Migration Planning Manager (OMPM) A tool for the 2007 Office system that can also be used to scan for conversion issues that are common to both the 2007 Office system and Office 2010. For more information, see Office Migration Planning Manager (OMPM) overview for Office 2010. A new version of OMPM for Office 2010 will be available shortly after the product releases.
For more information, see Application compatibility overview for Office 2010, and Application compatibility assessment and remediation guide for Office 2010.
Along with the introduction of 64-bit editions of Office 2010, Microsoft is releasing Microsoft Visual Basic for Applications 7.0 (VBA 7) to work with both 32-bit and 64-bit applications. For more information, see Compatibility Between the 32-bit and 64-bit Versions of Office 2010 (). The article discusses the changes that apply to the 64-bit version of Office 2010, introduces the new VBA 7 code base, and discusses compatibility issues between the 32-bit and 64-bit versions of Office 2010 and suggested solutions.
See Also
Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ()
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Setup architecture overview for Office 2010
Technical diagrams for Office 2010
These resources are visual representations of recommended solutions. They include poster-sized documents available in formats including Microsoft Office Visio 2007 files (.vsd), PDF files, and XPS files. You might need extra software to view these files. See the following table for information about opening these files.
|File type |Software |
|.vsd |Office Visio 2007, or the free Visio viewer |
| |() |
| |If you use the Visio viewer, right-click the VSD link, click Save Target As, save |
| |the file to your computer, and then open the file from your computer. |
|.pdf |Any PDF viewer, such as Adobe Reader |
| |() |
|.xps |Windows Vista, Windows XP with .NET Framework 3.0, or XPS Essentials Pack |
| |() |
Models
Models are 34-by-44-inch posters that detail a specific technical area. These models are intended to be used with corresponding articles on TechNet. These models are created by using Microsoft Visio 2010 or Office Visio 2007. You can modify the Visio files to illustrate how you plan to incorporate Microsoft Office 2010 in your own environment.
|Title |Description |
|Deployment Options for Microsoft Office 2010 |Describes and illustrates the client deployment methods for Office |
|[pic] |2010. Deployment options include network share, Group Policy startup |
| |scripts, managed deployment, and virtualization. Use this model with |
| |the following article: Choose an option for deploying Office 2010. |
|Download () | |
|Deploy Multilanguage Packs for Microsoft Office 2010 |Describes and illustrates how to deploy multilanguage packs for |
|[pic] |Office 2010. Elements include evaluation criteria, planning |
| |considerations, and deployment tasks. Use this model with the |
| |following article: Plan for multilanguage deployment of Office 2010. |
|Download () | |
|64-bit Client Installation of Microsoft Office 2010 |Describes and illustrates the 64-bit client installation of Office |
|[pic] |2010. Elements include setup overview, processes, requirements, |
| |deployment considerations, and supported scenarios. Use this model |
| |with the following article: 64-bit editions of Office 2010. |
|Download () | |
|Virtualization Overview - Architecture |Describes and illustrates the architectural overview of |
|[pic] |virtualization technology and the different models that are possible.|
| |Use this model with the following article: Plan for virtualization. |
| | |
|Download () | |
|Application Virtualization - Delivery Methods |Describes and illustrates delivery methods of virtualization, focused|
|[pic] |on sequencing. Use this model with the following article: Plan for |
| |virtualization. |
| | |
|Download () | |
|Application Virtualization for the Mobile User |Describes and illustrates stand-alone delivery method of virtualized |
|[pic] |applications for mobile users. Use this model with the following |
| |article: Plan for virtualization. |
| | |
|Download () | |
Getting help with Office 2010
There are several support options for the Microsoft Office 2010 suites. This article describes some of the options that are available.
In this article:
• Support options in the Backstage
• Other support options
Support options in the Backstage
The Microsoft Office Backstage is new feature within the Fluent user interface (UI) throughout the Office 2010 suites. The Backstage view provides the following options for finding help:
• Getting Started Links to the Getting Started Web site, which helps users quickly learn Office 2010 applications.
• Contact Us A link to connect users to the Microsoft Help and Support Web Pages where you can find Product Solution Centers and Customer Service Solution Centers.
Other support options
Outside of the Backstage, you can still find help as it was in the previous versions. Other support options include the following:
• F1 The standard help Function key still brings up the Microsoft Help and How-To within each product in the Office 2010 suites. This command can be easily added to the Quick Access Toolbar for quick reference.
• Microsoft Download Center You can download help and product updates from the Microsoft Download Center ().
• Office 2010 Resource Centers You can find information for IT administrators about Office 2010 on the Office 2010 resources page (). Specific resources include Evaluate and Get Started, Plan the Deployment, Configure and Deploy, Application Compatibility, Migration and Upgrade, Volume Activation and Licensing, Feature Changes, and System Requirements.
Planning the deployment of Office 2010 Beta
This section provides information about how to assess the current environment, and how to plan for desktop configurations, security, and applications including Microsoft Access 2010, Microsoft Excel 2010, Microsoft Outlook 2010, and Microsoft Project 2010. It also provides planning information for migration and upgrading from previous versions of Office, as well as planning for virtualization and Terminal Services.
In this section:
|Article |Description |
|Assess the environment for Office 2010 |Describes some of the tools and methods that are available to help |
| |plan the deployment of Microsoft Office 2010. |
|Plan desktop configurations for Office 2010 |Provides information and guidelines about items to consider before |
| |you deploy Office 2010. |
|Plan a migration and upgrade strategy for Office 2010 |Provides information about how to plan the installation of the |
| |Microsoft Office 2010 suites, and how to migrate the user data, such |
| |as user and computers settings and documents created from the |
| |previously installed versions of Microsoft Office. |
|Plan for volume activation of Office 2010 |Provides an overview of Microsoft Volume Licensing and Office |
| |Activation Technologies for Office 2010 and how describes how to plan|
| |for volume activation. |
Assess the environment for Office 2010
This section describes some of the tools and methods that are available to help plan the deployment of Microsoft Office 2010.
In this section:
|Article |Description |
|Assessment tools for Office 2010 |Describes some of the tools that are available to help complete the |
| |assessment step in the planning process for deploying Office 2010. |
|Application compatibility overview for Office 2010 |Provides the primary resources for Office 2010 application |
| |compatibility information and includes links to the new application |
| |compatibility tools and documentation. |
|Office Migration Planning Manager (OMPM) overview for Office 2010 |Provides an overview of the Office Migration Planning Manager (OMPM),|
| |which is a collection of tools that enables you to prepare an |
| |environment for migration to Office 2010. |
Assessment tools for Office 2010
This article describes some of the tools that are available to help complete the assessment step in a planning process.
Assessment tools
|Area |Tool |Description |Resources |
|Project |Microsoft Rapid|The Microsoft Rapid Economic Justification |Microsoft Rapid Economic Justification |
|assessment / |Economic |guide walks you step-by-step through the |guide() |
|business case |Justification |project assessment process in two to four | |
| |guide |weeks — from fiscal analysis to boardroom | |
| | |presentation. It includes tools, templates, | |
| | |and how-to information to help you make a | |
| | |compelling business case for an IT project. | |
|Hardware |Microsoft |The Microsoft Assessment and Planning (MAP) |Microsoft Assessment and Planning (MAP) Toolkit for |
|inventory / |Assessment and |Toolkit is an inventory, assessment, and |Microsoft Office 2007 |
|compatibility |Planning (MAP) |reporting tool that can securely run in small |() |
| |Toolkit |or large IT environments without requiring the| |
| | |installation of agent software on any | |
| | |computers or devices. | |
| | |The MAP Toolkit performs a detailed analysis | |
| | |of hardware and device compatibility for | |
| | |migration to the 2007 Microsoft Office system,| |
| | |Windows 7, Windows Server 2008, Windows Server| |
| | |2008 R2, Microsoft Application Virtualization | |
| | |(App-V), Windows Vista, and more. The hardware| |
| | |assessment examines the installed hardware and| |
| | |determines whether migration is recommended. | |
| | |If it is not recommended, the reports tell you| |
| | |why it is not. | |
| | |In addition, MAP has expanded its capabilities| |
| | |into assessment areas of Hyper-V server | |
| | |virtualization, desktop security, and | |
| | |Microsoft SQL Server 2008 migration. | |
|Software |Microsoft |With the Microsoft Software Inventory Analyzer|Microsoft Software Inventory |
|inventory |Software |(MSIA), you can generate an inventory of core |Analyzer() |
| |Inventory |Microsoft products installed on a local |Microsoft Software Asset |
| |Analyzer (MSIA)|computer, or throughout a network. |Management() |
| | |The MSIA is built specifically to be a | |
| | |starting point to work with Microsoft Software| |
| | |Asset Management. To that end, MSIA works with| |
| | |networks that have 250 computers or fewer, and| |
| | |locates only Microsoft software. | |
|Office add-ins |Office |The Office Environment Assessment Tool (OEAT) |Application compatibility overview for Office 2010 |
| |Environment |is designed to help an organization determine | |
| |Assessment Tool|the types of add-ins and the extent to which | |
| | |add-ins for Microsoft Office applications are | |
| | |used on users’ computers. OEAT collects and | |
| | |reports add-in information about Microsoft | |
| | |Office 2000 and later versions. | |
|User settings |User State |You can use Windows User State Migration Tool |User State Migration Tool 4.0 User's |
| |Migration Tool |(USMT) 4.0 to migrate user files and settings |Guide() |
| | |during large deployments of Windows Vista and | |
| | |Windows 7 operating systems. USMT captures | |
| | |desktop and application settings, user | |
| | |accounts and users' files, and then migrates | |
| | |them to a new Windows installation. | |
| | |One component of the USMT is ScanState. | |
| | |ScanState scans the source computer, collects | |
| | |the files and settings and creates a store. | |
| | |ScanState does not modify the source computer.| |
| | |By default, ScanState compresses the files and| |
| | |stores them as an image file (USMT4.mig). | |
|File / document|Office |The Office Migration Planning Manager (OMPM) |Office Migration Planning Manager (OMPM) overview for |
|management |Migration |checks for, and reports on, file properties to|Office 2010 |
| |Planning |help you analyze an environment and determine | |
| |Manager (OMPM) |any issues that you might experience when you | |
| | |convert from Office 97-Office 2003 file | |
| | |formats to the file formats for the 2007 | |
| | |Office system and Microsoft Office 2010 | |
| | |systems. | |
| | |OMPM for Office 2010 supports two new types of| |
| | |scanning: macro scanning and x64 migration | |
| | |scanning. The macro scanner optionally scans | |
| | |any macros it encounters for migration | |
| | |concerns, reports any issues it finds in the | |
| | |database, and optionally inserts comments into| |
| | |the macros identifying the issue with links to| |
| | |possible resolutions. The x64 migration | |
| | |scanner scans macros, ActiveX controls, and | |
| | |other COM objects (such as add-ins) in Office | |
| | |files for incompatibilities (for example, | |
| | |declaring 4-byte pointers instead of 8-byte | |
| | |pointers). | |
|Security |Microsoft |Microsoft Security Assessment Tool (MSAT) 4.0 |Microsoft Security Assessment |
| |Security |consists of more than 200 questions that cover|Tool() |
| |Assessment Tool|infrastructure, applications, operations, and | |
| |4.0 |people. The questions, associated answers, and| |
| | |recommendations are derived from generally | |
| | |accepted best practices, standards such as ISO| |
| | |17799 and NIST-800.x, and recommendations and | |
| | |prescriptive guidance from the Microsoft | |
| | |Trustworthy Computing Group and other external| |
| | |security sources. | |
|Security |System Center |Microsoft System Center Configuration Manager |System Center Configuration Manager |
| |Configuration |2007 can assess, deploy, and update servers, |TechCenter() |
| |Manager |client computers, and devices — across | |
| | |physical, virtual, distributed, and mobile | |
| | |environments. | |
| | |Client status reporting in System Center | |
| | |Configuration Manager 2007 R2 provides | |
| | |up-to-date information about the manageability| |
| | |of client computers in a System Center | |
| | |Configuration Manager 2007 hierarchy. A site | |
| | |administrator can use this information to | |
| | |identify individual client problems and to | |
| | |maintain a more accurate site database. The | |
| | |information can also help increase software | |
| | |distribution success rates. | |
|Licensing |Microsoft |Microsoft Volume Licensing provides many |Manage Your Volume |
| |Volume |online reporting services and tools that you |Licenses() |
| |Licensing |can use to track and manage your existing | |
| | |Microsoft software assets. | |
|Configurations |Group Policy |The Group Policy Management Console (GPMC) is |Group Policy Management Console Technical |
| |Management |the UI console to author and manage |Reference() |
| |Console (GPMC) |domain-based Group Policy objects (GPOs). The | |
| | |GPMC displays linking, permissions, and | |
| | |security filtering information relevant to a | |
| | |GPO. It also generates settings reports on a | |
| | |GPO in either HTML or XML format. | |
|Configurations |View XML |See View XML content from Office Customization|View XML content from Office Customization Tool |
| |content from |Tool customization files |customization files |
| |Office |(() |
| |Customization |) for a sample Microsoft Visual Basic script | |
| |Tool (OCT) |that administrators can use to view the | |
| |customization |settings that are stored in OCT .msp files. | |
| |files | | |
|Help |Microsoft |Microsoft Desktop Deployment Planning Services|Microsoft Volume Licensing Software |
| |Desktop |(DDPS) offers customers 1 to 15 days of |Assurance() |
| |Deployment |deployment planning services, based on how |You can find a Desktop Deployment Planning Services |
| |Planning |much Microsoft Software Assurance they |provider in your area by using the Microsoft Solution |
| |Services (DDPS)|purchase on Office software. Customers work |Finder (). |
| | |with consultants to develop a high-level | |
| | |desktop deployment plan for their environments| |
| | |and to assess the overall cost of upgrading to| |
| | |the latest versions of Windows and Office. | |
Application compatibility overview for Office 2010
This article provides the primary resources for Microsoft Office 2010 application compatibility information and includes links to the new application compatibility tools and documentation. These resources are especially useful for IT professionals who have to evaluate application compatibility issues and implement a plan for fixing incompatible Microsoft Office applications. Developers who are upgrading Office applications might also find the information that is listed in this article useful.
[pic]Important:
The application compatibility tools and resources that are discussed in this article will be available sometime during the Office 2010 Beta release.
In this article:
• Application compatibility and Office 2010
• Office Environment Assessment Tool
• Office Code Compatibility Inspector
• Office Migration Planning Manager
• Application Compatibility Assessment and Remediation Guide
• ISV Application Compatibility Visibility Program
• Application compatibility community resources
Application compatibility and Office 2010
Application compatibility issues can be a challenge for any organization that is migrating from an earlier version of Office to Office 2010. The most common application compatibility issues occur when an add-in or a Visual Basic for Applications (VBA) macro uses an Office feature that was removed or modified in Office 2010. To work correctly with the new version of Office, the add-in or VBA macro must be updated.
You can update applications many ways. If you have the source code for the incompatible add-in or VBA macro, a developer can usually update the application by modifying the application’s code. If the incompatible add-in or VBA macro is compiled, you must get the updated application from the vendor that compiled and distributed the application. This update process — known as the remediation process — is typically performed together with other tasks, such as application compatibility assessment, application testing, and piloting. Together, these tasks make up the application compatibility assessment and remediation process, which is shown in the following illustration.
[pic]
To help IT professionals and developers implement this process, we created a suite of application compatibility tools and resources for Office 2010. IT professionals who are evaluating application compatibility issues across an organization can use the tools and resources to do the following:
• Identify add-ins, VBA macros, and other applications that could cause application compatibility problems.
• Identify commercially available applications that are compatible with Office 2010.
• Analyze application compatibility assessment data and implement a plan for testing and remedying incompatible applications.
Developers who are upgrading add-ins and VBA macros can use the tools and resources to do the following:
• Identify sections of code that must be changed.
• Apply known object model changes and feature changes that cause code compatibility issues.
• Understand the remediation steps that are required to fix incompatible applications.
The following sections provide a summary of the application compatibility tools and documentation that will be available for Office 2010.
Office Environment Assessment Tool
The Office Environment Assessment Tool (OEAT) helps you determine the kinds of add-ins that are installed on users’ computers and the extent to which the add-ins are used. OEAT collects and reports add-in information about Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. It also identifies the applications that interact with Office (by using COM) and provides a summary report of the general state of the systems that are scanned. However, OEAT is not a software inventory tool, and it is not a substitute for inventory tools such as Microsoft System Center Configuration Manager 2007. For more information about how to use the OEAT, see Office Environment Assessment Tool (OEAT) quick start guide for Office 2010 and Office Environment Assessment Tool (OEAT) user's guide for Office 2010.
Office Code Compatibility Inspector
In addition to the assessment tool, there are two code inspection tools: the Microsoft Office Code Compatibility Inspector for VBA and the Microsoft Office Code Compatibility Inspector for Visual Studio. Each tool is an add-in that you install with Office 2010. The tools scan VBA, , and C# code for object model usage that is incompatible with Office 2010. When an inspector finds code that is incompatible with Office 2010, it adds a comment to the code. The comments can then be read by a developer when the developer updates the code. The inspector tools find code that is incompatible because of changes and deprecations in the Office 2010 object model. The inspector tools also scan code for Declare statements and can update the statements so that they are compatible with the 64-bit version of Office 2010. For more information about how to use the Inspector, see Microsoft Office Code Compatibility Inspector user's guide.
Office Migration Planning Manager
The Office Migration Planning Manager (OMPM) is a collection of tools that enables you to prepare an environment for migration to Office 2010. OMPM checks for, and reports on, file properties and contents to help you analyze the environment and determine any issues that you might experience converting from Office 97 Office 2003 file formats to Office 2010 file formats. For more information about OMPM, see Office Migration Planning Manager (OMPM) overview for Office 2010.
Application Compatibility Assessment and Remediation Guide
The Application compatibility assessment and remediation guide for Office 2010 describes the overall assessment and remediation process, including planning, testing, piloting, and deployment. In addition to recommended guidelines and best practices information, the guide contains information about feature deprecations and changes for each Office 2010 application. The guide is useful to IT professionals who must create and implement an application compatibility assessment and remediation plan. It is also useful for developers who are fixing applications that are incompatible with Office 2010.
ISV Application Compatibility Visibility Program
The Office 2010 Application Compatibility Visibility Program helps organizations find independent software vendors (ISVs) who pledge that their products are compatible with Office 2010. ISVs submit information about their products through a special ISV portal. The information is then listed on the Office 2010 Compatibility Center. The Office Environment Assessment Tool (OEAT) is integrated with the Application Compatibility Visibility Program. When the OEAT identifies an ISV application, it checks the Visibility Program Web site for information about the application and writes the information to the OEAT’s scan report. As part of the compatibility pledge, ISVs must provide the following information:
• Whether their product is compatible with 64-bit and 32-bit versions of Office 2010.
• Which Office 2010 applications their product is compatible with.
• Which versions of their application are compatible with Office 2010.
Application compatibility community resources
In addition to the application compatibility tools and documentation, there are several community resources that are focused on Office 2010 application compatibility, including a formal feedback mechanism for the Application Compatibility Visibility Program, a blog, and a forum. The feedback mechanism lets IT professionals and developers provide information to Microsoft about their real-world experience with an ISV’s pledged product. The forum encourages knowledge sharing among IT professionals and developers who are evaluating and remedying application compatibility issues. The blog provides ongoing and timely guidance from Microsoft about application compatibility issues and solutions.
See Also
Assessment tools for Office 2010
Application compatibility assessment and remediation guide for Office 2010
Through research, we have identified that one of the core barriers to a successful deployment of Microsoft Office is remediating application compatibility issues that slow or prevent the deployment process. This article contains information to help your organization assess the effect on customizations of Office applications when you migrate from an earlier version of Office to Microsoft Office 2010. It outlines a prescribed method for assessing, planning, testing, and remediating issues in relation to a deployment of Office 2010.
Upgrading to a new version of Office applications is not a simple undertaking and should be approached with careful planning. Office 2010 is a major release that offers many improvements and new features. Increasing Office application deployment readiness can be achieved by performing various tasks including capturing an inventory of custom applications and customizations to Office applications, assessing how these customizations will migrate, and then remediating any compatibility issues. A summary of the process is shown in the following illustration.
[pic]
This article takes you through the steps of identifying add-ins and line-of-business (LOB) applications that earlier versions of Office are using in your environment.
After completing the steps detailed in this guide, your organization will have a better understanding of what interacts with Office and how to deal with migrating those items to Office 2010. The benefits of this process include the following:
• Faster deployment of Office 2010.
• Fewer deployment issues, especially towards the late end of the deployment cycle.
• A more accurate identification of support and help desk issues.
• Documentation for user readiness training.
• Fewer issues that interfere with their job functions which results in increased user productivity and acceptance of the updated product.
• A better understanding of the purpose, function, and support for every application and add-in that results in better documentation of the environment and faster resolution of issues.
In this article:
• Office customizations
• Plan for compatibility testing
• Assess the environment
• Remediate compatibility issues
• Test and pilot remediations
• References and resources
Office customizations
Developers and experienced users of Office have been writing code to customize and extend Office almost since the first Office products were introduced.
There are various methods that can be used to customize Office applications. Office supports extensibility methods such as application add-ins (.dot, .wll, .xll, .xla, mda, etc.), Automation add-ins, XML expansion packs, XML style sheets, and smart tags. These can be developed in-house by the IT application development team or purchased from a third-party vendor.
Although customizations help users become more productive, they can be the cause of various compatibility issues when they migrate to a new version of Office applications. When addressing the compatibility of Office solutions, understanding how these customizations are developed is an important key to determining how to reduce possible issues that might occur during or after an Office migration.
Customizations to Office applications can be put into one of the following four classifications: macros, templates, add-ins, and Automation.
Macros
A macro is a series of commands and instructions that are grouped together to perform a task automatically. Macros can be contained in a document so that the functionality it provides can be shared with other users. In most Office programs, frequently used tasks can be automated by creating macros. Whereas some macros are a recording of a user’s keystrokes or mouse clicks macros can also be very extensive, which provide in-depth capabilities.
Example uses for macros are as follows:
• To automate routine editing and formatting.
• To combine multiple commands such as inserting a table with specific formatting and with a specific number of rows and columns.
• To make an option in a dialog box more available.
• To automate a complex series of tasks.
Visual Basic for Applications (VBA) is used to create macros in Windows-based applications and is included with several Microsoft programs. VBA is a macro-language version of Microsoft Visual Basic. VBA projects are viewed through the Visual Basic for Applications Editor (VBE).
Templates
Templates can automate the creation of documents. They provide organizations and their users a standardized method for creating company documents. contains thousands of templates. These templates can save an organization the time that is required to develop, distribute, and maintain standardized documentation. For more information about templates, see Deploy custom templates in the 2007 Office system ().
Add-ins
Add-ins are supplemental programs that can be installed to extend the capabilities of Office applications. Add-ins are typically COM objects that are loaded at runtime. COM add-ins let developers use a programming language and environment of their choice when they create Office-based solutions. After a COM add-in is written, it is then compiled as a DLL. The DLL can be loaded by one or more Office applications and can interact with Office object models.
Microsoft introduced the COM add-in as part of Microsoft Office 2000. COM components are generally more sophisticated than macros. For example, an add-in can add the capability of sending a document to a fax machine or an add-in might be designed by your organization to highlight company names in any document that you open on your computer.
COM-based add-ins must be registered and added to the following registry subkeys:
\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\\AddIns
\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\\\AddIns
In this example is the name of the application in which the add-in runs and is the number that represents the version of the Office suite. For example, version number of Office 2010 is 14.0.
Automation
Automation is the process of using COM to call Office APIs to perform specific tasks. An example of an Office automation process is a CRM application that writes customer’s billing data to a Microsoft Excel or Microsoft Word document to create an invoice.
For more information about Automation, see Office Automation Using Visual C++ () and Common Tasks in Office Programming ().
The following table lists the different kinds of Office customizations, the development tools that were used to create the customizations, and the likely compatibility status of that kind of customization.
|Office add-in type |Development tool |Status |
|Office XML format (xlam, |Use VBE similar to the previous, Save As to a macro-enabled add-in type. |Current |
|.dotm, .ppam) |For more information, see XML file name extensions in the 2007 Office system | |
| |(). | |
|VSTO add-in (.NET DLLs) |Microsoft Visual Studio 2008 |Current |
|Office 97-2003 format VBA |VBE, included with Office applications and accessed from the Developer tab on the |Legacy, still supported |
|template add-in (XLA, DOT, |application ribbon | |
|PPA, etc.) | | |
|COM add-in (Windows DLL) |Microsoft Visual Studio |Legacy, still supported |
|Automation add-ins (XLL or |XLL (specific to Excel) and WLL (specific to Word) and written in C+. When |Legacy, still supported |
|WLLs) |developing a new Excel or Word add-in, you should consider the features presented | |
| |with the current Office add-ins architecture. | |
| |For more information, see Excel COM add-ins and Automation add-ins | |
| |(). | |
Plan for compatibility testing
The planning phase is intended to determine the overall scope of the effort and to determine key roles and responsibilities. Included in this phase is the planning for the rest of the steps that are needed to prepare for application compatibility testing.
Planning activities
With any project, there is work that is required to manage and track the progress. For organizations that plan this work from a central organization but perform the work at the business units, building a central repository of discovered applications and the testing progress of each can keep the progress of the project on track. A tool that can centralize the results of the project such as Microsoft SharePoint Server 2010 can maintain a list of applications and their status within the complete process.
Identify stakeholders
A stakeholder is defined as the person or group that approved and will allocate resources to the project. The stakeholder is the person or group that is paying for the project whereas the user is the person who directly uses the result of the project deliverables. It is important to define the stakeholders so that the application compatibility upgrade team can communicate and validate the project deliverables to those that have a vested interest.
The following table shows the typical stakeholders in an Office application compatibility upgrade project.
|Role |Stake |
|Application Owner |Ensures that the business process done by using the previous Office |
| |version continues uninterrupted after the upgrade. |
|Project Sponsor |Promotes the success of the Office upgrade and positive publicity |
| |within the organization. |
Assign roles
The following table describes possible roles and their respective responsibilities that have to be filled in an application compatibility project:
|Role |Responsibility |
|Project manager |Ensures the overall flow of the project, manages overall resources, |
| |metrics and risks. |
|Compatibility Validation Tester (CVT) |Tests Office components for any potential incompatibility issues, |
| |that is file format, macros, add-in or Office automation. The CVT |
| |tester follows the test plan. |
|OMPM operator |Understands and performs setup and configuration of the OMPM tool in |
| |the context of this project. |
|Remediation lead |Performs the actions that resolve compatibility issues on Office |
| |customizations. |
|Regression tester (RT) |Ensures that the remediation performed on an Office object is |
| |successful. This role is often filled by the remediation lead. |
|User acceptance tester (UAT) |Representative of an affected business unit who determines that the |
| |remediation of an object was successful and that it does not |
| |interfere with other customizations or actions. This should never be |
| |the person who performs the remediation or regression testing. |
|Business analyst or owner |Owns the code and documentation of the customization objects that are|
| |critical to the business unit. |
|Deployment group lead (DGL) |Owns and tracks the timeliness of the complete technical process. |
| |Might delegate some reporting or administration activities. |
|Creates application package |Owns the Office 2010 installation package. |
|Client (Desktop) Team |Owns the deployment of the Office 2010 package via the organization’s|
| |configuration management tool, such as Systems Center Configuration |
| |Manager (SCCM). |
|Service Desk |Provides functional support of Office for the testers and, when the |
| |migration is complete, the users. |
Assessment planning
The goal of the assessment planning phase is to determine the techniques that will be used to discover applications and customizations that could be affected by an Office upgrade. By using tools such as the Office Environment Assessment Tool (OEAT) and Office Migration Planning Manager (OMPM) you can detect add-ins and line-of-business application applications that interact with Office and assess documents and templates that contain possible VBA solutions. Planning for the assessment phase is shown in the following illustration.
[pic]
Classification of applications
It is common for enterprises to develop, deploy, and maintain a wide variety and number of applications that use Office. These applications can have significantly different values to the organization. It is important to organize applications into classes or tiers based on the value of the application to the business. A simple method to use is to classify an application as either business-critical or not. Additional classifications are as follows:
• Line-of-business applications.
• Department.
• Unmanaged solutions (or end-user developed templates, add-ins, or macros).
An organization can consider using the approach to assessing Office customizations shown in the following table.
| |Mission critical |Non-mission critical |
|Add-ins |Proactive inventory scan, test, and |React to user discovered |
| |remediation | |
|Office Automation |Proactive manual inventory, test, and |React to user discovered |
| |remediation | |
|Macros/VBA |Proactive OMPM scan and remediation |React to user discovered |
| |Proactive Office Environment Assessment Tool |React to user discovered |
| |Proactive Office Code Compatibility Inspector |React to user discovered |
|Documents |Proactive OMPM scan and remediation |React to user discovered |
Types of deployments
During this planning phase, your organization might have already decided how it will deploy Office 2010. If this decision is not made, it is difficult to complete the assessment planning process. For more information about how to determine the best migration strategy, see Determining the best migration strategy ().
Test planning
Test planning includes strategies for creating a test environment, developing automation scripts, and defining the method for the reporting of issues found during testing. The steps that are needed to plan for the test phase are shown in the following illustration.
[pic]
Remediation planning
Remediation involves solving compatibility issues that are discovered during testing. Although the actual remediation work is difficult to plan, there are generic steps that can resolve issues for each kind of customization. The steps that are needed to plan for the remediation phase are shown in the following illustration.
[pic]
The following table describes generalized solutions for resolving Office customization issues during a migration.
|Type |Potential Strategy |
|In-house application that has a limited lifetime |Retire the application and find a new process. |
|In-house application that has a long lifetime |Rewrite or rework the code to fit the new object model. |
|Third-party application that has a limited lifetime |Retire the application and find a new process. |
|Third-party application that has a long lifetime |Contact the vendor for update or replacement. |
|Application is not working |Reinstall the application with a new directory structure or create a |
| |virtual environment for the application. |
Microsoft also has prescriptive information on TechNet about known issues that occur when you migrate Office customizations. For more information, see Migration considerations by application (). There are also Microsoft partners who have tools that help the remediation process.
Assess the environment
After the planning phase, the next step is to assess the environment. The assessment phase collects an inventory of custom solutions and their 2007 Office system compatibility status. Planning and performing an assessment includes identifying the systems that will be assessed, the deployment method to use, and performing the scan of the environment.
Preassessment tasks
Before you start an assessment, you must gather information about the applications that you expect to find and the systems that you plan on assessing.
Identify and interview business units
The first stage is to determine your departmental or business unit groupings. Each division must be assessed separately. For example, the accounting department might have a different set of important add-ins and applications than the human resources department. A good understanding of your organizational divisions and their needs is important to determining a relevant sample of computers to scan. After starting with functional departments, you can refine the set of systems that you want to scan by also interviewing key stakeholders in each business unit. The idea is gain an understanding of each groups needs and how the current set of applications is fulfilling those needs.
Some add-ins for Office applications might have been created informally within your organization. Often, these are add-ins created for a specific business process. It might not be possible to identify the owner or author of these add-ins. Therefore, some investigative work might be required to identity down an owner and the original source code, if it still exists. Knowing the importance of the add-in, its purpose, why it was made, what it does, and who made it are all important in making an informed decision about how to remediate it, and correct issues as they are found.
The following is an example of data to capture for each solution:
|Application information |
|Business group |
|Application name |
|Application contact/owner |
|AppID |
|Version |
|Priority |
|Tier |
|Office 2010 compatibility status (Pass, Fail) |
|Compatibility issue description |
|Number of users |
|Office version used by the application (XP, 2003, 2007, 2010, and so on.) |
|Describe the kind of usage (For example, exports an Office document, add-in to Office application, and so on.) |
|Office suite components used by the application |
|Word |
|Excel |
|Access |
|PowerPoint |
|Other |
|Does this application use complex Office objects such as charts, pivot tables, or drawing art? |
|Is this a data entry/front-end application? If Yes, provide details. |
|Which language(s) does the application support? |
Identify systems and servers
Before you can even start the process of scanning your environment, you must determine a sampling of systems and documents against which you will run tests and then perform an environmental assessment. Not all systems have to be scanned. Choose a group of users who is representative of the different needs that users have when they use Microsoft Office applications.
Scan the environment
When planning for your migration to Office 2010, specific knowledge about the computers on the network and their readiness for migration is important. Microsoft provides several tools to help with discovery, assessment, and mitigation of migrating Office templates, macros, and add-ins, or other customizations. This section provides guidance on the how to use each tool and the information that each tool provides. These tools include the following:
• Office Environment Assessment Tool
• Office Migration Planning Manager
• Office Code Compatibility Inspector
Office Migration Planning Manager (OMPM)
For the most part, documents created in Office 2003 and earlier Office versions behave the same way when they are opened in 2007 Office and Office 2010. However, there might be instances where files require manual intervention or analysis to ensure consistent behavior. For example, a custom solution built in Microsoft Office Excel 2003 might require modification because it relies on legacy Office features that are no longer supported in Excel 2010.
OMPM is a collection of tools that analyzes your environment and reports on file properties. You can also use OMPM to scan for and identify templates. OMPM includes the following features:
• A file scanner (offscan.exe) that scans files to identify possible conversion issues. The OMPM File Scanner performs is a command-line tool two kinds of scans:
A light scan that quickly identifies the Office documents on a user’s computer or network file system.
A deep scan that identifies Office documents and collects document properties that provide indicators of potential conversion issues.
• A set of utilities that automates creating a new database (in Microsoft SQL Server 2000, Microsoft SQL Server 2005, or Microsoft SQL Express) and then imports the XML log files generated by the OMPM File Scanner from scanned computers into that database.
• A reporting solution based in Microsoft Access 2010 that provides reports for your analysis and enables you to define file sets for automated processing.
• The Office File Converter (OFC) that enables you to convert specific files to the new Office release file formats in bulk.
• The Version Extraction Tool (VET) that extracts the contents of a file in Word 2003 and earlier versions of Word and then saves that content to a different file.
OMPM tools can be deployed by using an automated software deployment technology, such as Systems Management Server (SMS), or a logon script. To download OMPM, see 2007 Microsoft Office System Migration Guidance: Microsoft Office Migration Planning Manage ().
For more information about how to use OMPM in your environment, see Assess your environment by using the Office Migration Planning Manager () and Determining the best migration strategy ().
Office Environment Assessment Tool (OEAT)
OEAT is designed to help you determine the kinds of add-ins and the extent to which add-ins for Microsoft Office applications are used in your environment. OEAT collects and reports add-in information about Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. It also determines the applications that interact with Office 2010 (by using COM) and provides a summary report of the general status of the systems that are scanned.
The core purpose of OEAT is to help you assess what applications and add-ins you have in your environment that tie into Office APIs. This tool will also help you assess which add-ins vendors have verified will work with Office 2010 and give you enough information about other add-ins and applications in your environment to perform meaningful remediation of potential issues before you deploy.
[pic]Note:
OEAT is not an inventory tool, and it should not be used to collect information about user systems in your environment.
Information generated by OEAT
The following are the two major categories of information that is provided by OEAT:
• Systems Summary Report A summary of the hardware and software environment of your organization. This summary includes the following information:
• Drive Space
• Installed Memory
• Processor Types
• Computer Types
• Windows Installs
• Installed Anti-virus
• Charts that represent the summary reports
• Detailed Add-ins Report A detailed report of all systems scanned.
The following are some screen shot examples of reports that are generated by OEAT:
• AllInstalledAddins This report contains a list of all add-ins and automations that were found during the scans of your environment. This includes add-ins provided by Microsoft (installed with Office), third-party applications and add-ins, and line-of-business application or custom applications and add-ins that are installed in your environment.
• AddinsNotInstalledByOffice This report contains a list of all add-ins not included with Office. From this report, you get all custom applications, line-of-business applications, in-house add-ins, and third-party add-ins installed in your environment. The add-ins and applications on this list are the most likely to have compatibility issues with an Office upgrade.
• System Readiness Summary Report This report contains summary information that is useful in helping you determine whether your scanned systems are ready for Office 2010. These include reports on available and average free space on hard disks, processors on the systems scanned, computer manufacturers for the systems scanned, Windows installations (including service packs), and antivirus information (current status).
To download OEAT, see Office 2010 Tool: Office Environment Assessment Tool (). For more information about how to use OEAT, see Office Environment Assessment Tool (OEAT) quick start guide for Office 2010 and the Office Environment Assessment Tool (OEAT) user's guide for Office 2010.
Microsoft Assessment and Planning Toolkit
The Microsoft Assessment and Planning (MAP) Toolkit is a set of inventory assessment and reporting tools that can securely inventory small or large network environments without requiring the installation of any agent software on your computers. The data and analysis that the tool provides can significantly simplify the planning process for many migration projects.
You can enable MAP to discover computers in your environment or you can specify which computers to inventory using one of the following options:
• Active Directory Domain Services (AD DS)
• Windows networking protocols
• Computer names from a file
• An IP address range
• Manually entered computer names
For more information about MAP, see Microsoft Assessment and Planning (MAP) Toolkit for Microsoft Office 2007 ().
Additional tools
There are many other tools that you can use to help you perform a more detailed analysis of your environment. For more information, see Assessment tools for the 2007 Office system. ()
Remediate compatibility issues
After scans are run in your environment, you then have to study the results and determine a plan of action. If an application is determined to have compatibility issues, you must decide how those issues will be addressed.
One point stressed in the assessment and remediation processes is that after you have assessed your environment, and identified and categorized your add-ins and line-of-business applications that interact with Office, it is important to perform a methodical, iterative process of testing each add-in or application feature and function to verify it behaves as expected. Differences and issues should be cataloged so that appropriate actions can be taken. The next few sections discuss those different remediation options.
Once you have identified what each business unit has installed, and you have prioritized the applications and components found, you can start remediating those items. This involves the testing of each application and either contacting vendors or solution providers for updates, code fixes and solutions, or identifying workarounds (up to and including virtualization). This process is iterative and can move between pilot and lab testing until the release of Office is stabilized.
Assess the results
Some of the most common kind of add-ins you are likely to find in your environment are provided by third-party vendors. These add-ins are found and assessed by OEAT scans. Microsoft maintains a list of the add-ins that are verified by the vendor as compatible with Office 2010. Each time that you compile the results of an OEAT scan, you have the option to download an updated version of this list. OEAT compares the add-ins found in your environment with the vendor list and then assigns a compatibility status to each add-in. The compatibility status is one of the following options:
• GREEN The add-in is on the list of vendor add-ins that are compatible with Office 2010.
• YELLOW The vendor has reported that your version of the add-in is incompatible with Office 2010, but another version of the add-in might be compatible.
• UNKNOWN The add-in is currently not in the Microsoft vendor list of Office 2010 add-ins so the status of this add-in is unknown.
• MICROSOFT The add-in is included with earlier versions of Office 2010.
If the compatibility status is GREEN or YELLOW, a link to a Microsoft site is included that provides additional information.
Prioritize applications
It is common for enterprises to develop, deploy, and maintain a wide variety and number of applications that use Office. These applications can have significantly different values to the organization. It is important to acknowledge this fact, and then organize applications in classes or tiers based on the value of the application to the business. You can start by classifying an application as either mission-critical or not. Then an organization might consider the approach shown in the following table to classify Office customizations.
| |Mission critical |Non-mission critical |
|Add-ins |Proactive inventory scan, test, and |React to user discovered issues |
| |remediation | |
|Office Automation |Proactive manual inventory, test, and |React to user discovered issues |
| |remediation | |
|Macros/VBA |Proactive OMPM scan and remediation |React to user discovered issues |
| |Proactive Converter Technology solution |React to user discovered issues |
|Documents |Proactive OMPM scan and remediation |React to user discovered issues |
After you have identified the applications that are mission-critical, you can then continue to prioritize the list of applications by the numbers of users it has and whether executives used the applications.
Categorize the applications that have the highest business priority as Tier 1, followed by Tier 2 and Tier 3. Then identify applications that are out of scope. As you remediate the applications, you might find that their priority can change from your initial assessment. You should put a strict process in place for remediation assessments to only allow an application to move up in tier (but not down). For information about how Microsoft IT categorized and prioritized applications, see Deploying the 2007 Office System at Microsoft ().
• Tier 1: Mission Critical These applications are executive-used applications of any number of users and business priority. This category also includes applications that are used by more than 10% of the organization’s users and a business priority of external or mission-critical. Failure of these applications is damaging to business continuity or revenue of the organization.
• Tier 2: Business Critical These applications are business-critical or are used by 10% or more of the organization’s users. This tier can also include applications used by 1% to 10% the organizations users and be of any business priority. These are not mission-critical or revenue affecting applications, but they could indirectly increase expenses or reduce revenues by affecting productivity.
• Tier 3: Business Applications These applications are not mission-critical and can effect as few as 10 employees or up to 1 percent of the organization. They are usually tools that help small tasks and that have a low effect on the business.
Identify known issues
Microsoft discusses, in many areas, the changes from one version of Office to another. In the Migration Considerations per Application section, there is a more detailed result set for considerations moving from Office 2003 to Office 2010 and the 2007 Office system to Office 2010. From a higher level, this section will outline how these changes will affect the users in your environment, the solutions that integrate with Office and how they should be approached from a remediation standpoint.
Deprecations
As Microsoft makes changes to the application, there are some features that are removed from the application. When a feature is removed, all of the object model references to the feature are also removed. Deprecations can pose challenges if the feature is important to users. In-house and third-party add-in and line-of-business application solutions that interact with those removed features will also be affected.
Remediating removed features can require a lot of effort. It can require either obtaining an updated version of an add-in or application from a vendor, that no longer relies on a particular feature (if the vendor has provided one), or updating in-house solutions to no longer use the feature. If the feature is important or causes a failure of an extensively used line-of-business application, it might be required to implore solutions such as Microsoft Application Virtualization (App-V), Remote Applications, or Virtual PC to let that solution to still operate with a legacy version of Office in a virtualized environment.
Feature changes
Another kind of challenge is application changes in Office where a feature is updated to behave differently than it behaved in previous versions. This usually only poses a user challenge that is resolved through training. However, these changes can also affect the object model of a feature (whether the change is in the interface or not). Object model changes can cause customizations and third-party solutions such as add-ins and line-of-business applications that interact with Office to not operate as expected. Sometimes these changes are obvious, and other times they are only discovered through testing.
64-bit vs. 32-bit platforms
Operating systems and applications are available in 32-bit and 64-bit versions. Windows Vista, Windows 7 and Office 2010 are available in 64-bit versions. When reviewing the list of applications that are found in the network environment, ensure that you note whether the applications are designed for a 32-bit or 64-bit platform. Moving to a 64-bit platform might pose the largest challenge to legacy applications and add-ins.
32-bit Visual Basic 6.0, C, and C++ applications
Add-ins created in earlier versions of Visual Basic, C, or C++ that are developed for 32-bit systems, are incompatible with 64-bit versions of Office. There are remediation options for older add-ins and applications that interact with Office are as follows:
• If the application is internally managed and the source code still exists, you can recompile it as a 64-bit application by using Visual Studio 2008 with the x64/AMD64 option.
• If the application was purchased from a vendor, ask whether the vendor will provide a 64-bit version of the application.
You can run the application in a virtual 32-bit environment which users can access by using App-V, RemoteApp, or Virtual PC.
VSTO solutions
The runtime components for Office 2010 were created in Microsoft Visual Studio so that Visual Studio Tools for Office 2005 and Visual Studio 2008 .NET add-ins (VSTO), document solutions, and spreadsheet solutions will all run on 64-bit Office 2010. These runtime components are installed with Office_2nd_CurrentVer. Therefore an administrator does not have to include a separate installation for this runtime. However, there are other considerations that are needed.
In a Visual Studio project, C# or Visual Basic .NET code can be compiled into Microsoft intermediate language (MSIL) when the Any CPU option is used. At runtime the MSIL is Just in Time (JIT) compiled to the correct chip set, either AMD or Intel 32-bit or 64-bit. However, this technology does not apply to the .NET Framework in versions 1.0 and 1.1. These versions do not enable this 64-bit transformation.
Even conforming .NET Framework 2.0 code must be reviewed because calls to a process invoke (p/invoke) in your code are native (processor architecture specific). If you try to call native API methods by using p/invoke, you can have issues with your VSTO solution running correctly on 64-bit Office 2010.
Issues can also occur if the code makes deliberate calls to a Win32 API that does not have exactly the same signature (method name, parameter list, and DLL name) of an equivalent Win64 API. This is true for any solution, whether it is an Office solution or Windows based solution.
For more information about authoring solutions today for 64-bit Office 2010, see the MSDN Library Visual Studio 2005 article about how to develop 64-bit Applications () and the MSDN Library Visual Studio 2008 article about how to develop 64-bit Applications ().
VBA solutions and macros
Solutions and macros created by using VBA will function as long as they interface with the Office 2010 object model. However, certain calls might be deprecated and will no longer function. If VBA code is using Windows API calls, these calls were likely to 32-bit DLLs. A simple fix is to update the code so that the Declare statements use the PtrSafe keyword. For more information about VBA 64-bit compatibility, see 64-bit editions of Office 2010 ().
ActiveX controls
ActiveX controls that are native 32-bit controls (which is likely to be any control compatible with the 2007 Office system and previous Office versions), are not supported in 64-bit Office 2010. Remediation for any of these controls will require a recompile (if the source code is available), asking or waiting for a vendor update, or using a virtualization method.
Test for compatibility issues
After you have identified all the add-ins and line-of-business applications in your environment, and you have categorized and classified them, reviewed vendor add-ins and applications (or received updates), identified stakeholders for internally designed applications, you can start remediating each item to be included in your deployment. This section outlines the testing processes for identifying and remediating issues with:
• General LOB applications testing
• Office add-ins testing
• Macros and scripts testing
• Automated applications testing
General LOB application testing
[pic]
Office add-in testing
[pic]
Macros and scripts testing
[pic]
Office automation testing
[pic]
Remediate issues
There are several approaches to correcting an application or add-in that has a compatibility issue with Office 2010. The options include the following:
• Getting an update from the vendor.
• Updating the code for internal solutions.
• Rewriting solutions.
Get updates from vendors
OEAT reports provide links to add-ins known to be compatible. However, some applications might not be on this list. In this case, you have to contact the vendor directly. If the vendor plans an update to the add-in, but their timeframe does not work with the timeline of your migration to Office 2010 or if the vendor is unwilling to update their add-in or is no longer in business, you must seek an alternative, workaround the limitations or problems posed by the add-ins incompatibilities (should they be more minor), or consider a virtualization or parallel installation.
Update internal applications
When you have the source code and understand how the add-in or application functions or you have documentation and the original development team is still active or can be consulted, you have an ideal situation to update an internal application.
However, often a tool has a high priority, but you cannot locate a developer, source code, or an owner. In these situations, you should consider parallel installations or virtualization or a rewrite of the application or add-in.
If the application has a clear purpose and is a high priority, you might find documentation or source code, and even have access to the developer or team that created it. In this case, you have more options available to you. You can update the add-in or application by using tools such as the Microsoft Office Code Compatibility Inspector to help your development team in the process.
If the platform for writing the solution is very old (such as Visual Basic 6, or earlier versions), you should consider a complete rewrite of the tool into the .NET Framework.
Using Microsoft Office Code Compatibility Inspector
Updating add-ins and line-of-business applications that interact with Office and Office add-ins is a difficult troubleshooting and debugging task. To simplify this process, Microsoft has designed a set of tools that help developers in these tasks. These tools are the Office Code Compatibility Inspector for VBA and the Office Code Compatibility Inspector for VSTO.
Each tool is an add-in that installs with Office 2010 and Visual Studio 2008. Each operates on a per-user, per-document, and per-solution basis. A developer can run the Office Code Compatibility Inspector on an open document or Visual Studio Solution (Visual Basic .NET or C#).
The Inspector does not fix code. Each tool scans the solution (by using a simple text search) for known parentObject.Property combinations that have been changed or deprecated. Each also scans VBA Declare statements and update them for 64-bit compatibility. As potential issues are found, comments are added in the code to help a developer while debugging the solution for Office 2010 compatibility.
Each time that an Inspector scan is complete, a summary and detailed report of what was found in the project is provided. Items that are scanned include the following:
• Changes from Office 2000 to Office 2010 If there is a syntactical change it is flagged.
• Deprecations from Office 2000 to Office 2010 If an item was added then later deprecated or deprecated from a long standing feature, it is flagged.
The following is an example of Inspector results:
[pic]
Using parallel installation or virtualization
When there is no practical recode or rewrite solution, there are additional options that can assist you in finding a solution to a compatibility issue.
• If you are waiting for vendor updates for an add-in that might be delivered at some date past your deployment date, you can opt to install Office 2003 or earlier in parallel with Office 2010 (or just the specific applications that are waiting for vendor updates, for example, such as Excel 2003).
[pic]Note:
If you are moving to a 64-bit version of Office 2010, you cannot have a parallel installation of the 2007 Office system (or earlier version) installed at the same time. All previous versions are available only in 32-bit versions.
• If you are running Windows 7, you can install a parallel install of Office 2003 (or earlier) in Windows XP compatibility mode, or if you are on an older version of Office, you can install it in a Virtual PC environment.
• Use App-V (formally known as SoftGrid). For more information about App-V, see Microsoft Application Virtualization 4.5 SP1 ().
• Use Windows Terminal Services and perform one of two options:
• If you have Windows Server 2003, you can use Windows Terminal Services to provide desktop computers that can run these solutions remotely with an earlier version of Office.
• If you have Windows Server 2008, you can install RemoteApp. This will give users the feeling of the legacy application and the legacy version of Office on their system. For more information about RemoteApp, see Deploy Windows Server 2008 Terminal Services RemoteApp ().
Test and pilot remediations
Although the focus of this guide is individually remediating and finding solutions for each add-in and line-of-business application that interacts with Office, you cannot assume that these remediations will function together. You have to test all remediations together and then pilot these in a real-world scenario. Each step is important in validating the remediations, stabilizing the overall deployment of Office 2010, and ultimately creating a more successful migration.
Lab tests
It is important to clearly define your goals for the test lab and its long-term purpose. A test environment must simulate your production environment as closely as possible. Test plans must detail what you will test and the steps to follow when testing each component. You should develop a use case for each add-in and application that you have remediated to verify that each functions as planned in an isolated environment. Then, as each remediation option is verified, it should be rolled into the overall deployment pilot for Office 2010.
The following illustration shows from a high level the general process for planning and developing a test lab, and from a remediation standpoint.
[pic]
Pilot
Conducting the pilot is the last major step before deployment of Office 2010. The pilot is the ultimate proving ground for the remediated options and it should be part of the project team’s role to remain involved through the piloting of Office 2010 to capture and correct any problems that occur. During the pilot, your release management team monitors a controlled environment in which users perform their typical business tasks using the new features including remediated applications and add-ins that interact with Office 2010. This demonstrates that the remediation’s function as expected and that the organization’s business requirements are met.
As issues are reported in the pilot, an iterative approach should be taken to remediate the problems found, design a new test case, perform tests, and then deploy the updated applications back into the pilot for additional review. Specific focus should be given to how well these options work, user feedback, and any issues that limit the scope or functionality of the add-in or application that was remediated.
References and resources
Office 2010 has many new and modified features that make it easier for information workers to do their jobs. For information about feature changes, see the following resources:
• Changes in Office 2010 ()
• Changes in Access 2010 ()
• Changes in Excel 2010 ()
• Changes in InfoPath 2010 ()
• Changes in OneNote 2010 ()
• Changes in Outlook 2010 ()
• Changes in PowerPoint 2010 ()
• Changes in Project 2010 ()
• Changes in Publisher 2010 ()
• Changes in SharePoint Designer 2010 ()
• Changes in SharePoint Workspace 2010 ()
• Changes in Visio 2010 ()
• Changes in Word 2010 ()
See Also
Office Environment Assessment Tool (OEAT) quick start guide for Office 2010
Office Environment Assessment Tool (OEAT) user's guide for Office 2010
Microsoft Office Code Compatibility Inspector user's guide
Office Migration Planning Manager (OMPM) overview for Office 2010
Office Environment Assessment Tool (OEAT) quick start guide for Office 2010
This article contains quick-start information about how to use the Office Environment Assessment Tool (OEAT) to assess your existing environment before you deploy Microsoft Office 2010. OEAT is designed to help you determine the kinds of add-ins and the extent to which add-ins for Microsoft Office applications are used in your environment. OEAT collects and reports add-in information about Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. It also determines the applications that interact with Microsoft Office (by using COM) and provides a summary report of the general state of the systems that are scanned.
To download OEAT, see Office 2010 Tool: Office Environment Assessment Tool ().
[pic]Note:
OEAT is not an inventory tool, and it should not be used to collect information about user systems in your environment. For a more in-depth assessment of your Windows environment, see Microsoft Assessment and Planning Toolkit ().
In this article:
• Steps to configure OEAT
• How OEAT works
• OEAT command-line parameters
Steps to configure OEAT
OEAT is designed to run from a script that is available on a network share. It scans specified systems as the user logs in and then saves the results of the scans to a designated location, usually a network share. After the results are generated, OEAT then compiles those results into a Microsoft Excel spreadsheet that can be used to assess the environment and prepare for remediation as part of planning for the deployment of Office 2010. The following list details the steps that you must follow to successfully run OEAT in your environment:
1. Identify users and systems.
2. Create the network share.
3. Configure OEAT settings.
4. Create a script.
5. Compile scan results.
Identify users and systems
OEAT produces a system summary report that is designed to help you assess your current Microsoft Office environment so that you can better prepare for a deployment to another version of Microsoft Office. The purpose of OEAT is to collect a statistically relevant sampling of the systems in your environment. Not all systems need to be scanned. Choose a group of users that is representative of the different needs that users have when they use Microsoft Office applications.
Create the network share
OEAT is designed to run on the network without the need for administrative or user actions. To do this, you need to create a network share that will hold the OEAT application file, the results of the scans, and the results of the scan data compilation. When you create the share, you need to assign the user accounts that have been selected Contributor permissions to the share.
[pic]Note:
OEAT is a user-mode tool. This means that it cannot be run in a system context, with a system account, or as a service. Some of the information that OEAT collects requires administrative rights on the local computer. Therefore, the user account that runs OEAT must belong to the Administrators group on the local computer on which it is run.
Configure OEAT settings
Use the following procedure to create a settings file that OEAT uses when it runs scans on computers in your environment. The settings file is automatically saved to the folder that contains OEAT.exe.
[pic]To configure OEAT settings
|1. Navigate to the network share created for OEAT, and then double-click OEAT.exe. |
|2. On the Startup page, click Run settings file setup Wizard (Administrator). |
|[pic] |
| |
|3. On the Setup Wizard page, click Next. |
|[pic] |
| |
|4. On the Environment Scanning Information page, click each More information link to view a list of the items that are scanned on |
|each computer. To continue, click Next. |
|[pic] |
| |
|5. On the Passive Scan Settings page, you can specify the length of time that OEAT will wait between performing scans. Click More |
|information to open a message box that contains an explanation of what a passive scan is and how it is performed. To continue, |
|click OK in the message box. |
|[pic] |
| |
|On the Passive Scan Settings page, click Yes if you want to schedule the scans. Otherwise, click No. If you click Yes, in the Time|
|section, expand the selector, and then click hours or days. Type or use the arrow keys to specify the number of hours or days |
|between scans. |
|Select the Run hidden (silent) on the client while scanning check box if you want the scan to run in the background without user |
|interaction, and then click Next. |
|6. On the Results Folder Location page, type the UNC of the share to which scan results will be saved. For example: \\server |
|name\share name\results. Click Next. |
|[pic] |
| |
|7. On the Done page, click Finish. |
|[pic] |
Create a script
To automate the scans performed by OEAT, you can create a script and then copy the script to the folder that contains OEAT.exe. Be sure to replace \\\ with the UNC of the share that contains OEAT.exe. You can distribute the script to designated users by using a logon script or other means, as you want. Regardless of how the script is distributed, it must run with administrative rights on the local computer.
The following is a JScript code sample that you can edit to use in your environment.
// ***************************************************************
// Office Environment Assessment Tool Script
// CREATED: 8-14-2009
// VERSION:1.0
// PURPOSE:To launch the OEAT application from specified
// UNC share with the SCAN switch.
// ***************************************************************
/* create a scripting object */
w = new ActiveXObject("WScript.Shell");
/* shell the OEAT.exe scanner */
w.run("\\\\\\\\oeat.exe -scan");
/* done */
Compile scan results
After OEAT has collected data from scans in your environment, it can then compile the results into a Microsoft Excel spreadsheet for analysis. Use this procedure to compile OEAT scan results into an XML file.
[pic]To compile scan results
|1. Navigate to the network share that contains the scan results and the OEAT.exe file. |
|2. Double-click OEAT.exe. |
|3. On the Startup page, click Compile results (Administrator). |
|A message box might display that asks whether you want to update the Vendor.xml file. Click Yes to update the file. |
|4. A window opens with a progress bar that shows the progress of the compilation. |
How OEAT works
OEAT performs a passive scan on the system. The tool performs this scan by creating an audit key on the specific Word, PowerPoint, Excel, and Outlook CLSID Automation keys in the Windows registry. The tool then goes into passive (sleep) mode for a number of hours (or days, depending on the setting configured). When any application automates an Office application, Windows captures that event and adds it to the Windows Security log. Once the passive mode elapses and OEAT resumes operation, it removes the audit keys from the Windows registry and then reads the Windows Security log. The process of adding and removing the Windows registry audit keys and reading the Security log requires that the current user has administrative rights on the computer.
If OEAT is run on a system with a user account that does not have administrative rights, you will see a series of errors similar to the following in the Errors.log file generated by OEAT:
... SCAN: Error setting permissions on registry keys. PERMISSION ERROR: System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. … at OfficeAddinScanner.clsWatcher.addAudits()
These errors are caused as OEAT tries, but fails, to set a QueryValue audit on each of the following keys in the registry:
• Excel = HKEY_CLASSES_ROOT\CLSID\{00024500-0000-0000-C000-000000000046}
• PowerPoint = HKEY_CLASSES_ROOT\CLSID\{91493441-5A91-11CF-8700-00AA0060263B}
• Word = HKEY_CLASSES_ROOT\CLSID\{000209FF-0000-0000-C000-000000000046}
• Outlook = HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}
The failure occurs if the user account does not have administrative rights on the local computer. If you cannot assign user accounts administrative rights on the local computer, you can try to run OEAT by using a script that runs with Local System rights by using an administrative management system such as Systems Management Server (SMS) or Microsoft System Center Operations Manager (SCM).
OEAT command-line parameters
OEAT can be run at the command prompt or in a script by using the set of parameters shown in the following table.
|Scan |Runs OEAT.exe with the scan option. |
| |This parameter requires a Settings.xml file that is saved to the same|
| |folder as OEAT.exe. The Settings.xml file specifies the configuration|
| |that OEAT uses to run scans. |
|Setup |Runs the Setup wizard that creates the Settings.xml file. |
|Compile |Compiles the scan result files into an XML file. This file is saved |
| |to the folder that is specified in the Settings.xml file. If no |
| |Settings.xml file exists, the default configuration is used and the |
| |compilation of data is saved to a file in the current directory. |
|Help |Opens the Help file, which contains the following information: |
| |To scan a system from the command line, or to distribute this |
| |application and have it run from a logon script (or some other |
| |distribution method) you will want to do the following: |
| |1. Make sure the Settings.xml file is in the same folder as the |
| |OEAT.exe file. |
| |2. Run OEAT.exe with the '-scan' command line switch. |
| |You can also use these additional command lines switches: |
| |-debug:see a status message if the scan fails. |
| |-help :to see this screen again. |
| |-compile:to compile the results. |
| |-setup:to run the setup wizard. |
|Debug |Stops the scan if there is an error and displays a message box that |
| |describes the error. |
See Also
Office Environment Assessment Tool (OEAT) user's guide for Office 2010
Office Environment Assessment Tool (OEAT) user's guide for Office 2010
This article contains information about how to use the Office Environment Assessment Tool (OEAT) to assess your existing environment before you deploy Microsoft Office 2010. OEAT is designed to help you determine the kinds of add-ins and the extent to which add-ins for Microsoft Office applications are used in your environment. OEAT collects and reports add-in information about Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. It also determines the applications that interact with Office 2010 (by using COM) and provides a summary of the general state of the systems that are scanned.
To download OEAT, see Office 2010 Tool: Office Environment Assessment Tool ().
In this article:
• Planning an Office deployment by using OEAT
• Information provided by OEAT
• Steps to configure OEAT
• Deployment scenarios
• View OEAT data
• Review OEAT data
Planning an Office deployment by using OEAT
Microsoft Office is more than only a set of applications. It is a platform that allows rich interaction with other applications and data through its Open Object Model application programming interface (Office API). The purpose of OEAT is to help you assess which applications and add-ins you have in your environment that tie into the Office API. OEAT is an important step in preparing your environment for a successful deployment of Office 2010. It performs an assessment of your existing environment. The purpose of this assessment is to understand what potential issues that you might encounter before, during, and after the deployment. OEAT provides a snapshot of your organization’s add-ins and other applications that automate Office 2010. The result is a much smoother deployment that will reduce the burden on your help desk over issues dealing with incompatible add-ins and applications.
The following diagram shows the steps of an Office 2010 deployment. OEAT fits into the Assessment/Scan step of an Office 2010 deployment strategy.
[pic]
For more information about the assessment and remediation process, see Application compatibility assessment and remediation guide for Office 2010.
• Deployment Planning Determine your Office 2010 deployment project milestones.
• Scan Run OEAT on selected systems to assess the environment.
• Analyze and Plan Review OEAT scan results to compile a list of add-ins and determine the importance and compatibility of these add-ins.
• Remediate and Pilot Develop a plan for each add-in and third-party application in your existing desktop deployment and in your new image that remediates any issues. Implement updates, test, and then pilot the changes in your organization.
• Deploy Expand the pilot to deploy the Office 2010 upgrade to your organization.
Information provided by OEAT
The following are the two major categories of information that is provided by OEAT:
• Systems Summary Report A summary of the hardware and software environment of your organization. This summary includes the following information:
• Drive Space
• Installed Memory
• Processor Types
• Computer Types
• Windows Installs
• Installed Anti-virus
• Charts that represent the information in the summary
• Detailed Add-ins Report A detailed listing of all systems scanned. This includes reports on the following:
• All add-ins found Microsoft add-ins that are included with Office 2010.
• Add-ins not installed with Office A list of add-ins found that are not included with Office 2010.
• Raw data A collection of all information scanned from all systems. This information can be used for queries and additional customized reports.
Assessing the results
Microsoft maintains a list of the add-ins that are verified by the vendor as compatible with Office 2010. Each time that you compile the results of an OEAT scan, you have the option to download an updated version of this list. OEAT compares the add-ins found in your environment with the vendor list and then assigns a compatibility status to each add-in. The compatibility status is one of the following options:
• GREEN The add-in is on the list of vendor add-ins that are compatible with Office 2010.
• YELLOW The vendor has reported that your version of the add-in is incompatible with Office 2010, but another version of the add-in might be compatible.
• UNKNOWN The add-in is currently not in the Microsoft vendor list of Office 2010 add-ins so the status of this add-in is unknown.
• MICROSOFT The add-in is included with earlier versions of Microsoft Office.
If the compatibility status is GREEN or YELLOW, a link to a Microsoft site is included that provides additional information.
Additional reports
There are many roles that are part of a deployment team. The people in these roles can use data that is provided by OEAT to report the readiness of the environment for an Office 2010 deployment. Team members can also create custom reports by using the RAW DATA that is collected by OEAT.
Steps to configure OEAT
OEAT is designed to run from a script that is available on a network share. It scans specified systems as the user logs in and then saves the results of the scans to a designated location, usually a network share. After the results are generated, OEAT then compiles those results into a Microsoft Excel spreadsheet that can be used to assess the environment and prepare for remediation as part of planning for the deployment of Office 2010. The following list details the steps that you must follow to successfully run OEAT in your environment:
1. Identify users and systems.
2. Create the network share.
3. Configure OEAT settings.
4. Create a script.
5. Compile scan results.
Identify users and systems
OEAT produces a system summary report that is designed to help you assess your current Office 2010 environment so that you can better prepare for a deployment to another version of Office 2010. The purpose of OEAT is to collect a statistically relevant sampling of the systems in your environment. Not all systems need to be scanned. Choose a group of users that is representative of the different needs that users have when they use Office 2010 applications.
How to identify users and systems to scan
When you identify the target users and systems that should be scanned by OEAT, you must first identify how information technology is managed in your environment: divisionally, centrally, or unmanaged. This guide approaches the use of OEAT from either a centrally managed or divisionally managed IT perspective. For guidance about how to run OEAT in an unmanaged environment, see Scenario 3 later in this article.
For a centrally or divisionally managed organization, when you are trying to determine a statistically relevant sampling of target computers, you can look to functional departments or divisions. Each division must be assessed separately. For example, the accounting department might have a different set of critical add-ins and applications than the human resources department. A good understanding of your organizational divisions and their needs is critical to determining a relevant sample of computers to scan. After starting with functional departments, you can refine the set of systems that you want to scan by also looking at Active Directory organizational units (OU).
Define a significant sample
Once you determine the different groups that need to be scanned, you can start the process of identifying a statistically relevant sampling of each. Not every system in your organization needs to be scanned. However, in some cases (depending on the size of the organization) scanning the entire environment or an entire group or OU might be less restrictive (or easier) than to delineate separate systems to participate. A statistically relevant sampling of no more than 20 percent should provide enough information to successfully assess and correct the compatibility issues in your Office 2010 environment.
Configure tool prerequisites
The following components are required for OEAT to run on your target systems:
• Microsoft .NET Framework 2.0
• 2007 Microsoft Office system (for compiling results)
OEAT required permissions
OEAT performs a passive scan on each system. It performs this scan by adding an audit key to the Word, PowerPoint, Excel, and Outlook CLSID Automation keys in the Windows registry. The path of each key is as follows:
• Excel = HKEY_CLASSES_ROOT\CLSID\{00024500-0000-0000-C000-000000000046}
• PowerPoint = HKEY_CLASSES_ROOT\CLSID\{91493441-5A91-11CF-8700-00AA0060263B}
• Word = HKEY_CLASSES_ROOT\CLSID\{000209FF-0000-0000-C000-000000000046}
• Outlook = HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}
If OEAT is run on a system by using a user account that does not have the rights that are required to edit the registry, a series of errors are written to the errors.log file. You can perform the following workarounds if the user account that runs OEAT does not have the rights that are required to edit the registry:
1. Create a Group Policy object (GPO) that sets the values of the audit keys. For more information about how to set audit key values by using a GPO, see How to use Group Policy to audit registry keys in Windows Server 2003. ()
2. Deploy the tool to run under the Local System account by using a management solution such as Systems Management Server (SMS) or System Center Configuration Manager (SCCM). SMS and SCCM let you set up a Data-Collection Package. Specifically, you would follow these steps:
a. Deploy the OEAT.exe and Settings.xml files locally to a folder off the root of drive C on each of the target systems.
b. Have the tool run from the Startup folder or Windows Run registry key.
c. Copy the XML file generated by the tool, and place it on a network share on a designated server.
Create the network share
OEAT is designed to run on the network without the need for administrative or user actions. To do this, you need to create a network share that will hold the OEAT application file, the results of the scans, and the results of the scan data compilation.
[pic]Note:
OEAT is a user-mode tool. This means that it cannot be run in a system context, with a system account, or as a service. Some of the information that OEAT collects requires administrative rights on the local computer. Therefore, the user account that runs OEAT must belong to the Administrators group on the local computer on which it is run.
When you create the network share for OEAT, you need to assign the user accounts that have been selected Contributor permissions to the share. To allow users access to this folder, you should share the folder by using Full Permissions for everyone. Apply the permissions to the share as shown in the following figure.
[pic]
You must also check the NTFS permissions on the folder. Check NTFS permissions on the Security tab of the folder properties. Ensure Read, Execute, and Write permissions for each account that needs to access the folder are assigned. Apply NTFS permissions to the folder as shown in the following figure.
[pic]
Configure OEAT settings
Use the following procedure to create a settings file that OEAT uses when it runs scans on computers in your environment. The settings file is automatically saved to the folder that contains OEAT.exe. Before beginning this procedure, place the OEAT.exe application in that network share.
[pic]To configure OEAT settings
|1. Navigate to the network share created for OEAT, and then double-click OEAT.exe. |
|2. On the Startup page, click Run settings file setup Wizard (Administrator). |
|[pic] |
| |
|3. On the Setup Wizard page, click Next. |
|[pic] |
| |
|4. On the Environment Scanning Information page, click each More information link to view a list of the items that are scanned on |
|each computer. To continue, click Next. |
|[pic] |
| |
|5. On the Passive Scan Settings page, you can specify the length of time that OEAT will wait between performing scans. Click More |
|information to open a message box that contains an explanation of what a passive scan is and how it is performed. To continue, |
|click OK in the message box. |
|[pic] |
| |
|On the Passive Scan Settings page, click Yes if you want to schedule the scans. Otherwise, click No. If you click Yes, in the Time|
|section, expand the selector, and then click hours or days. Type or use the arrow keys to specify the number of hours or days |
|between scans. |
|Select the Run hidden (silent) on the client while scanning check box if you want the scan to run in the background without user |
|interaction, and then click Next. |
|6. In the Results Folder Location page, type the UNC of the share to which scan results will be saved. For example: \\server |
|name\share name\results. Click Next. |
|[pic] |
| |
|7. On the Done page, click Finish. |
|[pic] |
| |
|8. Verify that the setup of OEAT was successful by checking for the following items in the network share: |
|• OEAT.exe |
|• Settings.xml |
|• OEAT.js |
Create a script
To automate the scans performed by OEAT, you can create a script and then copy the script to the folder that contains OEAT.exe. Be sure to replace \\\ with the UNC of the share that contains OEAT.exe. You can distribute the script to designated users by using a logon script or other means, as you want. Regardless of how the script is distributed, it must run with administrative rights on the local computer.
The following is a JScript code sample that you can edit to use in your environment.
// ***************************************************************
// Office Environment Assessment Tool Script
// CREATED: 8-14-2009
// VERSION:1.0
// PURPOSE:To launch the OEAT application from specified
// UNC share with the SCAN switch.
// ***************************************************************
/* create a scripting object */
w = new ActiveXObject("WScript.Shell");
/* shell the OEAT.exe scanner */
w.run("\\\\\\\\oeat.exe -scan");
/* done */
Compile scan results
After OEAT has collected data from scans in your environment, it can then compile the results into an Excel spreadsheet for analysis. Use this procedure to compile OEAT scan results into an XML file.
[pic]To compile scan results
|1. Navigate to the network share that contains the scan results and the OEAT.exe file. |
|2. Double-click OEAT.exe. |
|3. On the Startup page, click Compile results (Administrator). |
|A message box might display that asks whether you want to update the Vendor.xml file. Click Yes to update the file. |
|4. A window opens with a progress bar that shows the progress of the compilation. |
Deployment scenarios
The following is a list of scenarios that are based on preferred methods of deploying and running OEAT.
Scenario 1
If you plan to run the tool in an Active Directory environment, you can deploy the tool by using a GPO (Active Directory Login Script). For more information about how to deploy the tool by using Group Policy, see How to use Group Policy to audit registry keys in Windows Server 2003 ().
Scenario 2
You can deploy OEAT by using a management solution such as SMS or SCCM. SMS and SCCM let you set up a Data-Collection Package. To do this, complete the following steps:
1. Deploy the OEAT.exe and Settings.xml files locally to a folder off the root of drive C on each of the target systems.
2. Have the tool run from the Startup folder or Windows Run registry key.
3. Copy the XML file generated by the tool, and place it on a network share on a designated server.
For more information about SCCM, see System Center Configuration Manager 2007 ().
For more information about SMS, see Systems Management Server ().
Scenario 3
In an unmanaged or non-centralized IT environment, you can either create a central location for the OEAT script file for users or send OEAT to users with instructions on how to use it.
If you create a central location, follow the instructions in Create the network share earlier in this article. To create a script for the users, follow the instructions in Create a script also earlier in this article. Send a link to the OEAT.JS script in an e-mail message with instructions for the users to click the link. As users receive the e-mail message, they can click the link to perform the scan of their system. The results will be stored in the central server location for later compiling.
If you choose to send OEAT to the users with instructions on how to use it, provide the users with the step-by-step instructions for each dialog box. Instruct the users to select Scan your system on the Startup page, and to send the XML file that contains the results back to you in an e-mail message.
View OEAT data
This section covers the data that is generate by OEAT and includes some strategies for getting the most out of this information. As provided, the data provides a very broad view of the system environment and a detailed view of the add-ins that are installed on each scanned computer. The data is put into an Excel workbook that contains several sheets so that it can be analyzed.
The following is a list of spreadsheets that are in the Excel workbook generated by OEAT:
• System Readiness Summary Report This spreadsheet contains summary information that is useful in helping to determine whether your scanned systems are ready for Office 2010. It includes data on available and average drive space, processors, computer manufacturers, Windows installations (including service pack levels), and antivirus information (current state) on the systems scanned. You can format the data into charts that present the information in a more graphical manner.
• AllInstalledAddins This spreadsheet contains a list of all add-ins and automation applications that were found as part of the system scans. This includes add-ins provided by Microsoft (installed with Office), third-party applications and add-ins, and line of business or custom applications or add-ins that are installed in your environment.
• AddinsNotInstalledByOffice This spreadsheet contains a list of all add-ins that are not included with Office. Much of your assessment and planning should come from this report. It includes all custom applications, line of business applications, in-house add-ins, and third-party add-ins that are installed in the environment.
The last few columns of this spreadsheet are some of the most meaningful in the assessment and remediation of compatibility issues.
• UNKNOWN The add-in is currently not in the Microsoft vendor list of Office 2010 add-ins so the status of this add-in is unknown.
• YELLOW The vendor has reported that your version of the add-in is incompatible with Office 2010, but another version of the add-in might be compatible.
• GREEN The add-in is on the list of vendor add-ins that are compatible with Office 2010.
Review OEAT data
This section covers some examples of how you can best use the data that is collected by OEAT. Each subsection includes some sample reports that you can generate, some procedural steps (when available), and some screen shots of results.
View top 10 add-ins
One method that you can use to begin your assessment is to use the currently filtered tables to select the Top 10 on the Count column. From there, you can quickly identify the 10 most common add-ins that interface with Office in your environment.
Organize results by application
Although you might want to study possible compatibility issues for each application in Office, at first you can focus on only one application. You can select to view the data from one Office application — such as Excel in the App column — and get a list of only the add-ins that interface with Excel.
View unknown add-ins
After you have filtered the list by application and by the top 10, you can again filter the list of applications that are UNKNOWN or YELLOW in the Compatibility column. By using filters again, you can also remove from the list all add-ins that are already known to be compatible with Office 2010.
Configuration management
After you have compiled a list of add-ins per application that are not specifically known to work with Office 2010, you can then order the list from most to least common and are the top 10 of concern. From this point, you can perform the following steps:
Study the version information From the items reviewed, check the version of the add-ins or applications. Do you already have the most recent version supported by the vendor? Is the application fully deployed? Can you contact the vendor to verify the latest version?
Note the last access date Determine if an add-in or application has been used in your environment recently. If it has an old access date, you can check the systems that report that particular add-in in the RAW DATA sheet to see whether it is used by current users.
Use the Load behavior column The Load behavior column lets you know if the add-in is loaded when Office runs. OEAT notes this behavior as follows:
• (0) Not loaded
• (1) Loaded at next startup only
• (2) Loaded on demand
• (3) Loaded at startup
Charts and pivot tables
There other opportunities for displaying the data that is provided by OEAT by using charts or highlighting specific information by using pivot tables. This guide is limited only to the most common and immediate reporting concerns to make immediate decisions on the assessment of the environment. For more information about Excel charts and pivot tables, see Overview of Excel charts () and Overview of pivot table reports ().
Microsoft Office Code Compatibility Inspector user's guide
The Microsoft Office Code Compatibility Inspector is a tool that you can use in Microsoft Excel 2010, Microsoft PowerPoint 2010, Microsoft Word 2010, and Microsoft Visual Studio 2008 to troubleshoot and resolve issues with your Microsoft Visual Basic for Application (VBA) Macros and add-ins. The tool scans your code for known compatibility issues, and then notifies you if it finds items in the code from the object model that have changed in some way or have been removed. This article describes how to use the tool to inspect VBA code that you created in previous versions of Microsoft Office and also how to use the tool to help you to make any Windows Application Programming Interface (API) calls in your code compatible with the 64-bit edition of Microsoft Office 2010.
In this article:
• About the Inspector
• Installation
• Inspecting VBA code
• Inspecting Visual Studio code
• Using the Inspector
• Additional resources
About the Inspector
The Microsoft Office Code Compatibility Inspector for is designed to help an enterprise or small business update Visual Basic for Applications (VBA) and Visual Studio Tools for Office code so that it is compatible with Office 2010. The Inspector does not correct code; it inspects code, and then comments specific lines of code that reference items in the object model that have changed in some way or have been deprecated. (In VBA code, the tool also comments Declare statements for 64-bit compatibility.) You can then modify the code based on the comments, or use the links that are provided in the comments to view topics on the Web that are pertinent to a particular line of your code.
Again, it is up to you to modify the code if you determine that it needs to be modified.
The key features of the Office Code Compatibility Inspector include the following:
• It consists of four add-ins that load, one add-in per application, in Excel 2010, PowerPoint 2010, Word 2010, and Visual Studio 2008.
• It runs on a per-user or a per-document basis. For VBA, users open a document and run the tool from the Developer tab. For Visual Studio projects, the developer runs the tool from the Tools menu.
• It scans the projects in the current document or Visual Studio Solution by using a simple text search, looking for parentObject.Property combinations, and scans Declare statements for 64-bit compatibility (in VBA).
• It adds comments in the code where it finds other potential issues.
• It displays a summary and a detailed report of its findings after it completes its inspection.
You cannot use this tool to inspect code from Microsoft Outlook or Microsoft Access. However, you can use the tool to inspect Excel, PowerPoint, and Word code for interaction with the Outlook object model.
Installation
To install the Office Code Compatibility Inspector, follow these steps:
1. Download SetupOCCI.msi () to your desktop or some other location that is convenient to you, and then double-click it to start the installation.
• You can select to install only the Visual Studio add-in.
• You can select to install only the Office add-ins.
• Or, you can select to install both.
2. Follow the prompts and then click Finish to complete the installation.
Displaying the Developer tab
For each Office application in which you plan to use the tool, do the following:
1. Open Excel 2010, PowerPoint 2010, or Word 2010 if it is not already open.
2. On the File tab, click Options.
3. Click Customize Ribbon.
4. Under Choose commands from on the left side of the dialog box, select Popular Commands.
5. Under Customize the ribbon on the right side of the dialog box, select Main tabs, and then select the Developer check box.
6. Click OK.
Enable VBA project access
For each Office application in which you plan to use the tool, do the following:
1. Open Excel 2010, PowerPoint 2010, or Word 2010 if it is not already open.
2. On the File tab, click Options.
3. Click Trust Center.
4. Click Trust Center Settings.
5. Select Trust access to the VBA project object model.
Inspecting VBA code
To inspect a document for compatibility, follow these steps:
1. Open the document in Excel 2010, PowerPoint 2010, or Word 2010.
2. On the Developer tab, click Inspect VBA Code.
Figure 1. Code Compatibility Inspector options on the Developer tab
[pic]
3. In the Inspect VBA Project dialog box, select or clear the options as appropriate, and then click Inspect.
Figure 2. Inspect VBA Project dialog box
[pic]
a. Select Inspect Visual Basic for Application Projects to inspect your VBA project for items in the object model that have changed or have been removed.
b. Select Inspect Declare statements if your project will only be run on Office 2010, or your project might run on a system that is running 64-bit Office 2010.
c. Select Add comments to place comments in your code where the tool identifies potential compatibility issues. The comments that the Inspector adds look similar to the following example.
'
'
' Potentially contains ...
' AnswerWizard.ResetFileList
'
'
'
d. Select Detailed Report to create a report at the end of the inspection process. The report is a text file that looks similar to the following example.
SUMMARY:
========
Document scanned: c:\TestFile.xls
Date Scanned: Thursday, November 12, 2009
Total lines scanned: 101
Total items found: 1
Deprecated items: 0
Changed items: 1
Redesigned items: 0
Declare statements: 0
DETAILS:
========
MODULE: Module1
FUNCTION: Macro1
LINE: 19
TYPE: CHANGE
ITEM: Workbook.VBProject
URL:
CODE: For Each comp In
ActiveWorkbook.VBProject.VBComponents
4. After the Inspector completes its scan, it displays a summary report similar to the following.
Figure 2a. Code Compatibility Inspector Summary
[pic]
• Total lines scanned – Total number of VBA code lines scanned in the document.
• Total items found – Total number of problematic items that the Inspector found in the code, including Declare statements to update, changed items, deprecated items, and items affected by design changes.
• Deprecated items – Items in the code that were removed from the object model, or are no longer supported in it. If your code is dependent on a deprecated item, you must rewrite that portion of the code.
• Changed items – Items in the code that use a command whose syntax has changed. If your code uses outdated syntax, you must update the code.
• Redesigned items – Items in the code whose syntax is the same and still exists, but whose updated design might yield unexpected results against your code. For example, formatting a particular text box might have changed because of new text services, and as a result, your code might create a text box, but the layout of the text in the box might be different from previous versions.
• Declare statements – Total number of Windows API statements detected in the VBA code and then updated for 64-bit compatibility by adding the PTRSAFE keyword.
Inspecting Visual Studio code
To inspect a document for compatibility, follow these steps:
1. Open the solution that you want to inspect in Visual Studio Tools for Office.
2. On the Tools menu, click Inspect VSTO Code.
Figure 3. VSTO Tools menu
[pic]
3. In the Inspect VSTO Project dialog box, select or clear the options as appropriate, and then click Inspect.
Figure 4. Inspect VSTO Project dialog box
[pic]
a. Select Inspect Visual Studio Tools for Office Source ( and C#) to inspect your Visual Studio Tools for Office project for items in the object model that have been changed or removed.
b. Select Add comments to place comments in your code where the tool identifies potential compatibility issues. The comments that the Inspector adds look similar to the following example.
//
//
// Potentially contains removed items...
// [mso]AnswerWizard.ResetFileList
//
//
//
c. Select Detailed Report to create a report at the end of the inspection process. The report is a text file that looks similar to the following example.
SUMMARY:
========
Solution scanned: ExcelAddIn1
Date scanned: Thursday, November 12, 2009
Total lines scanned: 43
Total items found: 3
Deprecated items: 3
Changed items: 0
Redesigned items: 0
DETAILS:
========
MODULE: ThisAddIn.cs
FUNCTION: ThisAddIn_Startup
LINE: 17
TYPE: DEPRECATION
APP: mso
ITEM: AnswerWizard
URL:
CODE: xlApp.AnswerWizard.ResetFileList();
MODULE: ThisAddIn.cs
FUNCTION: ThisAddIn_Startup
LINE: 19
TYPE: DEPRECATION
APP: xls
ITEM: SmartTagRecognizers
URL:
CODE: xlApp.SmartTagRecognizers.Recognize = true;
MODULE: ThisAddIn.cs
FUNCTION: ThisAddIn_Startup
LINE: 22
TYPE: DEPRECATION
APP: xls
ITEM: SmartTags
URL:
CODE: MessageBox.Show(r.SmartTags.Count.ToString());
d. Select Backup to back up your project files before inspecting your code.
4. After the Inspector completes its scan, it displays a summary report similar to the following.
Figure 5. Code Compatibility Inspector Summary
[pic]
• Total lines scanned – Total number of Visual Basic .NET or C# code lines scanned in the document.
• Total items found – Total number of problematic items that the Inspector found in the code, including changed items, deprecated items, and items affected by design changes.
• Deprecated items – Items in the code that were removed from the object model, or are no longer supported in it. If your code is dependent on a deprecated item, you must rewrite that portion of your code.
• Changed items – Items in the code that use a command whose syntax has changed. If your code uses outdated syntax, you must update the code.
• Redesigned items – Items in the code whose syntax is the same and still exists, but whose updated design might yield unexpected results against your code. For example, formatting a particular text box might have changed because of new text services, and as a result, your code might create a text box, but the layout of the text in the box might be different from previous versions.
• Declare statements – Total number of Windows API statements detected in the VBA code and then updated for 64-bit compatibility by adding the PTRSAFE keyword.
Using the Inspector
If the Inspector finds Changed, Deprecated, or Redesigned items in your code, you must debug your code and resolve any issues. We recommend that you perform a full test pass on your code, inspecting each function. As you debug your code, check for Office Code Compatibility Inspector comments above the lines that break your code. Those comments should help you to determine the underlying problem with that particular line of code. If the problem is not immediately obvious to you, paste the URL that is in the comments into your browser to get more information.
Removing comments in VBA
To remove the comments from the code after you complete the process and verify your code for Office 2010 compatibility, click Remove Comments on the Developer tab in your Office 2010 application.
The Inspector removes all comments that it placed in your VBA project and then notifies you how many items it removed.
Figure 6. Message that specifies the number of items removed
[pic]
Removing comments in Visual Studio
To remove the comments from the code after you complete the process and verify your code for Office 2010 compatibility, click Remove VSTO Inspector Comments on the Tools menu in Visual Studio.
The Inspector removes all comments that it placed in your Visual Studio Tools for Office project and then notifies you how many items it removed.
Figure 6a. Message that specifies the number of items removed
[pic]
Additional resources
For more information, see the following resources:
• Office 2010 Tool: Office Environment Assessment Tool ()
• Office 2010 Assessment and Remediation Guide ()
• Office Environment Assessment Tool Quick Start Guide ()
• Office Environment Assessment Tool User Manual ()
• Office Migration Planning Manager (OMPM) overview for Office 2010
Office Migration Planning Manager (OMPM) overview for Office 2010
This article provides an overview of the Office Migration Planning Manager (OMPM), including a description of the contents of the OMPM download package, requirements for running OMPM, and a high level overview of using OMPM tools.
In this article:
• OMPM components
• Office Migration Planning Manager Table of Requirements
• Client system requirements
• Admin requirements
• How the File Scanner Works
• Using OMPM tools
OMPM is a collection of tools that enables you to prepare an environment for migration to Microsoft Office 2010. OMPM checks for, and reports on, file properties and contents to help you analyze the environment and determine any issues that you might experience converting from Office 97 Office 2003 file formats to file formats. Office 2010. OMPM can be a very important part of an Office migration plan. You can use the tools in OMPM to scan Office 97 through Office 2003 files for conversion issues, create reports to help you analyze the scan data, store the scan data, and convert older Office files into the Office 2010 file formats. OMPM includes the following features:
• The OMPM File Scanner (offscan.exe), a command-line tool that scans files for conversion issues and stores the results in .xml log files on each computer that it scans and, optionally, can bundle these log files into .cab files. The OMPM File Scanner performs two kinds of scans:
• A light scan that quickly identifies the Office documents on a user’s computer or network file system.
• A deep scan that you can perform on Office documents to crawl document properties that provide indicators of potential conversion issues.
• A set of utilities that you can use to import the .xml log files generated by the OMPM File Scanner into one or more Microsoft SQL Server 2000, Microsoft SQL Server 2005, or Microsoft SQL Server 2005 Express Edition databases. OMPM for Office 2010 will be updated to provide Microsoft SQL Server 2008 support.
• A Microsoft Access 2010–based reporting solution that provides different reports for your analysis and enables you to define file sets for automated processing.
• The Office File Converter (OFC), which lets you convert specific files to the Office 2010 file formats in bulk.
• The Version Extraction Tool (VET), which lets you extract multiple saved versions of a document in Office Word 2003 to individual, different version files in Office 2010.
OMPM components
The OMPM download is packaged in a self-extracting executable file, MigrationPlanningManager.exe, which you can download from 2007 Microsoft Office System Migration Guidance: Microsoft Office Migration Planning Manager (). This download is the 2007 version of OMPM, which you can use to scan for conversion issues common to both 2007 Microsoft Office system and Office 2010. A new version of OMPM will be available in 2010.
OMPM components are contained in the following redistributable subfolders:
• Scan: The folder that contains the OMPM File Scanner.
• Report: The folder that contains OMPM Reports. To export file lists from OMPM Reports, the database folder and related components must also be available.
• Database: The folder that contains scripts to provision and populate the OMPM database.
• Tools: The folder that contains tools such as the OFC and the VET.
Office Migration Planning Manager Table of Requirements
The following table provides requirements/prerequisites for client, administrator, database, and network components.
Client system requirements
The following requirements are for client computers on which the OMPM File Scanner will run.
|Operating System |System Components |
|Windows 2000 SP4 | |
|Windows Server 2003 SP1 | |
|Windows XP SP3 |DAO 3.5 or later (included in Access 2000 and later and in Windows XP and |
| |later) |
|Windows Vista SP3 |Windows Script 5.6 or later |
|Windows 7 |Visual C Runtime (msvcrt.dll) |
|Internet Explorer 5.0 or later | |
|Office File Converter (OFC) requirement for any computer |Microsoft Office Compatibility Pack |
|containing files to be converted. |() |
|Version Extraction Tool (VET) requirement for any computer on |Microsoft .NET Framework V2.0 Redistribution Package (x86) |
|which vet.exe will run. |() |
| |Kernel32.dll |
| |Msjet40.dll |
| |Crypt32.dll |
| |Ole32.dll |
| |Oleaut32.dll |
| |User32.dll |
| |Advapi.dll |
|OMPM Reports (on client computers with data for analysis) |Reports requires Access 2007 or later |
|OMPM File Scanner (Office does not have to be installed to use)|Performing deep scans requires the use of Access 2007 or later. |
|OMPM File Scanner (Scanning doc storage systems) |Web-based Distributing Authoring and Versioning IIS 6.0 |
| |()(WebDAV interface) required |
| |[pic]Warning: |
| |Only the IIS 6.0 version of WebDAV is supported. For SSL-enabled doc |
| |libraries, use Windows Vista WebDAV. Prior versions of WebDAV client are |
| |not supported. |
Administrator system requirements
|Operating system |System components |
|Requirements for OMPM database provisioning and/or data import tools | |
|on admin computer. | |
|[pic]Warning: | |
|Maintain import tools, log file share, and database on the same | |
|server for optimal performance, or keep on same subnet to reduce | |
|network traffic. | |
|Windows 2000 SP4 | |
|Windows Server 2003 SP1 | |
|Windows XP SP3 |IExpress 2.0 runs on XP |
|Windows Vista SP3 |IExpress 2.0 runs on Vista |
|Windows 7 |IExpress 2.0 runs on Win7 |
| |[pic]Warning: |
| |Create self-extracting packages using IExpress. Do not use |
| |self-installing packages. |
|OMPM Reports |Reports requires Office Access 2007 or later |
|Database components |System components |
|SQL Server 2000 |4 GB free disk space |
|SQL Server 2005 (Only English edition is supported) |4 GB free disk space |
|SQL Server 2008 (Planned) |4 GB free disk space |
|SQL Server 2005 Express Edition |2 GB free disk space |
|() | |
|[pic]Warning: | |
|Only use for maximum 10,000 scan-able files. Use Express for client | |
|applications requiring an embedded database. | |
|SQLXML 3.0 SP3 () |Enables XML support for SQL Server 2005 database. |
|Sqlcmd.exe command-line utility (bundled with SQL Server 2005 and SQL|Sqlcmd.exe must be on client computer from which SQL provisioning and|
|Server 2005 Express edition) |import tools are run. |
|Bcp.exe command-line utility (bundled with SQL Server 2005 and SQL |Bcp.exe must be on client computer from which SQL provisioning and |
|Server 2005 Express edition) |import tools are run. |
|Network |System components |
|File share required to stage XML log files collected by OMPM File |File share 1GB free space |
|Scanner. Needs read/write/create permissions. | |
How the OMPM File Scanner works
The OMPM File Scanner collects information about the computer and recursively scans the designated path for Office files. The OMPM File Scanner then records the results in an XML log file to the designated destination path.
In addition, OMPM includes the latest Access Compatibility Toolkit, which it uses automatically when you scan Access files with it (provided you have set the AccessScan setting to 1 in the offscan.ini file), and shows the results on the Access Compatibility tab of the reporting tool.
The OMPM File Scanner performs the following tasks in a single scan:
• Scans the computer for Office files within the folder structure that is defined by the SourcePath setting specified in the configuration file offscan.ini.
• Scans the computer for properties such as operating system, memory, and language ID.
• Scans for file property information such as file name, path, size, format, created date, modified date, and file owner.
• If this is a deep scan, scans for compatibility issues.
• Writes an XML log file to the destination path for each file that contains compatibility issues.
• Adds the XML log files to a series of CAB files for later transfer to a SQL Server computer.
• Logs failures to the XML log files.
[pic]Note
Using OMPM tools
The following is a high-level view of how you can use the OMPM tools in your Office migration.
1. Use the OMPM file scanner to scan computers and generate log or cab files that with scan results data. For more information, see Set up the OMPM File Scanner for Office 2010. ((Office.14).aspx)
2. Import the log or cab files into the OMPM database. For more information, see Import Office Migration Planning Manager (OMPM) log files into a database. ((Office.14).aspx)
3. Use OMPM Reports to prepare reports from the data in the OMPM database. For more information, see Analyze reports from OMPM for Office 2010. ((Office.14).aspx)
4. Use the reports to determine what actions to take in your Office migration. For example, do one or both of the following
• Use the Office file converter to convert specific files from Office 2003 or Office 2007 file formats to the Office 2010 file formats in bulk.
• Use the Version extraction tool to extract multiple saved version s of a file in Office Word 2003 or Word 2007 to different files in Office 2010.
See Also
Set up the OMPM File Scanner for Office 2010 ((Office.14).aspx)
Run the OMPM File Scanner for Office 2010 ((Office.14).aspx)
Analyze reports from OMPM for Office 2010 ((Office.14).aspx)
Import Office Migration Planning Manager (OMPM) log files into a database ((Office.14).aspx)
Plan desktop configurations for Office 2010
This section provides information and guidelines about items to consider before you deploy Microsoft Office 2010.
In this section:
|Article |Description |
|Plan for OneNote 2010 |Describes how to plan a deployment of Microsoft OneNote 2010. |
|( |
|e9825(Office.14).aspx) | |
|Plan for Outlook 2010 |Guides you through the things to consider when you deploy Microsoft |
|( 2010. |
|d2ac8(Office.14).aspx) | |
|Plan for SharePoint Workspace 2010 |Describes how to plan a deployment of Microsoft SharePoint Workspace |
| |2010. |
|Plan customizations and options for Visio 2010 |Describes some of the customizations and options that are available |
|( Microsoft Visio 2010. |
|52b92(Office.14).aspx) | |
|Plan security for Office 2010 |Describes several new security controls in Office 2010 that help you |
| |plan a robust defense against threats while maintaining information |
| |worker productivity. |
|Plan Group Policy for Office 2010 |Provides information about how to use Group Policy to configure and |
|( settings for Office 2010 applications. |
|7811e(Office.14).aspx) | |
|Plan for multilanguage deployment of Office 2010 |Discusses planning considerations for deploying Office 2010 with |
| |multiple languages. |
|Plan for virtualization |Describes what virtualization is, how you can use virtualization in |
| |your organization, and which method and type is best for your |
| |environment. |
|Plan for Remote Desktop Services (Terminal Services) |Provides information about how to plan the deployment of Office 2010 |
|( using Remote Desktop Services (Terminal Services). |
|62daf(Office.14).aspx) | |
Planning overview for Outlook 2010
A close review of the organization's messaging requirements will help you plan the optimal Microsoft Outlook 2010 deployment. This article guides you through the things to consider when you deploy Outlook 2010.
In this article:
• Determining an organization’s needs
• Choosing when and how to install Outlook
• Security and privacy considerations
• Upgrading from an earlier version of Outlook
• Additional issues to consider when planning an upgrade
• Upgrading from other mail and scheduling programs
Determining an organization’s needs
The organization's messaging environment helps shape the Outlook 2010 deployment. Factors to consider include whether you are upgrading Outlook, installing the application for the first time, planning for roaming or remote users, or choosing a combination of these and other factors.
Upgrade or initial installation
If you are upgrading to Outlook 2010 from an earlier version of Microsoft Outlook, consider whether you will migrate previous settings, modify user profiles, and use new customization options. The Office Customization Tool (OCT) enables you to migrate users' current settings and make other customizations, such as define new Microsoft Exchange servers or customize new features. User settings are migrated automatically by default, except for security settings.
If you are deploying Outlook on client computers for the first time, each user needs an Outlook profile to store information about e-mail messaging server connections and other important Outlook settings. You use the OCT or deploy an Outlook Profile (.prf) file to define profile settings for users.
Migrating data
If the organization uses a different mail client, you might have to migrate data from those clients to Outlook 2010. The importers that are provided in Outlook (for example, for Eudora Light) might be helpful. Importers cannot be configured to run automatically. You use importers to migrate data for individual users.
Remote and roaming users
You can customize Outlook to optimize the experience for remote and roaming users, and to set up Outlook for multiple users on the same computer.
You might want to configure features such as Outlook Anywhere (known as RPC over HTTP in earlier versions of Outlook) and Cached Exchange Mode for remote users. These features enhance the user experience when Outlook is used over slower or less reliable connections. By using Outlook Anywhere, you can configure connections that enable users to connect more securely from the Internet to Exchange servers in your organization without using a virtual private network (VPN) connection. Cached Exchange Mode is an Outlook feature that was introduced with Office Outlook 2003 that creates a local copy of users' mailboxes. Cached Exchange Mode is recommended for all configurations, but especially benefits remote users. The feature enables users to have more reliable access to their Outlook data, whether or not they are connected to a network.
When multiple users share the same computer, use Microsoft Windows logon features on the computer's operating system to manage user logon verification. Unless you deploy application virtualization, users must use the same version of Outlook because only one version of Outlook can be installed on the same computer. To learn more about how to set up multiple Outlook users on the same computer, see Using Outlook on a computer you share with other people ().
Multilingual requirements
Microsoft Office 2010 provides broad support to deploy in international or multilingual environments. As with the 2007 Microsoft Office system, the Office 2010 product consists of the language-neutral core package plus one or more language-specific packages. In addition to the proofing tools included in each language version, you can download and deploy proofing tools for other languages to help multilingual groups work with and edit files in many languages.
Outlook 2010 supports Unicode throughout the product to help multilingual organizations seamlessly exchange messages and other information in a multilingual environment.
Client and messaging server platforms
Some features of Outlook 2010 (for example, Cached Exchange Mode) require Microsoft Exchange Server as a messaging platform. Although Outlook 2010 works well with earlier versions of Exchange, some features of Outlook 2010 require specific versions of Exchange. Because of this and other improved integration with Exchange throughout Outlook 2010, we recommend that you combine Outlook 2010 with the latest version of Exchange.
Deployment customization decisions for Outlook 2010 depend on which version of Exchange Server you use. If you currently use Exchange Server as your messaging server and you have not upgraded to Exchange 2003 or a later version, consider coordinating the Exchange Server upgrade with the deployment timing for Outlook 2010. Exchange Server 2003 is the earliest version of Exchange Server that can be used with Outlook 2010.
Choosing when and how to install Outlook
You have options for when and how you install Outlook 2010. For example, consider whether it would be best for the organization to do the following:
• Install or upgrade Outlook for different groups of users in stages, or at the same time.
• Install Outlook as a stand-alone application.
• Install Outlook before, during, or after Office 2010 installation.
Each organization has a different environment and might make different choices about timing Outlook 2010 upgrades. For example, you might have a messaging group that is responsible for upgrading Outlook and a separate group that plans deployment for other Microsoft Office applications. In this case, it might be easier to upgrade Outlook separately from the rest of Office, instead of to attempt to coordinate deployment between the two groups.
Note that Outlook 2010 cannot coexist with previous versions of Outlook on the same computer. If you have to use previous versions, do not install Outlook 2010 or deploy Outlook 2010 with application virtualization.
Customizing Outlook settings and profiles
You can customize an Outlook installation to handle Outlook user settings and profiles in two ways:
• Specify Outlook user settings in the OCT.
• Specify options for managing new and existing Outlook profiles in the OCT or use an Outlook Profile file (.prf).
For example, you can enable Outlook users to migrate their current profiles and settings while default profiles and settings are defined for new Outlook users. You can also modify existing profiles and establish new default profiles for new Outlook users. If you deploy Outlook 2010 with Microsoft Exchange Server 2010, you can add more than one Exchange account for a profile by using the OCT or .prf file.
When you use the OCT to customize Outlook, you save choices and other installation preferences in the customization file that is applied during Setup. Later, you update settings and profile information by opening the file in the OCT and saving a new copy of the file.
For more information about how to configure Outlook profiles, see Office Customization Tool in Office 2010.
Configuring subscriptions and other sharing features
As with Office Outlook 2007, Outlook 2010 includes features that let you easily subscribe to new sources of content and share the features with users inside and outside your organization. Content sources include Microsoft SharePoint Foundation 2010 and SharePoint Foundation 2010 contacts, tasks, and calendars, together with local and Internet-based calendars (iCals).
Really Simple Syndication (RSS) is another sharing feature that enables users to subscribe to internal or Internet-based sources of syndicated content (.xml files) to avoid having to check a site for new information. You can deploy specific RSS feeds or calendar subscriptions to users, configure settings to manage how users can share these subscriptions or content, specify how often the servers update users' copies of the data, and more.
Using Outlook with Terminal Services
Terminal Services in Windows Server enables you to install a single volume licensed copy of Outlook 2010 on a Terminal Services computer. Instead of having Outlook run on local computers, multiple users connect to the server and run Outlook from that server.
To achieve optimal results when you use Outlook with Terminal Services, pay attention to how you customize your Outlook configuration. For example, in Outlook 2010 you can configure Cached Exchange Mode with Terminal Services. However, you will have to provide sufficient disk space to accommodate each user’s mailbox on the Terminal Services server computer. Note that Outlook might be part of an environment that includes other applications provided on the same Terminal Services computer.
Collaboration Data Objects dependencies
Collaboration Data Objects (CDO) is not supported in Outlook 2010. Although some solutions that depend on CDO 1.2.1 might continue to run, CDO 1.2.1 is not designed for a multiple Exchange account environment and unexpected results can occur. For Outlook solutions, use the Outlook object model instead of CDO 1.2.1.
AutoArchive
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. Outlook 2010 AutoArchive can manage this process automatically for users. However, we recommend that you use the Personal Archive feature in Microsoft Exchange Server 2010 Messaging Records Management (MRM) because it eliminates the need for Personal Folder files (.pst). By using Personal Archive in Exchange Server 2010, the e-mail archive folders are stored online so that users can access the archived files by using Microsoft Outlook Web App or from a secondary computer by using Outlook 2010. By using either of these client applications, users can view an archive mailbox and move or copy messages between their primary mailboxes and the archive. If you plan to deploy Outlook 2010 with Exchange Server 2010, consider using the Exchange Server 2010 Personal Archive feature instead of Outlook 2010 AutoArchive. For more information, see Understanding Personal Archive: Exchange 2010 Help ().
If you choose to use the AutoArchive feature in Outlook 2010, you can configure the settings to customize Outlook 2010 AutoArchive by using the Outlook Group Policy template (Outlk14.adm). Or you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings.
Retention policies
Retention policy settings can help users follow retention policy guidelines that your organization establishes for document retention. With Outlook 2010, you cannot deploy AutoArchive-based retention settings through Outlook 2010 by using Group Policy. If you need to deploy retention policies, explore the Messaging Records Management (MRM) features in Exchange Server 2010. For more information, see Messaging Records Management: Exchange 2010 Help ().
Security and privacy considerations
Outlook includes many security and privacy features.
The Trust Center for Office
The Trust Center, introduced with the 2007 Office system, provides a central location for security and privacy options. The Very High, High, Medium, and Low security levels that were used in earlier versions of Office have been replaced with a more streamlined security system.
Limiting viruses and junk e-mail messages for users
Outlook 2010 includes features that are designed to help minimize the spread of viruses and to help users avoid junk e-mail.
As in Office Outlook 2007, in Outlook 2010 you can configure virus-prevention and other security settings in Group Policy to support the needs of an organization. You can also use the Outlook Security Template to configure settings, as in earlier releases of Outlook. By using either configuration method, you can, for example, modify the list of file types that are blocked in e-mail messages.
The Object Model (OM) Guard that helps prevent viruses from using the Outlook Address Book (OAB) to spread is updated. Outlook checks for up-to-date antivirus software to help determine when to display OAB access warnings and other Outlook security warnings.
Outlook 2010 has several features to help users reduce receipt of junk e-mail messages. Outlook 2010 includes a Junk E-mail Filter for users that replaces the rules used in previous versions of Outlook to filter mail. Messages caught by the filter are moved to the Junk E-mail folder, where they can be viewed or deleted later. Outlook 2010 includes a Postmarking feature that was introduced with Office Outlook 2007 that can help the Junk E-mail filter determine valid e-mail messages.
Junk e-mail senders can include a Web beacon in HTML e-mail messages that includes external content, such as graphic images. When users open or view the e-mail, the Web beacons verify that their e-mail addresses are valid. This increases the probability that they will receive more junk e-mail messages. Outlook 2010 reduces the probability that users will become targets for future junk e-mail by blocking automatic picture downloads from external servers by default.
Outlook 2010 helps protect against issues created by phishing e-mail messages and deceptive domain names. By default, Outlook screens phishing e-mail messages — e-mail that seems to be legitimate but is designed to capture personal information, such as a user's bank account number and password. Outlook also helps prevent the receipt of e-mail messages from deceptive users by warning about suspicious domain names in e-mail addresses. Outlook 2010 supports internationalized domain names (IDNs) in e-mail addresses. IDNs allow people to register and use domain names in their native languages instead of online English. IDN support allows phishers to send homograph attacks, a situation in which a look-alike domain name is created using alphabet characters from different languages, not just English, with the intention of deceiving users into thinking they are visiting a legitimate Web site.
For more information about planning for security and privacy in Outlook 2010, see Plan for security and protection in Outlook 2010.
Configuring cryptographic features
Outlook provides cryptographic features for sending and receiving security-enhanced e-mail messages over the Internet or local intranet. You can customize features in an Outlook 2010 deployment to set cryptographic options that are appropriate for your organization.
You can also implement additional features to help enhance security in e-mail messaging. For example, you can provide security labels that match your organization's security policy. An Internal Use Only label might be implemented as a security label to apply to e-mail messages that are not to be sent or forwarded outside your company.
Restricting permission on e-mail messages
Information Rights Management (IRM) helps users prevent sensitive e-mail messages and other 2007 Office system content, such as documents and worksheets, from being forwarded, edited, or copied by unauthorized people. In Outlook 2010, users can use IRM to mark e-mail messages with Do not forward, which automatically restricts permission for recipients to forward, print, or copy the message. In addition, you can define customized Office-wide IRM permission policies for your organization's needs and can deploy the new permission policies for users to use with e-mail messages or other Office documents.
Outlook 2010 and e-mail protocols and servers
Outlook 2010 can be used with a wide variety of e-mail servers and services. The primary e-mail servers and services supported by Outlook include the following:
• Simple Mail Transfer Protocol (SMTP)
• Post Office Protocol version 3 (POP3)
• Internet Mail Access Protocol version 4 (IMAP4)
• Messaging Application Programming Interface (MAPI) for Exchange Server (version 2003 and later)
• Other messaging and information sources, including Hewlett-Packard OpenMail. Use of these additional service providers is made possible by the way in which Outlook 2010 uses the MAPI extensibility interface.
HTTP is supported with the installation of the Outlook Connector.
Users can use Outlook 2010 without an e-mail server in order to use the Contacts, Tasks, and Calendar features in a stand-alone configuration.
Upgrading from an earlier version of Outlook
You can install Outlook 2010 over any previous installation of Outlook. As in other Office 2010 applications, user settings stored in the registry are migrated. If a MAPI profile already exists on a user's computer, you typically can configure a deployment to continue to use the profile. However, if you are upgrading from an Internet Mail Only installation of Outlook 2000 or earlier, you might have to re-create user profiles.
Outlook 2010 cannot coexist with previous versions of Outlook on the same computer. If you determine that users need a previous version, do not install Outlook 2010 or deploy Outlook 2010 with application virtualization.
When you upgrade users from an earlier version of Outlook, you must make choices about configuring user profiles, consider Cached Exchange Mode issues, and be aware of fax and forms changes.
For an overview of feature changes and migration considerations, see Changes in Outlook 2010.
Upgrading with Cached Exchange Mode enabled
The process of upgrading users to Outlook 2010 with Cached Exchange Mode already enabled in Office Outlook 2003 or Office Outlook 2007 is straightforward. If you do not change Cached Exchange Mode settings, the same settings are kept for Outlook 2010. There is no change to the .ost or OAB file format, and you do not need to re-create these files during an upgrade.
However, if ANSI Outlook data files (.ost) are in the organization’s environment, you might have to take additional steps when you migrate files to Outlook 2010. Users with non-Unicode (ANSI) formatted data files (.ost) and large Exchange mailboxes can experience errors when Outlook attempts to synchronize their mailboxes to their .ost files. We recommend that you upgrade users’ .ost files to the Unicode format because Outlook Unicode files do not have the 2-gigabyte (GB) size limit of Outlook ANSI files. Unicode is the default file format for Outlook 2010. For information about how to force an upgrade of an existing non-Unicode (ANSI) formatted .ost file to Unicode format, see the section “To force upgrade of non-Unicode ANSI format .ost files to Unicode” in the article Configure Cached Exchange Mode in Outlook 2010.
For additional Cached Exchange Mode planning considerations, see Plan a Cached Exchange Mode deployment in Outlook 2010.
Additional issues to consider when planning an upgrade
To prepare for an upgrade, you must decide on the following additional issues:
• Should you upgrade to Exchange Server 2010 to take advantage of new features such as integrated e-mail archive, centralized rights management, support for multiple Exchange accounts, MailTips, Voice Mail Preview and Protected Voice Mail? For more information about Exchange Server 2010, see Microsoft Exchange 2010 ().
• Should you make changes to Outlook user profiles as part of your upgrade? For example, you might define a new Exchange server or enable new features of Outlook 2010. For more information about customizing Outlook profiles, see Office Customization Tool in Office 2010.
• How should you create and store a backup of your existing installation? Before you upgrade to any new release, we recommend that you back up existing data. For more information about backing up Outlook files, see Back up Outlook data with the Microsoft Outlook Personal Folders Backup tool ().
• How will users learn about the new interface and features of Office 2010? For more information, see ().
• Will any discontinued features or new or changed functionality affect when and how you upgrade? For a list of changes from earlier versions of Outlook, see Changes in Outlook 2010.
Upgrading from other mail and scheduling programs
You can upgrade to Outlook 2010 from other e-mail and scheduling programs. The process can be simplified with the use of the import feature in Outlook.
The following table lists migration paths supported by Outlook 2010.
|Software program |Version |
|Outlook Express |4. x, 5. x, 6. x |
|Eudora Pro, Eudora Light |2. x, 3. x, 4. x, 5. x, 6. x, 7. x |
[pic]Note:
You cannot import Microsoft Mail files to Outlook 2010, and you cannot share information between Outlook 2010 and Schedule Plus.
See Also
Office Customization Tool in Office 2010
Changes in Outlook 2010
Plan a Cached Exchange Mode deployment in Outlook 2010
Determine when to install Outlook 2010
You can install Microsoft Outlook 2010 before, during, or after an installation of other applications in Microsoft Office 2010. You can also deploy Outlook 2010 to different groups of users at different times.
Note that installing Outlook 2010 without Microsoft Word 2010 limits Outlook 2010 functionality in the following ways: 1) The Outlook 2010 e-mail editor has fewer features, and 2) Internet Fax functionality is not available.
This article describes the requirements, advantages, and disadvantages of each installation strategy.
In this article:
• Installing Outlook with Office
• Installing Outlook before Office
• Installing Outlook after Office
• Staging an Outlook deployment
Installing Outlook with Office
You can install Outlook 2010 as part of an overall upgrade to Office 2010. Outlook 2010 is included in most editions of the Microsoft Office system.
Install Outlook 2010 with Office 2010 to eliminate the additional steps that you must follow to create separate application deployments.
Installing Outlook before Office
You might install Outlook 2010 in the following scenarios before you deploy other applications in Office 2010:
• To test custom solutions that rely on previous versions of Office applications (such as Microsoft Office Word 2007 or Microsoft Office Excel 2007) before you install the current version.
• When your messaging support group has the resources to install Outlook 2010 now, but the desktop applications support group must install the rest of Office later. Note that Outlook 2010 cannot coexist with previous versions of Microsoft Outlook. If users or tools require a previous version, do not install Outlook 2010 until your environment can support Outlook 2010 or deploy Outlook 2010 with application virtualization.
To install Outlook 2010 before you install Office 2010, do the following:
1. Customize Office Setup to install only Outlook 2010 from a network installation point.
2. Use the Office Customization Tool (OCT) to create or update a Setup customization file that installs Office 2010 from the same network installation point.
For details about how to install Office 2010 applications in stages, see Stage deployment of applications in the 2007 Office system ().
Advantages of installing Outlook before Office
If you deploy Outlook 2010 quickly, users can start to use new features without waiting for testing or technical support to become available for a complete upgrade.
Disadvantages of installing Outlook before Office
Installing Outlook 2010 before you install the rest of Office 2010 has several disadvantages:
• When you deploy the other Office 2010 applications later, you must customize the installation process to preserve your original Outlook 2010 settings.
• The Outlook 2010 editor has reduced functionality unless Word 2010 is also installed.
• Attachment Preview in Outlook 2010 does not work for Microsoft Office 2003 file types or earlier.
• When you use the same network installation point for Outlook 2010 and Office 2010, you must take additional steps to modify the installation options.
Installing Outlook after Office
You can wait to install Outlook 2010 until after you have installed the Office 2010. If any of the following scenarios applies to your organization, you might consider delaying your deployment of Outlook 2010:
• You plan to coordinate your Outlook 2010 deployment with a future upgrade of Microsoft Exchange Server.
• You want to convert IBM Lotus Notes to a Exchange Server solution before you upgrade to Outlook 2010.
• The desktop support group has the resources to upgrade to the Office 2010 now, but the messaging support group must wait to deploy Outlook 2010.
To install Outlook 2010 after you install Office 2010, do the following:
1. Customize Office Setup to install only Office 2010 without Outlook 2010 from a network installation point.
2. Use the OCT to create or update a Setup customization file that installs Outlook 2010 from the same network installation point.
For details about how to install Office 2010 applications in stages, see Stage deployment of applications in the 2007 Office system ().
Advantages of installing Outlook after Office
In many organizations, it makes sense to coordinate an Outlook 2010 deployment with an upgrade of an e-mail server, instead of with an upgrade of other desktop applications. For example, if you plan to upgrade to a new version of Exchange Server, you might plan an Outlook 2010 upgrade to follow immediately afterward — independently from an upgrade of other Office 2010 applications — to take advantage of features that work together between the e-mail server and client.
Disadvantages of installing Outlook after Office
When you install Office without Outlook 2010, you must use the OCT to customize Setup. This ensures that previous versions of Outlook are not removed from users' computers.
Regardless of when or how you install Outlook 2010 separately from Office 2010, you must perform additional steps to manage customizations to the installation process.
Staging an Outlook deployment
Some groups in an organization might be ready to immediately upgrade to Outlook 2010, but other groups might need more time. The following situations might warrant a staged deployment of Outlook 2010:
• The usual policy is to stage upgrades to help ensure a smooth rollout of new software throughout the organization.
• You have remote systems support groups (for example, in regional sales offices) that require autonomy in scheduling upgrades for their areas.
• Some groups want to wait until after a project deadline before they make changes to their local computers.
• You have limited resources for staging and upgrading systems throughout an organization.
Advantages of staging a deployment
Staging your Outlook 2010 deployment gives you more flexibility in managing your upgrading resources. In addition, pilot users immediately become familiar with the new features and productivity improvements of Outlook 2010.
In most circumstances, users encounter no significant technical problems when they work with different versions of Outlook. Outlook 2010 users can communicate seamlessly with users of Office Outlook 2007 and Office Outlook 2003. However, if users have delegate access in Outlook, the person who grants Delegate permissions and the delegate have to use the same version of Outlook.
Disadvantages of staging a deployment
You must consider the logistics of scheduling and managing a staged deployment. An organization might require additional resources to support users on different versions of the same product; for example, it might need additional training for Help desk staff.
For details about how to install Office 2010 applications in stages, see Stage deployment of applications in the 2007 Office system ().
See Also
Planning overview for Outlook 2010
Stage deployment of applications in the 2007 Office system ()
Plan a Cached Exchange Mode deployment in Outlook 2010
When Microsoft Outlook 2010 is configured for Cached Exchange Mode, the user can have a better online and offline experience because a copy of the user's mailbox is stored on the local computer.
When an Outlook 2010 account is configured to use Cached Exchange Mode, Outlook 2010 works from a local copy of a user's Microsoft Exchange mailbox stored in an Offline Folder file (.ost file) on the user's computer, together with the Offline Address Book (OAB). The cached mailbox and OAB are updated periodically from the Microsoft Exchange Server computer. This article contains information to consider when you plan a deployment of Outlook 2010.
In this article:
• How Cached Exchange Mode can help improve the Outlook user experience
• Outlook features that can reduce the effectiveness of Cached Exchange Mode
• Synchronization, disk space, and performance considerations
• Managing Outlook behavior for perceived slow connections
• Options for staging a Cached Exchange Mode deployment
• Upgrading current Cached Exchange Mode users to Outlook 2010
• Deploying Cached Exchange Mode to users who already have .ost files
• Using Group Policy to enforce Cached Exchange Mode settings
• Additional resources
How Cached Exchange Mode can help improve the Outlook user experience
Use of Cached Exchange Mode provides the following key benefits:
• Shields the user from network and server connection issues
• Facilitates switching from online to offline for mobile users
By caching the user's mailbox and the OAB locally, Outlook no longer depends on continuous network connectivity for access to user information. While connected, Outlook continuously updates users’ mailboxes so that the mailboxes are kept up to date. If a user disconnects from the network — for example, by removing a portable computer, such as a laptop, from a docking station — the latest information is automatically available offline.
In addition to using local copies of mailboxes to improve the user experience, Cached Exchange Mode optimizes the type and amount of data sent over a connection with the server. For example, if the On slow connections, download only headers setting is configured in the Office Customization Tool, Outlook changes the type and amount of data sent over the connection.
[pic]Note:
Outlook checks the network adapter speed on the user's computer to determine a user's connection speed, as supplied by the operating system. Reported network adapter speeds of 128 kilobytes (KB) or lower are defined as slow connections. Under some circumstances, the network adapter speed might not accurately reflect data throughput for users. For more information about adjusting the behavior of Outlook in these scenarios, see the section Managing Outlook behavior for perceived slow connections later in this article.
Outlook can adapt to changing connection environments by offering different levels of optimization, such as disconnecting from a corporate local area network (LAN), going offline, and then re-establishing a connection to the server over a slower, dial-up connection. As the Exchange Server connection type changes — for example, to LAN, wireless, cellular, or offline — transitions are seamless and do not require changing settings or restarting Outlook.
For example, a user might have a portable computer at work with a network cable connection to a corporate LAN. In this scenario, the user has access to headers and full items, including attachments. The user also has quick access and updates to the computer that runs Exchange Server. If a user disconnects the portable computers from the LAN, Outlook switches to Trying to connect mode. The user can continue to work uninterruptedly with the data in Outlook. If a user has wireless access, Outlook can re-establish a connection to the server and then switch back to Connected mode.
If the user later connects to the Exchange Server computer over a dial-up connection, Outlook recognizes that the connection is slow and automatically optimizes for that connection by downloading only headers and by not updating the OAB. In addition, Outlook 2010 and Office Outlook 2007 include optimizations to reduce the amount of data that is sent over the connection. The user does not need to change settings or restart Outlook in this scenario.
Outlook 2010 also includes the Need Password mode. A Need Password message is displayed when Outlook is in a disconnected state and requires user credentials to connect; for example, when a user clicks Cancel in a credentials authentication dialog box. When Outlook is disconnected but is not offline, a user-initiated action (such as clicking Send/Receive or the Type Password button on the ribbon) causes Outlook to prompt again for the password and to display a Trying to connect message until the user can successfully authenticate and connect.
Outlook features that can reduce the effectiveness of Cached Exchange Mode
Some Outlook features reduce the effectiveness of Cached Exchange Mode because they require network access or bypass Cached Exchange Mode functionality. The primary benefit of using Cached Exchange Mode is that the user is shielded from network and server connection issues. Features that rely on network access can cause delays in Outlook responsiveness that users would not otherwise experience when they use Cached Exchange Mode.
The following features might rely on network access and can cause delays in Outlook unless users have fast connections to Exchange Server data:
• Delegate access, when folders are not cached locally (local cache is the default)
• Opening another user's calendar or folder that is not cached locally (local cache is the default)
• Using a public folder that is not cached
See Managing Outlook folder sharing in Synchronization, disk space, and performance considerations later in this article.
We recommend that you disable or do not implement the following features, or combination of features, if you deploy Cached Exchange Mode:
• The toast alert feature with digital signatures on e-mail messages Outlook must check a server to verify a digital signature. By default, when new messages arrive in a user's Inbox, Outlook displays a toast message that contains a part of an e-mail message. If the user clicks the toast message to open a signed e-mail message, Outlook uses network access to check for a valid signature on the message.
• Multiple Address Book containers The Address Book typically contains the global address list (GAL) and user Contacts folders. Some organizations configure subsets of the GAL, which display in the Address Book. These subset address books can also be included in the list that defines the search order for address books. If subset address books are included in the search order list, Outlook might need to access the network to check these address books every time that a name is resolved in an e-mail message that a user is composing.
• Custom properties on the General tab in Properties dialog box for users The Properties dialog box appears when you double-click a user name (for example, on the To line of an e-mail message). This dialog box can be configured to include custom properties unique to an organization, such as a user's cost center. However, if you add properties to this dialog box, we recommend that you not add them to the General tab. Outlook must make a remote procedure call (RPC) to the server to retrieve custom properties. Because the General tab shows by default when the Properties dialog box is accessed, an RPC would be performed every time that the user accessed the Properties dialog box. As a result, a user who runs Outlook in Cached Exchange Mode might experience noticeable delays when he or she accesses this dialog box. To help avoid such delays, you create a new tab on the Properties dialog box for custom properties, or include custom properties on the Phone/Notes tab.
Certain Outlook add-ins can affect Cached Exchange Mode. Some add-ins can access Outlook data by using the object model to bypass the expected functionality of the Download only headers and On slow connections, download only headers settings in Cached Exchange Mode. For example, full Outlook items, not only headers, download if you use Microsoft ActiveSync technology to synchronize a hand-held computer, even over a slow connection. In addition, the update process is slower than if you download the items in Outlook, because one-time-only applications use a less-efficient kind of synchronization.
Synchronization, disk space, and performance considerations
Cached Exchange Mode uses a local copy of the user’s Exchange mailbox, and in some cases, you can improve the performance of cached mode for your whole organization or for a group of users; for example, users who work remotely.
Manual synchronization of Exchange accounts no longer necessary
Cached Exchange Mode works independently of existing Outlook Send/Receive actions to synchronize users' .ost and OAB files with Exchange Server data. Send/Receive settings update users' Outlook data in the same way the settings did in earlier versions of Outlook.
Users who have Send/Receive-enabled Exchange accounts and who synchronize Outlook data by pressing F9 or by clicking Send/Receive might not realize that manual synchronization is no longer necessary. In fact, network traffic and server usage can be adversely affected if users repeatedly execute Send/Receive requests to Exchange Server. To minimize the effects, inform users that manual Send/Receive actions are unnecessary in Cached Exchange Mode. This might be especially helpful for remote users who typically used Outlook in offline mode with earlier Outlook versions and used Send/Receive to synchronize the data or just before they disconnected from the network. This kind of data synchronization now occurs automatically in Cached Exchange Mode.
Another way to manage the issue is to disable the Send/Receive option for users. However, we do not recommend this because it can create problems for some users; for example, when you upgrade current Outlook users with POP accounts and existing customized Send/Receive groups to Outlook 2010. In this situation, if you disable the Send/Receive option, users cannot download POP e-mail messages or HTTP e-mail messages by using the Outlook Connector.
Offline Address Book access advantages
Cached Exchange Mode enables Outlook to access the local Offline Address Book (OAB) for user information, instead of requesting the data from Exchange Server. Local access to user data greatly reduces the need for Outlook to make RPCs to the Exchange Server computer, and lessens much of the network access that is required for users in Exchange online mode or in previous versions of Outlook.
When users have a current OAB installed on their computers, only incremental updates to the OAB are needed to help prevent unnecessary server calls. Outlook in Cached Exchange Mode synchronizes the user's OAB with updates from the Exchange Server copy of the OAB every 24 hours. You can help control how often users download OAB updates by limiting how often you update the Exchange Server copy of the OAB. If there is no new data to synchronize when Outlook checks, the user's OAB is not updated.
[pic]Note:
We recommend that users use the default Unicode OAB. The ANSI OAB files do not include some properties that are in the Unicode OAB files. Outlook must make server calls to retrieve required user properties that are not available in the local OAB, which can result in significant network access time when users do not have a Full Details OAB in Unicode format.
Offline folder (.ost file) recommendations
When you deploy Cached Exchange Mode for Outlook, be aware that users' local .ost files can increase 50 percent to 80 percent over the size of the mailbox reported in Exchange Server. The format Outlook uses to store data locally for Cached Exchange Mode is less space-efficient than the server data file format. This results in the use of more disk space when mailboxes are downloaded to provide a local copy for Cached Exchange Mode.
When Cached Exchange Mode first creates a local copy of a user's mailbox, the user's current .ost file, if one exists, is updated. If users currently have non-Unicode ANSI-formatted .ost files, we recommend that you upgrade their .ost files to Unicode. Non-Unicode (ANSI) Outlook files have a limit of 2 gigabytes (GB) of data storage. The maximum size for Unicode .ost files is configurable, with the default being 50 GB of data storage.
Also, make sure that users' .ost files are located in a folder that has sufficient disk space to accommodate users' mailboxes. For example, if users' hard drives are partitioned to use a smaller drive for system programs (the system drive is the default location for the folder that contains the .ost file), specify a folder on another drive that has more disk space as the location of users' .ost files.
• For more information about how to deploy .ost files in a location other than the default location, see "Configure a default .ost location by using Group Policy" in Configure Cached Exchange Mode in Outlook 2010.
• To determine whether your users’ .ost files are in ANSI or Unicode format, see How to determine the mode that Outlook 2007 or Outlook 2003 is using for offline folder files ().
• For information about how to force an upgrade of an existing non-Unicode (ANSI) formatted .ost file to Unicode format, see “Force upgrade of non-Unicode ANSI format .ost files to Unicode” in Configure Cached Exchange Mode in Outlook 2010.
• For more information about how to configure the Unicode .ost file size, see How to configure the size limit for both (.pst) and (.ost) files in Outlook 2007 and in Outlook 2003 ().
Managing performance issues
Most users will find that Cached Exchange Mode performs faster than online mode. However, many factors influence a user's perception of Cached Exchange Mode performance, including hard disk size and speed, CPU speed, .ost file size, and the expected level of performance.
For troubleshooting tips about diagnosing and addressing performance issues in Outlook, see the Microsoft Knowledge Base article How to troubleshoot performance issues in Outlook 2007 () and Performance tips for deploying Outlook 2007 ().
Managing Outlook folder sharing
In Outlook 2010 and Office Outlook 2007, by default, shared non-mail folders that users access in other mailboxes are downloaded and cached in the user's local .ost file when Cached Exchange Mode is enabled. Only shared Mail folders are not cached. For example, if a coworker shares a calendar with another user and the user opens it, Outlook 2010 starts caching the folder locally so that the user has offline access to the folder and is insulated from network issues. However, if a manager delegates access to his or her Inbox to a team member, accessing the folder is an online task and can cause response delays.
Cached non-mail folders, such as Calendar, enable offline access and can provide a much more reliable experience on slow or unreliable networks. But be aware that they take a little more time to populate initially; more data is synchronized, so the local .ost file size increases; and in scenarios with slow connections or where the user is offline, the non-mail folder is not current until the latest changes are synchronized and downloaded.
You can configure this option (Download shared non-mail folders) in the Office Customization Tool (OCT) when you customize your Cached Exchange Mode deployment.
You can also enable shared mail folders for users if it is necessary. However, the cautionary notes earlier in this article regarding the sharing of non-mail folders also apply to the sharing of mail folders. Local .ost file size increases for users who have shared folders enabled. Instructions on how to enable this setting are included in the article Configure Cached Exchange Mode in Outlook 2010.
For more information, see You cannot cache shared mail folders in Outlook 2007 ().
Public Folder Favorites considerations
Cached Exchange Mode can be configured to download and synchronize the public folders included in users' Favorites folders for Outlook Public Folders. By default, Public Folder Favorites are not synchronized. However, you might want to enable this option if your organization uses public folders extensively. You can configure an option to download Public Folder Favorites in the .ost when you customize your Cached Exchange Mode deployment.
If users' Public Folders Favorites folders include large public folders, their .ost files can also become large. This can adversely affect Outlook performance in Cached Exchange Mode. Before you configure Cached Exchange Mode to enable this option, ensure that users are selective about the public folders that are included in their Public Folder Favorites. Also, ensure that users' .ost files are large enough, and are in folders that have sufficient disk space, to accommodate the additional storage requirements for the public folder downloads.
Managing Outlook behavior for perceived slow connections
Outlook is configured to determine a user's connection speed by checking the network adapter speed on the user's computer, as supplied by the operating system. If the reported network adapter speed is 128 KB or lower, the connection is defined as a slow connection.
When a slow connection to an Exchange Server computer is detected, Outlook helps users have a better experience if they reduce the amount of less-critical information that is synchronized with the Exchange Server computer. Outlook makes the following changes to synchronization behavior for slow connections:
• Switches to downloading only headers
• Does not download the Offline Address Book or OAB updates
• Downloads the body of an item and associated attachments only when it is requested by the user
Outlook continues to synchronize the Outlook data with mobile devices, and some client-side rules might run.
[pic]Note:
We recommend that you do not synchronize mobile devices with the Cached Exchange Download only headers setting enabled. When you synchronize a mobile device — for example, by using ActiveSync — full items are downloaded in Outlook, and the synchronization process is less efficient than with regular Outlook synchronization to users' computers.
The Download only headers setting for synchronization is designed for Outlook users who have dial-up connections or cellular wireless connections, to minimize network traffic when there is a slow or expensive connection.
Under some circumstances, the network adapter speed might not accurately reflect data throughput for users. For example, if a user's computer is connected to a local area network (LAN) for fast access to local file servers, the network adapter speed is reported as fast because the user is connected to a LAN. However, the user's access to other locations on an organization's network, including the Exchange Server computer, might use a slow link, such as an ISDN connection. For such a scenario, where users' actual data throughput is slow although their network adapters report a fast connection, you might want to configure an option to change or lock down the behavior of Outlook; for example, by disabling automatic switching to downloading only headers by using the Group Policy Object Editor option, Disallow On Slow Connections Only Download Headers. Similarly, there might be connections that Outlook has determined are slow but which provide high data throughput to users. In this case, you might also disable automatic switching to downloading only headers .
You can configure the On slow connections, download only headers option in the OCT, or lock down the option by using Group Policy Object Editor to set Disallow On Slow Connections Only Download Headers. For more information about how to customize this setting, see Configure Cached Exchange Mode in Outlook 2010.
Options for staging a Cached Exchange Mode deployment
Stage the rollout over time if you plan to upgrade a large group of users from a deployment of Outlook without Cached Exchange Mode to Outlook 2010 with Cached Exchange Mode enabled. Outlook without Cached Exchanged Mode is the case for Outlook 2002 or earlier, or Office Outlook 2003, or for Office Outlook 2007 without Cached Exchange Mode installed. A staged rollout over time helps your organization's Exchange Server computers manage the requirements of creating or updating users' .ost files.
[pic]Caution:
If most user accounts are updated to use Cached Exchange Mode at the same time and then start Outlook at the same time (for example, on a Monday morning after a weekend upgrade), the Exchange Server computers have significant performance issues. These performance issues can sometimes be reduced; for example, if most of the users in your organization have current .ost files. But in general, we recommend staging deployment of Cached Exchange Mode over a period of time.
The following scenarios include examples of how you can deploy Cached Exchange Mode to avoid a large initial performance impact on the Exchange Server computers and, in some cases, minimize the time users spend waiting for the initial synchronization:
• Retain Outlook .ost files when you deploy Cached Exchange Mode. Because existing .ost files are merely updated with the latest mailbox information when Outlook with Cached Exchange Mode starts for the first time, retaining these .ost files when you deploy Cached Exchange Mode can help reduce the load on your organization's Exchange Server computers. Users who already have .ost files will have less Outlook information to synchronize with the server. This scenario works best when most users already have .ost files that have been synchronized recently with Exchange Server. To retain .ost files while you deploy Outlook with Cached Exchange Mode, do not specify a new Exchange Server computer when you customize Outlook profile information in the OCT. Or, when you customize Outlook profiles in the OCT, clear the Overwrite existing Exchange settings if an Exchange connection exists (only applies when modifying the profile) check box. (If you specify an Exchange Server computer when you configure and deploy Outlook with this option enabled, Outlook replaces the Exchange service provider in the MAPI profile, which removes the profile's entry for existing .ost files.) If you are currently using non-Unicode (ANSI) .ost files, we recommend that you upgrade users’ .ost files to Unicode for improved performance and functionality. In this case, the old non-Unicode (ANSI) .ost files cannot be retained; they would be re-created in the Unicode format.
For information about how to force an upgrade of an existing non-Unicode (ANSI) formatted .ost file to Unicode format, see the section “Force upgrade of non-Unicode ANSI format .ost files to Unicode” in Configure Cached Exchange Mode in Outlook 2010.
• Provide seed .ost files to remote users, and then deploy Cached Exchange Mode after users have installed the .ost files that you provide. If most users in your organization do not currently have .ost files or are not using Cached Exchange Mode, you can deploy Outlook 2010 with Cached Exchange Mode disabled. Then, before the date on which you plan to deploy Cached Exchange Mode, you provide initial, or seed, .ost files to each user with a snapshot of the user's mailbox; for example, by providing or mailing to the user a CD that contains the file together with installation instructions. You might also want to provide a recent version of your organization's Office Address Book (OAB) with Full Details. You configure and deploy Cached Exchange Mode when users confirm that they have installed the files.
When you update your Outlook deployment to use Cached Exchange Mode later, Exchange Server updates users' existing .ost files and there is much less data to synchronize than there would be if a new .ost file and OAB were created for each user. To create individual CDs for each user's .ost file can be time-consuming. Therefore, this seed-file deployment option might be most useful for select groups of remote users who would otherwise spend lots of time waiting for the initial mailbox and OAB synchronization, perhaps at a high cost, depending on their remote connection scenario.
For more information about how to create initial .ost files, see Providing an initial OST file for an Outlook Cached Exchange Mode deployment (). The article describes the creation initial .ost files for Office Outlook 2003. The process works similarly for Office Outlook 2007 and Outlook 2010.
• Deploy Outlook with Cached Exchange Mode to groups of users over time. You can balance the workload on the Exchange Server computers and the local area network by upgrading groups of users to Cached Exchange Mode over time. You can reduce the network traffic and server-intensive work of populating .ost files with users' mailbox items and downloading the OAB by rolling out the new feature in stages. The way that you create and deploy Cached Exchange Mode to groups of users depends on your organization's usual deployment methods. For example, you might create groups of users in Microsoft Systems Management Server (SMS), to which you deploy a SMS package that updates Outlook to use Cached Exchange Mode. You deploy SMS to each group over a period of time. To balance the load as much as you can, choose groups of users whose accounts are spread across groups of Exchange Server computers.
Upgrading current Cached Exchange Mode users to Outlook 2010
The process of upgrading users to Outlook 2010 with Cached Exchange Mode already enabled in Office Outlook 2003 or Office Outlook 2007 is straightforward. If you do not change Cached Exchange Mode settings, the same settings are kept for Outlook 2010. There is no change to the .ost or OAB file format, and you do not need to re-create these files during an upgrade.
However, note that the option to share non-mail folders was introduced in Office Outlook 2007 and is enabled by default. Therefore, existing Office Outlook 2003 profiles with Cached Exchange Mode will have this setting enabled when users are upgraded. This could be problematic if:
• Users in your organization use ANSI .ost files.
• Users' .ost files are close to the size limit.
• Your organization uses shared folders extensively.
When these factors are all present, downloading shared non-mail folders can create performance issues and other problems.
For new Outlook 2010 profiles or for upgrading existing Office Outlook 2003 profiles, use the OCT to disable the non-mail folder sharing option and therefore help prevent problems with downloading non-mail folders. When upgrading existing Office Outlook 2007 profiles, you can disable this setting by using the Group Policy Object Editor.
In addition, be aware that caching for shared non-mail folders works differently from other caching for Cached Exchange Mode. With shared non-mail folders, replication to the local .ost file starts only when the user clicks the shared folder. Once a user has activated caching for the folder by clicking it, Outlook updates the folder just like other Outlook folders are synchronized in Cached Exchange Mode. However, if the user does not go to the folder at least once every 45 days (the default value), the local data will be not be updated further until the user clicks the folder again.
You can configure the Synchronizing data in shared folders option in Group Policy. For more information about how to configure Cached Exchange Mode by using Group Policy, see Configure Cached Exchange Mode in Outlook 2010.
Deploying Cached Exchange Mode to users who already have .ost files
Some Outlook users who connect to Exchange Server in online mode might have .ost files. If these users have a non-Unicode (ANSI) formatted .ost file and large Exchange mailboxes, they might experience errors when Outlook attempts to synchronize their mailboxes to their .ost files. We recommend that you upgrade users’ .ost files to the Unicode format as Outlook Unicode files do not have the 2-GB size limit that Outlook ANSI files do. Unicode is the default file format for Outlook 2010. For information about how to force an upgrade of an existing non-Unicode (ANSI) formatted .ost file to Unicode format, see the section “Force upgrade of non-Unicode ANSI format .ost files to Unicode” in the article Configure Cached Exchange Mode in Outlook 2010.
Using Group Policy to enforce Cached Exchange Mode settings
By using Group Policy, you can help prevent users from enabling Cached Exchange Mode in Outlook, and you can enforce download options for Cached Exchange Mode or configure other Cached Exchange Mode options.
For example, you can specify the default times between Exchange Server synchronizations when data changes on an Exchange Server computer or on the client computer. You can configure these options as defaults by using the Modify user settings option in the Office Customization Tool, or you can lock down the settings by using Group Policy.
For steps to lock down settings by using Group Policy, see Configure Cached Exchange Mode in Outlook 2010.
Additional resources
For more information about how to plan a Cached Exchange Mode deployment, see the following resources.
• When you use Office Outlook 2003, Office Outlook 2007, or Outlook 2010 with Exchange Server-based systems, you can use Cached Exchange Mode and other features to enhance the user experience regarding issues such as high latency, loss of network connectivity, and limited network bandwidth. Download the Client Network Traffic with Exchange 2003 white paper () to learn about these improvements.
• Outlook 2010 includes the ability to automatically configure user accounts. Download the Outlook Automatic Account Configuration whitepaper () to learn how the discovery mechanisms work and how to modify an XML file to configure Autodiscover for your organization.
Plan for security and protection in Outlook 2010
This section describes features in Microsoft Outlook 2010 that can help keep an organization’s e-mail messaging secure.
In this section:
|Article |Description |
|Plan for limiting junk e-mail in Outlook 2010 |Discusses how the Outlook 2010 Junk E-mail Filter works, and which |
| |settings you can configure for the Junk E-mail Filter and for |
| |automatic picture download. |
Plan for limiting junk e-mail in Outlook 2010
This article discusses how the Outlook 2010 Junk E-mail Filter works, and which settings you can configure for the Junk E-mail Filter and automatic picture download to meet the needs of your organization.
This article is for Outlook administrators. To configure Outlook junk e-mail options on your computer, see Junk E-mail Filter options ().
In this article:
• Overview
• Supported account types
• Support in Exchange Server
• Configuring the Junk E-mail Filter user interface
• Configuring Automatic picture download
Overview
Microsoft Outlook 2010 includes features that can help users avoid receiving and reading junk e-mail messages. These include the Junk E-mail Filter and the ability to disable automatic content download from external servers.
Automatic picture download settings help reduce the risk of Web beacons activating in e-mail messages by automatically blocking the download of pictures, sounds, and other content from external servers in e-mail messages. By default, automatic content download is disabled.
The Junk E-mail Filter helps users avoid reading junk e-mail messages. By default, the filter is turned on, and the protection level is set to Low, which is designed to filter the most obvious junk e-mail messages. The filter replaces the rules for processing junk e-mail messages in previous versions of Outlook (before Microsoft Office Outlook 2003). The filter incorporates technology built into the software to evaluate e-mail messages to determine whether the messages are likely to be junk e-mail, in addition to filtering lists that automatically block or accept messages to or from specific senders.
The Junk E-mail Filter contains two parts:
• Three Junk e-mail Filter lists: Safe Senders, Safe Recipients, and Blocked Senders.
• The Junk E-mail Filter that evaluates whether an unread message should be treated as junk e-mail based on several factors that include the message content and whether the sender is included in Junk E-mail Filter lists.
All settings for the Junk E-mail Filter are stored in each user's Outlook profile. You can override the profile settings by using Group Policy or set default Junk E-mail Filter configurations by using the Office Customization Tool (OCT).
The Junk E-mail Filter is provided for a subset of Outlook 2010 account types. The types are listed in the following section, Supported account types. The filter works best when it is used with Microsoft Exchange Server 2003 and later versions. Note that Exchange Server 2003 is the earliest version of Exchange Server that can be used with Outlook 2010.
When Outlook users are upgraded to Outlook 2010, existing Junk E-mail Filter lists are maintained, unless you deploy new lists to users.
Supported account types
Outlook 2010 supports junk e-mail filtering for the following account types:
• Microsoft Exchange Server e-mail accounts in Cached Exchange Mode
• Microsoft Exchange Server e-mail accounts when mail is delivered to a personal Outlook Data File (.pst)
• HTTP accounts
• POP accounts
• Windows Live Hotmail accounts
• IMAP accounts
The following account types are not supported for the Outlook 2010 Junk E-mail Filter:
• Microsoft Exchange Server e-mail accounts in Online mode
• Third-party MAPI providers
Support in Exchange Server
If users use Cached Exchange Mode or download to a personal Outlook Data File (.pst), the Junk E-mail Filter lists that are available from any computer are also used by the server to evaluate mail. This means that if a sender is a member of a user's Blocked Senders list, mail from that sender moves to the Junk E-mail folder on the server and is not evaluated by Outlook 2010. In addition, Outlook 2010 uses the Junk E-mail Filter to evaluate e-mail messages.
If users’ accounts are set to connect in Online mode, the Junk E-mail Filter lists that are available from any computer are also used by the server to evaluate mail. This means that if a sender is a member of a user's Blocked Senders list, mail from that sender moves to the Junk E-mail folder on the server and is not evaluated by Outlook 2010.
Configuring the Junk E-mail Filter user interface
You can specify several options to configure how the Junk E-mail Filter works for your users. These include the following:
• Set the Junk E-mail Filter protection level.
• Permanently delete suspected junk e-mail messages or move the messages to the Junk E-mail folder.
• Trust e-mail messages from users' Contacts.
The default values for the Junk E-mail Filter are designed to help provide a positive experience for users. However, you can configure these settings to different defaults and set other options and policies when you deploy Outlook 2010 to your organization.
Junk e-mail settings are set only one time. When the user first starts Outlook 2010, the settings are configured in the profile that the user selects. Other profiles the user has, or may create later, do not include the settings that you have configured. Instead, default settings are used.
Default values for the Junk E-mail Filter settings are as follows:
• Junk E-mail protection level: Set to LOW
• Permanently delete Junk E-mail: Set to OFF
• Trust E-mail from Contacts: Set to OFF
You can use the OCT to configure these options to specify default values for users, or the options can be enforced by Group Policy. For information about how to configure options for the Junk E-mail Filter, see Configure junk e-mail settings in Outlook 2010.
[pic]Important:
If you configure default values by using the OCT or enforce settings by using Group Policy, the setting Junk Mail Import list must be configured so the new configurations can be applied.
You can configure the following settings for the Outlook 2010 Junk E-mail filter. In the OCT, on the Modify user settings page, these settings are under Microsoft Outlook 2010\Outlook Options\Preferences\Junk E-mail. In Group Policy, these settings are under User Configuration\Administrative Templates\Microsoft Outlook 2010\Outlook Options\Preferences\Junk E-mail.
|Junk e-mail option |Description |
|Add e-mail recipients to users' Safe Senders Lists |Automatically add all e-mail recipients to users' Safe Senders Lists.|
|Hide Junk Mail UI |In Group Policy, disable junk e-mail filtering and hide related |
| |settings in Outlook. |
|Hide warnings about suspicious domain names in e-mail addresses |Enable to hide warnings about suspicious domain names in the e-mail |
| |addresses. |
|Junk Mail Import List |Option in the OCT. You must enable this setting to enable other junk |
| |e-mail settings configured in the OCT or in Group Policy. |
|Junk E-mail protection level |Select the level of junk e-mail protection for users: No Protection, |
| |Low, High, Trusted Lists Only. |
|Overwrite or Append Junk Mail Import List |Change default from overwrite Junk Mail Import list to append to the |
| |list. |
|Permanently delete Junk E-mail |Permanently delete suspected junk e-mail instead of moving it to the |
| |Junk E-mail folder. |
|Specify path to Blocked Senders list |Specify a text file that contains a list of e-mail addresses to |
| |append to or overwrite the Blocked Senders list. |
|Specify path to Safe Recipients list |Specify a text file that contains a list of e-mail addresses to |
| |append to or overwrite the Safe Recipients list. |
|Specify path to Safe Senders list |Specify a text file that contains a list of e-mail addresses to |
| |append to or overwrite the Safe Senders list. |
|Trust E-mail from Contacts |Trust e-mail addresses included in users' Contacts folders. |
Deploying default Junk E-mail Filter lists
You can deploy default Junk E-mail Filter lists to your users. The Junk E-mail Filter uses these lists as follows:
• Safe Senders list E-mail messages that were received from the e-mail addresses in the list or from any e-mail address that includes a domain name in the list are never treated as junk e-mail.
• Safe Recipients list E-mail messages sent to the e-mail addresses in the list or to any e-mail address that includes a domain name in the list are never treated as junk e-mail.
• Blocked Senders list E-mail messages that were received from the e-mail addresses in the list or from any e-mail address that includes a domain name in the list are always treated as junk e-mail.
If a domain name or e-mail address is a member of both the Blocked Senders list and the Safe Senders list, the Safe Senders list takes precedence over the Blocked Senders list. This reduces the risk that mail that users want might be treated as junk e-mail by mistake. The lists are stored on the Exchange server and are available if users roam.
To deploy the Junk E-mail Filter lists, you create the lists on a test computer and distribute the lists to your users. You can distribute the lists by putting the lists on a network share, or if you have remote users not connected to the domain, you can use the OCT to add the files by using the Add files option. The lists that you provide are default lists. If you deploy the lists by using Group Policy, users can change the lists during their Outlook session. When users restart Outlook, Group Policy will append the list by default or, if you have enabled Overwrite or Append Junk Mail Import List, their changes will be overwritten with the original list that you deployed. For information about how to create and deploy default lists, see Configure junk e-mail settings in Outlook 2010.
Configuring 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 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 2010 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.
You can configure the following settings for automatic picture download. In the OCT, on the Modify user settings page, these settings are under Microsoft Outlook 2010\Security\Automatic Picture Download Settings. In Group Policy, these settings are under User Configuration\Administrative Templates\Microsoft Outlook 2010\Security\Automatic Picture Download Settings.
|Automatic picture download option |Description |
|Automatically download content for e-mail from people in Safe Senders|Enable this option to automatically download content when e-mail |
|and Safe Recipients lists |message is from someone in the user's Safe Senders list or to someone|
| |in the user's Safe Recipients list. |
|Block Trusted Zones |Disable this option to include Trusted Zones in the Safe Zones for |
| |Automatic Picture Download. |
|Display pictures and external content in HTML e-mail |Enable this option to automatically display external content in HTML |
| |mail. |
|Do not permit download of content from safe zones |Disable this option to automatically download content for sites in |
| |Safe Zones (as defined by Trusted Zones, Internet, and Intranet |
| |settings). |
|Include Internet in Safe Zones for Automatic Picture Download |Automatically download pictures for all Internet e-mail. |
|Include Intranet in Safe Zones for Automatic Picture Download |Automatically download pictures for all Intranet e-mail |
For information about how to configure automatic picture download, see Configure junk e-mail settings in Outlook 2010.
See Also
Configure junk e-mail settings in Outlook 2010
Plan for Project 2010
This article includes prerequisites and installation instructions for Microsoft Project 2010 Beta. The system requirements for Project 2010 are slightly different from the requirements for Microsoft Office 2010. For system requirements, see Microsoft Project Professional 2010 in System requirements for Office 2010. The prerequisites for installing Project 2010 apply only if you want to synchronize Project 2010 with a SharePoint Tasks List or use Visual Reports.
This article describes the most direct approach to install Project 2010 and to enable all available options so that you can use the product. We recommend following the procedures in this document in sequence for best results.
In this article:
• Prerequisites for Project 2010
• Installing Project 2010
Prerequisites for Project 2010
For Project 2010, to enable the feature that allows synchronizing Project 2010 with a SharePoint Tasks List, you must install either Microsoft Access 2010 or Microsoft Visio 2010.
To use Visual Reports with Office 2010, you must install the following before installing Project 2010:
• Office 2010
• Visio 2010
• Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider, which is available as a free download from Microsoft SQL Server 2008 Feature Pack, October 2008 ()
Installing Project 2010
Plan for SharePoint Workspace 2010
This article describes how to plan a Microsoft SharePoint Workspace 2010 deployment. SharePoint Workspace 2010 is a client for Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010 that supports online and offline collaboration. Therefore, it enables anytime synchronization of desktop content with SharePoint documents and lists. SharePoint Workspace 2010 also provides options that support peer collaboration through the creation of Groove workspaces and shared folders that do not require SharePoint connections, as described in SharePoint Workspace 2010 overview. SharePoint Workspace 2010 is installed automatically with enterprise versions of Microsoft Office 2010 or can be installed separately from the Microsoft Download Center (). The planning phases described in this article help you prepare for a successful deployment that optimizes collaboration throughout an organization’s software management infrastructure.
In this article:
• Plan topology for SharePoint Workspace 2010
• Plan network settings for SharePoint Workspace 2010
• Plan for capacity
• Plan for security
• Plan for authentication
• Plan for alternate access mapping
• Plan for performance monitoring and throttling
• Plan for SharePoint list and library actions and settings
• Plan for search
• Plan for SharePoint Workspace backup and recovery
Plan topology for SharePoint Workspace 2010
Planning a SharePoint Workspace deployment begins with choosing the level of collaboration that you need for employees in your organization. You can then choose the topology that best supports your collaboration strategy. When choosing a SharePoint Workspace topology, consider the operating environment and productivity requirements. Typical decision factors include the following:
• Whether SharePoint Server 2010 or SharePoint Foundation 2010 is part of your organization’s collaboration system.
• Whether team contributors work online and offline.
• Whether you need to support flexible, agile peer collaboration.
• Whether usage management practices permit peer collaboration.
• Whether team collaboration needs to extend outside a private network or LAN to trusted partners and field sites.
• Whether Active Directory system is used.
• Whether valuable contributions are expected from clients that have no access to your SharePoint Server 2010 server.
• Whether centralized management of peer collaboration is necessary for the organization’s security and management infrastructure.
The following table shows how different SharePoint Workspace topologies address these conditions:
SharePoint Workspace topologies and capabilities
|Topology |Capabilities |
|SharePoint Workspace as a SharePoint client only |This topology supports or builds upon: |
| |• Access to SharePoint Server 2010 or SharePoint Foundation 2010 |
| |document libraries and lists. |
| |• Team contributors who work online and offline. |
|SharePoint Workspace as a peer collaboration client |This topology supports or builds upon: |
| |• Team contributors working online and offline. |
| |• Flexible, agile peer collaboration. Groove workspaces support |
| |multiple communication protocols. This lets organizations control |
| |which ports are open for peer message transport. |
| |• Team collaboration extended outside a private network to trusted |
| |partners and field sites. |
| |• Valuable contributions from clients that have no access to the |
| |SharePoint Server 2010 server. |
|SharePoint Workspace as a SharePoint and peer collaboration client |This topology supports or builds upon: |
| |• Access to SharePoint Server 2010 or SharePoint Foundation 2010 |
| |document libraries and lists. |
| |• Team contributors working online and offline. |
| |• Flexible, agile peer collaboration. Groove workspaces support |
| |multiple communication protocols. This lets organizations control |
| |which ports are open for peer message transport. |
| |• Team collaboration extended outside a private network to trusted |
| |partners and field sites. |
| |• Valuable contributions from clients that have no access to the |
| |SharePoint Server 2010 server. |
|Groove Server and SharePoint Workspace as a managed collaboration |This topology supports or builds upon: |
|system |• Centralized management of peer collaboration to address the |
| |organization’s security and management requirements. |
| |• Team contributors working online and offline. |
| |• Flexible, agile peer collaboration. |
| |• Team collaboration extended outside a private network to trusted |
| |partners and field sites. |
| |• Valuable contributions from clients that have no access to the |
| |SharePoint Server 2010 server. |
| |• Existing integration with Active Directory system. |
The following sections describe how the key SharePoint Workspace deployment topologies map to different collaboration needs.
SharePoint Workspace as a SharePoint client only
SharePoint Workspace as a SharePoint client is most suitable for organizations with SharePoint team members and partners who need to contribute content from outside the corporate infrastructure — from data that is collected in the field or from locations that do not have a SharePoint server connection. This topology provides SharePoint Workspace users with the following collaboration option:
• The ability to easily create a SharePoint workspace that establishes a connection between a SharePoint server and a SharePoint Workspace client. This enables an individual SharePoint team member or partner to take SharePoint site content onto a local computer. By using a SharePoint workspace, a contributor can add, change, and delete content for a SharePoint document library or list whether online or offline, regardless of connectivity to a SharePoint server. Synchronization of content updates between the SharePoint Workspace client and SharePoint sites occurs automatically when the client is online so that contributors can share the work that they performed while offline as easily as they can share the work that they generate while connected to the Internet.
[pic]Note:
The SharePoint Workspace client lets users create SharePoint workspaces and peer workspaces. Peer workspace types can be Groove workspaces or Shared Folders, as described in SharePoint Workspace as a SharePoint and peer collaboration client. To deploy SharePoint Workspace exclusively as a SharePoint client, supporting SharePoint workspaces only, you can include with your deployment a policy that prohibits peer workspace options, as described in Configure and customize SharePoint Workspace 2010.
For this configuration, a basic level of client management can be achieved by using Windows and Active Directory tools.
SharePoint workspaces rely on SharePoint Workspace communications and dynamics technology to support individual client-to-SharePoint connections that enable SharePoint Workspace users to work with and synchronize SharePoint document and list content on their local computers. Figure 1 shows a basic setup of SharePoint Workspace to Microsoft SharePoint Server 2010.
Figure 1. SharePoint Workspace connection to SharePoint
[pic]
SharePoint Workspace as a peer collaboration client
SharePoint Workspace as a peer collaboration client is most suitable for organizations that need to provide information workers with a well-equipped, easy-to-use collaboration environment where neither Microsoft SharePoint Server 2010 nor Microsoft SharePoint Foundation 2010 is available. This topology provides SharePoint Workspace users with two peer collaboration options:
• The ability to easily and quickly create Groove workspaces where information workers can collaborate safely with trusted peers without the need of a virtual private network (VPN) and with access to a full set of local online and offline collaboration tools. Groove workspace collaboration tools support document creation and sharing, online discussions, meeting management, and Microsoft InfoPath forms, in an environment of real-time collaboration among team members and partners located inside or outside the corporate firewall.
• The ability to create Shared Folders where SharePoint Workspace users can collaborate on content within designated Windows folders on workspace member desktops.
For this configuration, a basic level of client management can be achieved by using Windows and Active Directory tools.
For peer collaboration through Groove workspaces and Shared Folders, SharePoint Workspace builds on its communications and dynamics foundation and provides a workspace manager module with a set of tools, a contacts manager, a message manager, and an implementation of standards-based Public Key Infrastructure (PKI) to help secure Groove workspaces and authenticate workspace members. Groove workspace data resides on client computers and built-in security provisions ensure that workspace member data is encrypted over the network. The core capabilities of SharePoint Workspace tools and components can be exercised on two client computers directly connected over a local area network (LAN), as shown in Figure 2.
Figure 2. Groove workspace peer connections on a LAN
[pic]
To sustain peer communications for Groove workspaces and Shared Folders, when a client is connected to a wide area network (WAN), offline, or behind a firewall, SharePoint Workspace relies on supporting Microsoft Groove Server Manager and Relay services, as shown in Figure 3. These servers, Microsoft-hosted or installed onsite, help ensure timely communication regardless of user context or Internet-wide environmental conditions.
Figure 3 Groove workspace connections beyond a LAN
[pic]
SharePoint Workspace as a SharePoint and peer collaboration client
SharePoint Workspace as a SharePoint and peer collaboration client is most suitable for organizations that need to synchronize client desktop content with SharePoint document libraries and lists while extending collaboration to ad hoc teams that work outside the SharePoint document framework. This option merges the previously described topologies to provide SharePoint Workspace users with the following collaboration options:
• The ability to create a SharePoint workspace that establishes a connection between a SharePoint server and a SharePoint Workspace client. This enables an individual SharePoint team member or partner to take SharePoint site content onto a local computer, as described in SharePoint Workspace as a SharePoint client only.
• The ability to easily create Groove workspaces where trusted peers can collaborate safely without the need of a VPN, as described in SharePoint Workspace 2010 overview.
• The ability to create Shared Folder workspaces where SharePoint Workspace users can collaborate on content within designated Windows folders on workspace member desktops.
For this configuration, a basic level of client management can be achieved by using Windows and Active Directory tools.
SharePoint Workspace communications and dynamics modules, together with TCP/IP protocols summarized in Plan network settings for SharePoint Workspace 2010, support message transport and content synchronization between individual clients and SharePoint servers, and between client peers. Figure 4 shows a SharePoint Workspace client/server system that involves a SharePoint server, Groove Server relay and management services, and four SharePoint Workspace clients:
Figure 4. SharePoint Workspace with SharePoint and Groove servers
[pic]
Groove Server and SharePoint Workspace as a managed collaboration system
When Groove workspaces and Shared Folders are used, installation of Microsoft Groove Server 2010 onsite as part of SharePoint Workspace deployment provides optimal client administration. Groove Server provides two applications that facilitate SharePoint Workspace deployment and operation in an enterprise: Groove Server Manager provides management, reporting, and policy distribution services, and Groove Server Relay facilitates client communications. This system can function with or without SharePoint Server and can be extended to partners outside corporate firewalls.
The following table shows how SharePoint Workspace topology options can serve a range of scenarios.
SharePoint Workspace scenarios and topologies
|Scenario |Description |Chosen topology and required components |
|Financial services |• Scope: City-wide |SharePoint Workspace as SharePoint client only|
| |• Size: 2,000 employees |Required components: |
| |• SharePoint Workspace users: 1,000 |• SharePoint Server |
| |• SharePoint infrastructure in place |• SharePoint Workspace clients |
|Regional school system |• Scope: State-wide |SharePoint Workspace as a peer collaboration |
| |• Size: 4,000 employees |client |
| |• SharePoint Workspace users: 10,000 |Required components: |
| |• No existing SharePoint installation |• SharePoint Workspace clients that have |
| | |Internet connectivity |
|Regional healthcare system |• Scope: Region |SharePoint Workspace as a SharePoint and peer |
| |• Size: 5,000 employees |collaboration client |
| |• SharePoint Workspace users: 10,000 |Required components: |
| |• SharePoint infrastructure in place |• SharePoint Server |
| | |• SharePoint Workspace clients |
| | |• Internet connectivity |
|Multinational corporation |• Scope: Global |Groove Server and SharePoint Workspace as a |
| |• Size: 500,000 employees |SharePoint managed collaboration system |
| |• SharePoint Workspace users: 50,000 |Required components: |
| |• IT department: Yes |• Microsoft Groove Server 2010 |
| | |• SharePoint Workspace clients |
| | |• Active Directory system (recommended) |
| | |• Internet connectivity (recommended) |
Plan network settings for SharePoint Workspace 2010
Microsoft SharePoint Workspace 2010 automatically configures Windows Firewall network ports for optimal operation. To verify client port connections or to configure Microsoft SharePoint Server and SharePoint Workspace ports for SharePoint workspaces only, start the Windows Firewall Control Panel add-in and edit settings as necessary.
For more information about SharePoint Workspace protocols, see Microsoft protocol documents ().
The following table describes which ports are required for which protocols in SharePoint Workspace.
Client port settings for SharePoint Workspace 2010
|Port |Protocols supported |Description |
|80/TCP - Outgoing |Microsoft File Synchronization by SOAP over |Supports the following communications: |
| |HTTP Protocol (MS-FSSHTTP) |• For SharePoint workspaces — Synchronization |
| |Microsoft Groove HTTP Encapsulation of Simple |of document and list content between Microsoft |
| |Symmetric Transport Protocol (MS-GRVHENC) |SharePoint Server and SharePoint Workspace |
| | |clients. |
| | |• For Groove workspaces and Shared Folders — |
| | |Transmission of SSTP messages among SharePoint |
| | |Workspace clients and Groove Relay servers when|
| | |neither SSTP port 2492/TCP nor port 443/TCP is |
| | |available. Encapsulates SSTP transmissions in |
| | |HTTP. |
| | |• For Groove workspaces and Shared Folders — |
| | |SOAP communication between SharePoint Workspace|
| | |clients and Groove management servers. |
|443/TCP - Outgoing |HTTPS |Supports the following communications: |
| |Microsoft Groove HTTP Encapsulation of Simple |• For SharePoint workspaces —Synchronization of|
| |Symmetric Transport Protocol Security Protocol|SSL-protected content between Microsoft |
| |(MS-GRVSSTPS) |SharePoint Server and SharePoint Workspace |
| | |clients. |
| | |• For Groove workspaces and Shared Folders — |
| | |Transmission of SSTP messages among SharePoint |
| | |Workspace clients and relay servers when SSTP |
| | |port 2492/TCP is not available. Utilizes Secure|
| | |HTTP Tunneling technology. |
|2492/TCP - Incoming and outgoing |Microsoft Groove Simple Symmetric Transport |Supports the following communications: |
| |Protocol (MS-GRVSSTP) |• For Groove workspaces and Shared Folders — |
| | |Transmission of SSTP messages among SharePoint |
| | |Workspace clients and relay servers. |
|1211/UDP - Incoming and outgoing |Local Area Network Device Presence Protocol |Supports following communications: |
| |(LANDPP) |• For Groove workspaces and Shared Folders - |
| | |Local area network (LAN) device presence |
| | |detection between SharePoint Workspace clients.|
Plan for capacity
To set up a topology that supports the expected SharePoint Workspace user base, collect the following information and determine network and SharePoint Server hardware needs accordingly:
• How many SharePoint Workspace users do you have to support on the LAN?
• How many internal clients will synchronize with SharePoint Server by using SharePoint workspaces?
• How many internal and external clients will communicate by using Groove workspaces or Shared Folders?
• How many concurrent SharePoint Workspace peer connections do you expect?
• How many bytes of client data do you expect to synchronize with SharePoint Server per day?
• How many bytes of client data do you expect to transmit between Groove workspaces per day?
For information about choosing the appropriate hardware to support predicted SharePoint Workspace client workload, see the Office client requirements listed in System requirements for Office 2010.
To determine the SharePoint Server requirements that will be necessary to support expected SharePoint Workspace workload, review Plan for performance monitoring and throttling, and SharePoint Server 2010 specifications in Deployment for SharePoint Server 2010. ((office.14).aspx)
Plan for security
SharePoint Workspace client exchanges with SharePoint sites rely on synchronization protocol and external mechanisms for security, such as those provided by VPNs or Secure Socket Layer (SSL) technology. Therefore, we recommend SSL encryption for SharePoint connections from outside a corporate domain. You can configure Group Policy settings that apply across an Active Directory organizational unit, as described in Configure and customize SharePoint Workspace 2010. In addition, you can secure the SharePoint site from unauthorized access by setting access control lists appropriately. For guidance about how to set access control for users to synchronize with SharePoint libraries and lists, see Managing Site Groups and Permissions () and Managing Site Users and Specifying Permissions ().
SharePoint Workspace uses strong cryptographic and encryption technologies to protect SharePoint Workspace accounts, which are the secure repositories for each user’s cryptographic keys, identity, contacts, messages, and unique workspace identifiers. Windows authentication and users’ Windows logon credentials are used to unlock SharePoint Workspace accounts.
SharePoint Workspace 2010 does not encrypt SharePoint Workspace 2010 documents and other binary files, including SharePoint workspace content, on disk. Therefore, consider using BitLocker Drive Encryption to encrypt all content on client data drives. For more information see BitLocker Drive Encryption (). You can strengthen protection by blocking Windows Search in the SharePoint Workspace Data directory, to prevent generation of unencrypted Search indexes. However, be aware that content shared with other clients that are not equally protected will remain unencrypted and searchable.
For Groove workspaces and Shared Folders, SharePoint Workspace uses native symmetric and public key cryptographic technologies to authenticate, encrypt, and protect transmissions between clients over the network. Strong encryption protects the following content on-disk: Groove instant messages, Groove invitations, Groove Discussion and Notepad entries, archived Groove workspaces, and Forms tool templates.
Plan for authentication
SharePoint Workspace 2010 uses Windows logon and the Data Protection API (DPAPI) to authenticate the user and access the SharePoint Workspace account. This single sign-on user (SSO) logon means that additional SharePoint Workspace-specific credentials are not required.
For authenticating SharePoint Workspace users to SharePoint Server, SharePoint Workspace supports the following SharePoint Server methods: Windows authentication and forms-based authentication. Typically, Windows authentication is used for internal SharePoint Workspace user access to SharePoint sites. Forms-based authentication can be used for external SharePoint Workspace user access to SharePoint sites.
For authenticating SharePoint Workspace users to one another (for Groove workspaces, Shared Folders, and messaging), SharePoint Workspace relies on its native public key infrastructure (PKI).
For more information about Single Sign-On for SharePoint Server, see Enterprise Single Sign-On ().
For more information about forms-based authentication, see Configure Forms Based Authentication ().
Plan for alternate access mapping
SharePoint Server supports alternate access mapping, which lets you define multiple URLs per site. When SharePoint workspaces are being used, you can take advantage of this capability to ensure that SharePoint Workspace can synchronize with SharePoint Server multiple URLs. Defining multiple URLs is useful for deployment scenarios in which the URL of a Web request received by Internet Information Services (IIS) differs from the URL that was typed by an end user; for example, in scenarios that include reverse proxy publishing and load balancing. For more information about alternate access mapping, see Planning alternate access mappings ().
Plan for performance monitoring and throttling
SharePoint Server 2010 moderates the flow of client communications by throttling requests when built-in server health monitors indicate that server performance is lagging because of heavy workload. When SharePoint workspaces are being used, SharePoint Workspace clients respond to SharePoint Server back-off signals by adjusting the frequency of server requests. SharePoint Workspace synchronization frequency adjustments reflect SharePoint workspace activity and SharePoint site changes, in such a way that the periodicity is lower when activity is minimal than when activity is greater. These adjustments reduce overall client bandwidth usage while they improve server performance.
In the case of Groove workspaces, SharePoint Workspace provides built-in performance provisions and relies on Groove Server Relay services, hosted by Microsoft or installed onsite to optimize communications. To optimize performance, SharePoint Workspace transmits Groove workspace data directly from client to client when network conditions allow. When data is addressed to a client that cannot be reached directly, Groove sends data over relay servers that optimize message transmission. Total bandwidth use under conditions of high traffic is often less when relay servers help in message transmission.
Plan for SharePoint list and library actions and settings
The following SharePoint Server 2010 actions and settings apply to SharePoint Workspace 2010:
• Site Actions: Sync to SharePoint Workspace — SharePoint Workspace users connected to the SharePoint site can click Sync to SharePoint Workspace to create a SharePoint workspace on the contributor’s local computer, or to synchronize content if a SharePoint workspace already exists for the site. From the local workspace, the user can add, change, or delete content regardless of connectivity to the SharePoint site. Synchronization with the SharePoint site occurs automatically at set intervals, or the user can click the Sync tab in the SharePoint workspace to force synchronization.
[pic]Note:
Sync to SharePoint Workspace is also available as a ribbon option from a SharePoint document library or list.
• Site Actions/Site Settings/Site Administration/Search and offline availability/Offline Client Availability — SharePoint site administrators must select this setting to enable SharePoint Workspace clients to access the site.
Plan for search
SharePoint Workspace content can be searched by using Windows Search 4.0 or later versions. By default, Windows Search crawling (index creation) is enabled for some SharePoint Workspace content. SharePoint Workspace users can access Windows Search 4.0 by clicking Search on the Home tab of the ribbon, unless prevented from doing this by a Windows policy.
Administrators can block Windows Search of SharePoint Workspace content and can override any user search setting by deploying an Active Directory GPO, as described in Configure and customize SharePoint Workspace 2010. For information about how to use Windows Search, see the Windows Search Administrator Guides ().
Plan for SharePoint Workspace backup and recovery
All SharePoint Workspace account information resides on client computers. Account information includes cryptographic keys and user identity information. SharePoint Workspace provides mechanisms for user account backup and recovery. In addition, users can back up Groove workspaces as workspace archives.
To help safeguard SharePoint Workspace user accounts, encourage SharePoint Workspace users to observe the following best practices:
• Enable SharePoint Workspace account recovery. The Enable account recovery setting can be accessed in SharePoint Workspace 2010 through the Account Preferences option and gives users a secure method for regaining access to accounts if a Windows logon must be reset. The Enable account recovery check box should remain selected on all clients, because it enables account recovery. Consider warning users against clearing this setting.
[pic]Note:
Enable account recovery also supports account portability and the ability to use the account on multiple computers. For organizations that must prevent users from porting their account to another computer, Microsoft Groove Server 2010 provides a policy that restricts managed accounts to a single computer.
• Back up SharePoint Workspace user accounts to a file in a secure location. SharePoint Workspace supports account recovery in the event of a lost or corrupted account, by providing an option that enables users to save their accounts to a .grv file. Encourage users to regularly save their accounts to file in a secure location. Users can save their account by clicking the File tab on the ribbon and in the Manage Account drop-down menu selecting Account Preferences, then selecting Save Account as File on the Account tab, entering a file name, and entering a password, for initial account recovery, when prompted. Note that Enable account recovery must be selected in the user’s account preferences for a reset code to be sent and the account to be recovered if the password is forgotten. When this setting is enabled SharePoint Workspace sends a reset code to the e-mail address provided in the Account Configuration Wizard when the account was created, so that users can reset a recovered account.
To help safeguard Groove workspaces, encourage users to periodically back up each Groove workspace by clicking the File tab on the ribbon, selecting Share, and then configuring the Workspace as Archive option. For more information about how to back up and recover Groove workspaces, see SharePoint Workspace product help at Microsoft products online ().
[pic]Note:
Groove workspace data and tools reside on client computers. Therefore, if other team members share a Groove workspace, the lost workspace can be retrieved from another client computer.
See Also
SharePoint Workspace 2010 overview
Configure and customize SharePoint Workspace 2010
Microsoft protocol documents ()
Plan security for Office 2010
An organization's success often depends on the productivity of its information workers and the integrity and confidentiality of its intellectual property. Many IT departments find it difficult to satisfy these business needs because protection often comes at the expense of productivity. This section describes the new security controls that are available in Microsoft Office 2010 to help you plan a robust defense against threats while maintaining information worker productivity.
In this section:
|Article |Description |
|Security overview for Office 2010 |Provides an overview of new security controls in Microsoft Office 2010|
| |that make it easier for IT professionals to build a robust defense |
| |against threats while maintaining information worker productivity. |
|Understand security threats and countermeasures for Office 2010 |Provides information to help you plan for a secure desktop |
| |configuration for Office 2010, including which security risks and |
| |threats are relevant to Office 2010, and which might pose a risk to |
| |the organization's business assets or processes. |
|Plan Trusted Locations settings for Office 2010 |Provides information about how to use the Trusted Locations feature in|
|( 2010 to differentiate safe files from potentially harmful |
|86912a9(Office.14).aspx) |files. |
|Plan Trusted Publishers settings for Office 2010 |Provides information about how to use the Trusted Publishers feature |
|( Office 2010 to designate content publishers that you trust. |
|945a312(Office.14).aspx) | |
|Plan security settings for add-ins for Office 2010 |Describes how to control the way add-ins behave, or to prevent users |
| |from running add-ins, by modifying the Office 2010 add-in settings. |
|Plan security settings for ActiveX controls for Office 2010 |Describes how to change the way Microsoft ActiveX controls behave in |
|( 2010 by modifying ActiveX control settings. |
|162076b(Office.14).aspx) | |
|Plan security settings for VBA macros for Office 2010 |Describes how to control the way Visual Basic for Applications (VBA) |
| |and VBA macros behave by modifying Microsoft Office 2010 VBA and VBA |
| |macros settings. |
|Plan COM object categorization for Office 2010 |Describes how to control the behavior of certain COM objects in Office|
|( by using COM object categorization. |
|449b257(Office.14).aspx) | |
|Plan Protected View settings for Office 2010 |Provides information about how to configure Protected View, a new |
| |security feature in Office 2010 that helps mitigate exploits to your |
| |computer by opening files in a restricted environment so they can be |
| |examined before the files are opened for editing. |
|Plan Office File Validation settings for Office 2010 |Provides information about how to configure Office File Validation, a |
| |new security feature in Office 2010 that helps prevent file format |
| |attacks by scanning Office binary file formats before the files are |
| |opened. |
|Plan privacy options for Office 2010 |Describes how to configure privacy options in Office 2010 to meet an |
| |organization’s security requirements. |
|Plan for Information Rights Management in Office 2010 |Provides a summary of Information Rights Management (IRM) technology |
|( how it works in Office applications. |
|aff440a(Office.14).aspx) | |
|Plan for security and protection in Outlook 2010 |Describes features in Microsoft Outlook 2010 that can help keep an |
| |organization’s e-mail messaging secure. |
Security overview for Office 2010
An organization's financial success often depends on the productivity of its information workers and the integrity and confidentiality of its intellectual property. Many IT departments find it difficult to satisfy these business needs because protection often comes at the expense of productivity. When too many security controls are implemented, worker productivity decreases. When too few security controls are implemented, worker productivity increases, but your attack surface also increases, forcing higher remediation costs and a higher total cost of ownership (TCO). Fortunately, several new security controls in Microsoft Office 2010 make it easier for IT professionals to build a robust defense against threats while maintaining information worker productivity.
Four of the new controls help harden and reduce the attack surface and help mitigate exploits. These new controls include the following:
Data Execution Prevention (DEP) support for Office applications A hardware and software technology that helps harden the attack surface by preventing viruses and worms that exploit buffer overflow vulnerabilities from running.
Office File Validation A software component that helps reduce the attack surface by identifying files that do not follow a valid file format definition.
Expanded file block settings Settings managed in the Trust Center and through Group Policy that help reduce the attack surface by providing more specific control over the file types that an application can access.
Protected View A feature that helps mitigate attacks by enabling users to preview untrusted or potentially harmful files in a sandbox environment.
In addition to these new controls, Office 2010 provides several security improvements that further harden the attack surface by helping to ensure the integrity and confidentiality of data. These security enhancements include the following:
• Cryptographic agility
• Trusted time stamping support for digital signatures
• Domain-based password complexity checking and enforcement
• Encryption-strengthening enhancements
• Improvements to the Encrypt with Password feature
• Integrity checking of encrypted files
Office 2010 also provides several security improvements that have a direct affect on information worker productivity. Improvements in the Message Bar user interface, Trust Center user interface settings, and a trust model that persists users’ trust decisions are some examples of the new features that help make security decisions and actions less intrusive to information workers. In addition, many of the new and enhanced security controls can be managed through Group Policy settings. This makes it easier for you to enforce and maintain the organization’s security architecture.
In this article:
• Layered defense is key
• Helping users make better security decisions
• Giving the administrator full control
• Migrating security and privacy settings from Office 2003
Layered defense is key
Defense in depth, a central tenet of any effective security architecture, is a security strategy that implements multiple overlapping layers of defense against unauthorized users and malicious code. In mid-sized and large organizations, the layers of defense typically include the following:
• Perimeter network protection, such as firewalls and proxy servers
• Physical security measures, such as restricted data centers and server rooms
• Desktop security tools, such as personal firewalls, virus scanning programs, and spyware-detection programs
A defense-in-depth strategy helps ensure that security threats are met with multiple and redundant security controls. For example, if a worm breaches the perimeter firewall and gains access to the internal network, it still has to pass through the virus-scanning program and the personal firewall to damage a desktop computer. A similar mechanism is built into the security architecture of Office 2010.
A four-layer approach
The security architecture of Office 2010 helps you extend the defense-in-depth strategy beyond desktop security tools by providing countermeasures for a layered defense. When implemented, these countermeasures take effect the moment a user attempts to open a file by using an Office 2010 application, and they continue to provide multiple layers of defense until the file is open and ready for editing. The following figure shows the four defensive layers that are built into the Office 2010 security architecture. It also shows some countermeasures that you can implement for each layer.
[pic]
Hardening the attack surface
This defensive layer helps harden the attack surface of Office 2010 applications by using a countermeasure known as Data Execution Prevention (DEP). DEP helps prevent buffer overflow exploits by identifying files that attempt to run code from a part of memory reserved only for data. By default, DEP is enabled in Office 2010. You can manage DEP settings in the Trust Center or through Group Policy settings.
Reducing the attack surface
This defensive layer helps reduce the attack surface of Office 2010 applications by limiting the kinds of files that applications can open and by preventing applications from running certain kinds of code that is embedded in files. To do this, Office applications use the following three countermeasures:
• Office File Validation This software component scans files for format differences and based on the implemented setting can prevent a file from being opened for editing if the format is not valid. A file that contains a file format exploit against an Office 2010 application is one example of a file that is not valid. By default, Office File Validation is enabled and is primarily managed through Group Policy settings.
• File block settings Introduced in the 2007 Microsoft Office system to reduce the attack surface, these settings enable you to prevent applications from opening and saving certain file types. In addition, you can specify what will occur if you allow a file type to be opened. For example, you can specify whether a file type is opened in Protected View and whether editing is allowed. Several new file block settings have been added in Office 2010. You can manage file block settings in the Trust Center and through Group Policy settings.
• Office ActiveX kill bit This new Office 2010 feature enables you to prevent specific ActiveX controls from running in Office 2010 applications without affecting how those controls run in Microsoft Internet Explorer. By default, Office ActiveX kill bit is not configured. However, you can configure this countermeasure by modifying the registry.
Mitigating exploits
This defensive layer helps mitigate exploits by opening potentially harmful files in an isolated sandbox environment. This sandbox environment, known as Protected View, enables users to preview files before they open them for editing in an application. By default, Protected View is enabled. However, you can turn it off and manage it in the Trust Center and through Group Policy settings.
Improving the user experience
This defensive layer mitigates exploits by reducing the number of security decisions users make and by improving the way users make security decisions. For example, documents that are considered untrustworthy are automatically opened in Protected View without any user feedback. Users can read and close these documents without making any security decisions, which in most cases means that they can effectively finish their work without being confronted with security prompts. If a user wants to edit a document that is in Protected View they can select the option to allow editing. Once editing is allowed, the document will not be opened in Protected View again. If the document contains active content, such as ActiveX controls and macros, a Message Bar appears that prompts the user whether to enable the active content. Once active content is enabled, the user will not be prompted again with the Message Bar for active content. You can configure Message Bar settings and Trusted Documents settings in the Trust Center and through Group Policy settings.
Enhanced hardening countermeasures
In addition to the countermeasures described in the previous section, Office 2010 provides several new and enhanced countermeasures for further hardening of the attack surface. These countermeasures help harden the attack surface by protecting the integrity and confidentiality of data.
Integrity countermeasures
Integrity settings help you mitigate threats to the integrity of business data and business processes. Malicious users attack the integrity of these assets by corrupting documents, presentations, and spreadsheets. For example, a malicious user might attack the integrity of business data or business processes by replacing a file with a similar file that contains corrupted data or information. Two countermeasures have been improved and enhanced — digital signatures and integrity checking of encrypted files — to help you mitigate integrity threats.
Digital signature improvements
Trusted time stamping is now supported in digital signatures, which makes Office documents compatible with the W3C XML Advanced Electronic Signatures (XAdES) standard. Trusted time stamping helps ensure that digital signatures remain valid and legally defensible even if the certificate that is used to sign the document expires. Trusted time stamping support is available only in Microsoft Excel 2010, Microsoft Access 2010, Microsoft PowerPoint 2010, and Microsoft Word 2010. To take advantage of this feature, you must use a time-stamping authority.
In addition to time stamping support, Office 2010 includes several improvements in the user interface that make managing and implementing digital signatures easier for users. You can also configure and manage trusted time stamping through several new Group Policy settings.
Integrity checking of encrypted files
Administrators can now decide whether to implement a hash-based message authentication code (HMAC) when a file is encrypted, which can help determine whether someone has tampered with a file. The HMAC is fully compliant with Microsoft Windows Cryptographic API: Next Generation (CNG), enabling administrators to configure the cryptographic provider, hash, and context that are used to generate the HMAC. These parameters are configurable through Group Policy settings.
Confidentiality countermeasures
Confidentiality settings help you mitigate threats to information that you do not want disclosed either publicly or privately, such as e-mail correspondence, project planning information, design specifications, financial information, customer data, and personal and private information. Several countermeasures have been improved and enhanced to help you mitigate confidentiality threats.
Cryptographic enhancements
Several Office 2010 applications are now cryptographically agile and support CNG, which means that administrators can specify any cryptographic algorithm for encrypting and signing documents. In addition, several Office 2010 applications now support Suite B cryptography.
Encrypt with Password improvements
The Encrypt with Password feature is now compliant with the ISO/IEC 29500 and ISO/IEC 10118-3:2004 requirements. This feature is also interoperable between Office 2010 and the 2007 Office system with Service Pack 2 (SP2), but only if the host operating systems support the same cryptographic providers. In addition, Office 2010 includes several changes in the user interface that make the Encrypt with Password feature easier for users to understand and implement.
Password complexity checking and enforcement
Passwords used by the Encrypt with Password feature can now be checked for length and complexity, and enforced by domain-based password policies. This applies only to passwords that are created by using the Encrypt with Password feature. You can use several new Group Policy settings to manage password complexity checking and enforcement.
Encryption enhancements
The encryption mechanism is enhanced, which helps ensure that the encryption/decryption key is never stored as plain text in a file. In general, these encryption enhancements are transparent to users and administrators.
Helping users make better security decisions
One of the benefits of a layered defense is its stepwise ability to weaken and slow security attacks, which gives you more time to identify attack vectors and deploy alternative countermeasures (if needed). Another benefit of a layered defense is its intrinsic ability to reduce the number of security decisions users have to make. In its default security configuration, Office 2010 makes most of the security decisions, not the user. As a result, users have fewer opportunities to make inaccurate security decisions and are more productive.
The following figure shows a high-level view of the main security controls that are implemented when a user opens a file in Excel 2010, PowerPoint 2010, or Word 2010. Security controls that require no user input are yellow; security controls that require user input are light blue. The figure shows the default behavior of Office 2010. You can change this default behavior to suit the organization’s security requirements and architecture. Also, this figure does not show all of the security controls that can be implemented, such as DEP, encryption, or Information Rights Management.
[pic]
As shown in the previous figure, documents must pass through several defensive layers before users are required to make a security decision. If users do not have to edit a document, they can read the document in Protected View and then close it without making any security decisions. Several key features make this efficient workflow possible.
Improved trust model When users attempt to open a file, Office 2010 evaluates the file’s trust state. By default, trusted files bypass most security checks and are opened for editing without requiring any security decisions by the user. Untrusted files must undergo the security checks that make up the layered defense. Documents that are considered untrustworthy are automatically opened in Protected View without any user feedback. If a user wants to edit a document that is in Protected View, the user can select the option to allow editing. Once editing is allowed, the document will not be opened in Protected View again. If the document contains active content, such as ActiveX controls and macros, a Message Bar appears that prompts the user whether to enable the active content. Once active content is enabled, the user will not be prompted again with the Message Bar for active content. In the 2007 Office system you can use the trusted locations and trusted publishers features to designate trusted files and trusted content. In Office 2010, you can also use a new feature known as Trusted Documents. Trusted Documents lets users designate a file as trusted after viewing the file in Protected View. When a user designates a file as being trusted, the trust decision persists with the file so that the user does not have to make the trust decision again the next time that they open the file.
[pic]Note:
Trusted files do not bypass antivirus checking or ActiveX kill-bit checking. If a file is trusted, it is scanned by the local antivirus scanning program (if available) and any ActiveX controls that have a kill-bit set are disabled.
Transparent countermeasures Several of the new countermeasures in Office 2010 are invisible to the user and require no user interaction. For example, Office 2010 applications evaluate untrusted files for file format differences by using a new technology known as Office File Validation. This technology runs autonomously when a user opens an untrusted file. If no potential file format differences are detected, users have no indication that this technology scanned the file.
[pic]Note:
In some cases, the Office File Validation feature might ask a user for permission to send file scan information to Microsoft to help improve the feature’s ability to detect exploits. You can prevent these prompts from occurring by configuring Group Policy settings.
Sandbox previewing environment Untrusted files are opened in a sandbox previewing environment known as Protected View. Users can read files in this sandbox environment, and they can copy content to the clipboard. However, they cannot print files or edit them. In most cases, previewing a document is sufficient for users and they can close the file without answering any security questions. For example, even if a file contains an untrusted Visual Basic for Applications (VBA) macro, a user does not have to enable the VBA macro to preview the content in Protected View.
In most cases, the default security configuration in Office 2010 is a suitable defense-in-depth solution, which provides multiple layers of defense without impinging too much on user productivity. However, some organizations might have to modify the default security configuration to meet more strict security requirements or to reduce security and provide more flexibility to users. For example, if the organization consists mostly of expert users who do not have to preview files in sandbox environment, you can disable Protected View. We do not recommend this (and it might be very risky), but it helps reduce the number of security decisions users make. Likewise, if the organization requires a locked-down security environment, you can modify the security settings so that all untrusted documents must be opened in Protected View and can never leave Protected View. This might provide more protection, but it also hinders a user’s ability to edit a file. Regardless of the organization’s particular security requirements, the multilayered countermeasures in Office 2010 let you effectively balance security and productivity; that is, you can increase or decrease the frequency and the kind of security decisions users have to make without completely compromising the security architecture.
Giving the administrator full control
Most large and mid-sized organizations use some centralized management tool, such as domain-based Group Policy settings, to deploy and manage their security configurations. Using domain-based Group Policy settings helps ensure that the computers in the organization have a consistent configuration and enables you to enforce the security configuration — two requirements of an effective security strategy. To that end, Office 2010 provides an expanded suite of Group Policy settings to help you effectively deploy and manage the security configuration.
The following table shows the different ways that you can manage the new security controls in Office 2010. It also shows which applications support the new security features.
|Security feature |Configurable in the Trust Center?|Configurable through Group Policy|Applies to which applications? |
| | |settings? | |
|Data Execution Prevention |Yes |Yes |All Office 2010 applications. |
|Office File Validation |No |Yes |Excel 2010 |
| | | |PowerPoint 2010 |
| | | |Word 2010 |
|File block settings |Yes |Yes |Excel 2010 |
| | | |PowerPoint 2010 |
| | | |Word 2010 |
|Office ActiveX kill bit |No |No (must be configured in the |Microsoft Access 2010 |
| | |registry) |Excel 2010 |
| | | |PowerPoint 2010 |
| | | |Microsoft Visio 2010 |
| | | |Word 2010 |
|Protected View |Yes |Yes |Excel 2010 |
| | | |PowerPoint 2010 |
| | | |Word 2010 |
|Trusted Documents |Yes |Yes |Access 2010 |
| | | |Excel 2010 |
| | | |PowerPoint 2010 |
| | | |Visio 2010 |
| | | |Word 2010 |
|Encryption (cryptographic agility) |No |Yes |Access 2010 |
|settings | | |Excel 2010 |
| | | |InfoPath 2010 |
| | | |OneNote 2010 |
| | | |PowerPoint 2010 |
| | | |Word 2010 |
|Time stamping of digital signatures|No |Yes |Excel 2010 |
| | | |InfoPath 2010 |
| | | |PowerPoint 2010 |
| | | |Word 2010 |
|Integrity checking of encrypted |No |Yes |Excel 2010 |
|files | | |PowerPoint 2010 |
| | | |Word 2010 |
|Password complexity and enforcement|No |Yes |Excel 2010 |
| | | |PowerPoint 2010 |
| | | |Word 2010 |
Migrating security and privacy settings from Office 2003
Office 2010 contains many security features that can help protect documents and help make desktops more secure. Some of these security features were introduced in the 2007 Office system, and have been enhanced in Office 2010. Other security features are new to Office 2010. If you are migrating to Office 2010 from Microsoft Office 2003 or an earlier version of Office, it might be helpful to understand when various Office 2010 security and privacy features were introduced.
The following table shows the main security and privacy features that were added or enhanced in the 2007 Office system and Office 2010.
|Security feature |Description |Feature status in|Feature status |For more information see… |
| | |the 2007 Office |in Office 2010 | |
| | |system | | |
|Trust Center |A central console in |Introduced in the|Enhanced and |Overview of security in the 2007 Office system |
| |the user interface that|2007 Office |expanded |() |
| |enables users to view |system |settings in | |
| |and configure security | |Office 2010 | |
| |settings and privacy | | | |
| |options. | | | |
|Message Bar |A user interface |Introduced in the|Enhanced the |Overview of security in the 2007 Office system |
| |element that gives |2007 Office |message bar user|() |
| |users notifications and|system |interface in | |
| |warnings when they open| |Office 2010 | |
| |a document that | | | |
| |contains potentially | | | |
| |harmful content. | | | |
|Trusted Locations |A security feature that|Introduced in the|No significant |Plan Trusted Locations and Trusted Publishers in the 2007 Office |
| |enables you to |2007 Office |changes in |system () |
| |differentiate safe and |system |Office 2010 | |
| |unsafe documents. | | | |
|File block settings |A suite of security |Introduced in the|Enhanced and |Plan block file format settings in the 2007 Office system |
| |settings that enable |2007 Office |expanded |() |
| |you to prevent users |system |settings in | |
| |from opening or saving | |Office 2010 | |
| |certain kinds of files.| | | |
|Document Inspector |A privacy tool that can|Introduced in the|Enhanced the |Overview of security in the 2007 Office system |
| |help users remove |2007 Office |user interface |() |
| |personal information |system |in Office 2010 | |
| |and hidden information | | | |
| |from a document. | | | |
|Global and |Enables you to disable |Introduced in the|No significant |Overview of security in the 2007 Office system |
|application-specific|all ActiveX controls, |2007 Office |functional |() |
|settings for ActiveX|configure ActiveX |system |changes in | |
|controls |control initialization,| |Office 2010 | |
| |and configure ActiveX | | | |
| |control prompts. | | | |
|Enhanced global and |Enables you to disable |Introduced in the|No significant |Overview of security in the 2007 Office system |
|application-specific|VBA and configure macro|2007 Office |functional |() |
|settings for VBA |warnings settings. |system |changes in | |
|macros | | |Office 2010 | |
|Application-specific|Enables you to disable |Introduced in the|No significant |Overview of security in the 2007 Office system |
|settings for add-ins|add-ins, require that |2007 Office |functional |() |
| |add-ins are signed by a|system |changes in | |
| |trusted publisher, and | |Office 2010 | |
| |configure add-in | | | |
| |warnings. | | | |
|Data Execution |A hardware and software|Not available in |Introduced in |Plan Data Execution Prevention settings for Office 2010 |
|Prevention (DEP) |technology that helps |2007 Office |Office 2010 | |
| |harden the attack |system | | |
| |surface by preventing |applications | | |
| |viruses and worms that | | | |
| |exploit buffer overflow| | | |
| |vulnerabilities. | | | |
|Office File |A countermeasure that |Not available in |Introduced in |Plan Office File Validation settings for Office 2010 |
|Validation |scans files for format |2007 Office |Office 2010 | |
| |differences and |system | | |
| |prevents files from |applications | | |
| |being opened for | | | |
| |editing if the format | | | |
| |is not valid. | | | |
|Office ActiveX kill |An Office feature that |Available in 2007|Introduced in |How to stop an ActiveX control from running in Internet Explorer |
|bit |administrators can use |Office system |Office 2010 as |() |
| |to prevent specific |applications as |an Office | |
| |ActiveX controls from |an Internet |ActiveX kill bit| |
| |running within Office |Explorer ActiveX | | |
| |applications. |kill bit | | |
|Protected View |An Office feature that |Not available in |Introduced in |Plan Protected View settings for Office 2010 |
| |helps mitigate attacks |2007 Office |Office 2010 | |
| |by enabling users to |system | | |
| |preview untrusted or |applications | | |
| |potentially harmful | | | |
| |files in a sandbox | | | |
| |environment. | | | |
|Trusted Documents |A security tool that |Not available in |Introduced in |Plan Trusted Documents settings for Office 2010 |
| |enables users to |2007 Office |Office 2010 | |
| |designate safe |system | | |
| |documents. |applications | | |
|Trusted time |Helps ensure that |Not available in |Introduced in |Plan digital signature settings for Office 2010 |
|stamping of digital |digital signatures |2007 Office |Office 2010 | |
|signatures |remain valid and |system | | |
| |legally defensible even|applications | | |
| |if the certificate that| | | |
| |you used to sign the | | | |
| |document expires. | | | |
|Integrity checking |Enables you to |Not available in |Introduced in |Plan cryptography and encryption settings for Office |
|of encrypted files |implement a hash-based |2007 Office |Office 2010 | |
| |message authentication |system | | |
| |code (HMAC) when a file|applications | | |
| |is encrypted. | | | |
|Password complexity |Enables you to check |Not available in |Introduced in |Plan password complexity settings for Office 2010 |
|checking and |and enforce passwords |2007 Office |Office 2010 | |
|enforcement |for length and |system | | |
| |complexity by using |applications | | |
| |domain-based password | | | |
| |policies. | | | |
|Cryptographic |Enables you to specify |Not available in |Introduced in |Plan cryptography and encryption settings for Office 20 |
|agility |cryptographic settings |2007 Office |Office 2010 | |
| |for encrypting |system | | |
| |documents. |applications | | |
Understand security threats and countermeasures for Office 2010
A secure desktop configuration is an important part of any organization's defense-in-depth strategy. But before you can plan for a secure desktop configuration that includes Microsoft Office 2010, you must understand which security risks and threats are relevant to Office 2010, and then determine which of those security risks and threats pose a risk to the organization's business assets or business processes. You also have to determine which privacy risks and threats pose a risk to users' personal and private information.
In this article:
• Information security risks
• Threats to desktop productivity applications
• Default countermeasures in Office 2010
Information security risks
Most IT professionals and IT security specialists categorize information security risks into three broad categories:
• Confidentiality risks These risks represent threats to an organization’s intellectual property from unauthorized users and malicious code that attempt to access what is said, written, and created in an organization.
• Integrity risks These risks represent threats to your business resources from unauthorized users and malicious code that attempt to corrupt the business data on which your organization relies. Integrity risks jeopardize any business asset that contains critical information for an organization, such as database servers, data files, and e-mail servers.
• Availability risks These risks represent threats to business processes by unauthorized users and malicious code that attempt to disrupt the way that you do business and how information workers complete their work. Business intelligence processes, application features and capabilities, and document workflow processes can all be threatened by availability risks.
To help ensure that your organization is protected from all three of these risk categories, a defense-in-depth security strategy is recommended; that is, a security strategy that includes multiple overlapping layers of defense against unauthorized users and malicious code. Layers typically include the following:
• Perimeter network protection, such as firewalls and proxy servers.
• Physical security measures, such as physically secure data centers and server rooms.
• Desktop security tools, such as personal firewalls, virus scanning programs, and spyware detection.
If Office 2010 is part of an organization’s environment, the defense-in-depth strategy must also include the mitigation mechanisms that are provided with Office 2010. These mitigation mechanisms include many technologies, settings, and features. By using these mechanisms, you can help mitigate threats to Office 2010 applications and help protect the intellectual property, business resources, and business processes that are at the heart of the business.
By default, the Office 2010 security model helps an organization mitigate all three kinds of risk. However, every organization has different infrastructure capabilities, different productivity demands, and different desktop security requirements. To determine exactly how the organization can mitigate these business risks, you have to evaluate the threats and threat agents that exploit these risks.
Threats to desktop productivity applications
The security model for Office 2010 helps you mitigate five kinds of productivity software security threats. Each of these threat types include several threat agents, which can be exploited by various security attacks. The following illustration shows the security threats and examples of the most common threat agents.
[pic]
Most organizations face some potential risk from five kinds of security threats. However, most organizations deal with unique combinations of threat agents and potential security attacks or exploits.
Active content threats
Active content threats are common desktop security threats. Typical threat agents include ActiveX controls, add-ins, and VBA macros. These threat agents can be exploited by programmers who write malicious code or create malicious programs, which then run on users' computers. Active content threats pose a potential risk to any size organization, especially organizations that let users do the following:
• Run ActiveX controls, add-ins, or VBA macros.
• Open e-mail attachments.
• Share documents across a public network, such as the Internet.
• Open documents from sources outside the organization, such as clients, vendors, or partners.
Unauthorized access threats
Unauthorized access threats occur when unauthorized users attempt to gain access to information. Potential targets of unauthorized users include the following:
• Document files If unauthorized users gain access to document files, they can delete, replace, or corrupt the files. For example, a malicious programmer might use a file format attack to exploit an unauthorized access threat in a document.
• Information within documents This information includes text, graphics, comments, revisions, annotations, custom XML data, hidden text, watermarks and header and footer information. When unauthorized users access the information within documents, they might access sensitive data, such as company confidential data, and personal or private information about users. They can also alter, corrupt, or delete information, and they can use their access to add active content to documents saved in trusted locations.
• Metadata Information associated with documents, including document properties such as author name, organization name, document editing time, or document version number. Unauthorized users who gain access to metadata might access sensitive personal or company data. They can also corrupt or remove metadata.
Most organizations face unauthorized access threats, although many organizations do not take sufficient measures to mitigate them because they perceive the threat to be minimal or consider the administrative cost for mitigating the threat excessive. These perceptions could lead to unsafe practices and circumstances such as the following:
• The organization's network security architecture cannot prevent an intruder or attacker from gaining access to your internal network, which increases the risk that an intruder or attacker might gain access to your organization's documents.
• The organization lets users send, receive, or share proprietary documents over the Internet, including financial data, project plans, presentations, or drawings.
• The organization does not prevent users from connecting portable computers to public networks, which increases the risk that an unidentifiable attacker might gain access to the documents that are saved on those portable computers.
• The organization does not prevent users from taking documents that contain proprietary information out of the office.
• There is a chance that an unauthorized attacker or intruder can gain access to documents that contain proprietary information.
External content threats
External content threats include any threat agent that links a document to another document, a database, or a Web site across an intranet or a public network, such as the Internet. External content threats are exploited through the following threat agents:
• Hyperlinks An attacker typically exploits this threat agent by creating hyperlinks to documents that are not trusted or Web sites that contain malicious code or content.
• Data connections An attacker typically exploits this threat agent by creating data connections to data sources or databases, and then by using such connections to maliciously manipulate or extract data.
• Web beacons A typical scenario for exploiting this threat agent is for an attacker to embed an invisible link to a remote image in an e-mail message. When a user opens the message, the link becomes active and downloads the remote image. In the process, user information can be sent to the remote computer, such as the user's e-mail address and the IP address of their computer.
• Packager objects An attacker can exploit this threat agent by having an embedded object run malicious code.
External threats pose a risk if the organization:
• Gives users unrestricted access to public networks, such as the Internet.
• Does not prevent users from receiving e-mail messages that contain embedded images and HTML.
• Does not prevent users from using data connections in spreadsheets or other documents.
Browser threats
These threats can exist when an application or a document programmatically uses the functionality of a Web browser, such as Microsoft Internet Explorer. Browser threats pose a risk to applications and documents because any threats that exist for the browser also exist for the application or document that hosts the browser. Browser threats include many threat agents, and can be exploited through various security attacks. Examples of these threat agents include ActiveX control installation, file downloads, MIME sniffing, zone elevation, and add-on installation.
Browser threats pose a risk if your organization:
• Allows users to run ActiveX controls, add-ins, or macros that use browser functionality.
• Develops and distributes Office solutions that use browser functionality.
Zero-day exploit threats
Zero-day exploits can be launched when a security vulnerability is found that has not yet been addressed by a software update, such as a Microsoft security bulletin or service pack. Zero-day exploits can take several forms, including the following:
• Remote code execution
• Elevation of privilege
• Information disclosure
Malicious programmers and users can exploit security vulnerabilities through various security attacks. Until a security bulletin or a service pack is released to respond to the security vulnerability, the vulnerability can pose a potential threat to your organization.
Default countermeasures in Office 2010
Office 2010 provides many countermeasures that help mitigate threats to your business assets and business processes. A countermeasure is a security feature or a security control that mitigates one or more security threats. You can usually change the behavior of countermeasures by configuring settings in the Office Customization Tool (OCT) or through Group Policy by using the Office 2010 Administrative Templates.
Many of the countermeasures in Office 2010 mitigate a specific kind of threat in one particular application. For example, Microsoft InfoPath 2010 includes a countermeasure that warns users about the possible presence of Web beacons in forms. You can change the behavior of this countermeasure by configuring the Beaconing UI for forms opened in InfoPath setting in the OCT or through Group Policy.
Other countermeasures mitigate broader kinds of threats that are common to several applications. For example, the Protected View feature enables users to view the content of untrusted documents, presentations, and workbooks without enabling unsafe content or malicious code to harm the computer. This countermeasure is used by Microsoft Excel 2010, Microsoft PowerPoint 2010, Microsoft Word 2010, and Microsoft Outlook 2010 when you preview attachments for Excel 2010, PowerPoint 2010, Microsoft Visio 2010, and Word 2010. You can change its behavior by configuring several settings in the OCT or through Group Policy.
The following sections describe the most frequently used countermeasures in Office 2010.
ActiveX control settings
You can use ActiveX control settings to disable ActiveX controls and change the way ActiveX controls are loaded into Office 2010 applications. By default, trusted ActiveX controls are loaded in safe mode with persistent values and users are not notified that the ActiveX controls loaded. Untrusted ActiveX controls load differently depending on how the ActiveX control is marked and whether a VBA project exists in the file together with the ActiveX control. The default behavior of untrusted ActiveX controls is as follows:
• If an ActiveX control is marked Safe for Initialization (SFI) and it is contained in a document that does not contain a VBA project, the ActiveX control is loaded in safe mode with persistent values. The Message Bar does not appear and users are not notified about the presence of the ActiveX control. All ActiveX controls in the document must be marked SFI for this behavior to occur.
• If an ActiveX control is marked Unsafe for Initialization (UFI) and it is contained in a document that does not contain a VBA project, users are notified in the Message Bar that ActiveX controls are disabled. However, users can click the Message Bar to enable ActiveX controls. If a user enables ActiveX controls, all ActiveX controls (those marked UFI and SFI) are loaded in safe mode with persistent values.
• If an ActiveX control marked UFI or SFI is contained in a document that also contains a VBA project, users are notified in the Message Bar that ActiveX controls are disabled. However, users can click the Message Bar to enable ActiveX controls. If a user enables ActiveX controls, all ActiveX controls (those marked SFI and UFI) are loaded in safe mode with persistent values.
[pic]Important:
If a kill bit is set in the registry for an ActiveX control, the control is not loaded and cannot be loaded in any circumstance. The Message Bar does not appear and users are not notified about the presence of the ActiveX control.
To change the default behavior of ActiveX controls, see Plan security settings for ActiveX controls for Office 2010.
Add-in settings
You can use add-in settings to disable add-ins, require add-ins be signed by a trusted publisher, and disable notifications for add-ins. By default, installed and registered add-ins can run without requiring user intervention or warning. To change this default behavior, see Plan security settings for add-ins for Office 2010.
Cryptography and encryption settings
These settings will be available when Office 2010 is officially released.
Data Execution Prevention settings
You can use Data Execution Prevention (DEP) settings to disable DEP in Office 2010 applications. DEP is a hardware and software countermeasure that helps prevent malicious code from running. By default, DEP is enabled in Office 2010 applications and we recommend that you do not change this default setting. For more information about DEP settings, see Security policies and settings in Office 2010.
Digital signature settings
These settings will be available when Office 2010 is officially released.
External content settings
You can use external content settings to change the way Office 2010 applications access external content. External content is any kind of content that is accessed remotely, such as data connections and workbook links, hyperlinks to Web sites and documents, and links to images and media. By default, when a user opens a file that contains links to external content, the Message Bar notifies the user that the links are disabled. Users can enable the links by clicking the Message Bar. We recommend that you do not change these default settings. For more information about external content settings, see Security policies and settings in Office 2010.
File Block settings
You can use File Block settings to prevent specific file types from being opened or saved. You can also use these settings to prevent or force certain file types from opening in Protected View. By default, Excel 2010, PowerPoint 2010, and Word 2010 force several kinds of files to open only in Protected View. Users cannot open these file types for editing. For more information about File Block settings, including information about the file types that are blocked by default, see Plan File Block settings for Office 2010.
Office File Validation settings
You can use Office File Validation settings to disable the Office File Validation feature and change how the Office File Validation feature handles files that do not pass validation. You can also use these settings to prevent the Office File Validation feature from prompting users to send validation information to Microsoft. By default, the Office File Validation feature is enabled. Files that do not pass validation are opened in Protected View and users can edit files after they are opened in Protected View. For more information about Office File Validation settings, see Plan Office File Validation settings for Office 2010.
Password complexity settings
You can use password complexity settings to enforce password length and complexity for passwords that are used with the Encrypt with Password feature. Password complexity settings let you enforce password length and complexity at the domain level if the organization has established password complexity rules through domain-based Group Policy, or at a local level if the organization has not implemented domain-based password complexity Group Policy. By default, Office 2010 applications do not check password length or complexity when a user encrypts a file by using the Encrypt with Password feature. For more information about password complexity settings, see Plan password complexity settings for Office 2010.
Privacy options
You can use privacy options to prevent the Welcome to Microsoft Office 2010 dialog box from appearing the first time that a user starts Office 2010. This dialog box lets users enroll in various Internet-based services that help protect and improve Office 2010 applications. You can also use privacy options to enable the Internet-based services that appear in the Welcome to Microsoft Office 2010 dialog box. By default, the Welcome to Microsoft Office 2010 dialog box appears when a user starts Office 2010 for the first time, and users can enable the recommended Internet-based services, enable a subset of these services, or make no configuration changes. If a user makes no configuration changes, the following default settings take effect:
• Office 2010 applications do not connect to for updated Help content.
• Office 2010 applications do not download small programs that help diagnose problems and error message information is not sent to Microsoft.
• Users are not enrolled in the Customer Experience Improvement Program.
• When users implement a search query from the Help system, information about which Office 2010 applications are installed is not sent to Microsoft to improve search results.
To change this default behavior, or to suppress the Welcome to Microsoft Office 2010 dialog box, see Plan privacy options for Office 2010.
Protected View settings
You can use Protected View settings to prevent files from opening in Protected View and force files to open in Protected View. You can also specify whether you want scripts and programs that run in Session 0 to open in Protected View. By default, Protected View is enabled and all untrusted files open in Protected View. Scripts and programs running in Session 0 do not open in Protected View. For more information about Protected View settings, see Plan Protected View settings for Office 2010.
[pic]Note:
You can also use File Block settings to prevent or force specific file types from opening in Protected View.
Trusted Documents settings
You can use Trusted Documents settings to disable the Trusted Documents feature and prevent users from trusting documents that are stored on network shares. Trusted documents bypass most security checks when they are opened and all active content is enabled (antivirus checking and ActiveX kill-bit checking are the two checks that cannot be bypassed). By default, the Trusted Documents feature is enabled, which means users can designate safe files as trusted documents. In addition, users can designate files on network shares as trusted documents. We recommend that you do not change these default settings. For more information about Trusted Documents settings, see Security policies and settings in Office 2010.
Trusted Locations settings
You can use Trusted Locations settings to designate safe locations for files. Files that are stored in trusted locations bypass most security checks when they are opened and all content in the file is enabled (antivirus checking and ActiveX kill-bit checking are the two checks that cannot be bypassed). By default, several locations are designated as trusted locations. Also, trusted locations that are on a network, such as shared folders, are disabled. To change this default behavior, and find out which locations are designated as trusted locations by default, see Plan Trusted Locations settings for Office 2010.
Trusted Publishers settings
You can use Trusted Publishers settings to designate certain kinds of active content as being safe, such as ActiveX controls, add-ins, and VBA macros. When a publisher signs active content with a digital certificate, and you add the publisher’s digital certificate to the Trusted Publishers list, the active content is considered trusted. By default, there are no publishers on the Trusted Publishers list. You must add publishers to the Trusted Publishers list in order to implement this security feature. To implement the Trusted Publishers feature, see Plan Trusted Publishers settings for Office 2010.
VBA macro settings
You can use VBA macro settings to change the way VBA macros behave, disable VBA, and change the way VBA macros behave in applications that are started programmatically. By default, VBA is enabled and trusted VBA macros are allowed to run without notification. Trusted VBA macros include VBA macros that are signed by a trusted publisher, stored in a trusted document, or stored in a document that is in a trusted location. Untrusted VBA macros are disabled, but a notification in the Message Bar lets users enable untrusted VBA macros. In addition, VBA macros are allowed to run in applications that are started programmatically.
To change this default behavior, see Plan security settings for VBA macros for Office 2010.
See Also
Security overview for Office 2010
Plan Protected View settings for Office 2010
If you want to change how the sandbox preview feature in Microsoft Office 2010 behaves, you can configure Protected View settings. Protected View is a new security feature in Office 2010 that helps mitigate exploits to your computer by opening files in a restricted environment so they can be examined before they are opened for editing in Microsoft Excel 2010, Microsoft PowerPoint 2010, or Microsoft Word 2010.
In this article:
• About planning Protected View settings
• Prevent files from opening in Protected View
• Force files to open in Protected View
• Add files to the list of unsafe files
About planning Protected View settings
Protected View helps mitigate several kinds of exploits by opening documents, presentations, and workbooks in a sandbox environment. A sandbox is a piece of computer memory or a specific computer process that is isolated from certain operating system components and applications. Because of this isolation, programs and processes that run in a sandbox environment are considered less dangerous. Sandbox environments are frequently used to test new applications and services that might make a computer unstable or fail. Sandbox environments are also used to prevent applications and processes from harming a computer.
When a file is opened in Protected View, users can view the file content but they cannot edit, save, or print the file content. Active file content, such as ActiveX controls, add-ins, database connections, hyperlinks, and Visual Basic for Applications (VBA) macros, is not enabled. Users can copy content from the file and paste it into another document. In addition, Protected View prevents users from viewing the details of digital signatures that are used to sign a document, presentation, or workbook.
Default behavior of Protected View
By default, Protected View is enabled in Excel 2010, PowerPoint 2010, and Word 2010. However, files open in Protected View only under certain conditions. In some cases, files bypass Protected View and are opened for editing. For example, files that are opened from trusted locations and files that are trusted documents bypass several security checks and are not opened in Protected View.
By default, files open in Protected View if any one of the following conditions is true:
• A file skips or fails Office File Validation Office File Validation is a new security feature that scans files for file format exploits. If Office File Validation detects a possible exploit or some other unsafe file corruption, the file opens in Protected View.
• AES zone information determines that a file is not safe Attachment Execution Services (AES) adds zone information to files that are downloaded by Microsoft Outlook or Microsoft Internet Explorer. If a file’s zone information indicates that the file originated from an untrusted Web site or the Internet, the downloaded file opens in Protected View.
• A user opens a file in Protected View Users can open files in Protected View by selecting Open in Protected View in the Open dialog box, or by holding down the SHIFT key, right-clicking a file, and then selecting Open in Protected View.
• A file is opened from an unsafe location By default, unsafe locations include the user’s Temporary Internet Files folder and the downloaded program files folder. However, you can use Group Policy settings to designate other unsafe locations.
In some cases, Protected View is bypassed even if one or more of the previously listed conditions are met. Specifically, files do not open in Protected View if any one of the following is true:
• A file is opened from a trusted location.
• A file is considered a trusted document.
Change Protected View behavior
We recommend that you do not change the default behavior of Protected View. Protected View is an important part of the layered defense strategy in Office 2010, and is designed to work with other security features such as Office File Validation and File Block. However, we recognize that some organizations might have to change Protected View settings to suit special security requirements. To that end, Office 2010 provides several settings that let you change how the Protected View feature behaves. You can use these settings to do the following:
• Prevent files that are downloaded from the Internet from opening in Protected View.
• Prevent files that are stored in unsafe locations from opening in Protected View.
• Prevent attachments opened in Microsoft Outlook 2010 from opening in Protected View.
• Add locations to the list of unsafe locations.
In addition, you can use File Block settings and Office File Validation settings to force files to open in Protected View. For more information, see Force files to open in Protected View later in this article.
[pic]Note:
For detailed information about the settings that are discussed in this article, see Security policies and settings in Office 2010. For information about how to configure security settings in the Office Customization Tool (OCT) and the Office 2010 Administrative Templates, see Configure security for Office 2010.
Prevent files from opening in Protected View
You can change Protected View settings so that certain files bypass Protected View. To do so, enable the following settings:
Do not open files from the Internet zone in Protected View This setting forces files to bypass Protected View if the AES zone information indicates that the file was downloaded from the Internet zone. This setting applies to files that are downloaded by using Internet Explorer, Outlook Express, and Outlook.
Do not open files in unsafe locations in Protected View This setting forces files to bypass Protected View if the files are opened from an unsafe location. You can add folders to the unsafe locations list by using the Specify list of unsafe locations setting, which is discussed later in this article.
Turn off Protected View for attachments opened in Outlook This setting forces Excel 2010. PowerPoint 2010, and Word 2010 files that are opened as Outlook 2010 attachments to bypass Protected View.
These settings do not apply if File Block settings force the file to open in Protected View. Also, these settings do not apply if a file fails Office File Validation. You can configure each of these settings on a per-application basis for Excel 2010, PowerPoint 2010, and Word 2010.
Force files to open in Protected View
The File Block and Office File Validation features have settings that let you force files to open in Protected View when certain conditions are met. You can use these settings to determine the circumstances under which files open in Protected View.
Use File Block to force files to open in Protected View
The File Block feature lets you prevent users from opening or saving certain file types. When you use File Block settings to block a file type, you can choose one of three file block actions:
• Blocked and not allowed to open.
• Blocked and opened only in Protected View (users cannot enable editing).
• Blocked and opened in Protected View (users can enable editing).
By selecting the second or third option, you can force blocked file types to open in Protected View. You can configure File Block settings only on a per-application basis for Excel 2010, PowerPoint 2010, and Word 2010. For more information about File Block settings, see Plan File Block settings for Office 2010.
Use Office File Validation settings to force files to open in Protected View
Office File Validation is a new security feature that scans files for file format exploits before they are opened by an Office 2010 application. By default, files that fail Office File Validation are opened in Protected View and users can enable editing after previewing the file in Protected View. However, you can use the Set document behavior if file validation fails setting to change this default behavior. You can use this setting to select one of three possible options for files that fail Office File Validation:
• Block completely Files that fail Office File Validation cannot be opened in Protected View or opened for editing.
• Open in Protected View and disallow editing Files that fail Office File Validation are opened in Protected View but users cannot edit the files.
• Open in Protected View and allow editing Files that fail Office File Validation are opened in Protected View and users are allowed to edit the files. This is the default.
By selecting the second option, you can restrict Protected View behavior for files that fail Office File Validation. You can configure this Office File Validation setting only on a per-application basis for Excel 2010, PowerPoint 2010, and Word 2010. For more information about Office File Validation settings, see Plan Office File Validation settings for Office 2010.
Add files to the list of unsafe files
You can use the Specify list of unsafe locations setting to add locations to the unsafe locations list. Files that are opened from unsafe locations are always opened in Protected View. The unsafe locations feature does not prevent users from editing a document; it only forces a document to open in Protected View before it is edited. This is a global setting that applies to Excel 2010, PowerPoint 2010, and Word 2010.
See Also
Security overview for Office 2010
Understand security threats and countermeasures for Office 2010
Plan Office File Validation settings for Office 2010
Plan Office File Validation settings for Office 2010
If you want to change how Microsoft Office 2010 validates files that are stored in Microsoft Office binary file formats, you can configure Office File Validation settings. Office File Validation is a new security feature in Office 2010 that helps prevent file format attacks by scanning Office binary file formats before they are opened in Microsoft Excel 2010, Microsoft PowerPoint 2010, or Microsoft Word 2010.
In this article:
• About planning Office File Validation settings
• Turn off Office File Validation
• Change document behavior when validation fails
• Turn off Office File Validation reporting
About planning Office File Validation settings
Office File Validation helps detect and prevent a kind of exploit known as a file format attack or file fuzzing attack. File format attacks exploit the integrity of a file, and they occur when someone modifies the structure of a file with the intent of adding malicious code. Usually the malicious code is run remotely and is used to elevate the privilege of restricted accounts on the computer. As a result, an attacker could gain access to a computer that they did not previously have access to. This could enable an attacker to read sensitive information from the computer’s hard disk drive or install malware, such as a worm or a key logging program. The Office File Validation feature helps prevent file format attacks by scanning and validating files before they are opened. To validate files, Office File Validation compares a file’s structure to a predefined file schema, which is a set of rules that determine what a readable file looks like. If Office File Validation detects that a file’s structure does not follow all of the rules described in the schema, the file does not pass validation.
File format attacks occur most frequently in files that are stored in Office binary file formats. For this reason, Office File Validation scans and validates the following kinds of files:
• Excel 97-2003 Workbook files. These files have an .xls extension and include all Binary Interchange File Format 8 (BIFF8) files.
• Excel 97-2003 Template files. These files have an .xlt extension and include all BIFF8 files.
• Microsoft Excel 5.0/95 files. These files have an .xls extension and include all BIFF5 files.
• PowerPoint 97-2003 Presentation files. These files have a .ppt extension.
• PowerPoint 97-2003 Show files. These files have a .pps extension.
• PowerPoint 97-2003 Template files. These files have a .pot extension.
• Word 97-2003 Document files. These files have a .doc extension.
• Word 97-2003 Template files. These files have a .dot extension.
Office 2010 provides several settings that let you change how the Office File Validation feature behaves. You can use these settings to do the following:
• Disable Office File Validation.
• Specify document behavior when a file fails validation.
• Prevent Office 2010 from sending Office File Validation information to Microsoft.
[pic]Note:
For detailed information about the settings that are discussed in this article, see Security policies and settings in Office 2010. For information about how to configure security settings in the Office Customization Tool (OCT) and the Office 2010 Administrative Templates, see Configure security for Office 2010.
By default, Office File Validation is enabled in Excel 2010, PowerPoint 2010, and Word 2010. Any files that fail validation are opened in Protected View and users can choose to enable editing for files that fail validation but are opened in Protected View. Also, users are prompted to send Office File Validation information to Microsoft. Information is collected only for files that fail validation.
We recommend that you do not change the default settings for Office File Validation. However, some organizations might have to configure Office File Validation settings to suit special security requirements. Specifically, organizations that have the following security requirements might have to change the default settings for the Office File Validation feature:
• Organizations that restrict access to the Internet. Office File Validation prompts users to send validation error information to Microsoft approximately every two weeks. This could violate an organization’s Internet access policies. In this case, you might need to prevent Office File Validation from sending the information to Microsoft. For more information, see Turn off Office File Validation reporting later in this article.
• Organizations that have highly restrictive security environments. You can configure Office File Validation so that files that fail validation cannot be opened or can only be opened in Protected View. This is a more restrictive than the default settings for Office File Validation and might be suitable to organizations that have a locked-down security environment. For more information about how to change document behavior, see Change document behavior when validation fails later in this article.
• Organizations that do not want their files sent to Microsoft. If users allow it, Office File Validation sends a copy of all files that fail validation to Microsoft. You can configure Office File Validation so that users are not prompted to send validation information to Microsoft.
Turn off Office File Validation
You can use the Turn off file validation setting to disable Office File Validation. This setting must be configured on a per-application basis for Excel 2010, PowerPoint 2010, and Word 2010. This setting prevents files that are stored in the Office binary file format from being scanned and validated. For example, if you enable the Turn off file validation setting for Excel 2010, Office File Validation does not scan or validate Excel 97-2003 Workbook files, Excel 97-2003 Template files, or Microsoft Excel 5.0/95 files. If a user opens one of those file types, and the file contains a file format attack, the attack will not be detected or prevented unless some other security control detects and prevents such an attack.
We recommend that you do not turn off Office File Validation. Office File Validation is a key part of the layered defense strategy in Office 2010 and should be enabled on all computers throughout an organization. If you want to prevent files from being validated by the Office File Validation feature, we recommend that you use the Trusted Locations feature. Files that are opened from trusted locations skip Office File Validation checks. You can also use the Trusted Documents feature to prevent a file from being validated by Office File Validation. Files that are considered to be trusted documents do not undergo Office File Validation checks.
Change document behavior when validation fails
You can use the Set document behavior if file validation fails setting to change how documents behave when they fail validation. When you enable this setting, you can select one of the following three options:
• Block files completely Files that fail validation do not open in Protected View and users cannot open files for editing.
• Open files in Protected View and disallow edit Files open in Protected View so users can see the content of the file, but users cannot open files for editing.
• Open files in Protected View and allow edit Files open in Protected View and users can choose to open files for editing. This option represents the default behavior of the Office File Validation feature.
If you select the Open files in Protected View and disallow edit option, users see the following text in the Message Bar when a file fails validation:
Protected View Office has detected a problem with this file. Editing it may harm your computer. Click for more details.
If a user clicks the Message Bar, the Microsoft Office Backstage view appears, which provides a more lengthy description of the problem and lets users enable the file for editing.
If you select the Block files completely option, users see the following text in a dialog box when a file fails validation:
Office has detected a problem with this file. To help protect your computer this file cannot be opened.
Users can expand the dialog box and see a more detailed explanation of why the file does not open, or they can close the dialog box by clicking OK.
Turn off Office File Validation reporting
You can use the Turn off error reporting for files that fail file validation setting to suppress the dialog box that prompts users to send information to Microsoft. This setting also prevents validation information from being sent to Microsoft.
Every time that a file fails validation, Office 2010 collects information about why the file failed validation. Approximately two weeks after a file fails validation, Office 2010 prompts users to send Office File Validation information to Microsoft. The validation information includes such things as the file types, file sizes, how long it took to open the files, and how long it took to validate the files. Copies of the files that failed validation are also sent to Microsoft. Users see the list of files when they are prompted to send validation information to Microsoft. Users can decline to send validation information to Microsoft, which means no information about failed validations is sent to Microsoft and no files are sent to Microsoft. If an organization restricts Internet access, has restrictive Internet access policies, or does not want files sent to Microsoft, you might have to enable the Turn off error reporting for files that fail file validation setting.
[pic]Important:
The Office File Validation feature can occasionally indicate that a file failed validation when in fact the file is valid. The validation reporting feature helps Microsoft improve the Office File Validation feature and minimize the occurrence of false positive results.
See Also
Security overview for Office 2010
Plan security settings for add-ins for Office 2010
If you want to control the way add-ins behave, or prevent users from running add-ins, you can modify Microsoft Office 2010 add-in settings.
In this article:
• About planning add-in settings
• Disable add-ins on a per-application basis
• Require that application add-ins are signed by trusted publisher
• Disable notifications for unsigned add-ins
About planning add-in settings
Microsoft Office 2010 provides several settings that enable you to control the behavior of add-ins. By configuring these settings, you can do the following:
• Disable add-ins on a per-application basis.
• Require that add-ins are signed by a trusted publisher.
• Disable notifications for unsigned add-ins.
Add-in settings can be configured only on a per-application basis. There are no global add-in settings.
For detailed information about the settings that are discussed in this article, see Security policies and settings in Office 2010. For information about how to configure security settings in the Office Customization Tool (OCT) and the Office 2010 Administrative Templates, see Configure security for Office 2010.
By default, any add-in that is installed and registered can run without user intervention or warning. Installed and registered add-ins can include the following:
• Component Object Model (COM) add-ins
• Visual Studio Tools for Office (VSTO) add-ins
• Automation add-ins
• RealTimeData (RTD) servers
• Application add-ins (for example, .wll, .xll, and .xlam files)
• XML expansion packs
• XML style sheets
This default behavior is the same as selecting the Trust all installed add-ins and templates setting in Microsoft Office 2003 or an earlier Microsoft Office system.
Disable add-ins on a per-application basis
Office 2010 provides a setting that enables you to disable add-ins. Use the following guidelines to determine whether to use this setting.
Setting name: Disable all application add-ins
Description: This setting disables all add-ins. By default, all installed and registered add-ins can run.
Impact: If you enable this setting, add-ins are disabled and users are not notified that add-ins are disabled. Enabling this setting could cause significant disruptions for users who work with add-ins. If users have business-critical add-ins installed, you might be unable to enable this setting.
Guidelines: Most organizations use the default configuration for this setting and do not change this setting.
Require that application add-ins are signed by trusted publisher
Office 2010 provides a setting that enables you to require that all add-ins be signed by a trusted publisher. Use the following guidelines to determine whether to use this setting.
Setting name: Require that application add-ins are signed by trusted publisher
Description: This setting controls whether add-ins must be digitally signed by a trusted publisher. By default, the publisher of an add-in does not have to be on the Trusted Publishers list for an add-in to run.
Impact: When you enable this setting, add-ins that are signed by a publisher that is on the Trusted Publishers list will run without notification. Unsigned add-ins and add-ins that are signed by a publisher that is not on the Trusted Publishers list will be disabled. But users are prompted to enable the add-ins. Enabling this setting could cause disruptions for users who rely on add-ins that are not signed by trusted publishers. These users will either have to obtain signed versions of such add-ins or stop using them.
Guidelines: Organizations that have a highly restrictive security environment typically enable this setting.
Disable notifications for unsigned add-ins
Office 2010 provides a setting that enables you to prevent users from seeing Message Bar warnings when unsigned add-ins are not able to run. Use the following guidelines to determine whether to use this setting.
Setting name: Disable Trust Bar Notification for unsigned application add-ins
Description: This setting controls whether to notify users when unsigned application add-ins are loaded or silently disable such add-ins without notification. By default, a warning appears in the Message Bar when an unsigned add-in attempts to run.
Impact: If you enable this setting, users will not see a warning in the Message Bar when an unsigned add-in attempts to run and users will be unable to enable the unsigned add-in. Enabling this setting could cause disruptions for users who rely on add-ins that are not signed by trusted publishers. These users will either have to obtain signed versions of such add-ins or stop using them.
Guidelines: Organizations that have a highly restrictive security environment typically enable this setting if they require all add-ins be signed by a trusted publisher.
See Also
Security overview for Office 2010
Plan security settings for VBA macros for Office 2010
If you want to control the way Visual Basic for Applications (VBA) and VBA macros behave, you can modify Microsoft Office 2010 VBA and VBA macros settings for the following applications: Microsoft Access 2010, Microsoft Excel 2010, Microsoft PowerPoint 2010, Microsoft Publisher 2010, Microsoft Visio 2010, and Microsoft Word 2010.
In this article:
• About planning VBA and VBA macro settings
• Change the security warning settings for VBA macros
• Disable VBA
• Change how VBA macros behave in applications that are started programmatically
• Change how encrypted VBA macros are scanned for viruses
• Related VBA macro settings
About planning VBA and VBA macro settings
Office 2010 provides several settings that enable you to control the behavior of VBA and VBA macros. By configuring these settings, you can do the following:
• Change the security warning settings for VBA macros. This includes disabling VBA macros, enabling all VBA macros, and changing the way that users are notified about VBA macros.
• Disable VBA.
• Change how VBA macros behave in applications that are started programmatically through Automation.
• Change how antivirus software scans encrypted VBA macros.
For detailed information about the settings that are discussed in this article, see Security policies and settings in Office 2010. For information about how to configure security settings in the Office Customization Tool (OCT) and the Office 2010 Administrative Templates, see Configure security for Office 2010.
By default, VBA is enabled and trusted VBA macros are allowed to run. This includes VBA macros in documents that are saved in a trusted location, VBA macros in trusted documents, and VBA macros that meet the following criteria:
• The macro is signed by the developer with a digital signature.
• The digital signature is valid.
• This digital signature is current (not expired).
• The certificate associated with the digital signature was issued by a reputable certification authority (CA).
• The developer who signed the macro is a trusted publisher.
[pic]Note:
The default security setting for macros is different in Microsoft Outlook 2010. For more information, see the Outlook 2010 security documentation.
VBA macros that are not trusted are not allowed to run until a user clicks the Message Bar and selects to enable the VBA macro.
Change the security warning settings for VBA macros
Office 2010 provides a setting that enables you to change the security warning settings and the behavior of VBA macros. Use the following guidelines to determine how to configure this setting if you want to change how users are notified about untrusted VBA macros or change the default behavior of VBA macros.
Setting name: VBA macro warning settings
Description: This setting controls how applications warn users about Visual Basic for Applications (VBA) macros. You configure this setting on a per-application basis for Access 2010, Excel 2010, PowerPoint 2010, Publisher 2010, Visio 2010, and Word 2010. You can select one of four possible options for this setting:
Trust Bar warning for all macros The application displays the Message Bar for all macros, whether signed or unsigned. This is the default setting.
Trust Bar warning for digitally signed macros only (unsigned macros will be disabled) The application displays the Message Bar for digitally signed macros. This allows users to enable them or leave them disabled. Any unsigned macros are disabled, and users are not notified or given the ability to enable the unsigned macros.
No warnings for all macros but disable all macros The application disables all macros, whether signed or unsigned, and does not notify users.
No security checks for macros (Not recommended) All macros are enabled, whether signed or unsigned. This option can significantly reduce security by letting dangerous code to run undetected.
Impact: If you enable this setting and select the Trust Bar warning for digitally signed macros only (unsigned macros will be disabled) option, documents and templates that contain unsigned macros lose all functionality supplied by those macros. To prevent this loss of functionality, users can put files that contain macros in a trusted location.
[pic]Important:
If Trust bar warning for digitally signed macros only (unsigned macros will be disabled) is selected, users cannot open unsigned Access 2010 databases.
If you select No warnings for all macros but disable all macros, documents and templates that contain unsigned and signed macros lose all functionality supplied by those macros. This is true even if a macro is signed and the publisher is listed in the Trusted Publisher list.
Guidelines: Organizations that have a highly restrictive security environment typically enable this setting and select the Trust Bar warning for digitally signed macros only (unsigned macros will be disabled) option. Organizations that do not let users run macros typically enable this setting and select No warnings for all macros but disable all macros.
Disable VBA
Office 2010 provides a setting that enables you to disable VBA. By default, VBA is enabled. Use the following guidelines to determine how to configure this setting if you want to disable VBA.
Setting name: Disable VBA for Office applications
Description: This setting disables VBA in Excel 2010, Microsoft Outlook 2010, PowerPoint 2010, Publisher 2010, Microsoft SharePoint Designer 2010, and Word 2010, and prevents any VBA code from running in these applications. You cannot configure this setting on a per-application basis. It is a global setting. Enabling this setting does not install or remove any VBA-related code from a user’s computer.
Impact: If you enable this setting, VBA code does not run. If your organization has business-critical requirements for using documents that have VBA code, do not enable this setting.
Guidelines: Organizations that have a highly restrictive security environment typically enable this setting.
Change how VBA macros behave in applications that are started programmatically
Office 2010 provides a setting that enables you to change the way VBA macros behave in applications that have been started programmatically through Automation. By default, when a separate program is used to programmatically start Excel 2010, PowerPoint 2010, or Word 2010, any macros can run in the application that was programmatically started. Use these guidelines to determine how to configure this setting if you want to do the following:
• Prevent macros from running in applications that are programmatically started through Automation.
• Allow VBA macros to run according to the VBA macro security settings that are configured for the applications that are programmatically started through Automation.
Setting name: Automation security
Description: This setting controls whether macros can run in an application that is opened programmatically by another application. This setting is a global setting and applies to Excel 2010, PowerPoint 2010, and Word 2010. You cannot configure this setting on a per-application basis. You can choose one of three possible options for this setting:
Disable macros by default All macros are disabled in the programmatically opened application.
Macros enabled (default) Macros are allowed to run in the programmatically opened application. This option enforces the default configuration.
Use application macro security level Macro functionality is determined according to how you configure the VBA macro warning settings setting for each application.
Impact: If you enable this setting and select the Disable macros by default option, macros will not run in applications that are programmatically started. This can be a problem if an application is started programmatically and then opens a document or a template that contains macros. In this case, the functionality that is provided by the macros is not available. The same situation might occur if you select the Use application macro security level option and you disable macros using the VBA macro warning settings setting.
Guidelines: Most organizations enable this setting and select the Use application macro security level option. However, organizations that have a highly restrictive security environment typically enable this setting and select the Disable macros by default option.
Change how encrypted VBA macros are scanned for viruses
Office 2010 provides a setting that enables you to modify the way encrypted VBA macros are scanned by antivirus software in Excel 2010, PowerPoint 2010, and Word 2010. By default, if a document, presentation, or workbook is encrypted and contains VBA macros, the VBA macros are disabled unless an antivirus program is installed on the client computer. In addition, encrypted VBA macros are scanned by the client computer’s antivirus program when a user opens a document that contains encrypted macros. Use these guidelines to determine how to configure this setting if you want to do the following:
• Allow all encrypted VBA macros to run without being scanned by an antivirus program.
• Scan encrypted VBA macros if an antivirus program is installed, but enable encrypted VBA macros if no antivirus program is installed.
Setting name: Scan encrypted macros in Excel Open XML documents, Scan encrypted macros in PowerPoint Open XML documents, Scan encrypted macros in Word Open XML documents
Description: This setting controls the way encrypted VBA macros undergo virus scanning. This setting is a per-application setting and can be configured for Excel 2010, PowerPoint 2010, and Word 2010. You can choose one of three possible options for this setting:
Scan encrypted macros (default). All encrypted VBA macros are disabled unless they are scanned by an antivirus program. This option enforces the default configuration.
Scan if antivirus software available. Encrypted VBA macros are disabled unless they are scanned by an antivirus program. However, if no antivirus program is installed on the client computer, all encrypted VBA macros are enabled.
Load macros without scanning. Encrypted VBA macros are enabled and are not scanned, regardless of whether an antivirus program is installed on the client computer.
Impact: If you enable this setting and select the Load macros without scanning option, security could be significantly reduced by encrypted macros that have not been scanned for viruses. The same is true if the client computer does not have an antivirus program installed and you enable this setting and select the Scan if antivirus software available option.
Guidelines: Most organizations use the default configuration for this setting and do not change this setting.
Related VBA macro settings
Several other settings affect how VBA macros behave in Office 2010 applications. If you are modifying VBA macro settings because you have a special security environment, you might want to evaluate the following settings:
Trust access to VBA project
This setting determines whether automation clients can access the VBA project.
Disable all Trust Bar notifications for security issues
This setting prevents users from seeing Message Bar warnings, including warnings about unsafe VBA macros.
To learn more about these settings, see Security policies and settings in Office 2010.
See Also
Security overview for Office 2010
Plan privacy options for Office 2010
If you want to suppress the Welcome to Microsoft Office 2010 dialog box that appears the first time that a user starts Microsoft Office 2010, you can configure privacy options. The Welcome to Microsoft Office 2010 dialog box, also known as the Opt-in wizard or the Recommended Settings dialog box, lets users enable or disable several Internet-based services that help protect and improve Office 2010 applications.
In this article:
• About planning privacy options
• Suppress the Welcome to Microsoft Office 2010 dialog box
• Configure privacy options
• Related privacy options
About planning privacy options
The first time that a user starts Office 2010, the following dialog box appears:
[pic]
If users select Use Recommended Settings, the following security settings and privacy options are enabled:
• Recommended and important updates are automatically installed for the Windows Vista and newer operating systems and Office 2010 applications. Users are notified about new optional software. For Windows XP, high priority updates are installed.
• Applications are able to connect to for updated Help content and can receive targeted Help content for Office 2010 applications that are installed.
• Applications are able to periodically download small files that help determine system problems and prompt users to send error reports to Microsoft.
• Users are signed up for the Customer Experience Improvement Program.
If users select Install Updates Only, recommended and important updates are automatically installed for the Windows Vista operating systems and newer Windows operating systems and Office 2010 applications. Users are notified about new optional software. For Windows XP, only high priority updates are installed. However, privacy options are not changed in Office 2010 applications, which means that the default privacy options take effect. If users select Don’t Make Changes, automatic updating is not changed in the Windows Security Center and privacy options are not changed in Office 2010, which means that the default privacy options take effect.
The default privacy options for Office 2010 applications are as follows:
• Office 2010 applications do not connect to for updated Help content and office applications are not detected on your computer to give users improved search results.
• Office 2010 applications do not download small programs that help diagnose problems and error message information is not sent to Microsoft.
• Users are not enrolled in the Customer Experience Improvement Program.
Because the Welcome to Microsoft Office 2010 dialog box lets users enable or disable several Internet-based services, you might want to prevent the dialog box from appearing and configure these services individually. If you suppress the dialog box, we recommend that you enable all of the Internet-based services, which you can do by configuring privacy options.
[pic]Note:
For detailed information about the settings that are discussed in this article, see Security policies and settings in Office 2010. For information about how to configure security settings in the Office Customization Tool (OCT) and the Office 2010 Administrative Templates, see Configure security for Office 2010.
Suppress the Welcome to Microsoft Office 2010 dialog box
You can suppress the Welcome to Microsoft Office 2010 dialog box by enabling the Suppress recommended settings dialog setting. This setting prevents the Welcome to Microsoft Office 2010 dialog box from appearing the first time that a user starts Office 2010. If you enable this setting, the automatic updating feature remains unchanged and the privacy options that control Internet-based services are not enabled.
If you suppress the Welcome to Microsoft Office 2010 dialog box without enabling certain privacy options, you disable several features that improve Office 2010 applications and you could expose a computer to security threats. Therefore, if you enable this setting we recommend that you also enable all of the privacy options that are discussed in Configure privacy options.
Most organizations enable this setting, including organizations that have a highly restrictive security environment or a security environment that restricts Internet access.
Configure privacy options
Office 2010 provides several settings that let you control the disclosure of private information. These settings are often known as privacy options. You can enable or disable each of these settings to suit your organization’s security requirements. However, if you suppress the Welcome to Microsoft Office 2010 dialog box, we recommend that you enable all these settings.
Setting name: Online content options
• Description: This setting controls whether the Office 2010 Help system can download Help content from . You can select one of three possible options for this setting:
Never show online content or entry points. The Help system does not connect to to download content. This is the default setting if you suppress the Welcome to Microsoft Office 2010 dialog box or if users select Don’t make changes or Install Updates Only on the Welcome to Microsoft Office 2010 dialog box.
Search only offline content whenever available. The Help system does not connect to to download content.
Search online content whenever available. The Help system connects to for content when the computer is connected to the Internet.
• Impact: If you enable this setting and select Never show online content or entry points or Search only offline content whenever available, users cannot access updated Help topics through the Help system and you cannot get templates from .
• Guidelines: Most organizations enable this setting and select Search online content whenever available. This is the recommended configuration for this setting. However, organizations that have a highly restrictive security environment, or a security environment that restricts Internet access, typically enable this setting and select Never show online content or entry points.
Setting name: Automatically receive small updates to improve reliability
Description: This setting controls whether client computers periodically download small files that enable Microsoft to diagnose system problems.
Impact: If you enable this setting, Microsoft collects information about specific errors and the IP address of the computer. No personally identifiable information is transmitted to Microsoft other than the IP address of the computer requesting the update.
Guidelines: Most organizations enable this setting, which is the recommended configuration. Organizations that have a highly restrictive security environment, or a security environment that restricts Internet access, typically disable this setting.
Setting name: Enable Customer Experience Improvement Program
Description: This setting controls whether users participate in the CEIP to help improve Office 2010. When users participate in the CEIP, Office 2010 applications automatically send information to Microsoft about how the applications are used. This information is combined with other CEIP data to help Microsoft solve problems and improve the products and features customers use most often. Participating in the CEIP does not collect users’ names, addresses, or any other identifying information except the IP address of the computer that is used to send the data.
Impact: If you enable this setting, users participate in the CEIP.
Guidelines: Most organizations enable this setting, which is the recommended configuration. Organizations that have a highly restrictive security environment, or a security environment that restricts Internet access, typically do not enable this setting.
Related privacy options
Several other settings are related to privacy disclosure in Office 2010 applications. If you are changing privacy options because you have a special security environment, you might want to evaluate the following settings:
Protect document metadata for password protected files This setting determines whether metadata is encrypted when you use the Encrypt with Password feature.
Protect document metadata for rights managed Office Open XML files This setting determines whether metadata is encrypted when you use the Restrict Permission by People feature.
Warn before printing, saving, or sending a file that contains tracked changes or comments This setting determines whether users are warned about comments and tracked changes before they print, save, or send a document.
Make hidden markup visible This setting determines whether all tracked changes are visible when you open a document.
Prevent document inspectors from running This setting lets you disable Document Inspector modules.
To learn more about these settings, see Security policies and settings in Office 2010.
See Also
Security overview for Office 2010
Plan for multilanguage deployment of Office 2010
This article discusses planning considerations for deploying Microsoft Office 2010 with multiple languages.
In this article:
• Plan Setup
• Plan customizations
• Plan for proofing tools
Plan Setup
The language-neutral design of Office 2010 helps simplify the deployment of Office products in multiple languages. Instead of creating a series of installations, you enable Setup to coordinate a single installation of multiple language versions.
All language-specific components for a particular language are contained in a Microsoft Office 2010 Language Pack. Each Office 2010 Language Pack includes language-specific folders for all Office 2010 products that are 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 and OptionState Id values in Office 2010.
You copy all the Office 2010 Language Packs that you need to a network installation point that contains at least one complete Office 2010 product. By default, Setup automatically installs the language version that matches the Windows user locale that is set on each user's computer. Or, 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 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 Microsoft Office 2010 Proofing Tools Kit for additional languages.
To identify which deployment solution is appropriate for your scenario, see the model poster Deploy Multilanguage Packs for Microsoft Office 2010 ().
[pic]
To determine which companion proofing languages are included in an Office 2010 Language Pack, see Companion proofing languages for Office 2010.
Each Office 2010 Language Pack contains the proofing tools for one or more additional languages. For example, the Office 2010 Language Pack - Danish contains the proofing tools for English and German, in addition to Danish. All Office 2010 Language Packs contain the proofing tools for English. For more information about proofing tools, see Plan for proofing tools.
Before it installs a language version of an Office 2010 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 2010.
It is important to plan which languages will be needed at the beginning of your deployment. There are special steps that you must take if you have 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 Office 2010.
Understanding the Setup logic for Shell UI language
Whenever you deploy the Office 2010 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 2010 installation language and for the Shell user interface (Shell UI). The Shell UI includes core elements of Office 2010 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 2010 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 no match, Setup looks for a close match. If the user locale is set to English (Canada), for example, Setup might install Office 2010 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\14.0\Common\LanguageResources
If the InstallLanguage entry has not been added to the LanguageResources subkey and set to a particular language (LCID), Setup prompts the user to select 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 2010 on each client computer, you should edit the Config.xml file and set the element for each language that you want to include. However, when you add more than one language in the Config.xml file, you must 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 element. In this case, the language of the Setup user interface follows the logic described previously. However, 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 2010 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; however, the user cannot remove French.
For specific steps on how to customize Setup for different scenarios, see applicable sections in Customize language setup and settings for Office 2010:
• Deploy a default language version of Office
• Specify which languages to install
• Deploy different languages to different groups of users
Plan customizations
When a user starts an Office 2010 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 2010:
• Primary editing language When more than one language version of Office 2010 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 2010 documents. Depending on the languages selected, 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 Office, by applying a Setup customization file (.msp file) or by setting policies, Office 2010 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 Group Policies enforce default language settings. Users in your organization cannot permanently change settings managed by policy. The settings are reapplied every time that the user logs on.
The following policies help you manage language settings in the Office 2010:
• Display menus and dialog boxes in Located in the Display Language folder. This determines the language of the user interface.
• Display help in Located in the Display Language folder. This determines the language of online Help. If this policy is not configured, the Help language uses the user interface language.
• Enabled Editing Languages Located in the Editing Languages folder. This enables editing languages from the list of languages supported by Office.
• Primary Editing Language Located in the Enabled Editing Languages folder. This specifies the language in which users work with Office applications and documents when more than one language version is available on the computer.
• Office Customization Tool (OCT) 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 change the settings after the installation.
• Language Settings tool If you do not enforce language settings by policy, users who work in Office 2010 applications can use the Language Settings tool to change their language settings.
For specific steps on how to use these tools to customize Office 2010 for multiple language deployments, see Customize language setup and settings for Office 2010.
Enable users to view the new language settings on first open
Typically, after you configure language settings by using one of the methods described in this article, Setup applies default settings that match the language that is installed on the computer when a user starts an Office 2010 application for the first time. This means the new language settings will display the next (second) time that the user starts the Office 2010 application.
If you want users to view the new language settings the first time that they open an Office 2010 application, you can deploy the following registry settings to their computers when you deploy an initial Office 2010 installation, or before they have to use an Office 2010 application. You can deploy these registry settings by using a script or batch file, Group Policy, or the OCT. The registry settings that you must configure are the following DWORD values under the HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\LanguageResources key:
UILanguage
HelpLanguage
FollowSystemUI
For each of these values, for Value name specify the LCID (locale identifier) that corresponds to the language that you want to use. For a list of LCIDs, see Language identifiers and OptionState Id values in Office 2010. LCIDs are decimal values. Therefore, you must also set the Base option to Decimal.
Customize language-specific settings related to user locale
In addition to using the Primary Editing Language setting, the Office 2010 also configures language-related settings, such as number format, to match the user locale of the operating system. This behavior is controlled by the LangTuneUp 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 2010. If the LangTuneUp entry does not exist, Office 2010 creates the entry the first time that 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 2010 as a whole. However, individual applications still check for new input method editors (IMEs) and language scripts, and still apply application settings that are 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 2010 or by any individual Office 2010 application.
In some scenarios, ignoring the user locale setting can help maintain a standard configuration across a multilingual organization. Setting the LangTuneUp 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 2010 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 2010 documents might not always have the Asian fonts they must have to display characters correctly. If the installation language on the user’s computer does not match the language that was used in the document and LangTuneUp is set to Prohibited, Office 2010 does not display fonts in the non-default language. If your Office 2010 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.
Plan for proofing tools
Proofing tools let users 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 language-specific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect.
The Office 2010 Proofing Tools Kit 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.
Determining the method for deploying proofing tools
You can deploy additional proofing tools for users who have to edit documents in languages other than those already installed on their computers. You can deploy additional proofing tools from either of these sources:
• Office 2010 Language Pack Use this option if users need both the user interface and the proofing tools for the language, or if one language pack can provide all the proofing tool languages that you need. Be aware that each language version of the Office 2010 includes proofing tools for a set of companion languages. For example, when you deploy the English version of an Office 2010 product, users receive proofing tools for both Spanish and French in addition to English. Depending on the number of user interface languages that you want to deploy and the included companion languages, Office 2010 Language Packs might provide all of the proofing tools that you need.
For a list of companion languages, see Companion proofing languages for Office 2010. If a language pack has all the proofing tool languages that you need, deploy a language pack by using the instructions that fit your scenario in Customize language setup and settings for Office 2010.
• Office 2010 Proofing Tools Kit This product contains the proofing tools for all of the languages that are available with Office 2010. Use this option if you do not need the user interface for the language and you must have many proofing tools that are not included in the set of companion languages for any languages installed or included in an additional language pack that you could install.
The Office 2010 Multi-Language Pack contains all of the Office 2010 Language Packs. Individual Office 2010 Language Packs, the Office 2010 Multi-Language Pack, and Office 2010 Proofing Tools Kit are available for purchase in major retail stores and their Web sites, and also through Microsoft volume licensing programs.
The hard disk space requirement to install proofing tools is 1 gigabyte (GB). However, the overall disk space depends on whether you deploy proofing tools from a language pack or from the Office 2010 Proofing Tools Kit. As with most products in the Office 2010, the complete Office 2010 Proofing Tools Kit package is cached to the local installation source (LIS).
[pic]Note:
Proofing tools do not include bilingual dictionaries or word breakers. Those tools are part of the language version or language pack.
Customizing Setup for Office 2010 Proofing Tools Kit
To customize the Setup of the Office 2010 Proofing Tools Kit, modify the Config.xml file in the ProofKit.WW folder. For each set of proofing tools that you do not want to install, in the OptionState element, set the State attribute to Absent.
Syntax
OptionState attributes
The following table shows OptionState attributes, values, and descriptions.
|Attribute |Value |Description |
|Id |optionID |An item that the user can choose to install. |
| | |See Proofing Tools Config.xml OptionState Id |
| | |values in Language identifiers and OptionState|
| | |Id values in Office 2010. |
|State |Absent |The feature is not installed. |
| |Advertise |The feature is installed the first time that |
| | |it is used. |
| |Default |The feature returns to its default |
| | |installation state. |
| |Local |The feature is installed on the user's |
| | |computer. |
|Children |force |All child features of the feature are set to |
| | |the specified state. |
[pic]Note:
The default value for the State attribute is Local.
Example Config.xml file for Office 2010 Proofing Tools Kit
The following example Config.xml file shows every language that has the OptionState element State attribute set to Absent. If you decide to copy this example into the Config.xml file for the Office 2010 Proofing Tools Kit, set the State attribute for each set of proofing tools that you want to deploy to Local (or Default or Advertise, if preferred).
Precaching the local installation source for the Office 2010 Proofing Tools Kit
When you deploy the Office 2010 Proofing Tools Kit, Setup creates a local installation source on the user's computer — a copy of the compressed source files for the Office 2010 Proofing Tools Kit. 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 the Office 2010 Proofing Tools Kit. To precache the local installation source for the Office 2010 Proofing Tools Kit, see Precache the local installation source for Office 2010. Use the Setup.exe and Config.xml files from the ProofKit.WW folder on the Office 2010 Proofing Tools Kit CD.
See Also
Language identifiers and OptionState Id values in Office 2010
Companion proofing languages for Office 2010
Customize language setup and settings for Office 2010
Add or remove languages after deploying Office 2010
International reference for Office 2010
Office Customization Tool in Office 2010
Precache the local installation source for Office 2010
Plan for virtualization
The content in this article will be available later in the Microsoft Office 2010 Beta.
Plan a migration and upgrade strategy for Office 2010
This section provides information about how to plan the installation of the Microsoft Office 2010 suites, and how to migrate the user data, such as user and computers settings and documents created from the previously installed versions of Microsoft Office.
In this section:
|Article |Description |
|Plan an upgrade to Office 2010 |Describes the upgrade process for Microsoft Office 2010, including |
| |the various upgrade options and data migration paths. |
|Migrate user data registry keys in Office 2010 |Lists the registry keys that are migrated when you use either the |
| |in-place upgrade or the uninstall-upgrade of Office 2010. |
|Choose an option for deploying Office 2010 |Provides areas of functionality you can use to deploy Office 2010, |
| |including network share, Group Policy startup scripts, managed |
| |deployment, application virtualization, and presentation |
| |virtualization. |
Plan an upgrade to Office 2010
This article describes the upgrade process for Microsoft Office 2010, including the various upgrade options and data migration paths.
In this article:
• Overview of the upgrade process
• Compare upgrade options and understand data migration
• Migrate documents
Overview of the upgrade process
The following diagram shows the tasks involved for planning an upgrade to Office 2010.
[pic]
The process of upgrading to Office 2010 can be divided into two primary tasks:
• Install the new Microsoft Office 2010 suites.
• Migrate the user data, such as user and computers settings and documents created from the previously installed version of Microsoft Office.
When you plan an upgrade strategy, first decide on the option for upgrading to Office 2010 that is best for the organization. The upgrade type then helps determine the available choices for data migration and how data migration is performed.
Compare upgrade options and understand data migration
The options for upgrading to Office 2010 can be categorized into the following three areas:
• In-place upgrade The earlier version of Office, such as the 2007 Microsoft Office system, is installed on computers.
• Uninstall upgrade The earlier version of Office, such as the 2007 Office system, is first uninstalled before the upgrade to Office 2010.
• New operating system upgrade The computers get a new version of the operating system, such as Windows 7, and an upgrade to Office 2010.
The following table lists the upgrade options and how the migration of the user and computer settings data takes place.
|Upgrade option |Migration of user and computer settings data |
|In-place upgrade |Migration performed during installation of Office 2010 |
|Uninstall-upgrade |Migration performed during first use of each Office 2010 application |
|New operating system upgrade |Migration performed by using the User State Migration Tool (USMT) to |
| |capture the settings from the targeted computers before the new |
| |operating system is installed. After the new operating system is |
| |installed, USMT is used to restore the settings. |
Migration of data to Office 2010 includes both the user and computer settings and the documents that were created from earlier versions of Office. For a list of the registry keys that are migrated, see Migrate user data registry keys in Office 2010.
The documents created from the previously installed version of Office remain on the computers in their current formats and can be migrated or converted, as needed, at another time if an in-place upgrade or uninstall upgrade is used. When performing a new operating system upgrade, you must move the documents from the source computers to a migration store before you install the new operating system and upgrade the computers to Office 2010. Using USMT makes this process easier. For more information about how to use USMT see the User State Migration Tool 4.0 User's Guide ().
After you decide on the best option for the organization, you have to determine the best migration strategy for the documents created by using earlier versions of Office.
Migrate documents
The following diagram shows the tasks involved in planning to migrate documents to Office 2010.
[pic]
These tasks are further defined in the following steps:
1. Review what has changed When you plan your document migration, first review changes to the Office 2010 applications that you plan to install, such as what is new, changed, or removed. For more information, see Changes in Office 2010.
2. Review migration considerations Next, review any application-specific migration considerations. For more information, see migration considerations for each application in Product and feature changes in Office 2010.
3. Plan file format support After you review the changes and migration considerations, determine a strategy for file format support after you upgrade to Office 2010. For more information, see FAQ: File format ().
4. Assess by using OMPM Finally, use the Office Migration Planning Manager (OMPM) to examine the files in your environment, and then and decide whether to archive them, convert them in bulk by using the Office File Converter available in OMPM, or convert them manually.
See Also
Migrate user data registry keys in Office 2010
Migrate user data registry keys in Office 2010
This article lists — in alphabetical order for Microsoft Office 2003 and 2007 Microsoft Office system applications — the registry keys that are migrated when you use either the in-place upgrade or the uninstall-upgrade of Microsoft Office 2010. You can migrate these same settings when using the new operating system upgrade when you use the User State Migration Tool (USMT) with the MigApp.xml file. This article also contains the keys that are included and those which are explicitly excluded during the migration.
For more information about MigApp.xml for USMT, see Customize USMT XML Files ().
In this article:
• Microsoft Office 2003 settings
• Microsoft Office 2007 settings
Microsoft Office 2003 settings
Common Settings
|HKCU\Software\Microsoft\Office\Common\* [*] |
|HKCU\Software\Microsoft\Office\11.0\* [*] |
|HKCU\Software\Microsoft\Shared Tools\* [*] |
|HKCU\Software\Microsoft\Shared Tools\Proofing Tools\Custom Dictionaries [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Internet\* [*] |
|%APPDATA%\Microsoft\Office [*.acl] |
|%APPDATA%\Microsoft\Office\Recent [*] |
|%APPDATA%\Microsoft\Proof\* [*] |
|HKCU\Software\Microsoft\Office\Common\Smart Tag\Recognizers\{4FFB3E8B-AE75-48F2-BF13-D0D7E93FA8F9}\* [*] |
|HKCU\Software\Microsoft\Office\Common\Smart Tag\Recognizers\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}\* [*] |
|HKCU\Software\Microsoft\Office\Common\Smart Tag\Recognizers\{87EF1CFE-51CA-4E6B-8C76-E576AA926888}\* [*] |
Common Settings
|HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Shortcut Bar [LocalPath] |
|HKCU\Software\Microsoft\Office\11.0\Common\Internet [LocationOfComponents] |
|HKCU\Software\Microsoft\Office\11.0\Common\Open Find\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Internet [UseRWHlinkNavigation] |
|HKCU\Software\Microsoft\Office\11.0\Common\InternetServer Cache\* [*] |
Access 2003
|HKCU\Software\Microsoft\Office\11.0\Common\LanguageResources [SKULanguage] |
|HKCU\Software\Microsoft\Office\Access\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Access\* [*] |
|HKCU\Software\Microsoft\Office\11.0\CMA\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings\ [Microsoft Access] |
|%APPDATA%\Microsoft\Office [Access11.pip] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Access\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Access\Recent Templates\* [Template*] |
Access 2003
|HKCU\Software\Microsoft\Office\11.0\Access\Settings [MRU*] |
Excel 2003
|HKCU\Software\Microsoft\Office\11.0\Common\LanguageResources [SKULanguage] |
|HKCU\Software\Microsoft\Office\11.0\Excel\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings\ [Microsoft Excel] |
|%APPDATA%\Microsoft\Excel\ [EXCEL11.xlb] |
|%APPDATA%\Microsoft\Office\ [EXCEL11.pip] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Excel\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Excel\Recent Templates\* [Template*] |
Excel 2003
|HKCU\Software\Microsoft\Office\11.0\Excel\Recent Files\* [*] |
FrontPage 2003
|HKCU\Software\Microsoft\FrontPage\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings [Microsoft FrontPage] |
|%APPDATA%\Microsoft\FrontPage\State [CmdUI.PRF] |
|%APPDATA%\Microsoft\Office [fp11.pip] |
|%APPDATA%\Microsoft\FrontPage\Snippets [FPSnippetsCustom.xml] |
FrontPage 2003
|HKCU\Software\Microsoft\FrontPage [WecErrorLog] |
|HKCU\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recent File List\* [*] |
|HKCU\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recent Web List\* [*] |
OneNote 2003
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Common\LanguageResources [SKULanguage] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\OneNote\* [*] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Common\Toolbars\Settings\ [Microsoft Office OneNote] |
|%APPDATA%\Microsoft\Office\ [OneNot11.pip] |
|%APPDATA%\Microsoft\OneNote\ [Preferences.dat] |
|%APPDATA%\Microsoft\OneNote\ [Toolbars.dat] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\Recent Templates\* [Template*] |
OneNote 2003
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\OneNote\Options\Save\ [BackupLastAutoBackupTime] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\OneNote\Options\Save\ [BackupFolderPath] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\OneNote\General\ [LastCurrentFolderForBoot] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\OneNote\General\ [Last Current Folder] |
Outlook 2003
|HKCU\Software\Microsoft\Office\11.0\Common\LanguageResources [SKULanguage] |
|HKCU\Software\Microsoft\Office\Outlook\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Outlook\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings [Microsoft Outlook] |
|HKCU\Software\Microsoft\Office\Outlook\OMI Account Manager\Accounts\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Outlook\Journal\* [*] |
|%APPDATA%\Microsoft\Signatures\* [*] |
|%CSIDL_LOCAL_APPDATA%\Microsoft\FORMS [frmcache.dat] |
|%APPDATA%\Microsoft\Outlook [outcmd11.dat] |
|%APPDATA%\Microsoft\Outlook [outcmd.dat] |
|%APPDATA%\Microsoft\Outlook [views.dat] |
|%APPDATA%\Microsoft\Outlook [OutlPrint] |
|%APPDATA%\Microsoft\Office [MSOut11.pip] |
|%APPDATA%\Microsoft\Outlook [*.rwz] |
|%APPDATA%\Microsoft\Outlook [*.srs] |
|%APPDATA%\Microsoft\Outlook [*.NK2] |
|%APPDATA%\Microsoft\Outlook [*.xml] |
|HKCU\Software\Microsoft\Exchange\* [*] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\* [001e023d] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\* [001f023d] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\* [*] |
Outlook 2003
|HKCU\Software\Microsoft\Office\11.0\Outlook [FirstRunDialog] |
|HKCU\Software\Microsoft\Office\11.0\Outlook [Machine Name] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\*\0a0d020000000000c000000000000046 [111f031e] |
|HKCU\Identities\* [LDAP Server] |
|HKCU\Software\Microsoft\Internet Account Manager\Accounts\* [LDAP Server] |
|HKCU\Software\Microsoft\Office\Outlook\OMI Account Manager\Accounts\* [LDAP Server] |
PowerPoint 2003
|HKCU\Software\Microsoft\Office\11.0\PowerPoint\* [*] |
|HKCU\Software\Microsoft\Office\11.0\PowerPoint\RecentFolderList [Default] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings [Microsoft PowerPoint] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\PowerPoint\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\PowerPoint\Recent Templates\* [Template*] |
PowerPoint 2003
|HKCU\Software\Microsoft\Office\11.0\PowerPoint\Recent File List\* [*] |
|HKCU\Software\Microsoft\Office\11.0\PowerPoint\RecentFolderList\* [*] |
Project 2003
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Common\LanguageResources [SKULanguage] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Common\Toolbars\Settings [Microsoft Project] |
|%APPDATA%\Microsoft\Office [MSProj11.pip] |
|%APPDATA%\Microsoft\MS Project\11\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\Recent Templates\* [Template*] |
Project 2003
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\Recent File List [*] |
Publisher 2003
|HKCU\Software\Microsoft\Office\11.0\Common\LanguageResources [SKULanguage] |
|HKCU\Software\Microsoft\Office\11.0\Publisher\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings [Microsoft Publisher] |
|%APPDATA%\Microsoft\Office [*.acl] |
|%APPDATA%\Microsoft\Publisher [pubcmd.dat] |
|%APPDATA%\Microsoft\Office\ [*.jsp] |
Publisher 2003
|HKCU\Software\Microsoft\Office\11.0\Publisher\Recent File List\* [*] |
Visio 2003
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\* [*] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Common\Toolbars\Settings\ [Microsoft Office Visio] |
|CSIDL_APPDATA\Microsoft\Office\[Visio11.pip] |
|CSIDL_LOCAL_APPDATA\Microsoft\Visio\ [content.dat] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Visio\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Visio\Recent Templates\* [Template*] |
Visio 2003
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\Application\ [LastFile*] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\Application\ [MyShapesPath] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\Application\ [UserDictionaryPath1] |
Word 2003
|HKCU\Software\Microsoft\Office\11.0\Common\LanguageResources [SKULanguage] |
|HKCU\Software\Microsoft\Office\11.0\Word\* [*] |
|HKCU\Software\Microsoft\Office\11.0\Common\Toolbars\Settings [Microsoft Word] |
|%APPDATA%\Microsoft\Templates [Normal.dot] |
|%APPDATA%\Microsoft\Office [Word11.pip] |
|%APPDATA%\Microsoft\Office [WordMa11.pip] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Word\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Word\Recent Templates\* [Template*] |
Word 2003
|HKCU\Software\Microsoft\Office\11.0\Word\Options [PROGRAMDIR] |
Microsoft Office 2007 settings
Common Settings
|HKCU\Software\Microsoft\Office\Common\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Common\* [*] |
|HKCU\Software\Microsoft\Shared Tools\* [*] |
|%APPDATA%\Microsoft\Office [*.acl] |
|%APPDATA%\Microsoft\Office\Recent [*] |
|%APPDATA%\Microsoft\Templates\* [*] |
|%CSIDL_LOCAL_APPDATA%\Microsoft\Office [*.qat] |
|%APPDATA%\Microsoft\Proof\* [*] |
|%APPDATA%\Microsoft\UProof\* [*] |
|HKCU\Software\Microsoft\Shared Tools\Proofing Tools\*\Custom Dictionaries [*] |
|HKCU\Software\Microsoft\Office\Common\Smart Tag\Recognizers\{4FFB3E8B-AE75-48F2-BF13-D0D7E93FA8F9}\* [*] |
|HKCU\Software\Microsoft\Office\Common\Smart Tag\Recognizers\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}\* [*] |
|HKCU\Software\Microsoft\Office\Common\Smart Tag\Recognizers\{87EF1CFE-51CA-4E6B-8C76-E576AA926888}\* [*] |
Common Settings
|HKCU\Software\Microsoft\Office\12.0\Shortcut Bar [LocalPath] |
|HKCU\Software\Microsoft\Office\12.0\Common\Internet [LocationOfComponents] |
|HKCU\Software\Microsoft\Office\12.0\Common\Open Find\* [*] |
|HKCU\Software\Microsoft\VBA\6.0\Common |
Access 2007
|%APPDATA%\Microsoft\Office [Access11.pip] |
|HKCU\Software\Microsoft\Office\Access\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Access\* [*] |
|HKCU\Software\Microsoft\Office\12.0\CMA\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Common\Toolbars\Settings\ [Microsoft Access] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Access\File MRU\* [*] |
Access 2007
|HKCU\Software\Microsoft\Office\12.0\Access\Settings [MRU*] |
Excel 2007
|HKCU\Software\Microsoft\Office\12.0\Excel\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Common\Toolbars\Settings\ [Microsoft Excel] |
|%APPDATA%\Microsoft\Excel\ [EXCEL11.xlb] |
|%APPDATA%\Microsoft\Office\ [EXCEL11.pip] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Excel\File MRU\* [*] |
Excel 2007
|HKCU\Software\Microsoft\Office\12.0\Excel\Recent Files\* [*] |
OneNote 2007
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Common\Toolbars\Settings\ [Microsoft Office OneNote] |
|%APPDATA%\Microsoft\Office\ [OneNot12.pip] |
|%APPDATA%\Microsoft\OneNote\%OFFICEVERSION%\ [Preferences.dat] |
|%APPDATA%\Microsoft\OneNote\%OFFICEVERSION%\ [Toolbars.dat] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\Recent Templates\* [*] |
|%APPDATA%\Microsoft\MS Project\12\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\Recent Templates\* [Template*] |
OneNote 2007
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\General\ [LastMyDocumentsPathUsed] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\OneNote\Options\Paths\ [BackupFolderPath] |
Outlook 2007
|HKCU\Software\Microsoft\Office\Outlook\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Outlook\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Common\Toolbars\Settings [Microsoft Outlook] |
|HKCU\Software\Microsoft\Office\Outlook\OMI Account Manager\Accounts\* [*] |
|%APPDATA%\Microsoft\Signatures\* [*] |
|%CSIDL_LOCAL_APPDATA%\Microsoft\FORMS [frmcache.dat] |
|%APPDATA%\Microsoft\Outlook [outcmd11.dat] |
|%APPDATA%\Microsoft\Outlook [outcmd.dat] |
|%APPDATA%\Microsoft\Outlook [views.dat] |
|%APPDATA%\Microsoft\Outlook [OutlPrint] |
|%APPDATA%\Microsoft\Office [MSOut11.pip] |
|HKCU\Software\Microsoft\Exchange\* [*] |
|%APPDATA%\Microsoft\Outlook [*.rwz] |
|%APPDATA%\Microsoft\Outlook [*.srs] |
|%APPDATA%\Microsoft\Outlook [*.NK2] |
|%APPDATA%\Microsoft\Outlook [*.xml] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Outlook\Journal\* [*] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\* [001e023d] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\* [001f023d] |
Outlook 2007
|HKCU\Software\Microsoft\Office\12.0\Outlook [FirstRunDialog] |
|HKCU\Software\Microsoft\Office\12.0\Outlook [Machine Name] |
|HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\*\0a0d020000000000c000000000000046 [111f031e] |
|HKCU\Identities\* [LDAP Server] |
|HKCU\Software\Microsoft\Internet Account Manager\Accounts\* [LDAP Server] |
|HKCU\Software\Microsoft\Office\Outlook\OMI Account Manager\Accounts\* [LDAP Server] |
PowerPoint 2007
|HKCU\Software\Microsoft\Office\12.0\PowerPoint\* [*] |
|HKCU\Software\Microsoft\Office\12.0\PowerPoint\RecentFolderList [Default] |
|HKCU\Software\Microsoft\Office\12.0\Common\Toolbars\Settings [Microsoft PowerPoint] |
|%APPDATA%\Microsoft\PowerPoint [PPT11.pcb] |
|%APPDATA%\Microsoft\Office [PowerP11.pip] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\PowerPoint\File MRU\* [*] |
PowerPoint 2007
|HKCU\Software\Microsoft\Office\12.0\PowerPoint\Recent File List\* [*] |
|HKCU\Software\Microsoft\Office\12.0\PowerPoint\RecentFolderList\* [*] |
Project 2007
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Common\Toolbars\Settings [Microsoft Office Project] |
|%APPDATA%\Microsoft\Office [MSProj12.pip] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\Recent Templates\* [Template*] |
Project 2007
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\MS Project\Recent File List [*] |
Publisher 2007
|HKCU\Software\Microsoft\Office\12.0\Publisher\* [*] |
|HKCU\Software\Microsoft\Office\12.0\Common\Toolbars\Settings [Microsoft Publisher] |
|%APPDATA%\Microsoft\Office [*.acl] |
|%APPDATA%\Microsoft\Publisher [pubcmd.dat] |
|%APPDATA%\Microsoft\Office [Publis11.pip] |
|%APPDATA%\Microsoft\Office\ [*.jsp] |
Publisher 2007
|HKCU\Software\Microsoft\Office\12.0\Publisher\Recent File List\* [*] |
Visio 2007
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\* [*] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Common\Toolbars\Settings\ [Microsoft Office Visio] |
|%APPDATA%\Microsoft\Office\ [Visio12.pip] |
|%CSIDL_LOCAL_APPDATA%\Microsoft\Visio\ [content.dat] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Visio\Recent Templates\* [*] |
|HKCU\Software\Microsoft\Office\%OFFICEVERSION%\Visio\Recent Templates\* [Template*] |
Visio 2007
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\Application\ [LastFile*] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\Application\ [MyShapesPath] |
|HKCU\software\Microsoft\Office\%OFFICEVERSION%\Visio\Application\ [UserDictionaryPath1] |
Word 2007
|HKCU\Software\Microsoft\Office\12.0\Word\* [*] |
|%APPDATA%\Microsoft\Templates\* [*] |
|%APPDATA%\Microsoft\QuickStyles\* [*] |
|%APPDATA%\Microsoft\Document Building Blocks\* [*] |
|%APPDATA%\Microsoft\Bibliography\* [*] |
|%APPDATA%\Microsoft\Office [Word11.pip] |
|%APPDATA%\Microsoft\Office [WordMa11.pip] |
Word 2007
|HKCU\Software\Microsoft\Office\12.0\Word\Data [PROGRAMDIR] |
|HKCU\Software\Microsoft\Office\12.0\Word\Options [PROGRAMDIR] |
Choose an option for deploying Office 2010
You can use five areas of functionality to deploy Microsoft Office 2010: network share, Group Policy startup scripts, managed deployment, application virtualization, and presentation virtualization. You can use any of these options or a combination of them, such as the managed deployment option to deploy and manage virtual Office 2010 applications. We do not support Office 2010 deployment by means of Group Policy Software Installation (GPSI). A workable alternative to GPSI is to assign computer startup scripts. This article describes each of the deployment options.
For a visual representation of the deployment options, see Deployment Options for Microsoft Office 2010 (), which includes diagrams, descriptions, advantages, limitations, recommendations, and tools.
[pic]
Deployment options
Determine which of the following deployment options works best for your organization.
Network share
A simple way to deploy Office 2010 is to create a network installation point and copy the contents of the Microsoft Office CD onto the network share. Make sure that the network share is accessible by the targeted resources: users/computers.
Group Policy startup scripts
Administrators can use Group Policy to assign computer startup scripts to deploy Office 2010. A script can be written in any language that is supported by the client computer. Windows Script Host-supported languages, such as Microsoft Visual Basic Scripting Editing (VBScript) and JScript, and command files are the most common.
Managed deployment
Administrators can use change and configuration management software, such as Microsoft System Center Essentials and Microsoft System Center Configuration Manager, to deploy Office 2010 applications. The choice of System Center Essentials or Configuration Manager depends in part on the size of your organization.
Applicationvirtualization
Administrators can use Microsoft Application Virtualization (App-V) as part of a deployment option to allow users to run Office 2010 applications on their desktops. Microsoft Application Virtualization streams applications on demand to the desktop, from which the application is run. However, the application is not installed on the desktop.
Presentationvirtualization
Administrators can use Windows Server 2008 Terminal Services as a deployment option to allow users to operate the Office 2010 applications from their workstations. Terminal Services is run on a shared server and presents the application user interface on a remote system, such as a local workstation. Microsoft Application Virtualization for Terminal Services allows for the optimization of the Office 2010 application through the sequencing process of application virtualization and then uses Terminal Services to deliver the application as a presentation virtualization.
Plan for volume activation of Office 2010
Microsoft policy requires the activation of all editions of Microsoft Office 2010 client software, including Volume License editions. For Office 2010, volume activation takes place through Office Activation Technologies, which is based on the Software Protection Platform (SPP) used in Windows Vista and Windows Server 2008.
In this section:
|Article |Description |
|Volume activation overview for Office 2010 |Provides an overview of Microsoft Volume Licensing and Office |
| |Activation Technologies for Office 2010. |
|Plan volume activation of Office 2010 |Describes how to plan for volume activation by using Office |
| |Activation Technologies. |
See Also
Volume activation quick start guide for Office 2010
Deploy volume activation of Office 2010
Volume activation overview for Office 2010
Microsoft includes product activation technologies in the following products sold through the Volume Licensing channel: Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, and now Microsoft Office 2010. Activation establishes a relationship between the software's product key and a particular installation of that software on a device. Activation requires interactive steps by the end user or IT professional, such as entering a product key contacting a networked server or telephone service center.
In this article:
• Volume Licensing overview
• Office Activation Technologies
Volume Licensing overview
Microsoft Volume Licensing offers programs that are customized to the size and purchasing preference of organizations. These programs provide simple, flexible, and affordable solutions that enable organizations to easily manage licenses. Some editions of Office 2010 are available only through the volume licensing channel. To become a Volume customer, organizations must set up a Volume License agreement with Microsoft.
By obtaining software licenses through Microsoft Volume Licensing programs, organizations only pay for the software license, instead of the media included in boxed software. Eliminating these physical costs and purchasing in volume often reduces cost and provides more customized purchasing options and improved software administration.
With some Volume Licensing programs, organizations can also purchase Software Assurance. This is a comprehensive maintenance offering that helps organizations get the most out of their software investment. It combines the latest software with telephone support, partner services, training, and information technology (IT) tools. Organizations can choose Software Assurance at the time of purchase and begin to use the benefits immediately for the term of the license agreement.
Depending on the Volume Licensing program chosen, organizations might receive media, and have the option to obtain media (or supplemental media), documentation, and product support separately as needed.
For more information about Volume Licensing, see Microsoft Volume Licensing (). For step-by-step information about activating Volume License editions of Office 2010 client products, see Volume activation quick start guide for Office 2010.
Changes in activation policy
Activation for the 2007 Microsoft Office system was required only for Microsoft software purchased from retail stores and OEMs. Product keys entered in Microsoft Office Enterprise 2007 bypassed activation. For Office 2010, the activation method uses Office Activation Technologies, based on the Software Protection Platform introduced in Windows Vista and Windows Server 2008.
Microsoft policy requires the activation of all editions of Office 2010 client software. This includes those obtained through a Volume Licensing program. This requirement applies to Office 2010 running on both physical computers and virtual computers. Activation is not required for any Office 2010 Server products: Microsoft SharePoint Server 2010 and Microsoft Project Server 2010, or any version of Microsoft Exchange Server.
Why is activation necessary?
Counterfeiting is a significant problem for the software industry. According to a recent study by the Business Software Alliance, 41 percent of all personal computer software installed worldwide during 2008 was obtained illegally. While the financial effects are serious to software manufacturers and vendors, with losses estimated at US$50 billion in 2008, the impact of counterfeit software goes beyond revenue loss to software manufacturers. Many consumers who have a counterfeit copy of Microsoft software are unwitting victims of a crime. Additionally, counterfeit software is increasingly becoming a vehicle for the distribution of viruses and malware that can target unsuspecting users, potentially exposing them to corruption or loss of personal or business data and identity theft. For more information about the Business Software Alliance study, see Sixth Annual BSA and IDC Global Software Piracy Study ().
Privacy
All methods of activation used by Microsoft are designed to help protect user privacy. The data that is collected is used to confirm that you have a legally licensed copy of the software. It is then aggregated for statistical analysis. Microsoft does not use this information to identify you or contact you.
Office Activation Technologies
Office Activation Technologies provide methods for activating products licensed under Microsoft Volume Licensing programs. Most Office Volume Licensing customers are familiar with Volume License Keys (VLKs) that were issued under a specific license agreement. This key effectively "bypassed" activation. For Office 2010, Office Activation Technologies help automate and manage the activation process while addressing the piracy and product key management problems that arose with keys issued for Office Enterprise 2007.
You can use the following methods to activate Office 2010 by using Office Activation Technologies, which are the same methods that are used for Windows Vista and later versions of Windows:
• Key Management Service (KMS) KMS uses a KMS host key to activate a KMS host computer and establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation.
• Multiple Activation Key (MAK) With a MAK, clients activate Office 2010 online with the Microsoft hosted activation servers or by telephone.
• A combination of KMS and MAK.
Key Management Service (KMS)
KMS enables product activations on the local network. This eliminates the need for individual computers to connect to Microsoft for product activation. It is a lightweight service that does not require a dedicated system and can easily be co-hosted on a system that provides other services. A computer is required to be configured as a KMS host. The KMS host contains a customer-specific volume license key (KMS host key) for each product to be activated and connects once to Microsoft hosted servers for activation. Computers running Windows Server 2003, Volume License editions of Windows 7, or Windows Server 2008 R2 operating systems can be configured as Office 2010 KMS hosts.
[pic]Important:
The Office 2010 KMS host key is not specific to the operating system. It is designed to be used on any of the operating systems that were mentioned earlier, including both 32-bit and 64-bit editions.
Office 2010 KMS clients
KMS clients are computers that are running Volume License editions of Office 2010, which are preinstalled with a KMS client key. KMS clients connect to an organization’s KMS host to request activation. Office 2010 KMS clients can be installed on the operating systems listed in System requirements for Office 2010.
By default, a KMS client key has already been installed in Volume License editions of Office 2010. No action is required by the end user, and you do not have to enter a product key for Office 2010 KMS clients. The only action required by the administrator is the initial activation of the KMS host.
The KMS client can be configured for variable lengths of reactivation and renewal periods. If a KMS client does not activate, notification dialog boxes will display starting 25 days after installation of Office 2010. If a KMS client is absent from the network for longer than 180 days after it has been successfully activated, when starting Office 2010, the user then sees notifications that it is unlicensed. However, there is no functionality loss even if the licenses for KMS clients cannot be renewed. Once Office 2010 is successfully activated, the user no longer receives notifications.
The Office 2010 KMS clients activate by connecting to a KMS host based on a client/server topology. KMS clients can locate KMS hosts by using Domain Name System (DNS) or by setting the KMS host name in the registry. KMS clients contact the host by using a remote procedure call (RPC). The activation process is invisible to the user and requires no interaction.
Multiple Activation Key (MAK)
A unique MAK key is given to an organization for each Volume License edition of Office 2010. Each computer must then activate once with the Microsoft hosted activation services. Associated with each key is a count of the number of activations. For example, a MAK key for an Office 2010 product with 100 activations allows the organization to install the key on 100 computers and activate each one.
MAK is appropriate for organizations with computers that are not connected to the corporate network for long periods of time, such as portable computers. For this to work, Office 2010 must be installed with a MAK key instead of the default GVLK used in volume license editions of Office 2010. There are two ways to activate computers by using MAK. The first method is MAK activation, which requires that each computer independently connect and activate with Microsoft, either over the Internet or by telephone.
The second method is MAK Proxy activation, which is performed by using the Volume Activation Management Tool (VAMT) 2.0. VAMT 2.0 supports Office 2010 MAK proxy activation, which is available at the final release of Office 2010. By using this method, a computer collects activation information from multiple computers on the network and then sends a centralized activation request on their behalf. In this setup, the VAMT 2.0 console is the only computer that connects to Microsoft hosted servers. For more information, see Plan a MAK activation in Plan volume activation of Office 2010. VAMT 2.0 Beta is available for Office 2010 Beta.
With MAK activation, there is no requirement to periodically renew activation. You must reactivate if significant hardware changes are detected. In addition, you must request more activation allowances when the number of activations passes the predetermined limit. You also have to manage the installation of MAKs and you might have to manually activate systems by using a telephone when no Internet connection is available.
[pic]Note:
Only VAMT 2.0 and later versions can support Office 2010.
KMS activation schedule
KMS activation provides a transparent experience for users. After installation, activation is tried every two hours during a 30-day grace period or when an application is started. If activation is not successful by the 25th day of the 30-day grace period, dialog boxes inform the user that activation is required every time that an application is started.
If a KMS client is activated, it enters a licensed state of 180 days. During these 180 days, activation is tried every seven days (this interval is configurable by the administrator). Each successful activation results in Office 2010 to be licensed for 180 days starting from the time of activation. If Office 2010 has not been activated for 180 days while in the licensed state, it re-enters the grace period of 30 days, and activation is tried every two hours (unless set otherwise by the administrator). If it has not reactivated at the end of 30 days, it enters the notifications state, where the user receives notification dialog boxes to activate the installation of Office 2010 every time that an Office application is started. It is important to be aware that Volume License editions of Office 2010 never lose any functionality.
Volume License product keys
If you use Volume License editions of Office 2010, planning for volume activation must be part of your Office 2010 deployment process. KMS host keys and MAKs are issued under a specific license agreement to enable organizations to use the licensed products. These keys can be used only with volume licensing products. They cannot be used with retail software or software that is preinstalled on a new computer by an original equipment manufacturer (OEM), unless the organization has an agreement with the OEM to preinstall Volume License editions of the products.
To obtain your KMS host key and MAK keys, go to the Web site where you downloaded Office 2010.
See Also
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
Tools to configure client computers in Office 2010
Troubleshoot volume activation for Office 2010
Office 2010 Volume Activation forum ()
Office 2010 forums ()
Plan volume activation of Office 2010
This article describes how to plan your testing for Office Activation Technologies. We recommend that you read Volume activation overview for Office 2010 before you read this article.
When you plan for testing Office Activation Technologies, consider the following information:
• The KMS activation threshold for Microsoft Office 2010 is five computers. This means that Office 2010 clients will become activated only after five or more clients have requested activation.
• There is no need to enter a product key for Office 2010 KMS clients. You only need to enter a KMS host key on your KMS host computer.
• If you choose to use MAK, enter the product key either through the Office Customization Tool (OCT) or the Config.xml file. After Office 2010 installation, the product key can be changed by using the Volume Activation Management Tool (VAMT) 2.0 or the Office Software Protection Platform script (ospp.vbs). (For more information, see Tools to configure client computers in Office 2010.)
This article provides a concise summary of the activation methods and the planning notes. This article specifically discusses Windows Vista and Windows Server 2008, but also applies to Office 2010 volume activation. If your organization uses Windows Vista or Windows Server 2008, you most likely are using KMS or MAK activation. You can also use KMS or MAK for Office 2010 volume activation if your KMS host is running on Windows Server 2003, Volume License editions of Windows 7, or Windows Server 2008 R2. For more information, see Plan a KMS deployment later in this article. However, for testing purposes, use a separate KMS host in an isolated environment.
[pic]Important:
The KMS host key for Office 2010 is not specific to a particular operating system. It is designed to be used on any of the operating systems that were mentioned earlier, including both 32-bit and 64-bit editions.
In this article:
• Review activation models
• Plan a KMS deployment
• Plan a MAK activation
Review activation models
Office Activation Technologies provide two activation models:
• Key Management Service (KMS)
• Multiple Activation Key (MAK)
The model chosen depends on the size, network infrastructure, connectivity, and security requirements. You can choose to use only one or a combination of these activation models for testing.
Key Management Service (KMS)
The KMS host must be installed with a KMS host key and activated before accepting KMS activation requests from KMS clients. For information about how to set up a KMS host, see Install and configure the KMS host in Deploy volume activation of Office 2010.
KMS activation requires TCP/IP connectivity. By default, KMS hosts use DNS to publish the KMS service, and client computers connect to the KMS host for activation by using anonymous remote procedure calls (RPCs) through TCP port 1688. You can use the default settings, which require little to no administrative action, or manually configure KMS hosts and clients based on network configuration and security requirements.
Publication of the KMS Service
The KMS service uses service (SRV) resource records (RRs) in DNS to store and communicate the locations of KMS hosts. KMS hosts use dynamic updates, if available, to publish the KMS SRV RRs. If dynamic updates are not available or if the KMS host does not have permissions to publish the RRs, you must publish the DNS records manually or configure client computers to connect to specific KMS hosts. This might require changing permissions on DNS to let more than one KMS host to publish SRV records.
[pic]Note:
DNS changes might take time to propagate to all DNS hosts, depending on the complexity and topology of the network.
Client discovery of KMS
The first time that a KMS client queries DNS for KMS information, it randomly selects a KMS host from the list of SRV RRs that DNS returns. The address of a DNS server that contains the SRV RRs can be listed as a suffixed entry on KMS clients, which allows advertisement of SRV RRs for KMS in one DNS server and KMS clients that have other primary DNS servers to find it.
You can add priority and weight parameters to the DnsDomainPublishList registry value for KMS hosts on Volume License editions of Windows 7 or Windows Server 2008 R2. Doing so enables you to establish KMS host priority groupings and weighting within each group, which specifies the order in which to use KMS hosts and balances traffic among multiple KMS hosts. If you are using priority and weight parameters, we recommend that KMS caching be disabled on the client. This allows the client to query DNS every time that activation is attempted, which will honor the priority and weight parameters, instead of directly contacting the cached KMS host that last resulted in successful activation.
If the KMS host that a client selects does not respond, the KMS client removes that KMS host from its list of SRV RRs and randomly selects another KMS host from the list. If the priority and weight parameters are set, the KMS client will use them while finding another KMS host. Otherwise, KMS hosts are selected randomly. After a KMS host responds, the KMS client caches the name of the KMS host and uses it for subsequent activation and renewal attempts if caching is enabled. If the cached KMS host does not respond on a subsequent renewal, the KMS client discovers a new KMS host by querying DNS for KMS SRV RRs.
KMS activation thresholds
For Office 2010, KMS activation requires a KMS host and at least five clients in a network environment. Five or more computers that are running Office 2010 volume editions must contact the KMS host for their activation requests to be successful. When five clients have connected to a KMS host, clients that later connect to the KMS host receive responses that allow the clients to be activated. Due to the re-activation schedule, the original five clients also become activated when they request activation from the KMS host again.
After initializing KMS, the KMS activation infrastructure is self-maintaining. The KMS service can be co-hosted with other services. A single KMS host can support hundreds of thousands of KMS clients. Most organizations can deploy merely two KMS hosts for their entire infrastructure (one main KMS host and one backup host for redundancy).
KMS activation renewal
KMS activations are valid for 180 days. This is called the activation validity interval. To remain activated, KMS clients must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers attempt to renew their activation every seven days. After a client’s activation is renewed, the activation validity interval begins again.
Multiple Activation Key (MAK)
A MAK key is used for one-time activation with the Microsoft hosted activation services. Each MAK key has a predetermined number of allowed activations. This number is based on Volume Licensing agreements and may not match the organization’s exact license count. Each activation that uses a MAK key with the Microsoft hosted activation service counts toward the activation limit. For Office 2010 Beta, each MAK key has 1000 activations.
There are two ways to activate computers by using a MAK:
• MAK Independent Activation MAK independent activation requires that each computer independently connect and be activated with Microsoft, either over the Internet or by telephone. MAK independent activation is best suited for computers in an organization that do not maintain a connection to the corporate network. For Office 2010 Beta, only online MAK independent activation is supported.
• MAK Proxy Activation by using VAMT 2.0 This enables a centralized activation request on behalf of multiple computers that have one connection to Microsoft. MAK Proxy activation is configured by using VAMT 2.0. MAK Proxy activation is appropriate for environments in which security concerns might restrict direct access to the Internet or the corporate network. It is also suited for development and test labs that do not have this connectivity.
MAK architecture
MAK activation requires that a MAK key is installed on a client computer and instructs that computer to activate itself against Microsoft hosted activation servers over the Internet. In MAK Proxy activation, a MAK key must be installed on the client computer by any of the methods previously described. VAMT 2.0 obtains the installation ID (IID) from the target computer, sends the IID to Microsoft on behalf of the client, and obtains a confirmation ID (CID). The tool then activates the client by installing the CID.
VAMT 2.0
VAMT 2.0 is a stand-alone application that collects activation requests from several computers, and then sends them to Microsoft hosted activation servers in bulk. This is called proxy activation. VAMT 2.0 also supports MAK independent activation. Only VAMT 2.0 or later versions supports Office 2010 in addition to Windows. VAMT 2.0 lets you specify a group of products to activate by using Active Directory Domain Services (AD DS), workgroup names, IP addresses, computer names, or a generic LDAP query. For proxy activation only, VAMT 2.0 distributes the activation confirmation codes from Microsoft hosted activation servers to the computers that requested activation. Because VAMT also stores these confirmation codes locally, it can reactivate a previously activated computer after it is reimaged without re-contacting Microsoft. Additionally, VAMT can be used to easily transition computers between MAK and KMS activation methods.
Plan a KMS deployment
The KMS service does not require a dedicated server. The KMS service can be co-hosted on a server that also hosts KMS for Windows. Specifically, you can configure a computer that is running Windows Server 2003 with KMS 1.1 or a later version installed, Volume License editions of Windows 7, or Windows Server 2008 R2 to act as a single KMS host that responds to both Windows and Office 2010 KMS client activation requests. This works as long as the appropriate Office 2010 KMS host licenses are installed and a valid KMS host key is installed and activated against Microsoft hosted activation servers. KMS host licenses are available on the Web site where you downloaded Office 2010. You can install Office 2010 KMS host licenses by using the KeyManagementServiceHost.exe tool that is available on the Web site where you downloaded Office 2010. You can also use a dedicated KMS host for Office 2010 testing if your enterprise resources allow it.
KMS hosts set up using Office 2010 Beta cannot be used to activate clients that are running the final version of Office 2010. To activate these clients, you can either install the final versions of KMS host licenses and KMS host key on the same KMS host when they become available, or you can set up a new KMS server solely for activating the final version of Office 2010.
Plan DNS server configuration
The default KMS auto-publishing feature requires SRV RR and dynamic update support. Microsoft DNS or any other DNS server that supports SRV RRs, as documented in Internet Engineering Task Force (IETF) Request for Comments (RFC) 2782, and dynamic updates, as documented in RFC 2136 can support KMS client default behavior and KMS SRV RR publishing. Berkeley Internet Domain Name (BIND) versions 8.x and 9.x support both SRV records and dynamic update, for example.
The KMS host must be configured so that it has the credentials needed to create and update SRV, A (IPv4), and AAAA (IPv6) RRs on the dynamic update servers, or the records need to be created manually. The recommended solution for giving the KMS host the needed credentials is to create a security group in AD DS and add all KMS hosts to that group. For Microsoft DNS, ensure that this security group is given full control over the _VLMCS._TCP record on each DNS domain that will contain the KMS SRV RRs.
Activate the KMS host
Installation of a KMS host key enables the Key Management Service on the KMS host. The KMS host must then activate with Microsoft hosted activation servers through the Internet or by telephone. Once the KMS host is activated, it does not communicate any additional information to Microsoft. For more information, see Install and configure the KMS host in Deploy volume activation of Office 2010.
Prepare KMS clients
By default, Volume License editions of Office 2010 are pre-installed with the KMS client key. This makes them KMS clients, without additional configuration required. KMS clients can locate a KMS host automatically by querying DNS for SRV RRs that publish the KMS service. If the network environment does not use SRV RRs, you can manually assign a KMS client to use a specific KMS host by configuring the following registry key:
HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform
The KMS host name is specified by KeyManagementServiceName (REG_SZ), and the port is specified by KeyManagementServicePort (REG_SZ).
Activate as a standard user
Office 2010 does not require administrator permissions for KMS activation. However, volume editions require administrator permissions for MAK activation. Administrators can enable users who have non-administrator permissions to activate with MAK by setting the appropriate registry key in the deployments or in the master image.
HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform\UserOperations = 1
Plan a MAK activation
MAK is recommended for computers that rarely or never connect to the corporate network and for environments in which the number of physical computers needing activation does not meet the Office 2010 KMS activation threshold (five computers). MAK can be used for individual computers or with an image that can be installed by using Microsoft or third-party deployment solutions. MAK can also be used on a computer that was originally configured to use KMS activation, which is useful for moving a computer off the core network to a disconnected environment.
See Also
Volume activation overview for Office 2010
Deploy volume activation of Office 2010
Tools to configure client computers in Office 2010
Troubleshoot volume activation for Office 2010
Office 2010 Volume Activation forum ()
Office 2010 forums ()
Configuration and deployment of Office 2010 Beta
This section provides how-to information for specific deployment tasks, such as customizing the installation, and installing Microsoft Office 2010 on users' computers. It also provides information about the new licensing options for Office 2010, including instructions for configuring the infrastructure for volume licensing and activation.
In this section:
|Article |Description |
|Configure and deploy volume activation of Office 2010 |Provides information and procedures to help you plan the volume |
| |activation of Office 2010. |
|Prepare the infrastructure for Office 2010 |Provides information and procedures to create a network installation |
| |point for the deployment of Office 2010. |
|Customize the installation for Office 2010 |Provides information and procedures for customizing the Office 2010 |
| |installation, including customizing Setup options, configuring user |
| |settings, configuring silent installations, and importing Setup |
| |customization files. This section also includes information and |
| |procedures for customizing Outlook and Microsoft SharePoint Workspace|
| |2010. |
|Deploy Office 2010 |Provides information and procedures for running Setup for Office |
| |2010, precaching the local installation source, and deploying to |
| |users who are not administrators. |
Configure and deploy volume activation of Office 2010
Once you complete the volume activation planning phase for your organization, the next step is to deploy the volume activation methods you have chosen. This section describes how to deploy volume activation.
In this section:
|Article |Description |
|Deploy volume activation of Office 2010 |Provides information about how to deploy Volume License editions of |
| |Microsoft Office 2010 through Office Activation Technologies. |
|Tools to configure client computers in Office 2010 |Describes the tools available for configuring and testing Volume |
| |License editions of Office 2010 through Office Activation |
| |Technologies. |
|Volume activation quick start guide for Office 2010 |Provides information and procedures to quickly activate Volume |
| |License editions of Office 2010 through Office Activation |
| |Technologies. |
See Also
Volume activation quick start guide for Office 2010
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
This article describes how to deploy Office Activation Technologies. We recommend that you read Volume activation overview for Office 2010 and Plan volume activation of Office 2010 before you read this article.
In this article:
• Prepare and configure the Office 2010 client for MAK activation
• Install and configure the KMS host
• Configure DNS
Prepare and configure the Office 2010 client for MAK activation
In the 2007 Microsoft Office system and previous versions, you had to enter a product key when you deployed Office. If you are using Key Management Service (KMS), you do not have to do this for Microsoft Office 2010, because all Volume License editions of Office 2010 have a KMS client key pre-installed. The KMS host key is common to all volume license clients. When an Office 2010 client first installs, KMS activation occurs transparently to the user. However, if you are using Multiple Activation Key (MAK), you must enter the MAK key by using one of the following supported methods:
• Enter the MAK in the Office Customization Tool (OCT).
• Enter the MAK in the Config.xml file.
• Switch to MAK after installation by using the Microsoft Office Backstage view.
• Use Volume Activation Management Tool (VAMT) 2.0.
[pic]Important:
Because different products require different MAK keys, you should first verify that the MAK key for the product is correct.
[pic]To enter a MAK key in the Office Customization Tool (OCT)
|1. In the Type a valid 25-character volume license key with no spaces field, enter the MAK key (five sets of five numbers or |
|characters), and then press ENTER. |
|2. After making any other necessary changes in the OCT, save the MSP file. |
Remember that you do not have to enter a product key in the OCT if you are using KMS activation. For more information about the OCT, see Customize Setup before installing Office 2010.
[pic]To enter a MAK key in the Config.xml file
|1. Add the following line to the Config.xml file: |
| |
|Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key. |
|2. To apply the settings in Config.xml, at a command prompt, type the following command, and then press ENTER: |
|Setup.exe /config |
You do not have to enter the MAK key in the Config.xml file if you are using KMS activation. For more information about how to use the Config.xml file, see Config.xml file in Office 2010.
[pic]To switch to a MAK key after installation
|• Users can manually switch the pre-installed product key (the GVLK for KMS clients) to a MAK after Office 2010 is installed. Only|
|administrators can perform this operation, unless the required registry key that allows non-administrators is set appropriately. |
|If the DWORD value in HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform\UserOperations is set to 1, |
|administrative permissions are not required for product key entry. Only an administrator can create and set this registry key. |
[pic]To create a registry key for manual MAK activation
|• An administrator can create a registry key that allows a standard user (non-administrator) to apply a MAK key and activate an |
|Office 2010 application. This means that a standard user can switch a KMS client to MAK activation, manually activate a computer, |
|and, if it is necessary, replace an existing MAK with a new MAK key. By default, all volume license editions of |
|Office_2nd_CurrentVer disable this behavior. Adding the following line to the Config.xml file will enable this behavior: |
| |
|• Or, you can set the following registry key to enable or disable standard user (non-administrator) activation: |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform]Enable Standard User Activation: |
|"UserOperations"=dword:00000001 (Office 2010 retail products default setting) |
|Disable Standard User Activation: "UserOperations"=dword:00000000 (Office 2010 volume license products default setting) |
[pic]To enter a MAK key manually
|1. Open an Office 2010 application. |
|2. Click the File tab. |
|3. Click Help. |
|4. Click Change Product Key and enter the product key. |
Use the previous procedure if an Office 2010 client was installed with the default KMS client key for KMS activation and you want the client to use MAK activation instead.
If you have to do this on many computers, you can use a computer that hosts VAMT 2.0 to select the computers that you have to change and push the MAK through remote Windows Management Infrastructure WMI calls. Clients must be connected to the network to receive a MAK with this method. For more information about VAMT 2.0, see the VAMT 2.0 documentation that is included with VAMT 2.0.
Activating MAK clients through a proxy server
Activation over the Internet will be blocked if the proxy server requires user authentication. In Microsoft Internet Security and Acceleration (ISA) Server, this setting is called basic authentication. Because activation requests do not present the user's credentials to the proxy server, we recommend that you do not use basic authentication with ISA Server or other proxy servers.
Install and configure the KMS host
Only the following operating systems can serve as the Office 2010 KMS host:
• Windows Server 2003 or with any service packs
• Volume License editions of Windows 7
• Windows Server 2008 R2
[pic]Important:
The KMS host key for Office 2010 is not specific to a particular operating system. It is designed to be used on any of the operating systems mentioned earlier, including both 32-bit and 64-bit editions.
The following operating systems are not supported as the Office 2010 KMS host:
• Windows Vista or with any service packs
• Windows Server 2008 or with any service packs
For more information, see Volume Activation 2.0 for Windows Vista and Windows Server 2008 ().
Manually assigning the KMS host on the KMS client
Administrators can manually assign a KMS host to KMS clients by using KMS host caching. Manually assigning a KMS host disables auto-discovery of KMS on the KMS client. A KMS host is manually assigned to a KMS client by configuring the registry key
HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform
The KMS host name is specified by KeyManagementServiceName (REG_SZ), and the port is specified by KeyManagementServicePort (REG_SZ).
[pic]To install a KMS host on Windows Server 2003
|1. Download Key Management Service 1.1 (x86) for Windows Server 2003 SP1 and Later |
|(). Or, for 64-bit Windows Server 2003, download Key Management Service 1.1 (x64) for|
|Windows Server 2003 SP1 and Later (). Extract these files: KMSW2K3.exe and |
|WindowsServer2003-KB948003-x86-ENU.exe. |
|2. Run KMSW2K3.exe to install SPPSVC, and then run WindowsServer2003-KB948003-x86-ENU.exe to update KMS to version 1.1. |
|3. Download and run KeyManagementServiceHost.exe from the Microsoft Download Center |
|() Web site (). |
|4. When prompted, enter the KMS host key which can be downloaded from the Microsoft Office 2010 KMS host keys |
|() page on TechNet. |
|5. If you have a firewall enabled, open TCP port 1688, which is the default port number. |
[pic]To install a KMS host on Windows 7 or Windows Server 2008 R2
|1. Download and run KeyManagementServiceHost.exe from the Microsoft Download Center Web site |
|(). |
|2. When prompted, enter the KMS host key which can be downloaded from the Microsoft Office 2010 KMS host keys |
|() page on TechNet. |
|3. If you have a firewall enabled, follow these steps to enable KMS through the firewall: |
|a. Open Control Panel and the Windows Firewall icon. |
|b. Click the Allow a program through Windows Firewall link. |
|c. Click the Change Settings button. |
|d. Check the Key Management Service box and then click OK. |
To verify that the KMS host is configured correctly, check the KMS count to see whether it is increasing. At a command prompt on the KMS host, type the following command, and then press ENTER:
cscript slmgr.vbs /dlv 86f3489b-e730-45ee-ad42-039a64c82ba4
This displays the current KMS count. Administrators can also check the KMS log that is in the Applications and Services Logs folder for event ID 12290, the ID for KMS-related activity. The KMS log records activation requests from KMS clients. Each event displays the name of the computer and the time stamp of each activation request.
Because the KMS host service automatically stops, you might encounter this error when you run KeyManagementServiceHost.exe.
Error: The Software Protection Platform service is not running: sppsvc State: Stopped
If you receive this error, perform the following:
1. Open a command prompt with administrator permissions (click Start, type cmd.exe, and then right-click and select Run as Administrator).
2. At the command prompt, type the following command, and then press ENTER:
net start sppsvc
3. Re-run KeyManagementServiceHost.exe.
Alternately, you can perform the following:
1. Right click My Computer and select Manage.
2. Under Services and Applications, select Software Protection Service.
3. Click Start and then OK to start the service.
4. Re-run KeyManagementServiceHost.exe.
Configuring the KMS host
Software License Manager (slmgr.vbs) is a script that is used to configure and retrieve Volume Activation information for the Office 2010 KMS host. The script can be run locally on the target computer or remotely from another computer. However, the script should be run with administrator permissions in the case of Windows Server 2008 R2 (if a standard user runs slmgr.vbs, some license data might be missing or incorrect, and many operations are prohibited).
The slmgr.vbs script can use wscript.exe or cscript.exe, and administrators can specify which script engine to use. If no script engine is specified, slmgr.vbs runs by using the default script engine, wscript.exe.
The Software Licensing Service must be restarted for any changes to take effect. To restart the Software Licensing Service, use the Microsoft Management Console (MMC) Services snap-in or run the following command with administrator permissions (in the case of Windows Server 2008 R2):
net stop sppsvc && net start sppsvc
The slmgr.vbs script requires at least one parameter. If the script is run that has no parameters, it displays help information. The following table lists slmgr.vbs command-line options, and a description of each. Most of the parameters in the table configure the KMS host. However, the parameters /sai and /sri are passed to KMS clients after they make contact with the host. The general syntax of slmgr.vbs is as follows:
slmgr.vbs /parameter
slmgr.vbs [ComputerName] [User] [Password] [Option]
ComputerName Name of remote computer. If a computer name is not passed local computer is used.
User Account with required permission on remote computer.
Password Password for the account. If a User account and password are not passed, current credentials are used.
Option Options are shown in the following table.
|Option |Description |
|/ipk [ProductKey] |Installs the product key for the KMS host or the application |
| |identified by the ActivationID when provided |
|/ato [ApplicationID] |Activates the KMS host for Windows (default), or the application |
| |identified by the application ID when provided. The Office |
| |application ID is |
| |86f3489b-e730-45ee-ad42-039a64c82ba4 |
|/dlv [ApplicationID] |Displays detailed license information for Windows (default), or the |
| |application identified by the application ID when provided. The |
| |Office application ID is |
| |86f3489b-e730-45ee-ad42-039a64c82ba4 |
|/dli [ApplicationID] |Displays license information for Windows (default), or the |
| |application identified by the application ID when provided. The |
| |Office application ID is |
| |86f3489b-e730-45ee-ad42-039a64c82ba4 |
|/sprt [PortNumber] |Sets the TCP communications port on a KMS host. Replaces PortNumber |
| |with the TCP port number to use. The default setting is 1688. |
|/cdns |Disables automatic DNS publishing by a KMS host. |
|/sdns |Enables automatic DNS publishing by the KMS host. |
|/cpri |Lowers the priority of KMS host processes. |
|/sai [ActivationInterval] |Changes how often a KMS client attempts to activate itself when it |
| |cannot find a KMS host. Replaces ActivationInterval with a number of |
| |minutes. The default setting is 120. |
|/sri [RenewalInterval] |Changes how often a KMS client attempts to renew its activation by |
| |contacting a KMS host. Replaces RenewalInterval with a number of |
| |minutes. The default setting is 10080 (7 days). This setting |
| |overrides the local KMS client settings. |
Configure DNS
KMS hosts automatically publish their existence by creating SRV RRs on the DNS server. If there is only one KMS host and dynamic update, no action is required for the KMS host to create the SRV RR that publishes the KMS service location.
If there is more than one KMS host, only the first KMS host can create an SRV RR. Subsequent KMS hosts cannot change or update SRV RRs unless the default permissions on the DNS server are changed.
Changing the default permissions on the DNS server requires administrative rights in the domain, and the KMS hosts must all belong to the same AD DS domain. Create a global security group in AD DS for your KMS hosts. Add each KMS host to the new security group, and set the permissions on the DNS server to allow updates by members of the newly created security group.
See Also
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Tools to configure client computers in Office 2010
Troubleshoot volume activation for Office 2010
Office 2010 Volume Activation forum ()
Office 2010 forums ()
Tools to configure client computers in Office 2010
This article describes how to activate Microsoft Office 2010 Key Management Service (KMS) clients through Office Activation Technologies. We recommend that you read Volume activation overview for Office 2010, Plan volume activation of Office 2010, and Deploy volume activation of Office 2010 before you read this article.
In this article:
• Use KMS for computers running Windows and Office 2010 clients
• Configure the KMS client
• Separate KMS hosts for computers running Windows and Office 2010 clients
• Same KMS host on a computer running Windows Server 2003
• Same KMS host on a computer running Windows 7 or Windows Server 2008 R2
Use KMS for computers running Windows and Office 2010 clients
When you use KMS to activate both computers running Windows and Office 2010 clients, you have the following options for Office 2010 Beta:
• Use separate KMS hosts for computers running Windows and Office 2010 clients
• Use the same KMS host on a computer that is running Windows Server 2003
• Use the same KMS host on a computer that is running Windows 7 or Windows Server 2008 R2.
For information about the operating systems that support KMS hosts for Office 2010, see Install and configure the KMS host in Deploy volume activation of Office 2010.
Configure the KMS client
In general, you do not have to configure Office KMS clients if the Office KMS host has been correctly set up and configured. The KMS client will automatically search for the KMS host by using Domain Name System (DNS) and attempt activation. The KMS service uses service (SRV) resource records (RR) in DNS to store and communicate the locations of KMS hosts. By default, KMS hosts automatically publish the information KMS clients need to find and connect to them by using DNS dynamic update protocol. By default, KMS clients query the DNS server for KMS service information.
You can manually configure KMS hosts and clients, depending on the network configuration and security requirements. For example, if the network environment does not use SRV records, you can manually configure a KMS client to use a specific KMS host. To configure the KMS client, use the Office Software Protection Platform script (ospp.vbs). The script is located in the %installdir%\Program Files\Microsoft Office\Office14 folder. Running ospp.vbs requires the cscript.exe script engine.
[pic]Note:
Although the primary use of the ospp.vbs script is to configure KMS clients, you can use ospp.vbs for all volume editions of Office 2010 products, including both MAK and KMS clients.
The general syntax for ospp.vbs is as follows:
cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]
Option Specifies the option and value to use to activate a product, install or uninstall a product key, install and display license information, set KMS host name and port, and remove KMS host. The options and values are listed in the table in this section.
ComputerName Name of the remote computer. If a computer name is not provided, the local computer is used.
User Account with required permission on the remote computer.
Password Password for the account. If a user account and password are not provided, the current credentials are used.
The following table lists the ospp.vbs options and values.
|Option |Description |
|-act |Activates Office 2010. |
|-inpkey:value |Installs a product key (replaces existing key). Value parameter is |
| |the product key. |
|-unpkeys:value |Uninstalls a product key. Value parameter is the last five characters|
| |of the product key to uninstall. |
|-inslic:value |Installs license. Value parameter is the license location path. |
|-dstatus |Displays license information for installed licenses. |
|-dinstid |Displays Installation ID for offline activation. |
|-actcid:value |Activates product with user-provided Confirmation ID. Value parameter|
| |is the confirmation ID. |
|-sethst:value |Sets KMS host name to activate against. Value parameter is the KMS |
| |host name. |
|-setprt:value |Sets KMS port. Value parameter is the KMS port number. |
|-remhst |Removes KMS host name (sets port to default). |
The following is an example of how you can configure an Office 2010 client:
1. On the computer on which Office 2010 is installed, run the command prompt with administrator permissions.
2. Install a product key by entering the following at the command prompt:
cscript ospp.vbs -inpkey:
3. Activate Office 2010 by entering the following at the command prompt:
cscript ospp.vbs –act
Separate KMS hosts for computers running Windows and Office 2010 clients
If you are using a separate KMS host for Office 2010 Beta, we recommend that you set the host name and port number registry keys on the client computers. This ensures that Office 2010 KMS clients contact the correct KMS host. Windows KMS clients can still find the Windows KMS host through DNS. You can do this by running ospp.vbs with the –sethst and –setprt parameters, which set the following registry values:
• For the new Office 2010 KMS host name, the REG_SZ value is set for the following registry key:
HKLM\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName
• If you want to set a different port, for the new port number on Office 2010 KMS clients, the REG_SZ value is set for the following registry key:
HKLM\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServicePort
Same KMS host on a computer running Windows Server 2003
If you are already using a computer that is running Windows Server 2003 as your Windows KMS host and you want to co-host the Office 2010 Beta KMS host, follow the steps in To install a KMS host on Windows 7 or Windows Server 2008 R2. When you move to the final version of Office 2010, you will need to download and run the updated KeyManagementServiceHost.exe file and obtain and activate the KMS host key for the final version of Office 2010. You cannot activate the final version of Office 2010 with the same KMS host file and key that was used for Office 2010 Beta.
Same KMS host on a computer running Windows 7 or Windows Server 2008 R2
If you are currently using an RC build of a Volume License edition of Windows 7 or using Windows Server 2008 R2 as a Windows KMS host and you want to co-host an Office 2010 KMS host, follow the steps in To install a KMS host on Windows 7 or Windows Server 2008 R2. If you migrate to a release build of Windows 7 or Windows Server 2008 R2, remember that this computer should not be shut down, because it is needed to activate Office 2010. When you are ready to activate the final version of Office 2010, we recommend that you set up the Office 2010 KMS host on a computer that is running the final release of Windows 7 or Windows Server 2008 R2. We recommend that you do not activate Office 2010 through a KMS host on a computer that is running pre-release versions of Windows 7 or Windows Server 2008 R2.
See Also
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
Troubleshoot volume activation for Office 2010
Office 2010 Volume Activation forum ()
Office 2010 forums ()
Volume activation quick start guide for Office 2010
This article is a quick start guide for activating volume editions of Microsoft Office 2010. The intended audience is IT administrators who are familiar with Windows Volume Activation and want to know which steps are required for volume activation of Office client products. If you are not familiar with volume activation, please see Windows Volume Activation Planning Guide (), Plan for volume activation of Office 2010, and Configure and deploy volume activation of Office 2010.
Volume editions of Office 2010 require activation. The activation technology is based on the Windows Software Protection Platform. If you are familiar with Windows Key Management Service (KMS) or Multiple Activation Key (MAK) activation, then you will be familiar with requirements for Office 2010 activation. The main focus of this article is on the differences between Windows and Office, in addition to the steps required to activate Office 2010.
In this article:
• Scenarios for Office 2010 volume activation
• Obtain Office 2010
• Office 2010 volume activation methods
• Deploy Office Activation Technologies
• Install and configure the KMS host
• Configure DNS
• Use KMS for computers running Windows and Office 2010 clients
Differences between Windows and Office activation
The following describes the differences between Windows KMS activation and Office KMS activation as well as between Windows MAK activation and Office MAK activation.
KMS
• The activation threshold for the KMS host is five client computers. Five physical or virtual computers that have Office installed must request activation before KMS clients become activated.
• Only one KMS host key must be installed and activated on the Office KMS host. This KMS host can then activate all Office 2010 products with the KMS client key installed.
• When using slmgr.vbs commands on the KMS host, you must enter the Office 2010 activation ID (bfe7a195-4f8f-4f0b-a622-cf13c7d16864). For more information about the slmgr.vbs script, see Deploy volume activation of Office 2010.
• To ensure that the Office 2010 KMS host key is recognized, you must run KeyManagementServiceHost.exe to install the Office license files.
• Each Office suite or product has its own MAK key. For example, you can activate all applications in the Office 2010 Professional Plus suite, but you must enter a separate MAK key for Microsoft Visio.
Scenarios for Office 2010 volume activation
The purpose of this section is to help users determine a possible scenario that best fits their current or proposed environment and to provide step-by-step guidance for activating their Volume License editions of Office 2010 software. The detailed steps for activation listed in this article apply to all Volume License editions of Office 2010 client products (Office 2010 Professional Plus, Microsoft Visio 2010, and Microsoft Project 2010).
The following scenarios are described in this section:
• Scenario 1: The individual user who wants to activate Office 2010 and get started quickly
• Scenario 2: The IT professional who wants to deploy Office 2010 to five or fewer computers
• Scenario 3: The IT professional who wants to try MAK proxy activation through VAMT 2.0
• Scenario 4: The IT professional who wants to deploy Office 2010 to more than five computers
Scenario 1: The individual user who wants to activate Office 2010 and get started quickly
Perform the steps in the following procedure.
[pic]To activate Office 2010 on a single computer
|1. Open any Office 2010 Professional Plus application. |
|2. Click the File tab. This opens the Microsoft Office Backstage. |
|3. Click Help in the left navigation pane. |
|4. Click the Change product key link and enter the MAK product key provided on the product key page of the Web site where you |
|downloaded Office 2010. |
|5. Select the check box to activate Office 2010 automatically or restart the application to activate Office 2010 by using the |
|activation dialog box. |
[pic]Important:
There are three distinct MAK keys: one for Office 2010 Professional Plus, one for Visio 2010, and one for Project 2010. The previous procedure must be performed separately for each of these products and with the respective MAK key. That is, entering the Office 2010 Professional Plus key results in Office 2010 Professional Plus being activated; entering the Visio 2010 key results in Visio 2010 being activated; entering the Project 2010 key results in Project 2010 being activated.
For more information about how to activate Volume License editions of Office 2010, see Volume activation overview for Office 2010.
Scenario 2: The IT professional who wants to deploy Office 2010 to five or fewer computers
When you deploy Office 2010 to five or fewer computers, use a MAK key to activate Office 2010 through either of the following methods:
• Before installation — Enter a MAK key in either:
• The Office Customization Tool (OCT), or
• The Config.xml file.
• After installation — Enter a MAK key through the Backstage (see Scenario 1).
[pic]To activate Office 2010 by entering a MAK key in the OCT
|1. At the command line, run setup.exe /admin to start the OCT. |
|2. Go to Setup| Licensing and user interface and enter the MAK key in Type a valid 25-character volume license key without any |
|spaces. |
|3. After making any other necessary changes in the OCT, save the .msp file. |
Office 2010 is then installed with the MAK key when users run setup from the network share. Users are prompted to activate Office 2010 over the Internet when they start an Office 2010 application. When the activation succeeds, users see a dialog box confirming activation with Microsoft.
[pic]Note:
This procedure applies only when you are using a MAK key to activate Office 2010. If you are activating Office 2010 through KMS, you do not need to enter a product key in the OCT.
For more information about the OCT, see Customize Setup before installing Office 2010.
[pic]To activate Office 2010 by entering a MAK key in the Config.xml file
|1. Add the following line to the Config.xml file: |
| |
|Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key. |
|2. Replace the PIDKEY value with the product key. |
|3. To apply the settings in Config.xml, at a command prompt, type the following command: |
|Setup.exe /config |
[pic]Note:
You do not need to enter the MAK key in the Config.xml file if you are using KMS activation. For more information about how to use the Config.xml file, see Config.xml file in Office 2010.
Office 2010 is then installed with the MAK key, and users are prompted to activate over the Internet when they start an Office 2010 application. When activation succeeds, users will see a dialog box confirming activation with Microsoft.
[pic]Note:
The Config.xml file is used to configure installation tasks and is used only while you are running the setup utility. It is not installed or cached on user computers. Administrators can edit the Config.xml file to customize the installation. By default, the Config.xml file that is stored in the core product folders (.WW, for example, Enterprise.WW or Pro.WW) directs the setup utility to install that product.
For more information about how to use a MAK key to activate a Volume License edition of Office 2010, see Volume activation overview for Office 2010.
Scenario 3: The IT professional who wants to try MAK proxy activation through VAMT 2.0
[pic]Note:
VAMT 2.0 Beta is available during Office 2010 Beta.
[pic]To activate Office 2010 through a MAK proxy through VAMT 2.0
|1. Download and run VAMT 2.0. |
|2. In VAMT 2.0, under Product Keys, enter the MAK key issued in the Product Key field, and then click Verify. |
|3. Right-click the computer on which you want to install the MAK key, select Install Product Key, select the MAK key, and then |
|click OK. |
|4. To activate Office 2010, right-click the computer name, select Activate, and then Independent Activate. You must provide |
|administrator permissions for this computer. |
For more information about how to activate a Volume License edition of Office 2010 through VAMT2.0, see Volume activation overview for Office 2010.
Scenario 4: The IT professional who wants to deploy Office 2010 to more than five computers
We recommend that KMS activation is used to deploy Office 2010 to more than five computers.
[pic]To activate Office 2010 to more than five computers through KMS
|1. Identify one computer to be your Office 2010 KMS host and download KeyManagementServiceHost.exe from the Web site where you |
|downloaded Office 2010. |
|[pic]Note: |
|Only Windows Server 2003, Windows Server 2008 R2, and Volume License editions of Windows 7 are supported as Office 2010 KMS hosts.|
|2. Run KeyManagementServiceHost.exe and enter the Office 2010 KMS host key when you are prompted. Continue with activating the |
|Office 2010 KMS host. |
|3. If you want the Office 2010 KMS host to publish its SRV record on DNS, skip this step. |
|On the KMS client computer where you installed Office 2010, run cscript ospp.vbs –sethst:, |
|where host name is the name of the Office 2010 KMS host (the computer on which you ran KeyManagementServiceHost.exe). |
|Ospp.vbs is located in the %installdir%\Program Files\Microsoft Office\Office14 folder. For more information about the OSPP |
|script, see Configure the KMS client. |
|4. On the Office 2010 KMS host, open port 1688. |
|Office 2010 KMS clients automatically activate against the host. No additional action is required. Note that five or more Office |
|2010 KMS clients must request activation before they can become activated. |
For more information about how to activate a Volume License edition of Office 2010 through KMS, see Volume activation overview for Office 2010.
Obtain Office 2010
To obtain Office 2010 Beta, download it from an appropriate download site beginning in November 2009.
Office 2010 volume activation methods
There are two methods for activating Volume License editions of Office 2010: Key Management Service (KMS) and Multiple Activation Key (MAK).
KMS activation
KMS enables clients to activate on the local network. To do this, administrators must first set up a KMS host (see Install and configure the KMS host). Office 2010 clients are pre-installed with a KMS client key. A user who is usually connected to the network can activate Office 2010 by connecting to the KMS host on the intranet. The activation process is invisible to the user and requires no user interaction. The computer that is running Office 2010 (the KMS client) can be configured for variable lengths of re-activation and renewal periods. If a KMS client fails to activate, the user will see notification messages 25 days after installation of Office 2010. If KMS clients are absent from the network for longer than 180 days after successful activation, users will see unlicensed notifications when they start Office 2010. However, there will be no functionality loss even if the licenses for KMS clients cannot be renewed. Upon successful activation, users no longer receive notifications.
MAK activation
If a KMS host is not available, the user can activate against Microsoft hosted activation servers, as long as the computer that is running Office 2010 uses a valid MAK key instead of the KMS client key. Administrators can change the product key from the KMS client key to the MAK key through the Office 2010 user interface (UI) or by using a script that calls OSPP WMI providers.
Deploy Office Activation Technologies
You do not need to enter a product key for client computers if you are using KMS as your activation method. This is new to Office 2010. All Volume License editions of Office 2010 already have the KMS client key pre-installed. For information about how to set up a KMS host, see Install and configure the KMS host.
You can use the following methods to enter a MAK for a client. Because different products require different MAK keys, first verify that the MAK is correct for the product.
• Enter the MAK in the Office Customization Tool (OCT).
• Enter the MAK in the Config.xml file.
• Switch to MAK after installation by using the Backstage view.
• Use VAMT 2.0 (available after Office 2010 Beta).
[pic]To enter a MAK in the Office Customization Tool (OCT)
|1. In the OCT under Setup | Licensing and user interface, enter the MAK key (five sets of five numbers or characters) in the Type |
|a valid 25-character volume license key with no spaces field and press Enter. |
|2. After making any other necessary changes in the OCT, save the MSP file. |
Remember that you do not need to enter a product key in the OCT if you are using KMS activation. For more information about the OCT, see Customize Setup before installing Office 2010.
[pic]To enter a MAK key in the Config.xml file
|1. Add the following line to the Config.xml file: |
| |
|Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key. |
|2. Replace the PIDKEY value with the product key. |
|3. To apply the settings in Config.xml, at a command prompt, type the following command: |
|Setup.exe /config |
You do not need to enter the MAK key in the Config.xml file if you are using KMS activation. For more information about how to use the Config.xml file, see Config.xml file in Office 2010.
[pic]To switch to a MAK after installation
|• Users can manually switch the pre-installed product key (the KMS client key) to a MAK key after Office 2010 is installed. Only |
|administrators can perform this operation, unless the required registry key that allows non-administrators is set appropriately. |
|If HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform\UserOperations is set to 1, administrator permissions |
|are not required for product key entry. Only an administrator can create and set this registry key. |
[pic]To create a registry key for manual MAK activation
|• An administrator can create a registry key that allows a standard user (non-administrator) to apply a MAK key and activate an |
|Office 2010 application. This means that a standard user can switch a KMS client to MAK activation, manually activate a computer, |
|and, if it is necessary, replace an existing MAK with a new MAK key. By default, all volume license editions of Office 2010 |
|disable this behavior. Adding the following line to the Config.xml file will enable this behavior: |
| |
|• Or, you can set the following registry key to enable or disable standard user (non-administrator) activation: |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform]Enable Standard User Activation: |
|"UserOperations"=dword:00000001 (Office 2010 retail products default setting) |
|Disable Standard User Activation: "UserOperations"=dword:00000000 (Office 2010 volume license products default setting) |
[pic]To enter a MAK manually
|• Open an Office 2010 application. |
|• Click the File tab. This opens the Backstage. |
|• Click Help. |
|• Click the Change product key link and enter the MAK product key that is provided on the product key page of the Web site where |
|you downloaded Office 2010. |
Use the previous procedure if an Office 2010 client was installed with the default KMS client key for KMS activation and you want the client to use MAK activation instead.
If you must do this on many computers, you can use a computer that is hosting VAMT 2.0 to select the computers that you need to change and push the MAK via remote Windows Management Infrastructure WMI calls. Clients must be connected to the network to receive a MAK with this method. For more information about VAMT 2.0, see the VAMT 2.0 documentation that will be included with VAMT 2.0 (not available during Office 2010 Beta).
Activating MAK clients through a proxy server
Activation over the Internet might be blocked if the proxy server requires user authentication. In Microsoft Internet Security and Acceleration (ISA) Server, this setting is called basic authentication. Because activation requests do not present the user's credentials to the proxy server, we recommend that you do not use basic authentication with ISA Server or other proxy servers.
Install and configure the KMS host
Only the following operating systems can serve as the KMS host:
• Windows Server 2003 or later versions
• Volume License editions of Windows 7
• Windows Server 2008 R2
[pic]Important:
The KMS host key for Office 2010 is not specific to a particular operating system. It is designed to be used on any of the operating systems that were mentioned earlier, including both 32-bit and 64-bit editions.
The following operating systems are not supported as the KMS host:
• Windows Vista or a later version
• Windows Server 2008 or a later version
For more information, see Volume Activation 2.0 for Windows Vista and Windows Server 2008 ().
Manually assign the KMS host on the KMS client
Administrators can manually assign a KMS host to KMS clients by using KMS host caching. Manually assigning a KMS host disables auto-discovery of KMS on the KMS client. A KMS host is manually assigned to a KMS client by configuring the registry key HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform. The KMS host name is KeyManagementServiceName (REG_SZ), and the port is KeyManagementServicePort (REG_SZ).
[pic]To install a KMS host on Windows Server 2003
|1. Download Key Management Service 1.1 (x86) for Windows Server 2003 SP1 and Later |
|(). Or, for 64-bit Windows Server 2003, download Key Management Service 1.1 (x64) for|
|Windows Server 2003 SP1 and Later (). Extract these files: KMSW2K3.exe and |
|WindowsServer2003-KB948003-x86-ENU.exe. |
|2. At a command prompt, run KMSW2K3.exe to install SPPSVC, and then run WindowsServer2003-KB948003-x86-ENU.exe to update KMS to |
|version 1.1. |
|3. To install the operating system-specific license files, download KeyManagementServiceHost.exe from the Web site where you |
|downloaded Office 2010. |
|4. Run KeyManagementServiceHost.exe. When prompted, enter the Microsoft Customer Service Volume License Key (KMS host key). |
|5. If you have a firewall enabled, open TCP port 1688, which is the default port number. |
[pic]To install a KMS host on Windows 7 or Windows Server 2008 R2
|1. To install the operating system-specific license files, download KeyManagementServiceHost.exe from the Web site where you |
|downloaded Office 2010. |
|2. Run KeyManagementServiceHost.exe. When prompted, enter the Microsoft Customer Service Volume License Key (CSVLK). |
|3. If you have a firewall enabled, follow these steps to allow KMS through the firewall: |
|a. Open Control Panel and then click the Windows Firewall icon. |
|b. Click the Allow a program through Windows Firewall link. |
|c. Click the Change Settings button. |
|d. Check the Key Management Service box and then click OK. |
To verify that the KMS host is configured correctly, check the KMS count to see whether it is increasing. At a command prompt on the KMS host, enter:
slmgr.vbs /dli 86f3489b-e730-45ee-ad42-039a64c82ba4
This displays the current KMS count for the Office 2010 KMS host. Administrators can also check the KMS log that is in the Applications and Services Logs folder for event ID 12290, the ID for KMS-related activity. The KMS log records activation requests from KMS clients. Each event displays the name of the computer and the time stamp of each activation request.
Because the KMS host service automatically stops, you might encounter this error when you run KeyManagementSystemHost.exe during the Office 2010 Beta:
Error: The Software Protection Platform service is not running: sppsvc State: Stopped
If you receive this error, perform the following:
1. Open a command prompt with administrator permissions (click Start, enter cmd.exe, right-click and select Run as Administrator).
2. At the command prompt, enter:
net start sppsvc
3. Re-run KeyManagementSystemHost.exe.
Alternately, you can perform the following:
1. Right click My Computer and select Manage.
2. Under Services and Applications, select Software Protection Service.
3. Click Start and then OK to start the service.
4. Re-run KeyManagementSystemHost.exe.
Configure the KMS host
Software License Manager (slmgr.vbs) is a script that is used to configure and retrieve Volume Activation information. The script can be run locally on the target computer or remotely from another computer. However, it should be run from an elevated command prompt in Windows Server 2008 R2 (if a standard user runs slmgr.vbs, some license data might be missing or incorrect, and many operations are prohibited).
The slmgr.vbs script can use wscript.exe or cscript.exe, and administrators can specify which script engine to use. If no script engine is specified, slmgr.vbs runs by using the default script engine, wscript.exe.
The Software Licensing Service must be restarted for any changes to take effect. To restart the Software Licensing Service, use the Microsoft Management Console (MMC) Services snap-in or run the following command at an elevated command prompt (in Windows Server 2008 R2):
net stop sppsvc && net start sppsvc
The slmgr.vbs script requires at least one parameter. If the script is run that has no parameters, it displays help information. The following table lists slmgr.vbs command-line options, and a description of each. Most of the parameters in the table configure the KMS host. However, the parameters /sai and /sri are passed to KMS clients after they make contact with the host. The general syntax of slmgr.vbs is as follows:
slmgr.vbs /parameter
slmgr.vbs [ComputerName] [User] [Password] [Option]
ComputerName Name of remote computer. If a computer name is not passed local computer is used.
User Account with required permission on remote computer.
Password Password for the account. If a User account and password are not passed, current credentials are used.
Option Options are shown in the following table.
|Option |Description |
|/ipk [ProductKey] |Installs the product key for the KMS host or the application |
| |identified by the ActivationID when provided |
|/ato [ActivationID] |Activates the KMS host for Windows (default), or the application |
| |identified by the application ID when provided. The Office |
| |application ID is |
| |86f3489b-e730-45ee-ad42-039a64c82ba4. |
|/dlv [ActivationID] |Displays detailed license information for Windows (default), or the |
| |application identified by the application ID when provided. The |
| |Office application ID is |
| |86f3489b-e730-45ee-ad42-039a64c82ba4. |
|/dli [ActivationID] |Displays license information for Windows (default), or the |
| |application identified by the application ID when provided. The |
| |Office application ID is |
| |86f3489b-e730-45ee-ad42-039a64c82ba4. |
|/sprt [PortNumber] |Sets the TCP communications port on a KMS host. Replaces PortNumber |
| |with the TCP port number to use. The default setting is 1688. |
|/cdns |Disables automatic DNS publishing by a KMS host. |
|/sdns |Enables automatic DNS publishing by the KMS host. |
|/cpri |Lowers the priority of KMS host processes. |
|/sai [ActivationInterval] |Changes how often a KMS client attempts to activate itself when it |
| |cannot find a KMS host. Replaces ActivationInterval with a number of |
| |minutes. The default setting is 120. |
|/sri [RenewalInterval] |Changes how often a KMS client attempts to renew its activation by |
| |contacting a KMS host. Replaces RenewalInterval with a number of |
| |minutes. The default setting is 10080 (7 days). This setting |
| |overrides the local KMS client settings. |
Configure DNS
KMS hosts automatically publish their existence by creating SRV RRs on the DNS server. If there is only one KMS host and dynamic update, no action is required for the KMS host to create the SRV RR that publishes the KMS service location.
However, If there is more than one KMS host, only the first KMS host can create an SRV RR. Subsequent KMS hosts cannot change or update SRV RRs unless the default permissions on the DNS server are changed.
Changing the default permissions on the DNS server requires administrative permissions in the domain, and the KMS hosts must all belong to the same AD DS domain. Create a global security group in AD DS for your KMS hosts. Add each KMS host to the new security group, and set the permissions on the DNS server to allow updates by members of the newly created security group.
Use KMS for computers running Windows and Office 2010 clients
When you use KMS to activate both Windows and Office 2010 clients, you have the following options for Office 2010 Beta:
• Use separate KMS hosts for computers running Windows and Office 2010 clients.
• Use the same KMS host on a computer that is running Windows Server 2003.
• Use the same KMS host on a computer that is running Windows 7 or Windows Server 2008 R2.
For information about the operating systems that support KMS hosts for Office 2010, see Install and configure the KMS host.
Configure the KMS client
The Office Software Protection Platform (OSPP) script (ospp.vbs) enables you to configure the KMS client. The script is located in the %installdir%\Program Files\Microsoft Office\Office14 folder. Running ospp.vbs requires the cscript.exe script engine. The general syntax for ospp.vbs is as follows:
cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]
ComputerName Name of remote computer. If a computer name is not provided, the local computer is used.
User Account with required permission on the remote computer.
Password Password for the account. If a user account and password are not provided, the current credentials are used.
Option Options are shown in the following table.
|Option |Description |
|-act |Activates Office 2010. |
|-inpkey:value |Installs a product key (replaces existing key). Value parameter is |
| |the product key. |
|-unpkeys:value |Uninstalls a product key. Value parameter is the last five characters|
| |of the product key to uninstall. |
|-inslic:value |Installs license. Value parameter is the license location path. |
|-dstatus |Displays license information for installed licenses. |
|-dinstid |Displays Installation ID for offline activation. |
|-actcid:value |Activates product with user-provided Confirmation ID. Value parameter|
| |is the confirmation ID. |
|-sethst:value |Sets KMS host name to activate against. Value parameter is the KMS |
| |host name. |
|-setprt:value |Sets KMS port. Value parameter is the KMS port number. |
|-remhst |Removes KMS host name (sets port to default). |
The following is an example of how you can configure an Office 2010 client:
1. On the computer in which Office 2010 is installed, run the command prompt with administrator permissions.
2. Install a license by entering the following at the command prompt:
cscript ospp.vbs -inslic:
3. Install a product key by entering the following at the command prompt:
cscript ospp.vbs -inpkey:
4. Activate Office 2010 by entering the following at the command prompt:
cscript ospp.vbs –act
Separate KMS hosts for computers running Windows and Office 2010 clients
If you are using a separate KMS host for Office 2010 Beta, we recommend that you set the host name and port number registry keys on the client computers. This ensures that Office 2010 KMS clients contact the correct KMS host. Windows KMS clients can still find the Windows KMS host through DNS. You can do this by running ospp.vbs with the –sethst and –setprt parameters, which set the following registry values:
• For the new Office 2010 KMS host name, the REG_SZ value is set for the following registry key:
HKLM\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName
• If you want to set a different port, for the new port number on Office 2010 KMS clients, the REG_SZ value is set for the following registry key:
HKLM\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServicePort
Same KMS host on a computer running Windows Server 2003
If you are already using a computer that is running Windows Server 2003 as your Windows KMS host and you want to co-host the Office 2010 Beta KMS host, follow the steps in To install a KMS host on Windows 7 or Windows Server 2008 R2, because you do not have to install the Office 2010 KMS host service on Windows Server 2003. When you move to the final version of Office 2010, you will need to download and run the updated KeyManagementServiceHost.exe file and obtain and activate the KMS host key for the final version of Office 2010. You cannot activate the final version of Office 2010 with the same KMS host file and key that was used for Office 2010 Beta.
Same KMS host on a computer running Windows 7 or Windows Server 2008 R2
If you are currently using an RC build of a Volume License edition of Windows 7 or using Windows Server 2008 R2 as a Windows KMS host and you want to co-host an Office 2010 KMS host, follow the steps in To install a KMS host on Windows 7 or Windows Server 2008 R2. If you migrate to a release build of Windows 7 or Windows Server 2008 R2, remember that this computer should not be shut down, because it is needed to activate Office 2010. When you are ready to activate the final version of Office 2010, we recommend that you set up the Office 2010 KMS host on a computer that is running the final release of Windows 7 or Windows Server 2008 R2. We recommended that you do not activate Office 2010 through a KMS host on a computer that is running pre-release versions of Windows 7 or Windows Server 2008 R2.
See Also
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
Tools to configure client computers in Office 2010
Troubleshoot volume activation for Office 2010
Office 2010 Volume Activation forum ()
Office 2010 forums ()
Prepare the infrastructure for Office 2010
This section provides information about how to create a network installation point by using the Microsoft Office 2010 source files.
In this section:
|Article |Description |
|Create a network installation point for Office 2010 |Provides information and procedures to create, replicate, and secure |
| |a network installation point for the deployment of Office 2010. |
Create a network installation point for Office 2010
This article describes how to create, replicate, and secure a network installation point for the deployment of Microsoft Office 2010. Typically, this is the first step in a corporate deployment of Office 2010. To do this, you copy all the source files from the Office installation 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 software deployment tool, such as Microsoft System Center Configuration Manager 2010.
In this article:
• Create the network installation point
• Replicate the network installation point
• Secure the network installation point
Create the network installation point
Use the following procedure to create a network installation point.
[pic]To create a network installation point
|1. Create a folder for the Office source files at a location that can be easily accessed on the server. For example: |
|\\server\share\Office14 |
|[pic]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 the network installation point. |
|4. If you deploy multiple language versions of Office 2010, copy each language pack that you want from the source media to the |
|installation point. When you are prompted to overwrite duplicate Setup files, click No. |
|[pic]Note: |
|In Office 2010, core Setup files are shared among all Office products and language packs. Because these core Setup files are |
|identical, there is no reason to overwrite the files if you add language packs, for example. Additionally, by not overwriting |
|Setup files, the network installation point remains online and available to users while you add files. |
|5. If you deploy multiple Office 2010 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. |
|Or, you can enter the /adminfile option at the command prompt to specify a Setup customization file. |
|7. If users are installing Office 2010 after product updates are released, store those .msp files in the Updates folder. |
The amount of space that is required on the network installation point varies by product and by language. The following table shows approximate space requirements for English versions of Office 2010 suites that are typically installed in enterprise organizations. These figures account for both the installed product and the installation files that are stored in the local installation source.
|Product |Approximate space required |
|Microsoft Office Professional 2010 |Approximately 3 gigabytes (GB) |
|Microsoft Office Professional Plus 2010 |Approximately 3 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.
[pic]Note:
Unlike in versions of Microsoft Office products earlier than the 2007 Microsoft Office system, in Office 2010 (and 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 Office 2010 and in the 2007 Office system, all installations occur from the compressed source.
Replicate the network installation point
In many enterprise organizations, the network installation point is the location from which users first install Office. After Office 2010 is installed, users do not typically have 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. However, if the local source is corrupted or deleted, Setup returns to the original network source to re-create the local source on the user's computer.
We recommend that you replicate the network source to multiple locations for the following reasons:
• Availability If you create multiple network installation points (which can be in the same physical location), you help 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. If you set up a duplicate network installation point at the remote locations, Office source files travel over the slow network connection only one time, and after that, users have access to a closer network source.
• Consistency If you create one network installation point with all the customizations that you want and then duplicate 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 2010, regional offices can apply additional customizations to the replicated network installation points and can customize Office 2010 for their unique region-specific requirements.
[pic]To specify additional network sources
|1. Start the Office Customization Tool (OCT) by running Setup with the /admin command-line option. |
|2. In the Setup section, click Additional Network Sources, and then click Add. In the Add Network Server Entry dialog box, enter |
|the path of the location where you plan to copy the network installation point, and then click OK. |
|You can add as many additional source locations as you want. |
|3. Save the Setup customization file (.msp file) that is generated by the OCT in the Updates folder at the root of the network |
|installation point. |
|4. Copy the complete folder structure of the network installation point to the locations that you specified in the Setup |
|customization file. |
|Users who install Office 2010 from any of these network installation points have access to the backup network sources. Setup |
|checks these sources automatically when an alternative source is required. |
Secure the network installation point
To help make the network installation point for Office more secure, follow these recommended best practices:
• Make sure that access to source files is read-only. (The Setup.xml and Package.xml files, such as ProPlusWW.xml for Microsoft Office Professional 2010, are digitally signed and cannot be modified.)
• Save all customization files that you create as read-only. These include Setup customization files and custom Config.xml files.
• If you are centralizing log files on the network, make sure that users have read/write permission to that location.
• Make sure that all users have administrative permissions before the users install Office 2010. You can do this by using your existing software deployment infrastructure.
As with any deployment of Office, test all the customizations and deployment in a non-production environment as part of the deployment pilot tests before you deploy Office 2010 to users in the organization.
See Also
Office Customization Tool in Office 2010
Customize the installation for Office 2010
This section provides information about the customization process and links to resources to help you customize a client installation of Microsoft Office 2010.
In this section:
|Article |Description |
|Customization overview for Office 2010 |Provides a summary of the customization tools and methods for Office |
| |2010. |
|Customize setup for Office 2010 |Provides information and procedures to help you customize the |
| |installation of Office 2010. |
|Customize specific features in Office 2010 |Provides information and procedures to help you customize language |
| |setup and settings in Office 2010. |
|Configure security for Office 2010 |Provides information and procedures to configure security settings |
|( Office 2010 by using the Office Customization Tool (OCT) and |
|c9165(Office.14).aspx) |Group Policy. |
|Configure Information Rights Management in Office 2010 |Provides information and procedures to restrict permission to content|
|( and e-mail messages in Office 2010 by using Information |
|6ce9d(Office.14).aspx) |Rights Management (IRM). |
|Configure Outlook 2010 |Provides information and procedures to configure Microsoft Outlook |
| |2010. This includes how to configure and use Outlook Anywhere, Cached|
| |Exchange Mode, and Microsoft Exchange Server send/receive settings. |
|Configure SharePoint Workspace 2010 |Provides information and procedures to configure and customize |
| |Microsoft SharePoint Workspace 2010. This includes how to test |
| |SharePoint Workspace connections. |
Customization overview for Office 2010
This article provides a summary of customization tools and methods for Microsoft Office 2010. To customize an installation of Office 2010, administrators can use the following tools: the Office Customization Tool (OCT), the Config.xml file, or the Setup command-line options.
To configure user and computer settings, administrators use either the OCT or Group Policy, depending on their business requirements. Administrators can use the OCT to provide initial default values. However, users can change the settings after Office is installed. To enforce settings, administrators must use Group Policy. For more information, see Configure user and computer settings.
In this article:
• Office Customization Tool
• Config.xml file
• Setup command-line options
• Configure user and computer settings
• Office 2010 licensing and activation
• Summary of client customization tasks
Office Customization Tool
The Office Customization Tool (OCT) is part of the Setup program and is the primary tool for most customizations. The OCT saves customizations in a Setup customization (.msp) file, which is applied at either Setup time or during a maintenance mode operation. After you create a network installation point and before you install Office 2010, use the OCT to customize the installation. To start the OCT, click Start, click Run, browse to the root of the network installation point that contains the Office 2010 source files, and type the following at the command prompt: setup.exe /admin. For example: \\server\share\Office14ProPlus\setup.exe /admin.
In Office 2010, two architecture-specific versions of the OCT are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
Administrators use the OCT to customize the following areas:
• Setup Used to specify default installation location and default organization name, additional network installation sources, the product key, end-user license agreement, display level, earlier versions of Office to remove, custom programs to run during installation, security settings, and Setup properties.
• Features Used to configure user settings and to customize how Office features are installed.
• Additional content Used to add or remove files, add or remove registry entries, and configure shortcuts.
• Outlook Used to customize a user's default Outlook profile, specify Exchange settings, add accounts, remove accounts and export settings, and specify Send\Receive groups.
For more information about how to use the OCT, see the following resources:
• Office Customization Tool in Office 2010
• Customize Office 2010
• Customize Setup before installing Office 2010
• Configure user settings for Office 2010
• Configure feature installation states for Office 2010
• Configure Outlook 2010
• Import an Office 2010 Setup customization file
Administrators can also configure some installation options by using the Config.xml file.
Config.xml file
The Config.xml file is used to specify installation options, and it runs only during setup. The Config.xml is not installed or cached on users’ computers. The Config.xml file that is stored in the core product folders (core_product_folder_name.WW folder such as ProPlus.WW for Microsoft Office Professional Plus 2010) directs Setup to install that product. If the network installation point contains multiple Office 2010 products, you can use the /config command-line option when you run Setup.exe to specify the path of the Office 2010 product that you want to install; if you do this, it will prevent Setup from prompting you about which product to install. For more information about Setup commands, see Setup command-line options for Office 2010.
If you use both an OCT Setup customization (.msp) file and the Config.xml to customize the installation, the settings that you specify in Config.xml take precedence over those in the Setup customization file. The Config.xml file in Office 2010 article provides detailed information about the installation options and indicates if a setting has a corresponding OCT setting.
You can also use the Config.xml file for maintenance operations such as adding or removing features, and repairs and uninstalls. To do this, you must run Setup again from the original source.
You can use the Config.xml file to configure installation options such as the following:
• Specify the path of the network installation point.
• Select the products to install.
• Customize Setup options, including logging and the location of the Setup customization file and software updates.
• Specify installation options, such as user and company name.
• Copy the Local Install Source (LIS) to the user's computer without installing Office.
• Add or remove languages from the installation.
Setup command-line options
Administrators can also use Setup.exe command-line options to perform the following tasks:
• Run the OCT to create a Setup customization (.msp) file.
• Specify a path of a specific Setup customization file or to the folder where you store Office 2010 customization files.
• Specify the Config.xml file that Setup uses during the installation.
• Run Setup in maintenance mode and make changes to an existing Office installation.
• Run Setup to repair the specified product from the user's computer.
• Run Setup to remove the specified product from the user's computer.
The following table lists the commands that Setup supports.
|Command |Description |
|/admin |Runs the OCT to create or modify a Setup customization file (.msp |
| |file). |
|/adminfile [path] |Applies the specified Setup customization file to the installation |
| |and can be used only for initial installations. You can specify a |
| |path of a specific customization file (.msp file) or to the folder |
| |where you store customization files. |
|/config [path] |Specifies the Config.xml file that Setup uses during the |
| |installation. By default, the Config.xml file that is stored in the |
| |core product folder directs Setup to install that product. For |
| |example, the Config.xml file in the ProPlus.WW folder installs Office|
| |Professional Plus 2010. |
|/modify [ProductID] |Used with a modified Config.xml file to run Setup in maintenance mode|
| |and make changes to an existing Office installation. For example, you|
| |can use the /modify option to add or remove features. Look up the |
| |value of [ProductID] in the Setup.xml file for the product that you |
| |want to modify. |
|/repair [ProductID] |Runs Setup to repair the specified product from the user’s computer. |
| |Look up the value of [ProductID] in the Setup.xml file for the |
| |product that you want to modify. |
|/uninstall [ProductID] |Runs Setup to remove the specified product from the user’s computer. |
| |Look up the value of [ProductID] in the Setup.xml file for the |
| |product that you want to modify. |
For more detailed information about Setup commands, see Setup command-line options for Office 2010.
Configure user and computer settings
As mentioned previously, depending on whether administrators must enforce user settings or whether they want to allow users to modify the settings after the installation, administrators use either Group Policy or the OCT. The majority of the Group Policy and OCT settings for Office are user settings. Most of the Office policy settings have a corresponding OCT setting.
Group Policy and the OCT can be used to configure user and computer settings for the following Office applications:
• Microsoft Access 2010
• Microsoft Excel 2010
• Microsoft InfoPath 2010
• Microsoft Office 2010 System
• Microsoft OneNote 2010
• Microsoft Outlook 2010
• Microsoft PowerPoint 2010
• Microsoft Project 2010
• Microsoft Publisher 2010
• Microsoft SharePoint Designer 2010
• Microsoft SharePoint Workspace 2010
• Microsoft Visio 2010
• Microsoft Word 2010
Configuring user and computer settings by using Group Policy
Group Policy is an infrastructure that administrators can use to implement specific computing configurations for users and computers. Policy settings can also be applied to member servers and domain controllers within the scope of an Active Directory forest. Administrators use Group Policy to define configurations once and then rely on the operating system to enforce that state.
Group Policy settings are contained in Group Policy objects (GPOs), which are linked to selected Active Directory Domain Services (AD DS) containers — sites, domains, or organizational units (OUs). The settings within GPOs are evaluated by the affected targets using the AD DS hierarchical container structure.
The Group Policy infrastructure consists of a Group Policy engine and several individual extensions. These extensions are used to configure Group Policy settings, either by modifying the registry through the Administrative Templates extension, or by configuring Group Policy settings for security settings, software installation, folder redirection, Internet Explorer Maintenance, wireless network settings, and other areas. The Office policy settings are contained in Administrative Template (.adm or .admx and .adml) files.
To mandate Office settings configurations for users and computers, the administrator uses Group Policy, and the operating system enforces those policy settings. For example, use Group Policy to mandate security settings to help counter attacks that target e-mail and desktop documents. In an Active Directory-based environment, administrators apply policy settings to groups of users and computers in a site, domain, or OU to which a GPO is linked. True policy settings are written to the approved registry key locations for policy, and these settings have access control list (ACL) restrictions that prevent non-administrator users from changing them. Administrators use Group Policy to create highly restricted or lightly managed desktop configurations, depending on their specific business and security requirements. Group Policy settings have precedence over OCT settings.
The following table lists the approved registry key locations for Group Policy settings. Users cannot change or disable these settings.
|For computer policy settings |For user policy settings |
|HKLM\Software\Policies (the preferred location) |HKCU\Software\Policies (the preferred location) |
|HKLM\Software\Microsoft\Windows\CurrentVersion\Policies |HKCU\Software\Microsoft\Windows\CurrentVersion\Policies |
For Office 2010, user-specific policy settings are stored in the HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0 subkey. Computer-specific policies are stored in the HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\14.0 subkey. By default, both policy subkeys are locked to prevent users from modifying them.
Group Policy settings can be set to one of three states:
• Not configured The policy setting is not enforced.
• Enabled The policy setting is activated. Additional settings appear in the Properties page for some policy settings. These settings determine what happens when the policy setting is enforced.
• Disabled For most policy settings, the Disabled state enforces the opposite behavior to that of the Enabled state. For example, if Enabled forces a feature's state to Off, Disabled forces the feature's state to On.
For more information about using Group Policy, see Enforce settings by using Group Policy in Office 2010. ((Office.14).aspx)
Configuring user and computer settings by using the Office Customization Tool
To specify initial default values of Office application settings for users and computers, administrators use the OCT to specify settings in a Setup customization .msp file. Users can modify most of the settings after the installation. This is because the OCT configures settings in publicly available portions of the registry, such as HKEY_CURRENT_USER\Software\Microsoft\Office\14.0 for user settings and HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0 for computer settings.
OCT settings can be set to one of the following states:
• Not Configured The setting remains as it is.
• Enabled The setting is modified based on your choices in the Properties page for the setting.
• Disabled The setting is disabled. Disabling an option might be different from not configuring the option. See the description of the specific option for more information.
Office 2010 licensing and activation
Microsoft policy requires the activation of all editions of Office 2010 client software, including those obtained through a Volume Licensing program. This requirement applies to Office 2010 running on both physical computers and virtual computers. Activation is not required for any Office 2010 server products: Microsoft SharePoint Server 2010 and Microsoft Project Server 2010, or any version of Microsoft Exchange Server. In Office 2010, the activation method uses Office Activation Technologies, based on the Software Protection Platform introduced in Windows Vista and Windows Server 2008 families.
You can use the following methods to activate Office 2010 by using Office Activation Technologies, which are the same methods that are used for Windows Vista and later versions of Windows:
• Key Management Service (KMS). KMS uses a KMS host key to activate a KMS host computer and establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. Office 2010 enterprise deployments that are using Key Management Service (KMS) activation do not require a product key entry because all Volume License editions of Office 2010 have a KMS client key pre-installed. However, administrators must configure a KMS host computer with a KMS host key to be activated and to establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. KMS is the default option for Volume Licensed clients.
• Multiple Activation Key (MAK). With a MAK, clients activate Office 2010 online with the Microsoft hosted activation servers or by telephone. MAK is appropriate for organizations with computers that are not connected to the corporate network for long periods of time, such as portable computers. If you use the MAK method, Office 2010 must be installed with a MAK key instead of the default KMS client key used in Volume License editions of Office 2010. MAK activation by telephone will be supported later when the product releases (RTM).
• A combination of KMS and MAK.
For detailed information about licensing and activation of Office 2010 clients, we recommend that you read the following articles before you customize the installation: Volume activation overview for Office 2010, Plan volume activation of Office 2010, Volume activation quick start guide for Office 2010, Deploy volume activation of Office 2010, Tools to configure client computers in Office 2010.
Summary of client customization tasks
The following illustration summarizes the tasks to perform to customize an Office 2010 client installation. As with any software deployment, your Office 2010 client deployment plans must include testing in a non-production environment and conducting pilot tests with small groups of users before you deploy to all users in the organization.
[pic]
The following resources provide information about planning and about customization tasks for Office 2010 client installations:
• Plan for volume activation of Office 2010
• Configure and deploy volume activation of Office 2010
• Prepare the infrastructure for Office 2010
• Customize setup for Office 2010
• Configure Outlook 2010
• Choose an option for deploying Office 2010
See Also
Office Customization Tool in Office 2010
64-bit editions of Office 2010
Config.xml file in Office 2010
Setup command-line options for Office 2010
Enforce settings by using Group Policy in Office 2010 ((Office.14).aspx)
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
Customize setup for Office 2010
This section provides information to help you customize an installation Microsoft Office 2010.
In this section:
|Article |Description |
|Customize Office 2010 |Provides information and procedures to customize an installation of |
| |Office 2010. |
|Customize Setup before installing Office 2010 |Provides information and procedures to customize Setup before |
| |installing Office 2010. |
|Configure feature installation states for Office 2010 |Provides information and procedures to customize Setup to configure |
| |feature installation states. |
|Configure user settings for Office 2010 |Provides information and procedures to configure Office 2010 user |
| |settings by using the Office Customization Tool (OCT). |
|Create different configurations of Office 2010 for different groups |Provides information and procedures to create unique configurations |
|of users |of Office 2010 for each group. |
|Import an Office 2010 Setup customization file |Provides information and procedures to import an OCT Setup |
| |customization file (.msp file) in Office 2010. |
|Configure a silent installation of Office 2010 by using Config.xml |Provides information and procedures for configuring a silent |
| |installation by using the Config.xml file. |
|Run arbitrary commands with installations of Office 2010 |Provides information and procedures to customize Setup to run an |
| |arbitrary command or a lightweight executable to install an Office |
| |2010 product. |
|Create custom configurations of Office 2010 |Describes how to deploy an initial customized installation of Office |
|( to users in an organization. |
|08b82(Office.14).aspx) | |
|View XML content from Office Customization Tool customization files |Provides a sample Microsoft Visual Basic script that administrators |
|( use to view the settings that are stored in Setup customization |
|16a66(Office.14).aspx) |.msp files. |
Customize Office 2010
This article provides information and procedures to customize an installation of Microsoft Office 2010. After you create a network installation point, but before you install Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file to configure the installation for 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.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
[pic]Note:
Office 2010 does not support side-by-side installations of 64-bit and 32-bit Office, including across applications. For example, there is no support for side-by-side installations of the 2007 Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit. You cannot use the Office 2010 customization tools to configure side-by-side installations or customizations of 64-bit and 32-bit Office. For example, you cannot create a custom side-by-side installation with 64-bit Microsoft Office Professional 2010 and 32-bit Microsoft Visio 2010 single image. For more information about 64-bit Office, see 64-bit editions of Office 2010.
Customize Office
[pic]To customize Office by using the OCT
|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 then 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 then select 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 articles provide more information about how to customize specific aspects of the installation:
• To customize the default behavior of Setup during installation, see Customize Setup before installing Office 2010.
• To customize which Office features are installed on the user's computer, see Configure feature installation states for Office 2010.
• To customize the user's default environment during installation, see Configure user settings for Office 2010.
• To configure Outlook options, see the Configure Outlook 2010 articles.
For complete information about the OCT, see Office Customization Tool in Office 2010.
The following customizations can only be made using the Config.xml file:
• Specifying the path of 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.
• Copying the local installation source (LIS) to the user's computer without installing Office.
• Adding or removing languages from the installation.
For more information about how to use the Config.xml file, see Config.xml file in Office 2010.
See Also
Setup architecture overview for Office 2010
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Volume activation quick start guide for Office 2010
Deploy volume activation of Office 2010
Office Customization Tool in Office 2010
Config.xml file in Office 2010
64-bit editions of Office 2010
Import an Office 2010 Setup customization file
Customize Setup before installing Office 2010
This article provides required information and procedures to customize Setup before installing Microsoft Office 2010. In Office 2010 (as in the 2007 Microsoft Office system), Setup controls the complete installation. This includes processes that Windows Installer handled in Office versions earlier than the 2007 Office system. Customizing the default behavior of Setup lets you 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.
We recommend that you read the Volume activation overview for Office 2010, Plan volume activation of Office 2010, and Configure and deploy volume activation of Office 2010 articles before customizing Setup.
In this article:
• Customize Setup
• Install Office silently
Customize Setup
To customize how Setup manages the installation process, use the Office Customization Tool (OCT) to create a Setup customization (MSP) file. Setup applies this file when users install Office on their computers.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
[pic]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. For |
|more information, see Create a network installation point for Office 2010. |
|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 of 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 of 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. The following options are available: |
|• Use KMS client key – A product key entry is not required for enterprise deployments that are using Key Management Service (KMS) |
|activation because all Volume License editions of Office 2010 have a KMS client key pre-installed. KMS is one of the methods that |
|are provided by Office Activation Technologies for activating products licensed under Microsoft Volume Licensing programs. Only a |
|KMS host computer needs a KMS host key to be activated and to establish a local activation service in your environment. Office |
|2010 connects to the local KMS host for activation. By default, the Use KMS client key option is selected. |
|For more information about the licensing options for Office 2010, see Volume activation overview for Office 2010. For information |
|about how to configure the KMS host, see Install and configure the KMS host in Deploy volume activation of Office 2010. |
|• Enter another product key – You can enter a valid Multiple Activation Key (MAK) key in the OCT by using the Enter another |
|product key entry. A MAK key is another method that Office Activation Technologies provide for activating products licensed under |
|Microsoft Volume Licensing programs. With a MAK, clients activate Office 2010 online by using the Microsoft hosted activation |
|servers or by telephone. |
|To use a MAK key, in the Enter another product key text box, enter the MAK key (twenty-five numbers or characters) without spaces.|
|For more information about using a MAK key, see Deploy volume activation of Office 2010. |
|10. 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 that |
|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 article. |
|[pic]Note |
|In enterprise deployments, we recommend 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 being used. 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 Office 2010. |
|If you set Display level to Basic and select the Suppress modal option, users may be prompted if any Office files are being used. |
|Setting Display level to None prevents prompting users in these 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. Click Save on the File menu, and then click 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.
[pic]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 element. For more information, see Config.xml file in Office 2010.
Install Office silently
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 gives users choices during the installation. If you are distributing a customized configuration, we recommend that you limit how much users interact with Setup. The installation continues 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 Office 2010.
If you are using a deployment tool such as Microsoft System Center Configuration Manager 2010 or Microsoft Systems Management Server (SMS) to deploy Office while users are not logged on to the network, set the display level to None, which installs Office without displaying any Setup user interface.
[pic]Note:
When you install Office silently, you must provide a valid product key. If the product key is missing, Setup logs an error and exits. As mentioned previously, if you are using KMS activation, a product key entry is not required because all Volume License editions of Office 2010 have a KMS client key pre-installed; however, if you are using MAK, you must enter the MAK key. If you do not accept the license terms on behalf of users, Setup does complete the installation. However, by installing Office silently, you have implicitly accepted the license terms.
The Windows Installer properties DISPLAY and PIDKEY do not work in Office 2010 (or in the 2007 Office system). Instead, in Office 2010 you customize Setup directly by specifying a display setting and specifying a product key in the OCT either by accepting the default option, Use KMS client key if you are using KMS validation, or by entering a MAK key in the Enter another product key textbox if you are using KMS, as described in Customize Setup.
Because Setup plays a more significant role in controlling the installation, many Windows Installer properties are no longer required. 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 that you can use with the Office 2010, and also a list of blocked or unsupported properties and their corresponding new mechanisms, see Setup properties in Office 2010.
See Also
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Configure and deploy volume activation of Office 2010
Tools to configure client computers in Office 2010
Deploy volume activation of Office 2010
Office Customization Tool in Office 2010
Customize Office 2010
Config.xml file in Office 2010
Setup properties in Office 2010
Setup architecture overview for Office 2010
Configure feature installation states for Office 2010
After you create a network installation point but before you install Microsoft Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file (.msp file) to configure the installation for users. You can use the OCT to change the default way that Office features are installed. You can set some features to be installed on the user's computer, some features to be installed only on first use, and some features not to be installed. You can even hide or lock features so that a user who runs Setup interactively cannot change what you have configured. For information about the network installation point, see Create a network installation point for Office 2010.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
Configure installation states
Use the following procedure to configure feature installation states.
[pic]To configure Office feature installation states
|1. To start the OCT, from the root of the network installation point, type the following at the command prompt: setup.exe /admin. |
|2. In the Select Product dialog box, select the product that you want to configure, and then click OK. |
|3. In the left navigation pane, locate Features, and then click Set feature installation states. |
|4. In the right navigation pane, expand the tree and select the feature that you want to customize. For example, if you opt not to|
|install the Equation Editor, expand Microsoft Office and Office Tools, right-click Equation Editor, and then 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. In the Save As dialog box, 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, Setup uses the customization file that it finds in the Updates folder and configures Office features according to your customizations.
The following table describes the available installation options.
|Option |Description |
|Run from My Computer |Setup copies files and writes registry entries and shortcuts that are|
| |associated with the feature to the user's hard disk, and the feature |
| |(or application) runs on the user's computer. |
|Run all from My Computer |This option is the same as Run from My Computer, except that all |
| |child features that belong to the feature are also set to this state.|
|Installed on First Use |Setup leaves components for the feature and all of 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. |
|Not Available |The components for the feature, and all of the child features that |
| |belong to that feature, are not installed on the user's computer. |
|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. |
| |[pic]Note |
| |• If you set the Hidden option for a specific feature by using the |
| |OCT or the Config.xml file during an initial installation of Office |
| |2010, you cannot “unhide” that feature in the feature tree by using |
| |another Config.xml file or by applying a second .msp file after the |
| |initial installation. If you selected the Hidden option, 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 Windows XP or under the |
| |Programs and Features option in Windows Vista) in Control Panel if |
| |you opt to change your Office 2010 installation; it will not be |
| |displayed in the Office Setup feature installation tree under the Add|
| |or Remove Features option for Office 2010. However, you can unlock |
| |the feature to install and run it locally later by using an .msp file|
| |or a Config.xml file. |
| |• If you set the Locked option for a feature by using the OCT or the |
| |Config.xml file during initial installation, that feature can be |
| |unlocked and installed locally by using an .msp file or a Config.xml |
| |file. |
| |• For instance, you can edit the Config.xml file to modify the |
| |OptionState element as shown in the following example. This adds the |
| |OptionState element line to uninstall the feature (in this case, |
| |Microsoft Access) on a user's computer, and to set child features of |
| |the feature to the specified state. |
| |• For more information about the Config.xml file, see Config.xml file|
| |in Office 2010. |
| |• You can also use the OCT to create an .msp file to install the |
| |feature later. To do this, click Set feature installation states. In |
| |the right navigation pane, right-click a feature, and then set the |
| |feature installation state to Run all from My Computer. |
|Locked |The feature cannot be changed by the user during interactive Setup or|
| |maintenance mode. |
[pic]Note
• The following subcomponents of Microsoft Publisher 2010 are not visible in the Setup feature installation state tree in Office 2010:
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 the Set feature installation states section in Office Customization Tool in Office 2010.
As with any deployment of Office, make sure that you test customizations and deployment in a non-production environment before you deploy Office 2010 to users in the organization.
See Also
Create a network installation point for Office 2010
Customize Office 2010
Setup architecture overview for Office 2010
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Configure user settings for Office 2010
After you create a network installation point but before you install the Microsoft Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file (.msp file). Many user settings can be configured in the OCT to customize the user's environment. For example, you can use the OCT to configure the default settings for several AutoCorrect options in Microsoft Word 2010. When you configure a user setting, that setting is in place when the user first runs an Office application.
[pic]Note:
Configuring a user setting in this manner is not necessarily permanent; it merely establishes the initial default value for the setting. The user can modify most settings after Office is installed. If you have to enforce user settings and prevent users from changing the settings, use Group Policy.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
Configure user settings
Use the following procedure to configure user settings for Office 2010.
[pic]To configure user settings
|1. To start the OCT, from the root of the network installation point, type the following at the command prompt: setup.exe /admin. |
|2. In the Select Product dialog box, select the product that you want to configure, and then click OK. |
|3. In the left navigation pane, locate Features, and then click Modify user settings. |
|4. In the right navigation pane, expand the tree, and then click the product for which you want to configure settings. |
|5. In the Settings column, double-click the user setting that you want to configure. A Properties dialog box appears. |
|6. Select one of the following options, and then click OK. |
|• Not Configured The setting remains as it is. |
|• Enabled The setting is modified based on your choices in the Properties dialog box. If values are available for the setting, |
|select the value that you want to use. |
|• 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 information. |
|[pic]Note: |
|If you click Enabled to view the options for a setting and then click OK, Previous Setting, or Next Setting, the status changes to|
|configured, even if you do not change the setting. Inadvertently configuring the setting with an empty hyperlink, path, or file |
|name can cause errors. If you clicked Enabled and want to ignore your changes or avoid configuring the setting, click Cancel in |
|the Properties dialog box for the setting. You can also return a setting to the Not Configured state by double-clicking the |
|setting, selecting Not Configured, and clicking OK. |
|For example, to specify the default format in which you want users to save Word 2010 files, in the navigation pane expand |
|Microsoft Word 2010, expand Word Options, and then click Save. In the list pane, in the Setting column, double-click Default file |
|format. The Default file format Properties dialog box appears. Select Enabled, click the drop-down list arrow, click the file |
|format that you want to specify, and then click OK. |
|7. If you want to preserve user settings from previous versions of Office, select the Migrate user settings check box. |
|[pic]Note: |
|If you modify user settings and also select the Migrate user settings check box, Setup first applies the modified settings and |
|then migrates the user's existing custom settings, overwriting any conflicting settings. |
|8. On the File menu, click Save As. |
|9. Specify a path and file name for the Setup customization file, and then click Save. |
|10. On the File menu, click Exit. |
|11. Copy the Setup customization file to the Updates folder in the network installation point. |
When you run Setup to install Office 2010, Setup uses the Setup customization file (.msp file) in the Updates folder and configures user settings.
See Also
Create a network installation point for Office 2010
Customize Office 2010
Setup architecture overview for Office 2010
Office Customization Tool in Office 2010
Create different configurations of Office 2010 for different groups of users
This article provides required information and procedures to create different configurations of Microsoft Office 2010 for groups of users that have different requirements. You can create unique configurations of Office 2010 customized for each group by using one of the methods described in this article.
The first method uses the Office Customization Tool (OCT) to create a Setup customization .msp file for each group. You then use the command line to run Setup and specify the customization .msp file. The second method uses the Config.xml file and a Setup customization .msp file to customize the installation, and uses a separate installation folder that contains the Setup program and all the customization files for the installation. You then run Setup from that separate installation folder.
In Office 2010, two architecture-specific versions of the OCT are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.
Typically, the first step in a corporate deployment of Office 2010 is to create a network installation point. You do this by copying 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 management tool such as Microsoft System Center Configuration Manager. For more information, see Create a network installation point for Office 2010.
In this article:
• Create custom configurations for a group of users
• Create a custom configuration for a group of users by using a separate installation folder
Create custom configurations for a group of users
The method described in this section uses the OCT to create a unique Setup customization file (.msp file) for each group. Then you install Office for the users by specifying the customization file on the Setup command line.
[pic]To configure customizations for a group of users
|1. Create a network installation point for Office. For more information, see Create a network installation point for Office 2010. |
|2. In the root of the network installation point, create a folder for your Setup customization files. |
|[pic]Note: |
|Do not put your customization files in the Updates folder. Setup automatically applies customization files that it finds in this |
|folder during installation. Instead, you direct Setup to use only the customization file that you specify on the command line, as |
|described in step 5. |
|3. Start the OCT by running Setup from the network installation point. Specify the /admin command-line option; for example, |
|\\server\share\setup.exe /admin. For more information, see Office Customization Tool in Office 2010. |
|4. Make the customizations that you want to use for the first group of users. |
|a. On the File menu, click Save. |
|b. Specify a unique name for the Setup customization file. Save the file in the folder that you created. |
|c. Repeat the process to create a unique Setup customization file for each group of users. |
|5. 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. For more information, see Run Setup from a network installation point. |
Create a custom configuration for a group of users by using a separate installation folder
The method described in this section uses the Config.xml file and a Setup customization .msp file to create customizations for each group of users. It also uses a separate installation folder from the primary network installation point to store Setup.exe, Config.xml, Osetup.dll, and the Setup customization .msp files. The remaining necessary installation files will be contained in the primary network installation folder for Office 2010. You run (or have users run) Setup from that separate installation folder.
The primary difference between the method described in this section and the preceding one is the use of the separate installation folder. The benefit of a separate installation folder for a group of users is that you (or the users in that group) can run Setup from that separate installation location and receive the customized configuration of the group without having to use complex commands and network paths with Setup.exe.
[pic]To create and install a custom configuration for a group of users by using a separate installation folder
|1. Create a folder that is separate from the primary network installation folder for Office 2010. For example, |
|GroupCustomOfficeInstallFolder. |
|2. Create a copy of Setup.exe, Config.xml, and Osetup.dll in the new folder. These files are in the primary network installation |
|folder. |
|Setup.exe is located at the root of the folder. The Config.xml file and Osetup.dll are stored in the core product folder: |
|core_product_folder_name.WW folder; for example, ProPlus.WW. |
|3. Using a text editor, open Config.xml and do the following: |
|• Edit the Location attribute in the DistributionPoint element to get the Office 2010 installation files from the primary network |
|installation folder, as shown in the following example. For information about Config.xml, see Config.xml file in Office 2010. |
| |
|• If you used the OCT to create one or more Setup customization files (.msp files), edit the CheckForSUpdates and SUpdateLocation |
|attributes in the SetupUpdates element in Config.xml as shown in the following example to enable Setup to find Setup customization|
|files in the new folder. (By default, Setup looks for Setup customization files in the Updates folder, and then runs them in |
|alphabetical order if there is more than one.) |
| |
|[pic]Important |
|4. Run Setup.exe from the new GroupCustomOfficeInstallFolder folder. You can map a drive for users or run Setup from the command |
|line, as shown in the following example. |
|\\share\GroupCustomOfficeInstallFolder\setup.exe |
You can use the Config.xml file to configure the following areas:
• Specify the path of the network installation point.
• Select which product to install.
• Customize Setup options, such as logging and the location of the Setup customization file and software updates.
• Add or remove languages from the installation.
• Set installation options, such as user name and company name.
• Copy the local installation source (LIS) to users’ computers without installing Office.
For more information, see Config.xml file in Office 2010.
As with any Office deployment, test customizations and deployment in a nonproduction environment before you deploy Office to users in the organization.
See Also
Setup architecture overview for Office 2010
64-bit editions of Office 2010
Office Customization Tool in Office 2010
Customize Office 2010
Config.xml file in Office 2010
Import an Office 2010 Setup customization file
This article provides required information and procedures to import an Office Customization Tool (OCT) Setup customization file (.msp file) in Microsoft Office 2010.
In this article:
• Overview
• Import a Setup customization file
• Import languages to an existing installation
Overview
In Office 2010, two architecture-specific versions of the Office Customization Tool are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version.
You start the OCT by running the setup.exe /admin command at the command prompt from the root of the network installation point that contains the Office 2010 source files. (For more information, see Create a network installation point for Office 2010.) For example, run the following command line to start the OCT: \\server\share\Office14\setup.exe /admin. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder.
The OCT supports the importing of Setup customization files (.msp files):
• 32-bit .msp files can be imported into the 64-bit OCT, and then they can be used to customize 64-bit Office 2010 products.
• 64-bit .msp files can be imported into the 32-bit OCT, and then they can be used to customize 32-bit Office 2010 products.
[pic]Note
• Importing customization .msp files is intended for equivalent cross-architecture products only. You can import a 32-bit Microsoft Office Professional Plus 2010 customization .msp file into the 64-bit version of the OCT for a 64-bit Office Professional Plus 2010 .msp file. However, you cannot import a 32-bit Microsoft Word 2010 stand-alone customization .msp file into the 64-bit OCT for a 64-bit Office Professional Plus 2010 .msp file; doing so is prevented and displays an error message. For information about how to use the OCT to create a Setup customization file and about all the areas that you can configure with the OCT, see Office Customization Tool in Office 2010.
• You cannot import 2007 Microsoft Office system Setup customization files (.msp files) into the Office 2010 OCT.
The Import feature can also be used when you have created an initial Setup customization file (.msp file) for an Office 2010 product (for example, Microsoft Office Professional Plus 2010) and you later want to modify the installation to add language packs. In such cases, you first add the language packs to the network installation point that contains the Office product source files. Then, you run the OCT from the root of the network installation point and create a new Setup customization file for the same product, and import the original customization .msp file that you created previously for Microsoft Office Professional Plus 2010. For more information, see To import a customization .msp file to add languages to an existing installation.
Import a Setup customization file
Use the following procedure to import a Setup customization file (.msp file).
[pic]To import a Setup customization file
|1. Start the OCT by typing setup.exe /admin at the command prompt from the root of the network installation point that contains |
|the Office 2010 source files. For example: |
|\\server\share\Office14\setup.exe /admin |
|2. To import a customization .msp file, in the OCT, on the File menu, click Import. |
|3. In the Open dialog box, select the .msp file that you want to convert, and then click Open to start the conversion. |
|4. On the File menu, click Save As. Specify a unique name for the file and save the file in the Updates folder of the network |
|installation point for the platform for which you imported the customization .msp file (either 32-bit or 64-bit). For example, if |
|you imported a 32-bit customization .msp file for customizing a 64-bit installation of Office 2010, you would save the file in the|
|Updates folder of the network installation point for 64-bit Office 2010. |
|5. Click Save. |
Import languages to an existing installation
If you create a Setup customization file (.msp file) to customize the Office 2010 installation and later decide to add languages, you can use the Import option in the OCT to apply the language changes. Use the following procedure to import languages to an existing installation. This procedure uses Office Professional Plus 2010 as an example.
[pic]To import a customization .msp file to add languages to an existing installation
|1. Add the language packs that you want to use to the network installation point that contains the Office Professional Plus 2010 |
|source files. For more information, see Create a network installation point for Office 2010. |
|2. Run the OCT by typing setup.exe /admin at the command-line prompt from the root of the network installation point that contains|
|the Office Professional Plus 2010 source files. For example: |
|\\server\share\Office14\setup.exe /admin |
|3. In the Select Product dialog box, click Create a new Setup customization file for the following product and then choose the |
|same product for which you previously customized installation options, Microsoft Office Professional Plus 2010 in this example. |
|4. To import the original customization .msp file that you created previously for Microsoft Office Professional Plus 2010, on the |
|File menu, click Import. |
|5. In the Open dialog box, select the .msp file that you want to update. |
|6. On the File menu, click Save As. Specify a unique name for the .msp file, and then click Save. |
|[pic]Note: |
|The Updates folder supports only one Setup customization .msp file. Therefore, if you import a Setup customization .msp file to |
|add languages to an existing installation, we recommend that you replace your previous customization .msp file (the original .msp |
|file) with the new customization .msp file that contains the language packs information. |
|7. Deploy and apply the updated Setup customization file .msp to users' computers. |
|To apply the Setup customization (.msp) file to existing installations, you must apply the .msp file directly to the user's |
|computer. Users can apply the Setup customization .msp file by double-clicking the .msp file, or by running the msiexec command |
|that has the /p option as shown in the following example (using custom.msp): msiexec.exe /p \\server\share\custom.msp. |
|For more information about Windows Installer commands, see Windows Installer Command-Line Options |
|(). |
|You can also use a deployment management program, such as Microsoft System Center Configuration Manager 2007, to deploy Setup |
|customization files. |
See Also
Office Customization Tool in Office 2010
Create a network installation point for Office 2010
Customize Office 2010
Customize Setup before installing Office 2010
Setup architecture overview for Office 2010
64-bit editions of Office 2010
Configure a silent installation of Office 2010 by using Config.xml
This article provides required information and procedures to configure a silent installation of Microsoft Office 2010 by using the Config.xml file. The Config.xml file is used to configure installation tasks and is used only when you run 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 2010.
Modify the Config.xml file to configure a silent installation
To configure a silent installation (unattended installation) of an Office 2010 product that requires no user interaction, modify the Config.xml file for the product that 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.
[pic]To specify silent installation options in Config.xml
|1. Open the Config.xml file for the Office product (such as Office Professional Plus 2010) 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: |
| |
|3. Modify the Display element entry with the silent options that you want to use. Make sure that you remove the comment |
|delimiters, "". For example, use the following syntax: |
| |
|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 |
|Office 2010. |
|4. Save the Config.xml file. |
Make sure that no Office applications are running when you install Office 2010. For example, to install Office Professional Plus 2010 after you modify the Config.xml file to specify silent installation options, use the following command:
\\server\share\setup.exe /config \\server\share\ProPlus.WW\config.xml
Where:
\\server\share is the path of the Office Professional Plus 2010 source files.
/config is a Setup command-line option that specifies the location of the Config.xml file. See Setup command-line options for Office 2010.
\\server\share\ProPlus.WW\config.xml is the location of your modified Config.xml file for Office Professional Plus 2010.
[pic]Note
• If you use the Config.xml file to set silent installation options as in the previous example, you will also want to use the Office Customization Tool (OCT) to create a Setup customization file (.msp file) to configure additional installation customizations. For example, you can use the OCT to specify previous versions of Microsoft Office applications to keep or remove. You can also set feature installation states by using the OCT to change the default way in which Office features are installed. For a complete description of the areas that you can configure by using the OCT, see Office Customization Tool in Office 2010. The OCT is available with Volume Licensing editions of Office 2010 (and the 2007 Office system). To determine whether your Office 2010 installation is a Volume Licensing edition, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a Volume Licensing edition. If the Admin folder does not exist, the disk is a retail edition.
• You can also set silent installation options by using the OCT. For more information, see the Licensing and user interface section in Office Customization Tool in Office 2010. (The Level attribute of the Display element in the Config.xml file is equivalent to the Display Level option in the OCT). In enterprise deployments, we recommend that you set the Display Level to None if using the OCT 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 being used. Setting the Display Level to None assumes that the Suppress modal and Completion notice options are silenced and that the I accept the terms in the License Agreement check box is selected. As noted previously, administrators must also make sure that no Office applications are running during an installation of Office 2010.
Run arbitrary commands with installations of Office 2010
By default, the Setup program for Microsoft Office 2010 installs one Office product at a time. You can use the chaining feature to customize Setup to run an arbitrary command or a lightweight executable that you want to run when this product is installed. To add an arbitrary command or a lightweight executable, you can use the Add installations and run programs feature in the Office Customization Tool (OCT) or the Command element in the Config.xml file. We recommend that you limit the use of Add installations and run programs and the Command element to running only lightweight executables or arbitrary commands that will not make changes to the computer or that do not require user input. For example, you can run a utility to copy logs or a command to launch a Welcome page at the end of installation.
The Add installations and run programs option in the OCT (command lines entered in the Add Program Entry and Modify Program Entry dialog boxes) and the Command element in the Config.xml file are intended to be used only for initial product installations and uninstallations. The commands are processed only during initial installations and uninstallations.
[pic]Important:
Chaining is not as reliable as installing each product separately. For example, if you chain two installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation might not finish successfully. Therefore, we do not recommend using the chaining approach. The recommended method for installing multiple products together is to use a deployment management program, such as Microsoft Systems Management Server or Microsoft System Center Configuration Manager 2007, or a third-party tool, instead of chaining.
In the following example, the OCT is used to add an arbitrary program to the installation.
[pic]To customize the primary installation to run a command
|1. Create a network installation point that includes the product that you will install. For more information, see Create a network|
|installation point for Office 2010. |
|2. Run the OCT by running Setup.exe from the root of the network installation point with the /admin command-line option. For |
|example, run: \\server\share\Office14\setup.exe /admin. |
|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. |
|For more information about “Licensing and user interface” and Display level options, see Office Customization Tool in Office 2010.|
|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 executable that is chained. |
|• For Target, enter the fully qualified path of the executable file that you want to run after the primary installation. For |
|example, enter \\server\share\Office14\copylogs.bat. |
|• For Arguments, enter the string of arguments to be passed to the executable. For example, enter: QuietArg="/q" Wait="30000". |
|For information about the Command element and supported attributes, see “Command element” in Config.xml file in Office 2010. |
|[pic]Note: |
|As mentioned previously, 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 the Run this program after the Office product has been installed option to run the program listed in the Target box after|
|the Office installation is completed. This is the recommended option. |
|You can also select the Run this program before the Office product has been installed option if you want the program listed in the|
|Target box to run before the Office installation starts. However, if the program does not terminate correctly, or if it restarts |
|the computer, Office is not installed, and programs further down the list do not run. |
|• Click OK. |
|7. Make other customizations in the OCT as needed. |
|8. Save the Setup customization file (.msp file) with a unique name in the Updates folder of the network installation point. |
|9. Exit the OCT. |
[pic]To install the product
|1. Run Setup from the root of the network installation point. For example, if the primary product is Microsoft Office Professional|
|Plus 2010, enter \\server\share\setup.exe |
|-or- |
|If you also used the Config.xml file to configure installation options in addition to the OCT setup customization .msp file |
|customizations, run Setup from the root of the network installation point and specify the Config.xml file that you customized for |
|the primary product. For example, if the primary product is Office Professional Plus 2010, enter: |
|\\server\share\setup.exe /config \\server\share\ProPlus.WW\config.xml |
|2. In the Select Product dialog box, select the primary product. |
After Setup installs the primary product, it runs the arbitrary command or lightweight executable that you specified in the OCT.
[pic]Tip:
You can put the customization files that you created in a location other than the Updates folder. Just add the /adminfile option to the Setup command lines in the procedures earlier in this section to specify the customization files to use. For more information about how to use Setup command-line options, see Setup command-line options for Office 2010.
How it works
The Setup program for the primary product follows the typical installation process. After that installation is complete, Setup runs the additional lightweight executable or arbitrary command that you specified in the OCT. Setup waits until each program is finished before it runs the next program.
It is important to 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 None. We recommend that chained installations also be 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.
See Also
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Run Setup from a network installation point
Customize specific features in Office 2010
This section provides how-to information for specific customization tasks, such as customizing language setup and settings, enforcing settings by using Group Policy, disabling user interface items and shortcut keys, and enabling the Microsoft SharePoint Server 2010 Colleague add-in for Microsoft Outlook 2010.
In this section:
|Article |Description |
|Customize language setup and settings for Office 2010 |Describes how to manage the distribution of multiple language |
| |versions when you deploy Microsoft Office 2010. |
|Customize the Office user interface in Office 2010 |Provides resources to help you customize the Microsoft Office Fluent |
|( interface (UI) in Office 2010. |
|9382f(Office.14).aspx) | |
|Enforce settings by using Group Policy in Office 2010 |Provides procedural information for using the Group Policy Management|
|( and the Group Policy Object Editor together with the Office |
|16d0e(Office.14).aspx) |2010 Administrative Templates. |
|Disable user interface items and shortcut keys in Office 2010 |Provides background and procedural information to disable user |
|( (UI) items and keyboard shortcuts in Office 2010 by using |
|97c36(Office.14).aspx) |Group Policy. |
|Enable SharePoint Server 2010 Colleague in Outlook 2010 |Describes how to configure Office 2010 client computers to enable the|
|( SharePoint Server 2010 Colleague add-in for Microsoft |
|0176a(Office.14).aspx) |Outlook 2010. |
Customize language setup and settings for Office 2010
This article describes how to manage the distribution of multiple language versions when you deploy Microsoft Office 2010.
In this article:
• Overview
• Before you begin
• Deploy a default language version of Office
• Specify which languages to install
• Deploy different languages to different groups of users
• Identify installed languages
• Customize language settings
• Customize and install the Office 2010 Proofing Tools Kit
Overview
By default, Setup automatically installs the language version that matches the Windows user locale that is set on each user's computer. Or, 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 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 Microsoft Office 2010 Proofing Tools Kit for additional languages.
For more information, see Plan Setup in Plan for multilanguage deployment of Office 2010.
When a user starts an Office 2010 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. However, you configure language settings by using Group Policy, the Office Customization Tool (OCT), or the Language Settings tool. For more information, see Plan customizations in Plan for multilanguage deployment of Office 2010.
If users will have to edit in a language or a companion proofing language that will not be installed, you can customize and install the Office 2010 Proofing Tools Kit. For more information, see Plan for proofing tools in Plan for multilanguage deployment of Office 2010.
Before you begin
To determine which of the following procedures to use for your deployment and which customizations that you might have to make, see Plan for multilanguage deployment of Office 2010.
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.
The following steps are the same as the standard steps for deploying Office 2010and included for testing. The only difference in the steps is that you must copy the language packs to the same network location as the installation files.
[pic]To deploy a default language version of Office to every client computer
|1. Create a network installation point for the primary Office 2010 product by copying all the files and folders from the 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 you are |
|prompted to overwrite duplicate files, click No. |
|3. Use the Office Customization Tool (OCT) to configure the installation to match your organization's requirements. |
|Because most of the customizations apply to the core product, you do not typically have to customize each language separately. |
|Setup applies your customizations during the installation regardless of the language being installed. For information about how to|
|customize language settings, see Customize language settings. |
|Language packs that are obtained through a volume license agreement do not require a unique product key; only one volume license |
|key is required for the 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 2010 in any language: |
|\\server\share\Office14\Setup.exe /config \\server\share\Office14\Standard.WW\Config.xml |
|where Office14 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 that you are installing. Setup does not |
|install the complete 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 Office 2010 and included for testing. The only difference in the steps is that you must 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.
[pic]To specify one or more languages to install on a client computer
|1. Create a network installation point for your primary Office 2010 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 you are |
|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 2010, 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. Add the element. |
|6. Set the value of the Id attribute to the language tag that corresponds to the language that you want to install. You can |
|specify more than one language by including additional elements and attributes. |
|7. Specify which language to use for the Shell user interface (Shell UI) by setting the attribute of the |
| element. |
|For example, to specify that Setup install both English and French, with English as the default installation language, add the |
|following elements: |
| |
|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 as follows: |
| |
| |
| |
|You are required to specify a value for the ShellTransform attribute when you add more than one 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: |
| |
|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 (OCT) to configure the installation to match your organization's requirements. |
|For information about how to customize language settings, see Customize language settings. |
|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\Office14\setup.exe |
|/config\\server\share\Office14\Standard.WW\Config.xml |
|where Office14 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 have to work with Office Standard 2010 documents in English and Japanese, whereas 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 Office 2010 and included for testing. The only differences in the steps is that you must copy the language packs to the same network location as the 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.
[pic]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 2010, 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 element and specify the set of languages that you want to install for this user group, as described |
|previously. |
|[pic]Note: |
|You must also set the attribute of the element, as described previously. |
|4. Save the Config.xml file by using a unique file name. |
|5. Repeat these steps for the next user group. |
|6. Use the OCT to configure the installation to match your organization's requirements. |
|For information about how to customize language settings, see Customize language settings. |
|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\Office14\setup.exe /config\\server\share\Office14\Standard.WW\SubAConfig.xml, or |
|\\server\share\Office14\setup.exe /config\\server\share\Office14\Standard.WW\SubBConfig.xml |
|where Office14 is the root of the network installation point. |
Identify installed languages
You can view a list of languages installed for Office 2010 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\14.0\Common\LanguageResources\EnabledLanguages
You can view the user interface (UI) language and fallback languages at the following registry key:
HKCU\Software\Microsoft\Office\14.0\Common\LanguageResources
Although all applications in the Office 2010 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 Office 2010 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 Word 2010 and Microsoft Excel 2010 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.
Customize language settings
Use Group Policy to enforce language settings
Policies enforce default language settings. Users in your organization cannot permanently modify settings managed by policy. The settings are reapplied every time that the user logs on.
[pic]To use Group Policy to manage language settings
|1. Copy the Office 2010 policy template files to your computer. |
|2. Under Computer Configuration or User Configuration in the console tree, right-click 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 that 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 2010 system\Language Settings node. |
|9. Select the languages that you want to use for each setting. |
|10. Save the GPO. |
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.
[pic]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 2010 system\Language Settings. |
|3. Open the folder that you want in the navigation pane. Double-click the setting in the right pane, select Enable, and then |
|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 how to use the OCT, see Office Customization Tool in Office 2010.
Use the Language Preferences tool to modify language settings
If you are not enforcing language settings by policy, users who work in Office applications can use the Language Preferences tool to change their language preferences.
[pic]To change language preferences by using the Language Preferences tool
|1. On the Start menu, point to Programs, point to Microsoft Office, and then point to Microsoft Office 2010 Tools. |
|2. Click Microsoft Office 2010 Language Preferences. |
|3. At the bottom of the Choose Editing Languages section, in the language list box, select the language that you want to be |
|available for editing, and then click the Add button. Repeat this step for each editing language that you want to add. |
|4. In the Choose Editing Languages section, select the language that you most often use for Office applications and documents, and|
|then click Set as Default. |
|5. In the Choose Display and Help Languages section, under Display Language, select the language that you want to use to view |
|Office application buttons and tabs, and then click Set as Default. |
|6. Under Help Language, select the language that you want to use to view Office application Help, and then click Set as Default. |
|If you do not specify a language for Help, the online Help language uses the display language. |
[pic]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.
Customize and install the Office 2010 Proofing Tools Kit
This section covers how to customize and install Office 2010 Proofing Tools Kit.
[pic]Note:
If you only need a few proofing languages, the installation of one or two language packs might provide all the proofing tool languages that you need. Each language version of Office 2010 includes proofing tools for a set of companion languages. For more information, see Plan for proofing tools in Plan for multilanguage deployment of Office 2010.
Customize the Office 2010 Proofing Tools Kit
You can specify which proofing tool languages to install by using the Proof.WW Setup file config.xml. For a list of the OptionState attributes and IDs to use, see Plan for proofing tools in Plan for multilanguage deployment of Office 2010.
[pic]To customize Setup for proofing tools
|1. In the ProofKit.WW folder, locate the Config.xml file. |
|2. Open the Config.xml file by using a text editor, such as Notepad. |
|3. For each set of proofing tools that you do not want to install, in the OptionState element, set the State attribute to Absent. |
|For example, if you do not want Catalan proofing tools installed, use this syntax: |
| |
|4. Set the State attribute for each set of proofing tools you want to deploy to Local (or Default or Advertise, if preferred). For|
|example, to deploy Basque proofing tools, you can use this syntax: |
| |
|5. Save the Config.xml file. |
|6. Run Setup.exe, and then specify the path of your modified Config.xml file. |
|Note that you must use a fully qualified path; for example: \\server\share\Office14\Proof.WW\setup.exe |
|/config\\server\share\Office14\Proof.WW\Config.xml |
|where Office14 is the root of the network installation point. |
Installing the Office Proofing Tools Kit 2010 on a single computer
If you have one or two users who need proofing tools, you can install proofing tools from the Office 2010 Proofing Tools Kit to individual computers.
[pic]To install the Office Proofing Tools Kit 2010 on a single computer
|1. On the Office 2010 Proofing Tools Kit 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 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 that you want to install, and then use the drop-down |
|arrows to set the appropriate installation states. |
|5. Click Install. |
See Also
Plan for multilanguage deployment of Office 2010
Office Customization Tool in Office 2010
Configure Outlook 2010
This section provides how-to information for configuring Microsoft Outlook 2010 with Microsoft Exchange Server account features, such as Outlook Anywhere, Cached Exchange Mode, Microsoft Exchange send/receive settings, and multiple Exchange accounts. It also provides information about how to configure security and protection features in Microsoft Outlook 2010 and how to customize Outlook profiles by using an Outlook Profile (.prf) file.
In this section:
|Article |Description |
|Configure Outlook Anywhere in Outlook 2010 |Describes the requirements and options for you to configure a group |
| |of Outlook user accounts to use Outlook Anywhere. |
|Configure Cached Exchange Mode in Outlook 2010 |Describes how to configure Cached Exchange Mode for Microsoft |
| |Exchange Server e-mail accounts in Microsoft Outlook 2010. |
|Configure Exchange Server send/receive settings in Outlook 2010 |Describes how to 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 operation in Microsoft |
| |Outlook 2010. |
|Configure multiple Exchange accounts for Outlook 2010 |Describes how to configure multiple Microsoft Exchange Server e-mail |
| |accounts for a Microsoft Outlook 2010 profile. |
|Configure security and protection in Outlook 2010 |Describes how to configure e-mail security, protection, and privacy |
| |in Microsoft Outlook 2010. |
|Customize Outlook profiles by using an Outlook Profile (PRF) file |Describes how to use the Microsoft Outlook 2010 profile file (.prf) |
| |to quickly create MAPI profiles for users, how to edit the profiles, |
| |and how to apply the profiles. |
Configure Outlook Anywhere in Outlook 2010
You can configure user accounts in Microsoft Outlook 2010 to connect to Microsoft Exchange Server 2003 or a later version over the Internet without using virtual private network (VPN) connections. This feature, which permits connection to an Exchange Server account by using Outlook Anywhere, enables Outlook users to access their Exchange Server accounts from the Internet when they travel or work outside the organization's firewall.
This article describes the requirements and options for you to configure a group of Outlook user accounts to use Outlook Anywhere. If you want to configure this feature on a single computer, see Use Outlook Anywhere to connect to your Exchange server without VPN ().
In this article:
• Overview
• Before you begin
• Use the OCT to configure Outlook Anywhere
• Use Group Policy to lock down Outlook Anywhere settings
• Verification
Overview
To configure Outlook 2010 with Outlook Anywhere as part of an Outlook deployment, you enable the option in the Office Customization Tool (OCT) and (optionally) specify additional settings, such as security-level requirements, to communicate with the Exchange Server computer. After you specify these options, you save the settings with other configurations in the Setup customization file (.msp file) that you use to deploy Outlook to users.
You can also lock down some Outlook Anywhere settings by using Group Policy. For more information about Outlook Anywhere Group Policy settings, see Use Group Policy to lock down Outlook Anywhere settings later in this article.
If your messaging server is Microsoft Exchange Server 2007 or Microsoft Exchange Server 2010, you can use the Outlook 2010 Autodiscover feature to automatically configure Outlook Anywhere. For more information about automatic account configuration, see Outlook Automatic Account Configuration ().
Outlook Anywhere was known as RPC over HTTP in earlier versions of Outlook.
Before you begin
• Before you start deployment, review Planning overview for Outlook 2010 to determine the settings that you might have to configure for Outlook Anywhere.
• 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 Plan a Cached Exchange Mode deployment in Outlook 2010.
• Download the Group Policy Administrative templates (.adm files) from the Microsoft Download Center, if needed.
• Before you configure Outlook Anywhere for Outlook 2010 in an Exchange environment without the Autodiscover service, obtain the URL for the Exchange proxy server that is configured for Outlook Anywhere. This URL is available from the organization's Exchange administrator.
Use the OCT to configure Outlook Anywhere
Use this procedure to use the OCT to configure Outlook Anywhere.
[pic]To configure Outlook Anywhere by using the OCT
|1. In the OCT, in the tree view, locate Outlook, and then click Add accounts. Click the Exchange account that you want to |
|configure and then click Modify. |
|2. If you are defining a new Exchange Server computer for users, enter a value or replaceable parameter in User Name. |
|For example, you might specify =%UserName% to use the exact logon name for each user. This helps prevent user prompts when Outlook|
|asks users to decide among several variations. |
|3. If you are defining a new Exchange Server computer, in the Exchange Server text box enter the name of the Exchange Server |
|computer. |
|Skip steps 2 and 3 if you are configuring Outlook Anywhere for existing Exchange users who are not moving to a new Exchange Server|
|computer. |
|4. Click More Settings. |
|5. In the Exchange Settings dialog box, select the Configure Outlook Anywhere check box and then select the Connect to Exchange |
|Mailbox using HTTP check box. |
|6. In the text box that follows these check boxes, type the server name for the Outlook Anywhere proxy server. |
|Do not enter http:// or https:// as part of the name. |
|7. Decide whether you want users to connect through Secured Sockets Layer (SSL) only. If you want to support both server |
|authentication and client authentication, select Mutually authenticate the session when the system connects with SSL and enter the|
|principal name of the proxy server. |
|8. Select whether or not to reverse the default way in which Outlook decides which connection type to try first, LAN (TCP/IP) or |
|Outlook Anywhere (HTTP). The default is LAN (TCP/IP) first, then Outlook Anywhere (HTTP). If you expect users to connect when they|
|are outside the corporate network more frequently than when they are inside the corporate network, we recommend that you configure|
|Outlook to try Outlook Anywhere (HTTP) first. |
|9. Select an authentication method from the drop-down list. |
|The default method is Password Authentication (NTLM). |
|10. Click OK to return to the Exchange Settings dialog box, and then click Finish. |
|11. Complete other Outlook or Microsoft Office configurations, and on the File menu, click Save to create the customization file |
|that you can deploy to users. |
Use Group Policy to lock down Outlook Anywhere settings
Use this procedure to use Group Policy to lock down Outlook Anywhere.
[pic]To lock down Outlook Anywhere settings in the user interface by using Group Policy
|1. In the Group Policy Object Editor, load the Outlook 2010 Administrative template (Outlk14.adm). |
|2. To customize Cached Exchange Mode options, open the Group Policy Management Console (GPMC) and in the tree view expand Domains |
|and then expand Group Policy Objects. |
|3. Right-click the policy object you want and click Edit. The Group Policy Management Editor window opens. |
|4. In the tree view, expand User Configuration, expand Policies, expand Administrative Templates, expand Classic Administrative |
|Templates (ADM), expand Microsoft Outlook 2010, expand Account Settings, and then click Exchange. |
|5. In the reading pane, in the Setting column, double-click the policy that you want to set. For example, double-click Configure |
|Outlook Anywhere user interface options. |
|6. Select Enabled. |
|7. Click an option in the Choose UI State when OS can support feature drop-down list. |
|8. Click OK. |
Verification
After you have finished your configurations, apply the configurations in a test environment. In the test environment, open Outlook and verify that the configurations are applied as expected.
See Also
Exchange Server 2003 RPC over HTTP Deployment Scenarios ()
Deploying Outlook Anywhere ()
Configure Cached Exchange Mode in Outlook 2010
This article describes how to configure Cached Exchange Mode for Microsoft Exchange Server e-mail accounts in Microsoft Outlook 2010.
In this article:
• Overview
• Before you begin
• Configure Cached Exchange Mode
• To configure Cached Exchange Mode settings by using the Office Customization Tool
• To configure Cached Exchange Mode settings by using Group Policy
• To configure a default .ost location by using Group Policy
• To force upgrade of non-Unicode ANSI format .ost files to Unicode
Overview
When an Outlook 2010 account is configured to use Cached Exchange Mode, Outlook 2010 works from a local copy of a user's Exchange mailbox stored in an Offline Folder (.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 computer.
Cached Exchange Mode can be configured for Exchange Server e-mail accounts only. Cached Exchange Mode is supported by all versions of Exchange Server with which Outlook 2010 can connect; that is, by Exchange Server 2003 or later versions.
If you do not configure Cached Exchange Mode options, the current state of Cached Exchange Mode does not change for existing profiles when Microsoft Outlook is upgraded to a new version. For example, if a user account was configured to use Cached Exchange Mode in Office Outlook 2003 or Microsoft Office Outlook 2007, Cached Exchange Mode remains enabled when the user upgrades the software to Outlook 2010. 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 and Windows 7, the location is %userprofile%\AppData\Local\Microsoft\Outlook.
You can configure several options for Cached Exchange Mode. These include the default .ost file location for users in your organization who do not already have .ost files for Cached Exchange Mode. If you do not specify a different .ost file 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 Administrative template (Outlk14.adm). Or, you can configure default settings by using the Office Customization Tool (OCT), in which case users can change the settings.
Before you begin
Before you start deployment, review Plan a Cached Exchange Mode deployment in Outlook 2010 and Office Customization Tool in Office 2010 to determine which settings you might have to configure for Cached Exchange Mode.
If you migrate from an earlier version of Outlook with Cached Exchange Mode enabled, determine which format your users’ .ost files are in (ANSI or Unicode). See How to determine the mode that Outlook 2007 or Outlook 2003 is using for offline folder files ().
Configure Cached Exchange Mode
Use the following procedures to configure Cached Exchange Mode settings.
[pic]To configure Cached Exchange Mode settings by using the Office Customization Tool
|1. In the Office Customization Tool, in the tree view, locate Outlook, click Add Accounts. In the Account Name column of the |
|reading pane list, click the account that you want to configure, and then click Modify. The Exchange Settings dialog box appears. |
|Note that in the tree view of the OCT you must click Outlook Profile and then select Modify Profile or New Profile to add an |
|Exchange account and configure Exchange Server settings. |
|2. To specify a new location for users' Outlook data files (.ost), in the Exchange Settings dialog box click More Settings, and |
|then select 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 text box |
|3. To enable or disable Cached Exchange Mode, or to specify default download behavior when Cached Exchange Mode is enabled, click |
|the Cached Mode tab. |
|4. Select Configure Cached Exchange Mode and then 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 Use Cached Exchange Mode check box. |
|5. If you enabled Cached Exchange Mode in step 4, select a default download option on the Cached Mode tab: |
|• 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 can be downloaded later in several ways; for example, by double-clicking to open the message or by |
|clicking Download the rest of this message now in 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. We recommend this option unless you have a slow network connection. 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, select the Download full items option button and 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. 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 shared non-mail folders increases the size of users' .ost files. |
|8. Download Public Folder Favorites as part of Cached Exchange Mode synchronizations to users' .ost files. By default, Public |
|Folder Favorites are not downloaded. As with shared non-mail folders, downloading Public Folder Favorites increases the size of |
|users' .ost files. Also, synchronizing Public Folder Favorites causes additional network traffic that might be unwelcome for users|
|who have slow connections. |
|9. If you have to enable shared mail folders that use Cached Exchange Mode, follow these steps: |
|a. In OCT, in the tree view, locate Additional Content and then click Add registry entries. |
|b. In the reading pane, click Add. |
|c. Enter the following information: |
| |
|Root |
|Data type |
|Key |
|Value name |
|Value data |
| |
|HKEY_Current_User |
|REG_SZ |
|Software\Microsoft\Office\14.0\Outlook\CachedMode |
|CacheOthersMail |
|1 |
| |
| |
|d. Click OK. |
[pic]To configure Cached Exchange Mode settings by using Group Policy
|1. In Group Policy, load the Outlook 2010 template (Outlk14.adm). |
|2. To customize Cached Exchange Mode options, open the Group Policy Management Console (GPMC) and in the tree view expand Domains |
|and then expand Group Policy Objects. |
|3. Right-click the policy object that you want and then click Edit. The Group Policy Management Editor window opens. |
|4. In the tree view, expand User Configuration, expand Policies, expand Administrative Templates, expand Classic Administrative |
|Templates (ADM), expand Microsoft Outlook 2010, expand Account Settings, and then click Exchange. You can also expand Exchange and|
|then click Cached Exchange Mode. |
|5. In the reading pane, in the Setting column, double-click the policy that you want to set. For example, in the Exchange reading |
|pane, double-click Use Cached Exchange Mode for new and existing Outlook profiles. |
|6. Select Enabled and select an option (if appropriate). |
|7. Click OK. |
[pic]To configure a default .ost location by using Group Policy
|1. In Group Policy, load the Outlook 2010 template (Outlk14.adm). |
|2. To configure a default .ost location, open the Group Policy Management Console (GPMC) and in the tree view expand Domains and |
|then expand Group Policy Objects. |
|3. Right-click the policy object that you want and then click Edit. The Group Policy Management Editor window opens. |
|4. In the tree view, expand User Configuration, expand Policies, expand Administrative Templates, expand Classic Administrative |
|Templates (ADM), expand Microsoft Outlook 2010, expand Miscellaneous, and then click PST Settings. |
|5. Double-click Default location for OST files. |
|6. Select Enabled to enable the policy setting. |
|7. In the Default location for OST files text box, enter the default location for .ost files. For example: |
|%userprofile%\Local Settings\Application Data\Microsoft\newfolder. |
|8. Click OK. |
|You can define a new default location for both Personal Outlook data files (.pst) and .ost files. After you click PST Settings in |
|the tree view, click the Default location for PST and OST files setting in the reading pane. |
[pic]To force upgrade of non-Unicode ANSI format .ost files to Unicode
|1. For users who have existing non-Unicode ANSI format .ost files, the following procedure does not upgrade ANSI .ost files to |
|Unicode .ost files. The procedure merely creates a new Unicode .ost file for the user’s profile, leaving the original ANSI .ost |
|files alone. |
|2. To determine which format your users’ .ost files are in (ANSI or Unicode), see How to determine the mode that Outlook 2007 or |
|Outlook 2003 is using for offline folder files (). |
|3. In Group Policy, load the Outlook 2010 template (Outlk14.adm). |
|4. Open the Group Policy Management Console (GPMC) and in the tree view expand Domains and then expand Group Policy Objects. |
|5. Right-click the policy object that you want and then click Edit. The Group Policy Management Editor window opens. |
|6. In the tree view, expand User Configuration, expand Policies, expand Administrative Templates, expand Classic Administrative |
|Templates (ADM), expand Microsoft Outlook 2010, expand Account Settings, and then expand Exchange. |
|7. Double-click Exchange Unicode Mode — Ignore OST Format. |
|8. Select Enabled to enable the policy configuration. |
|9. In the Choose whether existing OST format determines mailbox mode drop-down list, click Create new OST if format doesn't match |
|mode. |
|10. Click OK. |
|11. Double-click Exchange Unicode Mode — Silent OST format change. |
|12. Select Enabled to enable the policy configuration, and then click OK. |
|13. Double-click Exchange Unicode Mode — Turn off ANSI mode. |
|14. Select Enabled to enable the policy configuration, and then click OK. |
|15. In the tree view, expand Miscellaneous, click PST Settings, and in the reading pane double-click Preferred PST Mode |
|(Unicode/ANSI). |
|16. Select Enabled, in the Choose a default format for new PSTs drop-down list click Enforce Unicode PST, and then click OK. |
See Also
Plan a Cached Exchange Mode deployment in Outlook 2010
Configure Exchange Server send/receive settings in Outlook 2010
As part of a Microsoft Outlook 2010 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 operation in Outlook 2010.
[pic]Note:
This article is for Microsoft Outlook administrators. To configure Outlook send/receive settings on your computer, see Send/Receive groups ().
You configure these settings by using the Office Customization Tool (OCT). You cannot configure the settings by using the Group Policy feature.
In this article:
• Overview
• Before you begin
• Create and configure Send/Receive groups in Outlook 2010
Overview
Send/Receive groups contain one or more user e-mail accounts or folders in Outlook 2010. By default, the Send/Receive group All Accounts is preconfigured and is included with Outlook 2010. Users can specify different behavior for each group; for example, the frequency with which Outlook 2010 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 kinds of synchronization that will be performed on specific folders or on the Offline Address Book (OAB) when a Send/Receive operation is executed. You can also specify when a Send/Receive action for each Send/Receive group will ordinarily 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 ordinarily and every 30 minutes when users are offline.
You can also configure download options for the OAB, such as whether to download updates to the OAB only since the last OAB download.
Before you begin
Before you start deployment, review Planning overview for Outlook 2010.
Create and configure Send/Receive groups in Outlook 2010
Use this procedure to create and configure Send/Receive groups for Exchange accounts and folders.
To create and configure Send/Receive groups for Exchange accounts and folders
1. In the OCT, in the tree view, locate Outlook, and then click Specify Send/Receive groups.
2. In the reading pane, select Configure Send/Receive settings if it is not already selected.
3. Click New.
4. In the New Group Name text box, enter a name for the group, and then click OK.
5. Click Modify.
6. In the Modify Group dialog box, select options for the group, such as Synchronize forms during a Send/Receive operation.
7. In the list, click a folder and select Include this folder in Send/Receive.
8. Select download options for the folder. The download option is only relevant for folders that have the concept of headers, such as the Inbox, Outbox, Deleted Items, Sent Items, and Drafts folders:
• Download headers only
• Download complete item including attachments
• Download only headers for items larger than n KB
9. Enter a size limit in kilobytes (KB). This setting applies only to accounts that are set up to use Exchange Server 2003, or later versions of Exchange Server.
10. In the list, click another folder to include the folder in this Send/Receive group, and select a download option.
11. Add all the folders that you want to include in this group, and then click OK.
12. Double-click a group in the Group Name list.
13. Select the options available in the Modify Group dialog box to specify Send/Receive behavior for the group, and then click OK.
14. In the Exchange Address Book section, select Download offline address book so that the OAB will be synchronized when this Send/Receive group is synchronized. This setting is configured for each Send/Receive group.
15. Click Address Book Settings.
16. Select options in the Modify Address Book Settings dialog box. These settings apply to all Send/Receive groups in this profile.
17. Click OK.
Configure multiple Exchange accounts for Outlook 2010
This article describes how to configure multiple Microsoft Exchange Server e-mail accounts for a Microsoft Outlook 2010 profile.
In this article:
• Overview
• Before you begin
• Add multiple Exchange accounts to a profile
• Modify or remove Exchange accounts on a profile
Overview
With Outlook 2010, you can add, modify, or remove multiple Exchange Server e-mail accounts to an Outlook profile the same way you can for other e-mail accounts by using the Office Customization Tool (OCT). Without any additional configuration, Outlook 2010 can connect to up to ten Exchange accounts from a single profile.
Individual users can add additional Exchange accounts to their Outlook 2010 profile within Outlook 2010. To do so, users can either click the File tab, click Account Settings, and then click Add Account, or use the Microsoft Windows Control Panel Mail module. They can also remove Exchange accounts on their profile. For more information, see Add or remove an e-mail account ().
Before you begin
Before you begin deployment, review Planning overview for Outlook 2010 and Office Customization Tool in Office 2010 to determine which settings you might have to configure for the Exchange accounts. The following three articles describe how to configure specific Exchange account features by using the OCT.
• Configure Outlook Anywhere in Outlook 2010
• Configure Cached Exchange Mode in Outlook 2010
• Configure Exchange Server send/receive settings in Outlook 2010
Add multiple Exchange accounts to a profile
Use the following procedure to add multiple Exchange accounts to an Outlook profile.
[pic]To add multiple Exchange accounts to a profile
|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. To edit an existing customization file (.msp), in the Select Product dialog box, click Open an existing Setup customization |
|file. Or to create a new customization file, select the Office suite that you want to customize, and then click OK. |
|3. In the Outlook area, click Outlook profile. Select how you want to customize profiles for your users. To change an existing |
|profile or to add a new profile, choose Modify Profile or New Profile. |
|4. To add and configure new and existing accounts, click Add accounts, and then click Customize additional Outlook profile and |
|account information. |
|5. To add an Exchange account, click the Add button. |
|6. In the Add Accounts dialog box, select Exchange, and then click Next. |
|7. In the Exchange Settings dialog box, enter an account name and the name of the Exchange Server computer. If you want to |
|identify the user by using a specific value, enter a User Name. Otherwise, leave the default %username% value for the User Name. |
|Each user’s account information in the Active Directory directory service will be automatically populated for the profile. |
|8. If you want to change an existing Exchange account in a user’s profile, select the Overwrite existing Exchange accounts check |
|box. |
|9. Click More Settings for additional Exchange configuration options such as Cached Exchange Mode and Outlook Anywhere, and then |
|click OK. |
|10. When you are finished, click Finish. |
|11. To add an additional Exchange account, repeat steps 5-10. |
|12. If you are creating a new profile, add the Outlook Address Book account to the profile. This account allows you to use the |
|Contacts folder in your Exchange mailbox as an address book when you create e-mail messages. |
|13. After you have finished all your customizations, save the customization file (.msp) and exit the OCT. Put the .msp file in the|
|Office installation source \Updates folder. Install the Microsoft Office 2010 from the original installation source. |
Modify or remove Exchange accounts on a profile
You can easily modify or remove an Exchange account from a profile by using almost the same procedure as previously described in Add multiple Exchange accounts to a profile. In step 5, highlight the Exchange account that you want to modify or remove from the profile, and then click either Modify to modify or Remove to remove the account. Then, finish your customizations and save the customization file (.msp).
See Also
Office Customization Tool in Office 2010
Configure Cached Exchange Mode in Outlook 2010
Configure Outlook Anywhere in Outlook 2010
Configure Exchange Server send/receive settings in Outlook 2010
Configure security and protection in Outlook 2010
This section describes how to configure e-mail security, protection, and privacy in Microsoft Outlook 2010.
In this section:
|Article |Description |
|Configure junk e-mail settings in Outlook 2010 |Describes how to create Junk E-mail Filter lists in Outlook 2010, and|
| |how to configure the Junk E-mail Filter and automatic picture |
| |download by using Group Policy or the Office Customization Tool |
| |(OCT). |
Configure junk e-mail settings in Outlook 2010
This article describes how to create Junk E-mail Filter lists in Microsoft Outlook 2010, and how to configure the Junk E-mail Filter and automatic picture download by using Group Policy or the Office Customization Tool (OCT).
This article is for Outlook administrators. To learn more about how to configure junk e-mail settings in Outlook on your desktop, see Change the level of protection in the Junk E-Mail Filter ().
In this article:
• Overview
• Before you begin
• Create and deploy Junk E-mail Filter lists
• Configure the Junk E-mail Filter
• Configure automatic picture download
Overview
Microsoft Outlook 2010 provides features that can help users avoid receiving and reading junk e-mail messages that include the Junk E-mail Filter and the ability to disable automatic content download from external servers.
Junk e-mail filtering in Outlook 2010 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 that you provide are default lists. If you deploy the lists by using Group Policy, users can change the lists during their Outlook session. When users restart Outlook, Group Policy will append the list by default or, if you have enabled Overwrite or Append Junk Mail Import List, their changes will be overwritten with the original list that you deployed. If you deploy the lists by using the OCT, users can customize and keep their customized lists as they use Outlook, to fine-tune the filters to work best for their messaging needs.
You can use Group Policy or the Office Customization Tool (OCT) to customize settings for the Junk E-mail Filter, and to disable automatic content download to meet the needs of your organization. For example, you can configure the Junk E-mail Filter to be more aggressive. However, that might also catch more legitimate messages. Rules that are not part of the junk e-mail management built into the software are not affected.
Before you begin
Review Plan for limiting junk e-mail in Outlook 2010 to determine what settings to configure for the Junk E-mail Filter and automatic content download.
Create and deploy Junk E-mail Filter lists
To deploy Junk E-mail Filter lists, first create the lists on a test computer and then distribute the lists to users. You can distribute the lists by putting the lists on a network share. If you have remote users not connected to the domain, you can use the OCT to add the files by using the Add files option.
[pic]To create default Junk E-mail Filter lists
|1. Install Outlook 2010 on a test computer. |
|2. Start Outlook 2010. |
|3. In Outlook 2010, on the Home tab, in the Delete group, click Junk and Junk E-mail Options. |
|4. On the Safe Senders tab, click Add. |
|5. Enter an e-mail address or domain name. For example: |
|someone@exchange. |
|6. Click OK. |
|7. To add more e-mail addresses or domain names, repeat steps 3 through 6. |
|8. Click Export to file. |
|9. Enter a unique file name for the Safe Senders list, and then click OK. |
|10. Repeat steps 3 through 9 with the Safe Recipients tab and the Blocked Senders tab to create Safe Recipients and Blocked |
|Senders lists. Be sure to specify a unique file name for each of the three lists. |
[pic]Deploy Junk E-mail Filter lists for users by using the Office Customization Tool
|1. Copy the three Junk E-mail Filter files that you created in the previous procedure to a network file share. |
|2. If you have remote users not connected to the domain, follow these steps. |
|a. In the OCT, click Add Files and then click Add. |
|b. 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. |
|c. Click Add. |
|d. 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 then click OK. |
|e. Click OK again. |
|1. On the Modify User Settings page, under Microsoft Outlook 2010\Outlook Options\Preferences, click Junk Mail. |
|2. Double-click Junk Mail Import List, click Enabled and OK so that the setting is applied and Junk E-mail Filter lists are |
|imported for users. |
|3. To overwrite existing Junk E-mail Filter lists with new lists, double-click Overwrite or Append Junk Mail Import List, click |
|Enabled and then click OK. |
|4. To specify a path of each Junk E-mail Filter list, double-click the settings that correspond to each list (for example, Specify|
|path to Safe Senders), click Enabled and enter a path and file name in the box (for example, in the Specify path to Safe Senders |
|list). |
|5. Click OK or click Next setting to specify the path for another Junk E-mail Filter list. |
|6. Complete other Outlook 2010 or Office 2010 configurations, and on the File menu, click Save to create the customization file |
|that you can deploy to users. |
You can later change an existing Outlook 2010 installation to update the Junk E-mail Filter lists by following the procedure and including more recent Junk E-mail Filter files.
For more information about how to use the Office Customization Tool for configuring an Office installation to deploy files, see Office Customization Tool in Office 2010.
Configure the Junk E-mail Filter
You can lock down the settings to customize Junk E-mail Filter options by using the Outlook 2010 Group Policy template (Outlk14.adm). Or you can configure default settings by using the OCT. If this is the case, users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT.
If you decide to configure Junk E-mail Filter settings in the OCT, see the procedure To configure Outlook Junk E-mail Filter settings in the Office Customization Tool later in this article for an additional setting that must be configured.
Use the following procedure to configure Junk E-mail Filter options in Outlook. For the Junk E-mail Filter options that you can configure, see Plan for limiting junk e-mail in Outlook 2010.
[pic]To configure Outlook Junk E-mail Filter settings in Group Policy
|1. In Group Policy, load the Outlook 2010 template (Outlk14.adm) and open User Configuration\Administrative Templates\Microsoft |
|Outlook 2010\Outlook Options\Preferences\Junk E-mail. |
|2. Double-click the option that you want to configure. For example, double-click Junk E-mail protection level. |
|3. Click Enabled. |
|4. If appropriate, select a radio button for the option that you want to set, or select an option from a drop-down list. |
|5. Click OK. |
|6. To activate the Junk E-mail settings, you must set the Junk E-Mail Import list setting. You can do this by using the OCT. |
|f. In the OCT, on the Modify user settings page, under Microsoft Outlook 2010\Outlook Options\Preferences\Junk E-mail, |
|double-click Junk Mail Import list. |
|g. Click Enabled. |
|h. Click OK. |
|i. Complete other Outlook 2010 or Microsoft Office 2010 configurations in the OCT, and on the File menu, click Save to create the |
|customization file that you can deploy to users. |
[pic]To configure Outlook Junk E-mail Filter settings in the Office Customization Tool
|1. In the OCT, on the Modify user settings page, under Microsoft Outlook 2010\Outlook Options\Preferences\Junk E-mail, |
|double-click Junk Mail Import list. |
|2. Click Enabled. |
|3. Click OK. |
|4. Double-click and set any other Junk E-mail options that you want to configure. |
|5. Complete other Outlook 2010 or Microsoft Office 2010 configurations, and on the File menu, click Save to create the |
|customization file that you can deploy to users. |
Configure automatic picture download
To help protect users' privacy and to combat Web beacons—functionality embedded within items to detect when recipients have viewed an item—Outlook 2010 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 2010 Group Policy template (Outlk14.adm). Or you can configure default settings by using the OCT. If this is the case, users can change the settings. The OCT settings are in corresponding locations on the Modify user settings page of the OCT.
[pic]To configure options for automatic picture download behavior in Outlook by using Group Policy
|1. In Group Policy, load the Outlook 2010 template (Outlk14.adm). |
|2. Under User Configuration\Administrative Templates\Microsoft Outlook 2010\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 that you want to set, or select an option from a drop-down list. |
|6. Click OK. |
[pic]To configure options for automatic picture download behavior in Outlook by using the Office Customization Tool
|1. In the OCT, on the Modify user settings page, under Microsoft Outlook 2010\Security\Automatic Picture Download Settings, |
|double-click the option that you want to configure. For example, double-click Include Intranet in Safe Zones for Automatic Picture|
|Download. |
|2. Select a radio button for the option that you want to set. |
|3. Click OK. |
|4. Complete other Outlook 2010 or Office 2010 configurations, and on the File menu, click Save to create the customization file |
|that you can deploy to users. |
See Also
Plan for limiting junk e-mail in Outlook 2010
Customize Outlook profiles by using an Outlook Profile (PRF) file
The Microsoft Outlook 2010 profile file (.prf) allows you to quickly create Messaging Application Programming Interface (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 Outlook 2010 to include Outlook settings or MAPI services that are not included in the Office Customization Tool (OCT) user interface.
In this article:
• Overview
• Before you begin
• Create a .prf file
• Manually edit a .prf file
• Apply a .prf file
Overview
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 Outlook 2010 .prf file format has changed but Microsoft Office Outlook 2007, Office Outlook 2003, and Outlook 2002 versions of the file will work with Outlook 2010. If you plan to make updates to the .prf file for the Outlook 2010 deployment, we recommend that you re-create the .prf file by using the Office Customization Tool (OCT), export the settings to a new .prf file, and use that file to specify the additional Outlook settings or MAPI services that you need.
Before you begin
Before you begin deployment, review Planning overview for Outlook 2010 to determine which settings you might want to configure by using a .prf file.
Procedures
To create an Outlook 2010 .prf file, you can configure profile settings by using the OCT, and then export the settings to a .prf file. This process creates a new Outlook 2010 .prf file that includes your specifications.
You can also specify profile settings by editing an existing .prf file manually by using a text editor. This existing .prf file might be one that you created by using the OCT, or a .prf file from an earlier version of Outlook. However, the .prf file format has changed in Outlook 2010. Therefore, we recommend that you re-create the older .prf file to prevent unexpected behavior.
Create a .prf file
[pic]To create a PRF file by using the Office Customization Tool
|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. To edit an existing customization file (.msp), in the Select Product dialog box, click Open an existing Setup customization |
|file. Or to create a new customization file, select the Office suite that you want to customize, and then click OK. |
|3. In the Outlook area, click Outlook Profile. Select how you want to customize profiles for users. To specify settings to be |
|included in a .prf file, choose Modify Profile or New Profile. |
|4. To add and configure new accounts or to modify or remove existing accounts, click Add accounts, and then click Customize |
|additional Outlook profile and account information. |
|5. Once you complete the Outlook profile configurations, in the Outlook area, click Export settings. |
|6. Click the Export Profile Settings button to create a new .prf file. Enter a file name and the path on which to save the file, |
|and then click Save. |
Manually edit a .prf file
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 you have no other way to update user profiles. If possible, you should use the OCT to create and deploy .prf files.
[pic]To manually update a .prf file
|1. Open the .prf file by using a text editor such as Notepad. |
|2. Make your changes or additions. By manually editing the .prf file, you can add any MAPI service that is supported by Outlook |
|2010. The .prf file includes detailed comments for each section that describe existing settings and options for modifying the file|
|that has your updates. The file includes the seven sections shown in the following table. |
| |
|Section |
|Description |
| |
|Section 1 – Profile defaults |
|String identifiers found to the left of the equal sign (=) in this section (ProfileName, DefaultProfile, and so on) are defined in|
|the .prf processor in Outlook and cannot be modified externally. These are default settings that are used to set up a user |
|profile. |
|For example: |
|[General] |
|Custom=1 |
|ProfileName=EveryAccount |
| |
|An existing profile can be either overwritten or updated when a new .prf file is executed. Several settings control how the new |
|settings are applied: |
|• The OverwriteProfile setting can be set to Yes, Append, or No. To update existing profiles, set the value to Append. This |
|preserves the existing profile and updates the sections that have been changed. To overwrite existing profiles with a new profile,|
|set the value to Yes. To prevent overwriting an existing profile, set the value to No. |
|• The ModifyDefaultProfileIfPresent setting can be set to True or False. When set to True, Outlook will modify the default profile|
|even if the new and existing profile names are different. |
| |
|Section 2 – Services in Profile |
|This section includes the list of services to be configured in the client. The services are listed in the order in which they are |
|added to the profile. Each service listed here is defined and referenced in Section 4. |
|For example: |
|[Service List] |
|;ServiceX=Microsoft Outlook Client |
|ServiceEGS1=Exchange Global Section |
|Service1=Microsoft Exchange Server |
| |
|You can add any MAPI service that is supported by Outlook 2010. The following services were supported in earlier versions of |
|Outlook, and should not be added: |
|• MS Mail |
|• Symantec WinFax Lite |
|• AW Fax |
| |
|Section 3 – List of Internet accounts |
|Internet accounts can be POP or IMAP e-mail accounts. This section lists the Internet accounts that will be defined and referenced|
|in Section 5. |
|For example: |
|[Internet Account List] |
|Account1=I_Mail |
|Account2=IMAP_I_Mail |
| |
|Section 4 – Default values for each service |
|This is the section to which you can add properties or change existing property values for the services in the profile. MAPI |
|profile properties are defined for services under each respective [ServiceN] heading. Valid Profile Property names are determined |
|by the MAPI profile property mapping in Section 6. |
|For example: |
|[Service1] |
|OverwriteExistingService=No |
|UniqueService=Yes |
|MailboxName=%UserName% |
|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. |
|For each service to be updated, the OverwriteExistingService setting can be set to Yes or No. Set the value to Yes so properties |
|are re-created for that service. The default for OverwriteExistingService setting is No. If No is specified, the service will not |
|be updated, even if new settings have been listed. |
| |
|Section 5 – Values for each Internet account |
|This section defines values for the POP and IMAP e-mail accounts referenced in Section 3. Internet account properties are listed |
|similarly to service properties, by using [AccountN] heading notations. Valid Profile Property names are determined by the MAPI |
|profile property mapping in Section 7. |
|For example: |
|[Account1] |
|UniqueService=No |
|AccountName=POP Account |
|POP3Server=pop.mail. |
| |
|Section 6 – Mapping for profile properties |
|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. |
|Section 6 lists each service name that Outlook supports and the numeric MAPI profile property values that correspond to the |
|registry keys that the Outlook .prf processor implements when storing the profile properties. |
|All values listed in Section 6 map directly to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging |
|Subsystem\Profiles\ProfileName registry entries, where ProfileName is replaced by the name of the corresponding profile. When a |
|service is added, a new GUID is created for it. |
|The Exchange sections have predefined GUIDs assigned because they are unique services. A service can have more than one section |
|GUID. Therefore, the number of GUIDs in the registry does not always correspond to the number of services that Outlook has |
|“registered.” |
|Section 6 includes several mapping strings for profile properties. This makes the .prf file very flexible. If you know the |
|specific property that you want to change, you can write a .prf file that has the appropriate properties in Section 6 and the |
|appropriate corresponding property values in Section 4, which allows the property to be deployed. |
| |
|Section 7 – Mapping for Internet account properties. DO NOT MODIFY. |
|This section corresponds to the mapping for the specified [AccountN] accounts in Section 5. There is a GUID in the Profile section|
|(GUID 9375CFF0413111d3B88A00104B2A6676) that expands and lists DWORD data types. Each of these DWORD types corresponds to an |
|Account in the .prf file. There might be more than one DWORD registry key per account. Therefore, as with Services, there is not a|
|one-to-one mapping for Accounts. |
|The same registered property types are present here as are listed in Section 6, and the same notation is provided for MAPI profile|
|property mapping. The separate sections (2, 4, 6 and 3, 5, 7) are an artifact of Internet Only (OMI) and Corporate Workgroup |
|modes. Because OMI was stored in a different location in the registry for earlier versions of Outlook, and migration code depends |
|on values being in a consistent format, you should not modify this section even if you are deploying updates for a version of |
|Outlook later than Outlook 2000. |
| |
| |
|3. Once you have completed your changes, save the file. For instructions about how to apply the .prf file, see the following |
|section, Apply a .prf file. |
Apply a .prf file
You can apply a .prf file in several ways to update Outlook profiles.
[pic]To apply a .prf file by using the customization file
|1. From the root of the network installation point, run the following command line to start the OCT: \\server\share\setup.exe |
|/admin |
|2. To edit an existing .msp file, in the Select Product dialog box, click Open an existing Setup customization file. Or to create |
|a new customization file, select the Office suite that you want to customize, and then click OK. |
|3. In the Outlook area, click Outlook Profile. Select Apply PRF, and then browse to the file. |
|4. On the File menu, click Save to save the .msp file. |
|5. Exit the OCT. |
|6. Put the .msp file in the Office installation source \Updates folder. |
|7. Install Office 2010 from the original installation source. |
[pic]To apply a .prf file by using other options
|• Specify the .prf file as a command-line option for Outlook.exe to import a .prf file without prompting the user. For 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. For 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. |
See Also
Office Customization Tool in Office 2010
Planning overview for Outlook 2010
Configure SharePoint Workspace 2010
This section provides information and procedures for installing, configuring, and testing Microsoft SharePoint Workspace 2010, a client to Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010.
In this section:
|Article |Description |
|Configure and customize SharePoint Workspace 2010 |Provides information and procedures for installing and configuring |
| |SharePoint Workspace 2010, a client to SharePoint Server 2010 and |
| |SharePoint Foundation 2010. |
|Test SharePoint Workspace connections |Provides information and procedures for testing SharePoint Workspace |
| |2010 connections to and synchronization with SharePoint Server 2010 |
| |and client peers. |
Configure and customize SharePoint Workspace 2010
This article provides information and procedures for installing and configuring Microsoft SharePoint Workspace 2010, a client to Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010. SharePoint Workspace 2010 provides anytime interactive access to document libraries and lists at a designated SharePoint site and provides options for creating Groove peer workspaces and Shared Folder workspaces.
SharePoint Workspace 2010 is included with Microsoft Office Professional Plus 2010 installation or it can be installed separately from the Microsoft Download Center ().
Customizing the installation enables you to decide how SharePoint Workspace will be deployed and used. This article describes how to customize SharePoint Workspace 2010 installation.
In this article:
• Before you begin
• Review customization options for SharePoint Workspace 2010
• Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings
• Verify installation
Before you begin
Before you start deployment, address the following prerequisites:
• Confirm that your setup meets required hardware and software requirements, specified in System requirements for Office 2010.
• Address the planning steps in Plan for SharePoint Workspace 2010.
• Confirm that Internet Explorer 6 or later versions are installed on client computers, with a 32-bit browser.
• Confirm that SharePoint Workspace port settings comply with the specifications in Plan for SharePoint Workspace 2010. SharePoint Workspace 2010 is installed with Windows Firewall turned on and exceptions enabled to support SharePoint Workspace server and client communications. To review or change these settings, open Control Panel, click System and Security, click Windows Firewall, click Change notification settings, and then change or review the settings.
• If you use Active Directory Domain Services (AD DS) and want to customize SharePoint Workspace deployment for Active Directory system group members, make sure that you have appropriate administrative permissions on the Active Directory system and identify the group to which you want to deploy SharePoint Workspace policies.
• Review customization options in Review customization options for SharePoint Workspace 2010, later in this article.
• If you are integrating SharePoint Workspace with SharePoint Server 2010 sites, prepare SharePoint Server 2010 as follows:
• Open incoming port 80 to support client/server communications and enable File Synchronization by using SOAP over HTTP Protocol.
• Consider configuring a Secure Socket Layer (SSL) port for SharePoint Server-SharePoint Workspace communications. We strongly recommend this configuration, as no default encryption security is in place.
• Ensure that SharePoint Server site administrators enable offline availability: On the SharePoint Central Administration Web site, click Site Actions, click Site Settings, in the Site Administration section click Search and offline availability, and in the Offline Client Availability section select Yes. This lets SharePoint Workspace clients access the site.
• Install remote differential compression (RDC) on SharePoint Server. RDC supports File Synchronization via SOAP over HTTP Protocol and optimizes performance during document transfer between SharePoint Workspace and SharePoint Server. To verify RDC status, open Windows Server Manager on the SharePoint Server system and then click Add Features. In the Add Features Wizard dialog box, make sure that the Remote Differential Compression check box is selected, click Next, and follow the Wizard instructions to install. Or, you can install RDC from a Command Prompt window by typing the following: servermanagercmd -install rdc. For more information about RDC, see About Remote Differential Compression ().
• Configure access control settings for designated SharePoint sites to enable access by SharePoint Workspace users and groups. For more information about how to configure access to SharePoint sites, see Managing Site Groups and Permissions ().
Review customization options for SharePoint Workspace 2010
The following sections describe options for customizing SharePoint Workspace 2010 installation.
Control use of Groove workspaces
This option lets you prevent Groove workspaces and Shared Folders from being used in SharePoint Workspace, thus limiting SharePoint Workspace usage to SharePoint workspaces exclusively. You can set this option by configuring an Office Customization Tool (OCT) setting during SharePoint Workspace installation or by deploying a Group Policy object (GPO), as described in Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings.
Enable IPv6
This option lets you enable IPv6 for SharePoint Workspace installation. You can set this option by configuring an OCT setting during SharePoint Workspace installation or by deploying a GPO, as described in Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings.
Prefer IPv4
This option lets you specify that IPv4 is preferred over IPv6 for SharePoint Workspace 2010 on client computers. You can set this option by configuring an OCT setting during SharePoint Workspace installation or by deploying a GPO, as described in Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings.
Remove legacy files and registry settings
This option removes previous installations of SharePoint Workspace (Microsoft Office Groove 2007). You can also use these tools if you have special requirements that can only be enabled or disabled through the Windows Registry. For example, you can remove a Office Groove 2007 device management registry setting. You can set this option by configuring an OCT setting or by deploying a GPO, as described in Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings.
Prevent Windows Search crawling for SharePoint Workspace
This option prevents crawling of SharePoint Workspace paths by Windows Search. Crawling (creation of indexes) for Windows Search 4.0 is enabled by default for the following SharePoint Workspace content:
• Metadata for SharePoint workspaces and Groove workspaces for SharePoint Workspace 2010
• Metadata for all Groove workspace tools for SharePoint Workspace 2010
• The following Groove workspace content for SharePoint Workspace 2010: discussions, documents, Notepad entries, chat transcripts, member messages, and custom lists.
Users can start Windows Search 4.0 from SharePoint Workspace by clicking Search on the Home tab of the ribbon, unless prevented from doing this by administrative policy. To block Windows Search from crawling and searching SharePoint Workspace content and to override any user search settings, you can configure a Group Policy object in the Active Directory system to customize a SharePoint Workspace 2010 installation. The GPO prevents crawling of SharePoint Workspace content, removes Search from the ribbon in SharePoint Workspace, and cleans the Windows Search index of any previously crawled SharePoint Workspace data.
For more information about Windows Search, see Windows Search Administrator Guide () and Windows Search IT Guides ().
For information about how to use a Group Policy object to prevent Windows Search of content, see Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings.
Force Secure Socket Layer protection for external connections
This option requires all communication from SharePoint Workspace clients to SharePoint Server to be Secure Socket Layer (SSL)-encrypted. You can set this option by configuring a SharePoint Server GPO for SharePoint Workspace 2010 installation as described in Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings.
For information about how to use a GPO to require SSL, see Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings
Customize SharePoint Workspace in a managed environment
If you use Microsoft Groove Server 2010 to manage SharePoint Workspace, you can further customize installation to. make administrative tasks easier For example, you can use Group Policy to configure policy settings that apply across an organizational unit in the Active Directory server, or you can configure an Office Resource Kit setting, to require SharePoint Workspace users to automatically configure SharePoint Workspace user accounts for management. For more information about Groove Server-specific customizations, see Deploy SharePoint Workspace 2010. ((Office.14).aspx)
Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings
You can customize SharePoint Workspace installations by deploying Active Directory Group Policy objects (GPOs) or by including an Office Customization Tool (OCT) .msp file together with the SharePoint Workspace installation kit. The method that you choose depends on the following deployment conditions:
• If intended SharePoint Workspace clients are members of an in-house Active Directory group and are connected to the Windows domain, you can configure Active Directory GPOs to customize client installations, as described in To customize SharePoint Workspace installation through Active Directory Group Policy objects.
• If your organization does not use an Active Directory server or if intended SharePoint Workspace clients are outside your Windows domain, use OCT settings to customize installation as described in To customize SharePoint Workspace installation through Office Customization Tool settings.
[pic]Note:
Decide on one customization approach to help ensure a smooth deployment. Do not use both approaches, to configure GPOs and OCT settings. For more information about these customization options, see Group Policy overview (Office system) () and Office Customization Tool in the Office system ().
If you use Groove Server 2010 Manager to manage SharePoint Workspace clients, you can use a combination of Groove Server 2010 Manager policies and GPOs or OCT settings to customize SharePoint Workspace installations. For information about Groove Server 2010 Manager policies, see Deploying policies to SharePoint Workspace users ((Office.14).aspx). For information about how to customize SharePoint Workspace in a Groove Server 2010-managed environment, see Deploy SharePoint Workspace 2010 ((Office.14).aspx).
[pic]To customize SharePoint Workspace installation through Active Directory Group Policy objects
|1. Address the requirements in Before you begin. |
|2. Determine which Group Policy object (GPO) that you need to customize SharePoint Workspace for the management environment, based|
|on the information in Review customization options for SharePoint Workspace 2010. |
|3. From the Active Directory server, access the required policies by downloading the AdminTemplates.exe file for Office 2010, |
|available at the Microsoft Download Center (). |
|4. Double-click the AdminTemplates.exe file to extract the Administrative template files that enable you to edit Group Policy |
|settings that apply to an Active Directory unit. The spw14.admx file (or .adml file for language-specific versions) contains |
|SharePoint Workspace-specific policies. |
|5. If you are using a Windows Server 2008 computer, copy the ADMX\ADML files to folders as follows: |
|a. Copy the ADMX files (.admx) to your computer’s Policy Definitions folder (for example, \PolicyDefinitions). |
|b. Copy the ADML language-specific resource files (.adml) to the appropriate language folder, such as en-us; for example, |
|\PolicyDefinitions\[MUIculture]. |
|For more information about Group Policy object editing requirements and steps, see Requirements for Editing Group Policy Objects |
|Using ADMX Files () and Managing Group Policy ADMX Files Step-by-Step Guide. |
|() |
|6. From the Active Directory server, use the Group Policy Management Console (GPMC), accessible from gpedit.msc in the Microsoft |
|Management Console, to change the policy settings that are contained in the .adm files. |
|7. In the tree view, locate Group Policy Objects, click the policy that you want to configure, and then in the details pane fill |
|in the required fields to enable or change the policy. See Group Policy for SharePoint Workspace 2010 for more guidance. |
|8. When you are finished editing the GPO in the GPMC, save the policy settings. The policy settings are saved in the registry.pol |
|file, which the Group Policy program uses to store registry-based policy settings made through the use of the Administrative |
|template extension. |
|For more information about Group Policy technology and use, see Group Policy overview (Office system) |
|() and Enforce settings by using Group Policy in the Office system |
|(). |
[pic]To customize SharePoint Workspace installation through Office Customization Tool settings
|1. Address the requirements in Before you begin. |
|2. Determine how you want to customize SharePoint Workspace, based on the information in Review customization options for |
|SharePoint Workspace 2010. |
|3. You can run the Office Customization Tool (OCT) from the Start menu by clicking Run, typing cmd to open a command window, going|
|to the Office 2010 installation directory, and typing setup/admin. This opens the OCT tool. |
|Or, you can download the OTC from the Office 2010 installation media. |
|4. In the OCT tree view, locate Features, and then click Modify user settings. In the navigation pane, click SharePoint Workspace,|
|SharePoint Server, or Search Server, depending on the type of setting that you want to configure. |
|5. In the list pane, double-click the setting that you require, based on a review of Review customization options for SharePoint |
|Workspace 2010, and then change its properties as needed. See Office Customization Tool settings for SharePoint Workspace 2010 for|
|more guidance. |
|6. When you are finished, click the File drop-down menu and then click Save to save your updated settings in a Microsoft setup |
|customization file (.msp). For example, enter spw.msp as a file name. |
|7. Include the .msp file in the SharePoint Workspace deployment. |
|For more information about how to use the OCT, see Office Customization Tool in the Office system |
|(). |
Verify installation
Test SharePoint Workspace connections and synchronization as described in Test SharePoint Workspace connections.
See Also
Plan for SharePoint Workspace 2010
Group Policy for SharePoint Workspace 2010
Office Customization Tool settings for SharePoint Workspace 2010
Test SharePoint Workspace connections
This article provides information and procedures for testing SharePoint Workspace 2010 connections to and synchronization with SharePoint Server 2010 and client peers.
In this article:
• Before you begin
• Test SharePoint Workspace synchronization with SharePoint Server
• Test Groove workspace synchronization among peer clients
Before you begin
Before you start testing, address the following prerequisites:
• Choose a SharePoint Workspace 2010 deployment topology and plan accordingly, as described in Plan for SharePoint Workspace 2010.
• For a SharePoint Server 2010-based topology, prepare SharePoint Server 2010, as described in Configure and customize SharePoint Workspace 2010.
• Customize SharePoint Server 2010 deployment, as described in Configure and customize SharePoint Workspace 2010.
• Follow the organization’s standard client software deployment processes to install Office 2010 or SharePoint Workspace 2010 on target user desktops.
• Identify two SharePoint Server 2010 sites to synchronize with a test SharePoint Workspace 2010 client. Make sure that you are a member of these sites to that you can create and edit site content.
• Identify test SharePoint Workspace 2010 clients inside and outside the local firewalls.
Test SharePoint Workspace synchronization with SharePoint Server
The following procedure provides guidance for validating connections and content synchronization between SharePoint Workspace 2010 and SharePoint Server 2010, in support of SharePoint workspaces.
[pic]To test SharePoint Workspace connections and synchronization
|1. Create a SharePoint workspace from a SharePoint site as follows: |
|a. Start SharePoint Workspace 2010 on a test client. |
|b. Browse to a SharePoint Server 2010 Central Administration Web site from a test SharePoint Workspace 2010 client. |
|c. From the SharePoint Server site, click the Site Actions drop-down menu and then click Sync to SharePoint Workspace. |
|d. To download all the Document libraries and List content on the site to the local test client, click OK from the Sync to |
|Computer dialog box that appears. To download selected content, click Configure in the dialog box, select the document libraries |
|and lists that you want to download, and then click OK. Within a few moments, a new SharePoint workspace will be downloaded to |
|your computer. The new workspace contains a copy of the requested SharePoint lists and libraries which you can edit while your |
|online or offline. |
|e. Experiment with editing a document or list from the SharePoint workspace while you are online, and then save your changes. |
|These edits and updates will be synchronized automatically with the document and list content on the SharePoint site. |
|f. Disconnect from the Internet and experiment with update the content from an offline state, and then save your changes. When you|
|return online, these edits and updates will be synchronized automatically with the document and list content on the SharePoint |
|site. |
|2. Verify that the client updates are visible on the SharePoint site as follows: |
|a. Reconnect to the Internet and browse to the SharePoint site. Or, for quick browsing from the SharePoint workspace that contains|
|the SharePoint site content, open the SharePoint workspace and then click the site link next to the Contents pane in the |
|SharePoint workspace. |
|b. Select View all content from the Site Actions drop-down menu and navigate to the document or list that you changed from the |
|SharePoint workspace. |
|c. Wait several moments or refresh the screen to see the updates that you made from the client. |
|3. To verify that SharePoint site updates are visible in the SharePoint workspace, follow these steps: |
|a. Browse to the SharePoint site and update a document or list that you have synchronized with content in the test SharePoint |
|workspace. |
|b. Open the SharePoint workspace that you created on the test client. |
|c. Wait a few moments for the site content to appear in the workspace. Or, click the Sync tab in the ribbon, click the Sync |
|drop-down menu, and then select either, Sync Tool to synchronize with the current document library or list, or Sync Workspace to |
|synchronize with all the documents and libraries on the site. |
|4. You can test a similar procedure, initiated from a SharePoint Workspace test client, as follows: |
|a. Start SharePoint Workspace 2010 on a test client. |
|b. From the SharePoint Workspace Launchbar, on the Home tab, click the New drop-down menu, and then select SharePoint Workspace. |
|c. Enter the URL to a SharePoint site in the Location text box. |
|d. Click Configure to access the site and select the content that you want to download, and then click OK. Within a few moments, a|
|new SharePoint workspace will be downloaded to your computer. The new workspace contains a copy of the requested SharePoint lists |
|and libraries which you can edit while your online or offline. |
|e. Experiment with editing document or lists as described previously in this procedure. |
|For more information about how to create SharePoint workspaces and how to use SharePoint Workspace 2010, see the SharePoint |
|Workspace 2010 product information at Microsoft Office Online (). |
|5. If a test step fails, see Troubleshoot SharePoint Workspace 2010, resolve the problem, and run the test again. |
Test Groove workspace synchronization among peer clients
SharePoint Workspace supports peer connections for Groove workspace and Shared Folder workspace types. The following procedures explain how to validate Groove workspace and Shared Folder workspace connections and peer synchronization.
[pic]To test Groove workspace synchronization
|1. From SharePoint Workspace client 1, start SharePoint Workspace 2010, then create a Groove workspace in SharePoint Workspace by |
|clicking the New drop-down menu on the Home tab on the Launch bar and then clicking Groove workspace. Accept the default tools and|
|configuration. Then invite SharePoint Workspace client 2 to the workspace. |
|For more information about how to use SharePoint Workspace 2010 and how to create Groove workspaces, see the product information |
|at Microsoft Office Online (). |
|2. From SharePoint Workspace client 2, accept the invitation. When the accepted invitation download is complete, open the new |
|Groove workspace, click the New Documents option on the Home tab, and then add a document that contains some test content. |
|3. From client 1, click the Documents item in the Contents pane, check for the new content that you added in the previous step, |
|and then edit the document. Client 2 appears in the workspace Members list. |
|4. From client 2, look for the client 1 update in the test document. |
|5. Repeat these steps to test connections and synchronization between clients inside and outside the corporate LAN and for clients|
|who have made offline contributions. |
|6. If a test step fails, see Troubleshoot SharePoint Workspace 2010, resolve this problem, and run the test again. |
[pic]To test Shared Folder synchronization
|1. From SharePoint Workspace client 1, start SharePoint Workspace 2010, and then create a test folder in the Windows file system. |
|Then create a shared folder in SharePoint Workspace by clicking the New drop-down menu on the Home tab on the Launch bar, clicking|
|Shared Folder, and specifying the test folder. Now invite SharePoint Workspace client 2 to the workspace. |
|For more information about how to create shared folders and how to use SharePoint Workspace 2010, see the SharePoint Workspace |
|2010 product information at Microsoft Office Online (). |
|2. From SharePoint Workspace client 2, accept the invitation. When the folder download is complete, you will see the new folder in|
|the Windows file system on client 2 and client 2 will appear in the workspace Members list. Now add a document that contains some |
|test content to the folder. |
|3. From client 1, check for new content in the folder and client 2 in the workspace Members list. Then edit the document. |
|4. From client 2, look for the client 1 update in the test document. |
|5. Repeat these steps to test connections and synchronization between clients inside and outside the corporate LAN and for clients|
|who have made offline contributions. |
|6. If a test step fails, see Troubleshoot SharePoint Workspace 2010, resolve this problem, and run the test again. |
SharePoint Workspace peer connections are often supported in a managed environment where Microsoft Groove Server is deployed onsite. For more information about how to deploy these workspace types in a managed environment, see Deploy SharePoint Workspace 2010. ((Office.14).aspx)
See Also
Deploy SharePoint Workspace 2010 ((Office.14).aspx)
Deploy Office 2010
This section helps you deploy and configure Microsoft Office 2010. It includes information about deployment scenarios, step-by-step installation instructions, and various methods that you can use to deploy Office 2010. Before you deploy Office 2010, we recommend that you review the information in Planning the deployment of Office 2010 Beta.
In this section:
|Article |Description |
|Run Setup from a network installation point |Provides information and procedures to run Setup. |
|Precache the local installation source for Office 2010 |Provides information and procedures to deploy the local installation |
| |source separately before you deploy Office 2010. (Setup creates a |
| |local installation source on the user's computer when you deploy |
| |Office 2010.) |
|Run Setup from the local installation source to install Office 2010 |Provides information and procedures to run Setup directly from the |
| |local installation source. |
|Deploy Office 2010 to users who are not administrators |Provides information about how to install Office 2010 on computers |
| |where users lack administrative permissions. |
|Deploy Office 2010 with limited network capacity |Provides information about how to deploy Office 2010 in an |
| |environment that has limited network resources. |
|Deploy Office 2010 by running Setup from a network share |Provides information about how to run Setup from a network |
|( point to deploy Office 2010, and how to test in a |
|03dd3(Office.14).aspx) |nonproduction environment before you deploy to a production |
| |environment. |
|Deploy Office 2010 by using System Center Configuration Manager 2007 |Provides detailed technical guidance on the processes and procedures |
|( you use Microsoft System Center Configuration Manager 2007 to |
|d642e(Office.14).aspx) |deploy Office 2010 in a medium- to large-sized organization. |
|Deploy Office 2010 by using System Center Essentials 2010 |Provides detailed technical guidance on the processes and procedures |
|( you use Microsoft System Center Essentials 2010 to deploy Office|
|e9bfd(Office.14).aspx) |2010 in a medium-sized organization. |
|Deploy Microsoft Silverlight with Office 2010 |Provides information about how to install Microsoft Silverlight along|
| |with Microsoft Office 2010 to improve the information worker user |
| |experience with Office 2010. |
Run Setup from a network installation point
After you create a network installation point for Microsoft Office 2010, you can install Office on a user's computer by running the Setup program. Setup handles all the installation functions for Office 2010. This includes applying any customizations that you specify.
For information about how to create a network installation point, see Create a network installation point for Office 2010.
Office 2010 introduces native 64-bit versions of Office products to take advantage of the larger capacity of 64-bit processors. This lets users work with much larger data sets than they previously could and to analyze and solve large computational problems. This additional capacity is only needed by Office users who require Microsoft Excel spreadsheets that are larger than 2 gigabyte (GB), for example. The 32-bit version of Office 2010 provides the same functionality and is also compatible with 32-bit add-ins, which is why Office 2010 installs the 32-bit version by default. The 64-bit Office client installs only on 64-bit editions of Windows Vista with Service Pack 1 and 64-bit editions of Windows Server 2008 with Service Pack 1. For more information, see 64-bit editions of Office 2010.
For information about how to customize the installation, see the following resources:
• Office Customization Tool in Office 2010
• Config.xml file in Office 2010
• Customize Office 2010
• Customize Setup before installing Office 2010
Install an Office 2010 product
Use the following procedure to install an Office 2010 product by running Setup from a network installation point.
[pic]To install an Office product
|1. If you created a Setup customization file (.msp file) by using the Office Customization Tool (OCT), copy the file to the |
|Updates folder that is located in the root of the network installation point. For information about how to use the OCT, see Office|
|Customization Tool in Office 2010. |
|2. To customize the Config.xml file, edit the copy of Config.xml that is located in the product folder on the network installation|
|point. For example, the product folder for Microsoft Office Professional Plus 2010 is ProPlus.WW. For information about how to use|
|the Config.xml file, see Config.xml file in Office 2010. |
|3. Run Setup.exe from the root of the network installation point. Setup installs the product that resides in the network |
|installation point and applies the customizations that you entered in the Config.xml file and in the Setup customization file. |
|[pic]Important: |
|If you want to install 64-bit Office 2010, run Setup.exe from the x64 folder. For example, navigate to the |
|\\server\share\Office14\x64 folder in the network installation point, and then double-click Setup.exe. |
|If there are multiple Office products on the network installation point, Setup prompts you to select the product that 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 Professional Plus 2010, run the following |
|command: \\server\share\Office14\setup.exe /config \\server\share\Office14\ProPlus.WW\Config.xml |
|Setup installs the product associated with the Config.xml file that you specify without prompting you to select the product. For |
|information about the /config setup command-line option, see /config [path] in Setup command-line options for Office 2010. |
For information about the setup process, see Setup architecture overview for Office 2010.
See Also
Create a network installation point for Office 2010
Office Customization Tool in Office 2010
Config.xml file in Office 2010
64-bit editions of Office 2010
Precache the local installation source for Office 2010
When you deploy Microsoft Office 2010, Setup creates a local installation source on the user's computer — a copy of the compressed source files for the Office product that you install. After 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 a network by deploying the local installation source separately, before you deploy Office.
Deploy the local installation source
Use the following procedure to deploy the local installation source before you deploy Office 2010.
[pic]To deploy the local installation source separately
|1. On the network installation point, open the Config.xml file in a text editor, such as Notepad. For information about the |
|Config.xml file, see Config.xml file in Office 2010. |
|By default, Config.xml is located in the core product folder for the Office product that you are installing. For example, if you |
|install Microsoft Office Professional Plus 2010, open the Config.xml file in the ProPlus.WW folder. |
|2. Find the LIS element (); remove the comment marks in the line by deleting the opening tags. |
|3. Set the attribute to "CacheOnly". |
|The line in Config.xml should look as shown in the following example. |
| |
|4. Save the Config.xml file. |
|5. Run Setup.exe on users' computers; on the Setup command line, specify the path of the modified Config.xml file. |
|You must use a fully qualified path. For example: \\server\share\Office14\setup.exe /config |
|\\server\share\Office14\ProPlus.WW\Config.xml |
|where Office14 is the root of the network installation point. |
[pic]Note:
If you precache the local installation source on users' computers and then later have to remove it, you can set the attribute to "RemoveCacheOnly" and run Setup again. This setting works only if users have not yet installed Office.
Precaching lets most of the installation activity occur on the local computer instead of over the network. Precaching also lets you coordinate the upgrade to the new version. You can distribute the local installation source to groups of users over time and then schedule a concurrent installation throughout the organization without overtaxing 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 Setup customization file (.msp file), and the custom Config.xml file from a network installation source. You must use the fully qualified path of these files. If the share names contain spaces, use quotation marks around the paths as shown in the following example.
"C:\MSOCache\All Users\{10140000-0011-0000-0000-0000000FF1CE}-C\setup.exe" /adminfile "\\server\share\Office 14\mychanges\db_outlookonly.msp" /config "\\server\share\Office 14\ProPlus.WW\Config.xml"
where:
/adminfile specifies the location of the .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 uses the local installation source to repair, reinstall, or update Office later. If the local installation source is corrupted or deleted, Setup uses the original source on the network to repair or re-create it. For information about the /adminfile and /config setup command-line options, see /adminfile [path] and /config [path] in Setup command-line options for Office 2010.
[pic]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.
See Also
Setup architecture overview for Office 2010
Run Setup from the local installation source to install Office 2010
Config.xml file in Office 2010
Create a network installation point for Office 2010
Setup command-line options for Office 2010
Run Setup from the local installation source to install Office 2010
When you deploy Microsoft Office 2010 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 a 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, instead of running it over the network. This strategy lets you minimize the load on the network and still upgrade everyone to the new version at the same time.
In this article:
• Run Setup
• MSOCache folder
• Office product download codes
Run Setup
To run Setup, you must identify the subfolder in MSOCache\All Users that contains the core product that you want to install. See MSOCache folder later in this article. Setup.exe is located in the same folder that contains the core product file WW.msi, for example, ProPlusWW.msi. For example, for Microsoft Office Professional Plus 2010, the core product file is ProPlusWW.msi, and the folder that contains Setup.exe is {10140000-0011-0000-0000-0000000FF1CE}-drive. The folder includes files, such as the following:
• Office64WW.msi
• Office64WW.xml
• Ose.exe
• Osetup.dll
• OWOW64WW.cab
• ProPsWW.cab
• ProPlusWW.msi
• ProPlusWW.xml
• Pkeyconfig-office.xrm-ms
• Setup.exe
• Setup.xml
[pic]To 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 Office 2010. |
|2. Locate the download code for the Office product that you want to install. Download codes are included in the Setup.xml file in |
|the core product folder. For example, locate the line in Setup.xml that contains the LocalCache entry as in this example from |
|Office Professional Plus 2010: |
| |
|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 user's computer. |
|For example, if you deployed the local installation source for Microsoft Office Professional Plus 2010 on the C drive, use the |
|following command line: |
|C:\MSOCache\All Users\{10140000-0011-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. |
MSOCache folder
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, instead of the folder naming convention used on the network installation point.
The letter appended to the end of each download code (-C in the previous 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 enables 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 update files (.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 file for Office Professional Plus 2010 should look as shown in the following example:
See Also
Precache the local installation source for Office 2010
Setup architecture overview for Office 2010
Deploy Office 2010 to users who are not administrators
In the Windows environments that support the Microsoft Office 2010, by 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 permissions on the local computer to install Office.
To install Office 2010 on computers where users lack administrative permissions, you must run Setup in a context that provides it with administrative permissions. After Office is installed, users without administrative permissions can run all installed features, and can install features on demand.
In organizations where users are not the administrators of their computers, administrators can use the following ways to provide Office Setup with the appropriate permissions:
• Log on to the computer as an administrator and install Office 2010.
• Deploy Office 2010 to computers by using Group Policy computer startup scripts.
• Use a software management tool, such as Microsoft System Center Configuration Manager 2007, Systems Management Server (SMS) 2003, or Microsoft System Center Essentials 2007.
• Use application virtualization.
After the initial installation is performed with administrative permissions, all later installations — including installation on demand and automatic repair of features — also run with those permissions.
[pic]Important:
Two general Windows policy settings that help install previous versions of Office are not supported in Office 2010 or in the 2007 Office system: the Windows Installer Always install with elevated privileges policy setting and the Enable user to use media source while elevated policy setting (these settings are in the Computer Configuration\Administrative Templates\Windows Components\Windows Installer node in Group Policy Object Editor). Setting the Always install with elevated privileges policy setting allows a user without administrative permissions to the computer to install any Windows Installer package. Similarly, setting the Enable user to use media source while elevated policy setting allows users without administrative permissions 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 policy settings leaves the computer highly vulnerable, potentially allowing an attacker to run malicious code on the computer. Using these policy settings to allow a user who is not an administrator to install Office will not work with the 2010 or the 2007 version of Setup and is not supported in Office 2010 or in the 2007 Office system.
In this article:
• Logging on as an administrator
• Deploying Office by using Group Policy computer startup scripts
• Using a software management tool
• Using application virtualization
Logging on as an administrator
You can install Office 2010 on a user's computer by logging on to the computer by using an administrator account. This provides the administrative permissions that you need for Office Setup to access restricted areas of the user's computer. Once Office is installed, users have no further need for administrative permissions to run Office applications.
[pic]Note:
For security reasons, applying a software update (.msp file) to an Office installation always requires administrative permissions, even if the original installation was performed with administrative permissions.
Deploying Office by using Group Policy computer startup scripts
Administrators can use Group Policy to assign computer startup scripts to deploy Office 2010 (and the 2007 Office system). Scripts can be written in any language that is supported by the client computer. Windows Script Host-supported languages, such as Microsoft Visual Basic Scripting Edition (VBScript) and Jscript, and command files are the most common.
Using a software management tool
A software management tool, such as System Center Configuration Manager 2007 or SMS, can run Office Setup in an administrative context on the user's computer.
Administrators can also use System Center Essentials 2007 to deploy Office 2010 and the 2007 Office system. System Center Essentials 2007 is a management solution that was designed for IT system administrators in mid-sized organizations that include up to 30 servers and 500 client computers.
Using application virtualization
Administrators can use Microsoft Application Virtualization (App-V) to deploy Office 2010. The application is published on a local client computer, and the application remains in a virtual environment. Applications run locally in a virtual environment, and are not installed on the local computer. For more information about virtualization types, technologies, and deployment methods, see Plan for virtualization.
See Also
Plan for virtualization
Deploy Office 2010 with limited network capacity
If you are deploying Microsoft Office 2010 in an environment that has limited network resources, the Setup architecture in Office 2010 lets you minimize the demand on the network and still ensure that all users install the new version at exactly the same time.
For example, your organization has distant branch offices that connect to the 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 2010 by using a typical logon 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 over the network.
In these kinds of environments, you can distribute the Office 2010 source files to users over time. Once your targeted user groups have a local installation source deployed on their computers, you can schedule a concurrent installation of Office without overtaxing the corporate network.
For information about customization for Office 2010 clients, we recommend that you read the following articles before you customize the installation: Customization overview for Office 2010 and Volume activation overview for Office 2010.
In this article:
• Recommended solution
• How this solution works
Recommended solution
To distribute Office 2010 source files over time, follow these steps:
1. Create a network installation point for Office 2010
2. Customize Office 2010
3. Precache the local installation source for Office 2010
4. Run Setup from the local installation source to install Office 2010
How this solution works
This deployment strategy works because Setup always installs Office 2010 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 lets you manage the load on the network more efficiently.
You configure Office 2010 before you distribute the local installation source. To specify most user configuration options, you run the Office Customization Tool (OCT) to generate a Setup customization file (.msp file). We recommend that you store the customization file for initial installations in the Updates folder at the root of the network installation point. For information about how to customize the installation by using the OCT, see Office Customization Tool in Office 2010.
[pic]Note:
If you plan to deploy multiple Setup customization files (.msp files), you can place only one customization .msp file in the Updates folder for an initial installation. You must deploy the rest of the customization .msp files after the installation of Office 2010 is completed. Only one Setup customization file in the Updates folder is supported. The customization .msp file that you place in the Updates folder will be deployed first. Therefore, it must include any Setup customizations that cannot be changed after the installation (for example, the installation location).
For some customizations, such as specifying additional languages, you must edit the Config.xml file for the product that you are installing. You also edit the Config.xml file to specify that Setup deploy only the local source. For information about how to specify additional languages and how to use the Config.xml file, see Customize language setup and settings for Office 2010 and Config.xml file in Office 2010.
When the 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 logon script, a batch file, or an enterprise software deployment tool such as Microsoft Systems Management Server, Microsoft System Center Configuration Manager 2010, or a third-party tool. In the precache scenario only, Setup copies the Updates folder from the network installation point to the local source. All the 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 the customizations and software updates, occurs locally without file transfers or any other activity over the network.
[pic]Note:
When Setup installs Office 2010 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 user’s 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 Office 2010
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Customization overview for Office 2010
Customize language setup and settings for Office 2010
Deploy Microsoft Silverlight with Office 2010
Microsoft Silverlight, a technology that works in the browser and on desktops, brings many Microsoft Office experiences to life with improved video, graphics, animations, and interactivity. We recommend that you install Microsoft Silverlight together with Microsoft Office 2010 to improve the user experience with Office 2010. Specifically, Silverlight enables a better online experience with , powers the Office 2010 interactive guides (available with Office 2010), improves the user experience of Microsoft SharePoint Server 2010, improves the performance of Office Web Companion applications, and helps with the process of uploading Office documents to cloud services. For more information about Silverlight, see the Microsoft Silverlight Web site ().
To deploy Silverlight together with Office 2010 in an enterprise environment, we recommend that you use a deployment and configuration management tool, such as Microsoft Systems Management Server 2003 or Microsoft System Center Configuration Manager 2007. This approach enables you to target specific users or systems, elevate user rights for installation, schedule the installation, specify user interaction levels, control restarts, and monitor and troubleshoot the deployment. Or, you can use one of the following methods to deploy Silverlight in an organization:
• Windows Server Update Services (WSUS) 3.0 SP1 WSUS enables administrators to deploy Silverlight and manage the updates for Silverlight to computers that are running Windows 2000 with Service Pack 4, Windows Server 2003, Windows XP with Service Pack 2, Windows Server 2008, and Windows Vista or later versions of Windows operating systems through the Microsoft Update client.
• Group Policy computer startup scripts This method can be used in an Active Directory directory service environment, in organizations that do not have a deployment and management tool such as System Center Configuration Manager 2007.
• Manual install options This method can be useful in organizations that do not have an Active Directory environment, or WSUS, SMS, or System Center Configuration Manager 2007 infrastructure and use a separate means for software or updates distribution in the company, or want to deploy Silverlight to Apple clients.
For more information about system requirements, deployment methods, and instructions for Silverlight deployment, see Silverlight Deployment Guide v2 () and Silverlight Administration (). You can download all versions of Silverlight from the Get Microsoft Silverlight Web site ().
As with any deployment, we recommend that you fully test your Silverlight deployment and conduct pilot tests with small groups of users before you deploy Silverlight to users in the production environment. For more information about how to test your deployment, see Silverlight Deployment Guide v2 ().
Maintaining and updating Office 2010 Beta
This section provides information about how to apply updates and how to manage user configurations after you install Microsoft Office 2010.
In this section:
|Article |Description |
|Apply updates for Office 2010 |Provides information about how to apply updates to Office 2010. |
|Manage users' configurations for Office 2010 |Provides information about how to make changes to an existing |
| |installation of Office 2010 |
Apply updates for Office 2010
This section describes how to apply updates to Microsoft Office 2010.
In this section:
|Article |Description |
|Add or remove languages after deploying Office 2010 |Describes how to add and remove language packs for an existing Office|
| |2010 installation and also how to identify installed languages. |
Add or remove languages after deploying Office 2010
This article describes how to add and remove language packs for an existing Microsoft Office 2010 installation and also how to identify installed languages.
In this article:
• Overview
• Before you begin
• Modify an existing installation
• Deploy language packs
• Remove language packs
• Identify installed languages
Overview
Although the most frequently deployed languages for Office 2010 are released at the same time as the product, many other Office 2010 Language Packs are released over time. The Office 2010 Multi-Language Pack, which includes all available language packs, is not released until after all the individual language packs are released. However, if you upgrade your multilingual organization to Office 2010 before all the language packs are released, you can add or remove languages later. The Office 2010 Multi-Language Pack and Office 2010 Proofing Tools Kit CDs for Office 2010 will be available for purchase in major retail stores and via their Web sites, and also through Microsoft volume licensing programs.
There are two methods that you can use to add languages after deploying Office 2010:
• Modify an existing installation. With this recommended method, a language is treated as another feature to add to a deployment of Office 2010. This method involves modifying the Config.xml file to add the appropriate language and rerunning Setup.exe. This method installs only the necessary language parts for the products installed on the user's computer. For example, if you add Japanese to an installation of Microsoft Office Professional 2010, the Microsoft Visio 2010 resources for Japanese are not installed. However, if the computer has both Office Professional 2010 and Visio 2010 installed on it, you would have to add the Japanese resources for each product through two separate operations.
• Deploy Language Packs as separate products. With this method, there must be at least one Office 2010 product installed on the computer. This method involves running Setup.exe for the Office 2010 Language Pack that you want to install so that the full Language Pack is installed to the computer. This method is appropriate for adding languages after a deployment of Office 2010 where you do not know which set of products Office 2010 are installed on users' computers.
Before you begin
It is important to determine which languages will be used 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 Office 2010 Language Packs you want to deploy to the network installation point that contains the Office product files. For example, \\server\share\Office14. A static list of the products contained in the installation source is built only during the initial creation of a customization .msp file. If you later add more languages to the installation source, the existing .msp file is not updated to reflect this change. Addressing this issue involves the following steps:
1. Create a new customization file by using the Office Customization Tool (OCT).
2. Import your existing customization .msp file by using the File \| Import command in the OCT.
3. Make any additional customizations that you need and then save the .msp file.
4. After you update the installation source with additional languages, deploy the new .msp file to users.
Failure to create and deploy a new .msp file might result in unexpected behavior, because the changes to an existing customization .msp file will not apply to the languages that were added. If you do not create a new .msp file and import the existing .msp file into that file, your deployment may test correctly in your lab, but users might not see the new language in their Office 2010 applications, or they might see only a subset of the language features. For more information, see To import a customization .msp file to add languages to an existing installation in the article Import an Office 2010 Setup customization file and Change users' configurations after installing Office 2010.
For information about how to create a network installation point with multiple languages, see Customize language setup and settings for Office 2010.
For a complete list of language tags, see Language identifiers and OptionState Id values in Office 2010.
Modify an existing installation
The recommended method for adding languages to an existing installation of Office 2010 is to run Setup again and modify the existing Office installation. Because you are only modifying the original installation, no new entry appears in Add or Remove Programs in Control Panel.
You cannot replace the language of the shell user interface (Shell UI) that was installed during the initial installation. The Shell UI includes core elements of Office that register with the operating system, such as file name extensions, Tool Tips, and right-click menu items.
When you update a multilanguage installation, you can specify that the new language matches the user locale set on the local computer. For example, if your organization includes both English-speaking and Russian-speaking users, you might first deploy English to everyone. Later, when the Russian language pack becomes available, you can add the following line to Config.xml:
In this case, Setup installs Russian language elements on any computer that has the user locale set to Russian. Users with an English user locale are not affected.
[pic]To deploy additional languages after Office is installed
|1. Copy the files and folders in the new language packs from the source media to the original network installation point. When you|
|are prompted to overwrite Setup files, click No. |
|Each language pack includes language-specific elements for every product in the Office 2010. However, Setup installs |
|language-specific elements only for the Office product that you are updating. |
|2. In the core product folder for the product that you are updating, locate the Config.xml file. |
|For example, if you are adding languages to an installation of Microsoft Office Professional Plus 2010, find the Config.xml file |
|in the ProPlus.WW folder. |
|3. Open Config.xml in a text editor, such as Notepad. |
|4. Find the element. Uncomment the line by deleting the opening tags. |
|5. Set the value of the Id attribute to the language tag that corresponds to the language that you want to install. You can |
|specify more than one language by including additional elements and attributes. |
|For example, to add the Russian language version, the line should resemble this: |
| |
|6. If you add more than one language in Config.xml, you must specify one language as the language for the Shell UI. For example: |
| |
| |
|You must specify a ShellUI language, even though Setup does not change the ShellUI language that was set for the initial |
|installation. |
|7. Save the Config.xml file. Run Setup.exe and specify the path of your modified Config.xml file. |
|You must use a full qualified path. For example: \\server\share\Office14\setup.exe /config |
|\\server\share\Office14\ProPlus.WW\Config.xml |
|where Office14 is the root of the network installation point. |
|Because Setup also recognizes language packs as separate products, make sure that you specify the Config.xml file for the Office |
|product that you are updating, and not the language pack. |
To deploy these languages for new Office 2010 installations, see Specify which languages to install in the article Customize language setup and settings for Office 2010 and import existing customization .msp files into a new customization .msp file. A static list of the products contained in the installation source is built only during the initial creation of a customization file. If you later add more languages to the installation source, the existing customization file is not updated to reflect this change. For more information, see To import a customization .msp file to add languages to an existing installation in the article Import an Office 2010 Setup customization file.
Deploy language packs
If you deployed multiple Office 2010 products in your organization and you must add more language support, you can deploy language packs as separate products. In this case, Setup installs language-specific elements for every product in Office 2010. 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 Office 2010 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. Language pack requirements range from 800MB to 1.5 GB of hard disk space that is needed.
Language-specific elements for Microsoft Project 2010 and Microsoft Visio 2010 are installed separately. In each language pack, the core product folder for Project 2010 is PMUI.ll-cc. The core product folder for Visio 2010 is VisMUI.ll-cc.
[pic]To 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 an|
|Office 2010 Multi-Language 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. |
|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. Run the language pack Setup from the root of the network installation point for the Office 2010 Multi-Language Pack or Office |
|2010 Language Pack, and specify the path of the Config.xml file on the command line. For example: |
|\\server\share\Office14\LP\Setup.exe /Config\\server\share\Office14\LP\RU\OMUI.ru-ru\Config.xml |
|where Office14\LP is the root of the network installation point for the language packs and RU is the language folder name. |
|Complete the previous steps for each language that you want to install. |
To deploy these languages for new Office 2010 installations, see Specify which languages to install in the article Customize language setup and settings for Office 2010 and import existing customization .msp files into a new customization .msp file. A static list of the products contained in the installation source is built only during the initial creation of a customization file. If you later add more languages to the installation source, the existing customization file is not updated to reflect this change. For more information, see To import a customization .msp file to add languages to an existing installation in the article Import an Office 2010 Setup customization file.
Remove language packs
If the Office 2010 Language Packs were deployed as separate products, the Language Packs can be removed by using Windows Add or Remove Programs.
If the Office 2010 Language Packs were deployed with Office 2010 and not as separate products, the procedure to remove them resembles the deployment of the Language Packs. Instead of using the tag, use the tag. See the procedure that follows for the specific steps.
You must follow these steps for each language that you want to remove.
[pic]To 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 Office Professional Plus 2010, find the Config.xml file in the |
|ProPlus.WW folder. |
|2. Open Config.xml in a text editor, such as Notepad. |
|3. Find the element. Uncomment the line by deleting the opening 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 resemble this: |
| |
|5. Find the element. If it is in the file, comment out the line by adding opening tags around |
|the element. |
|The line should resemble this: |
| |
|6. Add the 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 resemble this: |
| |
|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\Office14\Setup.exe /Config\\server\share\Office14\ProPlus.WW\Config.xml |
|where Office14 is the root of the network installation point. |
|\\server\share\Office14\LP\Setup.exe /Config\\server\share\Office14\LP\RU\OMUI.ru-ru\Config.xml |
|where Office14\LP 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
In the registry, you can view a list of languages installed for the Office 2010 either during the initial installation or during a separate installation of a language pack.
Although all applications in the Office 2010 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 Office 2010 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 Word 2010 and Microsoft Excel 2010 installed in French, but another Office 2010 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.
[pic]To identify installed languages
|1. Open the registry. |
|2. Expand the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\LanguageResources\EnabledLanguages. |
|3. The LCID for the language is displayed. To identify the language, see Language identifiers and OptionState Id values in Office |
|2010. |
|4. To view the UI language, view the following registry key values and refer to Language identifiers and OptionState Id values in |
|Office 2010. |
|• HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\LanguageResources\HelpLanguage |
|• HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\LanguageResources\UILanguage |
|5. To view the fallback languages, view the registry key value for |
|HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\LanguageResources\UIFallback. To identify the language, see Language |
|identifiers and OptionState Id values in Office 2010. |
See Also
Import an Office 2010 Setup customization file
Change users' configurations after installing Office 2010
Language identifiers and OptionState Id values in Office 2010
Customize language setup and settings for Office 2010
Plan for multilanguage deployment of Office 2010
Manage users' configurations for Office 2010
This section describes how to manage users’ configurations in Microsoft Office 2010.
In this section:
|Article |Description |
|Change users' configurations after installing Office 2010 |Provides information about how to make changes to an existing |
| |installation of Office 2010. |
Change users' configurations after installing Office 2010
This article provides information about how to make changes to an existing installation of Microsoft Office 2010.
In this article:
• Overview
• Customize an existing Office installation
• How customization works
Overview
After you install Office 2010 on users' computers, you can make changes to the installation by using the same tool that you used to customize the installation originally. By running the Office Customization Tool (OCT) and creating or modifying a Setup customization file (.msp file), you can customize the Office installation. For example, you can add or remove features, modify user settings, or add or remove files or registry entries.
In Office 2010, two architecture-specific versions of the OCT are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010. For more information about the OCT, see Office Customization Tool in Office 2010.
[pic]Note:
If you have created an initial Setup customization file (.msp file) for an Office 2010 product (for example, Microsoft Office Professional Plus 2010) and you later want to modify the installation to add language packs, you can do so by using the Import feature in the OCT. In such cases, you first add the language packs to the network installation point that contains the Office product source files. Then, you run the OCT from the root of the network installation point and create a new Setup customization file for the same product, and import the original customization .msp file that you created previously for Office Professional Plus 2010. For more information, see To import a customization .msp file to add languages to an existing installation in Import an Office 2010 Setup customization file. For information about the network installation point, see Create a network installation point for Office 2010.
Customize an existing Office installation
Use the following procedure to customize an existing installation of Office 2010.
[pic]To customize the installation
|1. From the root of the network installation point that contains the source files, run the following command line to start the |
|OCT: \\server\share\setup.exe /admin |
|2. In the Select Product dialog box, select the product that you want to customize, and then click OK. |
|3. In the left pane, select an area of customization, click the option that you want to customize, and then customize the |
|installation in the right pane. |
|For example, to remove Microsoft Access 2010 from the installation, locate Features in the left pane, and then click Set feature |
|installation states. In the right pane, expand Microsoft Office, right-click Microsoft Office Access, and select Not Available. |
|4. On the File menu, click Save As after you finish customizing the installation. |
|5. Specify a unique name for the customization file with an .msp file name extension, and then click Save. |
|6. Deploy and apply the Setup customization file (.msp) to users' computers. For more information, see Applying Setup |
|customization .msp files to existing installations. |
If you decide later that you want to make additional changes to an existing installation, you can use the OCT to create a new maintenance customization .msp file. For example, you might want to modify existing feature installation states.
As a best practice for modifying existing feature installation states on an existing installation of Office 2010, we recommend that you create a new Setup customization .msp file to make only the changes that you want to implement. To avoid unexpected results, you must specify only the changes that you want to make. For example, to create a Setup customization .msp file to add the Access feature after an initial installation, start the OCT and create a new customization .msp file for the product. In the left pane of the OCT, locate Features, and then click Set feature installation states. In the right pane, expand Microsoft Office, right-click Microsoft Office Access, and then select Run from My Computer. On the File menu, click Save As, and specify a path and file name for the .msp customization file.
How customization works
Because the Setup customization file that is created by the OCT is a Windows Installer package (.msp), you can apply the file to users' computers as you would apply a software update. The Office installation is modified by using the customizations defined in the .msp file. The following sections describe how to deploy customization .msp files to existing Office installations and show customization patch sequencing.
Applying Setup customization .msp files to existing installations
To apply the Setup customization (.msp) file to existing installations, you must apply the .msp file directly to the user's computer. You cannot apply the customization file to existing installations by placing the .msp 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.
For example, users can apply the Setup customization .msp file by double-clicking the .msp file or by running msiexec with the /p option, at a command prompt as shown in the following example:
msiexec.exe /p \\server\share\custom.msp
For information about Windows Installer command-line options, see Windows Installer Command-Line Options ().
You can also use a deployment management program, such as Microsoft System Center Configuration Manager 2010, to deploy Setup customization files. For more information, see the System Center Configuration Manager TechCenter Web site ().
Although you can use Windows Server Update Services (WSUS) to deploy software updates, you cannot use WSUS to deploy Setup customization .msp files.
Setup customization patch sequencing
Every time that you save a customization .msp file in the OCT, the tool updates the customization file’s patch sequencing number with the current computer date and time stamp and generates a new patch globally unique identifier (GUID). The OCT .msp files are applied chronologically according to their time stamps.
To show the sequencing behavior, assume that you created the following .msp maintenance files:
1. An OCT .msp file that is named uninstall-access.msp, in which you set Microsoft Office Access to Not Available. This file is saved first, so it has a lower patch sequence number and an older date and time stamp. This .msp file is sequenced first and Access is set to Not Available on users' computers.
2. An OCT .msp file that is named install-access.msp, in which you set Microsoft Office Access to Run all from My Computer. This file is saved last, so it has a higher patch sequence number and a newer date and time stamp. This .msp file is sequenced later than the first OCT .msp file, uninstall-access.msp. Therefore, Access is set to Run all from My Computer on users' computers.
See Also
Office Customization Tool in Office 2010
64-bit editions of Office 2010
Setup architecture overview for Office 2010
Import an Office 2010 Setup customization file
Security and protection for Office 2010 Beta
This section provides links to security documentation for Microsoft Office 2010. This documentation is especially useful for IT professionals who design and implement desktop security configurations for medium or large organizations. The security documentation for Office 2010 includes overview articles, planning articles, and configuration articles.
In this section:
• Overview articles
• Planning articles
• Configuration articles
Overview articles
|Article |Description |
|Security overview for Office 2010 |Provides an overview of new security controls in Office 2010 that |
| |make it easier for IT professionals to build a robust defense against|
| |threats while maintaining information worker productivity. |
|Understand security threats and countermeasures for Office 2010 |Provides information to help you plan for a secure desktop |
| |configuration for Office 2010, including which security risks and |
| |threats are relevant to Office 2010, and which might pose a risk to |
| |the organization's business assets or processes. |
Planning articles
|Article |Description |
|Plan Protected View settings for Office 2010 |Provides information about how to configure Protected View, a new |
| |security feature in Office 2010 that helps mitigate exploits to your |
| |computer by opening files in a restricted environment so they can be |
| |examined before the files are opened for editing. |
|Plan Office File Validation settings for Office 2010 |Provides information about how to configure Office File Validation, a|
| |new security feature in Office 2010 that helps prevent file format |
| |attacks by scanning Office binary file formats before the files are |
| |opened. |
|Plan Trusted Locations settings for Office 2010 |Provides information about how to use the Trusted Locations feature |
|( Office 2010 to differentiate safe files from potentially harmful |
|912a9(Office.14).aspx) |files. |
|Plan Trusted Publishers settings for Office 2010 |Provides information about how to use the Trusted Publishers feature |
|( Office 2010 to designate content publishers that you trust. |
|5a312(Office.14).aspx) | |
|Plan security settings for ActiveX controls for Office 2010 |Describes how to change the way Microsoft ActiveX controls behave in |
|( 2010 by modifying ActiveX control settings. |
|2076b(Office.14).aspx) | |
|Plan security settings for add-ins for Office 2010 |Describes how to control the way add-ins behave, or to prevent users |
| |from running add-ins, by modifying the Office 2010 add-in settings. |
|Plan security settings for VBA macros for Office 2010 |Describes how to control the way Visual Basic for Applications (VBA) |
| |and VBA macros behave by modifying Office 2010 VBA and VBA macros |
| |settings. |
|Plan privacy options for Office 2010 |Describes how to configure privacy options in Office 2010 to meet an |
| |organization’s security requirements. |
Configuration articles
|Article |Description |
|Configure security for Office 2010 |Provides information and procedures to configure security settings |
|( Office 2010 by using the Office Customization Tool (OCT) and |
|c9165(Office.14).aspx) |Group Policy. |
Troubleshooting for Office 2010 Beta
This section provides suggested solutions to troubleshooting issues that you might encounter during a deployment of Microsoft Office 2010.
In this section:
|Article |Description |
|Troubleshoot volume activation for Office 2010 |Provides troubleshooting information and suggested solutions to |
| |issues that you might encounter when activating Office 2010. |
|Troubleshoot SharePoint Workspace 2010 |Provides troubleshooting information and suggested solutions to |
| |issues that you might encounter when deploying Microsoft SharePoint |
| |Workspace 2010. |
See Also
Getting help with Office 2010
Troubleshoot volume activation for Office 2010
This article provides troubleshooting information for issues that you might encounter when activating Microsoft Office 2010. We recommend that you read Volume activation overview for Office 2010, Plan volume activation of Office 2010, Deploy volume activation of Office 2010, and Tools to configure client computers in Office 2010 before you read this article.
In this article:
• The Office 2010 KMS client does not activate
• The client activation request count on the KMS host is not high enough for client computers to activate
• The Office 2010 client does not activate when it is connected to the network through an authenticated proxy
• An activation notification dialog box displays when an Office 2010 application is started
Activation error codes
Error codes help troubleshoot activation issues. If a user sees a dialog box containing an activation notification, then an error code might be displayed at the bottom-left of the dialog box. Another way to obtain an error code is to run ospp.vbs /act on the client computer to attempt activation. If activation fails, then an error code is reported. Use ospp.vbs /ddescr with the appropriate error code to get the error message. For more information about the ospp.vbs script, see Tools to configure client computers in Office 2010.
General activation
The following are general activation issues and their solutions.
Users see notification dialogs to activate
The activation notification dialog box usually appears when the copy of Office 2010 is not yet activated. An error code is displayed on the bottom-left of the dialog box to help you troubleshoot activation issues. No dialog box is shown until 25 days after installation, at which time the user sees a notification dialog box. If Office 2010 has not been activated 30 days after installation, the notification dialog box then contains a red title bar.
When you install Office 2010, you must activate it either through Multiple Activation Key (MAK) or through Key Management System (KMS) connecting to a KMS host on your intranet.
If you installed a MAK key, you must then activate Office 2010 online.
The Office 2010 client software includes an embedded KMS client key. Once your Office 2010 KMS client automatically discovers the Office 2010 KMS host on your intranet, and at least five Office 2010 KMS clients have already requested activation from the KMS host, your KMS client is automatically activated.
Information in the Backstage view is not updated
If you click File tab | Help
The Office 2010 KMS client does not activate
There might be a number of reasons why the Office 2010 Key Management Service (KMS) client is not activated. This section describes issues and how to mitigate them.
The KMS host is not activated
Relevant error code: 0xC004F041
The KMS host must be activated first, and then the KMS clients can be activated. Please see this section on installing and activating the Office 2010 KMS host. You must run the KeyManagementServiceHost.exe file, enter the Office 2010 KMS host key, and activate.
If you are using slmgr.vbs, the Office 2010 you must activate the KMS host within the command by including the Office 2010 Activation ID:
cscript slmgr.vbs /ato bfe7a195-4f8f-4f0b-a622-cf13c7d16864
The client activation request count on the KMS host is not high enough for client computers to activate
Relevant error code: 0xC004F038
The Office 2010 KMS host must receive activation requests from at least five Office 2010 KMS clients before KMS clients on that network can be activated. If the KMS host does not receive more than five requests, KMS clients will not be activated. If you deployed Office 2010 to more than five computers, their initial activation requests will be used to build up the count. If activation fails, the computers will attempt activation two hours later. At that time, if the KMS host has a sufficient count, then activation will be successful. To trigger activation manually on the client, run ospp.vbs /act.
To determine the current count on the KMS host, at the command prompt (with administrator permissions), run the following command:
cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864
The “Current count” displayed must be 5 or higher for KMS clients to be activated. The output should be similar to the following:
Name: Microsoft Office 2010, KMSHost edition
Description: Microsoft Office 2010 KMS, VOLUME_KMS channel
Activation ID: bfe7a195-4f8f-4f0b-a622-cf13c7d16864
Application ID: 59a52881-a989-479d-af46-f275c6370663
Extended PID: 55041-00096-199-000004-03-1033-7600.0000-3632009
Installation ID: 008585014214769124199722184000850026888810090785321136
Processor Certificate URL:
Machine Certificate URL:
Use License URL:
Product Key Certificate URL:
Partial Product Key: RP3HH
License Status: Licensed
Remaining Windows rearm count: 1
Trusted time: 12/29/2009 1:45:54 PM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
The operating system that the KMS clients are running under determines how the KMS clients send activation requests.
• For Office 2010 KMS clients that are running under Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 After Office 2010 is installed, the Office Software Protection Platform (OSPP) service automatically sends activation requests to the KMS host every two hours until activation occurs, regardless of whether Office 2010 is running. Once five of these KMS clients connect to the corporate network and successfully request activation against the KMS host, the KMS clients are activated. Clients that later connect to the corporate network are also activated. KMS clients that are not on the corporate network (at home, for example) become activated once they connect to the network.
• For Office 2010 KMS clients that are running under Windows XP and Windows Server 2003 An activation request is sent when the computer is connected to the corporate network and an Office 2010 application is started. Starting an Office 2010 application starts the Configure the KMS client, which continues to run until the computer is restarted. Although the OSPP service is running, an activation request is automatically sent every two hours during the 30-day grace period. If these KMS clients connect to the corporate network, and no Office 2010 application is started, no activation requests are sent to the KMS host. There are two ways to manually send an activation request to the KMS host to increase the current count. On each KMS client, perform either of the following while connected to the corporate network:
• Launch an Office 2010 application. This sends an activation request and starts the OSPP service.
• Run cscript ospp.vbs –act from the command line with administrator permissions. The script is located in the %installdir%\Program Files\Microsoft Office\Office14 folder.
The KMS host cannot be reached
Relevant error code: 0xC004F041
If you want your KMS clients to utilize auto-discovery of the KMS host, look at the Windows documentation to ensure your DNS configuration is correct. Ensure the KMS host has network connectivity, and it is reachable by the KMS clients.
As a test on the KMS client, you may want to use ospp.vbs /sethst to specify the KMS host computer name. Then run ospp.vbs /act to send an activation request directly to the KMS host. If this is successful, then KMS host auto-discovery may be the issue. Remember to use ospp.vbs /remhst to remove the KMS host name after testing is done.
The Office 2010 client does not activate when it is connected to the network through an authenticated proxy
Independent MAK activation requires an Internet connection. If the Office 2010 client is connected to the Internet through an authenticated proxy, you must activate the client over the telephone. Please see KB article 921471 for workarounds.
See Also
Volume activation overview for Office 2010
Plan volume activation of Office 2010
Deploy volume activation of Office 2010
Tools to configure client computers in Office 2010
Office 2010 Volume Activation forum ()
Office 2010 forums ()
Troubleshoot SharePoint Workspace 2010
This article presents suggested solutions to problems that you might encounter with a Microsoft SharePoint Workspace 2010 deployment.
In this article:
• SharePoint Workspace and SharePoint Server are not synchronizing correctly
• SharePoint Workspace users receive messages about freeing disk space
SharePoint Workspace and SharePoint Server are not synchronizing correctly
Try one of the following:
• Verify that SharePoint Workspace 2010 clients are accessing a correctly installed SharePoint Server 2010. Both SharePoint Server 2010 and SharePoint Workspace 2010 installations include Microsoft Sync Framework.
• Verify that File Synchronization through SOAP over HTTP Protocol is enabled on SharePoint Server. Disabling File Synchronization through SOAP over HTTP Protocol prevents synchronization with SharePoint Workspace.
For additional assistance, see help for SharePoint Workspace at Microsoft Help and Support ().
SharePoint Workspace users receive messages about freeing disk space
To maintain performance, the number of documents that SharePoint Workspace users can store in SharePoint Workspace is limited to approximately 500 documents. If users exceed this limit, SharePoint Workspace displays a warning message every time users start SharePoint Workspace to remind them to free up disk space. If users continue to add files and their stored documents for all the SharePoint workspaces exceed 1,800, they will receive a warning message that states that only document properties will be downloaded to the workspace.
Users can ignore these messages and continue to work. However, this might affect performance. Users can reduce the number of documents that they have offline by deleting unused SharePoint workspaces, disconnecting from unused document libraries, or discarding local copies of documents.
See Also
Configure and customize SharePoint Workspace 2010
Technical reference for Office 2010 Beta
This section provides technical details related to Microsoft Office 2010 Setup properties and command-line options, and describes the Office Customization Tool and Config.xml file. It also describes the product and feature changes for Office 2010, and provides reference information for Microsoft SharePoint Workspace 2010.
In this section:
|Article |Description |
|Setup reference for Office 2010 |Provides information about the Setup properties, commands, |
| |customization tool, and configuration file that administrators use to|
| |customize a Microsoft Office 2010 client installation. |
|International reference for Office 2010 |Provides information about companion proofing languages for each |
| |language in Office 2010, the language tags and identifiers that might|
| |be needed to configure Setup, and the recommended base languages to |
| |install. |
|Product and feature changes in Office 2010 |Provides information about new features, changed features, and |
| |deprecated features for the products in the Microsoft Office 2010 |
| |suites, as well as Microsoft Project 2010 and Microsoft Visio 2010. |
| |Also included are migration considerations for the specific products.|
|SharePoint Workspace 2010 reference |Describes how to use the Office Customization Tool (OCT) and Group |
| |Policy to customize an installation of Microsoft SharePoint Workspace|
| |2010. |
Setup reference for Office 2010
This section provides information about the Setup properties, commands, customization tool, and configuration file that administrators use to customize a Microsoft Office 2010 client installation.
In this section:
|Article |Description |
|Setup properties in Office 2010 |Describes the setup properties, options in the Office Customization |
| |Tool (OCT), and elements in the Config.xml file that can be used in |
| |the installation of Office 2010. |
|Setup command-line options for Office 2010 |Describes the command-line options that Setup recognizes in the |
| |installation of Office 2010. |
|Config.xml file in Office 2010 |Describes how to use the Config.xml file to customize an installation|
| |of Office 2010. |
|Office Customization Tool in Office 2010 |Describes how to use the Office Customization Tool (OCT) to customize|
| |an installation of Office 2010. |
Setup properties in Office 2010
In versions of Microsoft Office earlier than the 2007 Microsoft Office system, you used Windows Installer properties to customize and control the Office installation. The Setup process was redesigned in the 2007 Microsoft Office system release, and most of these functions were replaced by options in the Office Customization Tool (OCT) or elements in the Config.xml file. The following information also applies to Microsoft Office 2010.
In this article:
• Property quick reference
• Available properties
• Replaced properties
• Blocked properties
• Office activation
Property quick reference
The following table summarizes the recognized Windows Installer properties that you might have used in versions of Office earlier than the 2007 Office system. The table shows if the functionality of that property is blocked and replaced by options in the OCT or Config.xml, or if the property is available for use. More detail is provided in the following sections.
|Property |Use in Office 2010 |
|ADDDEFAULT |Replaced |
|ADDLOCAL |Replaced |
|ADDSOURCE |Replaced |
|ADVERTISE |Replaced |
|ALLUSERS |Blocked |
|ARPAUTHORIZEDCDFPREFIX |Replaced |
|ARPCOMMENTS |Replaced |
|ARPCONTACTS |Replaced |
|ARPHELPLINK |Replaced |
|ARPHELPTELEPHONE |Replaced |
|ARPINSTALLLOCATION |Replaced |
|ARPNOMODIFY |Replaced |
|ARPNOREMOVE |Replaced |
|ARPNOREPAIR |Replaced |
|ARPPRODUCTICON |Replaced |
|ARPREADME |Replaced |
|ARPSIZE |Replaced |
|ARPSYSTEMCOMPONENT |Replaced |
|ARPURLINFOABOUT |Replaced |
|ARPURLUPDATEINFO |Replaced |
|CCP_DRIVE |Replaced |
|COMPADDLOCAL |Replaced |
|COMPADDSOURCE |Replaced |
|COMPANYNAME |Replaced |
|DISABLEROLLBACK |Blocked |
|EXECUTEACTION |Blocked |
|EXECUTEMODE |Blocked |
|FILEADDDEFAULT |Replaced |
|FILEADDLOCAL |Replaced |
|FILEADDSOURCE |Replaced |
|HIDEUPDATEUI |Available |
|INSTALLLEVEL |Blocked |
|INSTALLLOCATION |Replaced |
|LIMITUI |Replaced |
|LOGACTION |Blocked |
|MEDIAPACKAGEPATH |Blocked |
|NOCOMPANYNAME |Replaced |
|NOUSERNAME |Replaced |
|PIDKEY |Replaced |
|PRIMARYFOLDER |Available |
|PROMPTROLLBACKCOST |Blocked |
|REBOOTPROMPT |Blocked |
|REINSTALL |Blocked |
|REMOVE |Replaced |
|ROOTDRIVE |Available |
|SEQUENCE |Blocked |
|SETUP_REBOOT |Available |
|SOURCELIST |Replaced |
|TARGETDIR |Replaced |
|UNINSTALL |Blocked |
|USERNAME |Replaced |
Available properties
The following properties can be used when you install Office 2010 (and the 2007 Office system):
• HIDEUPDATEUI – If set to True, hides the Check for Updates button on the completion dialog box. This property is ignored if the completion dialog box is not displayed. The default value is False.
• PRIMARYFOLDER – Designates a primary folder for the installation.
• ROOTDRIVE – Specifies the default drive for the destination folder of the installation. The value for this property must end with '\'.
• SETUP_REBOOT – Determines how Setup restarts the computer after installation. You must use all uppercase letters, SETUP_REBOOT.
• AutoAlways – Always initiate a restart. Do not prompt the user.
• Always – Always prompt for a restart at the end of Setup.
• IfNeeded – Prompt for a restart at the end of Setup, if Setup requires a restart. (Default)
• AutoIfNeeded – Initiate a restart, if Setup requires a restart. Do not prompt the user.
• Never – Never initiate or prompt for a restart.
You set these properties in the Modify Setup properties page of the OCT, or the Setting element element in the Config.xml file.
Replaced properties
A number of Windows Installer properties are replaced by options in the OCT or in the Config.xml file. Some properties are not applicable in Office 2010 (or in the 2007 Office system) because of Setup design changes that were introduced in the 2007 version of the product. All of these properties are blocked by Setup. That is, if you specify any of these properties in the OCT Modify Setup properties page, or with the Config.xml Setting element, Setup will end the installation.
The following table lists blocked properties whose functions are replaced by options in the OCT or by elements in the Config.xml file.
|Property |Replacement OCT option |Replacement Config.xml element |
|SOURCELIST (in LIS element) |Additional network sources |SOURCELIST attribute inLIS element element |
|COMPANYNAME |Installation location and organization |COMPANYNAME element |
| |name | |
|INSTALLLOCATION |Installation location and organization |INSTALLLOCATION element |
| |name | |
|TARGETDIR |Installation location and organization |INSTALLLOCATION element |
| |name | |
|LIMITUI |Licensing and user interface |Display element |
|PIDKEY |Licensing and user interface |PIDKEY element |
|ARPAUTHORIZEDCDFPREFIX |None |ARP element |
|ARPCOMMENTS |None |ARP element |
|ARPCONTACTS |None |ARP element |
|ARPHELPLINK |None |ARP element |
|ARPHELPTELEPHONE |None |ARP element |
|ARPINSTALLLOCATION |None |ARP element |
|ARPNOMODIFY |None |ARP element |
|ARPNOREMOVE |None |ARP element |
|ARPNOREPAIR |None |ARP element |
|ARPPRODUCTICON |None |ARP element |
|ARPREADME |None |ARP element |
|ARPSIZE |None |ARP element |
|ARPSYSTEMCOMPONENT |None |ARP element |
|ARPURLINFOABOUT |None |ARP element |
|ARPURLUPDATEINFO |None |ARP element |
|NOCOMPANYNAME |None |None |
|NOUSERNAME |None |None |
|USERNAME |None |USERNAME element |
|ADDDEFAULT |Set feature installation states |OptionState element |
|ADDLOCAL |Set feature installation states |OptionState element |
|ADDSOURCE |Set feature installation states |OptionState element |
|ADVERTISE |Set feature installation states |OptionState element |
|COMPADDLOCAL |Set feature installation states |OptionState element |
|COMPADDSOURCE |Set feature installation states |OptionState element |
|FILEADDDEFAULT |Set feature installation states |OptionState element |
|FILEADDLOCAL |Set feature installation states |OptionState element |
|FILEADDSOURCE |Set feature installation states |OptionState element |
|REMOVE |Set feature installation states |OptionState element |
The following properties are replaced by Setup command-line options for Office 2010:
• REINSTALL – Use the Setup /repair command-line option.
• UNINSTALL – Use the Setup /uninstall command-line option.
Blocked properties
The following properties are no longer applicable in Office 2010 (and in the 2007 Office system) and are blocked. That is, if you specify these properties in the OCT Modify Setup properties page, or with the Config.xml Setting element, Setup will end the installation.
• ALLUSERS (All installations of Office 2010 and the 2007 Office system are per-computer.)
• DISABLEROLLBACK
• EXECUTEACTION
• EXECUTEMODE
• INSTALLLEVEL
• LOGACTION
• MEDIAPACKAGEPATH
• PROMPTROLLBACKCOST
• REBOOTPROMPT
• SEQUENCE
Office activation
The Microsoft policy for Office 2010 requires the activation of all editions of Office 2010, including those obtained through a Volume Licensing program. This requirement applies to Office 2010 running on both physical computers and virtual computers. Activation is not required for any Office 2010 server products, including Microsoft SharePoint Server 2010, Microsoft Project Server 2010, or for any version of Microsoft Exchange Server.
Office Activation Technologies provide the following methods for activating products licensed under Microsoft Volume Licensing programs:
• Key Management Service (KMS) – KMS uses a KMS host key to activate a KMS host computer and establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation.
• Multiple Activation Key (MAK) – With a MAK, clients activate Office 2010 online by using the Microsoft hosted activation servers or by telephone.
• A combination of KMS and MAK.
For more information about the licensing options in Office 2010, including instructions for configuring the KMS host and port number, see the Volume activation overview for Office 2010 and Volume activation quick start guide for Office 2010.
For information about Office 2010 product activation via the Internet or phone for non-volume licensed versions of Office 2010 products, see “Activate Microsoft Office programs” on the Office Online () Web site.
See Also
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Setup command-line options for Office 2010
Setup command-line options for Office 2010
The Setup.exe command line is used for very few operations in the Microsoft Office 2010 (as in the 2007 Microsoft Office system). Setup recognizes the command-line options described in this article.
In this article:
• /admin
• /adminfile [path]
• /config [path]
• /modify [ProductID]
• /repair [ProductID]
• /uninstall [ProductID]
[pic]Note:
Although Setup recognizes only a few command-line options in Office 2010, you can still make all the same modifications to the Office installation. Instead of using the command line, you use the Office Customization Tool in Office 2010 to set Setup properties and make other customizations. You can also edit the Config.xml file for the product that you are installing.
/admin
Runs the Office Customization Tool to create a Setup customization file (.msp file).
Example
\\server\share\Office14\setup.exe /admin
/adminfile [path]
Applies the specified Setup customization file to the installation. You can specify a path of a specific customization file (.msp file) or to the folder where you store customization files.
[pic]Note:
The /adminfile command-line option can be used only during initial installation of the product.
The recommended location for customization files is the Updates folder at the root of the network installation point. When you store a customization file in this folder, you do not need to specify the file on the command line. Setup automatically finds the customization file that matches the product that is being installed and applies the file during the installation. The Updates folder can only be used to deploy software updates during an initial installation of Office 2010.
If you store more than one customization file per product in the Updates folder, Setup applies all of the files to the installation. If you want to create unique configurations for different groups of users, you must store the customization files in a separate folder and specify the customization file that you want on the command line.
Example
\\server\share\Office14\setup.exe /adminfile \\server\share\MyUpdates\Engineering.msp
where Office14 is the root of the network installation point.
/config [path]
Specifies the Config.xml file that Setup uses during the installation. By default, the Config.xml file that is stored in the core product folder directs Setup to install that product. For example, the Config.xml file in the ProPlus.WW folder installs Microsoft Office Professional Plus 2010.
You can edit Config.xml to make additional customizations to the installation. This includes specifying one or more language versions to install. Use /config on the Setup command line to point to the location of the default Config.xml file for a product or to point to a custom Config.xml file.
Example
\\server\share\Office14\setup.exe /config \\server\share\Office14\ProPlus.WW\Config.xml
where Office14 is the root of the network installation point.
[pic]Note:
You must use a fully qualified path. Setup does not recognize relative paths with /config.
/modify [ProductID]
Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation. For example, you can use the /modify option to add or remove features. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify.
The Setup.xml file is located in the core product folder on the network installation point. In Setup.xml, [ProductID] is equal to the value of the Id attribute of the Setup element. For example:
Example
\\server\share\Office14\setup.exe /modify ProPlus /config \\server\share\Office14\AddOutlookConfig.xml
where Office14 is the root of the network installation point.
/repair [ProductID]
Runs Setup to repair the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify.
Example
\\server\share\Office14\setup.exe /repair ProPlus
where:
• Office14 is the root of the network installation point.
• ProPlus is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in \\server\share\Office14\ProPlus.WW\setup.xml), where ProPlus.WW is the location of the Office Professional Plus 2010 installation files.
You can customize the /repair option by using it with /config and a modified Config.xml file. This is necessary if you want to run a “silent” repair. In enterprise deployments, we recommend that you run a silent repair to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used.
[pic]To run a silent repair
|1. Using a text editor, edit the following element attributes in the \\server\share\Office14\ProPlus.WW\SilentRepairConfig.xml |
|file: |
| |
| |
| |
| |
| |
|2. At the command line, use the following syntax: |
|\\server\share\Office 14\setup.exe /repair ProPlus /config \\server\share\Office 14\ProPlus.WW\SilentRepairConfig.xml |
/uninstall [ProductID]
Runs Setup to remove the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify.
Example
\\server\share\Office14\setup.exe /uninstall ProPlus
where:
• Office14 is the root of the network installation point.
• ProPlus is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in \\server\share\Office14\ProPlus.WW\setup.xml), where ProPlus.WW is the location of the Office Professional Plus 2010 installation files.
You can customize the /uninstall option by using it with /config and a modified Config.xml file. This is necessary if you want to run a “silent” uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used.
[pic]To run a silent uninstall
|1. Using a text editor, edit the following element attributes in the \\server\share\Office14\ProPlus.WW\SilentUninstallConfig.xml |
|file: |
| |
| |
| |
| |
| |
|2. At the command line, use the following syntax: |
|\\server\share\Office 14\setup.exe /uninstall ProPlus /config \\server\share\Office 14\ProPlus.WW\SilentUninstallConfig.xml |
[pic]Note:
In Office 2010 as in the 2007 Office system, you cannot use the Setup.exe command line to set Windows Installer properties, such as PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked and unsupported properties, see Setup properties in Office 2010.
See Also
Office Customization Tool in Office 2010
Config.xml file in Office 2010
Config.xml file in Office 2010
Administrators use the Config.xml file to perform installation and maintenance tasks for Microsoft Office 2010.
The primary tool that administrators use to customize the installation of products in Office 2010 is the Office Customization Tool (OCT). The customization tools and methods in Office 2010 are the same as for the 2007 Microsoft Office system. For more information about how to use the OCT to create a Setup customization file and to learn about updates to the OCT in Office 2010, see Office Customization Tool in Office 2010.
The Config.xml file is used to configure installation tasks and is used only when you run Setup. Config.xml is not installed or cached on users' computers. Administrators 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, ProPlus.WW) directs Setup to install that product. For example, the Config.xml file in the ProPlus.WW folder installs Microsoft Office Professional Plus 2010.
You use the Config.xml file to perform the following installation tasks:
• Specify the path of the network installation point.
• Select which product to install.
• Customize Setup options, such as logging and the location of the Setup customization file and software updates.
• Set installation options, such as user and company name.
• Copy the Local Install Source (LIS) to the user's computer without installing Microsoft Office.
• Add or remove languages from the installation.
The Config.xml file can also be used for maintenance operations such as adding or removing features, repairs, and removing installations. To do this, administrators must run Setup.exe again from the original source.
[pic]Important:
To edit Config.xml, use a text editor, such as Notepad. Do not use a general-purpose XML editor, such as Microsoft Word 2010.
In this article:
• Config.xml element quick reference
• How Setup uses Config.xml
• Config.xml file format
• Config.xml element reference
• Sample Config.xml file
Config.xml element quick reference
The following table lists the Config.xml elements. These elements can appear in any order, except for Configuration element, which must be first, and elements such as Command element, whose order in Config.xml affects how they are processed during installation.
|Element |Description |
|Configuration element |Top-level element |
|AddLanguage element |Add a language to the installation |
|ARP element |Values that control the text and behavior of the Programs and |
| |Features option, in Control Panel, to add or remove features for the |
| |product |
|Command element |Run a command during installation |
|COMPANYNAME element |The name of the organization or company of the user on whose computer|
| |the product is being installed |
|Display element |The level of UI that Setup displays to the user |
|DistributionPoint element |The fully qualified path of the network installation point from which|
| |the installation is to run |
|INSTALLLOCATION element |The fully qualified path of the folder on the user's computer in |
| |which the product is installed |
|LIS element |Options for how the Local Install Source (LIS) is cached on the |
| |user's computer |
|Logging element |Options for the kind of logging that Setup performs |
|MinOSRequirement element |The minimum supported operating system for this product |
|OptionState element |Options to specify how individual product features are to be handled |
| |during installation |
|PIDKEY element |The 25-character volume license key |
|RemoveLanguage element |Remove a language from the installation |
|Setting element |Values for Windows Installer properties |
|SetupUpdates element |The search path for Setup to use to find Setup customization files |
|USERINITIALS element |The initials of the user on whose computer the product is being |
| |installed |
|USERNAME element |The name of the user on whose computer the product is being installed|
How Setup uses Config.xml
Setup looks for a copy of Config.xml in the same folder as Setup.exe. If a copy is not found there, Setup uses the Config.xml file that resides in the core product folder for the product that you are installing. (If multiple products are in the network installation point, Setup waits until you specify which product to install before it looks for the copy of Config.xml.) The copy of Config.xml that resides in the product folder identifies the product through the Product attribute of the Configuration element element.
You can also use the /config Setup command-line option to specify the location of the Config.xml file. For example:
\\server\share\setup.exe /config \\server\share\ProPlus.WW\config.xml
[pic]Note:
If you also created a Setup customization (.msp) file by using the OCT, the customizations that you define in Config.xml take precedence over those in the customization file.
Config.xml file format
XML elements in Config.xml begin with < and end with />.
The basic element format is as follows:
For example:
The following statements apply to format:
• Elements and attributes are case-sensitive.
• Attribute values must be enclosed in quotation marks (") and are not case-sensitive.
• An element definition can span multiple lines. Spaces, carriage returns, line feeds, and tab characters are ignored in an element definition.
The following is an example of an element definition that spans multiple lines.
[pic]Tip:
For long element definitions, put attributes on separate lines and use indentation to make the file easier to read.
The Configuration element element is a special case and is required. All other elements are contained in the Configuration element element, and the element is closed with , as shown in the following example.
Comments can be added anywhere and are delimited by "".
For example:
Level="none"
CompletionNotice="no"
SuppressModal="yes"
AcceptEula="Yes"
/
Each Office product folder contains a default Config.xml file, which consists of a Configuration element element that has the Product attribute set to the appropriate value for the product. A number of example elements enclosed in comments are included in the Configuration element element. To activate these elements, remove the beginning and closing comment marks and enter the appropriate attribute values.
As shown in the following example, you can activate the PIDKEY element element by changing this line:
to this:
The Display options in the previous example direct Setup to run a silent installation, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction.
Config.xml element reference
The following conventions are used in the descriptions in this reference.
|bold |Element or attribute name |
|normal |Text to be entered exactly as shown |
|italic |Placeholder for a value to be added |
|x|y |Choose among multiple values |
|[x] |Optional value |
Configuration element
Top-level element. This element is required, and all other elements must appear in this element.
Syntax
...
Attributes
|Attribute |Value |Description |
|Product |productID |The value of the ID attribute in the Setup |
| | |element in the Setup.xml file for the product |
| | |that is being installed. |
Remarks
The Product attribute identifies the product affected by this Config.xml file. The productID is defined in the Setup.xml file that is located in the core folder for the product, in the ID attribute of the Setup element.
The Product attribute is optional, unless you set the Display elementLevel attribute to “basic” or “none”. In this case, the Product attribute is required. If the product specified by the Product attribute does not exist in the network installation point, Setup ends the installation.
Example
The productID for Microsoft Office Professional Plus 2010 is located in ProPlus.WW\Setup.xml in the following line:
You use this productID in Config.xml to specify Office Professional Plus 2010 by entering the following:
...
AddLanguage element
Adds the specified language to the installation.
Syntax
Attributes
|Attribute |Value |Description |
|Id |ll-cc |The language identifier. |
| |match |Matches the language Id of the user's Windows |
| | |user locale. |
|ShellTransform |Yes |Specifies the language for the shell user |
| | |interface. If more than one AddLanguage element|
| | |is specified, one (and only one) language must |
| | |specify the ShellTransform element. |
Remarks
The language must be available on the network installation point.
You can have multiple AddLanguage and RemoveLanguage element elements. If both the RemoveLanguage element element and the AddLanguage element specify the same language, the AddLanguage element takes precedence and the language is installed.
[pic]Note:
If more than one AddLanguage element is specified, one (and only one) language must specify the ShellTransform element or Setup ends the installation.
There are three language concepts that you should know about when you install the Office 2010:
• Setup user interface (UI): the language of the installation.
• Shell UI: the language of shortcuts, right-click context menus, and tooltips.
• Office UI: the language of the Office user interface and menus.
When there are multiple Office languages, these three values are determined as follows:
By default, the Setup UI depends on the set of available resources for installation and the ability to match the user locale. By default, the Setup UI matches the user locale. The Shell UI depends on the set of languages that is being installed and, by default, follows the Setup UI. The default Office UI language depends on the user locale and current user settings. The default is to use the Windows user locale set on each user's computer. This means that in the default case, the Setup UI, Shell UI, and Office UI will all be the same.
A locale in the Windows operating system is a set of user preference information related to the user's language, environment, and cultural conventions. This information is represented as a list of values that are used to determine the correct input language, keyboard layout, sorting order, and the formats that are used for numbers, dates, currencies, and time. The user locale is a per-user setting that determines the formats that are used, by default, to display dates, times, currency, and numbers, and the sorting order of text. A user locale is specified for each account that is created on a computer.
If an administrator specifies multiple languages for installation in the Config.xml file, the Shell UI language must be selected from the set of languages that are being installed. To do this, administrators specify the ShellTransform attribute of the AddLanguage element in the Config.xml file. AddLanguage specifies the language that Setup uses for the Shell UI. However, this will not necessarily affect the choice of Setup UI or Office UI when it is installed on the user’s computer.
For example, if you have an Office image with English, French, German, and Spanish, to specify that Setup install full language support for all these languages and have the Shell UI follow the user’s default regional options, you add the following elements in the Config.xml file.
In the previous example, Setup installs all the specified languages and the Shell UI matches the language of the user's locale. If more languages were available in the source image, the match value in the previous example might install an additional language if the match language does not resolve to one of the other four explicitly called-out languages. For instance, if Japanese was also included in the source, this example would install Japanese in addition to the other four languages when it is installed on a computer that has the user locale set to Japanese.
Example
ARP element
Specifies values that control the text and behavior of Programs and Features in Control Panel for the product.
Syntax
Attributes
|Attribute |Value |Description |
|ARPCOMMENTS |text |Additional text. Can be up to 255 |
| | |characters, although all characters might |
| | |not be displayed. |
|ARPCONTACT |text |List of technical support contacts. |
|ARPNOMODIFY |Yes |Prevents users from modifying the product |
| | |installation by making the Change button |
| | |unavailable. |
| |No (default) |Allows users to modify the product |
| | |installation. |
|ARPNOREMOVE |Yes |Making the Remove button unavailable |
| | |Prevents users from removing the product by |
| | |making the Remove button unavailable. |
| |No (default) |Allows users to remove the product. |
|ARPURLINFOABOUT |URL |URL for the product's home page. |
|ARPURLUPDATEINFO |URL |URL for information about product updates. |
|ARPHELPLINK |URL |URL of a Web site where users can receive |
| | |technical support. |
|ARPHELPTELEPHONE |text |Telephone numbers for technical support. |
Command element
Specifies a command line to run. For more information, see Remarks later in this article.
[pic]Tip:
The equivalent option in the OCT is Add installations and run programs.
Syntax
Attributes
The following table describes the Command element attributes.
|Attribute |Value |Description |
|Path |path |Fully qualified path of the executable file. If |
| | |the path value contains a space, you must use |
| | |double quotes as shown in the following example: |
| | |"\\server\share\Office 14\copylogs.bat" |
|QuietArg |string |String of arguments to be appended to the command|
| | |line if you configure a silent installation. For |
| | |more information about when to use the QuietArg |
| | |attribute, see the Remarks section that follows |
| | |this table. |
|Args |string |String of arguments to be passed to the |
| | |executable. For information about when to use the|
| | |Args attribute for chained installations, see the|
| | |Remarks section, following this table. |
| | |If the value of the Args element includes |
| | |quotation marks, you can enclose the entire value|
| | |in single (') quotes as shown in the following |
| | |example: |
| | |Args='"/param value"' |
|ChainPosition |Before |This command is executed before the primary |
| | |product installation. |
| |After (default) |This command is executed after the primary |
| | |product installation. |
|Wait |mseconds |When you install a product with the Display |
| | |elementLevel attribute set to "full" or “basic”, |
| | |this is the number of milliseconds to wait after |
| | |you run the program before you continue the |
| | |installation. The default is 0 (zero), which |
| | |indicates no waiting. |
|Execute |Install (default) |Setup executes this command when the primary |
| | |product is installed. |
| |Uninstall |Setup executes this command when the primary |
| | |product is uninstalled. |
|Platform |x86 (default) |Specifies that this program requires the Intel |
| | |x86 platform. This command runs only if the |
| | |computer on which the installation is run matches|
| | |this platform requirement. |
| |x64 |Specifies that this program requires a 64-bit |
| | |processor that supports the x64 extensions to the|
| | |x86 architecture. This command runs only if the |
| | |computer on which the installation is run matches|
| | |this platform requirement. |
Remarks
The Command element in 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 installations and uninstallations. The Command element commands are processed only during initial installations and uninstallations. If Command element commands are used for customizations after the initial installation, they are ignored.
The command line can be specified to run an arbitrary command or to run a lightweight executable that you want to run when this product is installed.
The Command element in Config.xml and the Add installations and run programs option in the OCT do not provide the software deployment capabilities that an enterprise software deployment and management tool provides, such as the ability to track deployment progress and troubleshoot problems. Therefore, it is recommended that you limit the use of Command element in Config.xml and Add installations and run programs in the OCT to running only lightweight executables or arbitrary commands that will not make changes to the computer or that do not require user input. For example, you can run a utility to copy logs or a command to launch a Welcome page at the end of installation.
[pic]Important:
Chaining is not as reliable as installing each product separately. For example, if you chain two installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation might not be completed successfully. Therefore, using the chaining approach is not recommended. The recommended method for installing multiple products together in enterprise environments is to use a deployment management program, such as Microsoft System Center Configuration Manager 2010 or Microsoft Systems Management Server (SMS) 2003, or a third party tool, instead of chaining.
The use of Args and QuietArg is as follows:
• The Args attribute is always appended to the command. This can include switches such as "/install" or "Company=MyCorporation".
• The QuietArg attribute is also appended if setup is running silently (with Display set as Display="none"). In such cases, you can specify the QuietArg attribute with the "/quiet" switch, for example, you can use: QuietArg="/quiet".
The following statements apply to the Wait attribute:
• Setting the Wait attribute to 0 milliseconds indicates no waiting after you run the program before you continue the installation; the command will execute and move on immediately.
Return codes are only respected if the Wait value is nonzero. If you specify 0, Setup will not wait to continue the installation after running the specified program; therefore, there is no return code to report in that case.
• Setting the Wait attribute to any positive nonzero value will wait exactly the number of milliseconds you specify. If the process ends earlier than the specified time, setup will continue. If the process has not ended when the specified time is up, setup will fail.
• Setting the Wait attribute to -1 indicates to wait indefinitely. This can be problematic because if the command process stops responding (hangs), setup will stop responding and will wait indefinitely for the command to run.
If there are two or more Command elements in the Config.xml file, they run in the order in which they are specified in Config.xml.
Examples
COMPANYNAME element
The name of the organization or company of the user on whose computer the product is being installed.
[pic]Tip:
The equivalent option in the OCT is the Organization name setting in Installation location and organization name.
Syntax
Attributes
|Attribute |Value |Description |
|Value |companyname |The company or organization name. |
Example
Display element
The level of UI that Setup displays to the user.
[pic]Tip:
The equivalent option in the OCT is the Display level and license agreement settings in “Licensing and user interface” in Office Customization Tool in Office 2010.
Syntax
Attributes
|Attribute |Value |Description |
|Level |None |No Setup UI is displayed. If you set Display |
| | |Level="none", Setup runs a silent (unattended)|
| | |installation. See the Remarks section for more|
| | |information. |
| |Basic |Setup displays a Welcome screen, the product |
| | |key (PIDKEY) page (if needed), the software |
| | |license terms page (if needed), a progress |
| | |bar, and the completion notice (if allowed). |
| |Full (default) |Setup displays all UI to the user. |
|CompletionNotice |Yes |Only applies if Level is set to "basic" or |
| | |“none”: Setup displays the completion notice. |
| |No (default) |Only applies if Level is set to "basic": Setup|
| | |does not display the completion notice. |
|SuppressModal |Yes |Only applies if Level is set to "basic": Setup|
| | |does not display error messages and other |
| | |dialog boxes that might interrupt the |
| | |installation. |
| |No (default) |Only applies if Level is set to ”basic”: Setup|
| | |displays errors and other dialog boxes as |
| | |needed. |
|NoCancel |Yes |If Level is set to "full" or "basic", disable |
| | |the cancel button (X in upper-right corner of |
| | |the progress dialog box). |
| |No (default) |If Level is set to "full" or "basic", let the |
| | |user cancel the installation from the progress|
| | |bar. |
|AcceptEULA |Yes |The End-User License Agreement (EULA) is |
| | |accepted on behalf of the user. Setup does not|
| | |display the software license terms page. |
| |No (default) |If Level is not set to ”none”, Setup displays |
| | |the software license terms page. |
Remarks
If this element is not defined, the default settings are used. If an invalid value is specified, Setup ends the installation.
If the Level attribute is set to "basic" or “none” and you supply a product key using the PIDKEY element element, Setup assumes that you also accept the license agreement on behalf of the user.
[pic]Note
• In enterprise deployments, we recommend that you set the Display Level value to “none” to direct Setup to run a silent installation, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used. Setting the Display Level value to “none” assumes that the SuppressModal and CompletionNotice attributes are silenced and that the Microsoft Software License Terms is accepted. Administrators must also make sure that no Office applications run during an installation of the Office 2010.
• If you set the Display Level value to “basic” and SuppressModal to “yes”, users might be prompted if any Office files are being used. Setting Display Level to “none” prevents prompting users in these cases. The SuppressModal attribute does not prevent files in use messages from being displayed. Only if Display Level is set to “none” are files in use messages prevented from being displayed.
• The Display element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, Setup uses the default display options.
Example
DistributionPoint element
Specifies the fully qualified path of the network installation point from which the installation is to run.
Syntax
Attributes
|Attribute |Value |Description |
|Location |path |The fully qualified path of the network |
| | |installation point from which the installation |
| | |is to run. |
Remarks
If this is not specified, Setup assumes that the Setup.exe file is located at the root of the network installation point.
[pic]Note:
The DistributionPoint element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, it ignores this element because the network installation point has already been found.
Example
INSTALLLOCATION element
Specifies the fully qualified path of the folder on the user's computer where the product is installed.
[pic]Tip:
The equivalent option in the OCT is the Default installation path setting in Installation location and organization name.
Syntax
Attributes
|Attribute |Value |Description |
|Value |path |The fully qualified path of the folder on the |
| | |user's computer in which the product is |
| | |installed. |
Remarks
You can use system environment variables in the path. If this element is not specified, Office is installed in %ProgramFiles%\Microsoft Office.
Example
LIS element
Controls how the Local Installation Source (LIS) is cached on the user's computer and specifies the location of one or more network installation points that contain the installation files for the product.
Syntax
Attributes
|Attribute |Value |Description |
|CACHEACTION |CacheOnly |Setup copies the LIS to the user's |
| | |computer, but does not install the product.|
| |RemoveCacheOnly |If the cache is copied to the user's |
| | |computer and Office is not installed, Setup|
| | |removes the LIS from the user's computer |
| | |but does not install or uninstall the |
| | |product. |
|SOURCELIST |semicolon-delimited-path-list |A list, separated by semicolons, of one or |
| | |more network installation points that |
| | |contain the installation files for the |
| | |product. |
| | |The equivalent option in the OCT is |
| | |Additional network sources. |
Remarks
By default, the LIS is created in the folder \MsoCache\All Users at the root of the drive on which Office is installed. Setup customization files and software updates in the Updates folder in the network installation point are also copied.
If you specify INSTALLLOCATION element, the drive designation in the path is used to determine on what drive the LIS is created. For example, if the INSTALLLOCATION element path is E:\office\files, the LIS is created on drive E. The sources listed by the SOURCELIST attribute are kept with the installed product and are used by Setup if the LIS on the user's computer is missing or corrupted.
Example
Logging element
Specifies the kind of logging that Setup performs.
Syntax
Attributes
|Attribute |Value |Description |
|Type |Off |Setup performs no logging. |
| |Standard (default) |Setup writes installation information to the log|
| | |file. |
| |Verbose |Setup writes all installation information to the|
| | |log file. |
|Path |path |The fully qualified path of the folder used for |
| | |the log file. You can use environment variables.|
| | |Default is %temp%. |
|Template |filename.txt |The name of the log file. If you insert the |
| | |string * anywhere in the file name, a unique log|
| | |file is created for each installation performed |
| | |by setup.exe (see the explanation later in this |
| | |article). If the * character is not included and|
| | |the file name that is specified already exists, |
| | |log information is appended to the existing |
| | |file. The .txt file name extension must be |
| | |included. The default template is |
| | |SetupExe(*).log. |
Remarks
You can specify a * anywhere in the Template value. Setup inserts a string in that location that has the following format.
YYYYMMDDHHMMSSxxx
where:
1. YYYY = Year
2. MM = Month
3. DD = Day
4. HH = Hour
5. MM = Minute
6. SS = Seconds
7. xxx = a unique string generated by Setup
[pic]Note:
The Logging element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, Setup uses the default logging options.
Example
With this example, Setup creates a log file every time that it installs the product. Setup uses unique file names such as the following.
%temp%\MyLog(20060428110717CFC).txt
%temp%\MyLog(20060429113143C70).txt
MinOSRequirement element
Specifies the minimum supported operating system for this product.
Syntax
Attributes
|Attribute |Value |Description |
|VersionNT |version |Windows NT version. |
|WindowsBuild |number |Windows build number. |
|ServicePackLevel |number |Windows service pack (SP) number. |
The following values can be used.
|System |VersionNT |WindowsBuild |ServicePackLevel |
|Windows XP |501 |2600 |2 or greater |
|Windows Server 2003 |502 |3790 |0 or greater |
Remarks
Setup does not continue with the installation if the user's computer has an operating system with a version earlier than what is specified here (or the Office default if this element is not specified). You cannot specify a version of Microsoft Windows here that is earlier than the version required by Office 2010.
For information about system requirements, see Getting started with the deployment of Office 2010.
OptionState element
Specifies how specific product features are handled during installation.
[pic]Important:
In most situations, we recommend that you use the OCT to change the installation state of features. The equivalent option in the OCT is Set feature installation states.
Syntax
Attributes
|Attribute |Value |Description |
|Id |optionID |An item that the user can choose to install. |
|State |Absent |The feature is not installed. |
| |Advertise |The feature is installed the first time that |
| | |it is used. |
| |Local |The feature is installed on the user's |
| | |computer. |
|Children |force |All child features of the feature are set to |
| | |the specified state. |
Remarks
A feature is an item that the user can choose to install. The Id value for a feature is defined in the Option element of the Setup.xml file in the core product folder.
[pic]Note
• The following subcomponents of Microsoft Publisher 2010 are not visible in the Setup feature installation state tree in Office 2010.
Example
PIDKEY element
The 25-character volume license key.
[pic]Note
• The equivalent option in the OCT is the Product key setting in “Licensing and user interface” in Office Customization Tool in Office 2010. For more information about volume licensing in Office Professional 2010, see Volume activation overview for Office 2010 and Tools to configure client computers in Office 2010.
• A product key entry is not required for enterprise deployments that use Key Management Service (KMS) activation because all Volume License editions of Office 2010 have a KMS client key pre-installed. KMS is one of the methods that are provided by Office Activation Technologies for activating products licensed under Microsoft Volume Licensing programs. KMS uses a KMS host key to activate a KMS host computer and establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. By default, the Use KMS client key option is selected in the OCT (in the Licensing and user interface section).
• A Multiple Activation Key (MAK) key is another method that Office Activation Technologies provide for activating products licensed under Microsoft Volume Licensing programs. By using a MAK, clients activate Office 2010 online with Microsoft-hosted activation servers or by telephone. Administrators can use the Config.xml file to enter a MAK key. See the Remarks section for more information about how to add a MAK key.
Syntax
Attributes
|Attribute |Value |Description |
|Value |25-character-key |The 25-character volume license key. |
Remarks
When the PIDKEY value is set, users are not required to enter a product key when they install Office.
To enter a MAK key in the Config.xml file, add the following line to the file.
Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key. For more information about licensing for Office 2010, see the Volume activation overview for Office 2010.
Example
[pic]Note:
If the Level attribute of the Display element element is set to "basic" or "none" and you supply a product key by using the PIDKEY element, Setup assumes that you also accept the license agreement on behalf of the user. In this case, regardless of how you set the AcceptEULA attribute of the Display element element, the user is not prompted for the license agreement either during installation or the first time that an Office application runs.
RemoveLanguage element
Removes the specified language from the installation.
Syntax
Attributes
|Attribute |Value |Description |
|Id |ll-cc |The language identifier. |
Remarks
If the language is not installed on the user's computer, the RemoveLanguage element is ignored.
You can have multiple AddLanguage element and RemoveLanguage elements. If both RemoveLanguage and AddLanguage element elements specify the same language, the AddLanguage element element takes precedence and the language is installed.
Example
Setting element
Allows you to specify values for Windows Installer properties.
[pic]Tip:
The equivalent option in the OCT is “Modify Setup properties” in Office Customization Tool in Office 2010.
Syntax
Attributes
|Attribute |Value |Description |
|Id |name |The name of the Windows Installer property. |
|Value |value |The value to assign to the property. |
Remarks
Not all Windows Installer properties can be specified in the Setting element. If a blocked property is specified, Setup ends the installation process. If a supported property is specified, Setup passes the property directly to Windows Installer. For a complete list of Windows Installer properties, which includes an explanation of supported and blocked properties, see Setup properties in Office 2010.
The Setting element supports the REMOVEPREVIOUS setting. This setting removes the specified application from the installation and uses the following syntax.
where Option Id is the identifier value for the Office 2010 application. To specify multiple applications, use a comma-separated list to indicate the appropriate Option Id values.
[pic]Note:
If you install Outlook, a previously installed version of Outlook is always removed, regardless of the user’s preference.
If you specify REMOVEPREVIOUS with an Option Id value, only the specified applications are removed.
If you do not specify REMOVEPREVIOUS, any previously installed Office applications for which a replacement is being installed are removed. This is the default behavior.
If you specify REMOVEPREVIOUS with a blank value (REMOVEPREVIOUS=""), no applications are removed.
The Setting element also supports the SETUP_REBOOT property. SETUP_REBOOT begins a restart after installation and uses the following syntax:
where value can be one of the following:
• AutoAlways — Always begin a restart. Do not prompt the user.
• Always — Always prompt for a restart at the end of setup.
• IfNeeded — Prompt for a restart at the end of setup if setup requires a restart. (Default)
• AutoIfNeeded — Begin a restart if setup requires a restart. Do not prompt the user.
• Never — Never begin or prompt for a restart.
Examples
SetupUpdates element
Specifies a search path for Setup to use to find Setup customization files.
Syntax
Attributes
|Attribute |Value |Description |
|CheckForSUpdates |Yes (default) |Setup uses the path list in SUpdateLocation to |
| | |find Setup customization files. |
| |No |Setup does not search for Setup customization |
| | |files by using the path list in |
| | |SUpdateLocation. |
|SUpdateLocation |path-list |A list of fully qualified paths to folders, |
| | |separated by semicolons. |
Remarks
Setup looks in all the specified folders for Setup customization files that were created for the product that is being installed, and applies them in alphabetical order by file name. If a Setup customization file was specified in the Setup command line, that file is applied first, followed by any files that are found in the folder that is specified by this element.
Example
USERINITIALS element
The initials of the user on whose computer the product is being installed.
Syntax
Attributes
|Attribute |Value |Description |
|Value |value |The user's initials |
Example
USERNAME element
The name of the user on whose computer the product is being installed.
Syntax
Attributes
|Attribute |Value |Description |
|Value |value |The user's name. |
Remarks
The Office 2010 Username element data is populated as follows.
If the user who runs Office is the same user who installed Office, the Username and Initials supplied during setup are used. The user is not prompted when Office first starts. This case is most popular for home users who install Office themselves.
If the user who is running Office is not the same user who installed Office, Office prompts the user to confirm his or her Username and Initials when Office first starts. This case is most popular in a corporate environment, where an administrator installs Office for the user.
The value for the Username element shown to the user at first start time might be pre-populated with a default value from a previously installed version of Office or from the currently logged-on user. Note that the default value is not used unless it is confirmed by the user. If an earlier version of Office is installed on the computer, the registry key that was created by the earlier version of Office is used. For example, if the previous Office installation is Microsoft Office 2003, the registry key is provided at HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\UserInfo.
Example
Sample Config.xml file
The following example shows a Config.xml file for a typical installation. The example uses the Office Professional Plus 2010 version of the product.
See Also
Setup architecture overview for Office 2010
Office Customization Tool in Office 2010
Setup properties in Office 2010
Setup command-line options for Office 2010
64-bit editions of Office 2010
Office Customization Tool in Office 2010
This article describes how to use the Office Customization Tool (OCT) to customize an installation of Microsoft Office 2010.
In this article:
• Overview of the Office Customization Tool
• New Office Customization Tool features in Office 2010
• Architecture-specific versions of the Office Customization Tool
• Importing Office Customization Tool .msp customization files
• Configuring Setup, Features, Additional content, and Outlook settings
• Setup
• Features
• Additional content
• Outlook
Overview of the Office Customization Tool
The OCT is part of the Setup program and is the recommended tool for most customizations. You run the OCT by typing setup.exe /admin at the command line from the root of the network installation point that contains the Office 2010 source files. For example, use the following: \\server\share\Office14\setup.exe /admin. The OCT is available only with volume licensed versions of Office 2010 and the 2007 Office system. To determine whether an Office 2010 installation is a volume licensed version, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a volume license edition. If the Admin folder does not exist, the disk is a retail edition. For information about the network installation point, see Create a network installation point for Office 2010.
When you run the OCT, you choose to create a new Setup customization (.msp) file or to open an existing .msp file. If you create a new file, the OCT displays a list of the products that are available on the network installation point. You must select a single product that you want to customize.
If you use the OCT to modify an existing .msp customization file, we recommend that you select the .msp file for the same product that you customize. For example, if you customize Microsoft Office Professional Plus 2010, select an Office Professional Plus 2010 customization .msp file.
[pic]Note:
The Office 2010 release requires Windows Installer 4.0 or a later version on all computers on which Office runs. This includes the computer that you use to run the OCT. For information about Windows Installer, see Windows Installer ().
Using the OCT, you customize Office and save your customizations in a Setup customization .msp file. You place the file in the Updates folder on the network installation point. When you install Office, Setup looks for a Setup customization file in the Updates folder and applies the customizations. The Updates folder can only be used to deploy software updates during an initial installation of Office 2010.
[pic]Important
• If you plan to deploy multiple Setup customization files (.msp files), you can place only one customization .msp file for each Office 2010 product that you are installing in the Updates folder for an initial installation. You must deploy the rest of the customization .msp files for a product after the Office installation is completed. Only one Setup customization file per product in the Updates folder is supported. If you are deploying multiple Office 2010 products, such as Microsoft Office Professional Plus 2010 and Microsoft Visio Professional 2010, you can include one customization .msp file for Office Professional Plus 2010 and one customization .msp file for Visio Professional 2010 in the Updates folder. The customization .msp files that you place in the Updates folder will be deployed first. Therefore, they must include any Setup customizations that cannot be changed after the installation, for example, the installation location.
• If you are deploying an initial installation of Office 2010 and you also want to deploy Office 2010 software updates, such as service packs and hotfixes, Setup can apply the product updates as part of the installation process. You can place the Office 2010 product updates in the Updates folder. In scenarios such as this where the Updates folder includes both one Setup customization .msp file and product updates, Setup applies only the Setup customization .msp file with the initial installation and the product updates are applied after the installation is complete.
As an alternative to placing the customization .msp file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully-qualified path of the location of the .msp file. For example, type: setup.exe /adminfile \\server\share\mychanges\custom.msp.
If you use a folder other than the Updates folder for your customization files, you can specify the folder's location in the Config.xml file by using the SUpdateLocation attribute of the SetupUpdates element. The Config.xml file is located in the core product folder (core_product_folder_name.WW folder, for example, ProPlus.WW for Microsoft Office Professional Plus 2010) for the Office 2010 product that you install. For more information, see Config.xml file in Office 2010.
You can also use a Setup customization file to change an existing installation. Because a Setup customization file is an expanded form of a Windows Installer .msp file, you apply the customization file to the user's computer exactly as you would a software update. The user's existing Office installation is updated with the customizations that you make. For example, if you change the installation states of some features to Not Available and apply the resulting customization file to an existing installation of Office, those features are removed from the user's computer.
Some options in the OCT are applicable only to a new installation of Office. These options are identified in the OCT and in the OCT Help. For example, you can use the Default installation path option (in the Installation location and organization name section) to specify the folder where Office is to be installed on the user's computer. However, if a customization file is applied to an existing installation, the Default installation path option is ignored (you must uninstall and reinstall Office to change the installation location).
Before you exit the OCT, click the File menu and then click Save as to save the Setup customization file.
Every time that you save a customization file in the OCT, the tool updates the customization file’s sequencing number with the current computer date and time stamp and generates a new update globally unique identifier (GUID). The OCT MSP files are applied chronologically according to their time stamp.
To show the sequencing behavior, assume that you have created the following OCT .msp maintenance files:
1. An OCT .msp file that is named “uninstall-access.msp” in which you set Microsoft Office Access to Not Available. This file is saved first so that it has a lower sequencing number and an older date and time stamp. This .msp file is sequenced first and Access 2010 is set to Not Available on users' computers.
2. An OCT .msp file named "install-access.msp" in which you set Microsoft Office Access to Run All from My Computer (by selecting the product and setting the installation state in the Set feature installation states section). This file is saved last so that it has a higher sequencing number and a newer date and time stamp. This .msp file is sequenced later than the first OCT .msp file, "uninstall-access.msp". Therefore, the Access 2010 feature is set to Run All from My Computer on users' computers.
The OCT includes four major sections: Setup, Features, Additional Content, and Outlook. Each section contains several pages of options. When you change an option, the page name in the left pane of the OCT changes to bold type. If you open an existing Setup customization file, the bold page names indicate where options are customized.
The following table lists options that are available in the OCT.
|Section |Page |
|Setup | |
| |Installation location and organization name |
| |Additional network sources |
| |Licensing and user interface |
| |Remove previous installations |
| |Add installations and run programs |
| |Office security settings |
| |Modify Setup properties |
|Features | |
| |Modify user settings |
| |Set feature installation states |
|Additional content | |
| |Add files |
| |Remove files |
| |Add registry entries |
| |Remove registry entries |
| |Configure shortcuts |
|Outlook | |
| |Outlook Profile |
| |Add Accounts |
| |Export Settings |
| |Specify Send/Receive Groups |
New Office Customization Tool features in Office 2010
The Office 2010 release provides the following new features:
• Two architecture-specific versions of the OCT, one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. The OCT files are located in the Admin folder under the x86 (32-bit) and x64 (64-bit) folders, respectively.
For information about 64-bit Office 2010, see 64-bit editions of Office 2010.
• Import feature that allows administrators to import 32-bit OCT customization .msp files into the 64-bit version of the OCT and 64-bit .msp files into the 32-bit version of the OCT. This allows administrators of mixed environments (32-bit and 64-bit) to do the Setup customizations one time.
• Support for adding multiple Outlook e-mail accounts.
For more information about how to import .msp customization files, see Import an Office 2010 Setup customization file.
Architecture-specific versions of the Office Customization Tool
As mentioned earlier in this article, administrators run the following command-line option to start the OCT from the root of the network installation source: setup.exe /admin. You use the same command to run the 32-bit or 64-bit version of the OCT. Running setup.exe /admin on a 32-bit computer starts the 32-bit OCT, and running this command on a 64-bit computer starts the 64-bit OCT.
To run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder.
Setup detects which products are available to create Setup customization updates and lists the results in the Create a new Setup customization file for the following product list. Because the 64-bit and 32-bit Office files are in different root directories, the 32-bit OCT lists all the 32-bit Office products in the product selection dialog box (Create a new Setup customization file for the following product), and the 64-bit OCT lists the 64-bit Office products.
Administrators use the 32-bit OCT to create, edit, and save OCT customization updates for the 32-bit Office products, and the 64-bit OCT to create, edit, and save OCT updates for the 64-bit Office products.
Office 2010 includes two architecture-specific folders: one for 32-bit and one for 64-bit, with a separate Config.xml file and Updates subfolder in the 32-bit and 64-bit folders.
[pic]Note:
Office 2010 does not support side-by-side installations of 64-bit and 32-bit Office on the same computer, including across applications. For example, there is no support for side-by-side installations of the 2007 Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit. You cannot use the Office 2010 customization tools to configure side-by-side installations or customizations of 64-bit and 32-bit Office. For example, you cannot create a custom side-by-side installation with 64-bit Microsoft Office Professional 2010 and 32-bit Visio 2010 single image. For more information about 64-bit Office, see 64-bit editions of Office 2010.
Importing Office Customization Tool .msp customization files
The OCT provides support for importing Setup customization .msp files as follows:
• 32-bit Setup customization .msp files can be imported into 64-bit OCT and can then be used to customize 64-bit Office products.
• 64-bit Setup customization .msp files can be imported to 32-bit OCT and can then be used to customize 32-bit Office products.
A 32-bit Setup customization .msp file that is imported to 64-bit OCT is converted to 64-bit, and a 64-bit customization .msp file that is imported to 32-bit OCT is converted to 32-bit. To import a customization .msp file, in the Office Customization Tool, click the File menu and then click Import. In the Open dialog box, select the .msp file that you want to convert, and then click Open to start the conversion.
[pic]Note
• Importing customization .msp files is intended for equivalent cross-architecture products only. You can import a 32-bit Microsoft Office Professional Plus 2010 customization .msp file into the 64-bit version of the OCT for a 64-bit Office Professional Plus 2010 .msp file. However, you cannot import a 32-bit Microsoft Word 2010 stand-alone customization .msp file into the 64-bit OCT for a 64-bit Office Professional Plus 2010 .msp file; doing so is prevented and an error message is displayed.
• You cannot import 2007 Office system Setup customization .msp files into the Office 2010 OCT.
The Import feature can also be used when you have created an initial Setup customization .msp file for an Office 2010 product (for example, Microsoft Office Professional Plus 2010) and then later want to modify the installation to add language packs. In such cases, you first add the language packs to the network installation point that contains the Office product source files. Then you run the OCT from the root of the network installation point, create a new Setup customization file for the same product (in this example, Microsoft Office Professional Plus 2010), and then import the original customization .msp file that you created previously for Microsoft Office Professional Plus 2010. To import an .msp customization file, in the OCT, click the File menu, and then click Import. In the Open dialog box, select the previously created customization .msp file that you want to update. On the File menu, click Save As. Specify a unique name for the .msp file, and then click Save. Importing the previously created .msp file into the OCT will update the .msp file and include the added languages.
For more information about how to import .msp customization files, see Import an Office 2010 Setup customization file. For information about how to create a network installation point, see Create a network installation point for Office 2010.
Configuring Setup, Features, Additional content, and Outlook settings
The following sections provide information about the OCT areas that you can configure:
• Setup
• Features
• Additional content
• Outlook
Setup
Use the Setup section to specify the following:
• Default installation location
• Default organization name
• Additional network installation sources
• Product key
• End-user license agreement (EULA)
• Display level
• Previous versions of Office to remove
• Custom programs to run during installation
• Security settings
• Setup properties
Installation location and organization name
Specify a default organization name and installation location for all users whose installation includes this Setup customization file:
• Default installation path – This option specifies where Setup installs Office on the user's computer. You can use the predefined folder keyword [ProgramFilesFolder] to specify a path to standard folders in Windows. The default path is [ProgramFilesFolder]\Microsoft Office. This option is recognized only when you first install Office on a user's computer. You cannot change the installation path without uninstalling and reinstalling Office.
• Organization name – This name appears in the About text box (Help menu) and on the banner pages of Office applications. The name that you specify is used as the default company name for all users whose installation includes this customization file.
Additional network sources
Specify additional servers that have a copy of the network installation point.
Setup looks for servers in this list, in the order specified, if it is installing a feature on demand or if it is repairing Office and the original network installation point is unavailable.
Click Add to add a source to the list. To edit a path, select a server from the list and then click Modify. To remove a server from this list, select the server and then click Remove. To change the order of the list, select a server and then click the Move arrows to move the server up or down in the list. To remove all servers from the list, select Clear existing server list.
[pic]Note:
The OCT verifies all server paths and connects to any available servers during the initial installation process to load balance the file copy process when it creates the Local Install Source (LIS). However, be aware that an unavailable source that is specified as an additional source does not cause the installation to fail.
Add/Modify Network Server Entry dialog box
In the Add Network Server Entry dialog box or Modify Network Server Entry dialog box, enter the path of a server and then click OK.
You can use a UNC path or, if all users have access to the server that uses the same drive letter, you can use a drive letter in the path. The path can contain environment variables that are delimited by percent (%) if the variables are defined for all users.
For example:
z:\office
\\server1\share\office_root
%USERNAME%\office_root
Licensing and user interface
Use this section for the product key and to accept the Microsoft Software License Terms on behalf of each user who installs Office by using the Setup customization file. Set the Display level of the user interface. These options are recognized by Setup only when you first install Office on a user's computer.
• Use KMS client key A product key entry is not required for enterprise deployments that use Key Management Service (KMS) activation because all Volume License editions of Office 2010 have a KMS client key pre-installed. KMS is one of the methods that are provided by Office Activation Technologies for activating products licensed under Microsoft Volume Licensing programs. Only a KMS host computer needs a KMS host key to be activated and to establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. By default, the Use KMS client key option is selected in Enter a valid product key and licensing agreement for users.
For more information about the licensing options for Office 2010, see the Volume activation overview for Office 2010 and Volume activation quick start guide for Office 2010 included in the current release.
• Enter another product key You can enter a valid Multiple Activation Key (MAK) key in the OCT by using the Enter another product key option in Enter a valid product key and licensing agreement for users in the results pane. A MAK key is another method that Office Activation Technologies provide to activate products licensed under Microsoft Volume Licensing programs. By using a MAK key, clients activate Office 2010 online by using the Microsoft hosted activation servers or by telephone.
To use a MAK key, in the Enter another product key text box, enter the MAK key (25 numbers or characters) without spaces.
• I accept the terms in the License Agreement Select this check box to accept terms of your license agreement on behalf of the user.
If Display level is set to Basic or None and you supply a product key, Setup assumes that you also accept the license terms on behalf of the user. In this case, even if you do not select the I accept the terms in the License Agreement check box, the user is not prompted to accept license terms either during installation or the first time that an Office application runs.
• Display level Select the user interface that you want displayed to users during installation. The options are as follows:
• Full - default Setup runs interactively, displaying all the user interface options and messages.
• Basic Setup displays the Welcome screen, prompts for the product key and license terms (if needed), and displays a progress bar and completion notice. No other options are presented to the user.
• None Setup runs silently and displays no user interface.
[pic]Important
• In enterprise deployments, we recommend 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 being used. Setting Display level to None assumes that the Suppress modal and Completion notice options are silenced and that the license terms are accepted. Administrators must also make sure that no Office applications run during an installation of Office 2010.
• If you set Display level to Basic and select the Suppress modal option, users may be prompted if there are any Office files as they are being used. Setting Display level to None prevents prompting users in these cases. The Suppress modal option does not prevent files-in-use messages from being displayed; only Display level set to None prevents files-in-use messages from being displayed.
• Completion notice Select this check box if you want Setup to display a message to the user when installation is complete.
• Suppress modal Select this check box if you do not want Setup to display error messages and other dialog boxes that might interrupt the installation. If you set Display level to Full, error messages and other dialog boxes are displayed regardless of the state of this check box.
• No cancel Select this check box if you want to disable the cancel button (the X in upper-right corner). This setting only applies when Display level is set to Full or Basic.
[pic]Note:
The Setup customization file (.msp) sets the licensing information only during the initial installation.
The previous options are identical to the settings in the Config.xml file that are shown in the following table.
|OCT option |Config.xml setting |
|Product key |PIDKEY element |
|I accept the terms in the License Agreement |AcceptEula attribute of the Display element |
|Display level |Level attribute of the Display element |
|Completion notice |CompletionNotice attribute of the Display element |
|Suppress modal |SuppressModal attribute of the Display element |
[pic]Note:
If there are multiple products on the network installation point and you do not specify which product Setup is to install, Setup uses full display level when it prompts the user for a product, regardless of how you set Display level in the Setup customization file. You use the /config command-line option to specify which product to install. For more information, see Run Setup from a network installation point.
Remove previous installations
Specify previous versions of Microsoft Office applications to keep or remove. This option is only recognized by Setup when you first install Office on a user's computer.
By default, Setup removes previous versions of Office applications. To keep an installed Office application, click Remove previous installations in the OCT, and in the results pane select Remove the following earlier versions of Microsoft Office programs, in the list select the Office application that you do not want to remove, click Details, and in the Select Earlier Versions to Remove dialog box, under Choose which earlier versions you want Setup to remove, clear the check box for the product you want to remove, and then click OK.
[pic]Note:
Microsoft Outlook 2010 cannot coexist with previous versions of Outlook. If you choose to keep previous versions, do not install Outlook 2010.
Add installations and run programs
Run additional executable programs before or after the Office installation is complete. Setup runs command lines in the order listed in the tool and does not finish the installation until all command lines are executed.
In the OCT, click Add installations and run programs and in the results pane click Add to add a program to the list. To change a program, select the program in the list and then click Modify. To remove a program, select the program and then click Remove. To change the order of programs in the list, select a program and then click the Move arrows to move the program up or down in the list.
[pic]Note
• Do not add a program that requires the computer to be restarted, unless it is the last program in the list. If a custom program restarts the computer, the Office installation is complete, but custom programs that appear later in this list do not run.
• Command-lines entered in the Add Program Entry and Modify Program Entry dialog boxes or by using the Command element element in the Config.xml file are intended to be used only for initial product installations and uninstalls. The Command element commands are processed only during initial installations and uninstalls. If Command element commands are used for customizations after the initial installation, they are ignored.
Add/Modify Program Entry dialog box
When you add or modify a program entry, you enter the following information in the Add Program Entry dialog box or Modify Program Entry dialog box, and then click OK.
• Target Enter the path and file name of the executable program.
• Arguments Enter a string of command-line options; for example, /q /path c:\temp.
• Run this program after the Office product has been installed. The program runs after the Office installation is complete. This is the recommended option. If the program does not close correctly or if the program restarts the computer, the Office installation is not affected. However, programs further down the list do not run.
• Run this program before the Office product has been installed. The program runs before the Office installation starts. If the program does not close correctly or if it restarts the computer, Office is not installed, and programs further down the list do not run.
In the Add Program Entry dialog box or Modify Program Entry dialog box, you can include any of the following standard Windows folders in the path of the executable file.
|Folder |Description |
|[INSTALLLOCATION] |The folder in which Office is installed |
|[WindowsFolder] |Windows folder |
|[SystemFolder] |Windows System32 folder |
|[ProgramFilesFolder] |Program Files folder |
|[CommonFilesFolder] |Program Files\Common Files folder |
|[DesktopFolder] |Windows Desktop folder |
|[StartMenuFolder] |Windows Start menu |
|[ProgramMenuFolder] |Windows Start\Programs menu |
Office security settings
Customize the security settings for Office applications.
[pic]Important:
Security settings specified in a Setup customization (.msp) file provide only initial default settings on users' computers. Users can change the settings after installation. To help lock down and enforce security settings, you must use Group Policy. For more information, refer to the recommendations in the 2007 Microsoft Office Security Compliance Management Toolkit ().
The following table lists the available options.
|Setting |Description |
|Trusted Publishers |Manage the list that identifies trusted sources for digitally signed |
| |macros, add-ins, Microsoft ActiveX controls, and other executable |
| |code that is used by Office applications. Office applications share a|
| |certificate-based list of trusted sources with Internet Explorer. |
| |Click Add to add a digital certificate (CER file). |
|Trusted Locations |Manage the list that identifies locations from which any file can be |
| |opened without a check by the Trust Center security feature. Click |
| |Add to add a new location, enter the following information, and then |
| |click OK: |
| |• Application Select the Office application that uses this |
| |location. This is supported by Microsoft Access 2010, Microsoft Excel|
| |2010, Microsoft PowerPoint 2010, Microsoft Visio 2010, and Microsoft |
| |Word 2010. |
| |• Path Enter the path of the trusted location. Enter a fully |
| |qualified path with drive letter or UNC path. The path can include |
| |environment variables. |
| |• Subfolders of this location are also trusted Select this check |
| |box to include subfolders as trusted locations. |
| |• Description Enter text to describe the purpose of the location. |
| |To remove a trusted location from this list, select the location and |
| |then click Remove. |
| |[pic]Note: |
| |When you specify one or more trusted locations here, the Trusted |
| |Locations list previously defined on the user’s computer is cleared |
| |and replaced by this list. |
|Remove all Trusted Locations written by OCT during installation |Clears the Trusted Locations list on the user's computer. Use this |
| |check box to clear the Trusted Locations list on the user's computer |
| |without adding new locations. |
|Default Security Settings |Set default security levels for add-ins, templates, and Office |
| |applications. You can set security options for the following Office |
| |applications: |
| |• Microsoft Office Access |
| |• Microsoft Office Excel |
| |• Microsoft Office Outlook |
| |• Microsoft Office PowerPoint |
| |• Microsoft Office Project |
| |• Microsoft Office Publisher |
| |• Microsoft Office Visio |
| |• Microsoft Office Word |
| |The following security options are available: |
| |• Allow trusted locations options |
| |• Allow trusted locations that are NOT on user's computer |
| |• Allow Trusted Locations on the User's machine only (application |
| |default) |
| |• Disable all trusted locations. Only files signed by trusted |
| |publishers will be trusted |
| |• Application Add-ins warnings options |
| |• Disable all Application Extensions |
| |• Require that Application Extensions are signed by a trusted |
| |publisher |
| |• Require that Application Extensions are signed and silently disable|
| |unsigned Extensions |
| |• Enable all installed Application Add-ins (application default) |
| |• VBA macro warnings options |
| |• Disable all VBA macros |
| |• Disable Trust Bar warning for unsigned VBA macros (unsigned code |
| |will be disabled) |
| |• Disable all VBA macros with notification (application default) |
| |• No security checks for VBA macros (not recommended, code in all |
| |documents can run) |
| |• Add-ins and templates (Microsoft Project 2010 only) |
| |• Trust all installed add-ins and templates |
| |• Do not trust installed add-ins and templates |
| |• Security level (Project 2010 only) |
| |• Very High – Only macros installed in trusted locations will be able|
| |to run. All other signed and unsigned macros are automatically |
| |disabled |
| |• High – Only signed macros from trusted sources will be able to run;|
| |unsigned macros are disabled |
| |• Medium – The user can choose whether to run potentially unsafe |
| |macros |
| |• Low (not recommended) – Users are not protected from potentially |
| |unsafe macros |
|Unsafe ActiveX Initialization |Determine whether unsigned and, therefore, potentially unsafe, |
| |ActiveX controls can initialize using persisted data, that is, data |
| |that is saved from one instance of the control to the next. The |
| |possible values are as follows: |
| |• – Setup does not modify the setting specified on|
| |the user's computer. New applications are installed with the default |
| |setting, which is Prompt user to use persisted data. |
| |• Prompt user to use control defaults – The user is warned before an |
| |application begins ActiveX controls that might be unsafe. If the user|
| |trusts the source of the document, the control is initialized by |
| |using its default settings. |
| |• Prompt user to use persisted data – The user is warned before an |
| |application begins ActiveX controls that might be unsafe. If the user|
| |trusts the source of the document, the control is initialized by |
| |using persisted data. |
| |• Do not prompt – All unsigned ActiveX controls run without prompting|
| |the user. This setting provides the least protection and is not |
| |recommended. |
| |• Do not prompt and disable all controls – All unsigned ActiveX |
| |controls are disabled without prompting the user. |
Modify Setup properties
Modify Setup properties that are applied during the Office installation. You can customize Setup properties only when you first install Office on a user's computer. Properties set in a customization file do not take effect if you apply the file to an existing installation.
To add a property, click Add. To modify a property that you have added, select the property and then click Modify. To remove a property that you have added, select the property and then click Remove.
For more information about properties and their values, see Setup properties in Office 2010.
Add/Modify Property Value dialog box
When you add or modify a Setup property, enter the information that is shown in the following table in the Add/Modify Property Value dialog box, and then click OK.
|Setting |Description |
|Name |The property name. Property names must be all uppercase. |
|Value |The value of the property. |
Features
Use the Features section to configure user settings and to customize which Office features are installed.
Modify user settings
Set the default values of Office application settings for users who install Office with this customization file.
[pic]Note:
Using the OCT to configure user settings establishes the initial default values for the settings. Users can modify most of the settings after Office is installed. If you want to enforce user settings, use Group Policy.
You can use the OCT to provide default user settings for the following Office applications. Some applications also provide computer settings, including: Microsoft Excel 2010, Microsoft SharePoint Workspace 2010, Microsoft InfoPath 2010, Microsoft Office 2010 System, Microsoft Project 2010, Microsoft Word 2010, and Microsoft Visio 2010.
• Microsoft Access 2010
• Microsoft Excel 2010
• Microsoft SharePoint Workspace 2010
• Microsoft InfoPath 2010
• Microsoft Office 2010 System
• Microsoft OneNote 2010
• Microsoft Outlook 2010
• Microsoft PowerPoint 2010
• Microsoft Project 2010
• Microsoft Publisher 2010
• Microsoft SharePoint Designer 2010
• Microsoft Visio 2010
• Microsoft Word 2010
To configure an option, expand the tree on the left, and click the user-interface element. Configurable settings associated with that element appear on the right. Double-click a setting, and select one of the options shown in the following table.
|Setting |Description |
|Not Configured |The setting remains as it is. |
|Enabled |The setting is modified based on your choices in the dialog box. |
|Disabled |The setting is disabled. Disabling an option may differ from not |
| |configuring the option. See the description of the specific option |
| |for more information. |
Click Show all settings to display all available user settings. Click Show configured settings only to display only those settings that you have configured.
Select the Migrate user settings check box to preserve users' custom settings from an earlier version of Office. If you change user settings and also select this check box, Setup first applies the modified settings and then migrates the user's existing custom settings, overwriting any conflicting settings.
[pic]Note:
When you click Enabled to view the options for a setting and then click OK, Previous Setting, or Next Setting, the status changes to Configured, even if you do not change the setting. Inadvertently configuring the setting with an empty hyperlink, path, or file name can cause errors. If you clicked Enabled and want to ignore your changes or avoid configuring the setting, click Cancel. You can also return a setting to the Not Configured state by double-clicking the setting, selecting Not Configured, and clicking OK.
Set feature installation states
Customize how Office features are installed on the user's computer.
To change the installation state of a feature, click Set feature installation states in the OCT and in the results pane right-click the feature, and in the shortcut menu click the installation state. Some parent features consist of multiple child features. Click the plus sign (+) to the left of the parent feature to expand to view child features.
When you change the installation state of a feature, the name of the feature and the names of all its child features (if any) are displayed in bold font. This indicates that Setup will apply these changes to the installation. Features that are not displayed in bold font are installed by using the default installation state. To remove a change, select the feature and select the Reset option or select the feature and click the Reset Branch button.
The following feature installation states are typically available to users during Setup. Not all installation states are available for every feature. For example, if a feature contains a component that cannot be advertised, Installed on First Use is not included in the list of available installation states for that feature.
|State |Description |
|Run from My Computer |Setup copies files and writes registry entries and shortcuts |
| |associated with the feature to the user's hard disk. The application |
| |or feature runs locally. |
|Run All from My Computer |Same as Run from My Computer, except all child features that belong |
| |to the feature are also set to this state. |
|Installed on First Use |Setup leaves components for the feature and its child features in the|
| |local installation source until the user attempts to use the feature |
| |for the first time, at which time the components are installed. This |
| |is also known as an advertised feature. |
|Not Available |The components for the feature and the child features that belong to |
| |this feature are not installed on the computer. |
[pic]Note
• The following subcomponents of Microsoft Publisher 2010 are not visible in the Setup feature installation state tree in the Office 2010 release:
The following options are also available for each feature.
|Option |Description |
|Hidden |Setup does not display the feature in the feature tree during |
| |installation if Setup runs interactively. The symbol [H] is prepended|
| |to the feature name to indicate the feature is hidden. |
|Locked |The installation state that you choose for this feature cannot be |
| |changed by the user during installation or in maintenance mode after |
| |Office is installed. The symbol [L] is prepended to the feature name |
| |to indicate the feature is locked. |
|Reset |The feature is returned to its default installation state. This is |
| |the same as selecting the feature and clicking the Reset Branch |
| |button. |
If you explicitly set a feature to its default state, the symbol [F] is prepended to the feature name to indicate that the feature will be forced into this state. This is useful if you are creating a Setup customization file to modify an existing Office installation. If you do not change the installation state of a feature, Setup does not change the feature on the user's computer. If you specify a change, including setting the feature to its default state, Setup ensures that the feature is set to that state on the user's computer.
When you change the installation state of a feature, Setup might change the installation state of a parent or child feature to match the installation state. For example, if you set a parent feature to Installed on First Use, but set a child feature to Run from My Computer, Setup also changes the state of the parent feature to Run from My Computer.
Setup does not display hidden features in the feature tree when users run Setup interactively. The feature is installed according to its defined installation state. Child features that belong to the hidden feature are also hidden.
[pic]Tip:
The best use of the Hide setting is to simplify the feature tree for users. For example, you might hide the Office Tools branch of the feature tree so that users do not have to decide which tools that they need. Only the tools that you select are installed.
[pic]Note
• If you set the Hidden option for a feature by using the OCT or the Config.xml file during an initial installation of Office 2010, you cannot unhide that feature in the feature tree by using another Config.xml file or applying a second customization .msp file after the initial installation. This means that the feature is not displayed in the feature tree during installation. The feature remains hidden. The feature will not be displayed in Add or Remove Programs (Change or Remove Programs) in Control Panel under the Add or Remove Features option for Microsoft Office 2010 (or under the Programs and Features option in Windows Vista). However, you can unlock the feature to install and run locally later by using an .msp customization file or a Config.xml file.
• If you set the Locked option for a feature by using the OCT or the Config.xml during initial installation, that feature can be unlocked and installed locally by using an .msp customization file or a Config.xml file.
• For example, you can customize the Config.xml file to modify the OptionState element and add the following line to install the feature (Access in this example) on the user's computer and to set child features of the feature to the specified state.
•
• You can also use the OCT to create an .msp customization file to unlock the feature by setting the feature installation state to Run All from My Computer in the Set feature installation states screen.
For information about the OptionState element, see Config.xml file in Office 2010.
If you set a feature to Not Available and hide the feature in the feature tree, users can still change the setting and install the feature by installing the parent feature or by running Setup in maintenance mode. For example, if you set the Name Smart Tag Plugin feature to Not Available and Hidden, users can still install the feature by setting the parent Smart Tags Plugins feature to Run All from My Computer.
If you want to help prevent users from installing hidden features, select the Not Available, Hidden, and Locked installation states. In this case, the feature or application is not installed and is not available in maintenance mode. Users cannot install the feature by changing the state of the parent feature. The only way to reverse the Not Available, Hidden, and Locked installation state selection after Office is installed is to use the OCT to create a Setup customization file that is configured to change the installation state of the feature. Then you apply the customization file to the user's computer.
Additional content
Use this section to add or remove custom files, registry entries, and shortcuts during the installation.
Add files
Add files to users' computers when Office is installed.
To create a list of files to add to the user's computer during installation, click Add, select the file that you want to add to the list, and click Add again. To change the destination path of a file, select the file in the Add custom files list and click Modify. To remove a file from the list, select the file and click Remove. You can use the SHIFT and CTRL keys to select multiple files at the same time.
When you add files to an Office installation, note the following:
• Files are copied into the Setup customization file when you save the customization file and exit the OCT. Large files increase the size of the customization file and the time that is required to create the file.
• If you revise a file that is currently included in the customization file, you must open the customization file by using the OCT, remove the file from the Add files list, add the revised version, and save the customization file.
• If the user removes, repairs, or reinstalls Office, the custom files are removed or reinstalled together with Office. Setup does not reinstall a custom file if the file has changed since installation.
File Destination Path dialog box
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.
You can select multiple files at the same time by using the SHIFT and CTRL keys. These files will be associated with the same destination folder. You can use the special folder names that are shown in the following table in the destination path.
|Folder |Description |
|[INSTALLLOCATION] |The folder in which Office is installed |
|[ROOTDRIVE] |The local disk drive with the most free space |
|[ProgramFilesFolder] |Program Files folder |
|[CommonFilesFolder] |Program Files\Common Files folder |
|[WindowsFolder] |Windows folder |
|[SystemFolder] |Windows System32 folder |
|[PersonalFolder] |The user's My Documents folder |
|[AppDataFolder] |The user's Application Data folder |
|[NetHoodFolder] |The user's My Network Places folder |
Remove files
Remove files from users' computers when Office is installed.
To create a list of files to remove from the user's computer during installation, click Add. To modify the path or name of a file, select the file in the Remove files list and click Modify. To remove a file from the list, select the file and click Remove. You can use the SHIFT key and CTRL key to select multiple files at the same time.
[pic]Note:
Files listed in the Remove files list are removed from the user's computer before files listed in the Add files list are installed. Therefore, you can delete existing files on a user's computer and replace them with new versions. If the destination file on a user's computer is renamed or modified, an added file that has the same name does not replace it.
File Path dialog box
In the File path dialog box, enter the path and file name of the file that you want to add to the list of files to remove from the user's computer, and click OK.
The path must begin with a drive letter, a UNC path, or one of the special folders shown in the following table.
|Folder |Description |
|[INSTALLLOCATION] |The folder in which Office is installed |
|[ROOTDRIVE] |The local disk drive with the most free space |
|[ProgramFilesFolder] |Program Files folder |
|[CommonFilesFolder] |Program Files\Common Files folder |
|[WindowsFolder] |Windows folder |
|[SystemFolder] |Windows System32 folder |
|[PersonalFolder] |The user's My Documents folder |
|[AppDataFolder] |The user's Application Data folder |
|[NetHoodFolder] |The user's My Network Places folder |
Add registry entries
Add or modify registry entries on users' computers when Office is installed.
To create a list of registry entries to add to users' computers, click Add. To change an entry in the list, select the entry and click Modify. To remove an entry from the list, select the entry and click Remove. Click Import to add a set of entries from a registry file (.reg file). If an entry in the .reg file duplicates an entry in the list, the OCT prompts you to choose whether to overwrite existing registry entries with entries in the .reg file.
[pic]Important
• Registry entries customized in this section might override settings customized elsewhere in the OCT. Use this section to customize options that cannot be set directly in the Office user interface and that are not configurable by using other methods in the OCT.
• You should not use the Add registry entries section of the OCT to add registry-based policy keys (Group Policy-based registry keys). Configuring and distributing those settings in a customization update (.MSP file) to users is not supported, and the settings might not be applied correctly. Registry-based policy settings are settings that are stored in any of the four registry locations for Group Policy settings:
• For user policy settings:
• For computer policy settings:
• The supported way to manage registry-based policy keys is to use Group Policy to apply the registry policy settings. Using Group Policy lets you centrally manage client registry keys; use Group Policy to define configurations once and then rely on the operating system to enforce that state. Administrative Templates files are UNICODE text files that Group Policy uses to describe where registry-based policy settings are stored in the registry. All registry-based policy settings appear and are configured in Group Policy Object Editor under the Administrative Templates nodes.
Add/Modify Registry Entry dialog box
In the Add/Modify Registry Entry dialog box, enter the information that is shown in the following table for each registry entry, and then click OK.
|Setting |Description |
|Root |Select the branch that contains the entries that you want to add or |
| |modify. Settings are applied once per user (HKEY_CURRENT_USER) or |
| |once per computer (HKEY_LOCAL_MACHINE). You cannot add registry |
| |entries to the root of HKEY_USERS or HKEY_LOCAL_MACHINE. |
|Data type |Select a data type for the registry value. |
|Key |Enter the name of the subkey where the entry is stored. For example, |
| |Software\Microsoft\Office\14.0\Common. |
|Create empty key |Select this check box if the registry entry does not contain a value |
| |name or value data. Some settings are determined by the presence or |
| |absence of the registry entry. |
|Value name |Enter a name for the new registry entry. If you include Value data |
| |but leave this field blank, the value is assigned the name .|
| |A key can have only one value name. |
|Value data |Enter the data (value) to store in the new registry entry. The data |
| |must match the data type. |
Remove registry entries
Remove registry entries from users' computers when Office is installed.
To create a list of registry entries to remove from users' computers, click Add. To change an entry in the list, select the entry and click Modify. To remove an entry from the list, select the entry and click Remove.
To create a list of registry entries to remove from users' computers, click Add and enter the following information for each registry entry.
[pic]Note:
If the user removes, repairs, or reinstalls Office, the custom registry entries are removed or reinstalled with Office.
Delete/Modify Registry Entry dialog box
In the Delete/Modify Registry Entry dialog box, enter the information that is shown in the following table for each registry entry, and then click OK.
|Entry |Description |
|Root |Select the branch that contains the entries that you want to remove. |
|Key |Enter the full name of the subkey where the entry is stored. For |
| |example, Software\Microsoft\Office\14.0\Common. |
|Value name |Enter the name of the registry entry that you want to remove. Leave |
| |this field blank to remove the entire subkey, including all its value|
| |entries. |
Configure shortcuts
Add shortcuts to files installed with Office 2010 or files that were already on the user's computer. You can configure shortcuts only when you first install Office on a user's computer. This option is ignored if you apply the Setup customization file to an existing installation.
Click Add to add a new shortcut. To modify a shortcut in the list, select the shortcut and click Modify. To remove a shortcut from the list, select the shortcut and click Remove.
Shortcuts with Yes in the Installed column are configured during installation. Shortcuts with No in this column are configured if the corresponding product is later installed.
[pic]Note:
If you add a shortcut to a custom application or file, that shortcut is not updated or removed if the user modifies, repairs, reinstalls, or removes Office.
Add/Modify Shortcut Entry dialog box
In the Add/Modify Shortcut Entry dialog box, enter the information that is shown in the following table for the shortcut that you create or modify, and then click OK.
|Setting |Description |
|Target |Specify the application associated with the shortcut by selecting a |
| |predefined application keyword or by entering the name and path of |
| |the file to which the shortcut will point. If you select an |
| |application keyword, the OCT automatically enters information in the |
| |remaining boxes. The names in the list correspond to features that |
| |you select on the Set feature installation states page of the OCT, |
| |plus any custom files that you add to the installation on the Add |
| |files page. If you enter a name and path and the name or path |
| |contains a space, you must enclose the entire string in double |
| |quotation marks (""). You can add command-line options for the |
| |application by using the Arguments field. |
|Location |Specify the folder in which the shortcut is created by selecting a |
| |predefined folder keyword or by entering the name and path of the |
| |location of the shortcut. You can specify a subfolder by appending a |
| |backslash (\) followed by the subfolder name. For example, to install|
| |the Microsoft Word 2010 shortcut in the Microsoft Office subfolder in|
| |the Programs folder in the Start menu, select [ProgramMenuFolder] and|
| |append the subfolder name as follows: [ProgramMenuFolder]\Microsoft |
| |Office. |
| |You can use the following special folders for Location: |
| |• [StartMenuFolder]: Windows Start menu. |
| |• [ProgramMenuFolder]: Windows Start\Programs menu. |
| |• [StartupFolder]: Startup folder in the Windows Start\Programs menu.|
| |• [DesktopFolder]: Windows Desktop folder. |
| |• [INSTALLLOCATION]: The folder in which Office is installed. |
| |• [FavoritesFolder]: The user's Favorites folder. |
| |• [AppDataFolder]: The user's Application Data folder. |
| |• [NetHoodFolder]: The user's My Network Places folder. |
|Name |Enter any string to specify a name for the shortcut. |
|Start in |Enter a path to specify the default starting folder for the |
| |application. If you leave this box blank, the default folder is set |
| |to the folder where the destination file resides. If the path is not |
| |valid on a user's computer, the user sees an error message when the |
| |user tries to use the shortcut. |
|Arguments |Enter optional arguments to pass to the application on the command |
| |line. |
|Shortcut key |Enter an optional keyboard shortcut for the application or file. The |
| |syntax for the shortcut key is as follows: |
| |[modifier+]VK_key |
| |where modifier is SHIFT, CTRL, ALT, or EXT, and VK_key is a virtual |
| |key name (virtual key names, and hexadecimal key codes and |
| |descriptions are provided in the following table). The modifier is |
| |optional. You may specify more than one, in any order, separated by |
| |plus signs (+). If you use a modifier, it must precede the virtual |
| |key name. You must enter one virtual key name. Do not use spaces |
| |anywhere in the key definition. |
| |For example, |
| |CTRL+VK_F12 |
| |CTRL+SHIFT+VK_A |
| |ALT+CTRL+VK_SNAPSHOT |
| |Some key combinations, such as CTRL+ALT+VK_DELETE, might be used by |
| |the system or other processes. These combinations must not be used to|
| |open the application on the user’s computer. |
|Run |Select the kind of window in which the application or file is to |
| |start (Normal window, Minimized, or Maximized). |
|Change Icon |Select a different icon for the shortcut. |
The following table lists virtual key names and their corresponding hexadecimal key codes.
|Virtual Key Name |Key Code (Hex) |Description |
|VK_0 – VK_9 |30-39 |Keys 0-9 |
|VK_A – VK_Z |41-5A |Keys A-Z |
|VK_NUMPAD0 – VK_NUMPAD9 |60-69 |Keys 0-9 on the numeric keypad |
|VK_F1 ... VK_F24 |70-87 |Function keys F1-F24 |
|VK_LBUTTON |01 |Left mouse button |
|VK_RBUTTON |02 |Right mouse button |
|VK_CANCEL |03 |Control-break processing |
|VK_MBUTTON |04 |Middle mouse button (three-button mouse) |
|VK_BACK |08 |BACKSPACE key |
|VK_CLEAR |0C |CLEAR key |
|VK_RETURN |0D |ENTER key |
|VK_PAUSE |13 |PAUSE key |
|VK_CAPITAL |14 |CAPS LOCK key |
|VK_PRIOR |21 |PAGE UP key |
|VK_NEXT |22 |PAGE DOWN key |
|VK_END |23 |END key |
|VK_HOME |24 |HOME key |
|VK_LEFT |25 |LEFT ARROW key |
|VK_UP |26 |UP ARROW key |
|VK_RIGHT |27 |RIGHT ARROW key |
|VK_DOWN |28 |DOWN ARROW key |
|VK_SELECT |29 |SELECT key |
|VK_EXECUTE |2B |EXECUTE key |
|VK_SNAPSHOT |2C |PRINT SCREEN key |
|VK_INSERT |2D |INS key |
|VK_DELETE |2E |DEL key |
|VK_HELP |2F |HELP key |
|VK_MULTIPLY |6A |Multiply key |
|VK_ADD |6B |Add key |
|VK_SEPARATOR |6C |Separator key |
|VK_SUBTRACT |6D |Subtract key |
|VK_DECIMAL |6E |Decimal key |
|VK_DIVIDE |6F |Divide key |
|VK_NUMLOCK |90 |NUM LOCK key |
|VK_SCROLL |91 |SCROLL LOCK key |
Outlook
Use the Outlook section of the OCT to customize the default Microsoft Outlook 2010 profile and to set Outlook 2010 and Microsoft Exchange Server 2010 options.
Outlook Profile
Customize a user's default Outlook profile, which is the set of values in the Windows registry that defines user-specific information. An Outlook profile can contain multiple e-mail accounts. Users can have multiple Outlook profiles. However, you can configure only one profile in the Setup customization file. The settings in the following table enable you to customize a user’s Outlook profile.
|Setting |Description |
|Use existing profile |Use the profile already configured on the user’s computer, or if no |
| |profile exists, prompt the user to create a profile the first time |
| |Outlook starts. |
|Modify profile |Select one of two options: |
| |Define changes to make to the existing default profile. If a default |
| |profile does not exist, Outlook creates a new one using your |
| |customizations. Modify the default profile on the user’s computer.|
| |Define changes to the profile named Specify the name of the |
| |profile to which your changes apply. |
| |If no default profile exists or there is no profile by the name that |
| |you specify with the second option, Outlook creates a profile based |
| |on the options that you choose in the other Outlook sections of the |
| |OCT. Outlook uses the default profile name or uses the profile name |
| |that you specify. |
|New profile |Create a new profile on the user’s computer and make it the default |
| |profile. Existing profiles are not removed and remain available to |
| |users. You must enter a name in the Profile name text box. To find |
| |the name of an existing profile, go to Mail in the Control Panel and |
| |click Show Profiles. Outlook creates the profile based on the options|
| |that you choose in the other Outlook sections of the OCT. |
|Apply PRF |Import an Outlook profile file (.prf) to define a new default profile|
| |or to update an existing profile. Selecting this option does not |
| |update the OCT with the settings in the .prf file. Enter a name and |
| |path for the profile in the Apply the following profile (PRF file) |
| |text box. If you created a .prf file for an earlier version of |
| |Outlook, you can import it to Outlook 2010 if the profile defines |
| |only MAPI services. |
Add Accounts
Include new Outlook e-mail accounts in the user’s profile.
Select the Do not customize Outlook profile and account information option if you do not want to add accounts to a new or modified Outlook profile.
Select the Customize additional Outlook profile and account information option to specify new account information in a new or modified Outlook profile.
Click Add to add a new account to the list. To modify an account in the list, select the account and then click Modify. To remove an account from the list, select the account and then click Remove.
You can also specify the following:
• Deliver new mail to the following location When you configure an Exchange Server computer or add an Outlook data file (.pst), select this option to specify a delivery location for new e-mail messages. The default location is the Exchange Server computer, if one is configured; otherwise, the location defaults to the .pst file on the user’s computer.
• Default e-mail account Select the account that is the default e-mail account for users.
Add Account and Account Settings dialog box
If you are adding a new account, select the kind of account to add and then click Next.
In the Settings dialog box, set the options that are appropriate for the kind of account that you are adding or modifying, such as account name, user name, mail server, and e-mail address. Click More Settings for additional configuration options. If you are adding or modifying an Exchange account, see Exchange settings in the next section. Click Finish when you are finished.
To ensure that e-mail services do not overlap, Outlook might not enable you to add more than one new account for the same kind of service. For example, Outlook verifies that all POP accounts have unique names. The following table shows how Outlook determines whether a new account of the same type as an existing account can be added to the Setup customization file.
|Account type |More than one of this type allowed? |Data used to determine whether conflict exists|
|POP3 |Yes |Account name |
|IMAP |Yes |Account name |
|Outlook Data File (.pst) |Yes |File name and path of .pst file |
|Outlook Address Book |No |Existence of account |
|LDAP |Yes |Account name |
|Exchange |Yes |Account name |
Exchange settings
Configure users' Microsoft Exchange settings in a new or modified Outlook profile. The following table lists the possible settings.
|Setting |Description |
|Account name |Specify a name for the Account type. |
|User name |Identify the user by using a specific value or replaceable parameter.|
| |If you specify the default %USERNAME%, Outlook uses the user's exact |
| |logon name, instead of prompting the user with possible variations |
| |when Outlook starts. |
|Exchange Server |Enter the name of an Exchange server that is likely to be available |
| |when users start Outlook. When a user starts Outlook for the first |
| |time, Outlook replaces this value with the user’s correct Exchange |
| |server. Provide only a literal server name in this text box; for |
| |example, Exch-2-Srvr. Do not include backslashes (\\) or similar |
| |syntax. |
|Overwrite existing Exchange accounts |Select this option to replace an existing Exchange Server account in |
| |the user’s profile with this account. |
More Exchange Server Settings
Click the More Settings button in the Exchange Settings dialog box to configure Exchange Server offline use options and the Outlook Anywhere feature.
Exchange
Use the following options to configure user’s Outlook profiles for offline use and Outlook Anywhere.
|Option |Description |
|Enable offline use | |
| |Path and filename of the Outlook data file (.ost) Specify the name|
| |and where the offline Outlook data file should be stored. |
| |Directory path to store Offline Address Book files Specify the |
| |path where the offline Address Book files should be stored. |
|Configure Outlook Anywhere |Connect to Exchange Mailbox using HTTP Select this option to |
| |enable Outlook Anywhere. |
| |If you have enabled Outlook Anywhere, you can configure the following|
| |options: |
| |Use this URL to connect to the proxy server for Exchange Server |
| |name URL for the Outlook Anywhere proxy server |
| |Do not enter 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. |
| |Connect using SSL only Select this option to connect by using |
| |Secured Sockets Layer only. If you want to support both server |
| |authentication and client authentication, select: |
| |Mutually authenticate the session when connecting with SSL If this|
| |is enabled, enter the Principal name for proxy server. |
| |On fast network, connect using HTTP first, then connect using |
| |TCP/IP On a fast network, connect by using Outlook Anywhere (HTTP)|
| |first instead of the default LAN (TCP/IP). |
| |On slow network, connect using HTTP first, then connect using |
| |TCP/IP On a slow network, connect by using Outlook Anywhere (HTTP)|
| |first instead of the default LAN (TCP/IP). |
| |Use this authentication when connecting to the proxy server for |
| |Exchange The default method is Password Authentication (NTLM). |
Cached Mode
Use the following options to configure users' Outlook profiles to use a local copy of the Exchange mailbox.
|Option |Description |
|Do not configure Cached Exchange Mode |By default, Exchange mailboxes can be accessed from the Exchange |
| |Server computer, instead of being cached on users’ computers in an |
| |offline Outlook Data File (.ost). |
|Configure Cached Exchange Mode |Create an .ost file or use an existing .ost file. Users work with a |
| |local copy of their Exchange mailbox. If you select Use Cached |
| |Exchange Mode, you can configure Cached Exchange Mode for users by |
| |using the following options: |
| |• Download only headers Download copies of headers only from |
| |users’ Exchange mailboxes. |
| |• Download headers followed by the full item Download copies of |
| |headers from users’ Exchange mailboxes and download copies of |
| |messages. |
| |• Download full items Download copies of full messages (headers |
| |and message bodies) from users’ Exchange mailboxes. |
| |• On slow connections, download only headers When a slow network |
| |connection is detected, download copies of headers only from users’ |
| |Exchange mailboxes. |
| |• Download shared non-mail folders Download shared non-mail |
| |folders from other users’ mailboxes. |
| |• Download Public Folder Favorites Download the list of Public |
| |Folder Favorites. |
Export Settings
Export settings to a Outlook profile file (.prf).
Click the Export Profile Settings button to save the Outlook profile settings that you have defined in a .prf file.
[pic]Tip:
An efficient way to create an Outlook .prf file is to use the OCT to make selections and then export them to a .prf file, even if you are not using a Setup customization file when you deploy Office. You can edit the .prf file to make additional customizations that are not exposed in the OCT. For example, you can add an e-mail provider that is not listed in the OCT.
Specify Send/Receive Groups
Define Send/Receive groups for Exchange accounts and folders, and specify the tasks that are performed on each group during a Send/Receive in Outlook. A Send/Receive group contains a collection of Outlook accounts and folders. You can specify different options for Send/Receive groups when Outlook is online and offline, as shown in the following table.
|Option |Description |
|Do not configure Send/Receive settings |Do not configure settings for Send/Receive groups. Outlook is |
| |configured to use only the All Accounts group and its default |
| |settings. (If users have created additional groups, those groups |
| |migrate when users upgrade to Outlook 2010.) |
|Configure Send/Receive settings |Configure settings for Send/Receive groups (Exchange accounts and |
| |folders only). |
| |• Click New to create a new group of accounts and folders. |
| |• Click Modify to specify or redefine options for a Send/Receive |
| |group. |
| |• Click Rename to change the name of an existing Send/Receive group. |
| |• Click Remove to remove an existing Send/Receive group. |
New Exchange Group dialog box
Enter the name of the Exchange send/receive group that you are creating in the New Group Name box and then click OK.
Modify Group dialog box
When you modify a group, select from the following options in the Modify Group dialog box and then click OK.
Select the options shown in the following table under Select options for this Send/Receive group.
|Option |Description |
|Send mail items |Send mail items from the Outbox when you execute a Send/Receive for |
| |this group. |
|Receive mail items |Receive mail items when you execute a Send/Receive for this group. |
|Make folder home pages available offline |Refresh the content in folder home pages when you execute a |
| |Send/Receive for this group. |
|Synchronize forms |Synchronize forms when you execute a Send/Receive for this group. |
Under Change folder options for this Send/Receive group, select a folder and provide the information that is shown in the following table.
|Option |Description |
|Include this folder in Send/Receive |Add this folder to the set of folders that are updated during a |
| |Send/Receive for this Send/Receive group, and select from the |
| |following options: |
| |• Download headers only Download only headers for this folder when|
| |you update by executing a Send/Receive for this Send/Receive group. |
| |• Download complete item including attachments Download complete |
| |e-mail messages (or other items) for this folder when you update by |
| |executing a Send/Receive for this Send/Receive group. |
| |• Download only headers for items larger than When items are |
| |larger than the specified size, download only the header for the |
| |item. This setting applies to only this folder when you update by |
| |executing a Send/Receive for this Send/Receive group. |
Rename Exchange Group dialog box
Enter the new name of the Exchange send/receive group in the New Group Name box and then click OK.
Send/Receive settings for the selected group
Specify settings for the Send/Receive group selected in the list. The name of the selected group appears in the option label. You can specify different settings for when Outlook is online or offline.
• When Outlook is Online
• Include this group in Send/Receive Execute a Send/Receive action on this group when the user clicks Send/Receive.
• Schedule an automatic Send/Receive every n minutes Choose the interval between each Send/Receive action.
• Perform an automatic Send/Receive when exiting Automatically execute a Send/Receive action for this group when the user exits Outlook.
• When Outlook is Offline
• Include this group in Send/Receive Execute a Send/Receive action on this group when the user clicks Send/Receive.
• Schedule an automatic Send/Receive every n minutes Choose the interval between each Send/Receive action.
• Exchange Address Book
• Download offline address book Download the offline address book (OAB) when the user clicks Send/Receive.
• Click Address Book Settings to open the Modify Address Book Settings dialog box. You can select Download changes since last Send/Receive to download only updates to the address book since the last download. To download the full address book with each Send/Receive, clear the Download changes since last Send/Receive check box.
Modify Address Book Settings dialog box
Configure the default way in which Outlook updates the offline address book (OAB). Select from the following options:
• Download changes since last Send/Receive Outlook downloads only the changes that were made to the address book since the last Send/Receive. This generally takes less time to download than downloading the complete address book.
• Full Details When the address book is downloaded, Outlook copies all of the details for each entry.
• No Details When the address book is downloaded, Outlook copies only essential information, such as the name and e-mail address for each entry. This takes less time to download, but address details are not included in the offline address book. This is a legacy option supported by Outlook Address book (OAB) versions 2.0 and 3.0. If Outlook connects to a server that supports OAB 4.0 or a later version, the full details are downloaded even if this option is selected.
See Also
Setup architecture overview for Office 2010
Config.xml file in Office 2010
Setup properties in Office 2010
Import an Office 2010 Setup customization file
Customization overview for Office 2010
Customize the installation for Office 2010
Customize setup for Office 2010
Create custom configurations of Office 2010 ((Office.14).aspx)
Customize language setup and settings for Office 2010
Configure Outlook 2010
Change users' configurations after installing Office 2010
View XML content from Office Customization Tool customization files ((Office.14).aspx)
Group Policy overview for Office 2010 ((Office.14).aspx)
Enforce settings by using Group Policy in Office 2010 ((Office.14).aspx)
International reference for Office 2010
This section provides information to help administrators plan which languages to install and includes the language tags and identifiers used to configure the Microsoft Office 2010 Setup.
In this section:
|Article |Description |
|Companion proofing languages for Office 2010 |Provides a list of the companion proofing languages for each language|
| |in Office 2010. |
|Language identifiers and OptionState Id values in Office 2010 |Provides a list of the language tags and identifiers that might be |
| |needed to configure Setup for Office 2010 or for the Office 2010 |
| |Proofing Tools Kit. |
|Mixed language versions of Office 2010 |Describes the language versions that are available for the Office |
| |2010 applications, which applications will work with Language |
| |Interface Packs, and the recommended base languages to install. |
Companion proofing languages for Office 2010
Each language version of Microsoft Office 2010 includes proofing tools for a set of companion languages. For example, when you deploy the English version of an Office 2010 product, users receive proofing tools for both Spanish and French in addition to English. Depending on the number of user interface languages that you want to deploy and the included companion proofing languages, Office 2010 Language Packs might provide all of the proofing tools that you need. For more information about Office 2010 Language Packs, see Plan for multilanguage deployment of Office 2010.
Identify companion proofing languages
The following table lists companion proofing languages for each language in Office 2010.
|Primary language |Companion proofing languages |
|Arabic |Arabic, English, French |
|Brazilian |Brazilian, English, Spanish |
|Bulgarian |Bulgarian, English, German, Russian |
|Chinese (Simplified) |Chinese (Simplified), English |
|Chinese (Traditional) |Chinese (Traditional), English |
|Croatian |Croatian, English, German, Serbian, Italian |
|Czech |Czech, English, German, Slovak |
|Danish |Danish, English, German, Swedish |
|Dutch |Dutch, English, French, German |
|English |English, French, Spanish |
|Estonian |Estonian, English, German, Russian, Finnish, |
|Finnish |Finnish, English, Swedish, German, Russian |
|French |French, English, German, Dutch, Arabic, Spanish |
|German |German, English, French, Italian |
|Greek |Greek, English, French, German |
|Hebrew |Hebrew, English, French, Arabic, Russian |
|Hindi |Hindi, English, Tamil, Telegu, Marathi, Kannada, Guajarati, Punjabi, |
| |Urdu |
|Hungarian |Hungarian, English, German |
|Italian |Italian, English, French, German |
|Japanese |Japanese, English |
|Kazakh |Kazakh, English, Russian |
|Korean |Korean, English |
|Latvian |Latvian, English, German, Russian |
|Lithuanian |Lithuanian, English, German, Russian, Polish |
|Norwegian (Bk) |Norwegian (Bk), English, German, Norwegian (Ny) |
|Polish |Polish, English, German |
|Portuguese |Portuguese, English, French, Spanish |
|Romanian |Romanian, English, French |
|Russian |Russian, English, Ukrainian, German |
|Serbian (Latin) |Serbian (Latin), English, German, French, Croatian |
|Slovak |Slovak, English, Czech, Hungarian, German |
|Slovenian |Slovenian, English, German, Italian, Croatian |
|Spanish |Spanish, English, French, Basque, Catalan, Galician, Brazilian |
|Swedish |Swedish, English, Finnish, German |
|Thai |Thai, English, French |
|Turkish |Turkish, English, French, German |
|Ukrainian |Ukrainian, English, Russian, German |
See Also
Plan for multilanguage deployment of Office 2010
Customize language setup and settings for Office 2010
Language identifiers and OptionState Id values in Office 2010
This article contains a list of the language tags and identifiers that you might need when you configure Setup for Microsoft Office 2010 or for the Microsoft Office 2010 Proofing Tools Kit, or to identify installed languages.
In this article:
• Language identifiers
• Proofing Tools Config.xml OptionState Id values
Language identifiers
Office 2010 is available in many languages. In an international setting, you can deploy multiple language versions of Office 2010 in a single installation process. Setup combines a language-neutral core product with one or more language-specific packages to create a complete product.
On the source media, language-specific packages are organized into separate folders. Each folder name has a language tag appended to it, in the form ll-cc, that identifies the language and culture. For example, U.S. English language folders are identified by the folder name extension en-us. The language tags help you determine the folders that you need to copy to the network installation point.
The language folders included in a fully localized version of an Office 2010 product are the same language folders included in the Microsoft Office 2010 Language Pack for a particular language. For example, the same Outlook.ar-sa folder is used in the Arabic language version of Microsoft Office Standard 2010, the Arabic language version of Microsoft Outlook 2010, and the Office 2010 Language Pack - Arabic.
Office 2010 offers localized versions in all the languages listed in the following table. Folders for the language-specific components are identified by the language tag shown in the table. The Windows operating system uses locale identifiers (LCIDs) to identify languages in the Windows registry.
In addition to the fully localized languages listed here, Office 2010 provides Language Interface Packs (LIPs), which contain a subset of language-specific components and are designed to be installed with a logical parent language. Elements that are not localized in the LIP language appear in the parent language. For more information about LIPs, see Language Interface Packs in Mixed language versions of Office 2010.
|Language |Geographic area |Language tag (ll-cc) |LCID |
|Arabic |Saudi Arabia |ar-sa |1025 |
|Bulgarian |Bulgaria |bg-bg |1026 |
|Chinese (Simplified) |People's Republic of China |zh-cn |2052 |
|Chinese |Taiwanese |zh-tw |1028 |
|Croatian |Croatia |hr-hr |1050 |
|Czech |Czech Republic |cs-cz |1029 |
|Danish |Denmark |da-dk |1030 |
|Dutch |Netherlands |nl-nl |1043 |
|English |United States |en-us |1033 |
|Estonian |Estonia |et-ee |1061 |
|Finnish |Finland |fi-fi |1035 |
|French |France |fr-fr |1036 |
|German |Germany |de-de |1031 |
|Greek |Greece |el-gr |1032 |
|Hebrew |Israel |he-il |1037 |
|Hindi |India |hi-in |1081 |
|Hungarian |Hungary |hu-hu |1038 |
|Italian |Italy |it-it |1040 |
|Japanese |Japan |ja-jp |1041 |
|Kazakh |Kazakhstan |kk-kh |1087 |
|Korean |Korea |ko-kr |1042 |
|Latvian |Latvia |lv-lv |1062 |
|Lithuanian |Lithuania |lt-lt |1063 |
|Norwegian (Bokmål) |Norway |nb-no |1044 |
|Polish |Poland |pl-pl |1045 |
|Portuguese |Brazil |pt-br |1046 |
|Portuguese |Portugal |pt-pt |2070 |
|Romanian |Romania |ro-ro |1048 |
|Russian |Russia |ru-ru |1049 |
|Serbian (Latin) |Serbia |sr-sp-latn |2074 |
|Slovak |Slovakia |sk-sk |1051 |
|Slovenian |Slovenia |sl-si |1060 |
|Spanish |Spain |es-es |3082 |
|Swedish |Sweden |sv-se |1053 |
|Thai |Thailand |th-th |1054 |
|Turkish |Turkey |tr-tr |1055 |
|Ukrainian |Ukrainian |uk-ua |1058 |
Proofing Tools Config.xml OptionState Id values
The following table provides the OptionState Id values for the Office 2010 Proofing Tools Kit. Use these values to modify the Config.xml file in the ProofKit.WW folder when customizing the Setup of the Office 2010 Proofing Tools Kit. For more information about proofing tools, see Plan for proofing tools in Plan for multilanguage deployment of Office 2010.
|OptionState Id |Proofing tools language |
|IMEMain_1028 |Chinese Traditional Input Method Editor (IME) |
|IMEMain_1041 |Japanese IME |
|IMEMain_1042 |Korean IME |
|IMEMain_2052 |Pinyin IME |
|ProofingTools_1025 |Arabic |
|ProofingTools_1026 |Bulgarian |
|ProofingTools_2052 |Chinese (People's Republic of China) |
|ProofingTools_3076 |Chinese (Hong Kong) |
|ProofingTools_1028 |Chinese (Taiwan) |
|ProofingTools_1050 |Croatian |
|ProofingTools_1029 |Czech |
|ProofingTools_1030 |Danish |
|ProofingTools_1043 |Dutch |
|ProofingTools_1033 |English |
|ProofingTools_1061 |Estonian |
|ProofingTools_1035 |Finnish |
|ProofingTools_1036 |French |
|ProofingTools_1031 |German |
|ProofingTools_1032 |Greek |
|ProofingTools_1037 |Hebrew |
|ProofingTools_1081 |Hindi |
|ProofingTools_1038 |Hungarian |
|ProofingTools_1040 |Italian |
|ProofingTools_1041 |Japanese |
|ProofingTools_1087 |Kazakh |
|ProofingTools_1042 |Korean |
|ProofingTools_1062 |Latvian |
|ProofingTools_1063 |Lithuanian |
|ProofingTools_1044 |Norwegian (Bokmål) |
|ProofingTools_1045 |Polish |
|ProofingTools_1046 |Portuguese (Brazil) |
|ProofingTools_2070 |Portuguese (Portugal) |
|ProofingTools_1048 |Romanian |
|ProofingTools_1049 |Russian |
|ProofingTools_2074 |Serbian (Latin) |
|ProofingTools_1051 |Slovak |
|ProofingTools_1060 |Slovenian |
|ProofingTools_3082 |Spanish |
|ProofingTools_1053 |Swedish |
|ProofingTools_1054 |Thai |
|ProofingTools_1055 |Turkish |
|ProofingTools_1058 |Ukrainian |
|ProofingTools_1027 |Catalan |
|ProofingTools_1056 |Urdu |
|ProofingTools_1069 |Basque |
|ProofingTools_1094 |Punjabi |
|ProofingTools_1095 |Gujarati |
|ProofingTools_1097 |Tamil |
|ProofingTools_1099 |Kannada |
|ProofingTools_1102 |Marathi |
|ProofingTools_1110 |Galician |
|ProofingTools_2068 |Norwegian (Nynorsk) |
|ProofingTools_1098 |Telugu |
See Also
Plan for multilanguage deployment of Office 2010
Customize language setup and settings for Office 2010
Mixed language versions of Office 2010
Setup architecture overview for Office 2010
Mixed language versions of Office 2010
Not every product in the Microsoft Office 2010 suites is available in every language. In some scenarios, this results in an installation of Office 2010 that includes applications or user interface elements in more than one language.
This article describes which language versions are available for a subset of the Office 2010 applications, which Office 2010 applications will work with Language Interface Packs, and what are the recommended base languages to install for Office 2010 Language Interface Packs.
In this article:
• Applications and language availability
• Language Interface Packs
Applications and language availability
Individual applications will install with the Office 2010 language version installed with a few exceptions. One exception is that the Hindi language version installs Microsoft Access 2010 in English.
In other language versions, certain applications are not available at all.
Microsoft Project 2010, Microsoft Visio 2010, and Microsoft SharePoint Designer 2010 are available in a subset of languages, as shown in the following table.
|Language |Project 2010 |Visio 2010 |SharePoint Designer 2010 |
|Arabic |yes |yes |yes |
|Brazilian |yes |yes |yes |
|Chinese - Simple |yes |yes |yes |
|Chinese - Traditional |yes |yes |yes |
|Czech |yes |yes |yes |
|Danish |yes |yes |yes |
|Dutch |yes |yes |yes |
|English |yes |yes |yes |
|Finnish |yes |yes |yes |
|French |yes |yes |yes |
|German |yes |yes |yes |
|Greek |yes |yes |yes |
|Hebrew |yes |yes |yes |
|Hindi |no |no |yes |
|Hungarian |yes |yes |yes |
|Italian |yes |yes |yes |
|Japanese |yes |yes |yes |
|Korean |yes |yes |yes |
|Norwegian |yes |yes |yes |
|Polish |yes |yes |yes |
|Portuguese (European) |yes |yes |yes |
|Russian |yes |yes |yes |
|Slovak |yes |yes |no |
|Slovenian |yes |yes |no |
|Spanish |yes |yes |yes |
|Swedish |yes |yes |yes |
|Thai |no |no |yes |
|Turkish |yes |yes |yes |
|Ukrainian |yes |yes |no |
Language Interface Packs
For some languages, Microsoft localizes only some Office 2010 applications and releases them as Language Interface Packs (LIPs). Users must first install a full language version of Office 2010, and then they can install the LIP. They work in their preferred language in the following applications and features:
• Microsoft Word 2010
• Microsoft Outlook 2010
• Microsoft Excel 2010
• Microsoft PowerPoint 2010
• Shared Office features
The rest of the applications appear in the primary Office 2010 installation language. The following table lists the recommended base language for each LIP language.
|LIP language |Recommended base language |
|Afrikaans |English |
|Albanian |English |
|Amharic |English |
|Armenian |English |
|Assamese |English or Hindi |
|Azeri |English or Russian |
|Basque |Spanish or French |
|Bengali - Bangladesh |English |
|Bengali - India |English or Hindi |
|Bosnian - Cyrillic |Serbian Latin, English, or Croatian |
|Bosnian - Latin |Serbian Latin, English, or Croatian |
|Byelorussian |Russian |
|Filipino |English |
|Galician |Spanish |
|Georgian |English |
|Gujarati |English or Hindi |
|Hausa |English |
|Igbo |English |
|Icelandic |English |
|Indonesian Bahasa |English |
|Inuktitut |English |
|Irish - Gaelic |English |
|isiXhosa |English |
|isiZulu |English |
|Kannada |English or Hindi |
|Kazakh |Russian or English |
|Khmer |English |
|Ki'che |Spanish |
|Kyrgyz |Russian |
|Kiswahili |English |
|Konkani |English or Hindi |
|Luxembourgish |German, English, or French |
|Macedonian (FYROM) |English |
|Malay |English |
|Malay - Brunei |English |
|Malayalam |English or Hindi |
|Maltese |English |
|Maori |English |
|Marathi |English or Hindi |
|Mongolian (Cyrillic) |English or Russian |
|Nepali |English or Hindi |
|Norwegian - Nynorsk |Norwegian |
|Oriya |English or Hindi |
|Persian |English |
|Punjabi |English or Hindi |
|Quechua |Spanish |
|Setswana |English |
|Sesotho sa Leboa |English |
|Sinhalese |English |
|Tamil |English or Hindi |
|Tatar |Russian |
|Telugu |English or Hindi |
|Turkmen |English or Russian |
|Urdu |English |
|Uzbek - Latin |English or Russian |
|Vietnamese |English |
|Welsh |English |
|Yoruba |English |
See Also
Plan for multilanguage deployment of Office 2010
Customize language setup and settings for Office 2010
Product and feature changes in Office 2010
This section contains a list of articles that describe new features, changed features, and deprecated features for the products in the Microsoft Office 2010 suites, as well as Microsoft Project 2010 and Microsoft Visio 2010. Each article also describes migration considerations for the particular product.
In this section:
|Article |Description |
|Changes in Office 2010 |Lists changes in Microsoft Office 2010 since the 2007 Microsoft |
| |Office system. |
|Changes in Access 2010 |Lists changes in Microsoft Access 2010 since Microsoft Office Access |
| |2007 and migration considerations. |
|Changes in Excel 2010 |Lists changes in Microsoft Excel 2010 since Microsoft Office Excel |
| |2007 and migration considerations. |
|Changes in InfoPath 2010 |Lists changes in Microsoft InfoPath 2010 since Microsoft Office |
| |InfoPath 2007. |
|Changes in OneNote 2010 |Lists changes in Microsoft OneNote 2010 since Microsoft Office |
| |OneNote 2007 and migration considerations. |
|Changes in Outlook 2010 |Lists changes in Microsoft Outlook 2010 since Microsoft Office |
| |Outlook 2007 and migration considerations. |
|Changes in PowerPoint 2010 |Lists changes in Microsoft PowerPoint 2010 since Microsoft Office |
| |PowerPoint 2007 and migration considerations. |
|Changes in Project 2010 |Lists changes in Microsoft Project 2010 since Microsoft Office |
| |Project 2007 and migration considerations. |
|Changes in Publisher 2010 |Lists changes in Microsoft Publisher 2010 since Microsoft Office |
| |Publisher 2007 and migration considerations. |
|Changes in SharePoint Designer 2010 |Lists changes in Microsoft SharePoint Designer 2010 since Microsoft |
| |Office SharePoint Designer 2007. |
|Changes in SharePoint Workspace 2010 |Lists changes in Microsoft SharePoint Workspace 2010 since Microsoft |
| |Office Groove 2007 and migration considerations. |
|Changes in Visio 2010 |Lists changes in Microsoft Visio 2010 since Microsoft Office Visio |
| |2007 and migration considerations. |
|Changes in Word 2010 |Lists changes in Microsoft Word 2010 since Microsoft Office Word 2007|
| |and migration considerations. |
Changes in Office 2010
This article lists changes in Microsoft Office 2010 since the 2007 Microsoft Office system.
In this article:
What’s new
What’s changed
What’s removed
What’s new
For information about the new features in Microsoft Office 2010 that are relevant to IT administrators, see What’s new for IT professionals in Office 2010 in Getting started with the deployment of Office 2010.
What’s changed
This section summarizes the feature changes in Office 2010.
Insert Clip Art task pane and Clip Organizer
The Insert Clip Art task pane and Clip Organizer functionality remains generally unchanged in Office 2010. However, the feature that enabled downloading and managing a locally stored clip art collection has instead been replaced by the ability to search for and insert online clip art. This change is due to an increased desire by Office users (who are becoming more Internet savvy) to be able to grab and use images from the Web immediately without having to store them for later use.
HTML editor
The HTML editor is updated for Windows SharePoint Services, Microsoft Office SharePoint Server, and Microsoft InfoPath. New features include cross-browser support, XHTML support, and a shared editor.
Legacy brightness and contrast
Da Vinci brightness and contrast algorithms replace legacy algorithms, and are now available through the user interface and Office Manager. Legacy brightness and contrast algorithms are still available for backward compatibility. This is a core architecture change.
Besides brightness and contrast, other photo editing algorithms and tools are provided through the user interface and Office Manager. With this change, users can receive improved photo editing results. If a photo does not contain 2007 Office system brightness or contrast edits, the visual fidelity of the 2007 Office system brightness and contrast is retained in Office 2010. If a photo does contain 2007 Office system brightness or contrast edits, Office 2010 produces better results because the old effects are converted into new effects.
Language Preferences
Language Preferences replaces Language Settings and assists users in showcasing language packs and in determining whether the necessary proofing tools or keyboards are enabled. Included are direct links to online locations where users can obtain additional tools. There is also new functionality, such as ScreenTip Language.
What’s removed
This section provides information about removed features in Office 2010.
Insert Clip Art task pane and Clip Organizer
Deprecated functionality in both the Insert Clip Art task pane (within client applications) and the standalone Clip Organizer application:
• Simplified drop-down menu options for "Search In" (replaced by a check box to include or exclude online content) and "Media Types" (Photo, Illustration, Audio and Video. The level of granularity for file extensions is removed).
• Removing thumbnail icons indicating online content and clip art loading from a media CD.
Deprecated functionality in the Insert Clip Art task pane only:
• Removing the "Organize Clips" link.
Deprecated functionality in the standalone Clip Organizer application only:
• Auto-import local content into Clip Organizer
• Associate a folder with a particular collection (for use by auto-import)
• Find Similar Style within a user's local clipart content library
• Send clip art to Mail recipient(s) feature
• List and Details views of the Clip art (we keep only thumbnail view now)
• Delete a clip from a particular collection.
Symbol input add-in: East Asia versions of Office 2010
The special symbol input add-in is removed from Microsoft Word 2010, Microsoft Excel 2010, Microsoft PowerPoint 2010, and Microsoft Access 2010 in the East Asia versions of Office 2010.
This change includes the language releases shown in the following table.
|Language |Geographic area |Language tag (ll-cc) |LCID |
|Chinese (Simplified) |People's Republic of China |zh-cn |2052 |
|Chinese (Traditional) |Hong Kong SAR |zh-hk |3076 |
|Chinese (Traditional) |Taiwan |zh-tw |1028 |
This feature is removed because users can easily access this functionality through the similar feature that is available through the Insert Symbol button in the Symbol group under the Insert tab, or through the Input Method Editor (IME).
InterConnect
InterConnect is removed from Office 2010. InterConnect provided Japanese users with a unique, electronic business card that could be secured and delivered. It was available as a part of Microsoft Office Ultimate, InterConnect retail SKU, and Microsoft Outlook+InterConnect retail SKU.
Office Startup Assistant
Although turned off by default in 2007 Microsoft Office system, the ability to create a new Office document from the Start menu, or Office Startup Assistant (OSA), is completely removed in Microsoft Office 2010. Users can no longer manually turn on the feature in the Start menu through Office 2010 setup or open a dialog box to create a new document in an Office 2010 application.
This feature is replaced by the ability to create a new Office document for each Office 2010 application from the Microsoft Office Backstage by clicking New and then creating the document. In addition, the improved functionality is compatible with the 64-bit version of Office 2010.
Office Diagnostics
Office Diagnostics, also known as Customer Watson, is removed for all Office 2010 applications. Because of shifting resources, the focus must be on analysis and reporting features that have been proven beneficial for other teams. Users must now run the repair utility from the Control Panel.
Document workspaces
The following is removed from Microsoft Word 2010, Microsoft Excel 2010, Microsoft PowerPoint 2010, Microsoft OneNote 2010, Microsoft Visio 2010, and Microsoft Outlook 2010.
• The ability to create document workspaces.
• The ability to create shared attachments in Outlook.
• The ability to invoke actions on Microsoft SharePoint Foundation by using the Document Management pane.
• The functionality that enables the local copy of the document to synchronize with the server copy.
Users can no longer access the following in Service Options in the Option dialog box: Create Document Workspace, Document Information Management, and Document Management. The synchronization functionality is replaced by the implicit cache, which enables users to continue editing within the document workspace even when the document is offline and then automatically sync the changes to Windows SharePoint Services the next time that the document is online. The implicit cache prevents user confusion over which option to use.
MSXML5 support
Office 2010 does not support MSXML5. Existing solutions will not instantiate MSXML5 objects when they are loaded by Office 2010. Migrate code to MSXML6 or to managed code that uses the .NET Framework.
[pic]Note:
MSXML6 does not support Digital Signature code.
See Also
Changes in Access 2010
Changes in Excel 2010
Changes in InfoPath 2010
Changes in OneNote 2010
Changes in Outlook 2010
Changes in PowerPoint 2010
Changes in Project 2010
Changes in Publisher 2010
Changes in SharePoint Designer 2010
Changes in SharePoint Workspace 2010
Changes in Visio 2010
Changes in Word 2010
Changes in Access 2010
This article lists changes in Microsoft Access 2010 since Microsoft Office Access 2007 and migration considerations. If you are upgrading from Microsoft Office Access 2003, see also Changes in Access 2007 () and Migration considerations for Access 2007 ().
In this article:
What’s new
What’s changed
What’s removed
Migration considerations
What’s new
This section highlights new feature in Access 2010 that might be of more interest to IT administrators. For more information about new features, see Microsoft Access 2010 ().
Share a database on the Web
In Office Access 2007, there was limited support in sharing a database to the Web, where you could only publish your lists and move the database to document libraries. Now, in Access 2010, if you have access to Access Services in Microsoft SharePoint Server 2010, you can create a Web database by using Access 2010. Users can use your database in a Web browser window, but you must use Access 2010 to make design changes. Although some desktop database features do not translate to the Web, you can do many of the same things by using new features, such as calculated fields and data macros.
Export to .pdf and .xps
In Access 2010, you can export data to a .pdf file format (Portable Document Format) or an .xps file format (XML Paper Specification) to print, post, and distribute e-mail. In Office Access 2007 this capability was also available through a downloadable add-in. Beginning with Office Access 2007 SP2 and continued with Access 2010, this feature was built into the product so you do not need to install any additional software. Exporting a form, report, or datasheet to a .pdf file or an .xps file lets you capture information in an easy-to-distribute form that retains all the formatting characteristics, but does not require other users to install Access on their computers to print or review your output.
Connect to a Web service as an external data source
You can now connect to a Web service as an external data source. You will need a Web service definition file provided by the Web service administrator. After you install the definition file, you can link to Web service data as a linked table.
Backstage view
The Microsoft Office Backstage is part of the Microsoft Office Fluent user interface (UI) and a companion feature to the ribbon. The Backstage view, which can be accessed from the File tab, contains commands that you apply to an entire database, such as compact and repair, or open a new database. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier releases of Microsoft Office.) Commands are arranged on tabs on the left side of the screen, and each tab contains a group of related commands or links. For example, if you click New, you see a set of buttons that let you create a new database from scratch, or you can select from a library of professionally designed database templates.
What’s changed
This section summarizes some of the feature changes in Access 2010 that might be of more interest to IT administrators.
Backward compatibility between Access 2010 and Access 2007
Access 2010 introduces features that are not supported in Office Access 2007. Although Office Access 2007 SP1 will not open databases that contain these features, Office Access 2007 SP2 offers limited viewing and designing capabilities.
Enhanced security
Enhanced security features and strong integration with Microsoft SharePoint Foundation 2010 help you more effectively manage data and allow you to make your information tracking applications more secure than before. By storing your tracking application data in lists on SharePoint Foundation 2010, you can audit revision history, recover deleted information, and set data access permissions.
Office Access 2007 introduced a new security model that is carried forward and improved in Access 2010. Unified trust decisions are integrated with the Microsoft Office Trust Center. Trusted locations make it easy to trust all databases in secure folders. You can load an Office Access 2007 application with code or macros that are disabled to provide a more secure, sandbox experience (that is, unsafe commands cannot be run). Trusted macros are run in Sandbox mode.
Support for SQL Server 2008 data types
Access 2010 provides limited support in Access projects (.adp) for the following seven new data types introduced in Microsoft SQL Server 2008:
• date
• datetime2
• datetimeoffset
• time
• geography
• geometry
• hierarchyID
The following three data types are unsupported when you use table or view design mode in Access 2010:
• geography
• geometry
• hierarchyID
The alternative is to use SQL Server 2008 design tools for creating tables, views, stored procedures, and functions when you use any of these three data types. You can still use Access 2010 to design reports, forms, modules and macros that reference these data types.
What’s removed
This section provides information about removed features in Access 2010 that might be of more interest to IT administrators.
Calendar control (mscal.ocx)
The Microsoft Calendar control (mscal.ocx) is not available in Access 2010. An alternative is to use the date picker control in Access 2010. Opening an application from an earlier version of Access where the control was used will generate an error message in Access 2010 and the control will not appear.
Microsoft Replication Conflict Viewer
The Microsoft Replication Conflict Viewer is not available in Access 2010. To achieve the same functionality, you can use the ReplicationConflictFunction property in a database replica set so that you can create a custom procedure to resolve synchronization conflicts. For more information, see How to Use the ReplicationConflictFunction Property ().
Snapshot file format
The ability to export a report as a snapshot file is not available in Access 2010. Alternatives to the snapshot file format, in which file formats preserve the layout and formatting of the original report, are .pdf and .xps file formats.
Data access pages
Beginning with Office Access 2007, the ability to create, modify, or import data access pages was no longer supported. However, data access pages in an Office Access 2007 database would still function. By using Access 2010, you can open a database that includes data access pages. However, the data access pages will not function. When you attempt to open a data access page, you will receive an error message that states that Microsoft Office Access does not support this operation for Data Access Pages.
An alternative to using data access pages is to create a Web database and publish to a SharePoint site by using Access Services. For more information, see What's new for Access Services in SharePoint Server 2010 ().
Lotus 1-2-3, Paradox, Jet2.x, and Red2 IISAM
The IISAM (installable index sequential access method) for Lotus 1-2-3, Paradox, Jet2.x, and Red 2 is not available in Access 2010. If you need to link to, import from, or export to one of these IISAMs, you can use Office Access 2007 or earlier. When you attempt to create a link to, import from, or export to a Jet 2.x or Red 2 database, and when you select or paste a linked table to Lotus 1-2-3 or Paradox, you might receive one of the following error messages:
Migration considerations
When you plan a migration to Access 2010, review what is new, changed, and removed for Access 2010. Because Access 2010 has many similarities with Office Access 2007, such as the same native file format, you can also review and use the existing migration documentation for Office Access 2007 when you migrate to Access 2010.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ().
See Also
Changes in Office 2010
Changes in Office Access 2007 ()
Migration considerations for Access 2007 ()
Introduction to Office Migration Planning Manager (OMPM) ()
When to Migrate from Microsoft Access to Microsoft SQL Server ()
Changes in Excel 2010
This article lists changes in Microsoft Excel 2010 since the release of Microsoft Office Excel 2007 and in view of migration considerations. If you are upgrading from Microsoft Office Excel 2003, see also Changes in Excel 2007 () and Migration considerations for Excel 2007 ().
In this article:
What’s new
What’s changed
What’s removed
Migration considerations
What’s new
This section highlights new features in Excel 2010 that might be of interest to IT administrators. For more information about new features, see Microsoft Excel 2010 ().
In Addressing Customer Needs
This section highlights changes in Excel 2010 to address customer needs, especially improvements in programmability.
High performance computing clusters
In Microsoft OfficeExcel 2010, High Performance Computing (HPC) solves computationally intensive problems using multiple computers. Excel 2010, running on a desktop PC, can offload the evaluation of certain types of user defined functions (UDF) to a compatible cluster, such as HPC Windows Server 2008. This offload enables Excel_2nd_CurrentVerl to continue calculating other parts of the workbook in parallel to the cluster calculating the UDFs. Secondly, entire workbooks can also be calculated on the cluster. For example, a workbook model can be recalculated many thousands of times by performing batches of calculations in parallel on the cluster. When a supported computer cluster is available, users can instruct Excel 2010 to use that cluster by selecting a cluster connector and configuring a specific cluster name to use in the Advanced options of the Excel Options dialog box.
Use this capability in Excel 2010 to solve mathematical analysis or data processing problems, or Monte Carlo simulations. Cluster safe UDFs must be implemented in an XLL. You cannot create a cluster safe UDF in VBA or in a COM automation add-in. Also, cluster safe UDFs cannot interact with Excel in any way except to return their value. Workbooks need to be designed for the cluster. This means that existing workbooks won’t necessarily work on the cluster without modification. This option is not supported for 32-bit and ia64-based, language-specific, Itanium platforms. This option is not supported for 32-bit and ia64-based, language-specific, Itanium platforms.
Macro recording support for chart elements
In Microsoft Office Excel 2007, recording a macro while formatting a chart, or other object, did not produce any macro code. However, in Excel 2010, you can use the macro recorder to record formatting changes to charts and other objects and then reuse those changes again and again. Standardize formatting by distributing these macros to end users.
XLM/VBA gaps closing
Excel has a macro facility, known as Excel 4 macros (XLM for short), that was the primary macro language prior to the introduction of VBA in Excel 5.0. Most people have long since migrating their Excel 4 macros to VBA; however, some Excel 4 macro capabilities were missing from VBA, which made this migration difficult.
In Excel 2010, one of our goals was to remove any remaining barriers that people had to complete the migration of Excel 4 macros to VBA. Excel 2010 does still enable the creation, editing and execution of Excel 4 macros. Please use Excel 2010 to migrate your macros and let us know if we missed any functionality.
UDFs run asynchronously
In Excel 2010 you can author these non-processor-intensive UDFs as asynchronous. This ability is supported in XLL add-ins, and the new Excel 2010 SDK has all you need for writing asynchronous UDFs.
How it works
Break your UDF in two parts:
1. A synchronous function call, which sets up the asynchronous calculation, data request, external web service call, etc., and returns immediately.
2. An asynchronous part, which returns the result to Excel when it is ready.
Excel tracks uncompleted UDF calls and continues independent parts of the calculation. When the UDF call result becomes available to your XLL add-in, the add-in then calls back into Excel with the UDF result. For details on configuring your XLL add-in see the Excel BLOG. ()
In Business Intelligence
Business Intelligence (BI) is a category of technologies used to support decision making.
Sparklines
Sparklines are a new type of visualization in Excel 2010. They are small cell-sized graphics used to show trends in series of values using line, column, or win/loss charts. Sparklines allow the viewer to see in a single cell information-dense graphics that greatly increase reader comprehension of the data. They demonstrate the “what” not the “why” of the data. For more information see Sparklines. ()
Slicers
Slicers make filtering and interpretation of data easier. They enhance PivotTables and CUBE functions within a workbook. Slices filtered data interactively. They float above the grid and act like report filters so you can hook them to PivotTables, PivotCharts, or CUBE functions to create interactive reports or dashboards. For more information, see Easy (and Even Fun!) Data Exploration: Introducing Excel 2010 Slicers (), and Interacting with Slicers (), and Dressing up your Slicers. ()
Microsoft SQL Server PowerPivot for Excel add-in
If you need to model and analyze very large amounts of data, you can download the PowerPivot for Excel add-in and work with that data inside your Excel workbooks. By using this add-in, you can quickly combine data from multiple sources, including corporate databases, worksheets, reports, and data feeds. You can then interactively explore, calculate, and summarize that data by using PivotTables, slicers, and other Excel features. As you interact with the data, you will notice that the response time is fast, whether you are working with hundreds of rows, or hundreds of millions of rows.If you have access to Excel Services in Microsoft SharePoint Server 2010, you can make your reports and analyses available on a SharePoint site so that other people in your organization can benefit from your work.
Calculation feature improvements
This section provides updates to the Excel calculation engine.
New version of Solver
Excel 2010 includes a new version of the Solver add-in, which you can use to find optimal solutions in what-if analysis. Solver has an improved user interface, a new Evolutionary Solver, based on genetic algorithms, that handles models with any Excel functions, new global optimization options, better linear programming and nonlinear optimization methods, and new linearity and feasibility reports. In addition, the Solver add-in is now available in a 64-bit version. For more detailed help about Solver from Frontline Systems, see Solver Help at ().
New Statistical functions
Excel's function library improved in 2010. Accuracy of functions improved, consistency improved with Excel's function names and definitions with 50 new functions, and a new functions user interface was added. New algorithms were implemented to improve the accuracy of our statistical, financial and math functions. See Excel BLOG () for list and details of improvements.
In Excel Web App
This section highlights changes in the Excel 2010 web app. For more information, see Excel Web App 2010 Overview (), and in the Microsoft Office Web Apps () blog.
Multiple user editing
Collaborative editing functionality is a feature of Microsoft Excel Web App. Multiple authors can edit the same spreadsheet at the same time because the Excel Web App manages all the changes. A file can still be checked out and locked for exclusive access by the person who initiated the checkout. For more information, see Collaborative Editing Using Excel Web App. ()
Excel Services enhancements
Many organizations use Excel Services to share workbooks and data with other people, such as executives and other stakeholders in your organization. If you use Excel Services to save or publish workbooks to a SharePoint site, you can take advantage of the following improvements:
• Share workbooks from Backstage
Before Excel 2010, it was previously possible to save and publish worksheet data to a SharePoint site, in Excel 2010, the options for doing this are now conveniently located together on the Share tab in the Microsoft Office Backstage.
• More support for Excel features
Before Excel 2010, if a workbook contained unsupported features, it could not be opened in the browser. In this release, most workbooks with unsupported features will open. In addition, more Excel features are supported in Excel Services, including new Excel 2010 features such as Sparklines and Slicers.
• Edit and collaborate on workbooks
If you publish a workbook to a SharePoint site where Microsoft Excel Web App are installed, you can edit your workbook in a supported Web browser, in addition to viewing it. In addition, you and your colleagues can work on the same workbook at the same time. This means that you no longer have to e-mail a workbook around, or wait for someone to check it back in on the server before you can edit it. For example, imagine that you and your manager are currently viewing the same worksheet in different offices. If you make a change to the data, your manager will see that change on her screen.For more information about Excel Services, see What's New for Excel Services ()
In Office Suite Changes
The new 64-bit version of Office allows the processing of larger data sets, which is especially important for Excel 2010. Use in conjunction with the new VBA 7.0. You may need to update VBA when using 64-bit Excel 2010. See the Excel BLOG () for more details.
Backstage view
The new Backstage view replaces the traditional File menu. All file management tasks are available in Backstage. Click the File tab to access the Backstage view. Although it was previously possible to save and publish worksheet data to a SharePoint site, in Excel 2010, the options for doing this are now conveniently located together on the Share tab in Microsoft Office Backstage. For more information, see Backstage ()
Excel 2010 64-bit Advantages
Applications built with the 64-bit version simply can use more physical memory than ever before, especially important for those who need to work with really large data sets. In Excel 2010 investments were made in our 64-bit architecture to optimize our memory consumption while keeping the cell table (and related operations) as fast as possible.
For example, create bigger workbooks using 64-bit Excel that can be too big for 32-bit Excel to open. But generally workbooks are interchangeable between 32-bit and 64-bit. Review 64-bit Support and Code Compatibility in the Excel BLOG. ()
What’s changed
This section summarizes the feature changes in Excel 2010 that might be of interest to IT administrators. For more information about changed features, see Microsoft Excel 2010 ().
In Addressing Customer Needs
This section highlights changes in Excel 2010 to address customer needs, especially improvements in programmability.
Compatibility mode tool
New features in Excel 2010 are disabled when opening previous versions of Excel in 2010. For example, new 2010 Sparklines and Slicers features are disabled with opening previous version of Excel. Workbooks created in the Excel 97-2003 file format (.xls) automatically open in Compatibility Mode. Workbook created in Excel 2010, but destined for others using earlier versions of Excel, should turn on Compatibility Mode to prevent accidental use of functions and features that are incompatible with the earlier versions of Excel. This is critical for users that plan to share workbooks with others who have not yet migrated to Office Excel 2007 or later.
File loading performance
File loading (opening and saving) lends itself well to parallel processing and the multi-core functionality of Excel 2010. However, the structure and content of workbooks significantly affects the performance gains. For example, if there is only one huge sheet in a workbook, a proportionally large amount of file loading time will be spent simply loading the one sheet. But if you have two huge sheets, Excelcan fetch the second sheet off disk while the first sheet is still being loaded into memory.
In Business Intelligence
Business Intelligence (BI) is a category of technologies used to support decision making.
PivotTable enhancements
PivotTables are easier and faster to use in Excel 2010. Some of the key improvements include the following:
• Improved performance In Excel 2010, multithreading helps speed up data retrieval, sorting, and filtering in PivotTables.
• OLAP Write-back supportIn Excel 2010, you can change values in the OLAP PivotTable Values area and have them written back to the Analysis Services cube on the OLAP server.
Online Analytical Processing (OLAP) using Excel 2010 is available with the CubeCellValue add-in. Excel workbook data can be stored directly in an Online Analytical Processing (OLAP) cube. The OLAP data is written back to the worksheet to create PivotTable reports that are based on the OLAP source data. Before Excel displays any summarized data in a PivotTable report, an OLAP server performs calculations to summarize the data. The CubeCellValue add-in must be downloaded and installed on computers where this feature is required.
• Named sets
Named sets are a tool that allows a re-usable group of items to be created for use in PivotTables. Combine items from different hierarchies (asymmetric reporting) in ways that otherwise wouldn’t be possible. Create PivotTables based on your own custom Multidimensional Expressions (MDX). Create PivotTables that dynamically change based on filters by using dynamic sets. For more information, see PivotTable Named Sets in Excel 2010. ()
• Dynamic sets support
When you work with the same set of items from data over and over again, Excel 2010 provides the ability to easily create and reuse this logical grouping of items as a single object. For OLAP PivotTable users, dynamic rendering using the filter in the matrix is supported.
Filtering
For large worksheets filtering enables the quick location and display of specific data in tables and PivotTable views. Use new Search Filter capability to spend less time sifting through large data sets. For additional information, see Excel 2010: New Search Filter ().
Conditional formatting
Conditional formatting allows references to be made to different sheets on the workbook (cross-sheet conditional formatting). Use conditional formatting to discover and illustrate important trends and highlight data exceptions. More styles, data bar options, and new icon sets made available. References to other worksheets allow in conditional formatting rules. Conditional formatting stores dependencies of the formulas used so reevaluation of the entire conditional format is not necessary as often. Pivot tables or scrolling refresh more quickly so they can display faster. For more information, see More Conditional Formatting Features in Excel 2010 ().
Icon sets
Icon Sets are a new type of conditional formatting. An icon is drawn in each cell representing the value of the cell relative to the other cells in the selected range. Icons sets are a great way to create groups of similar data as a part of your data analysis. For additional information see Icon Set Improvements in Excel 2010 ().
Data bars
Data bars now drawn proportionally according to their values. Negative values more clearly displayed and zero values are suppressed. For more information, see Data Bar Improvements in Excel 2010 ().
OfficeArt controls and objects
In Excel 2010, in addition to shape objects, the following controls and objects are converted to the new OfficeArt technology:
1. Form controls
2. Microsoft ActiveX objects
3. OLE objects
4. Camera tool objects
Shape objects drawn in earlier versions of Microsoft Excel that are not upgraded to Microsoft Excel 2010 SmartArt format cannot be grouped with shape objects that are created in or upgraded to Excel 2010 SmartArt format. Mixed shape objects are layered, with the earlier versions of shape objects drawn on top of all later versions. This also means that Excel 2010 charts cannot be shown on dialog sheets that were created in an earlier version of Excel. You won’t be able to access the new shape objects by clicking Select Objects (Home tab, Editing group, Find & Select button). To select the newer shape objects, you must use the Select Multiple Objects command (File tab, Options, Customize Ribbon).
Pattern fills
Pattern fills removed in 2007 have been reintroduced in 2010. Charts formatted with pattern fills in previous versions of Excel will retain and display the pattern fills when opened in Office Excel 2007. For more information, see Chart Pattern Fills ().
In Strategic Improvements
Charting enhancements
It is easier to work with charts in Excel 2010. Specific improvements include the following:
• New charting limits It is easier to work with charts in Microsoft Office Excel 2007. Specific improvements include new charting limits. In Microsoft Office Excel 2007, you could have up to 32,000 data points in a data series for 2-D charts. In Excel 2010, the number of data points in a data series is limited only by available memory. This enables users — especially those in the scientific community — to more effectively visualize and analyze large sets of data. Memory errors could result if large 64-bit worksheets are calculated on a 32-bit machine.
• Macro recording for chart elements In Office Excel 2007, recording a macro while formatting a chart or other object did not produce any macro code. However, in Excel 2010, you can use the macro recorder to record formatting changes to charts and other objects.
• Improvements in the chart UI
Include PivotChart Interactivity, Formatting Enhancements, Parity Improvements, and Limit Increases. Double click any chart element and the format dialog appears. The chart element selector is available in the right click mini-bar. Pattern fills are available again. When formatting charts you can now record a macro to use format and layout changes again. Parity Improvements were made in the areas of Axis Scaling, Layout, Visual Parity, and Object Model Parity. Data size limits on charts are removed or increased. Prior limit of 32,000 points per data series on 2D is removed. Machine memory is the current limit. The maximum of 256,000 data points is now removed. The only limit is the available memory and machine capacity. For more information, see More Charting Enhancements in Excel 2010. ()
What’s removed
This section highlights features that were available in previous versions of Microsoft Office that are removed from Excel 2010 and that might be of interest to IT administrators. For more information about removed features, see Microsoft Excel 2010 ().
In Addressing Customer Needs
This section highlights changes in Excel2010 to address customer needs, especially improvements in programmability.
Clip Art task pane Search in Box
The Search in box is no longer available, which means that you can no longer limit your search to specific collections of content. To narrow your search, you can use multiple search terms in the Search for box.
ClipArt task pane Clip Organizer
Clip Organizer is a tool that arranges and catalogs clip art and other media files stored on your hard disk. Clip Organizer is no longer directly accesses the Clip Art task pane in Office programs. In addition, the following changes were made to Clip Organizer:
• Although you can delete clips from Clip Organizer, you can no longer delete a clip from a specific collection.
• The command that allowed you to find clips of a similar style is no longer available.
• The command for sending a clip as an attachment in e-mail messages is no longer available.
• The List and Details views are no longer available. Instead, all clips appear as thumbnails in the Clip Organizer window.
• The Organize clips link is no longer available. To open Microsoft Clip Organizer from Windows 7, Windows Vista, or Windows XP, click the Windows Start button, click All Programs, click Microsoft Office, click Microsoft Office 2010 Tools, and then click Microsoft Clip Organizer.
• The command for automatically finding media files on your computer and organizing them into collections no longer exists. However, you can still add clips manually to Clip Organizer or import them from a scanner or camera.
In Calculation features
Conditional Sum Wizard
The Conditional Sum Wizard is replaced in Excel 2010 by a Function Wizard that includes SUMIF and SUMIFS functions. Formulas created in a previous version that were generated by the Conditional Sum Wizard will continue to work and can be edited using other methods. The legacy Conditional Sum Wizard add-in is no longer available with Excel2010.
Lookup Wizard
The Lookup Wizard is replaced in Excel2010 by a Function Wizard that includes SUMIF and SUMIFS functions. Formulas created in a previous version that were generated by the Lookup Wizard will continue to work and can be edited using other methods. The legacy Lookup Wizard add-in is no longer available with Excel2010.
In Office Suite Changes
Smart tags now “Additional actions”
Smart tags have been replaced by the context menu option “Additional actions” in Excel 2010. Text is no longer automatically recognized by a smart tag recognizer and is no longer marked by a purple dotted underline of the activated cell. Instead, users are able to trigger the data recognition function and view the custom actions associated with text by selecting the text and choosing the Additional actions item on the context menu activated by right-clicking a selected cell.
Calendar Control
Calendar control (mscal.ocx) was a Microsoft Access feature that could be used in Access worksheets. Calendar control is removed in Access 2010 and is not usable for Excel 2010. Instead, users can use Date Picker or their own custom calendar controls.
Migration considerations
When planning a migration to Excel 2010, review what is new, changed, and removed for Excel 2010. Because Excel 2010 has many similarities with Office Excel 2007, such as the same native file format, you can also review and use the existing migration documentation for Office Excel 2007 when you migrate to Excel 2010. For more information, see the links provided in the See Also section.
MSXML5
MSXML5 is not supported in Excel 2010. Users will receive a runtime error if they attempt to run an Excel extensibility solution created by using MSXML5. Migrate code to MSXML6 or to managed code that uses the .NET Framework.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010.
See Also
Changes in Office 2010
Changes in Office Excel 2007 ()
Migration considerations for Excel 2007 ()
Introduction to Office Migration Planning Manager (OMPM) ()
Changes in InfoPath 2010
This article lists changes in Microsoft InfoPath 2010 since Microsoft Office InfoPath 2007.
In this article:
• What’s removed
What’s removed
This section provides information about removed features in InfoPath 2010.
Data importer framework
In the InfoPath 2010 Editor, the entry point for Import form data is removed. The Import form data option enabled users to select a third-party data importer to import form data into their forms.
Data set change tracking
The functionality to track data set changes when a user designs a form in InfoPath Form Designer against a Web service that returns the System.DataSet type is removed in InfoPath 2010. However, existing forms that use change tracking with the System.DataSet type will continue to work in InfoPath 2010.
InfoPath Form Designer Group Policy template settings
The settings that let you disable aspects of InfoPath Form Designer are removed from the Office 2010 Group Policy templates. This change provides more consistent functionality across installations of InfoPath 2010.
Form template exporter
The form template exporter extensibility option is removed from the InfoPath 2010 Form Designer. In Office InfoPath 2007, this option enabled third-party vendors to provide tools to export InfoPath form templates to other formats.
Form template samples
The sample form templates that were included with Office 2003 and the 2007 Office system are removed in InfoPath 2010. If an organization uses these templates, you must republish these form templates to a location other than the default location to continue using the forms. The new page and section layouts that are now in the InfoPath Form Designer replace the form templates.
Human Workflow Services integration
All integration points with BizTalk Human Workflow Services are removed from InfoPath 2010. This functionality is replaced by Workflows in Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010.
Installable form templates
The capability to publish a form template that can be installed on the local client computer as an application is removed. Instead, users can publish forms to a specific location and run the form from that location. Existing installable forms will continue to run in the InfoPath 2010 Editor.
Receive and Submit Web service connection
The Receive and submit data Web service connection option is removed for new forms. To simplify the feature and promote best practices, it is replaced with separate options to create a Receive data connection and then create a secondary Submit data connection. Existing forms that use the Receive and submit data Web service connection type will still work in InfoPath 2010.
Sample data
The capability to display sample data in the controls is removed. In InfoPath 2010 users must preview the form and manually enter sample data to evaluate how it looks in the form.
Script code development environment
The ability to develop script code in InfoPath 2010 is removed. When existing forms with script code are opened, all of the entry points to add code to a form will be disabled and hidden. Runtime support continues, but customers will have to upgrade script code to managed code to continue developing by using an integrated development environment in InfoPath.
Support for Microsoft XML Parser 5
Office 2010 does not support Microsoft XML Parser version 5 (MSXML5). Existing solutions will not create an instance of MSXML5 objects when loaded by Office 2010. Migrate code to managed code by using the Microsoft .NET Framework or to MSXML6. Note that MSXML6 does not support digital signature code.
Changes in OneNote 2010
This article lists changes in Microsoft OneNote 2010 since Microsoft Office OneNote 2007. If you are upgrading from Microsoft Office OneNote 2003, see also Changes in Office OneNote 2007 ().
In this article:
• What’s new
• What’s changed
• What’s removed
• Migration considerations
What’s new
This section highlights new features in OneNote 2010.
Fluent UI
The OneNote 2010 user interface is redesigned and now uses the Microsoft Office Fluent user interface (UI). Introduced in the 2007 Microsoft Office system, the Fluent UI is designed to make it easier for people to find and use the full range of features that Office applications provide, and to preserve an uncluttered workspace. For more information about the Fluent UI, see the resources in Microsoft Office Fluent User Interface Resource Center ().
The ribbon
The ribbon, part of the Fluent UI, is designed to optimize key OneNote note-taking scenarios to make them easier to use. The ribbon in OneNote 2010 provides quicker access to all the commands and allows for easier future additions and customizations. You can also customize the ribbon. For example, you can create custom tabs and custom groups to contain frequently used commands. To help maximize the note-taking space on the page, the ribbon can also be hidden while writing.
Backstage view
The Microsoft Office Backstage is part of the Fluent UI and a companion feature to the ribbon. The Backstage view, which can be accessed from the File tab, helps you find frequently used features for managing your Microsoft OneNote notebook files. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier releases of Microsoft Office.) The Backstage is used to manage files and the data about the files, such as creating and saving files, inspecting for hidden metadata or personal information, and setting file options.
Language preferences
OneNote 2010 also provides simplified language settings that allow multilingual users to use a single dialog box in OneNote 2010 to set preferences for editing, display, ScreenTip Language, and Help languages. If users do not have a required software or keyboard layout installed, a notification displays to provide information and links to resolve such issues.
File format
The OneNote 2010 file format enables new features, such as sharing on the Web, linked note-taking, mathematical equations, and versioning.
OneNote 2010 will continue to work on Office OneNote 2007 notebooks without changing to the new file format. By default, notebooks are not upgraded. Do not upgrade notebooks if you plan to share them with Office OneNote 2007 users. To change an existing notebook to the OneNote 2010 notebook format, use the Notebook Properties dialog box: Click the File tab, click the Settings drop-down menu, and then click Properties, or right-click the Notebook and click Properties.
[pic]Note:
If you change a notebook to the OneNote 2010 notebook format, you cannot change it back to the Office OneNote 2007 format.
Improved access to information
OneNote 2010 provides virtually uninterrupted access to notes by allowing you to view and use your notebook files anywhere — at work, home, or in transit.
• Sync to Windows Live You can access notebooks from any computer. You can also synchronize notebooks by using shared folders, Microsoft SharePoint Server 2010, and USB drives.
• Microsoft OneNote Web App You can access and edit notebooks from a Web browser, even on computers on which the full version of OneNote is not installed.
• Microsoft OneNote Mobile 2010 By using a compact version of OneNote on a Windows Mobile-based smartphone, you can access and edit your notebooks stored on Windows Live and SharePoint.
Search, Outlook integration, organization, and editing improvements
The changes in these areas include the following:
• Improved search, which can find information on either the current page, within selected sections or notebooks, or within notebooks.
• Outlook integration improvements:
• Create Outlook tasks from OneNote.
• Improved organization and search features:
• Section and page tab improvements.
• Search improvements allow for rapid search and navigation within the search results. For example, by typing the first few letters of a title, users can quickly jump to recently visited pages, or repeat a previous search.
• The ability to easily add links to content within other content — for example, pages, sections, or section groups — and to quickly navigate through these links. This enables you to create Wiki-like notebooks.
• Quick Filing feature, which lets you choose where in your notebook you want to send information (such as mails from Outlook, pages from Internet Explorer, and so on).
• Editing improvements:
• Quick Styles for creating and applying headings.
• Support for mathematical equations.
• Formatting improvements for bulleted lists.
• Mini Translator, which lets you use your mouse to point to a foreign word or phrase and see a translation into your native language in a small window (you can also use the Play button to hear the pronunciation of the word or phrase, and use a Copy button to paste the translation elsewhere in your notebook).
• Research and note-taking improvements:
• Linked note-taking to Web page URLs, Microsoft Word 2010, and Microsoft PowerPoint 2010.
• Automatic text wrapping.
• Docked OneNote.
• Information Rights Management (IRM) protected printouts.
• Print driver for 64-bit operating systems.
Sharing and collaboration features
OneNote 2010 supports simultaneous editing of notebooks by multiple users. For example, a group of users can work on a notebook at the same time, or a single user can work on the same notebook from different computers simultaneously, all without locking the file.
The changes are as follows:
• New content is automatically highlighted.
• Author information for any added or shared content is identified by a color-coded bar and the author’s initials.
• Version support lets users see when and by whom changes were made to a notebook. Changes relative to earlier versions of the notebook are automatically highlighted.
• Faster synchronization of pages so that changes are displayed to all authors in near real time.
• Display recently added content (by last day, week, month, and so on). You can also get an overview of what specific users changed on specific days.
• Merge feature allows merging two sections of a shared notebook.
Support for touch-enabled computers
OneNote 2010 provides support for computers that run touch-enabled operating systems such as Windows 7. The features include the following:
• Panning and auto-switching On compatible computers that run Windows 7, the user can scroll and pan around any page in OneNote 2010 by using a finger and, depending on the input device, OneNote automatically switches between pen, pan, and selection.
• Zooming On multitouch devices, such as a computer that runs a touch-compatible or multitouch-compatible operating system such as Windows 7, using a pinch gesture with the fingers allows a user to zoom in or out of a notebook page in OneNote to customize the page view.
• Improved navigation Several navigational enhancements have been added to OneNote 2010 for users who have computers that run touch-enabled operating systems.
[pic]Note:
For more information, see the OneNote 2010 resources in the “Getting Started with OneNote” guide included in the product. For information about OneNote 2010 features and how to use the product features, see the Microsoft OneNote 2010 Beta Help blog ().
Top of page
What’s changed
This section summarizes the feature changes in OneNote 2010.
Task pane replacements
The following task panes are replaced in OneNote 2010:
• Customize My Tags — Replaced by a dialog box in the Fluent UI.
• New — Options in the New task pane are available in the New section of the File tab.
• Font — Options are available in the Basic Text group on the Home tab on the ribbon.
• Bullets — Replaced by the Bullets gallery in the new Basic Text group on the Home tab. The ability to change all bullets at a specific level is removed.
Some task panes are removed in OneNote 2010, as noted in Task Panes removed later in this article.
Top of page
What’s removed
This section provides information about removed features in OneNote 2010.
Outlining features and body text
The Outlining toolbar, including the Make Body Text option, is removed in Microsoft OneNote 2010. The ability to increase and decrease indentations and expand or collapse text is available through other user interface entry points and keyboard shortcuts.
SimpleImporter API
The SimpleImporter API was introduced in Microsoft Office 2003, and was replaced by another API in the 2007 Microsoft Office system, although it remained available to the few users who still needed it. The SimpleImporter API is completely removed in Microsoft OneNote 2010.
Start Live Session
The Start Live Session functionality is removed. In OneNote 2010, we recommend that you use a shared notebook. To share a notebook in OneNote 2010, you can specify a Web location so that you can use the notebook from any computer or from a Web browser. This option requires that you sign in or sign up for an account such as Windows Live. You can also enter the full path of a network file share, enter a mapped network drive, or paste the full address of a SharePoint document library where you want to create and store the shared notebook. The page updates will be reflected in near real-time to all users. To use the shared notebooks feature, select Share This Notebook (or New Shared Notebook) on the Share tab. For more information, see the “Getting Started with OneNote” guide included in the product.
Join Live Session
This functionality is removed. As noted in the Start Live Session section, in OneNote 2010, we recommend that you use a shared notebook.
Current Live Session
This functionality is removed. As noted in the Start Live Session section, in OneNote 2010, we recommend that you use a shared notebook.
Create Outlook Appointment and Create Outlook Contact
The Create Outlook Appointment and Create Outlook Contact functionality is no longer available.
Task Panes removed
The List and Document Management task panes are removed from Microsoft OneNote 2010. The functionality is no longer available, and the user interface entry points are removed. New features in OneNote 2010 provide more functionality than these rarely used features.
For information about task pane replacements, see Task pane replacements earlier in this article.
Top of page
Migration considerations
This section discusses issues that administrators should consider when migrating from previous versions of Microsoft OneNote to Microsoft OneNote 2010.
In this section:
• OneNote 2010 availability
• OneNote 2010 file format
• Upgrading OneNote 2007 notebooks
• Upgrading OneNote 2003 notebooks
• OneNote notebook sharing
• OneNote user data settings migration
OneNote 2010 availability
OneNote 2010 is included in all editions of the Office 2010 suites:
• Microsoft Office Home and Student 2010
• Microsoft Office Home and Business 2010
• Microsoft Office Standard 2010
• Microsoft Office Professional 2010
• Microsoft Office Professional Plus 2010
For information about system requirements for OneNote 2010, see the Microsoft OneNote 2010 section in System requirements for Office 2010.
In the 2007 Microsoft Office system, Microsoft Office OneNote 2007 was included in these editions of the product: Microsoft Office Home and Student 2007, Microsoft Office Ultimate 2007, and Microsoft Office Enterprise 2007.
Microsoft Office OneNote 2003 was available only as a stand-alone product.
OneNote 2010 file format
OneNote 2010 uses a new file format for saving files than previous versions of the product. Many of the new OneNote 2010 features (such as math equations, versioning, linked note taking, and multi-level subpages) require the new format to work. The new file format also lets you share your notebooks on the Web, so you can use a Web browser to view and edit your notebook files. When you create a notebook in OneNote 2010, the file is saved in the new OneNote 2010 file format by default.
With OneNote 2010, you can view, open, and edit notebooks that are saved in the Office OneNote 2007 file format. You can convert Office OneNote 2007 notebooks to OneNote 2010, and you can also convert them back to the Office OneNote 2007 format. For more information, see Upgrading OneNote 2007 notebooks later in this article.
Notebooks that use the OneNote 2003 file format are read-only in OneNote 2010 (and in Office OneNote 2007). This means that you cannot edit files that use the OneNote 2003 format in OneNote 2010 or in Office OneNote 2007. For more information, see Upgrading OneNote 2003 notebooks later in this article.
To determine the file format of a notebook, in OneNote 2010, right-click the notebook icon in the navigation bar, and then click Properties. The Notebook Properties dialog box displays, and the Default File Format section indicates the file format version. If you open an Office OneNote 2007 notebook, the application title bar also displays "[Compatibility Mode]" to indicate the file format is Office OneNote 2007.
Upgrading OneNote 2007 notebooks
OneNote 2010 works on Office OneNote 2007 notebooks without changing to the new file format. OneNote 2010 can view, open, and edit Office OneNote 2007 notebook files. By default, existing Office OneNote 2007 notebooks are not automatically converted when you update from Office OneNote 2007 to OneNote 2010. You cannot use Office OneNote 2007 to open and use notebooks that are saved in the OneNote 2010 file format.
If you plan to share your notebooks with Office OneNote 2007 users who do not have OneNote 2010, we recommend that you do not upgrade the notebooks.
If sharing notebooks with users of earlier versions of OneNote is not a requirement, we recommend that you convert existing notebooks to the OneNote 2010 format to enable all of the new product features.
Upgrading OneNote 2003 notebooks
As noted previously, notebooks that use the OneNote 2003 format are read-only in OneNote 2010. If you want to be able to edit your OneNote 2003 notes when you upgrade from OneNote 2003 to OneNote 2010, you must upgrade your notebook to the OneNote 2010 format (or the Office OneNote 2007 format). To do this, open the notebook in OneNote 2010, and then click the Information Bar that appears at the top of every page in your OneNote 2003 notebook.
[pic]Note:
After you convert OneNote 2003 notebooks to the OneNote 2010 or the Office OneNote 2007 format, they cannot be changed back. Therefore, we recommend making a backup copy of the notebooks before you convert the files to a newer format.
OneNote notebook sharing
In Office OneNote 2007, users can participate in live shared note-taking sessions. User can store their shared notebooks in a Web location or a network location such as a network file share, or a SharePoint document library. They can access their shared notebooks from any computer or from a Web browser, or from a computer on the same network or a SharePoint document library. This allows all participants to view and edit each other's notes. To use the live shared session feature, users open the notebook and section that they want to share with others, point to Live Sharing Session on the Share menu, and then click Start Sharing Current Section.
In OneNote 2010, the Start Live SessionJoin Live Session, and Current Live Session functionality is removed. In OneNote 2010, we recommend that you use a shared notebook. The page updates are reflected in near real-time to all users. In OneNote 2010, multiple authors can access a shared notebook simultaneously. When authors edit the pages and sections in the shared notebook, OneNote automatically synchronizes the changes so that the notebook is always up-to-date. OneNote maintains a separate offline copy of the notes on each user’s computer. Authors can edit the notes locally even when their computer is disconnected from the network. The next time that the users connect to the shared notebook, OneNote automatically merges their changes with the changes made by other authors.
To use the shared notebooks feature in OneNote 2010, select Share This Notebook (or New Shared Notebook) on the Share tab. Users can choose to share their notebooks on the Web so they can be accessed from any browser (this option requires a Windows Live account). They can also choose to use the full path of a network file share, enter a mapped network drive, or paste the full address of a SharePoint document library. For more information, see “Share notebooks in OneNote 2010” in the OneNote online Help.
OneNote user data settings migration
Information about the OneNote registry keys that are migrated when performing an Microsoft Office 2010 installation is available in Migrate user data registry keys in Office 2010. The article provides information about the Office OneNote 2007 and OneNote 2003 user data registry keys that are migrated and those that are not migrated for the following Microsoft Office 2010 upgrade scenarios:
• In-place upgrade An earlier version of Office such as the 2007 Microsoft Office system is installed on computers.
• Uninstall and upgrade The installed version of Office is uninstalled first and then Office 2010 is installed on computers.
• Operating system upgrade A new version of the operating system such as Windows 7 is installed with Microsoft Office 2010.
For information about Office OneNote 2007, see the following sections: “OneNote 2007 ” and “OneNote 2007 ” in Migrate user data registry keys in Office 2010.
For information about OneNote 2003, see the following sections: “OneNote 2003 ” and “OneNote 2003 ” in Migrate user data registry keys in Office 2010.
See Also
System requirements for Office 2010
Migrate user data registry keys in Office 2010
Product and feature changes in Office 2010
Changes in Outlook 2010
This article lists changes in Microsoft Outlook 2010 since Microsoft Office Outlook 2007 and migration considerations. If you are upgrading from Office Outlook 2003, see also Changes in Outlook 2007 () and Migration considerations for Outlook 2007 ().
In this article:
What’s new
What’s changed
What’s removed
Migration considerations
What’s new
This section highlights new features in Outlook 2010.
64-bit editions
Starting with Microsoft Office 2010, Outlook is available as a 32-bit application and a 64-bit application. The version (bitness) of Outlook that you choose depends on the edition of the Windows operating system (32-bit or 64-bit) and the edition of Office 2010 (32-bit or 64-bit) that is installed on the computer, if Office is already installed on that computer. The bitness of an installed version of Outlook is always the same as the bitness of Office 2010, if Office is installed on the same computer. For more information, see 64-bit editions of Office 2010.
If you have a MAPI application in your environment, that the bitness of the MAPI application must be the same as the installed version of Outlook 2010. For more information, see Considerations for MAPI applications for Outlook in 64-bit editions of Office 2010.
Bitness registry key
When Outlook 2010 is installed, it sets the new registry key named Bitness, which indicates whether the Outlook 2010 installation is a 32-bit or 64-bit version. This can be useful to administrators who want to audit computers to determine the installed versions of Outlook 2010 in their organizations.
Registry path: HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook
Registry key: Bitness
Value: either x86 or x64
For more information about Microsoft Office 2010 in 64-bit, see 64-bit editions of Office 2010.
Calendar Preview in meeting requests
Microsoft Outlook shows a preview of your calendar in meeting requests. The Calendar Preview feature shows where the meeting appears in your Calendar together with any conflicting and adjacent meetings. When you view a meeting request for a recurring meeting, you can use the Calendar Preview feature to navigate between meeting instances in the series.
Conversation actions
Outlook 2010 contains several new features to help users manage their Inboxes more effectively, including the Ignore and Clean Up commands. The Ignore button on the ribbon moves all of a conversation and any future replies to that conversation directly to the Deleted Items folder. The Clean Up button moves older, redundant messages in the conversation to the Deleted Items folder but keeps the most recent message.
Quick Steps
Quick Steps are one-click buttons that can perform multiple actions at the same time. Users can create their own Quick Steps to manage their e-mail with a single click.
Multiple Exchange accounts
Outlook 2010 can connect to multiple Exchange accounts at the same time. The Exchange accounts can be in the same or different domains or servers.
Roaming AutoComplete list
Recipient AutoComplete lists are now stored on the Exchange Server. A user’s recipient AutoComplete list is now available to any computer on which Outlook 2010 runs that is connected to the same Exchange account. Names can be easily removed from the list by using the new inline Delete function.
The ribbon
The ribbon, part of the Microsoft Office Fluent user interface (UI), replaces the menus and toolbars of the Outlook main window. Ribbon tabs can be customized or replaced with tabs that you create. Through the Options menu on the File tab, you can create new tabs that bring together your favorite commands and groups. Existing tabs can also be customized to meet the organization’s needs.
Features available with Office Communicator 2007 R2, Office Communicator Server 2007 R2, or later versions
With richer integration of Microsoft Communicator than in earlier versions, you can start live conversations from Outlook 2010. Hover over a name, see a person’s availability and then easily start a conversation directly through instant messaging, voice call, or video.
Features available with Microsoft Exchange Server 2010
The following features are available with Microsoft Exchange Server 2010 and Outlook 2010.
• Calendar features An organization can now establish a federated trust relationship with an external partner and share availability (free/busy) information, calendar, or contacts. Federation provides the underlying trust infrastructure to enable easy and secure sharing of information across Exchange organizations and in cross-premises organizations. You can also use the new Group Schedule view in Outlook Calendar to see multiple calendars vertically, instead of side by side, or save frequently used groups of calendars together from one location. The Group Schedule view is optimized for viewing a schedule for a group and scheduling a meeting for a group.
• Call answering and routing rules Unified Messaging in Exchange Server 2010 enables you to create call answering and routing rules for individuals or groups of callers based on Caller ID and contact information.
• Centralized rights management You can set up rules to automatically apply Information Rights Management policies to outgoing e-mails based on content or recipients.
• Integrated e-mail archive The Personal Archive feature is available with Outlook 2010 and Exchange Server 2010 and lets you regain control of the organization's messaging data by eliminating the need for Personal Folder files (.pst). Like .pst files, the Personal Archive feature does not affect the user’s primary mailbox size. However, unlike .pst files, the e-mail archive folders are stored online so that users can access the archived files by using Microsoft Outlook Web App or from a secondary computer by using Outlook 2010. By using either of these client applications, users can view an archive mailbox and move or copy messages between their primary mailboxes and the archive.
• MailTips This feature is a configurable warning system to help prevent common e-mail mistakes. Extra information is presented to users when they compose e-mail messages. The MailTips are displayed in an InfoBar, similar to the banner that says "This message has not been sent”. MailTips do not prevent sending an e-mail message. But they reveal things that might be unexpected about the delivery or audience of the message, such as recipient validity, whether the recipient is external to the organization or is out of the office, if the distribution list is unusually large, or if a message might not be delivered.
• Protected Voice Mail This feature enables encrypted voice mail to be sent to a user’s mailbox. Protected voice messages can be marked as Private to prevent them from being forwarded.
• Text messaging through Exchange ActiveSync Windows Mobile 6.5 (or a later version) telephones or browser-enabled cellular telephones can access text messages by using Exchange ActiveSync, a synchronization protocol that is optimized to work together with high-latency and low-bandwidth networks.
• Voice Mail Preview Microsoft speech technology converts voice mail messages into text that users receive in an e-mail or text message.
For more information about Microsoft Exchange Server 2010, see Microsoft Exchange 2010 () and What's New in Exchange Server 2010 ().
What’s changed
This section summarizes the feature changes in Outlook 2010.
Conversation view
The Conversation view in Outlook 2010 is changed. The Conversation view provides a threaded view of e-mail messages in an Microsoft Outlook folder, and in Outlook 2010 is accessed by clicking View, Conversation, and then Show Messages in Conversations. The improved Conversation view helps users deal with larger volumes of incoming e-mail, reduces information overload, and increases user productivity in e-mail.
Improved IMAP support
IMAP accounts are easier to set up in Outlook 2010 than in earlier versions. When users add a new account in Outlook 2010, the automatic configuration of a Webmail account will set the account type to IMAP by default for IMAP-supported Webmail accounts such as Google Gmail. Note that users can change the account type to POP3 by selecting the Manually configure server settings option in the Add New Account dialog box.
The Delete and Send operations for IMAP accounts are also improved in Outlook 2010. IMAP accounts now have a separate Deleted Items folder. Also, Outlook 2010 does not prompt for a Sent Items folder, as Office Outlook 2007 did. This is consistent with Outlook behavior for other e-mail account types.
Outlook is more responsive for IMAP users in Outlook 2010 and Office Outlook 2007 SP2. On-demand downloads of messages now occur in the background.
Faster performance
Outlook 2010 starts and exits faster than Office Outlook 2007. Outlook 2010 performance is faster overall than Office Outlook 2007.
Menu and commands
• ALT keyboard shortcuts With the introduction of the ribbon in Outlook 2010, the ALT keyboard shortcuts have changes. Press ALT to display the command key tips.
• Copy Folder Design The Copy Folder Design command is replaced with the ribbon View tab option Apply Current View to Other Mail Folders.
• Current View and Organize panes The Current View pane in the navigation pane for Contacts, Tasks, and Notes is removed in Outlook 2010. Also the Organize pane accessed in Office Outlook 2007 by clicking Tools and Organize is removed in Outlook 2010. You can change and format your views by using the features on the ribbon View tab.
• Go menu The Go menu option is redundant with the Navigation pane in Office Outlook 2007. The keyboard shortcuts that were shown in the Go menu still work and are now displayed as tooltips on the navigation pane buttons. For example, you can use Ctrl+1 to switch to Mail, Ctrl+2 for Calendar, Ctrl+3 for Contacts, Ctrl+4 for Tasks, and so on.
• Plan a Meeting This dialog box accessed in Office Outlook 2007 from the Actions menu in the Calendar view is replaced by the ribbon Home tab Schedule View command in the Calendar view.
• View Group Schedules This dialog box accessed in Office Outlook 2007 from the Actions menu in the Calendar view is replaced by the commands in the Manage Calendars section on the ribbon Home tab and in the navigation pane in the Calendar view. From the ribbon Calendar Groups option, you can create a Calendar Group by clicking Create New Calendar Group or save currently displayed calendars by using the Save as New Calendar Group. In the navigation pane, you can select which group calendars to view and right-click on a group to find the Rename Group, Delete Group, and New Calendar Group commands.
Search tools
Outlook 2010 enables you to easily find and manage large quantities of e-mail, calendar items and contact files. The Search tab on the new Outlook 2010 ribbon includes search filter options to help quickly narrow your search results. You can quickly change the scope of search by selecting, for example, All Subfolders. You can then refine the search by using search filter buttons such as Subject, Has Attachment, or Unread. You can also run advanced searches and view your recent searches to run them again.
Improved in Outlook 2010 with Exchange Server 2010
The following Outlook 2010 improvements are available through Exchange Server 2010.
• Greater calendar reliability Improvements in Outlook 2010 and Exchange Server 2010 logic make calendars more reliable than in Office Outlook 2007. Improvements include conflict resolution in online mode to resolve conflicts when there are different updated versions of an item on the server and on the client. Also, multiple instances of a recurring meeting can now be changed independently of one another.
Exchange Server 2010 introduces the Calendar Repair Assistant (CRA). CRA can automatically detect and correct inconsistencies that occur for single and recurring meeting items for mailboxes that are on an Exchange Server 2010 mailbox on which the Microsoft Exchange Mailbox Assistants service runs.
• Improved retention and compliance functionality Users can apply retention policy to a message or a folder. IT can enforce policies on built-in folders (Inbox, sent items, and so on). Also, an online archive provides separate, online-only folders for long-term retention and archiving.
• Simplified administration By using role-based access control (RBAC), you can control resources and the features that users can access. You create role assignment policies for each specialized user group and tailor those role assignment policies to grant more-restrictive or less-restrictive permissions to the groups. For example, you could create a Compliance Offer role to conduct mailbox searches for legal discovery, a Human Resources role to update employee information in the company directory, or a Help Desk role to manage mailbox quotas. Users can also manage some tasks on their own, such as creating and managing distribution groups or tracking message delivery.
For more information about Microsoft Exchange Server 2010, see Microsoft Exchange 2010 ().
What’s removed
This section provides information about removed features in Outlook 2010.
ANSI offline Outlook data files (.ost) for Exchange synchronization
ANSI offline Outlook data files (.ost) can no longer be created (unless overridden by Group Policy). By default, newly created profiles in Outlook 2010 will be in Unicode.
Unicode Outlook data files (.ost) are recommended in all scenarios except when alternate display names are required. To use alternate display names, configure Group Policy to set the default Outlook data files (.ost) to ANSI. The Group Policy keys to set are in the Outlook 2010 Group Policy template in Microsoft Outlook 2010\Account Settings\Exchange and Microsoft Outlook 2010\Miscellaneous\PST Settings. Note that ANSI .ost files do not work for profiles that contain multiple Microsoft Exchange Server accounts.
AutoArchive-based retention
Users can no longer deploy AutoArchive-based retention settings through Outlook 2010 by using Group Policy. Users who need retention policies are encouraged to explore the Messaging Records Management (MRM) features in Microsoft Exchange Server 2007 and later versions.
Calendar rebasing tool
The calendar rebasing tool is removed in Outlook 2010. Calendar rebasing was introduced in Microsoft Office Outlook 2007, and was accessed by clicking Tools, Options, Calendar Options, Time zone, and then making selections in the Time zone drop-down list. Calendar rebasing is available through a separate Web tool, Time Zone Data Update Tool for Microsoft Office, which is currently available to users from the Microsoft Download Center.
The Change Time zone button is no longer available in the Time zone dialog box, and all underlying code and user interface code are removed. New calendar items that are created in Outlook 2010 can display start and end times correctly without the need for rebasing. Users can use Time Zone Data Update Tool to rebase down-level clients and servers.
Customization of Contact Activity Search folders
In Outlook 2010, the Activities tab on the Contact Folder Properties dialog box is removed because of low usage. This feature allowed you to customize the list of folder groups available to search when in the Activities view on the individual Contact item.
DAV connectivity for HTTP account types
Distributed Authoring and Versioning (DAV) connectivity is removed in Outlook 2010. DAV is an old mechanism used when you connect to Windows Live Hotmail and synchronize e-mail. A new mechanism for Hotmail connectivity exists, and enables synchronization of e-mail, contacts, and calendar synchronization through a Web download. There is no visible loss of functionality to Hotmail users. Users who connect to other DAV accounts (non-Hotmail accounts) will lose connectivity and will be unable to synchronize e-mail.
Exchange 2000 connectivity
Outlook 2010 cannot connect to Microsoft Exchange Server 2000 or earlier versions of Exchange. Users who run Exchange Server 2000 in their environments will receive an error message when Outlook 2010 attempts to connect to the server. The error message will state that the server version is not supported. Public folders in Microsoft Outlook 2010 also cannot connect to Exchange Server 2000, although an error message does not appear. Users will have to migrate to Exchange Server 2003 or a later version.
Exchange Message Security feature support
Support for the Exchange Message Security feature in Outlook 2010 is removed. Customers must use S/MIME to support message security. The infrastructure to support the Exchange Message Security feature was deprecated in Exchange 2000 Server SP2. For more information about S/MIME, see Understanding S/MIME ().
Most Recently Used list
The list of last opened Other User's Folder in the File | Open menu is removed. As a replacement, consider using delegates, adding additional Exchange accounts to user profiles or sharing tasks and calendars. The Other User's Folder is still available in Outlook 2010 by clicking the ribbon File tab and Open.
Outlook integrity check tool (.ost)
The Outlook Offline Folder (.ost) integrity check tool (scanost.exe) is not included in Outlook 2010. This tool was recommended in previous versions for fixing errors in Outlook data files (.ost).
If there is an issue with a specific folder, you can resync the folder:
1. Right-click the folder and then click Properties.
2. In the dialog box that appears, click the Clear Offline Items button and then click OK.
3. On the Outlook 2010 ribbon, click the Send/Receive tab.
4. Click Update Folder.
Otherwise, we recommend that you delete the .ost file and let Outlook download information again from Exchange. The exception is if you have local data that is not present on the server. In that case, we recommend that you export the data to an Outlook Data File (.pst), delete the .ost file, allow the server data to download again, and then import the .pst file data by using the Do not import duplicates option that can be accessed through the Open option on the File tab.
Photo resize options
The Outlook 2010 options to resize attached photo do not include 640 x 480 or 800 x 600 pixels. If you decide to resize an image, the largest of the three previously supported choices (1024 x 768) is used by default in Outlook 2010.
Also, the resize options have been moved to the File tab.
These changes were made to simplify the resize options and make them more discoverable.
Postmarking
The Postmarking feature is removed in Outlook 2010. The When sending e-mail, Postmark the message to help e-mail clients distinguish regular e-mail from junk e-mail option is removed from the Junk E-mail Options dialog box and Postmarks will not be generated by Outlook 2010.
Preview of published Office Online calendars
The Office Online Calendar Sharing Service Web site enabled users to view and manage their shared calendars in a Web browser without having to subscribe to the published calendar. Within Outlook, users could select the Preview this Calendar option when they were notified that a calendar was shared to them.
The Web site for Outlook Calendar Sharing Service is discontinued with Outlook 2010. Therefore, the Preview this Calendar option is removed in Outlook 2010. Users can still publish their calendars for sharing. However, to view the contents of the calendar, users will have to subscribe to the calendar for viewing within Outlook. For Web access, users will have to subscribe to the calendar in Windows Live Calendar. Users who subscribe to the published Office Online Calendar in Outlook are not affected.
Quick View
Quick View is a file viewer that was included with Windows 95, Windows 98, and Windows NT 4.0. The related code in Outlook was removed in Outlook 2010. There is no related change to the user experience for those who are on supported operating systems.
Remote Mail
Remote Mail is removed from Outlook 2010. The Remote Mail functionality is replaced by Cached Mode, which was introduced in Outlook 2003.
Search Toolbar add-in
The Search Toolbar add-in setup code is removed in Outlook 2010. The Search Toolbar add-in enables local indexing of online mode Exchange Server mailbox stores by using Windows Desktop Search. As a result of this change, e-mail in online Exchange mailboxes will not appear in the results of Windows Explorer searches. The online indexing add-in is a legacy component that adversely affects performance of Outlook during startup and shutdown. With this removed in Outlook 2010, users will experience improved Outlook reliability and significantly lower Exchange bandwidth usage. For fast search, use Cached Exchange Mode or for online mode, use Exchange Search in Exchange 2007 and later versions.
Send Link to This Folder
In Office Outlook 2007 and earlier versions, this feature opens a new mail message that has an attached .xnk file that links to the public folder. Because of increased security in Office Outlook 2007, by default access is denied to Microsoft Exchange Server public folder shortcuts with an .xnk file name extension. So in Outlook 2010, the Send Link to This Folder on the Public Folder context menu is removed. Instead, consider using SharePoint Server for collaboration.
Send Options
In Outlook 2010, the ability to specify the format for e-mail messages by using Send Options is removed. This feature was once useful for sending e-mail to people who would receive an e-mail on an Apple computer. Apple computers can now read e-mail messages in Multipurpose Internet Mail Extensions (MIME) type. In Office Outlook 2007, to find the Send Options command enter an e-mail address in the To line, resolve the e-mail address, right-click the e-mail address and select Send Options.
Shade group headings
The ability to shade group headings is removed in Outlook. In Office Outlook 2007, to access this feature right-click on the column heading, select Custom…, Customize current view and then click Other Settings.
Third-party Exchange client extensions do not load
Third-party Exchange client extensions do not load on Outlook 2010. We recommend that users contact their Exchange client extension vendor for more information regarding an update to their solutions. Third-party exchange client extensions are replaced by add-ins built by using Microsoft Visual C++, Visual Studio Tools for Office, or third-party tools that can create an Outlook COM add-in.
Web browser support
Web browser support is removed in Outlook 2010. The following related features have also been removed.
• View Web pages from within Outlook
• Save as Web Page option for Calendar
• Search the Internet from within Outlook
• Navigate to Web pages within Outlook
Migration considerations
Even though several new features and user interface changes are added in Outlook 2010, the Outlook data files (.ost and .pst) and Outlook profile file (.prf) formats in Outlook 2010 are compatible with earlier releases.
Outlook data files (.pst and.ost)
With Outlook 2010, users can open and use Outlook data files that were created in earlier versions of Outlook. Users who have offline Outlook data files (.ost) do not need to re-create those files; for example, users whose accounts are configured to use Cached Exchange Mode. Similarly, users who have Outlook data files (.pst) can continue to use the files without converting or migrating the files.
By default, Outlook .pst and .ost files that are created by using Office Outlook 2003 and later versions are in the updated Unicode file format that allows larger file sizes (the 2-gigabyte (GB) limit is eliminated). The data file format (non-Unicode ANSI) used by Outlook 2002 and earlier is also supported by Outlook 2010.
If users currently have non-Unicode ANSI-formatted .ost files, we recommend that you upgrade the .ost files to Unicode.
• To determine whether users’ .ost files are in ANSI or Unicode format, see How to determine the mode that Outlook 2007 or Outlook 2003 is using for offline folder files ().
• For information about how to force an upgrade of an existing non-Unicode (ANSI) formatted .ost file to Unicode format, see the section “Force upgrade of non-Unicode ANSI format .ost files to Unicode” in Configure Cached Exchange Mode in Outlook 2010.
Outlook profile file (.prf)
As in earlier versions of Outlook, you can continue to use the Outlook profile file (.prf) to provide options for specifying additional Outlook settings or MAPI services.The Outlook 2010 .prf file format has changed but Office Outlook 2007, Office Outlook 2003, and Outlook 2002 versions of the file will work with Outlook 2010. If you plan to make updates to the .prf file for an Outlook 2010 deployment, we recommend that you re-create the .prf file by using the Office 2010 Office Customization Tool (OCT), export the settings to a new .prf file, and use that file to specify the additional Outlook settings or MAPI services that you need.
Reverting to Office 2007 from Office 2010
Because of the changes in Outlook 2010 that allow for multiple Exchange e-mail accounts, user profiles that were upgraded to Outlook 2010 will not work if the user removes Outlook 2010, reinstalls Office Outlook 2007, and then attempts to start Office Outlook 2007 by using the same user profile. In this scenario, the user profile will have to be removed and re-created in Windows through the Control Panel and Mail options.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 is updated to VBA 7.0. VBA 7.0 settings are reset to their defaults after migration instead of automatically repopulating. This occurs because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|2007 Office system and previous versions |HKEY_CURRENT_USER\Software\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\Software\Microsoft\VBA\7.0\Common |
For more information, see Migrate user data registry keys in Office 2010.
See Also
Changes in Outlook 2007 ()
Changes in Office 2010
Changes in PowerPoint 2010
This article lists changes in Microsoft PowerPoint 2010 since Microsoft Office PowerPoint 2007 and migration considerations. If you are upgrading from Microsoft Office PowerPoint 2003, see also Changes in Office PowerPoint 2007 ().
In this article:
• What’s new
• What’s changed
• What’s removed
• Migration considerations
What’s new
This section highlights new features in PowerPoint 2010.
Fluent UI
The PowerPoint 2010 user interface is updated from the Microsoft Office Fluent user interface (UI) that was introduced in the 2007 Microsoft Office system. The Microsoft Office Fluent UI is designed to make it easier for people to find and use the full range of features that Office applications provide, and to preserve an uncluttered workspace. For more information about the Fluent UI, see the resources in Microsoft Office Fluent User Interface Resource Center ().
The ribbon
The ribbon, part of the Fluent UI, was designed to optimize key PowerPoint presentation scenarios to make them easier to use. The ribbon provides quicker access to all the commands in PowerPoint 2010 and allows for easier future additions and customizations. You can also customize the ribbon. For example, you can create custom tabs and custom groups to contain frequently used commands. To help maximize the editing of your presentation space on the page, the ribbon can also be hidden while writing.
Backstage view
The Microsoft Office Backstage is now part of the Fluent UI and a companion feature to the ribbon. The Backstage view, which can be accessed from the File tab, helps you find frequently used features for managing your PowerPoint presentation files. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier release of Microsoft Office.) The Backstage view is used to manage files and the data about the files, such as creating and saving files, inspecting for hidden metadata or personal information, and setting file options.
File format
The PowerPoint 2010 file format enables new features such as sharing on the Web, linked presentation co-authoring, and versioning. PowerPoint 2010 will continue to work on Office PowerPoint 2007 presentations.
Protected View
Files from a potentially unsafe location (such as the Internet or an e-mail attachment) or files that contain active content (such as macros, data connections, or ActiveX controls) are validated and can open in Protected View. When you open files in Protected View mode, the editing functions are disabled. You can open and edit files from trusted sources by clicking Enable Editing. You can also explore data about the files in the Backstage view.
Collaboration and sharing features
PowerPoint 2010 supports simultaneous editing of presentations by multiple users. For example, a group of users can work on a presentation at the same time, or a single user can work on the same presentation from different computers at the same time, all without locking the file.
The changes are as follows:
• New content is automatically highlighted.
• Author information for any added or shared content is identified by a color-coded bar showing the author’s initials.
• Version support lets users see when and by whom changes were made to a presentation, and automatically highlights changes relative to earlier versions of the presentation.
• Faster synchronization of pages so that changes are displayed to all authors in near real-time.
Presentations to live and virtual audiences
PowerPoint 2010 has a remote slide show capability that lets you present a slide show over the Web or a network connection to virtual attendees or live attendees, or both.
Some common broadcast scenarios are as follows:
• Ad hoc one-on-one broadcast.
• Invite multiple viewers to view a presentation remotely at any time.
• Present a slide show to both live and remote attendees at the same time in the context of a training session, meeting, or conference call.
Working with text and objects
PowerPoint 2010 provides improved editing tools with a new set of Photo Effects that enable you to transform your images.
• Video and audio editing
• Graphics, transitions, and animations
• Help and translation
Top of page
What’s changed
This section summarizes the changes in PowerPoint 2010.
Arrange Group
The Arrange Group is now the Arrange menu.
Insert a shape
Previously, Drawing Tools (on the Format tab) automatically display when you insert a shape on a slide. This is no longer the case. The tab appears, but it does not open automatically. You can double-click the shape to bring up the tools.
Selection pane
The Selection pane is a feature that lists all objects in a presentation. In PowerPoint 2010 it is now located on the Arrange menu on the Home tab.
What’s removed
This section provides information about removed features in PowerPoint 2010.
Maximum sound file size
The audio/video link and embed feature has replaced the maximum sound file size embed feature. In Microsoft Office PowerPoint 2007, this appears in two locations: 1) as Max Sound File Size (KB) in Sound Tools | Options | Sound Options and 2) Link sounds with file size greater than in PowerPoint Options. This feature was necessary before because you were only able to embed of .wav files less than a certain size, as specified at one of the two places. In PowerPoint 2010, you can embed any file of any size so that these two features are no longer necessary.
The functionality is still there, but only as part of the new audio/video insertion behavior. The feature itself is deprecated.
You will not see Max Sound File Size (KB) in the ribbon and Link sounds with file size greater than in PowerPoint Options. Instead, the audio/video link and embed feature will replace this functionality. You will be able to do the same thing with fewer limitations and also do it directly when a media file is inserted.
In PowerPoint 2010, the user can choose whether to embed any file directly by using the Insert dialog box. Therefore, Max Sound File Size and Link sounds with files size greater than boxes are no longer needed. You can embed any file kind of any size instead of being limited to .wav files less than 50 MB.
Save as Web Page
The entry points for Save as Web Page have been removed.
Top of page
Migration considerations
This section provides information about features and changes that administrators should consider when migrating from Microsoft Office PowerPoint 2007 to Microsoft PowerPoint 2010.
PowerPoint Presentation Files (.ppt/.pptx)
The default file format for presentations created in PowerPoint 2010 has not changed from PowerPoint 2007, which is an XML-enabled file format. PowerPoint 2010 does not support saving to PowerPoint 95 (or earlier) file formats, nor Pack and Go Wizard (.ppz) files. For more information about new file formats in Office 2010, see File Formats supported in PowerPoint 2010 ().
To ensure that a presentation in PowerPoint 2010 can be viewed in PowerPoint 2003 or earlier versions, you can run the Compatibility Checker in PowerPoint 2010. The Compatibility Checker finds potential compatibility issues between PowerPoint 2010 and earlier versions of PowerPoint, and creates a report to help you resolve any issues.
With all the new media capabilities, photo effects, graphics, and formatting capabilities in PowerPoint 2010, knowing how they will translate when the file is opened in an earlier version is important. For example, the new photo effects are stored in the file in such a way that when you open the file in PowerPoint 2007, the photos that use the new effects look exactly as they did in PowerPoint 2010. However you cannot modify the effect if you return to PowerPoint 2007.
The new slide transitions are mapped to a PowerPoint 2007 transition when the presentation is viewed in PowerPoint 2007, and any improved slide transitions revert to the original look in PowerPoint 2007. Embedded videos will work to view in PowerPoint 2007, because PowerPoint 2007 Service Pack 2 was updated to include support for embedded videos. However, if you applied some PowerPoint 2010 effects to the video in PowerPoint 2010, such as crop it to a shape, apply 3-D to it, layer shapes, or apply a duotone, it will return to a default video and play without the special effects. The new slide transitions are mapped to a PowerPoint 2007 transition when the presentation is viewed in PowerPoint 2007, and any improved slide transitions revert to the original look in PowerPoint 2007. Embedded videos will work to view in PowerPoint 2007, because PowerPoint 2007 Service Pack 2 was updated to include support for embedded videos. However, if you applied some PowerPoint 2010 effects to the video in PowerPoint 2010, such as crop it to a shape, apply 3-D to it, layer shapes, or apply a duotone, it will return to a default video and play without the special effects.
For information about formatting compatibility with PowerPoint 2003 or earlier versions, see Features that change when you open a PowerPoint 2010 presentation in PowerPoint 2003 or earlier ().
Storing or sharing files
PowerPoint 2010 supports exporting files to all previous file formats that were found in PowerPoint 2007 and OpenDocumentation Presentations. In the Microsoft Office Backstage view, there is a quick-click sharing capability to send a presentation via e-mail as an attachment, as a link to the presentation on a Web server, or as a .pdf or .xps copy. You can also share the presentation via an instant message, in the Presentation Window, via Internet Fax, by publishing to Microsoft SharePoint 2010 Products or any specific location, or packaging it for a CD.
Presentation security
In Office PowerPoint 2007, new security features were introduced to help ensure that a presentation was safely managed after it left the user’s hands. In PowerPoint 2010, the permissions can still be set, but now through the Backstage view. Security features include the following:
• Prevent unintended changes to a final version of a document by using the Mark as Final command.
• Provide assurance as to the authenticity, integrity, and origin of the presentation by adding a digital signature.
• Assign permissions that prevent other users from copying, printing, or editing the presentation by selecting the access level specific to their requirements.
• Manage document properties through the Backstage view.
PowerPoint Viewer
The Viewer is not included with an installation of Office. Therefore, for users who require viewing a PPT/PPTX presentation offline, a new PowerPoint Viewer is available online. The Viewer lets you view presentations created in Microsoft PowerPoint 2000, PowerPoint 2002, PowerPoint 2003, PowerPoint 2007, and PowerPoint 2010. The Viewer also supports opening password-protected PowerPoint presentations.
The Viewer cannot be installed side-by-side with 64-bit Microsoft Office, and cannot open files created in PowerPoint 95 or earlier versions. Support is limited to Windows XP, Windows Server 2003, Windows Vista, and Windows 7. Windows 2000 and Windows 98 are not supported. Unlike previous viewers, users will have the option to use Reading mode or Full Screen Slide Show mode.
Macro recorder
The macro recorder, used to automate frequent tasks, is not available in PowerPoint 2010. Instead, you can use Microsoft Visual Basic for Applications (VBA) to create or configure macros. If you create a macro in a version of PowerPoint earlier than PowerPoint 2007 by using the macro reader, use VBA to configure the macro.
If you want to access developer controls, write code, or create macros, do the following to display the Developer tab:
1. Click the File tab.
2. Select Options.
3. In the PowerPoint Options dialog box, click Customize Ribbon.
4. In Customize the Ribbon, in the Main Tabs list, select the Developer tab, click Add, and then click OK.
The macro recorder, used to automate frequent tasks, is not available in PowerPoint 2010. Instead, you can use Microsoft Visual Basic for Applications (VBA) to create or configure macros. If you create a macro in a version of PowerPoint earlier than PowerPoint 2007 by using the macro reader, use VBA to configure the macro.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ().
See Also
Changes in Office 2010
System requirements for Office 2010
Changes in Project 2010
This article lists changes in Microsoft Project 2010 since Microsoft Office Project 2007 and migration considerations.
In this article:
What’s new
What’s changed
What’s removed
Migration considerations
What’s new
This section highlights new features in Project 2010.
Fluent UI
The Project 2010 user interface is redesigned and now uses the Microsoft Office Fluent user interface (UI). Introduced in the 2007 Microsoft Office system, the Fluent UI is designed to make it easier for people to find and use the full range of features that Office applications provide, and to preserve an uncluttered workspace. For more information about the Fluent UI, see the resources in Microsoft Office Fluent User Interface Resource Center ().
Backstage view
The Microsoft Office Backstage is part of the Fluent UI and a companion feature to the ribbon. The Backstage view, which can be accessed from the File tab, helps you find frequently used features for managing your Microsoft Project files. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier releases of Microsoft Office.) The Backstage is used to manage Microsoft Project Server connections, and to check out and publish projects.
Team Planner
Project 2010 Professional contains the Team Planner, a resource scheduling view that lets users see at a glance what their team members are working on and move tasks from one person to another. Users can also view and assign unassigned work, view over-allocations, and see task names and resource names.
Synchronization with SharePoint lists
In Project 2010 Professional, users can export project files to a list in Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010. This provides a quick and easy way for a project manager to share status or create reports that can be viewed across the organization. Project Web Access (PWA) is not required to synchronize with a SharePoint list.
Manual scheduling
Project 2010 changes how projects are scheduled. Factors such as task dependencies and the project calendar no longer automatically adjust task dates when a task is manually scheduled. This feature can be especially useful for early planning when the duration of a task might not yet be known. Users can place a manually scheduled task anywhere in their schedules, and Project 2010 will not move it. Project managers who are accustomed to automatic scheduling with past versions of Project can turn the new manual scheduling feature off for specific tasks or the entire project. Some projects may require the powerful scheduling engine of Project to handle scheduling.
Placeholder tasks
Placeholder tasks let users create a plan by using task names only. Users can enter any combination of start date, finish date, and duration and fill in the rest later.
Inactive tasks
Users can make tasks inactive and still keep them in their projects. The main value of this feature is that custom field information, resource assignments, and all other data stays in the task. (Note that these factors do not contribute to roll-ups.)Inactive tasks often have important information (such as cost information) that can be valuable for archival purposes and what-if planning.
Top-down summary
Creating subtasks and then rolling them up into summary tasks is no longer restricted. In Project 2010, users can create summary tasks first, and the summary tasks can have dates that do not exactly match the roll-up dates of the subtasks. At the beginning of the planning phase, users might only have some high-level information about key deliverables and major milestones of their projects. In Project 2010, users can divide projects into high-level phases based on the overall timeline and budget. This means that it is not necessary for dates of individual work items to line up exactly with dates of the high-level phases.
Compare projects
The compare projects feature in Project 2010 now includes Gantt bars to help users see more clearly how one version of a project differs from another version.
Timeline
Project 2010 now includes a timeline view. For new files, the timeline view is automatically displayed above most other views. This shows a concise overview of the entire schedule. Otherwise, users can turn on the timeline view manually. Users can add tasks to the timeline, print it, or paste it into an e-mail message for an easy-to-view project summary.
Enhanced copy and paste
This feature lets users copy and paste content between Microsoft Office programs and Project 2010, and keep formatting, outline levels, and column headers.
Excel-like features
Features similar to those in Microsoft Excel are available in Project 2010. This includes the following:
• Simplified adding of new columns. A user can click the Add New Column heading at the right end of a sheet view, and then type or select the name of a new or existing column. An existing column can also be quickly renamed by clicking its title and typing a different column name.
• Enhanced filter UI makes it easier for users to find tasks and resources.
• 32-bit color support and text wrapping enable users to create views that are similar to Excel reports.
Find commonly used commands quickly
The most commonly used commands can now be found easily. By right-clicking any item in a view, such as bar, table cell, or chart, a mini-toolbar with a quick list of commonly used commands is displayed.
The view slider
In Project 2010, users can quickly zoom in and out of the time phased section of a view by using a slider in the status bar. Move the view slider to the right to zoom in a schedule and move the slider to the left to zoom out. The view slider works in the Gantt chart, network diagram, calendar, and all graph views.
Backwards compatibility
Project 2010 is compatible with previous versions of Microsoft Project.
Users can create files in Office Project 2007 or earlier and then open and edit them in Project 2010, although certain features of Project 2010 are not enabled. If you save the earlier version files in the Project 2010 format, all Project 2010 is available.
In addition, you can create files in Project 2010 and then convert them to the Office Project 2007, Project 2000, and Project 2003 file formats.
What’s changed
This section summarizes the feature changes in Project 2010.
Application settings
The following dialog boxes contain features that are changed:
• Spelling options
• Customize
• Service options
• Options
What’s removed
This section provides information about removed features in Project 2010.
Custom forms
The ability to create and use custom forms through the user interface (Tools | Customize | Forms) is removed in Project 2010. If users previously created custom forms in their application, the forms can no longer be accessed.
This is an outdated and rarely used feature. The amount of effort required to maintain the feature (for example, updating the controls to be compatible with Project 2010) is not feasible. Use Microsoft Visual Basic for Applications (VBA) to create custom forms that replace the previously created forms. Customers usually use VBA, Visual Studio Tools for Office (VSTO), or other methods to perform the same task.
OWC resource availability graphs
Because OWC is removed in Microsoft Office 2010, resource availability graphs have changed in Project 2010, and users can no longer see proposed availability on the selected task without temporarily assigning a resource to the task. In addition, users lose the split when they select to see the graph, can no longer graph multiple resources together (you must do this one at a time), and do not see numbers next to the graph saying how high the bars are. The team builder experience is also different from the assign resource experience. Team builder starts PWA, and the assigned resource uses resource graphs in Project 2010. The new graphs are customizable and are now printable.
Add-ins, sample macros, and project guide
Add-ins, sample macros, and sample project guide are not included with Project 2010.
The following add-ins are incorporated into Project 2010:
• Compare Project Versions
• Adjust Dates
The following add-ins are removed:
• Pert Analysis
• Copy picture (no longer automatically creates an Office document and cannot export to the JPG format)
• Format_Duration
• ResMgmt_TaskEntry
• Rollup_Formatting
• Toggle_Read_only
• Update_File
Save as Excel Pivot Table
Save as Excel Pivot Table is replaced by Desktop Reports in Project 2010, Professional and Standard.
The ability to save directly into a pivot table is removed.
The File | Save As menu used to include the following:
• Save as XLS
• Save as XLS Pivot Table
The File | Save As menu now includes the following:
• Save as XLS
• Save as XLSX
• Save as XLSB
Project 2010 now supports the new file formats in Microsoft Excel 2010. Users should use desktop reports to generate a normalized version of their tasks in Excel 2010.
Migration considerations
When planning a migration to Project 2010, review what is new, changed, and removed for Project 2010.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ().
Changes in Publisher 2010
This article lists changes in Microsoft Publisher 2010 since Microsoft Office Publisher 2007 and migration considerations.
In this article:
• What’s new
• What’s changed
• What’s removed
• Migration considerations
What’s new
This section highlights new features in Publisher 2010.
The ribbon
The ribbon, part of the Microsoft Office Fluent user interface (UI), was designed to optimize key Publisher scenarios to make them easier to use. The ribbon in Publisher 2010 provides quicker access to all the commands and allows for easier future additions and customizations. You can also customize the ribbon. For example, you can create custom tabs and custom groups to contain frequently used commands. To help maximize the note-taking space on the page, the ribbon can also be hidden while writing.
Backstage view
The Microsoft Office Backstage is part of the Fluent UI and a companion feature to the ribbon. The Backstage view, which can be accessed from the File tab, helps you find frequently used features for managing your Publisher 2010 files. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier releases of Microsoft Office.) The Backstage is used to manage files and the data about the files, such as creating and saving files, inspecting for hidden metadata or personal information, and setting file options.
Simplified, cleaner workspace
In the new workspace, users will see object boundaries only when they want them (for example, when they pause on or select an object), and alignment guides when they need them (for example, as they drag an object). Users can also move from page to page quickly by using the new page navigation pane, which displays single-page or double-page thumbnails.
[pic]Note:
The ribbon and the Backstage view are features of the Microsoft Office Fluent user interface, which is a feature of Microsoft Office 2010 applications. This it easier for users to find and use Office 2010 features. For more information about the Microsoft Office Fluent user interface, see Microsoft Office Fluent User Interface Resource Center ().
Integrated print and preview experience
Print and Print Preview are integrated so that it is easier for users to get a more accurate view of what their publications will look like when they are printed. This includes the ability to make print adjustments while viewing the effect of the changes in a large preview of their publication. Users can view multiple pages at the same time, view page boundaries, page numbers, and sheet rulers while in print preview, and even view a simulation of a two-sided document as if it were held up to a light — to see the front and back at the same time, as the publication will look when printed.
Save file as .pdf or .xps
Users can save files in the .pdf or .xps file format. This feature can be blocked by using Group Policy. Also, .pdf files can be password-protected for an added layer of security.
64-bit edition
Publisher 2010 64-bit edition can be installed on Windows 64-bit operating systems, and is backward-compatible with other versions of Publisher. Users can open, edit, and save any Publisher 2003, Office Publisher 2007, Publisher 2010 32-bit edition, or Publisher 2010 64-bit edition file on a computer that is running either a 32-bit or 64-bit Windows operating system. For more information, see 64-bit editions of Office 2010.
What’s changed
This section summarizes the feature changes in Publisher 2010.
Improved picture technology
Users can more easily work with pictures in their publications with the following picture technology improvements:
• Cropping Users can rotate and resize pictures, crop them into non-rectangular shapes, and preview the images while keeping the picture in the desired size, shape, and location.
• Replacing pictures Users can replace pictures by drag-and-drop, swap two pictures in a single operation, and paste pictures copied outside from Publisher into a placeholder in Publisher.
• Using picture placeholders Users can maintain placeholder dimensions when a picture is inserted. For example, pictures either too small or too large for a placeholder are automatically resized.
• Add captions Users can now add captions to their pictures, choosing from a gallery of caption designs and layouts, and make changes easily.
Object alignment
Users can use visual alignment guides to align objects to other objects or text, but can ultimately determine where they want to place their objects. This includes the ability to offset-align an object.
Improved access to templates and building blocks online
Users can use templates and insert building blocks of content (for example, mastheads, borders, and graphics) to create professional-looking pages. Publisher 2010 makes it easier for users to access the Publisher online community to get pre-built templates and building blocks, and share ones they create.
Catalog merge
Catalog merge, which lets users merge text and images from a database (such as Microsoft Excel, Microsoft Access, or Microsoft Outlook) is more easily accessed through the UI. Users will be able to initiate catalog merge at any point while making their publications.
What’s removed
This section provides information about removed features in Publisher 2010.
Web mode
Creating new Web sites and Web publications is not available in Publisher 2010. However, users can still edit Web publications created in an earlier version of Publisher. Publisher 2010 does not display a folder of Web site templates, or a user interface access point to change a publication to Web mode. However, users see a Web mode tab when they open a Web publication created in an earlier version of Publisher.
Outdated application settings
Users no longer have access to several settings that were available in Tools | Options. This includes changes to the following dialog boxes: Spelling options, Customize, Service options, and several tabs in Options. This also includes removal of or changes to the following in Settings: Show basic colors in color palette, Show TipPages + Reset Tips button, Show underline for merge fields and business information fields, Automatically synchronize formatting, and Use a wizard for blank publications.
Migration considerations
When planning a migration to Publisher 2010, review what is new, changed and removed for Publisher 2010.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ().
See Also
Changes in Office 2010
Changes in SharePoint Designer 2010
This article lists changes in Microsoft SharePoint Designer 2010 since Microsoft Office SharePoint Designer 2007.
In this article:
What’s removed
What’s removed
This section provides information about removed features in SharePoint Designer 2010.
Contributor Settings
In Office SharePoint Designer 2007, Contributor Settings was used to configure and enable Contributor mode, a limited access mode. Users who opened a site for editing in Office SharePoint Designer 2007 had access to different commands or features, depending on which Contributor group they were assigned to and which editing restrictions had been assigned to that Contributor group. Contributor Settings worked at the site level, and the settings could not be inherited by any subsites of a parent site. Contributor Settings was not a security feature, it was designed to be used in an environment where site managers were confident of the intentions of the users and was intended to help prevent accidental changes to a Web site.
Contributor Settings is removed in Microsoft SharePoint Designer 2010 because the feature was complicated, underused, and did not integrate well with the SharePoint Products and Technologies permission model, because users could bypass the restrictions imposed by the feature. The functionality is replaced by a mix of reliance on the SharePoint Products and Technologies permission model and the SharePoint Role Designer feature.
Database features
The database features in Microsoft FrontPage and Office SharePoint Designer 2007 do not apply to SharePoint Product and Technologies Web sites and are not supported in Microsoft SharePoint Designer 2010. The features that are removed in Microsoft SharePoint Designer 2010 include the following:
• Database Interface Wizard Creates a new database-driven Web site in Office SharePoint Designer 2007.
• Database Results Wizard Creates Web pages that contain the database results Web component, also known as a WebBot, in Office SharePoint Designer 2007. SharePoint Designer 2010 does not support the Database Results WebBot. When you view a Web page or if you use Design view in SharePoint Designer 2010 to open an existing database results page, the Database Results WebBot is rendered as an HTML comment.
• Database tab of the Site settings dialog box Manages database connection settings in Office SharePoint Designer 2007.
Layout tables
In Office FrontPage 2003 and Office SharePoint Designer 2007, you could create Web page layouts by using layout tables and cells. A layout table is the framework you create for a page layout. Layout cells are the regions within that framework that contain the content in a page, including text, images, Web parts, and other elements. Together, layout tables and cells represent horizontal and vertical regions that users can add to Web pages, which provide visual structure for your content.
CSS layout features have replaced the layout tables feature in Microsoft SharePoint Designer 2010, and the extensive HTML comments that layout tables rely on are not recognized. If you open a Web page that contains an existing layout table in SharePoint Designer 2010, the layout table functions correctly. However, you cannot use SharePoint Designer 2010 to insert a new layout table.
Microsoft Script Editor (MSE)
In Office SharePoint Designer 2007 and previous versions of Microsoft FrontPage, you could use the Microsoft Script Editor (MSE) to add text, edit HTML tags, and edit any Microsoft Visual Basic Scripting Edition (VBScript) code in a data access page. MSE also provided IntelliSense features for script creation and editing. You could also use the Script Editor to view your page as it would appear in a Web browser. Microsoft SharePoint Designer 2010 does not include Microsoft Script Editor.
Publish, backup, and restore remote Web site
SharePoint Designer 2010 is designed for users to work on — instead of designing and publishing — SharePoint Products and Technologies Web sites. In contrast, Microsoft FrontPage was designed as a server-agnostic Web site creation and management tool. Legacy features for publishing and connecting to remote Web sites and managing the transfer of Web sites and Web content are removed in SharePoint Designer 2010.
SharePoint Designer 2010 is not designed to take the place of server administration tasks such as backup or restore. Operations — such as backup, restore, content migration, and other management tasks that affect entire SharePoint Products and Technologies Web sites — should be completed by using the Central Administration Web page.
Back up a Web site
SharePoint Designer 2010 is designed to work with content on an existing SharePoint Products and Technologies Web site. To back up a Web site, an administrator for the SharePoint Products and Technologies Web site uses the Central Administration Web site for the collection.
Restore a Web site
SharePoint Designer 2010 is designed to work with content on an existing SharePoint Products and Technologies Web site. To restore a Web site, an administrator for the SharePoint Products and Technologies Web site uses the Central Administration Web site for the collection.
FTP
FrontPage provided a built-in FTP client for connecting to servers without Microsoft FrontPage server extensions. The built-in FTP client enabled users to open sites over FTP and then publish an entire Web site or manage individual files on the remote Web server. Because SharePoint Designer 2010 is designed for working with SharePoint Products and Technologies Web sites, and these servers already have the necessary underlying code installed, an FTP client is not required and is removed.
Import Web site wizard
SharePoint Designer 2010 is designed to work with content on an existing SharePoint Products and Technologies Web site. Therefore, the ability to import a Web site from another server or from a file location is removed.
Publish Web site
SharePoint Designer 2010 is designed to work with content on a SharePoint Products and Technologies Web site. Therefore, the ability to create, edit, or publish a disk-based Web site and work with remote Web sites is removed. Unlike SharePoint Designer 2010, Office SharePoint Designer 2007 did support disk-based Web sites. When you edited Web pages from a Web site folder, metadata such as your logon name was saved for each file edited and used to display the author information, such as Created by or Modified by, for files in the Office SharePoint Designer 2007Web Site views and File Properties dialog box. By clearing the Manage the Web site using Office SharePoint Designer 2007 metadata files check box in the Site Settings dialog box, you could choose to remove the metadata from the Web site folder on your local computer. Because the ability to open and work with disk-based Web sites is removed, this privacy concern does not apply to SharePoint Designer 2010.
Web package
A Web package can contain Web pages, templates, Web components, themes, graphics, style sheets, and other elements. Web packages are CAB files (with .fwp file name extensions) that you use to import or export from a Web site. When working with a SharePoint Products and Technologies Web site, SharePoint Designer 2010 provides direct access to importing or exporting Web packages. SharePoint Designer 2010 does not import Web package files.
There are two alternative methods that we recommend to deploy packaged functionality when you are working with a SharePoint Products and Technologies Web site. The first method is that you can use a custom site template. Custom site templates are stored as an .stp file in the SharePoint database. Second, you can use the Windows SharePoint Services solution framework. You can use solutions to package and deploy custom features, site definitions, templates, Web parts, and assemblies. The Windows SharePoint Services solution framework lets you bundle all the components for extending Windows SharePoint Services in a solution file. A solution file is a cabinet format file but it has a .wsp extension. A solution is a deployable, reusable package that contains a set of features, site definitions, and assemblies that apply to sites, and that you can individually enable or disable. You can use the solution file to deploy the contents of a Web Part package. This includes assemblies, class resources, .dwp files, and other package components.
Views
Views in FrontPage and Office SharePoint Designer 2007 offered various ways to view the files and edit Web pages in your Web site. Each view offered its own advantages for performing Web site creation, editing, maintenance, and management tasks. SharePoint Designer 2010 includes changes to the Reports, Navigation, and Hyperlinks views.
Reports view
In Office SharePoint Designer 2007, Reports view enables you to run reports for information such as the number and kind of images on your page, broken or outdated hyperlinks, or pages that might be slow to load. In FrontPage and Office SharePoint Designer 2007, Reports view provides access to statistics that let you monitor all aspects of your Web site. You can examine detailed information about the performance of your Web site and also information about your visitors. You can also use the reports to find and fix many common problems, keep track of the development on your Web site, and continue to improve and tailor your Web site to enhance the user experience.
SharePoint Designer 2010 changes the way that you access reports and has removed those reports that are not useful in a SharePoint Products and Technologies Web site.
Navigation view
In FrontPage or Office SharePoint Designer 2007, the Navigation view provides an overhead look at the navigation structure of your Web site and shows the Web pages that are a part of the navigation structure of the Web site as a flowchart. The Navigation view and Navigation task pane do not work well with SharePoint Products and Technologies Web sites and have been replaced by new features such as site navigation and the quick launch bar.
Hyperlinks view
Hyperlinks view provides a visual representation of all the hyperlinks related to a specific Web page in a Web site. When you select a Web page in the hyperlinks view, all the other Web pages in that Web site that contain hyperlinks that connect to the selected Web page are displayed, and a line connects the Web pages. Along with displaying these hyperlinks, the hyperlinks from the Web page to any resource — image, Web page, or other object — is displayed together with an indication of the link validity.
The Hyperlinks view is removed from SharePoint Designer 2010, because this approach to hyperlinks is not useful in a SharePoint Products and Technologies Web site. The error checking features in SharePoint Designer 2010 let you check for broken links, unused pages, cascading style sheets usage, and master page usage.
Changes in SharePoint Workspace 2010
This article lists changes in Microsoft SharePoint Workspace 2010 since Microsoft Office Groove 2007.
• What’s new
• What’s changed
• What’s removed
• Migration considerations
What’s new
This section highlights new features in SharePoint Workspace 2010 and succeeds Office Groove 2007.
SharePoint integration
SharePoint Workspace 2010 enables SharePoint Server 2010 users to create a personal SharePoint workspace, which is a local, synchronized cache of document and list content on a SharePoint site. This feature allows information workers who have access to a SharePoint site to easily access and contribute to SharePoint document libraries and lists from offline locations and when they are working online.
SharePoint Workspace user interface
The appearance and behavior of the Fluent user interface (UI) in SharePoint Workspace 2010 is optimized for familiarity to SharePoint users.
What’s changed
This section summarizes the feature changes in SharePoint Workspace 2010.
SharePoint Workspace product
The Groove client application is now the Microsoft SharePoint Workspace client application. Like Office Groove 2007, SharePoint Workspace 2010 enables users to create a local, synchronized cache of document content on a SharePoint site. However, in SharePoint Workspace this is achieved by creating a personal, synchronized SharePoint workspace instead of using a Connect tool as in Office Groove 2007. Like Office Groove 2007, SharePoint Workspace 2010 enables users to create Groove workspaces and shared folders. The appearance and behavior of the SharePoint Workspace 2010 user interface is updated for more continuity with SharePoint team spaces.
Tools location
The list of tools in SharePoint Workspace 2010 has moved from the horizontal tab arrangement in the lower part of Workspace Explorer to a vertical arrangement on the File tab. Reordering tools by dragging them to a new location in the UI is no longer supported. However, users can now decide to order tools by type or alphabetically. This change makes tools more visible to users.
Groove logon password and smartcard
To improve consistency with other Microsoft Office 2010 applications, SharePoint Workspace 2010 has changed its security approach from a Groove-specific logon password and smartcards to Windows logon credentials. Elimination of the Groove-specific logon credentials helps provide a more secure and manageable environment. When users log on to SharePoint Workspace 2010, a message appears indicates that a Groove password or smartcard is no longer required for logging on to Groove and that accounts will be protected by using their Windows logon credentials. This notification is a new feature.
Logon credentials
SharePoint Workspace 2010 relies on user credentials from the server operating system instead of a set of SharePoint Workspace 2010 dedicated logon credentials. Due to this change, some logon-related features are removed, as described in Logon-related features.
Workspace Manager
Workspace Manager is a feature that gives SharePoint Workspace users a list of all their workspaces. This includes the workspace type, status information, and the last unread date and time. In SharePoint Workspace 2010, the Workspace Manager no longer exists as separate feature because the Launchbar provides comparable functionality.
What’s removed
This section provides information about removed features in SharePoint Workspace 2010. The following Office Groove 2007 capabilities are not supported in SharePoint Workspace 2010, usually because the capability is unnecessary, or to avoid confusion with or duplication of similar functionality that is provided by another application.
Alerts on contacts
The option to set an alert on specific SharePoint Workspace contacts to indicate their online presence in a workspace is removed. Alerts that were set on contacts in Microsoft Office Groove 2007 do not appear in SharePoint Workspace 2010. Instead of setting an alert on a contact, SharePoint Workspace 2010 users can use Microsoft Communicator to “tag” the contact.
E-mail invitation
Support of the mailto protocol for sending Groove workspace invitations and contact information through e-mail clients other than Microsoft Outlook 2010 is removed in SharePoint Workspace 2010. The Send e-mail invitations using Microsoft Outlook check box is removed from the Preferences dialog box. Users who have Outlook 2010 as their e-mail client will not be affected by this change. However, users who have other e-mail clients or instant messaging applications must copy the invitation and paste it into the message. Limitations of the mailto protocol prevented it from working correctly for all languages and from providing the internationalization support that users required.
Groove Forms Designer
The Groove Forms Designer is removed in SharePoint Workspace 2010. The Groove Forms Designer functionality is replaced by the Lists tool, which includes a designer capability that lets developers import Microsoft InfoPath 2010 form templates. When Office Groove 2007 users upgrade to SharePoint Workspace 2010, the forms in existing Groove workspaces will work as expected. Application developers must use a Office Groove 2007 client installation to maintain or modify legacy custom forms in existing Groove workspaces.
Groove InfoPath Forms
The Groove InfoPath Forms Designer is removed in SharePoint Workspace 2010. After upgrading, the forms in existing Groove workspaces will work as expected. We recommend that you use Microsoft InfoPath 2010 to edit or create forms. SharePoint Workspace 2010 users can import new forms that are created in InfoPath 2010 into a Groove workspace.
Custom tools
The tool set feature is removed in SharePoint Workspace 2010. SharePoint Workspace users cannot add a custom tool or create custom groupings of tools. In Office Groove 2007, a user could find the Custom Tool option in the Add tool dialog box.
Groove Workspace Explorer contact list
The area of the SharePoint Workspace 2010 Workspace Explorer that contains tools and lists and the ability to display a contact list as part of Workspace Explorer is not available. The functionality of working with contacts is otherwise unchanged and users can continue to work with contacts on the Launchbar.
Groove Workspace Explorer workspace list
The area of SharePoint Workspace 2010 Workspace Explorer that contains tools and lists and the ability to display a workspace list as part of Workspace Explorer is not available. The functionality of working with a workspace is otherwise unchanged and users can continue to work with workspaces on the Launchbar.
Lite Chat invitations
Microsoft Communicator is integrated into Office 2010. Because Communicator supports multiuser chat, support for Lite Chat invitations in SharePoint Workspace 2010 is removed as a redundant feature.
Connect tool
SharePoint Workspace enables users to create a local, synchronized cache of document content on a SharePoint site through a personal, synchronized SharePoint workspace. This process replaces the Office Groove 2007 Connect tool. Therefore, the Connect tool is removed.
Navigate Together feature
The Navigate Together feature, which can be accessed through the Options menu, is removed in SharePoint Workspace 2010. By using this feature, one person could navigate through the UI and then have all users who were in Navigate Together mode navigate through the workspace UI together. In SharePoint Workspace 2010, users who need to move through the UI with other users must coordinate directly with the other users during the session, either by telephone or by instant messaging.
Communicator
The Windows API-based Microsoft Communicator integration is removed in Microsoft SharePoint Workspace 2010 because Microsoft Office-based integration replaces it. This provides a richer, more robust, and more consistent experience across all Office 2010 applications. Users can see information and actions available on SharePoint Workspace 2010 contacts.
Suspended icon overlay
When members are suspended in a Office Groove 2007 workspace, their contact name is marked with a Suspended icon and they are grouped under a Suspended heading in a member's lists. In SharePoint Workspace 2010, the Suspended icon is removed and suspended users are grouped under a Suspended heading only if the Members pane is sorted by status.
Tooltip information about user entering tool
In Office Groove 2007, every time that a user enters a tool in any workspace, every user receives a ScreenTip: " has entered ". To improve performance and to minimize the distraction that users experience, especially in workspaces with many members, this ScreenTip notification functionality is removed in SharePoint Workspace 2010. Users can still use the numbered presence indicator on the tool name to see the names of the users in a tool.
Multiple identities
In Office Groove 2007, a user could create multiple identities within a single account. This feature was sometimes confusing for users. Therefore, the ability to create multiple identities for an account is removed in SharePoint Workspace 2010. SharePoint Workspace 2010 supports one account for one identity only. If existing Office Groove 2007 accounts have multiple identities, upon upgrade, those identities are maintained as part of the account. Note that the ability to create multiple accounts is still supported.
Push-to-talk and voice memos
Office Groove 2007 provided a button UI that users could click to converse by voice over IP. This functionality was not always effective and rarely used. Therefore, it is removed in SharePoint Workspace 2010. Similarly, Office Groove 2007 voice memos that could be attached to an instant message are removed in SharePoint Workspace 2010.
Ink chat
The Office Groove 2007 chat capability provided Ink mode options that let users draw chat entries by dragging with the mouse. Ink mode options were not of prime importance to most users and do not exist in SharePoint Workspace 2010.
Logon-related features
SharePoint Workspace 2010 relies on user credentials from the server operating system instead of a set of SharePoint Workspace 2010 dedicated logon credentials. Because of this change, the following three logon-related features are removed:
• Manual Fingerprint-Based Logon Credentials Reset This feature let an administrator use a temporary digital fingerprint to manually authenticate a user before the user resets credentials. We recommend that administrators use the e-mail-based password reset functionality instead.
• Partial Data Recovery This capability gave an administrator limited access to SharePoint Workspace data for a user without needing to impersonate the user. This functionality does not exist in SharePoint Workspace 2010 because other methods are available to administrators to recover SharePoint Workspace data for a user. For example, with single sign-on (SSO), when the user or an administrator is logged on they can access the user’s SharePoint Workspace data. If users need to limit access to SharePoint Workspace data, they can choose to configure their operating system to prevent administrators from accessing user DPAPI keys and disabling Groove Account-Access. If users choose to follow this approach and a key is lost, this configuration makes recovering the user SharePoint Workspace data more difficult.
• Data Recovery Admin This is a stand-alone client tool that worked together with the Partial Data Recovery feature to recover the space data or to reset a password for a user. Because Partial Data Recovery is removed, the Data Recovery Admin tool is no longer required.
Migration considerations
If you are migrating from Office Groove 2007 to SharePoint Workspace 2010 and you want to maintain legacy custom forms, note that application developers must use a Office Groove 2007 client installation to maintain or modify custom forms in existing Groove workspaces. Forms Designer functionality is replaced by the Lists tool, as mentioned earlier in this article.
See Also
Deploy SharePoint Workspace 2010
Changes in Visio 2010
This article lists changes in Microsoft Visio 2010 since Microsoft Office Visio 2007 and migration considerations. If you are upgrading from Microsoft Office Visio 2003, see also Changes in Office Visio 2007 ().
In this article:
• What’s new
• What’s changed
• What’s removed
• Migration considerations
What’s new
This section highlights new features in Visio 2010.
Fluent UI
The Visio 2010 user interface is redesigned and now uses the Microsoft Office Fluent user interface (UI). First introduced in the 2007 Microsoft Office system, the Fluent UI is designed to make it easier for people to find and use the full range of features that Office applications provide, and to preserve an uncluttered workspace. For more information about the Fluent UI, see the resources in Microsoft Office Fluent User Interface Resource Center ().
The ribbon
The ribbon, part of the Fluent UI, was designed to optimize key Visio design scenarios to make them easier to use. The ribbon provides quicker access to all the commands in Visio 2010 and allows for easier future additions and customizations. You can also customize the ribbon. For example, you can create custom tabs and custom groups to contain frequently used commands. To help maximize the editing of your presentation space on the page, the ribbon can also be hidden while you write. All existing Visio Software Development Kit (SDK) sample applications will be changed to use the RibbonX extensibility framework.
Backstage view
The Microsoft Office Backstage is part of the Fluent UI and a companion feature to the ribbon. The Backstage view, which can be accessed from the File tab, helps you find frequently used features for managing your Visio drawings. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier release of Microsoft Office.) The Backstage view is used to manage files and the data about the files, such as creating and saving files, inspecting for hidden metadata or personal information, and setting file options.
ShapeSheet IntelliSense
If you are new to ShapeSheet formulas in Visio, they are similar to the formulas in Excel, except you can use them to program and recalculate shapes. A ShapeSheet spreadsheet stores information for every Visio shape. Within a ShapeSheet, formulas from previous versions of Visio are still valid.
The IntelliSense is new to Visio 2010. This feature does an automatic lookup and auto-complete for formulas.
Some of the benefits of ShapeSheet IntelliSense are as follows:
• Keyword lookup
• Keyword auto-complete
• Keyword definition pop-up
• Function signature hints pop-up
• Parenthesis matching
• Multi-line formula input for developers
• Supports local and cross-sheet references
Top of page
What’s changed
This section summarizes the changes in Visio 2010.
Status bar
The following status items are removed from the status bar in Visio 2010, but still appear in the Size & Position window:
• X
• Y
• Begin X
• Begin Y
• End X
• End Y
Customize ink pens
The Customize Pens dialog box is removed in Visio 2010 and replaced with the new Pens model that is used by OfficeArt and OneNote. Visio 2010 no longer persists settings for five distinct pens in the registry. Users can no longer see an entry point for the Customize Pens dialog box or access the dialog box by any means. Instead, users can customize ink pen properties by using the controls on the Ink Tools tab.
Color by Value
The Color By Value add-on no longer functions in Visio 2010. It is replaced by the Data Graphics feature set, which provides more functionality. You can no longer see the Color By Value add-on in the Add-Ons hierarchical control. Shapes no longer contain right-click actions to open the add-on. Object model calls from shapes that invoke the legacy Color By Value add-on result in an alert about the new Data Graphics functionality and a suggestion to view the Data Graphics Help files.
Visual Studio Add-in/Add-on Wizard
The Visual Studio Add-in/Add-on wizard, which is included with the Visio 2010 SDK, was changed from the earlier version. The wizard in Visio 2010 SDK creates Visio add-on projects, but no longer creates add-in projects. Wizard support for Visio 2010 VSTO add-in projects is available natively in Microsoft Visual Studio 2010.
What’s removed
This section provides information about removed features in Visio 2010.
ShapeStudio
The ShapeStudio tool available in previous versions of the Visio SDK has been removed from the Visio 2010 SDK.
Status bar
The following status items are removed from the status bar in Visio 2010:
• Begin
• End
• Dx
• Dy
• Snap
• Top
• Bottom
• Left
• Right
• Tile
• Tile Row
• Tile Column
• Ancestor
The status bar in the Fluent UI focuses on higher priority status items, many of which have the added utility of being actionable.
Find Shape feature
The Find Shape server feature previously available in Visio enabled users to search for shapes installed on Microsoft Web sites. Additional, new, and updated shapes were then made available together with those already on the local computer.
The Find Shape feature no longer connects to the Internet to look for additional Visio shapes as did in previous versions. The Find Shape feature no longer connects to additional Web servers that an administrator might have set up to host additional shapes. Instead, users must download the content from Office Online. Users can access download instructions by using the Find Shapes Online command on the More Shapes menus.
With this change, the Find Shape feature will display search results found only on the local computer.
In Visio 2010, the user can toggle the user interface on and off by using the Search for Shapes toggle available on the More Shapes menu.
Stencil docking
The redesign of the Shapes Window in Visio 2010 is now optimized for the vertical orientation of the window. Therefore, in Visio 2010, stencils are docked on the left or right of the Shapes Window with docking in the top and bottom positions no longer allowed.
Top of page
Migration considerations
This section provides information about features and changes that administrators should consider when migrating from Microsoft Office Visio 2007 to Microsoft Visio 2010. A noticeable change is that Visio has joined the rest of the Microsoft Office products design and uses the Microsoft Office Fluent user interface (UI). In Visio 2010, you navigate the features by using the ribbon, the Quick Access Toolbar, and the Microsoft Office Backstage view.
Process Repository
In Visio 2010, you can easily manage collections of process diagrams that are typically stored on network file shares. You can ensure that you are editing the most recent version and updating a user if any changes were made to the process diagrams. For many administrators and managers who supervise these document repositories, ensuring diagrams comply with internal standards and tracking all the processes involved can be overwhelming. The Visio Process Repository, a new site template that is included with Microsoft SharePoint Server 2010, uses the collaborative features in SharePoint Server 2010, including:
• Check in/Check out
• Versioning
• Workflow
These features integrate with several new process management features in Visio 2010. The result is that, in a few clicks, a SharePoint administrator can create a Visio Process Repository that is preconfigured for easy storage and management of Visio process diagrams. A Repository site contains a library for documentation, a task list, and a discussion board. The Process Diagrams document library is designed to store processes and comes prepopulated with several templates that can be used to create new process diagrams.
Publish a process diagram to a repository
You can check a diagram for validation issues prior to publishing by using the Validation feature. When you are ready, you can save the document back to the repository by using the Save to SharePoint billboard in the Backstage view. To save a document to the repository, follow these steps:
1. In the Backstage view, click the File tab.
2. Click Save & Send.
3. Under Save & Send, click Save to SharePoint.
4. Select the desired Process Diagrams document library and file type.
5. Click Save As to save the document.
6. The process diagram will be listed in the Process Diagrams document library at this point. The document library has two special columns:
a. Keywords This column displays the swim-lane headings of each cross-functional flowchart in the document library.
b. Category This column displays the validation status of each document. When used with the Diagram Validation feature in Visio 2010, it is easier for administrators and managers to monitor whether the processes in the repository meet their organization’s standards.
Because the Process Repository is built on top of SharePoint Server 2010, you can take advantage of other SharePoint features. For example, you can:
• Set up workflows.
• Set up automatic e-mail notifications when documents change.
• View revision history for a given document.
• Visio Services in SharePoint Server 2010 is a service application that lets users view the processes in a browser with one click, even if they do not have Visio installed on their computers. For more information, see Visio Services overview (SharePoint Server 2010) ().
Visio Viewer
Visio Viewer 2002 and Visio Viewer 2003 have been discontinued. If you use Visio Viewer 2007, ensure that you have the latest upgrades or you can move to the Visio 2010 (Beta) Viewer. The Visio 2010 Viewer has all the functionality of the previous viewers, and includes all the security fixes. If you do not want to update to the Visio 2010 Viewer, you must update your existing viewer by following these steps:
1. If you use Viewer 2002 or Viewer 2003, uninstall it and install Visio 2007 Viewer.
2. Install Visio Viewer 2007 Service Pack 1.
3. Install the security update for Visio Viewer 2007. For more information, see Microsoft Knowledge Base article 973709: Security Update for Microsoft Office Visio Viewer 2007 ().
You can also update the view by using Microsoft Update. However, it might involve multiple runs of Microsoft Update to download the relevant updates.
Customization and options
In Visio 2010, there are many settings and customizations that can be made to personalize the user experience. For more information, see Plan customizations and options for Visio 2010. ((Office.14).aspx)
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ().
See Also
Visio Beta SDK ()
Changes in Office 2010
System requirements for Office 2010
Changes in Word 2010
This article lists changes in Microsoft Word 2010 since Microsoft Office Word 2007 and migration considerations. If you are upgrading from Microsoft Office Word 2003, see also Changes in Office Word 2007 ().
In this article:
• What’s new
• What’s changed?
• What’s removed
• Migrations considerations
What’s new
This section highlights new features in Word 2010.
Fluent UI
The Word 2010 user interface is redesigned and now uses the Microsoft Office Fluent user interface (UI). Introduced in the 2007 Microsoft Office system, the Fluent UI is designed to make it easier for people to find and use the full range of features that Office applications provide, and to preserve an uncluttered workspace. For more information about the Fluent UI, see the resources in Microsoft Office Fluent User Interface Resource Center ().
The ribbon
The ribbon, part of the Fluent UI, was designed to optimize key Word 2010 documentation scenarios to make them easier to use. The ribbon provides quicker access to all the commands in Word 2010 and allows for easier future additions and customizations. You can also customize the ribbon. For example, you can create custom tabs and custom groups to contain frequently used commands. To help maximize the editing of your documentation space on the page, the ribbon can also be hidden while you write.
Backstage view
The Microsoft Office Backstage is part of the Fluent UI and a companion feature to the ribbon. The Backstage view, which can be accessed from the File menu, helps you find frequently used features for managing your Word documentation files. (The File tab replaces the Microsoft Office Button and File menu that were used in earlier release of Microsoft Office.) The Backstage view is used to manage files and the data about the files, such as creating and saving files, inspecting for hidden metadata or personal information, and setting file options.
File format
The Word 2010 file format enables new features such as sharing on the Web, co-authoring, and versioning. Word 2010 works with Office Word 2007 documents.
Protected View
Files from a potentially unsafe location (such as the Internet or an e-mail attachment) or files that contain active content (such as macros, data connections, or ActiveX controls) are validated and can open in Protected View. When you open files in Protected View mode, the editing functions are disabled. You can open and edit files from trusted sources by clicking Enable Editing. You can also explore data about the files in the Backstage view.
Collaboration and sharing features
Word 2010 supports concurrent editing of documents by multiple users when the file is .docx and is located on a server that is running Microsoft SharePoint Server 2010 (or a cobalt-enabled server). For example, a group of users can work on a document at the same time, or a single user can work on the same document from different computers at the same time, all without locking the file. When working with documents that are not located on a server that runs SharePoint Server 2010, Word 2010 only supports single-user editing. The changes are as follows:
• New content is automatically highlighted.
• Author information for any added or shared content is identified by a color-coded bar showing the author’s initials.
• Version support lets users see when and by whom changes were made to a document, and automatically highlights changes relative to earlier versions of the document.
• Faster synchronization of pages so that changes are displayed to all authors in near real-time.
Document authoring and graphic enhancements
Word 2010 provides improved editing tools with a new set of Picture Tools that enable you to transform your documents into artistically engaging documents. New editing tools are as follows:
• Picture Correction Options
• Artistic Effect Options
• Background Removal
• Picture Layout Options
Top of page
What’s changed?
This section summarizes the changes in Word 2010.
Cut, copy, and paste
Cut, copy, and paste is the most common way to move content between applications. Word 2010 can copy and paste content in many formats. Word 2010 has many options available at paste time through the Preview before you paste. Paste options include the following:
• Keep Source Formatting
• Merge Formatting
• Use Destination Theme
• Keep Text Only
Document map
The authoring experience is improved with new ways to navigate content by heading, page, or object. The document map is replaced by the navigation pane. Instead of the document map, users see a new navigation pane in its place. Users can see all the headings of a document, their relative positions, and the current location. With that available, moving between various headings is made by clicking parts of the pane. Outlines can be collapsed to hide nested headings, for long complex documents. Users can no longer see revision marks on headings within the map. Instead, users see the final result of the revisions within the pane.
The overall benefit of this change is a cleaner interface that matches the look of the ribbon. Users also have access to some new functionality as follows:
• Manipulate the headings within the pane to rearrange the content in the document.
• Integration with the Find feature, highlighting the headings with the find results.
The resizable pane consists of the following:
• A text box for the new Find feature
• A view switcher for changing view types
• Buttons for skipping to the Next and Previous items
• The main region, a list of navigable items, with scrolling when it is necessary
The pane is shown by default, but can be hidden through a toggle button at the top of the scroll bar, via the View tab, or the navigation control in Reading mode. The check box to access the navigation pane is the same as the former document map (only the name is changed).
Print preview
The Print preview experience and the Print dialog box have been combined into the Print Place via the Backstage. This feature is consistent across all Office applications. It can be invoked through the object model for third-party developers to create add-ins for Word 2010. The workflow process is still the same by using CTRL+P or by selecting Print in the Backstage. The Print Preview Edit Mode was fully deprecated.
RTF file format
The RTF file format is no longer enhanced to include new features and functionality. Features and functionality that are new to Word 2010 and future versions of Word are lost when they are saved in RTF. In addition, Word 2010 supports a new converter interface based on Open XML Formats.
Smart tags
Text is no longer automatically recognized by a smart tag recognizer and will no longer display a purple dotted underline. Instead, users will be able to trigger recognition and view custom actions associated with text by selecting the text and clicking the Additional actions on the context menu. Once the user has moved the IP outside the current paragraph, the text tagging will be cleared for that paragraph. There are changes to the object model to reflect that text marked by a smart tag recognizer will not be stored in the document.
Views
In Word 2010, when you click the View tab, the options are as follows:
• Print Layout
• Full Screen Reading
• Web Layout
• Outline
• Draft (Normal)
What’s removed
This section provides information about removed features in Word 2010.
Person Name removal of smart tag
The Person Name (Outlook E-mail Contacts) smart tag will be removed and replaced with functionality that uses the Global Address List (GAL) through Microsoft Office Communicator. In Word the functionality will be replaced by the “additional actions” functionality described earlier in this article, but in Excel the functionality will be completely removed. The 2007 Office system will be the last version that supports this functionality.
AutoSummary
AutoSummary is the feature that lists the Title, Subject, Author, Keywords, and Comments. This feature was available from the Tools menu. In Word 2010, this feature is no longer used. If you insert an abstract into the document, that is not AutoSummary data and will remain. However, if the document was in a summary view when it is saved, it will not be after you open it.
Microsoft Office Document Imaging (MODI)
MODI provided a common document imaging and scanning solution for Office. It was also the basis of the Fax feature for Office. When MODI was installed, it was the default handler for .tif, .tiff, and .mdi files. In Office 2010, MODI is fully deprecated. This change also affects the setup tree, which no longer shows the MODI Help, OCR, or Indexing Service Filter nodes on the Tools menu. The Internet Fax feature in Office 2010 uses the Windows Fax printer driver to generate a fixed file format (TIF). MODI and all its components are deprecated for 64-bit Office 2010.
Research and Reference pane
The Research and Reference pane is removed from Windows Internet Explorer 7. Therefore, the shortcut ALT+Click in Microsoft Word 2010 no longer takes users to that pane. The Research and Reference feature brought up a research pane to search all Intranet sites and portals.
Mail Merge by using a Works database
Users cannot perform a mail merge in Microsoft Word 2010 or Microsoft Publisher 2010 by using a Microsoft Works database, because of a change in the object model. This primarily affects users who have configured a recurring mail merge that reads content from a Works database. We recommend that you use Works to export the data and then create a new data source for performing the mail merge operation.
Search Libraries button
The Search Libraries button is removed from the Insert Citations menu (on the References Tab).
WLL (Word Add-in Libraries)
WLL files are deprecated for both 32-bit and 64-bit Office 2010. A WLL is an add-in for Microsoft Word that you can build with any compiler that supports building DLLs.
Migrations considerations
This section describes changes to consider when you migrate from Office Word 2007 to Word 2010.
Migrating Word files
The default file format has not changed in Microsoft Office 2010. The XML-based file format was introduced in the 2007 Microsoft Office system and continues to be used. For a review of the XML file format, see Overview of the XML file formats in the 2007 Office system ().
When you open a document in Word 2010, it will open in one of three modes:
• Word 2010
• Word 2007 compatibility mode
• Word 97-2003 compatibility mode
To determine which mode the document is in, check the document’s title bar. If (Compatibility Mode) appears after the file name, the document is in either Word 2007 compatibility mode or Word 97-2003 compatibility mode. You can continue to work in compatibility mode or you can convert your document to the Word 2010 file format.
1. Click the File tab.
2. Perform one of the following:
• To convert the document without saving a copy, click Info, and then click Convert.
• To create a new copy of the document in Word 2010 mode, click Save As, type a new name for the document in the File name box, and then click Word Document in the Save as Type list.
3. Click Info, and then click Convert.
Compatibility Checker
The Compatibility Checker lists elements in a document that are not supported or that will behave differently in Word 2007 or in Word 97-2003 format. Some of these features will be permanently changed and will not be converted to Word 2010 elements, even if you later convert the document to Word 2010 format.
Embedded Word 2010 objects
Open XML embedded objects can be converted to enable users on earlier versions of Word to be able to change them.
1. Right-click the embedded object.
2. Point to Document Object, and then click Convert.
3. In the Convert dialog box, click Convert To.
4. In the Object type list, select Microsoft Word 97-2003 Document.
Equations
If you save a document in Word 97-2003 format, equations will be converted to images that you cannot edit. However, if you later convert the document to Word 2010 file format and no changes have been made to the equation images in an earlier version, the equations will become text and you will be able to change them.
SmartArt graphics
When you save a document that contains a SmartArt graphics in Word 97-2003 format, the graphics will be converted to static images. You will be unable to change text inside a graphic, change its layout, or change its general appearance. If you later convert the document to Word 2010 format and no changes have been made to the images in an earlier version, the graphic will be changed back to a SmartArt object.
Migration considerations from Office 97-2003 to Office 2010
Many of the changes from Office 97-2003 to Office 2010 are no different from Office 97-2003 to the 2007 Office system.
For a list of migration considerations from Office 97-2003 to the 2007 Office system, see Migration considerations for Word 2007 ().
The following changes in Word 2010 might affect migration:
• AutoText is being moved back to Normal.dotm to facilitate autocomplete. For users going from Office Word 2003 to Word 2010, we recommend that you move the document to %AppData%\Word\Startup, and then follow the steps to upgrade a document. Office Word 2007 users will find their autotext automatically moved.
• AutoText gallery is now available in the Quick Parts gallery. Therefore, users no longer have to remember to move their autotext to the Quick Parts gallery.
• Word will automatically migrate building blocks to Word 2010 when you first start the application. This is done by creating a copy of the existing building blocks file and putting it in a new directory, %AppData%\Document Building Block\{||cc}\14, and the striping the building blocks that were provided with Office Word 2007 from the file.
• Similarly to Word 2007, Word 2010 gives you a new Normal.dotm on the first start. Your old normal file will be named normalold.dotm. If you want to restore your setting from Word 2007, right-click the file, and then click Open. Once in Word, you should use the Upconvert button in the OutSpace to convert the normal file to Word 2010 format.
VBA settings migration
In Office 2010, Visual Basic for Applications (VBA) 6.0 was updated to VBA 7.0. VBA 7.0 settings were reset to their defaults after migration instead of automatically repopulating. This occurred because the registry settings for VBA are in a different hive in Office 2010, as shown in the following table.
|Version |Registry subkey |
|Office 2000 through Office 2007 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\6.0\Common |
|Office 2010 |HKEY_CURRENT_USER\SOFTWARE\Microsoft\VBA\7.0\Common |
To correct this problem, copy the VBA 6.0 registry keys from the 6.0 hive to the 7.0 hive.
For more information, see Migrate user data registry keys in Office 2010 and Compatibility Between the 32-bit and 64-bit Versions of Office 2010 ().
Top of page
See Also
Changes in Office 2010
System requirements for Office 2010
SharePoint Workspace 2010 reference
This section describes how to use the Office Customization Tool (OCT) and Group Policy to customize an installation of Microsoft SharePoint Workspace 2010.
In this section:
|Article |Description |
|Office Customization Tool settings for SharePoint Workspace 2010 |Describes how to use the Office Customization Tool (OCT) to customize|
| |an installation of SharePoint Workspace 2010. |
|Group Policy for SharePoint Workspace 2010 |Describes Group Policy settings that, when applied to an Active |
| |Directory organizational unit, can be used to customize an |
| |installation of SharePoint Workspace 2010. |
Group Policy for SharePoint Workspace 2010
This article describes Group Policy settings that, when applied to an Active Directory organizational unit, you can use to customize an installation of Microsoft SharePoint Workspace 2010. A collection of Group Policy settings, called a Group Policy object (GPO), is tied to a rules engine that determines which Active Directory group receives related policy settings. SharePoint Workspace–specific Group Policy settings can found in the groove.adm file.
For more information about how to access and use the Group Policy feature, see Group Policy overview (Office system) () and Enforce settings by using Group Policy in the Office system ().
For more information about how to customize deployments, see Configure and customize SharePoint Workspace 2010.
The following table describes GPOs that affect SharePoint Workspace 2010 installation.
|Group Policy object |Description |Default value or |
| | |undefined value |
|Prohibit Groove Workspaces |Prohibits use of Groove workspaces and Shared Folders. Limits SharePoint Workspace |Disabled |
| |use to SharePoint workspaces only. | |
|Enable IPv6 |Enables IPv6 for SharePoint Workspace. |Disabled |
|Prefer IPv4 |Indicates that IPv4 is preferred over IPv6 if both are supported on client |Disabled |
| |computers. | |
|Prevent Indexing Certain |Prevent Windows Search 4.0 (or later versions) from crawling (creating indexes for)|Enabled |
|Paths |SharePoint Workspace content. This policy prevents Windows Search crawling for | |
| |SharePoint Workspace, removes Search from the ribbon in SharePoint Workspace, | |
| |overrides any user-initiated content crawling, and cleans the Windows Search index | |
| |of previously indexed SharePoint Workspace content. | |
| |If this policy is not enabled, Windows Search indexing is enabled by default for | |
| |the following SharePoint Workspace content: | |
| |• Metadata for SharePoint workspaces and Groove workspaces for SharePoint Workspace| |
| |2010 | |
| |• Metadata for all Groove workspace tools for SharePoint Workspace 2010 | |
| |• The following Groove workspace content is for SharePoint Workspace 2010: | |
| |Discussions, Documents, Notepad entries, chat transcripts, member messages, and | |
| |custom lists. | |
| |If this policy is enabled, Windows Search does not crawl specified paths. The | |
| |format for specifying a non-searchable path is: Protocol://site/path/file and | |
| |SharePointWorkspaceSearch must be entered as the search protocol. | |
| |For example, the following entry prevents indexing of any SharePoint Workspace | |
| |content for all users on target SharePoint Workspace computers: | |
| |SharePointWorkspaceSearch://{*}/* | |
| |For more information about the Prevent Indexing Certain Paths GPO, see Group Policy| |
| |for Windows Search (). | |
| |[pic]Note: | |
| |This setting is a Windows Search policy that affects SharePoint Workspace 2010. | |
| |For more information about Group Policy for Windows Search, see Windows Search | |
| |Administrators Guides (). | |
|Sync Only On Domain Network |Forces a Secure Socket Layer (SSL) connection for SharePoint Workspace clients that|Disabled |
| |connect to SharePoint Server 2010. | |
| |[pic]Note: | |
| |This setting is a SharePoint Server 2010 custom policy that affects SharePoint | |
| |Workspace 2010. | |
|SharePoint Workspace Account|If you use Groove Server 2010 Manager to manage SharePoint Workspace, use this |Disabled |
|Configuration Code Required |policy to require that a managed account configuration code be entered, manually or| |
| |automatically, in order to create a SharePoint Workspace account. This prevents | |
| |users from creating unmanaged SharePoint Workspace accounts. | |
| |For information about Groove Server 2010 and automatic account configuration, see | |
| |Deployment for Groove Server 2010 Beta. | |
| |((Office.1| |
| |4).aspx) | |
|Groove Server Manager Name |If you use Groove Server 2010 Manager to manage SharePoint Workspace, use this |Disabled |
| |policy to specify the Groove Server 2010 Manager server name to which users are | |
| |assigned. This attribute supports automatic SharePoint Workspace account | |
| |configuration or restoration, and migration of unmanaged accounts to managed | |
| |accounts. For information about how to migrate unmanaged accounts to Groove Server | |
| |2010 Manager, see the Migration section of Operations for Groove Server 2010 | |
| |Manager. | |
| |((Office.1| |
| |4).aspx) | |
|Groove Server Manager Valid |If you use Groove Server 2010 Manager to manage SharePoint Workspace, use this |Enabled |
|Link Security |policy to ensure a trusted SharePoint Workspace-to-Manager communication link. When| |
| |this requirement is enabled, the presented Groove Server Manager SSL certificate | |
| |must be valid to enable SharePoint Workspace-to-Manager communication. | |
|Maximum Number of Proxy |If you use Groove Server 2010 Manager to manage SharePoint Workspace, use this |Enabled |
|Connection Failures to |policy to limit the number of failed proxy connection attempts to a Groove Server | |
|Groove Server Relay |Relay by the SharePoint Workspace client. When the limit is reached, additional | |
| |proxy connection attempts to the Relay server are abandoned. | |
|List of Blocked Groove Relay|If you use Groove Server 2010 Manager to manage SharePoint Workspace, use this |Disabled |
|Servers |policy to prevent SharePoint Workspace clients from initiating communications to | |
| |listed Groove Relay servers that are known to be permanently decommissioned. The | |
| |format is a comma-separated list of fully qualified domain names of Relay servers. | |
| |Wildcards in the names are supported. The question mark (?) is for single character| |
| |substitution and the asterisk (*) is for domain part substitution. | |
See Also
Configure and customize SharePoint Workspace 2010
Office Customization Tool settings for SharePoint Workspace 2010
Deployment for Groove Server 2010 Beta ((Office.14).aspx)
Plan for SharePoint Workspace 2010
Office Customization Tool settings for SharePoint Workspace 2010
This article describes how to use the Office Customization Tool (OCT) to customize an installation of Microsoft SharePoint Workspace 2010. This customization option is especially useful if you cannot access the Group Policy feature.
For information about how to use the OCT, see Office Customization Tool in Office 2010.
For more information about customization options, see Configure and customize SharePoint Workspace 2010.
The following table describes OCT settings that affect SharePoint Workspace 2010.
|OCT paths to settings for SharePoint Workspace |Description |
|Features/Modify user settings/Microsoft SharePoint Workspace 2010 |• Prohibit Groove workspaces — Prohibits use of Groove workspaces and|
| |Shared Folders. Limits SharePoint Workspace use to SharePoint |
| |workspaces only. |
| |Default setting: Disabled |
| |• Enable IPv6 — Enables IPv6 for SharePoint Workspace. |
| |Default setting: Disabled |
| |• Prefer IPv4 — Indicates that IPv4 is preferred over IPv6 if both |
| |are supported on client computers. |
| |Default setting: Disabled |
| |• SharePoint Workspace Account Configuration Code Required — If you |
| |use Groove Server 2010 to manage SharePoint Workspace, use this |
| |setting to require that a managed account configuration code be |
| |entered, manually or automatically, in order to create a SharePoint |
| |Workspace account. This prevents users from creating unmanaged |
| |SharePoint Workspace accounts. For information about Groove Server |
| |2010 and automatic account configuration, see Deployment for Groove |
| |Server 2010 Beta. |
| |(
| |19489(Office.14).aspx) |
| |Default setting: Disabled |
| |• Groove Server Manager Name — If you use Groove Server 2010 to |
| |manage SharePoint Workspace, use this setting to specify the server |
| |name for use with automatic account configuration or restoration, or |
| |when you migrate unmanaged to managed accounts. |
| |Default setting: Disabled |
| |• Groove Server Manager Valid Link Security — If you use Groove |
| |Server 2010 to manage SharePoint Workspace, use this setting to |
| |ensure a trusted SharePoint Workspace-to-Manager communications link.|
| |When this requirement is enabled, the presented Groove Server Manager|
| |Secure Socket Layer (SSL) certificate must be valid to enable |
| |SharePoint Workspace-to-Manager communication. |
| |Default setting: Enabled |
| |• Groove Server Manager Valid Link Security — If you use Groove |
| |Server 2010 to manage SharePoint Workspace, use this link to ensure a|
| |trusted SharePoint Workspace-to-Manager communication link. When this|
| |requirement is enabled, the presented Groove Server Manager SSL |
| |certificate must be valid to enable SharePoint Workspace-to-Manager |
| |communication. |
| |Default setting: Enabled |
| |• Maximum Number of Proxy Connection Failures to Groove Server |
| |Relay — If you use Groove Server 2010 to manage SharePoint Workspace,|
| |use this setting to limit the number of failed proxy connection |
| |attempts to a Groove Server Relay by the SharePoint Workspace client.|
| |When the limit is reached, additional proxy connection attempts to |
| |the Relay server are discontinued. |
| |Default setting: Enabled |
| |• List of Blocked Groove Relay Servers —If you use Groove Server 2010|
| |to manage SharePoint Workspace, use this setting to prevent the |
| |SharePoint Workspace clients from initiating connections to listed |
| |Groove Relay servers that are known to be permanently decommissioned.|
| |The format is a comma-separated list of fully qualified domain names |
| |of Relay servers. Wildcards in the names are supported. The question |
| |mark (?) is for single character substitution and the asterisk (*) is|
| |for domain part substitution. |
| |Default setting: Disabled |
| |For more information about SharePoint Workspace settings, see Deploy |
| |SharePoint Workspace 2010 |
| |(
| |0c425(Office.14).aspx) |
|Additional content |• Use the Add files setting in the OCT to automatically add files, |
| |such as SharePoint Workspace templates, to user installations. |
| |• Use the Remove Files setting if you have special requirements that |
| |can only be enabled or disabled through the Windows Registry. For |
| |example, you can use this setting to remove legacy SharePoint |
| |Workspace or Microsoft Office Groove 2007 device management registry |
| |settings or you can set the registry value that disables running of |
| |the New User video upon configuration of a new account. Files to be |
| |removed might also include workspace templates from previous Office |
| |Groove 2007 installations. |
See Also
Configure and customize SharePoint Workspace 2010
Group Policy for SharePoint Workspace 2010
Deployment for Groove Server 2010 Beta
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
Related searches
- download microsoft office onenote 2016
- download microsoft office for free
- download microsoft office for free windows 10
- download microsoft office already purchased
- download microsoft desktop app
- how to download microsoft office for free
- download microsoft onenote 2016 free
- free download microsoft office 2010
- download microsoft office 365 free full
- download microsoft word for pc
- minecraft download microsoft store
- download microsoft word for mac