0% found this document useful (0 votes)

82 views68 pages

Getting Started With The 2007 Office Resource Kit: Office IT and Servers User Assistance

Uploaded by

M Abo Samra

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

82 views68 pages

Getting Started With The 2007 Office Resource Kit: Office IT and Servers User Assistance

Uploaded by

M Abo Samra

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

You are on page 1/ 68

Getting started with the 2007 Office

Resource Kit

Microsoft Corporation
Published: March 2009
Author: Office IT and Servers User Assistance ([email protected])

Abstract
This book provides an overview of the new architecture and tools provided in the 2007 Microsoft
Office system. This includes a description of the language-neutral architecture and the improved
design for deploying Office in multiple languages. The consolidated deployment tool for Office,
the Office Customization Tool, is introduced along with the streamlined customization model for
deploying the 2007 Office system. The audience for this book includes IT generalists, IT
operations, help desk, and deployment staff, IT messaging administrators, and consultants.
The content in this book is a copy of selected content in the 2007 Office Resource Kit technical
library (http://go.microsoft.com/fwlink/?LinkID=84741&clcid=0x409) as of the publication date. For
the most current content, see the technical library on the Web.
The information contained in this document represents the current view of Microsoft Corporation
on the issues discussed as of the date of publication. Because Microsoft must respond to
changing market conditions, it should not be interpreted to be a commitment on the part of
Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the
date of publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this document may be reproduced, stored in or introduced into a
retrieval system, or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the express written
permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places and events depicted herein are fictitious, and no association
with any real company, organization, product, domain name, e-mail address, logo, person, place
or event is intended or should be inferred.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Excel, InfoPath, Outlook, SharePoint, SQL Server, Windows,
Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries. The names of actual companies and
products mentioned herein may be the trademarks of their respective owners.

ii
Contents
Getting Help.................................................................................................................................... v

Getting started with the 2007 Office system...................................................................................7

About the 2007 Office Resource Kit............................................................................................ 7
What's new for IT professionals in the 2007 Office system.........................................................8
Setup architecture.................................................................................................................... 9
Setup features comparison................................................................................................... 9
Language-neutral architecture............................................................................................... 10
Customization model.............................................................................................................. 11
System requirements for the 2007 Office release..................................................................15
Microsoft Office Basic 2007................................................................................................ 16
Microsoft Office Standard 2007.......................................................................................... 18
Microsoft Office Home and Student 2007...........................................................................20
Microsoft Office Professional 2007.....................................................................................22
Microsoft Office Small Business 2007.................................................................................24
Microsoft Office Professional Plus 2007.............................................................................26
Microsoft Office Enterprise 2007......................................................................................... 28
Microsoft Office Ultimate 2007............................................................................................30
Microsoft Office Accounting 2007.......................................................................................32
Microsoft Office Access 2007..............................................................................................33
Microsoft Office Excel 2007................................................................................................ 33
Microsoft Office InfoPath 2007............................................................................................ 34
Microsoft Office Groove 2007.............................................................................................36
Microsoft Office OneNote 2007...........................................................................................37
Microsoft Office Outlook 2007............................................................................................. 38
Microsoft Office PowerPoint 2007.......................................................................................39
Microsoft Office Publisher 2007..........................................................................................40
Microsoft Office Word 2007................................................................................................41
Microsoft Office Multi-Language Pack 2007.......................................................................42
More information................................................................................................................. 43
Migration from previous versions of Office.............................................................................43
Installing, customizing, and updating the 2007 Office system.............................................44
File format........................................................................................................................... 45
Security............................................................................................................................... 45
User Interface..................................................................................................................... 46
Object model....................................................................................................................... 46
Access 2007....................................................................................................................... 46
Excel 2007.......................................................................................................................... 47
Outlook 2007...................................................................................................................... 47
Word 2007, PowerPoint 2007, and OneNote 2007.............................................................47

Setup architecture overview for the 2007 Office system...............................................................49

iii
Setup process........................................................................................................................... 49
Setup sequence of events...................................................................................................... 50
Run Setup........................................................................................................................... 50
Check prerequisites............................................................................................................ 51
Read XML data................................................................................................................... 51
Build the feature tree.......................................................................................................... 52
Create a local installation source on the user's computer...................................................52
Install Office........................................................................................................................ 53
Apply the customization file................................................................................................53
Apply software updates....................................................................................................... 54
Including more than one product on the installation point......................................................54
Running Setup interactively.................................................................................................... 55
Language-neutral design........................................................................................................... 55
Language versions of Office................................................................................................... 56
Language packs for Office..................................................................................................... 57
Installing multiple languages of Office....................................................................................59
Installing a default language on each user's computer.......................................................59
Specifying one or more languages to install on users' computers......................................60
Installing language packs separately..................................................................................60
Installing Proofing Tools...................................................................................................... 61
Adding languages after Office is installed...........................................................................61
Streamlined customization model.............................................................................................. 61
Using the Office Customization Tool.......................................................................................62
Customizing a new installation............................................................................................... 62
Making changes to an existing Office installation...................................................................63
Using the Config.xml file to customize Office.........................................................................63
Using Setup command-line options........................................................................................64
Using Group Policy................................................................................................................ 64
Required local installation source........................................................................................... 65
Creating a local installation source on users' computers....................................................66
Deploying the local installation source by itself...................................................................66
Consolidated update process................................................................................................. 67
Applying Office updates during new installations................................................................67
Updating existing Office installations..................................................................................68
Download this book................................................................................................................ 68

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

v
Getting started with the 2007 Office system
In this section:
 About the 2007 Office Resource Kit
 What's new for IT professionals in the 2007 Office system
 Setup architecture
 Language-neutral architecture
 Customization model
 System requirements for the 2007 Office system release
 Migration from previous versions of Office

About the 2007 Office Resource Kit

The Office Resource Kit for the 2007 Microsoft Office system provides information about new
features and changes in deployment strategies for the 2007 Office system. The 2007 Office
Resource Kit documentation is intended for IT professionals who plan, implement, and maintain
Office installations in their organizations. New and updated content is published on a regular
basis. The Getting Started with the 2007 Office system section provides a basic overview about
what is new in the 2007 Office system, describes system requirements, and provides a roadmap
of the 2007 Office Resource Kit content.

Note:
The primary administrative tools for deploying the 2007 Office system are now included
with the product and are no longer available as a download as in previous versions of
Office. To view the Office Resource Kit for previous versions of Office, see Microsoft
Office Suites and Programs (http://technet.microsoft.com/en-us/library/cc308571.aspx).
The Office Resource Kit for the 2007 Office system is organized into the following sections:
 Product evaluation for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc179178.aspx). This section includes white papers about migrating to Microsoft
Office Access 2007 and Microsoft Office Excel 2007, and about the fluent user interface.
 Planning and architecture for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc179137.aspx). This section describes how Setup for the 2007 Office system
works, and provides planning information for: migration from previous versions of Office,
Group Policy for the 2007 Office system, Microsoft Office Outlook 2007, and Information
Rights Management.
 Deployment for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc178982.aspx). This section provides how-to information for specific deployment
tasks, such as customizing the installation, installing the 2007 Office system on users'
computers, implementing the deployment in multiple languages, and migrating to the new file
format. It also includes Office Outlook 2007 deployment tasks.

7
 Operations for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc179068.aspx). This section provides information about maintaining and managing
an installation after deploying the 2007 Office system, including up-to-date information about
the 2007 Office system administrative updates and how-to information for distributing product
updates.
 Security and protection for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc179135.aspx). This section provides an overview of the security model for the
2007 Office system, and security planning and deployment information.
 Troubleshooting for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc298433.aspx). This section presents are a collection of troubleshooting resources
