64-bit Client Installation of Microsoft Office 2010

Overview Supported scenarios Deployment considerations

Processors that are 64-bit are becoming the standard for systems
that range from servers to desktop computers. 64-bit systems can
use more virtual and physical memory than 32-bit systems. This
lets users work with much larger data sets than they could
previously, and to analyze and solve large computational problems.
Microsoft Office 2010 introduces native 64-bit versions of Microsoft
Office products to take advantage of this larger capacity, but many
users of Office are unlikely to require the 64-bit version. For
example, this additional capacity is needed only by those Microsoft
Excel users who require Excel spreadsheets that are larger than 2
gigabytes (GB).
The 32-bit version of Office 2010 provides the same functionality
and is also compatible with 32-bit add-ins. Therefore, the 32-bit
version of Office 2010 is installed by default.
Office 2010 also provides support for running 32-bit Office 2010
applications on 64-bit Windows operating systems by using
Windows-32-on-Windows-64 (WOW64). WOW64 is the x86
emulator that enables 32-bit Windows-based applications to run
seamlessly on 64-bit Windows systems. Office 2010 lets users
continue to use existing 32-bit Microsoft ActiveX Controls,
Component Object Model (COM) add-ins, and Visual Basic for
Applications (VBA).
Supported 64-bit Windows operating systems
The supported Windows operating system editions for 64-bit
Office 2010 client include:
· 64-bit editions of Windows Vista with Service Pack 1
· 64-bit editions of Windows 7
· 64-bit editions of Windows Server 2008 with SP1
· 64-bit editions of Windows Server 2008 R2
Notes:
· The 64-bit Office client can be installed only on 64-bit editions of
Windows Vista with Service Pack 1, 64-bit editions of Windows
Server 2008 with Service Pack 1, Windows 7, and Windows
Server 2008 R2.
· The 32-bit Office client is the default installation on 64-bit
Windows operating systems. It is installed as a WOW64
installation.
· Office 2010 server products (Microsoft SharePoint Server 2010,
Microsoft SharePoint Foundation 2010, and Microsoft Project
Server 2010) support the 64-bit edition of Windows Server 2008
with Service Pack 2, and Windows Server 2008 R2.
· For click-to-run scenarios on supported 64-bit operating
systems, the only supported version is Office 2010 32-bit
(WOW64).
Architecture-specific folders and
customization tools
The Office 2010 DVD sources include two architecture-specific
folders: one for 32-bit systems and one for 64-bit. A separate
Config.xml file and Updates folder is included in each of these
folders.
A 64-bit version of the Office Customization Tool (OCT) is also
included. The 64-bit version of the OCT provides the same user
interface, capabilities, and configurable settings as the 32-bit
version. The following figure shows the architecture-specific folders.
For the latest information, see “64-bit editions of Office 2010” in the
Office 2010 Resource Kit.
32-bit Office on 64-bit Office on 32-bit Office on Advantages Disadvantages General feature deprecations
Scenario 64-bit operating 64-bit operating 32-bit operating
system system system The following section lists feature deprecations.
Running Office 2010 64-bit provides the following advantages: The following issues might affect compatibility.
· Ability to utilize additional memory.
Microsoft Access MDE/ADE/ACCDE files Microsoft Access
Enterprise Default  
· Excel 2010 can load much larger workbooks. Excel 2010 made updates to use 64-bit Databases that have had their source code removed (such as .mde, .ade, and .accde files) cannot be The Replication Conflict Viewer is removed from both the 32-bit and 64-bit installations of Office 2010. This
memory addressing to break out of the 2-GB addressable memory boundary that limits moved between 32-bit and 64-bit editions of Office 2010. Such databases that are created by using 32-bit functionality can still be implemented by using a documented custom function, ReplicationConflictFunction.
32-bit applications. Office (any version) can be used only with 32-bit Office, and a database that is created on 64-bit Office can For information, see the Access 2007 Developer Reference (http://go.microsoft.com/fwlink/?LinkId=150854).
be used only on 64-bit Office.
Default · Microsoft Project 2010 provides improved capacity, especially when you are dealing
Retail  
with many subprojects to a large project. Publisher
ActiveX controls and COM Add-ins The Microsoft Works database converter (wdbimp.dll) is removed from both 32-bit and 64-bit installations of
· Enhanced default security protections through Hardware Data Execution Prevention
ActiveX controls and add-in (COM) DLLs (dynamic link libraries) that were written for 32-bit Office will not Office 2010. This converter was previously used in the Mail Merge functionality to connect to a data source
(DEP).
work in a 64-bit process. As a result, Office 2010 64-bit solutions that try to load 32-bit ActiveX controls or created in Microsoft Works.
Upgrades  Not supported  DLLs will not work. 64-bit Office 2010 installations will only run 64-bit controls. Computers can have 64-bit
and 32-bit controls installed and Microsoft Office 2010 64-bit can only run the 64-bit versions of the controls. Word
Microsoft Office Document Imaging (MODI) and all its components are deprecated for both 32-bit and 64-bit
The workaround for resolving these issues is to obtain 64-bit compatible controls and add-ins or to install
Office 2010. The legacy Equation Editor is not supported on 64-bit Office 2010, but is supported for 32-bit
Office 2010 32-bit (WOW).
Office 2010 installations (WOW64).
In addition to controls that load into Office applications, there are also Web-based solutions that use ActiveX
WLL (Word Add-in libraries) WLL files are deprecated for both 32-bit and 64-bit Office 2010. A WLL is an
controls in Microsoft Internet Explorer. Office 2010 64-bit editions install some Office 32-bit client-side
add-in for Microsoft Word that you can build with any compiler that supports building DLLs.
controls for supporting solutions in a 32-bit browser (the default browser on current 64-bit Windows
systems). The Edit in Datasheet View functionality is not supported if you install Office 2010 64-bit clients.
The Datasheet View functionality is available if you install Office 2010 32-bit. Considerations for MAPI applications
If you developed and installed 32-bit Messaging Application Programming Interface (MAPI) applications,
In-place activation there are actions that you should take to change and rebuild 32-bit MAPI applications to run on a 64-bit
The following issues might occur if there is not a match between the bitness of Office 2010 and registered platform. This also applies for 64-bit applications to run on a 32-bit platform.
applications: Starting with Office 2010, Outlook is available as a 32-bit application and a 64-bit application. The version
· An OLE server may not instantiate in place and may fail to open if the application registered is not the (bitness) of Outlook that you choose depends on the edition of the Windows operating system (32-bit or 64-
bit) and the edition of Office 2010 (32- or 64-bit) that is installed on the computer, if Office is already installed
same bitness as the version of Office installed. For example, if your OLE Server application is 32-bit and
the version of Office installed is 64-bit. on that computer. The bitness of an installed version of Outlook is always the same as the bitness of Office
2010, if Office is installed on the same computer. A 32-bit version of Outlook 2010 cannot be installed on the
· Inserting an object into an Office 2010 application document may fail in cross-bitness scenarios. For same computer on which 64-bit versions of other Office 2010 applications are already installed, such as 64-
example if you insert a 32-bit object in a 64-bit Office 2010 application document. bit Microsoft Word 2010 or 64-bit Microsoft Excel 2010. Similarly, a 64-bit version of Outlook 2010 cannot be
installed on the same computer on which 32-bit versions of other Office applications are already installed.
Graphics rendering
There are differences between the 32-bit and 64-bit Graphics Device Interface (GDI) that might have MAPI applications include stand-alone applications such as Microsoft Communicator and MFCMAPI, and
performance implications because of the lack of MMX support on 64-bit. Intel's MMX technology is an service providers such as address book, store, and transport providers. For MAPI method and function calls
extension of the Intel architecture (IA) instruction set. The technology uses a single-instruction, multiple-data to work in a MAPI application (except for one Simple MAPI function, MAPISendMail), the bitness of the MAPI
(SIMD) technique to speed up multimedia and communications software by processing data elements in application must be the same as the bitness of the MAPI subsystem on the computer on which the
parallel. application is targeted to run. The bitness of the MAPI subsystem, in turn, is determined by and is always the
same as the bitness of the installed version of Outlook. For information about how to prepare MAPI
Visual Basic for Applications (VBA) applications for 32-bit and 64-bit platforms, see “Building MAPI Applications on 32-bit and 64-bit Platforms”

Tasks: Installing native 64-bit

VBA code that uses the Declare statement to access the Windows application programming interface (API) (http://go.microsoft.com/fwlink/?LinkId=165489).
or other DLL entry points will see differences between 32-bit and 64-bit versions. The Declare statement
must be updated with the PtrSafe attribute after inputs and outputs to the API have been reviewed and

Office 2010 in enterprise

updated. Declare statements will not work in 64-bit VBA without the PtrSafe attribute. New data types are
added to 64-bit Office 2010 VBA: LongLong and LongPtr.

environments Office 2010 64-bit Setup processes

This section highlights the tasks to perform when installing 64-bit Office 2010 in an
enterprise. The Setup sequence for a 64-bit Office client installation is as follows. The sequence is the same as for a standard
32-bit Office client installation with the addition of specific checks done for 64-bit Office 2010, as shown in the
diagrams in this section. For more information, see “64-bit editions of Office 2010” in the Office 2010 Resource Kit.
Verify that Uninstall 32-bit
Determine if 32-
computers meet Office
Prepare 64- bit Office Create network
hardware applications
bit installation applications are installation point
requirements for before running
installed
64-bit Office 64-bit setup
Office 2010 Setup platform chooser: Running Setup.exe from root folder Running Office 2010 Setup.exe from x64 folder Running Office 2010 Setup.exe from x86 folder: 64-bit setup sequence
from 64-bit operating system: Setup checks Setup checks
Check for 64-bit
Office 2010
Run Setup.exe prerequisites
32-bit Office 64-bit Office
applications No applications No
installed? Install 64-bit edition installed? Install 32-bit edition
32-bit edition of Windows 64-bit edition of Windows
of Office 2010 of Office 2010
Read XML data
Determine Yes Yes
Windows
Use 64-bit OCT Use Config.xml Configure user operating
Configure 64-
to customize (x64 folder) to settings through Install Office system edition
bit installation
installation customize setup Group Policy 2010 32-bit
Build feature tree
Yes Error message displays to Error message displays.
inform users they must Setup is blocked if Office
Install Office 64-bit Office 2010 64-bit is detected
uninstall all 32-bit Office
2010 64-bit application when users try to install
applications if they want to
installed? Office 2010 by running the
install Office 2010 64-bit. Create local
Error lists installed 32-bit 32-bit version of setup (from installation
No Office applications. the x86 folder). source

Install Office
Test 64-bit Install Office
configuration Test deployment method you will use to deploy 2010 32-bit
in non-
production Note: Office 2010 32-bit is the default install on
environment a 64-bit Windows operating system (uses
WOW). Also applies if upgrading existing 32-bit Apply 64-bit
Office installation. customization
Precache local Run Setup from Use enterprise MSP file
Run Setup.exe
installation local installation deployment tool
from x64 folder
source source to install

Apply software
updates

Install 64-bit
Office 2010 Choose deployment method based on testing
in production
environment

Precache local Run Setup from Use enterprise

Run Setup.exe
installation local installation deployment tool
from x64 folder
source source to install

Enterprise software deployment options include:

● Installing from network share

● Enterprise software distribution tools such as:

● Systems Management Server

● System Center Configuration Manager

● Microsoft System Center Essentials

● Group Policy Computer Startup Scripts

● Windows Server Terminal Services

© 2010 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at FeedORK@microsoft.com.