Microsoft® Office Outlook® Connector for IBM Lotus Domino is an Outlook 2002 and Office Outlook 2003 add-in that allows users to access an IBM Lotus Domino R5 or R6 server for features such as e-mail messaging, calendaring and scheduling, the address book, and To Do (task) items. This add-in replaces the Outlook 2002 Connector.

This add-in is particularly useful in environments with mixed e-mail infrastructures and in companies where employees would like the option to use Outlook 2002 or Outlook 2003 with Domino mail servers. The add-in can be installed and used on any machine properly licensed for Outlook 2002, Outlook 2003, Microsoft Office XP or the Microsoft Office System.

Toolbox   The Microsoft Office Outlook Connector for IBM Lotus Domino (olconn2.exe) replaces the Microsoft Outlook 2002 Connector. The new version works with Microsoft Outlook 2002 and Microsoft Office Outlook 2003, and it includes a number of enhancements. The files for Microsoft Outlook Connector for Domino are packaged in a self-extracting executable (olconn2.exe). You can find this downloadable file on the Office XP Resource Kit Downloads page.

The section “Localized versions of the add-in” below will be updated soon with a list of languages for which the new version of the Outlook Connector is available.

Microsoft Outlook Connector for Domino does not do the following:

• Enable any Lotus Notes features that are not present in Outlook 2002 or Outlook 2003, such as access to Notes databases and applications.
• Allow you to have an Exchange account and a Microsoft Outlook Connector Domino account in the same user profile.
• Provide Outlook features that are not currently supported by Domino, such as message recall.

Refer to the Readme and User Guide provided with the product for a full description of the capabilities and limitations of Microsoft Outlook Connector for Domino.

The Microsoft Outlook Connector for Domino is covered by the mainstream support lifecycle policies described on http://support.microsoft.com/lifecycle. Microsoft will only support this product when the add-in is installed with Outlook 2002 or Outlook 2003 and is used with any R5 or R6 release of the Lotus Domino server and Lotus Notes client.

Note   Outlook Connector for Domino does not work with Lotus Notes releases 6.0.2 CF1 and 6.0.2 CF2. When these releases are used with Outlook Connector for Domino, attachments larger than 32 KB get corrupted when received.

You can deploy Microsoft Outlook Connector for Domino — and configure a new Outlook profile to access the Domino server — in the following ways, depending on your organization’s deployment practices and whether Office is installed:

• Chain the add-in with an Office XP or Office 2003 installation by using a modified Office Setup.ini file together with a customized Office transform (MST file).
• Distribute the add-in installation file (Msocsetup.exe) separately to run on users’ computers, and distribute a configuration maintenance file (CMW file) created by using the Custom Maintenance Wizard to apply to users’ computers.
• Use Group Policy (this method requires the Active Directory® directory service).

Note   As with a standard Office installation, you must have administrative rights to the computer or run Office Setup with elevated privileges to install Microsoft Outlook Connector for Domino. For more information about installing with elevated privileges, see the Office Resource Kit topic Installations That Require Elevated Privileges.

This article provides an overview of Office deployment, with links to the Office Resource Kit for more detailed information. Furthermore, it provides step-by-step deployment procedures for the deployment strategies listed above.

You download Olconn2.exe from the Office Resource Kit Toolbox to a local computer that has at least 5 MB of hard disk space. You can then extract the files to a network share folder (for example, to a Microsoft Office administrative installation point) by typing the following at a command prompt:

Olconn2.exe /C /T:foldername

where foldername is the network share folder. The /C option specifies extraction only (Setup does not begin).

Note   Extracting these files to a folder on your Office administrative installation point will make it simpler to use the files during deployment.

The following table describes the files included in Olconn2.exe.

Software requirements for Microsoft Outlook Connector Domino

To deploy and use Microsoft Outlook Connector for Domino requires specific operating system versions and other software on the server and client computers. Furthermore, you must be using Windows Installer version 2.0 or later to deploy the add-in.

Note  Windows Installer version 2.0 is included with Office XP, Office 2003, Outlook 2002, and Outlook 2003.

There must be at least 5 MB of hard disk space available on the client computer to install Microsoft Outlook Connector for Domino.

The Readme file included in the download package includes information about specific product limitations.

Server software requirements

To use Microsoft Outlook Connector for Domino with Lotus Notes, the Lotus Domino R5 or R6 server that hosts Lotus Notes must be running on one of the following operating systems:

• Microsoft Windows® Server 2003
• Microsoft Windows® 2000
• Microsoft Windows NT®
• Red Hat Linux
• IBM AIX
• Hewlett-Packard HP-UX
• Sun Solaris-Sparc
• Sun Solaris (Intel Platform Edition)