for the 2007 Office system.
 Technical reference for the 2007 Office release (http://technet.microsoft.com/en-
us/library/cc179032.aspx). This section provides technical details in these areas of the 2007
Office system: Setup, file formats, fonts, migration resources, international languages,
messaging, and security.
Content in the 2007 Office Resource Kit is also available in downloadable and printable form. For
more information, see Downloadable content for the 2007 Office Resource Kit
(http://technet.microsoft.com/en-us/library/cc178979.aspx).

What's new for IT professionals in the 2007 Office

system
The 2007 Office system provides new features and enhancements that help IT administrators
configure, deploy, and maintain their Office installations. These features provide benefits that
allow administrators to work more efficiently and help reduce administrative costs. The changes
include:
 A new 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.
 New Extensible Markup Language (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 disparate data sources,
accelerating document assembly, data mining, and content reuse.
 New 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 not be able 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.
 New 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.
8
In this section:
 Setup architecture
 Language-neutral architecture
 Customization model
 System requirements for the 2007 Office system release
 Migration from previous versions of Office

Setup architecture
The Setup program for the 2007 Office system has been redesigned to support a more efficient
installation process. Most of the tools and procedures are new but the overall objective is 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 has been absorbed by
the new Setup program. Setup handles the most difficult parts for you behind the scenes, and the
steps you take to customize and distribute the product are simpler than in any previous version.

Setup features comparison

The following table compares Setup features in the 2007 Office system release to their closest
counterparts in previous versions (Microsoft Office 2000, Office XP, and Office 2003).

Previous version 2007 Office system release Function

Windows Installer Setup program (Setup.exe) Installation program

(Msiexec.exe)

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 Language-neutral architecture Deploy multiple languages at
Pack once

Setup.ini file Config.xml file Customize installation file

Setup command line Config.xml file Customize installation file

Custom Installation Wizard Office Customization Tool Customize installation of

(OCT) 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

9
Previous version 2007 Office system release Function

Management Console (MMC)

snap-ins are used to manage
policy settings

Setup files
In previous versions of Office, 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 Window Installer properties on the command line.
In the 2007 Office system release, a single Office product consists of multiple MSI files. 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 beginning to end.
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.

Note:
You cannot use the Windows Installer command line (Msiexec.exe) to install any product
in the 2007 Office release, nor can you set Windows Installer properties on the Setup
command line. You can, however, use the new deployment tools to customize all aspects
of the installation process, just as you did in previous versions. For more information, see
Setup architecture overview for the 2007 Office system.

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 of the 2007 Office release eliminates the need to chain
language packs and condenses the process to a single installation. After you create your initial
network installation point (which always includes a core product), you copy all the additional
language folders 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 allow Setup to manage the process of assembling the correct
language version for each user automatically from the available language options.

10
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/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 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.

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 the 2007 Office system.

Customization model
In previous versions of Office products, several tools were required to customize Setup and to
manage Office after installation. However, the 2007 Office system provides a consistent,
streamlined customization model. You can use one of several methods to customize the
installation, although the best method depends upon what you are customizing and whether you
want users to be able to change the default configuration.

11
Choosing a customization tool
The following table summarizes the differences between the customization methods for the 2007
Office system and describes the recommended or required scenarios for each method.

Tool or method Scenarios Results

Use the Office Customization Recommended for most Setup installs a default
Tool to create a Setup customizations, including: configuration on all computers
customization file (MSP file).  Accepting License Terms to which this MSP file is
and entering a volume applied.
license key Users can modify most settings
 Running Setup without after the installation.
user interaction
 Customizing features and
user settings
 Distributing an Outlook
profile

Edit the Config.xml file. Required for the following Setup installs the specified
customizations: products and languages on all
 Specifying the path to the computers installed with this
network installation point Config.xml file.

 Specifying languages to Settings specified in Config.xml

install take precedence over duplicate
settings in the Setup
 Pointing Setup to a custom
customization file.
Config.xml or Setup
customization file
 Copying the local
installation source to the
user's computer without
installing Office
 Chaining additional
products to the primary
installation

12
Tool or method Scenarios Results

Add options or properties to Available for only the following Setup applies your
the Setup command line. customizations: customizations when it initially
 Pointing Setup to a custom installs Office or when it runs in
Config.xml or Setup maintenance mode.
customization file You cannot set Windows
 Modifying an existing Installer properties on the
installation command line.

 Repairing the product

 Uninstalling the product

Use the Group Policy Object Used to configure highly Administrators use Group
Editor Microsoft Management restricted or lightly managed Policy to define configurations
Console (MMC) snap-in to configurations for user and once and then rely on the
specify policy settings. computer 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 on a periodic
basis.

In this section:
 Office Customization Tool
 Config.xml file
 Setup command-line options
 Group Policy
Office Customization Tool
The Office Customization Tool (OCT) is built into the Setup program and is the primary tool for
customizing the installation of products in the 2007 Office system. You do not need to install a
separate tool. Instead, you run Setup with the /admin command-line option to start the tool:
setup.exe /admin
Using the OCT, create a Setup customization file, which you store in the Updates folder (for new
or initial installations) at the root of the network installation point. Setup applies the file when it
installs the relevant product. A Setup customization file is an expanded form of a Windows
Installer MSP file. Each file is configured for a specific product, such as Microsoft Office
Professional 2007 or Microsoft Office OneNote 2007. You do not need to specify the MSP file on
the Setup command line. When you run Setup to install an Office product, Setup looks in the

13
Updates folder for a customization file that corresponds to the product you are installing. As Setup
installs the product, is applied the customizations from this file.
You can create more than one Setup customization file to configure Office for different groups or
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 the Config.xml file.
For more information about the OCT, see Office Customization Tool in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179097.aspx).
Config.xml file
The Config.xml file is used to configure installation options such as the following:
 Specifying the path of the network installation point.
 Specifying the products to install.
 Customizing Setup options such as logging and the location of the Setup customization file
and software updates.
 Specifying 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.
If you use both the OCT and the Config.xml file to customize an installation, the settings defined
in the Config.xml file take precedence over those in the Setup customization MSP file. For more
information about using the Config.xml file, see Config.xml file in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179195.aspx).
Setup command-line options
The Setup.exe command line is used for the following tasks:
 Running the Office Customization Tool to create a Setup customization (MSP) file.
 Specifying a path to a specific customization file (MSP file) or to the folder where you store
customization files.
 Specifying the Config.xml file that Setup uses during the installation.
 Running Setup in maintenance mode and making changes to an existing Office installation.
 Running Setup to repair the specified product from the user's computer
 Running Setup to remove the specified product from the user's computer.
For detailed information about how to use the Setup command-line options, see Setup command-
line options for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc178956.aspx).
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. Group Policy settings are
contained in Group Policy objects (GPOs), which are linked to selected Active Directory directory
service containers — sites, domains, or organizational units (OUs). The settings within GPOs are
evaluated by the affected targets using the hierarchical nature of Active Directory.

14
To configure Group Policy settings in GPOs, administrators use the Group Policy Object Editor
Microsoft Management Console (MMC) snap-in from the Group Policy Management Console
snap-in. The 2007 Office system policy settings are contained in Administrative Template files
(.adm and ADMX files). You can download the Administrative Template files for the 2007 Office
system from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=78161. For
more information, see Group Policy Overview (http://technet.microsoft.com/en-
us/library/cc179176.aspx) and Enforce settings by using Group Policy in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179081.aspx).
Most of the settings available in the OCT are included in the Office Administrative Template files,
but the Group Policy settings are recorded in different areas of the Windows registry. The 2007
Office system policy settings are stored in the Policies branch of the registry, and these settings
have access control list (ACL) restrictions that prevent non-administrator users from changing
them. In contrast, OCT settings can be changed by users.

System requirements for the 2007 Office release

A hardware upgrade should not be necessary when you upgrade from Microsoft Office 2003 to
the 2007 Office system. You may need to upgrade to a supported operating system. When you
upgrade from Microsoft Office 2000 or Microsoft Office XP to the 2007 Office system, you must
ensure that your hardware and operating system meet the minimum system requirements for the
2007 Office system.
It is strongly recommend that you evaluate your computer to verify that it meets or exceeds the
minimum system requirements before you install applications in the 2007 Office system.

Note:
The 2007 Office system client is a 32-bit application that runs on a Windows 64-bit
platform (Windows XP, Windows Server 2003, and Windows Vista). There may be feature
limitations, as noted in the system requirements listed in the following sections.
In this section:
 Microsoft Office Basic 2007
 Microsoft Office Standard 2007
 Microsoft Office Home and Student 2007
 Microsoft Office Professional 2007
 Microsoft Office Small Business 2007
 Microsoft Office Professional Plus 2007
 Microsoft Office Enterprise 2007
 Microsoft Office Ultimate 2007
 Microsoft Office Accounting 2007
 Microsoft Office Access 2007
 Microsoft Office Excel 2007
 Microsoft Office InfoPath 2007

15
 Microsoft Office Groove 2007
 Microsoft Office OneNote 2007
 Microsoft Office Outlook 2007
 Microsoft Office PowerPoint 2007
 Microsoft Office Publisher 2007
 Microsoft Office Word 2007
 Microsoft Office Multi-Language Pack 2007
 More information

Microsoft Office Basic 2007

The following table lists the system requirements for Microsoft Office Basic 2007.

Component Requirement

Computer and processor 500 megahertz (MHz) processor or higher.

Memory 256 megabyte (MB) RAM or higher. 512 MB

RAM or higher recommended for Outlook
Instant Search. Grammar and contextual
spelling in Office Word do not turn on unless the
computer has 1 gigabyte (GB) of memory.

Hard disk 1.5 GB of memory. A portion of this disk space

is free after installation if the original download
package is removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with Service Pack (SP) 2,

Windows Server 2003 with SP1, or later
operating system. The Office Clean-up wizard is
not available on 64-bit operating systems.

16
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

17
Microsoft Office Standard 2007
The following table lists the system requirements for Office Standard 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher. 512 MB RAM or higher

recommended for Outlook Instant Search.
Grammar and contextual spelling in Office Word
are not turned on unless the computer has 1
GB of memory.

Hard disk 1.5 GB of memory. A portion of this disk space

is free after installation if the original download
package is removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. The Office
Clean-up wizard is not available on 64-bit
operating systems.

18
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

