| Sun Java System Connector for Microsoft Outlook Desktop Deployment Configuration Program Reference Manual |
About This Guide
This guide describes the Deployment Configuration Program for the Sun Java™ System Connector for Microsoft Outlook. Topics covered in this chapter include:
Who Should Read This BookYou should read this book if you are responsible for administering and deploying Sun Java System Connector for Microsoft Outlook at your site.
What You Need to KnowThis book assumes that you are responsible for administering and deploying the Connector for Microsoft Outlook software and that you have a general understanding of the following:
How This Book is OrganizedThis Reference Manual contains the preface you are now reading, followed by three chapters:
- Chapter 1, "Getting Started"—Brief narrative explanations of what the Sun Java System Connector software is designed to do, how it is typically used within the broader context of an overall migration scenario, and what an administrator should do to get started with the software — plus instructions for installing the administrator’s software on the administrator’s own computer.
- Chapter 2, "Creating End-User Installation Packages"—This chapter describes how to use the Deployment Configuration Program to create customized installation packages for Outlook end users. These packages can be configured to install the necessary software, or to convert existing Outlook and Exchange data files for use with the new Connector for Microsoft Outlook, or both—depending on your circumstances.
- Chapter 3, "Application Notes for Special Circumstances"—This chapter explains how to deploy the Sun Java System Connector for Microsoft Outlook under certain special circumstances or network configurations:
- “Push” Method Deployment, If End Users Lack Installation Privileges: Installation of software to an end user’s desktop requires access privileges that often are disallowed to many or most end users. Most organizations in these circumstances implement a “push” method of software distribution from the system administrator to user desktops, which bypasses the requirement for user access privileges. If your network serves “locked-down” Windows environments where end users cannot install software, we strongly recommend this sort of automated configuration management as a way to avoid many individual desktop visits.
- Command-Line Switches for the User Installation Package: A user-installation package can be run from the command line, with switches to pass the necessary user passwords to the conversion program as it runs. An installation package can therefore be run by an SMS script, with command-line switches, to make possible a truly silent installation and configuration, requiring no user interaction whatsoever.
- Migrating Terminal Service Users from Exchange to the Sun Java System: The Sun Java System Connector administrator’s tools can also be used to migrate existing Outlook users of Windows terminal service from Exchange to a Sun Java System server.
- To Designate Microsoft Outlook as a User’s Default E-mail Client: Installation of the Sun Java System Connector software requires that Outlook be set as the default e-mail client for every user. If a user does not have Outlook set as his or her default client, he or she (or an administrator) should follow the instructions in this section to reset the default to Outlook.
- To Remove the Sun ONE Sync Program from a User’s Workstation: The Sun Java System Connector software cannot coexist on the same desktop with the Sun ONE Sync program. If the Sun ONE Sync program has been installed on a user’s desktop, the user (or an administrator) should follow the instructions in this section to remove it.
- Undoing (Reversing) a User’s Migration: How to abandon a user’s connection to the new Sun Java System server and restore the user’s mailbox to service with the old Exchange server.
- Recovering from a User’s Removal of LDAP Services from Outlook: How to restore LDAP services to the user’s workstation.
Document ConventionsIn this guide, file and directory paths are given in the Windows format (with backslashes separating directory or folder names). If you reference other Sun Java System documentation, you may notice that UNIX conventions designate file and directory paths (with front slashes separating directories).
- Monospaced font is used for any text that appears on the computer screen or text that you should type. It is also used for filenames, distinguished names, functions, and examples.
- Bold monospaced font is used to represent text within a code example that you should type.
- Italicized font is used to represent text that you enter using information that is unique to your installation (for example, variables). It is used for server paths and names.
For example, you might see path references of the form:
ISTOREx.LOG
In this situation, x is a numerical value for the day of the week.
Italicized font is also used for variables within the synopsis of a command line utility. For example, the installation package supports the command line utility:
/USERNAME=xxx
In the above example, the italicized font is an argument for its associated command. The xxx refers to the UserID on the server.
It is possible to run the installer command by itself as follows to start the Messaging Server installation:
setup
However, the presence of [options] and [arguments] indicate that there are additional optional parameters that may be added to the setup command. For example, you could use setup command with the -k option to keep the installation cache:
setup -k
Where to Find Related InformationFor more information about the Deployment Configuration Program and the system administrator’s role in the deployment of the Sun Java System Connector for Microsoft Outlook, please see:
- Sun Java System Connector for Microsoft Outlook Desktop Deployment Administrator’s Guide: The Desktop Deployment Administrator’s Guide provides a more global overview of the deployment process, explaining several strategic and high-level tactical options that a system administrator should consider prior to actual deployment. As you prepare user installation packages, you will encounter many available choices that let you determine how the new software will be distributed, installed and configured on user desktops. Some of your choices will be dictated by logistical imperatives, while others will be judgment calls, derived from your personal familiarity with your organization, your network, and your users. The Desktop Deployment Administrator’s Guide is intended to help you anticipate all such choices, to help you understand the significance and implications of each option.
Documentation for Sun Java System Connector for Microsoft Outlook can be found at the following URL:
http://docs.sun.com/coll/ConnectorMSO_60
Where to Find This Book OnlineYou can find the Sun Java System Connector for Microsoft Outlook Desktop Deployment Configuration Program Reference Manual online in PDF and HTML formats. This book can be found at the following URL:
http://docs.sun.com/db/doc/817-4219
