Building MAPI applications on 32-bit and 64-bit platforms

Applies to: Outlook 2013 | Outlook 2016

This topic describes the actions that MAPI developers should take to change and rebuild 32-bit MAPI applications to run on a 64-bit platform, and 64-bit applications to run on a 32-bit platform. In this topic, a 64-bit platform is a computer installed with 64-bit Microsoft Outlook and 64-bit Windows, and a 32-bit platform is a computer installed with a 32-bit Outlook and 32-bit or 64-bit Windows.

Operating system and Office support for 64-bit Outlook

The term bitness refers to the distinction between 32-bit and 64-bit processor architectures and the associated compatibility of applications. In this topic, bitness is used to qualify the version of Windows, Microsoft Office, Outlook, or a MAPI application built to suit a 32-bit or 64-bit processor architecture of a computer, and possibly other applications that run on that computer.

Starting in Microsoft Office 2010, Outlook is available as a 32-bit and a 64-bit application. On the same computer, the bitness of Outlook depends on the bitness of the Windows operating system (x86 or x64), and of Microsoft Office, if Office is already installed on that computer. The following are some of the factors that determine the feasibility of installing a 32-bit or a 64-bit version of Outlook:

32-bit Office (and 32-bit Outlook) can be installed on a 32-bit or 64-bit version of the Windows operating system. 64-bit Office (and 64-bit Outlook) can be installed only on a 64-bit operating system.

The default installation of Office on a 64-bit version of the Windows operating system is 32-bit Office.

The bitness of an installed version of Outlook is always the same as the bitness of Office, if Office is installed on the same computer. In other words, a 32-bit version of Outlook cannot be installed on the same computer that already has 64-bit versions of other Office applications installed, such as 64-bit Microsoft Word or 64-bit Microsoft Excel. Similarly, a 64-bit version of Outlook cannot be installed on the same computer that already has 32-bit versions of other Office applications installed.

Preparing MAPI applications for 32-bit and 64-bit platforms

MAPI applications include standalone applications such as Microsoft Communicator and MFCMAPI, and service providers such as address book, store, and transport providers. For MAPI method and function calls to work in a MAPI application (with the exception of one Simple MAPI function, MAPISendMail), the bitness of the MAPI application must be the same as the bitness of the MAPI subsystem on the computer that the application is targeted to run on. The bitness of the MAPI subsystem, in turn, is determined by and always the same as the bitness of the installed version of Outlook. The following table summarizes the necessary actions to prepare MAPI applications to run on targeted computers configured with Office and Windows of various bitness.

The following sections further explain each scenario. For scenarios that require rebuilding the MAPI application, see Link to MAPI Functions for additional information regarding linking to and calling MAPI functions.

32-bit MAPI application and 32-bit Outlook

MAPI applications compiled for a 32-bit MAPI subsystem that is available in 32-bit versions of Outlook, including those versions prior to Microsoft Outlook 2013, continue to be supported on computers installed with 32-bit Outlook and a 32-bit or 64-bit Windows operating system. There is no specific action necessary for the application developers.

32-bit MAPI application and 64-bit Outlook

32-bit MAPI applications are not supported to run on a computer installed with 64-bit Outlook and 64-bit Windows. The application developer must update and rebuild the application as a 64-bit application for the 64-bit platform. This is because a 32-bit application cannot load a 64-bit Msmapi32.dll file. There are a small number of API changes that application developers must incorporate to build their code successfully for a 64-bit environment. MAPI header files have been updated with these changes to support the 64-bit platform. You can download these header files at Outlook 2010: MAPI Header Files. Developers can use this same set of MAPI header files to build both 32-bit and 64-bit MAPI applications.

64-bit MAPI application and 64-bit Outlook

64-bit MAPI applications are supported on computers installed with 64-bit Outlook and 64-bit Windows. There is no specific action necessary for the application developers.

64-bit MAPI application and 32-bit Outlook

64-bit MAPI applications are not supported to run on a computer installed with 32-bit Outlook and 32-bit or 64-bit Windows. The application developer must update and rebuild the application as a 32-bit application to work with 32-bit Outlook. Use the updated MAPI header files, which you can download at Outlook 2010: MAPI Header Files. Developers can use this same set of MAPI header files to build both 32-bit and 64-bit MAPI applications.

Exception: MAPISendMail