19
Microsoft Office Home and Student 2007
The following table lists the system requirements for Office Home and Student 2007.

Component Requirement

Computer and processor 500 MHz processor or higher. 2 GHz processor

or higher recommended for OneNote Audio
Search. Close-talking microphone required.
Audio Search not available in all languages.

Memory 256 MB RAM or higher. Grammar and

contextual spelling in Office Word are not turned
on unless the computer has 1 GB of memory. 1
GB RAM or higher recommended for OneNote
Audio Search.

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Send to
OneNote 2007 print driver not available on 64-
bit operating systems. Office Clean-up wizard
not available on 64-bit operating systems.

20
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

21
Microsoft Office Professional 2007
The following table lists the system requirements for Office Professional 2007.

Component Requirement

Computer and processor 500 MHz processor or higher. 1 GHz processor

or higher recommended for Business Contact
Manager.

Memory 256 MB RAM or higher. 512 MB RAM or higher

recommended for Business Contact Manager.
Business Contact Manager not available in all
languages. 512 MB RAM or higher
recommended for Outlook Instant Search.
Grammar and contextual spelling in Office Word
are not turned on unless the computer has 1
GB of memory.

Hard disk 2 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

22
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

23
Microsoft Office Small Business 2007
The following table lists the system requirements for Office Small Business 2007.

Component Requirement

Computer and processor 500 MHz processor or higher. 1 GHz processor

or higher recommended for Business Contact
Manager.

Memory 256 MB RAM or higher. 512 MB RAM or higher

recommended for Business Contact Manager.
Business Contact Manager not available in all
languages. 512 MB RAM or higher
recommended for Outlook Instant Search.
Grammar and contextual spelling in Office Word
is not turned on unless the computer has 1 GB
of memory.

Hard disk 2 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

24
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

25
Microsoft Office Professional Plus 2007
The following table lists the system requirements for Office Professional Plus 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher. 512 MB RAM or higher

recommended for Outlook Instant Search.
Grammar and contextual spelling in Office Word
is not turned on unless the computer has 1 GB
of memory.

Hard disk 2 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

26
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

27
Microsoft Office Enterprise 2007
The following table lists the system requirements for Office Enterprise 2007.

Component Requirement

Computer and processor 500 MHz processor or higher. 2 GHz processor

or higher recommended for OneNote Audio
Search. Close-talking microphone required.

Memory 256 MB RAM or higher. 1 GB RAM or higher

recommended for OneNote Audio Search.
Close-talking microphone required. Audio
Search not available in all languages. 512 MB
RAM or higher recommended for Outlook
Instant Search. Grammar and contextual
spelling in Office Word is not turned on unless
the computer has 1 GB of memory.

Hard disk 2 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Send to
OneNote 2007 print driver not available on a
64-bit operating system. Microsoft Office
Groove 2007 Folder Synchronization not
available on 64-bit operating systems. Office
Clean-up wizard not available on 64-bit
operating systems.

28
Component Requirement

Other Some inking features require 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 2003 Server with SP1 or later that is
running Windows Rights Management Services.
Connectivity to Microsoft Exchange Server
2000 or later is required for some 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 that is running Windows SharePoint
Services 3.0 or Office SharePoint Server 2007
is required for some advanced collaboration
functionality. PowerPoint Slide Library requires
Office SharePoint Server 2007. Connectivity to
Office SharePoint Server 2007 is required for
browser-enabled Office InfoPath forms and
additional collaboration functionality. Office
Groove 2007 Messenger integration requires
Windows Messenger 5.1 or later or Microsoft
Office Communicator 1.0 or later. Includes 5-
year subscription to the Office Groove 2007
relay service.
Some features require Windows Desktop
Search 3.0, Windows Media Player 9.0,
Microsoft DirectX 9.0b, Microsoft Active Sync
4.1, microphone1, audio output device, video
recording device (such as a Web cam), TWAIN-
compatible digital camera or scanner, Windows
Mobile 2003 powered Smartphone or Windows
Mobile 5 powered Smartphone or Pocket PC, or
a router that supports Universal Plug and Play
(UPnP). Users must be on the same network to
share notebooks.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

Additional Requirements and product functionality may

29
Component Requirement

vary based on your system configuration and

operating system.

Microsoft Office Ultimate 2007

The following table lists the system requirements for Office Ultimate 2007.

Component Requirement

Computer and processor 500 MHz processor or higher. 2 GHz processor or

higher recommended for OneNote Audio Search.
Close-talking microphone required. Audio Search not
available in all languages. 1 GHz processor or
higher recommended for Business Contact Manager.

Memory 256 MB RAM or higher. 1 GB RAM or higher

recommended for OneNote Audio Search. Close-
talking microphone required. Audio Search not
available in all languages. 512 MB RAM or higher
recommended for Business Contact Manager.
Business Contact Manager not available in all
languages. 512 MB RAM or higher recommended
for Outlook Instant Search. Grammar and contextual
spelling in Office Word is not turned on unless the
computer has 1 GB memory.

Hard disk 3 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003 with

SP1, or later operating system. Send to OneNote
2007 print driver not available on 64-bit operating
systems. Office Groove 2007 Folder Synchronization
not available on 64-bit operating systems. Office
Clean-up wizard not available on 64-bit operating
systems.

30
Component Requirement

Other Some inking features require 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 2003 Server with SP1
or later that is running Windows Rights Management
Services.
Connectivity to Microsoft Exchange Server 2000 or
later is required for some 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 3.0 or
Office SharePoint Server 2007 is required for some
advanced collaboration functionality. PowerPoint
Slide Library requires Office SharePoint Server
2007. Connectivity to Office SharePoint Server 2007
is required for browser-enabled InfoPath forms and
additional collaboration functionality. Office Groove
2007 Messenger integration requires Windows
Messenger 5.1 or later or Office Communicator 1.0
or later. Includes 5-year subscription to the Office
Groove 2007 relay service.
Some features require Windows Desktop Search
3.0, Windows Media Player 9.0, Microsoft DirectX
9.0b, Microsoft Active Sync 4.1, microphone1, audio
output device, video recording device (such as a
Web cam), TWAIN-compatible digital camera or
scanner, Windows Mobile 2003 powered
Smartphone or Windows Mobile 5 powered
Smartphone or Pocket PC, or a router that supports
UPnP. Users must be on the same network to share
notebooks.
Internet Explorer 6.0 or later, 32-bit browser only.
Internet functionality requires Internet access. Fees
may apply.

Additional Requirements and product functionality may vary

based on your system configuration and operating
system.

31
Microsoft Office Accounting 2007
The following table lists the system requirements for Office Accounting 2007.

Component Requirement

Computer and processor 1 GHz processor or higher.

Memory 512 MB RAM or higher.

Hard disk 2 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

Other Microsoft Office Small Business Edition 2003 or

later is required to create customized invoices,
sales orders, quotes, customer credit memos,
customer statements, and purchase orders.
Microsoft Office XP or later is required to export
data to Microsoft Office Word or Excel.
Microsoft Office Outlook 2003 with Business
Contact Manager SP2 or later is required to
share financial data. The host computer must
run Windows Server 2003 SP1, Windows XP
Professional SP2, or later to share data among
multiple computers. Office Accounting analysis
pack requires Microsoft Office Excel 2003 and
Office Access 2003 or later. Online Accounting
Transfer requires Office Live.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply. Third-party services
are available for additional fees.

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

32
Note:
Microsoft Office Accounting 2007 is available in the U.S. only.

Microsoft Office Access 2007

The following table lists the system requirements for Office Access 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor. Office

Clean-up wizard not available on 64-bit
operating systems.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system1.

Other Connectivity to Windows Server 2003 with SP1

or later that is running Windows SharePoint
Services 3.0 is required for some advanced
collaboration functionality. Collecting data via e-
mail requires Office Outlook 2007.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office Excel 2007

The following components are required to use Office Excel 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

33
Component Requirement

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office InfoPath 2007

The following table lists the system requirements for Microsoft Office InfoPath 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

34
Component Requirement

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

Other Information Rights Management features

require access to a Windows 2003 Server with
SP1 or later that is running Windows Rights
Management Services.
Connectivity to Windows Server 2003 with SP1
or later that is running Windows SharePoint
Services 3.0 is required for some advanced
collaboration functionality. Office Outlook 2007
required for e-mail-based collaboration.
Sending forms as e-mail messages requires
Office Outlook 2007. Conversion of Office Word
documents requires Office Word 2007.
Conversion of Office Excel documents requires
Office Excel 2007. Office SharePoint Server
2007 required for browser-enabled Office
InfoPath forms and additional collaboration
functionality.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

35
Microsoft Office Groove 2007
The following table lists the system requirements for Office Groove 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 1 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Groove 2007 Folder Synchronization and some
other features not available on 64-bit operating
systems. Office Clean-up wizard not available
on 64-bit operating systems.

Other Integration with Windows SharePoint Services