Client software requirements

To install Microsoft Outlook Connector for Domino on client computers, the software listed below must be installed on the client:

One of the following versions of the Microsoft Windows operating system:

• Microsoft Windows XP (recommended)
• Microsoft Windows Server 2003
• Microsoft Windows 2000

and one of the following:

• Microsoft Office Outlook 2003
• Outlook 2003 with Service Pack 1 (not yet released)
• Microsoft Outlook 2002
• Outlook 2002 with Service Pack 2

and

• Lotus Notes R5 or R6

  ---

  Note   You must have the Lotus Notes client already installed on client computers before installing Microsoft Outlook Connector for Domino. The Notes client must also already be configured to use the Domino R5 server that Outlook will be accessing through Microsoft Outlook Connector for Domino. An Outlook profile will be configured to allow Microsoft Outlook Connector for Domino to access the same Domino server by using the user’s account information included in the Notes.ini configuration file.

  ---

Files installed for the add-in

When you install Microsoft Outlook Connector for Domino, the Setup program (Msocsetup.exe) installs the files listed in the following table.

Testing the add-in

If you want to test Microsoft Outlook Connector for Domino on your computer before deploying it to users in your organization, you can install Microsoft Outlook Connector for Domino on your local computer by running Msocsetup.exe.

To install Microsoft Outlook Connector for Domino

1. Extract the Microsoft Outlook Connector for Domino files from Olconn2.exe.
2. At a command prompt, type the following:

   Msocsetup.exe /i Msoc.msi /qn
   
   

   
   

This assumes that Msocsetup.exe and Msoc.msi are in your local directory. Otherwise you must include the full folder path for both files.

Later you can uninstall Microsoft Outlook Connector for Domino if you no longer need it. At a command prompt, type the following:

Msocsetup.exe /x Msoc.msi /qn

Note that Msocsetup.exe is a Windows Installer program and supports all of the command-line options supported by Windows Installer.

Using the add-in with multilingual users

Outlook Connector for Domino will be able to be used with a number of languages at a later date. If you are upgrading from using the add-in with Outlook 2002 to using Outlook 2003, you can also ensure that multilingual data is stored properly in Outlook by converting your ANSI store (NST file) to Unicode. The steps for converting NST files to Unicode are provided following the list of localized versions of the add-in.

Localized versions of the add-in

In addition to English, you can currently deploy the previous version of the connector, Outlook 2002 Connector, with localized versions of Office or with Office with Multilingual User Interface (MUI) Pack. (Localized versions of Outlook Connector for Domino will be released at a later date.) For more information about deploying a localized version of Office or Office with a MUI Pack, see Deploying Office Internationally.

The following localized versions of the Outlook 2002 Connector are available from the Office XP Resource Kit Localized Downloads page:

Converting NST files to Unicode to store multilingual data

When you use Outlook Connector for Domino with Outlook 2003, you can take advantage of Unicode support for Outlook data files to store multilingual data. To convert users with existing data files from Outlook 2002 to Unicode data files, you delete the existing ANSI NST data file and restart Outlook. Outlook detects that the NST file is missing and creates a new one, which is Unicode by default.

To convert users with ANSI data files to use Unicode files

1. In Outlook, click Tools, then under Send/Receive, click Synchronize Domino Mailbox. This ensures that the user’s Domino mailbox is up-to-date with the server.
2. Back up any non-mail items (such as Calendar, Contacts, Tasks, and so on) from existing Domino folders to an Outlook PST file. For more information about how to do this, see the Outlook Help topic “Create a new data file and move or copy items to it.”
3. Exit Outlook.
4. Rename the existing NST file in the file system to a new name. If the current ANSI NST file is not present, Outlook creates a new NST file which is Unicode by default. By default, the NST file is stored in %UserProfile%\Local Settings\Application Data\Microsoft\Outlook.
5. Start Outlook. Outlook will create a new NST file that is Unicode, and will synchronize the user’s mailbox with the Domino server.
6. Restore non-mail items from the PST file to the Domino folders.

Overview of deploying Office

If you are not familiar with the standard Office deployment scenarios and tools, review this section for a summary. Links are included in each section to lead you to more detailed information in the Office Resource Kit.

How Office deployment works

You can use only Office tools to deploy Office, or you can use Office tools with other deployment software, such as SMS or Group Policy (which requires Active Directory). Typically, you first customize your Office deployment by using the Office tools available with enterprise versions of Office — such as the Custom Installation Wizard and Custom Maintenance Wizard. Then you distribute your customized package by using SMS or Group Policy, creating and distributing a custom CD, providing a link to a network file share with a batch file that installs Office, or employing other methods used by your organization.