In general, a 32-bit MAPI application must not run on a 64-bit platform (64-bit Outlook on 64-bit Windows) without first being rebuilt as a 64-bit application, and a 64-bit MAPI application must not run on a computer installed with 32-bit Outlook and 32-bit or 64-bit Windows without first being rebuilt as a 32-bit application. Figure 1 shows an alert dialog box that would be displayed if either of these scenarios occurs.

Figure 1. Error message for most cross-bitness MAPI calls.

However, one function call among all Simple MAPI and MAPI elements, MAPISendMail, would succeed in a Windows-32-bit-on-Windows-64-bit (WOW64) or Windows-64-bit-on-Windows-32-bit (WOW32) scenario and would not result in the above alert. This WOW64 scenario only applies to Windows 7.

Figure 2 shows a WOW64 scenario in which a 32-bit MAPI application calls MAPISendMail on a computer installed with 64-bit Windows 7. In this scenario, the MAPI library makes a COM call to launch a 64-bit Fixmapi application. The Fixmapi application implicitly links to the MAPI library, which routes the function call to the Windows MAPI stub, which in turn forwards the call to the Outlook MAPI stub, enabling the MAPISendMail function call to succeed.

Figure 2. Processing MAPISendMail in a WOW64 scenario.

Windows Setup Supported Platforms and Cross-Platform Deployments

This topic describes the supported platforms and deployment scenarios for running for Windows Setup.

When you’re deploying different types of PCs, you can use Windows Setup as a way to choose between your images through the Windows Setup user interface to select a specific image. You can include images for a variety of hardware platforms (such as BIOS and UEFI, 32-bit and 64-bit PCs), and across different versions of Windows (such as Windows 8.1, Windows Server 2012 R2, and Windows 7).

You can also run Windows Setup through a script. Boot the PC to Windows PE, and then use the \sources\setup.exe file to specify your image.

Firmware considerations: BIOS vs. UEFI

For UEFI-based PCs that support booting into either UEFI or legacy BIOS modes, make sure your PC is booted into the correct firmware mode before starting Windows Setup. Otherwise, Windows Setup may set up the hard drive partitions incorrectly, or may abort the installation if the hard drives are preconfigured. For more information, see WinPE: Boot in UEFI or legacy BIOS mode.

Firmware: BIOS 32-bit and 64-bit

To set up a single environment or set of scripts that can deploy Windows to both 32-bit and 64-bit BIOS PCs, use a 32-bit version of Windows PE and a 32-bit version of Windows Setup.

The 64-bit version of Windows Setup does not run on the 32-bit version of Windows PE.

To install a 64-bit version of Windows from a 32-bit version of Windows PE:

Boot the PC using the 32-bit version of Windows PE.

Use any of the following techniques to install a 64-bit version of Windows:

Run a 32-bit version of Windows Setup, and use the /InstallFrom command-line option to select a 64-bit Windows image:

Run a 32-bit version of Windows Setup, and use the Microsoft-Windows-Setup\ImageInstall\OSImage\ InstallFrom unattend setting to select a 64-bit Windows image.

Use image-capturing tools to apply a 64-bit version of Windows to the PC.

WarningВ В This procedure does not support deploying Windows 7.

Using Windows Setup to Install Previous Versions of Windows

You can use the Windows 8.1 and WindowsВ Server 2012 R2 versions of Windows Setup to install previous versions of Windows:

WindowsВ Server 2012 R2

Windows ServerВ 2012

Windows ServerВ 2008В R2

Windows ServerВ 2008

Windows XP with SP3

Windows Server 2003 R2 and previous versions

Windows XP with SP2 and previous versions

You can also run Windows Setup from the Windows Preinstallation Environment (WindowsВ PE). The following table lists the supported WindowsВ PE environments:

Windows 8.1 Setup

WindowsВ 8 Setup

WindowsВ 7 Setup

WindowsВ Vista Setup

Cross-Platform Deployment

Cross-platform deployment is the process of installing a specific architecture of Windows from an environment of a different architecture. For example, you can deploy a 64-bit edition of Windows 8.1 or WindowsВ 8 from a 32-bit edition of WindowsВ PE. The benefit of using a cross-platform deployment solution is that you don’t have to maintain multiple versions of WindowsВ PE for installing different architecture editions of Windows. You can build a single WindowsВ PE image that you can use to install both 32-bit and 64-bit editions of Windows.

When you install a 64-bit edition of Windows from a 32-bit version of WindowsВ PE, you must use WindowsВ PEВ 2.0 or a later version. For more information about WindowsВ PE releases, see WinPE for Windows 10.