requires connectivity to a computer running
Office SharePoint Server 2007 or Windows
SharePoint Services 3.0. Built-in Office InfoPath
2007 Forms Tool requires Office InfoPath 2007.
Office Groove 2007/messenger integration
requires Windows Messenger 5.1 or later or
Communicator 1.0 or later. Includes a 5-year
subscription to the Office Groove 2007 relay
service.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Important:
Installation of Office Groove 2007 upgrades your Office Groove account. There is no
support for downgrading or reverting to a previous version of your Office Groove account
after the upgrade process starts. Each computer must be upgraded to Office Groove

36
2007 to run Office Groove accounts on multiple computers. Review the readme
document for further information on Office Groove 2007 before you upgrade your
account.

Microsoft Office OneNote 2007

The following table lists the system requirements for Office OneNote 2007.

Component Requirement

Computer and processor 500 MHz processor or higher. 2 GHz processor

or higher recommended for OneNote Audio
Search. Close-talking microphone required.
Audio Search not available in all languages.

Memory 256 MB RAM or higher. 1 GB RAM or higher

recommended for OneNote Audio Search.
Close-talking microphone required. Audio
Search not available in all languages.

Hard disk 1 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Send to
OneNote 2007 print driver not available on 64-
bit operating systems. Office Clean-up wizard
not available on 64-bit operating systems.

Other Some features require Windows Desktop

Search 3.0, Windows Media Player 9.0,
Microsoft DirectX 9.0b, Microsoft Active Sync
4.1, microphone1, audio output device; video
recording device (such as a Web cam), TWAIN-
compatible digital camera or scanner, Windows
Mobile 2003 powered Smartphone or Windows
Mobile 5 powered Smartphone or Pocket PC, or
a router that supports Universal Plug and Play
(UPnP). Users must be on the same network to
share notebooks.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

37
Component Requirement

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office Outlook 2007

The following table lists the system requirements for Microsoft Office Outlook 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

38
Component Requirement

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office PowerPoint 2007

The following table lists the system requirements for Microsoft Office PowerPoint 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 1 GB. A portion of this disk space is free after

installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

39
Component Requirement

with SP1, or later operating system. Office

Clean-up wizard not available on 64-bit
operating systems.

Other Some inking features require Windows XP

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office Publisher 2007

The following table lists the system requirements for Microsoft Office Publisher 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit

40
Component Requirement

operating systems.

Other Some inking features require Windows XP

Tablet PC Edition or later. Speech recognition
functionality requires a close-talk microphone
and audio output device.
Publications can be sent using Office Outlook
2007, Outlook Express 6.0, or Windows Live
Mail. Recipients can view publications in a
variety of e-mail clients and Web-based
services.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office Word 2007

The following table lists the system requirements for Office Word 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher. Grammar and

contextual spelling in Office Word 2007 is not
turned on unless the computer has 1 GB of
memory.

Hard disk 1.5 GB. A portion of this disk space is free after
installation if the original download package is
removed from the hard drive.

Drive CD-ROM or DVD drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2, Windows Server 2003

with SP1, or later operating system. Office
Clean-up wizard not available on 64-bit
operating systems.

Other Some inking features require Windows XP

41
Component Requirement

Tablet PC Edition or later. Speech recognition

functionality requires a close-talk microphone
and audio output device.
Publications can be sent using Office Outlook
2007, Outlook Express 6.0, or Windows Live
Mail. Recipients can view publications in a
variety of e-mail clients and Web-based
services.
Internet Explorer 6.0 or later, 32-bit browser
only. Internet functionality requires Internet
access. Fees may apply.

Additional Requirements and product functionality may

vary based on your system configuration and
operating system.

Microsoft Office Multi-Language Pack 2007

The following components are required to use Office Multi-Language Pack 2007.

Component Requirement

Computer and processor 500 MHz processor or higher.

Memory 256 MB RAM or higher.

Hard disk 2 GB of hard disk space necessary for

installation. A portion of this hard disk space is
free after installation.
750 MB-1.5 GB of hard disk space per
language that is installed.

Drive DVD-ROM drive.

Display 1024 x 768 or higher resolution monitor.

Operating system Windows XP with SP2 or later, or Windows

Server 2003 or later.

Other One or more of the following 2007 Office

system products installed: Office Home and
Student 2007, Office Standard 2007, Office
Basic 2007, Office Small Business 2007, Office
Professional 2007, Office Professional Plus
2007, Office Enterprise 2007, Office Ultimate

42
Component Requirement

2007, Office Word 2007, Office Excel 2007,

Office Outlook 2007, Office PowerPoint 2007,
Office Access 2007, Office OneNote 2007,
Microsoft Office Visio 2007, Microsoft Office
Project 2007, Office InfoPath 2007, Microsoft
Office SharePoint Designer 2007, Office
Publisher 2007, Office Groove 2007.

More information
Servers and programs that are not included in the 2007 Office suites require higher system
memory and supporting software.
Refer to the Microsoft Office Enterprise Project Management (EPM) Solution system
requirements (http://go.microsoft.com/fwlink/?LinkId=93530) for details on requirements for the
EPM Solution, which includes Microsoft Office Project Professional 2007, Microsoft Office Project
Server 2007, Microsoft Office Project Web Access, Microsoft Office Project Portfolio Server 2007,
and Microsoft Office Project Portfolio Web Access.
Refer to the Microsoft Office Groove 2007 system requirements (http://go.microsoft.com/fwlink/?
LinkId=93531) for integration and deployment requirements for products such as Office Groove
2007 and Microsoft Office Groove Enterprise Services 2007.
Refer to the Microsoft Office SharePoint Server 2007 system requirements
(http://go.microsoft.com/fwlink/?LinkId=93532) for integration and deployment requirements for
products such as Office SharePoint Server 2007, Microsoft Office SharePoint Server 2007 for
Search, and Microsoft Office Forms Server 2007.

Migration from previous versions of Office

The 2007 Office system changes most likely to affect your migration from previous versions of
Office are in the following areas:
 Installing, customizing, and updating the 2007 Office system
 File format
 Security
 User Interface
 Object model
 Access 2007
 Excel 2007
 Outlook 2007
 Word 2007, PowerPoint 2007, and OneNote 2007

43
For information about feature changes, see Differences in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179054.aspx). For information about migrating to the
2007 Office system, see Migrating to the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc303380.aspx).

Installing, customizing, and updating the 2007 Office system

Previous versions of Office required several tools to customize Setup and to manage Office after
installation. As mentioned previously, the new Setup architecture in the 2007 Office system
simplifies the process of installing and maintaining Office. This change mainly affects
administrators, and is important to consider because it might represent a change in your
deployment methods.
 Installation. In the 2007 Office system, all language-neutral components are in one core
