What’s Next?

Planning and foresight are critical to a smooth deployment, so you should have already prepared a comprehensive Deployment Plan before installing the administrator software as described in this chapter. If you haven’t yet prepared a Deployment Plan, do it now, before you attempt to create your first desktop deployment kit. 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. 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.

After you have prepared your Deployment Plan and installed the administrator software, you can:

1. Configure an end-user package. The Sun Java System Connector for Microsoft Outlook 7.2 Administration Guide 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.

2. Deploy each end-user package. 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 Sun Java System Connector for Microsoft Outlook 7.2 User’s Guideto a shared folder, and then provide links to the installation package and documentation in an announcement email to users.

   If your migration strategy calls for two or more different installation packages for different users or user groups, simply repeat these two steps for each package until all users have been migrated.