Planning and foresight are critical to a smooth deployment. The process of developing a comprehensive Deployment Plan is a valuable exercise that will lead you to consider and accommodate all of the factors likely to influence your organization's migration. The Part VI, Deploying Connector for Microsoft Outlook, in Sun Java Communications Suite 5 Deployment Planning Guide explains important migration concepts, prerequisites, and strategic choices, and explains how to develop a Deployment Plan that will guide you through your migration. Every administrator should therefore read Part VI, Deploying Connector for Microsoft Outlook, in Sun Java Communications Suite 5 Deployment Planning Guide and prepare a comprehensive Deployment Plan.
Sun’s administrative software obviously must reside on the administrator’s computer before it can be used to create end-user installation packages. The installation instructions can be found in the Sun Java System Connector for Microsoft Outlook 7.2 Installation Guide.
Configure end-user package.
Chapter 2, Configuring End-User Packages explains how to use the Deployment Configuration Program to create customized packages for Outlook end users. These packages can be configured to install the necessary software on user desktops, or to convert users’ existing Outlook and Exchange data files for use with the new software—or both, depending on your circumstances.
Once you have created an installation package for your users, you must tell them where to find it and how to use it. Many administrators simply copy the package and the associated Sun Java System Connector for Microsoft Outlook 7.2 User’s Guide to a shared folder, and then provide links to the installation package and documentation in an announcement email to users.
Steps 1 and 2 of this process overview are a good place to start regardless of your unique configuration and preferences. If your migration strategy calls for two or more different installation packages for different users or user groups, simply repeat steps 3 and 4 for each package until all users have been migrated.
The deployment process can proceed along 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 should be involved in the process of installing and configuring their own desktop software. Moreover, your network configuration or preferences may dictate some variation to the standard scenario described above. Chapter 3, Application Notes for Special Circumstances provides application notes for the most common of these variations.