package, and all language-specific components are in separate packages. A basic 2007
Office release installation consists of the core package plus one language. Adding more
languages is as simple as copying additional language-specific packages to the network
installation point. All of the packages plug into the global core in exactly the same way. For
more information about the Setup architecture for the 2007 Office system, see Evaluating the
new Setup architecture (http://technet.microsoft.com/en-us/library/cc179189.aspx).
 Customization. You can use the Office Customization Tool (OCT), a component of Setup in
the 2007 Office system, to create a Setup customization file. You can use customization files
to configure the 2007 Office system for different groups of users. For more information about
configuration files, see Create different configurations of the 2007 Office system for different
groups of users (http://technet.microsoft.com/en-us/library/cc178950.aspx). For more
information about how to use the OCT, see Office Customization Tool in the 2007 Office
system (http://technet.microsoft.com/en-us/library/cc179097.aspx).
 Updates. In Microsoft Office 2003, you used an administrative installation point to install the
product. The 2007 Office system requires a local installation source. The process of
distributing software updates is more efficient and reliable, because a complete installation
source is always available on the local computer. In the 2007 Office system, you create a
network installation point that you never have to update, so client computers never become
out-of-sync with the installation source. Keeping new installations current is as simple as
copying updates to a folder on the network installation point. For more information about the
local installation source, see Required local installation source for the 2007 Office system
(http://technet.microsoft.com/en-us/library/dd162398.aspx#BKMK_ReqLIS). For more
information about updating Office, see Consolidated update process for the 2007 Office
system (http://technet.microsoft.com/en-us/library/dd162398.aspx#BKMK_ConsUpdProc).

File format
The default file format for Office Word 2007, Office Excel 2007, and Office PowerPoint 2007 has
changed to Extensible Markup Language (XML). This change is in response to customer
requests, and provides the following benefits:
 Enables more rapid document creation from different data sources

44
 Enables easier data mining and content reuse
 Reduces the size of Word, Excel, and PowerPoint files
 Improves data recovery in corrupted files
Several factors help to ease transition and coexistence issues with the new file format:
 The file formats used in Office 2003 and previous versions are still available in the 2007
Office system. You can change the default file format during deployment, or a user can
change the default file format after installation.
 Updates are available for Microsoft Office 2000, Office XP, and Office 2003 to enable
customers using older versions of Office to read, edit, and save files by using the new format.
 Converters are available for Office 2000, Office XP, and Office 2003. Customers using
previous versions of Office can open files created with the new file format.
 The Office Migration Planning Manager (OMPM) helps you assess the impact of the change
on your environment and allows bulk conversion of files.
For more information about the new file format, see File format reference for the 2007 Office
system (http://technet.microsoft.com/en-us/library/cc179118.aspx.) For more information about
file coexistence, see Collaborating with previous versions of Office and other programs
(http://technet.microsoft.com/en-us/library/cc179174.aspx.) For more information about OMPM,
see Migrating to the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc303380.aspx) and Office Migration Planning Manager reference for the 2007 Office
system (http://technet.microsoft.com/en-us/library/cc179211.aspx.)

Security
The Trust Center is new to the 2007 Office system, and hosts all security settings for Office
applications in one place. The Trust Center also provides a document action bar that replaces the
security prompts when a file opens. By default, potentially dangerous content is blocked in the file
without prompting, so there are no security decisions when the file opens. If content is blocked,
the document action bar appears and informs the user. Clicking the document action bar displays
a dialog box with 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.
This change requires user education and planning. For more information about security features
that have changed, see Differences in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179054.aspx.) For detailed information about planning for and deploying security
features for the 2007 Office system, see the resources in the Security and protection for the 2007
Office release section (http://technet.microsoft.com/en-us/library/cc179135.aspx.)

User Interface
Office Word 2007, Office Excel 2007, Office Access 2007, Office PowerPoint 2007, and Office
Outlook 2007 have 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

45
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. User education is required.
Most commands continue to work as before. There is minimal need to change macros or
application code due to the new ribbon interface. Because some commands are changed, see
Differences in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179054.aspx)
to determine whether you need to revise macros or application code.
For more information about the Microsoft Office Fluent user interface, see the Microsoft Office
Fluent User Interface Resource Center (http://go.microsoft.com/fwlink/?linkid=111045).

Object model
Because of improvements 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 are 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, see Differences in the 2007 Office
system (http://technet.microsoft.com/en-us/library/cc179054.aspx.)

Access 2007
Office Access 2007 introduces a new file format. While previous versions 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.
You can use the Office Custom Installation Wizard (CIW) to set a policy so that all new databases
default to the MDB format instead of ACCDB. This setting can be used to prevent users from
creating ACCDB files until your Office Access 2007 deployment is complete.
Users can convert their MDB databases to ACCDB format with the Convert Database command
on the Database tab of the ribbon in Office Access 2007. Once it is converted, the database can
only open in Office Access 2007. In Office Access 2007, users can use the Save Database As
option to save the database in a previous format. If the database was created as an ACCDB file,
and if it contains complex data, offline data, or attachments created in Office Access 2007, the
user cannot save the database as a prior version.
For more information about feature changes in Office Access 2007, see Changes in Access 2007
(http://technet.microsoft.com/en-us/library/cc179181.aspx.)

Excel 2007
In addition to the new user interface and file format changes, Office Excel 2007 features major
changes in the following areas:
 Grid size. The grid size for Office Excel 2007 worksheets is greatly expanded to 1,000,000
rows by 16,000 columns (compared to 65,536 rows by 256 columns in Office Excel 2003).

46
This change could result in Range Names that conflict with the new references, and can also
affect the ability to save a worksheet to a previous version.
 Formulas and functions. The Analysis ToolPak is integrated into Office Excel 2007 to improve
the installation process. This requires 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 of the
integrated functions might conflict with user-defined functions. Changes to statistical functions
provide more precision. With multi-threaded calculation, Office Excel 2007 provides increased
performance when it runs on computers with 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, rather than 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, rather than 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.
For more information about feature changes in Office Excel 2007, see Changes in Excel 2007
(http://technet.microsoft.com/en-us/library/cc179167.aspx.)

Outlook 2007
Office Outlook 2007 includes improvements in the Calendar, Tasks, and other features. One of
the biggest changes is that instead of using the Exchange Security Form (ESF), a custom form
for administering Office Outlook 2007 security options when you are connected to an Exchange
Server mailbox, you use Group Policy. This changes the method you use to lock down Office
Outlook 2007 in a network environment. Some situations still require use of the ESF, due to
Group Policy restrictions. For example, hosted Exchange situations still require using the ESF to
lock down Office Outlook 2007.
For more information about feature changes in Office Outlook 2007, see Changes in Outlook
2007 (http://technet.microsoft.com/en-us/library/cc179110.aspx.)

Word 2007, PowerPoint 2007, and OneNote 2007

There are changes that you should review for Office Word 2007, Office PowerPoint 2007, and
Office OneNote 2007 to determine whether files or applications might need modification during
migration. For more information about feature changes, see Differences in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179054.aspx.)

See Also
Concepts
Setup architecture overview for the 2007 Office system

47
Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179097.aspx)
Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179195.aspx)
Group Policy Overview (http://technet.microsoft.com/en-us/library/cc179176.aspx)
Enforce settings by using Group Policy in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179081.aspx)
Planning for migration to the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179048.aspx)
Migrating to the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303380.aspx)
Migration reference for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc178980.aspx)
Customize and deploy multiple language versions of the 2007 Office system
(http://technet.microsoft.com/en-us/library/dd162397.aspx)
Deploying the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303395.aspx)

48
Setup architecture overview for the 2007
Office system
In this article:
 Setup process
 Language-neutral design
 Streamlined customization model
 Required local installation source
 Consolidated update process
The Setup architecture in the 2007 Microsoft Office system has been designed to streamline all
aspects of installing, customizing, and maintaining Office. The new Setup program unifies and
manages the entire installation process, including customizing users' Office configuration,
deploying multiple languages at once, and applying software updates to new installations. This
article provides an overview of the changes in 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 changes in 2007 Office system help administrators manage areas such as the
following more efficiently:
 Deployment process so that Office installs 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 previous versions of Office, 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. In contrast, the 2007 Office system products consist
of multiple MSI files, and no single MSI file represents a complete product. In the 2007 Office
system, 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 Standard 2007 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.

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

Note:
Unlike previous versions of Microsoft Office products, the 2007 Office system does not
allow you to create an administrative installation point by running Setup with the /a
command-line option to extract compressed source files. Instead, all installations 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 initiates all the mechanisms of the installation process; it is located
at the root of the network installation point. You run Setup once for each Office product 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 presents the user with 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 Office Standard 2007, you can use the following command line:

50
\\server\share\Office12\setup.exe /config \\server\share\Office12\Standard.WW\Config.xml
where Office12 is the root of the network installation point.
In previous versions of Office, Setup.exe called Windows Installer (Msiexec.exe) to perform the
installation of 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 2007
Office system.

Note:
This version of Setup.exe recognizes only a few command-line options. For more
information, see Setup command-line options for the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc178956.aspx.)

Check prerequisites
When Setup starts, it checks for a number of installation prerequisites, including minimum
operating system requirements and administrative rights. 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 to run the installation with elevated privileges.
For more information about giving users administrative rights for an Office installation, see Deploy
the 2007 Office system to users who are not administrators (http://technet.microsoft.com/en-
us/library/cc178988.aspx.)

Read XML data

Setup gathers information about each package on the installation point, collects default settings
for the installation, and incorporates customizations you specify. Setup gathers 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,
StandardWW.xml for Office Standard 2007). Information in these files allows 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 required for the installation.

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 the 2007 Microsoft Office system. The OCT is part

51
of the Setup program and is the recommended tool for most customizations. The
customization file contains all the modifications you specify for an installation, including
customizations that control the installation process.
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. The Updates folder is included by default on the installation
point; in most cases, it is the recommended location in which to store both customization files
and software updates for all the Office products included on the installation point.
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 using the OCT, see Office Customization Tool in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179097.aspx.)
 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 the 2007
Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx.)

Build the feature tree

Setup uses the information 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 allow users to run Setup interactively, they view the feature tree with your
modifications in the Setup user interface.
For more information about specifying which Office features to install, see Configure feature
installation states of the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179043.aspx.)

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 location 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:

52
 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, allowing users to complete the Office installation with
no network connection.
For more information about the local installation source, see Required local installation source.

Install Office
When the installation begins, 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 entire installation process into account, including applying
customizations and software updates from the Updates folder.

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 is similar to 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. However, if you store more than one customization file for the same
product in the Updates folder, Setup applies all of the files to the user's configuration in
alphabetical order.
If you create different configurations for different groups of users, Microsoft recommends that you
store the customization files in another location and then use the /adminfile option on the Setup
command line to specify the file you want. For example:
\\server\share\Office12\setup.exe /adminfile
\\server\share\Office12\MyUpdates\Engineering.msp
where Office12 is the root of the network installation point.

53
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 way, 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 the
2007 Office system (http://technet.microsoft.com/en-us/library/cc179231.aspx.)

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 also need 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 entire process is a single event. This model preserves the original
installation point and still allows you to give new users the most up-to-date version of the product.

Note:
The Updates folder is used only for initial or new installations of the 2007 Office system.
The Updates folder can contain initial or baseline OCT MSP patches, OCT MSP
maintenance patches, and 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 2007 Office system 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.

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
2007 Office system 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.
For more information, see Sequentially install multiple products of the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179200.aspx.)