For more information, see Installing and Customizing Office.

Preparing to deploy Office

An efficient method of deploying a customized version of Office to a large number of users is to create an administrative installation point on a network server, and then create one or more custom configurations of Office at that location. An administrative installation point is a network share from which users install Office. It contains all the Office files and is created by running Office Setup with the /a command-line option. After you have customized the Office package (MSI file), users who install Office from that administrative installation point receive your customized version. For information about how to use Office Setup to create an administrative installation point, see the topic Setup Components.

You can choose to install all of Office together, or install some Office applications first and install others later. For example, some organizations decide to install Outlook first, and then deploy the rest of Office at a later time. Making decisions about deployment timing for Outlook is discussed in Determining When to Install Outlook.

You can also choose to deploy Office (or certain Office applications) alone, or together with other software by using a process called chaining. Chaining makes it simple to deploy additional software at the same time that you deploy a customized version of Office. For more information on chaining, see Including Additional Packages in the Office Installation.

Office deployment tools and methods

To follow deployment procedures in this article, you need to download and install certain Office deployment tools. The Office Resource Kit tools are provided in a single download. You can find this downloadable file on the Office XP Resource Kit Downloads page. The version of the tools must match the version of Office you are working with (for example, Office XP Resource Kit tools with Office XP). Tools that you might use to deploy Microsoft Outlook Connector for Domino include the following:

• Custom Installation Wizard
• Custom Maintenance Wizard
• Setup INI Customization Wizard

You might also choose to use command-line properties and options as a method of deploying Office. For an overview of the methods and tools used to configure Office, see Customizing the Office Installation.

Custom Installation Wizard

Use the Custom Installation Wizard to make changes to the default Office configuration. The wizard reads the package (MSI file) and records your modifications in a transform (MST file). When you run Office Setup with both the package and the transform, Windows Installer applies the transform to the original package, and Setup installs the customized configuration.

For example, the Custom Installation Wizard allows you to include custom settings and profile configurations for Outlook. Customizations are stored in a transform and applied when Outlook is installed from an administrative installation point.

For an Outlook deployment, the MST file specifies an Outlook profile configuration file (PRF file) that includes Outlook profile customization information. For Microsoft Outlook Connector for Domino, the PRF file includes configuration information to allow users to connect to a Lotus Domino server. In the wizard, you can choose to customize Outlook profile information to save in a PRF file or specify an existing PRF file. For Microsoft Outlook Connector for Domino deployment, you specify the PRF file provided in the IExpress download file. The PRF file is then automatically included in the deployment when you save the MST file.

For more information, see Custom Installation Wizard in the Office Resource Kit Setup Reference.

Custom Maintenance Wizard

Once Microsoft Office is installed on a user's computer, the Custom Installation Wizard cannot be used to install new applications, features, user settings, or to make any changes to the installation. If you want to change an existing installation — for example, to modify users’ Outlook profile configuration to include Microsoft Outlook Connector for Domino information — you use the Custom Maintenance Wizard. Note, however, that you cannot chain additional programs by using the Custom Maintenance Wizard as you can with the Custom Installation Wizard.

Unlike the Custom Installation Wizard, which uses a transform to convey customizations through Setup.exe, the Custom Maintenance Wizard is run from, and applies a configuration maintenance file (CMW file) to, users' computers. Note that you will need to copy the Custom Maintenance Wizard (Maintwiz.exe) to the administrative installation point to use this tool.

If you already have Office (or Outlook) deployed in your organization, you use the Custom Maintenance Wizard to help deploy Microsoft Outlook Connector for Domino to your users. For more information, see Custom Maintenance Wizard in the Office Resource Kit Setup Reference.

Setup INI Customization Wizard

Microsoft Outlook Connector for Domino can be deployed with Office by using a process called chaining. The Setup.ini file, which is read by the Office Setup program, specifies which packages to chain to an Office installation. This INI file can be modified manually in Notepad or through Setup INI Customization Wizard (Iniwiz.exe). The wizard provides a convenient interface for adding and customizing chained packages. The procedures in this article use the Setup INI Customization Wizard for chaining Microsoft Outlook Connector for Domino to an Office deployment.

For more information on modifying the Setup.ini file with the Setup INI Customization Wizard, see Including Additional Packages in the Office Installation.

Command line properties and options

In addition to the Office Resource Kit deployment tools, you can also customize your Office installation process through options and properties specified on the command line.

Setup properties control many aspects of the installation process, including display settings, logging options, and other properties used by Setup to manage the installation process. For example, you can specify an MST file to use with Setup by setting the TRANSFORMS property on the command line.

