Sun Java System Connector for Microsoft Outlook 7 2005Q4 Deployment Planning Guide

Chapter 1 Introduction and Overview

This Guide was developed to help you, the system administrator, understand and plan for the deployment of the Sun Java System Connector for Microsoft Outlook to the end users in your organization. The deployment process can proceed along many different paths depending on your original and destination network configurations, the administrative structure of your organization, and your own informed sense of the extent to which your users can and should be involved in the process of installing and configuring their own desktop software.

Your organization will use Sun Java System Connector software so that your users can use Microsoft Outlook as their email and calendar client while connected to Sun Java System servers. The Connector software must be installed and configured for each of your desktop users to facilitate the necessary ongoing communications between Outlook and the Sun Java System server. Sun also provides a Desktop Deployment Toolkit, a collection of software tools for system administrators designed to simplify both the administrator's work and the user tasks associated with installing and configuring the Sun Java System Connector software for individual users.

The Desktop Deployment Toolkit lets the administrator create customized end-user installation packages for the Connector software, with preset configuration parameters to simplify and streamline the user’s process, and to enforce any configuration settings the administrator deems necessary or desirable for a particular user or group of users. The Deployment Configuration Program saves those preset configuration parameters in an .ini text file, and then bundles the .ini file with an installation program—the Setup Wizard—for end users. When an end user activates the package, the Setup Wizard reads the .ini file to install and configure the Connector software on his or her desktop according to the administrator’s specifications.

As you plan for your deployment and use the Deployment Toolkit to prepare installation packets for your users, you will find many choices available for how the new software will be distributed, installed and configured on individual user desktops. Some of your choices will be dictated by logistical imperatives, while other choices will be derived from your personal familiarity with your organization, your network, and your users.

This Guide is intended to help you anticipate these choices, and explain the significance and implications of your options before you start using the Deployment Toolkit.

Why Use the Deployment Toolkit?

With the Deployment Toolkit, an administrator can control a wide range of configuration parameters for desktop users. Mandating many or most configuration settings will bypass the need for users to ponder options, make choices and set values themselves. These automated or semi-automated installations will spare the corporate help desk many calls for guidance, support, and solutions to the inevitable problems that arise when user choices produce unexpected results. Overall, the toolkit substantially reduces the cost, time and effort required to deploy the Sun Java System Connector software.

A system administrator may create different installation packages for different groups of desktop end user—for example, to enforce different configuration schemes for users in the Sales department vs. the Engineering department and so forth, or to offer configuration options to some groups of users while setting fixed parameters (eliminating the choices) for other groups.

If your organization is migrating from Microsoft Exchange, the user's installation packages will also preserve the considerable value of their existing Outlook data stored in .pst files on user desktops, as well as their Notes, Journals and Contacts stored on the Exchange server. The bundled installation packages include a conversion utility that quickly converts all such data to pure Internet addresses, so users will be able to reply to older messages, appointment invitees will receive change notices, and address books and personal distribution lists will remain serviceable after your migration to the Sun Java System server.

Deployment Process Per Desktop: Three Tasks

Deployment of the Sun Java System Connector software to each user desktop requires three distinct tasks:

The Deployment Configuration Program lets a system administrator create installation packages that will automate some or all of these tasks for end users, depending on the administrator's deployment strategy for any particular group of users.

Deployment Toolkit Components

The Sun Java System Connector Desktop Deployment Toolkit consists of these components:

In addition to the above-listed components of the Deployment Toolkit, the Microsoft installation program for Web Publishing Wizard (WPW) (available from other vendors) may be necessary for your users to install the Sun Java System Connector for Microsoft Outlook.

Microsoft's WPW is a tool used to generate HTML-coded documents, typically in the form of web pages to be viewed in a web browser. But WPW can also be used to “publish” information for other purposes—to create documents containing certain types of data and upload the documents to locations where other applications can find them and extract the pertinent data. The Sun Java System Connector uses WPW this way to facilitate the transfer of users' free/busy data between Outlook and the Sun Java System server, and WPW therefore is a necessary intermediary and a required component of every user's installation of the Sun Java System Connector.

Note –

The WPW, however, is not included in the Deployment Toolkit package because it is a Microsoft product, so you must obtain the Web Publishing Wizard from Microsoft. The installation program for Microsoft’s WPW is available as a free download from