54
Running Setup interactively
You can choose to run the installation quietly, so that users see little or none of the process;
however, if you allow users to view the Setup user interface, the choices 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 with no command-line options, then Setup presents the user with 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 by default. However, if a user
chooses the Customize installation option, the Languages tab in the Setup interface
presents the user with 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 customizing display settings, see Customize Setup before installing the
2007 Office system (http://technet.microsoft.com/en-us/library/cc179121.aspx.)

Language-neutral design
In the 2007 Office system, an Office product such as Microsoft Office Standard 2007 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.
In this section:
 Language versions of Office
 Language packs for Office
 Installing multiple languages of Office
 Installing a default language on each user's computer
 Specifying one or more languages to install on users' computers
 Installing language packs separately
 Installing Proofing Tools
 Adding languages after Office is installed

55
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, that identifies the language.
For example, an installation point for Microsoft Office Standard 2007 with both U.S. English and
French language elements includes the following files and folders:
2007 Office system network installation point
 Setup.exe—Setup program
 Standard.WW folder—Language-neutral core product
 Office.en-us folder—U.S. English shared features
 Excel.en-us folder—U.S. English Excel features
 Outlook.en-us folder—U.S. English Outlook features
 PowerPoint.en-us folder—U.S. English PowerPoint features
 Word.en-us folder—U.S.English Word features
 Office.fr-fr folder—French shared features
 Excel.fr-fr folder—French Excel features
 Outlook.fr-fr folder—French Outlook features
 PowerPoint.fr-fr folder—French PowerPoint features
 Word.fr-fr folder—French Word features
Each folder contains a parallel set of installation files:
2007 Office system network installation point
 Setup.exe
 Standard.WW folder
 StandardWW.msi—Windows Installer package
 StandardWW.cab—Compressed cabinet file
 StandardWW.xml—XML data read by Setup.exe
 Setup.xml—XML data read by Setup.exe
 Config.xml—XML data read by Setup.exe
 Word.en-us folder
 WordMUI.msi—Windows Installer package
 WordLR.cab—Compressed cabinet file
 WordMUI.xml—XML data read by Setup.exe
 Setup.xml—XML data read by Setup.exe
 Word.fr-fr folder—French Word features
 WordMUI.msi—Windows Installer package
 WordLR.cab—Compressed cabinet file

56
 WordMUI.xml—XML data read by Setup.exe
 Setup.xml—XML data read by Setup.exe

Note:
These examples show only a portion of the network installation point. You might see
additional folders, all of which follow the same naming conventions show here.
The Office Standard 2007 product is spread out among the files in these folders. For example,
elements that are not specific to any language, such as Winword.exe (the executable file for
Microsoft Office Word 2007), reside in the core Standard.WW package. Other elements, such as
Help and the user interface for Office Word 2007, 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 Standard 2007 MSI file in the Standard.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 the 2007 Office system by detaching the language-
specific folder that contains the individual MSI file, such as the Word.en-us or Word.fr-fr folder.
You can, however, determine which applications and features are installed on users' computers
by customizing the installation.

Note:
None of the MSI files on an Office installation point can be installed independently by
using Windows Installer or any other method. Nor can the digitally-signed XML files
(Setup.xml and Package.xml) be edited or altered. In the 2007 Office system, 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. The French version of Office
Standard 2007 has a language-specific folder for each application and for shared features in
Office Standard 2007. The same folders are included in the French SLP, which also includes
language-specific folders for other products in the 2007 Office system.
For example, the Japanese language pack contains the following files and folders:
2007 Office system network installation point
 Setup.exe—Setup program

57
 Access.ja-jp folder—Japanese Access features
 Excel.ja-jp folder—Japanese Excel features
 Groove.ja-jp folder—Japanese Groove features
 InfoPath.ja-jp folder—Japanese InfoPath features
 Office.ja-jp folder—Japanese Shared Office features
 OneNote.ja-jp folder—Japanese OneNote features
 Outlook.ja-jp folder—Japanese Outlook features
 PowerPoint.ja-jp folder—Japanese PowerPoint features
 Publisher.ja-jp folder—Japanese Publisher features
 SharePointDesigner.ja-jp folder—Japanese SharePoint Designer features
 Word.ja-jp folder—Japanese Word features
 OMUI.ja-jp folder—Defines the language pack as a separate product
 XMUI.ja-jp folder—Identifies the particular culture for the language pack
Language-specific features for Microsoft Office Project 2007 are included in each SLP, but are
deployed separately. For example, the Japanese SLP also includes the following folders for Office
Project 2007:
2007 Office system network installation point
 Project.ja-jp folder—Japanese Project features
 PMUI.ja-jp folder—Defines the Project language pack as a separate product
Language-specific features for Microsoft Office Visio 2007 are handled in a similar way. For
example, the Japanese SLP includes the following folders for Office Visio 2007:
2007 Office system network installation point
 Visio.ja-jp folder—Japanese Visio features
 VMUI.ja-jp folder—Defines the Visio language pack as a separate product
All three language packs on a specific SLP share some common folders—the Office.ll-cc folder
(for shared Office features) and the XMUI.ll-cc folder (for culture definition). In the preceding
example, the Office.ja-jp and the XMUI.ja-jp folders are shared by Office, Visio, and Project
language packs.
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.

Note:
In previous versions of Office, 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 has been
simplified and improved in the 2007 Office system.

58
Installing multiple languages of Office
After you create a network installation point for Office, you can make any number of languages
available to users by copying language packs directly to the network installation point. Instead of
creating a series of installations, you can allow Setup to coordinate a single installation with
multiple languages.
For example, if your network installation point contains the U.S. English version of Office
Standard 2007, the French language pack, and the Japanese language pack, then Setup detects
that there is more than one language available for Office Standard 2007. During the installation,
Setup might combine the language-neutral core package with language-specific packages for
English, French, or Japanese, or for a combination of those languages. Only one product key is
required for the entire process; only one entry appears in Add or Remove Programs in the
user's Control Panel. When Setup creates the local installation source on the user's computer,
only the languages actually being installed are cached.
When you run the Office Customization Tool to customize the installation, the majority of your
customizations apply to the core product. This design allows Setup to apply the same
customization file (MSP file) to every installation, regardless of the language. The feature tree
displayed in the tool includes common features and a smaller number of language-specific
features for each language on the installation point. For more information, see Office
Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179097.aspx).

Note:
Before it installs a language version of an Office product, Setup determines whether the
user has the required operating system support for that language. Setup stops the
installation if there is no support. For example, if a user has not enabled support for East
Asian languages, Setup does not install the Japanese version of Office.

Installing a default language on each user's computer

When you install an Office product, Setup searches the installation point for all the possible
languages for that product. By default, Setup installs Office in the language that matches the
language specified by the user's Windows user locale. Without your having to control the process,
every user gets the most likely language of Office for his or her needs. A user in Paris might get
the Office Standard 2007 in French, while a user in London gets Office Standard 2007 in English,
and a user with a Japanese user locale gets Office Standard 2007 in Japanese.
If there is no exact match between the user locale and the set of available languages on the
installation point, Setup uses the closest match. If there is no acceptable match, Setup prompts
the user to select an available language. If you are running Setup in quiet mode (without user
interaction) and there is no acceptable language match, the installation fails.
If users run Setup interactively and choose the Install Now option, Setup follows the same
default pattern and installs the language version of Office that matches the user’s user locale
setting.

59
For step-by-step instructions about how to deploy multiple languages of Office, see Customize
and deploy multiple language versions of the 2007 Office system
(http://technet.microsoft.com/en-us/library/dd162397.aspx.)

Note:
Language packs cannot be deployed as products independent of a 2007 Office system
product. If the user has already installed at least one 2007 Office system product,
however, then Setup treats the language packs as products and includes them in the list
of products that the user can choose to install.

Specifying one or more languages to install on users' computers

You can override default behavior and specify exactly which languages Setup installs on users’
computers. In the Config.xml file located in the core product folder (Standard.WW for Office
Standard 2007), you can specify that Setup install a specific language or set of languages. Then
you use the /config command line option to point to your custom Config.xml file. For example:
\\server\share\Office12\setup.exe /config \\server\share\Office12\Standard.WW\MyConfig.xml
where Office12 is the root of the network installation point.
If users run Setup interactively and choose the Customize installation option, they can select one
or more languages to install on the Languages tab.

Important:

When you edit the Config.xml file to install more than language, you must also specify
which of those languages Setup uses for the shell user interface (Shell UI). The Shell UI
includes core elements of Office that register with the operating system, such as file
extensions, Tool Tips, and right-click menu items. Failure to specify a Shell UI language
in this scenario causes the installation to fail. For more information about managing the
deployment of multiple languages, see Customize and deploy multiple language versions
of the 2007 Office system (http://technet.microsoft.com/en-us/library/dd162397.aspx) and
Customize language settings for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179091.aspx.)

Installing language packs separately

Because a language pack is also defined as a unique product, you can install language packs
separately from Office. If you have already deployed a number of Office products in your
organization—for example, standalone versions of Microsoft Office Outlook 2007, Microsoft Office
Word 2007, and Microsoft Office OneNote 2007 — you can install the Japanese language pack
as a separate product and distribute Japanese components for all those products at once. In this
case, a separate entry appears in Add or Remove Programs for the Japanese language pack.

Note:
To install a language pack, users must first have an Office product installed. Although
Setup can install the language pack as a separate product, a language pack by itself

60
does not function as a complete 2007 Office system product. A core product is always
required.

Installing Proofing Tools

Proofing Tools allow users to enable additional languages for editing and to work with documents
in multiple languages. Each language pack (and each language version) includes Proofing Tools
for a set of companion languages. The enterprise edition of the Japanese language pack, for
example, includes Proofing Tools for English. Proofing Tools for each language are located in the
Proof.ll-cc folder at the root of the network installation point.
2007 Office system network installation point
 Proofing.ja-jp
 Proof.ar—Japanese Proofing Tools
 Proof.en—English Proofing Tools
You can distribute additional Proofing Tools in your organization. Proofing Tools for each
language are installed as separate packages (MSI files). The entire set of Proofing Tools is
included with the Microsoft Multi-language Pack. For more information about deploying Proofing
Tools in your organization, see Deploy Proofing Tools for the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179042.aspx.)