When you run Setup, you can use command-line options to change some of the parameters that Setup uses to install Office. By using command-line options, for example, you can direct Setup to run in quiet mode (/qb).

For a complete reference of properties, see Setup Properties.

For a complete reference of command-line options, see Setup Command-line Options.

Using the Custom Installation Wizard to deploy the add-in with Office

You can use the Custom Installation Wizard to customize and deploy Office with Microsoft Outlook Connector for Domino. First you customize your Office deployment to include the software and configurations needed for Microsoft Outlook Connector for Domino. Then you have your users install the custom configuration.

The following procedures assume that you have downloaded and extracted the Microsoft Outlook Connector for Domino files to an Office administrative installation point.

Customizing your Office deployment

You customize your Office deployment to include Microsoft Outlook Connector Domino in two steps. First, you configure Office Setup to run the Microsoft Outlook Connector for Domino Setup program directly after Office Setup completes — a process called chaining. To do this, you use the Setup INI Customization Wizard to modify the Office Setup.ini file to include the Microsoft Outlook Connector for Domino package.

To chain an Office deployment to include Microsoft Outlook Connector Domino

1. In the Setup INI Customization Wizard, type the path to the administrative installation point.
2. On the Select MSI and EXE files to include in your INI file page, select the check box next to the package Msocsetup.exe to include it in your custom INI file, then click Next.

   Note that if Msocsetup.exe is not located on your Office administrative installation point, it will not appear in this list. In this case you must browse and select Msocsetup.exe from the correct location.

3. On the Specify options for each package in your INI file page, select the Microsoft Outlook Connector for Domino package and specify the required command-line options. For example:

   /I Msoc.msi /qn
   

   
   

   This assumes that Msoc.msi is in the same folder as the Office Setup.exe file (or in a subfolder of the Office Setup location). If it is not, you must precede the Msoc.msi file name with the folder location (the absolute folder location or the folder location relative to the Office Setup.exe file).

4. Click Finish to save the new Setup.ini file (and overwrite the existing Setup.ini file).

Note   For more information about chaining Windows installer packages with Office, see the Office Resource Kit topic Including Additional Packages in the Office Installation.

Next, you customize your Office installation in the wizard and, along with your other Office settings, include the Microsoft Outlook Connector for Domino Outlook Profile (PRF) file that you extracted from the IExpress package. This PRF file will use the user’s existing Notes.ini configuration file to add a new Outlook profile for your users. The new profile will allow users to connect to the Lotus Notes Domino server defined in the Notes.ini file.

To configure the new Domino server profile in an Office transform

1. In the Custom Installation Wizard, follow the steps to specify your Office MSI file and make other customizations for your Office installation.
2. On the Outlook: Customize Default Profile page of the wizard, select Apply PRF.
3. In the Apply the following profile (PRF file) text box, browse to the Msoc.prf file and select it, and then click Next.
4. Make any other customizations for your overall Office deployment, then click Finish to save your transform.

Distributing a customized version of Office to your users

You can deploy your customized version of Office to your users by using one of several methods. For example, you can have users run a command line from the administrative installation point or you can create a custom CD and provide it to your users. Methods for distributing customized Office deployments to users are described in detail in the Office Resource Kit topic Distributing Office to Users' Computers.

As an example, suppose you choose to have users install Office with Microsoft Outlook Connector for Domino from the administrative installation point. One option in this scenario is to create an MS-DOS batch file that runs Setup.exe with your command-line options. A second option is to create a Windows shortcut and add options to the command line box. Users double-click the batch file or shortcut to run the Setup command line that you have defined. You can distribute the batch file or shortcut to users in an e-mail message.

For instance, if your Office transform was named Officewithnotes.mst, then the Setup.exe command line you include might look like this:

Setup.exe /qb TRANSFORMS="\\server\share\OfficeAdmin\OfficeWithNotes.mst"

The /qb option specifies a quiet installation (no user interaction).

Deploying the add-in after an Office deployment

If you have already deployed Office, you can deploy Microsoft Outlook Connector Domino in two steps:

• Distribute MSOCSetup.exe file to your users.
• Use the Custom Maintenance Wizard to add an Outlook profile with the Domino server connection for each user.

Distributing the add-in to users

You can deploy the Microsoft Outlook Connector for Domino Setup program (MSOCSetup.exe) to your users in several ways. For example, you can have users run a command line from the administrative installation point, or you can create a custom CD and provide it to your users. You might find it useful to review the Office Resource Kit topic Distributing Office to Users' Computers, which describes methods for distributing customized Office deployments to users. Because MSOCSetup.exe is a Windows Installer program (as is Office Setup.exe), you can use similar scenarios for distributing the Microsoft Outlook Connector for Domino Setup program.