The following table lists the different architecture types of Windows images (32-bit or 64-bit) that a specific version of Windows 8.1 Setup is able to install.

64-bit Windows 8.1 Setup

32-bit Windows 8.1 Setup

Limitations of cross-platform deployment

These cross-platform deployment scenarios aren’t supported:

Installing a 64-bit Windows image on a 32-bit computer.

Deploying a 32-bit Windows image from a 64-bit preinstallation environment.

Using a 32-bit version of Windows Setup to upgrade a 64-bit operating system.

Using a 32-bit version of WindowsВ 8 Setup to deploy a 64-bit version of the WindowsВ 7 operating system.

For example, you must use a 64-bit version of WindowsВ 8 Setup to deploy a 64-bit version of WindowsВ 7. In previous releases, the version of Windows Setup version had to match the operating system that you would deploy. For example, you had to use the WindowsВ 7 Setup.exe to install WindowsВ 7.

Using Microsoft Internet SCSI (iSCSI) boot disk in a cross-platform deployment scenario.

For example, installing Windows (64-bit version) from cross-platform media, such as Windows PE (32-bit version), to an iSCSI boot disk is unsupported. You must use the same architecture for Windows PE as the target deployment architecture when you deploy Windows to an iSCSI boot disk.

On Unified Extensible Firmware Interface (UEFI), deploying a 64-bit edition of Windows from a 32-bit version of WindowsВ PE. On some UEFI computers, you can’t install Windows in BIOS-compatibility mode and must switch to UEFI-compatibility mode. For more information, see Boot to UEFI Mode or Legacy BIOS mode.

Performing cross-platform deployments, except as part of a clean installation, or performing a Windows Deployment Services deployment.

Providing cross-platform installation media to users for recovery.

To prevent users from installing the wrong edition of Windows for the architecture of their computer, don’t provide cross-platform installation media to users for recovery or reinstallation. Also, the Windows Recovery Environment (WindowsВ RE) feature that’s included on the media applies only to 32-bit Windows installations.

Creating a .wim file for multiple architecture types

If a .wim file contains both 32-bit and 64-bit Windows editions, you must select the Windows image that you want to install. Typically, Windows Setup uses the product key that you specify in the ProductKey setting to determine which Windows image to install. But if the file contains 2 editions of the same Windows version, like Windows 8.1 Pro, you must use the MetaData setting in an answer file to specify the edition to install.

To choose an image, specify metadata that corresponds to the image index, name, description, or architecture type. For the metadata for architecture type, use 0В for 32-bit editions and 9В for 64-bit editions. For more info, see the MetaData В Key setting.

The answer file must include processor-specific components. The answer-file settings in the windowsPE configuration pass must match the architecture type of the preinstallation environment. The settings that apply to the Windows image must match the architecture type of the image. For example, if you create an answer file that deploys 64-bit images from a 32-bit preinstallation environment, all components in the answer file for the windowsPE configuration pass must include the processor attribute type of x86. Settings to be applied in the specialize, oobeSystem, or other configuration passes must include the processor attribute type of amd64.

Installing 64-bit drivers

All drivers that are included with Windows are signed. In cross-architecture deployments, you can use an out-of-box device driver. But if you use an unsigned out-of-box device driver that’s boot critical in a 64-bit installation, the installation may become unusable.

You can install 64-bit drivers for a Windows image during WindowsВ Setup in either of these ways:

In attended installations, you can press F6 or click the Load Driver button on the Disk Configuration page of Windows Setup.

In unattended installations, you can use the Microsoft-Windows-PnpCustomizationsWinPE or Microsoft-Windows-PnpCustomizationsNonWinPE component in an answer file to specify a driver path. For more information about how to automate your installation, see Automate Windows Setup.

Hardware considerations: Encrypted Hard Drives (e-Drives)

We added support for Encrypted Hard Drive Devices (also known as E-Drives) in WindowsВ 8, Windows ServerВ 2012, and WindowsВ PE 4.0.

To install a previous version of Windows (examples: WindowsВ 7 or WindowsВ Vista) to an Encrypted Hard Drive Device, use WindowsВ PE 4.0 or later.

Вам также может понравиться

Windows или Linux: Что лучше выбрать?

Есть много причин выбирать между Windows и Linux, но

Файл владелец изменить linux

Команда Chown в Linux Chown Command in Linux (File

Установка шлюза по умолчанию linux

Настройка сети вручную Содержание Краткое описание

Чем разбить диск для linux

ИТ База знаний Курс по Asterisk Полезно — Узнать IP —