Adding languages after Office is installed

If you deploy Office first and then acquire additional language packs, you can add languages in
much the same way that you deploy multiple languages during the initial installation.
To add languages after you install Office, you rerun Setup from the network installation point. By
editing Config.xml for that product, you can specify that Setup add languages or that Setup match
the language to the user's operating system language. In this case, Setup modifies the existing
installation; it does not add the new language as a separate product.
For more information, see Add languages after deploying the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179145.aspx.)

Streamlined customization model

In previous versions of Microsoft Office, several tools were required to customize Setup and to
manage Office after installation. The 2007 Office system provides a consistent, streamlined
model. Administrators can use Setup to install, customize, and manage Office. To enforce specific
user settings, administrators can use 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

61
 Using Setup command-line options
 Using Group Policy

Using the Office Customization Tool

You customize an Office installation by using the Office Customization Tool, which is a component
of Setup. Start the OCT by running Setup with the /admin command-line option. Using the OCT,
create a Setup customization 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 the 2007 Office system.
A Setup customization file is an expanded form of a Windows Installer MSP file. Each file is
configured for a specific product, such as Microsoft Office Professional 2007 or Microsoft Office
OneNote 2007. When you run Setup to install an Office product, Setup looks in the Updates
folder for a customization file that corresponds to the product 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 more information, see Create different configurations of the 2007 Office system for different
groups of users (http://technet.microsoft.com/en-us/library/cc178950.aspx.)
For complete details on how to use the OCT to create a Setup customization file, see Office
Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179097.aspx.) To view the settings stored in Setup customization MSP files, see View
XML content from Office Customization Tool customization files (http://technet.microsoft.com/en-
us/library/cc178950.aspx.)

Customizing a new installation

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 allows you to 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 installing the 2007 Office
system.
 Determine which Office features are installed.
 Specify the default values for a large number of user options, including Microsoft Outlook
settings.

62
For information about how to customize Setup, see Customize Setup before installing the Office
2007 system (http://technet.microsoft.com/en-us/library/cc179121.aspx.)

Making changes to an existing Office installation

If you need to make changes to an existing Office installation, use the same tool 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 just 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.

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.
For more information about updating an existing Office installation, see Change users'
configurations after installing the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179141.aspx.)

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

Note:
If you specify both a Setup customization file and the Config.xml file, the customizations
you define in Config.xml take precedence over the same customizations in the
customization file.

63
For a complete description of the contents and format of the Config.xml file, see Config.xml file in
the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx.)

Using Setup command-line options