As an example, suppose you choose to have users install Microsoft Outlook Connector Domino from the administrative installation point. One option in this scenario is to create an MS-DOS batch file that runs MSOCSetup.exe with your command-line options. A second option is to create a Windows shortcut and add options to the command line box. Users double-click the batch file or shortcut to run the Setup command line that you have defined. You can distribute the batch file or shortcut to users in an e-mail message.

For instance, the Microsoft Outlook Connector for Domino Setup command line might look like this:

Msocsetup.exe /i Msoc.msi /qn

The /i option specifies the MSI file to use. The /qn option specifies a quiet installation (no user interaction).

Deploying a new profile for the Domino server

Once you have distributed the Microsoft Outlook Connector for Domino Setup program, you modify your Office installation to add a new Outlook profile for each user. The profile will be configured and added the first time the user starts Outlook after running the maintenance program that includes the configuration information. Then users can choose this profile to connect to their Lotus Notes Domino server.

To configure the new Domino server profile in a configuration maintenance file

1. In the Custom Maintenance Wizard, follow the steps to specify your Office MSI file.
2. On the Outlook: Customize Default Profile page of the wizard, select Apply PRF.
3. In the Apply the following profile (PRF file) text box, browse to the Msoc.prf file and select it, and then click Next.
4. Make any other customizations for your overall Office deployment, then click Finish to save your CMW file.

Next, deploy the CMW file to your users with a specific command line. You can, if you choose, use the same method that you used to deploy the MSOCSetup.exe command line — for example, distribute a batch file or a Windows shortcut with the Maintwiz.exe command line to your users in an e-mail message.

Use the following syntax for your command line (Mycmwfile.cmw is used as an example here):

Maintwiz.exe /c Mycmwfile.cmw /q

The /c option specifies the maintenance file to be applied to users’ computers. The /q option prevents dialogs from being presented to the users during the update.

Using Group Policy to deploy the add-in

Another method for deploying Microsoft Outlook Connector for Domino is to use Group Policy with Active Directory with Windows 2000 or Windows XP. You create a package for Microsoft Outlook Connector for Domino in the Active Directory administrative tool and then assign the software to be installed on users’ computers at startup.

The following procedures assume that you have downloaded and extracted the Microsoft Outlook Connector for Domino files to a network share location.

Note   If you use Group Policy to deploy the add-in, you must deploy Office and the add-in separately. You cannot chain the two installations together as you can by using other deployment methods.

Also, if you have already installed Office, you cannot — using this method — create the Microsoft Outlook Connector for Domino profile with the account configured for connecting to the Domino R5 or R6 server. If you install Microsoft Office first, you can configure your Office installation with a transform (MST file) that includes the PRF file (provided in the Microsoft Outlook Connector for Domino package). For more information about how to include the Microsoft Outlook Connector for Domino PRF file in your Office deployment, see the section titled “Using the Custom Installation Wizard to deploy the add-in with Office” earlier in this article.

1. Click the Start button, point to Programs, point to Administrative Tools, then click Active Directory Users and Computers.

   The Active Directory Users and Computers tree is displayed.

2. Right-click the domain node at the top of the tree.
3. Click Properties on the shortcut menu.

   The Properties dialog box is displayed.

4. Click the Group Policy tab.
5. Click the Edit button.

   A window is displayed with the Default Domain Policy tree.

   The following steps will ensure that Microsoft Outlook Connector for Domino will be installed on the computer the next time the computer starts, and that it is available to all users of the computer. (There are other options, but this is the recommended approach.)

6. Select and expand the Computer Configuration node in Group Policy.

   This sets policies to be applied to computers, regardless of who logs on to them.

7. Expand the Software Settings folder located under the Computer Configuration node.
8. Right-click Software installation, point to New, then click Package on the shortcut menu.

   A dialog box is displayed that prompts you for the path to the Windows Installer package (MSI file).

9. Browse to the location to which you extracted the files for Microsoft Outlook Connector for Domino, then choose the Msoc.msi file.
10. Choose the Advanced Published or Assigned selection, and click OK.
11. Click OK on the Properties dialog.
12. Exit the Active Directory Users and Computers console.

This completes the package setup for Microsoft Outlook Connector for Domino. Next, verify that the package is available for installation. To do this, restart any computer that is part of the domain. Microsoft Outlook Connector for Domino installation will start as soon as the computer restarts.

More information about deploying Office with Group Policy is in the Office Resource Kit topic Using Windows 2000 Software Installation.