Setup recognizes only a few command-line options in the 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 to 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 the
2007 Office system (http://technet.microsoft.com/en-us/library/cc178956.aspx.) For information
about Windows Installer properties that were used in previous versions of Office, and about
properties that can be used when you install the 2007 Office system, see Setup properties in the
2007 Office system (http://technet.microsoft.com/en-us/library/cc179018.aspx.)

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 2007 Office system 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,
allowing administrators to create highly restricted or lightly managed configurations.
Administrators can use policy settings for the 2007 Office system applications to manage most
options that configure the Office user interface, including:
 Menu commands and their corresponding toolbar buttons
 Shortcut keys
 Most options in the Options dialog box

Note:
Most of the 2007 Office system 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

64
installation. Use Group Policy if you want to enforce specific configurations. Group Policy
settings have precedence over OCT settings.
For more information about Group Policy for the 2007 Office system, see Group Policy Overview
(http://technet.microsoft.com/en-us/library/cc179176.aspx), Enforce settings by using Group
Policy in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179081.aspx), and
Disable user interface items and shortcut keys (http://technet.microsoft.com/en-
us/library/cc179143.aspx).

Required local installation source

In the 2007 Microsoft Office system, Setup creates a local installation source on the user's
computer as part of the default installation process. Setup installs all 2007 Office system 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.

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 2007 Office system, 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 impact on the network and ensures that all users install the product and begin using 2007
Office system 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 with 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

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

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

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 ahead of time. For
example, 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 takes place on the local computer instead of over the network.
For more information, see Precache the local installation source for the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179231.aspx).
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, takes
place over the network. In this scenario, you must identify the subfolder in MSOCache\All Users

66
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 allows users to install Office without relying on a network connection.
For more information, see Run Setup from the local installation source to install the 2007 Office
system (http://technet.microsoft.com/en-us/library/cc179070.aspx).

Consolidated update process

In previous versions of Microsoft Office, 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 your client computers.
The new architecture of the 2007 Office system makes this process much simpler. 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 your network installation point. The existing files in the network installation
point remain the same as when you first copied them from the Office CD.

Note:
You can use the Updates folder to incorporate the installation of updates with an initial
installation of the 2007 Office system products. Only Windows Installer patch files
contained in this folder are installed with the initial installation, so you must extract the
patches from Microsoft Self-Extractor packages. You can also install customization
patches by using this method. For detailed information, see "Deploying software updates
with an initial 2007 Office system installation" in Distribute product updates for the 2007
Office system (http://technet.microsoft.com/en-us/library/cc178995.aspx).
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. 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.

67
Tip:
To direct Setup to look for software updates in a folder other than Updates, use the
SetupUpdates element in the Config.xml file. For more information, see "SetupUpdates"
in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179195.aspx).

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, by using Microsoft Windows Server
Update Services, or by updating computers directly from the Internet using Microsoft Update. For
information about deploying software updates after an initial installation of the 2007 Office release
by using Microsoft Self-Extractor files, see "Deploying all Microsoft Self-Extractor packages in a
folder" in Distribute product updates for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc178995.aspx). For details on keeping existing Office installations up to date, see
Distribute product updates for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc178995.aspx).

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.

Download this book

This topic is included in the following downloadable book for easier reading and printing:
 Planning and architecture for the 2007 Office release at http://go.microsoft.com/fwlink/?
LinkID=79592.
For a complete list of available downloadable books, see Downloadable content for the 2007
Office Resource Kit at http://technet.microsoft.com/en-us/library/cc178979.aspx.
See Also
Concepts
Specify language settings for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179091.aspx)
Preparing to deploy the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc303378.aspx)
Deploying the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303395.aspx)
Deploying internationally (http://technet.microsoft.com/en-us/library/cc303393.aspx)
Using enterprise deployment tools (http://technet.microsoft.com/en-us/library/cc303382.aspx)
Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179097.aspx)

68
Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179195.aspx)
Setup command-line options for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc178956.aspx)
Setup properties in the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179018.aspx)
Group Policy Overview (http://technet.microsoft.com/en-us/library/cc179176.aspx)
Enforce settings by using Group Policy in the 2007 Office system
(http://technet.microsoft.com/en-us/library/cc179081.aspx)
Distribute product updates for the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc178995.aspx)
Planning for migration to the 2007 Office system (http://technet.microsoft.com/en-
us/library/cc179048.aspx)
Migrating to the 2007 Office system (http://technet.microsoft.com/en-us/library/cc303380.aspx)

3BUR001977R3501 AdvaBld Admin
No ratings yet
3BUR001977R3501 AdvaBld Admin
174 pages
Planning and Architecture For Office SharePoint Server 2007, Part 1
No ratings yet
Planning and Architecture For Office SharePoint Server 2007, Part 1
630 pages
ORCAweb Administrator Guide V3.40
No ratings yet
ORCAweb Administrator Guide V3.40
113 pages
Microsoft Certified Systems Engineer
No ratings yet
Microsoft Certified Systems Engineer
3 pages
Printer Driver Packager NX - Operation Guide
No ratings yet
Printer Driver Packager NX - Operation Guide
76 pages
AM101638461033
No ratings yet
AM101638461033
172 pages
Tutorial Office 2010
100% (1)
Tutorial Office 2010
357 pages
OCS 2007 R2 Technical Reference For Clients
No ratings yet
OCS 2007 R2 Technical Reference For Clients
94 pages
Group Policy Overview For Office 2007: 2007 Office Resource Kit Technical Library
No ratings yet
Group Policy Overview For Office 2007: 2007 Office Resource Kit Technical Library
182 pages
For IT Professionals: Getting Started With Microsoft Office 2010
No ratings yet
For IT Professionals: Getting Started With Microsoft Office 2010
233 pages
Ork Group Policy
No ratings yet
Ork Group Policy
303 pages
97 03delta
No ratings yet
97 03delta
86 pages
Office 2010 Modul
No ratings yet
Office 2010 Modul
341 pages
First Look 2007 Microsoft Office System 1st Edition Katherine Murray pdf download
No ratings yet
First Look 2007 Microsoft Office System 1st Edition Katherine Murray pdf download
144 pages
Programming Applications For Microsoft Office Outlook 2007 Third Edition Randy Byrne Instant Download
No ratings yet
Programming Applications For Microsoft Office Outlook 2007 Third Edition Randy Byrne Instant Download
52 pages
Management Interfaces in Exchange Server 2007
No ratings yet
Management Interfaces in Exchange Server 2007
112 pages
Educating Information Workers About Exchange Server 2007
No ratings yet
Educating Information Workers About Exchange Server 2007
94 pages
First Look 2007 Microsoft Office System 1st Edition Katherine Murray PDF Download
No ratings yet
First Look 2007 Microsoft Office System 1st Edition Katherine Murray PDF Download
52 pages
The Ultimate Guide To Office 2010
100% (2)
The Ultimate Guide To Office 2010
164 pages
PDF Scanner 080924 9.38.50
No ratings yet
PDF Scanner 080924 9.38.50
3 pages
Office 2007 Group Policy and OCTSettings
No ratings yet
Office 2007 Group Policy and OCTSettings
1,912 pages
3359896
No ratings yet
3359896
27 pages
Group Policy For Microsoft Office 2010
No ratings yet
Group Policy For Microsoft Office 2010
259 pages
Word 2003 Productguide
No ratings yet
Word 2003 Productguide
42 pages
Windows Steady State Handbook
No ratings yet
Windows Steady State Handbook
81 pages
Office 2013 Grouppolicyandoctsettings
No ratings yet
Office 2013 Grouppolicyandoctsettings
410 pages
Office 2010 Windows 7
No ratings yet
Office 2010 Windows 7
84 pages
Office 2010 Inside Out
100% (1)
Office 2010 Inside Out
959 pages
Official Microsoft E-Learning Course: 2695 Computer Basics
No ratings yet
Official Microsoft E-Learning Course: 2695 Computer Basics
3 pages
Windows 7 Security Guide
No ratings yet
Windows 7 Security Guide
89 pages
Exploring Microsoft Office The Illustrated Practical Guide to Using Office and Microsoft 365 7 Exploring Tech Wilson instant download
No ratings yet
Exploring Microsoft Office The Illustrated Practical Guide to Using Office and Microsoft 365 7 Exploring Tech Wilson instant download
162 pages
Microsoft Office Outlook 2007 Inside Out 1ST Edition Jim Boyce Complete Edition
No ratings yet
Microsoft Office Outlook 2007 Inside Out 1ST Edition Jim Boyce Complete Edition
172 pages
Records Management Features
No ratings yet
Records Management Features
188 pages
Microsoft Office Outlook 2007 Inside Out 1ST Edition Jim Boyce available any format
No ratings yet
Microsoft Office Outlook 2007 Inside Out 1ST Edition Jim Boyce available any format
142 pages
Your PC, Simplified.: Retail Pocket Guide - Fall 2009
No ratings yet
Your PC, Simplified.: Retail Pocket Guide - Fall 2009
15 pages
Microsoft Office 2010 Deployment Guide
No ratings yet
Microsoft Office 2010 Deployment Guide
212 pages
Microsoft Office 365 Deployment Guide
100% (2)
Microsoft Office 365 Deployment Guide
201 pages
WSS PowerPoint Ch02
No ratings yet
WSS PowerPoint Ch02
75 pages
Microsoft - Windows 7 At-a-Glance Whitepaper
No ratings yet
Microsoft - Windows 7 At-a-Glance Whitepaper
10 pages
Computer ProjectM - Phil
No ratings yet
Computer ProjectM - Phil
70 pages
Common Features of Microsoft Office 2010
No ratings yet
Common Features of Microsoft Office 2010
37 pages
Office 2010 Bible 3rd Edition John Walkenbach download full chapters
No ratings yet
Office 2010 Bible 3rd Edition John Walkenbach download full chapters
151 pages
Mof SMF Overview
No ratings yet
Mof SMF Overview
106 pages
(Ebook) Microsoft Outlook 2010 Step by Step by Joan Lambert, Joyce Cox ISBN 9780735626904, 0735626901
No ratings yet
(Ebook) Microsoft Outlook 2010 Step by Step by Joan Lambert, Joyce Cox ISBN 9780735626904, 0735626901
81 pages
Microsoft Guide To Security Patch Management - Solutions For Management
No ratings yet
Microsoft Guide To Security Patch Management - Solutions For Management
157 pages
Trial Guide
No ratings yet
Trial Guide
81 pages
Office Cheat Sheet
No ratings yet
Office Cheat Sheet
2 pages
How to Use Microsoft Office XP 1st Edition Sherry Kinkoph updated 2025
No ratings yet
How to Use Microsoft Office XP 1st Edition Sherry Kinkoph updated 2025
151 pages
Governance Guide For Share Point
No ratings yet
Governance Guide For Share Point
30 pages
AF010163853
No ratings yet
AF010163853
411 pages
Software Update Services Overview: Microsoft Corporation Published: June 2002
No ratings yet
Software Update Services Overview: Microsoft Corporation Published: June 2002
27 pages
Microsoft Office 2010 Product Guide
No ratings yet
Microsoft Office 2010 Product Guide
188 pages
SIPLACE Pro V4.1 - Configurations - 12 - 2006 - EN
No ratings yet
SIPLACE Pro V4.1 - Configurations - 12 - 2006 - EN
18 pages
Active Directory Resume Sample
50% (2)
Active Directory Resume Sample
3 pages
B0700ey A PDF
No ratings yet
B0700ey A PDF
138 pages
PL2303 Windows Driver User Manual v1.14.0
No ratings yet
PL2303 Windows Driver User Manual v1.14.0
17 pages
Facility Commander End-User
No ratings yet
Facility Commander End-User
48 pages
AlvariSTAR 4 1 GA Release Note 090728
No ratings yet
AlvariSTAR 4 1 GA Release Note 090728
8 pages
Configure Distributed Monitor Email-Home Webex Remote Access
No ratings yet
Configure Distributed Monitor Email-Home Webex Remote Access
6 pages
Dell Equallogic SAN HQ Guide v2.2
No ratings yet
Dell Equallogic SAN HQ Guide v2.2
144 pages
EdgeSight Edocs
No ratings yet
EdgeSight Edocs
184 pages
HP Installation and Startup Service For HP BladeSystem C Class Infrastructure
No ratings yet
HP Installation and Startup Service For HP BladeSystem C Class Infrastructure
7 pages
Hasp Security
No ratings yet
Hasp Security
88 pages
S7-PCT - Readme
No ratings yet
S7-PCT - Readme
10 pages
Xcalibur Global 1.2 - Installation Guide
No ratings yet
Xcalibur Global 1.2 - Installation Guide
67 pages
PC Hardware Lab
No ratings yet
PC Hardware Lab
4 pages
Distributed File System (DFS)
No ratings yet
Distributed File System (DFS)
27 pages
TOOLBOX II Version 5.0 Installation Manual
No ratings yet
TOOLBOX II Version 5.0 Installation Manual
18 pages
Virtual Infrastructure Web Access Administrator'S Guide: Esx Server 3.0.1 and Virtualcenter Server 2.0.1
No ratings yet
Virtual Infrastructure Web Access Administrator'S Guide: Esx Server 3.0.1 and Virtualcenter Server 2.0.1
110 pages
Computer Professional
No ratings yet
Computer Professional
185 pages
TPM PD Guide
No ratings yet
TPM PD Guide
572 pages
PROII 8.1 Getting Started Guide
100% (3)
PROII 8.1 Getting Started Guide
139 pages
Microsoft Certificate Lifecycle Manager Quick Start Guide
No ratings yet
Microsoft Certificate Lifecycle Manager Quick Start Guide
8 pages
Vmware Manual
No ratings yet
Vmware Manual
512 pages
How To Determine The Appropriate Page File Size For 64
No ratings yet
How To Determine The Appropriate Page File Size For 64
6 pages
Installation Guide Valvelink Software
No ratings yet
Installation Guide Valvelink Software
130 pages
PI Release 4.0 e
No ratings yet
PI Release 4.0 e
9 pages
CCC Book (Course of Computer Concept)
94% (34)
CCC Book (Course of Computer Concept)
159 pages