This chapter describes some administration tasks you may need to perform for users of Oracle Communications Connector for Microsoft Outlook. Most of these tasks are performed on end-user computers.
If you have decided to stop using the Oracle Communications Unified Communications Suite software, you may need to reverse any migrated user profiles and data files.
To reverse migrated user profiles and data files:
Delete the profile Xxx (old).
Copy the profile Xxx to Xxx Oracle or some other name, like Xxx (new), and so forth.
Delete the profile Xxx.
Copy the profile Xxx (Backup) to Xxx.
Delete the profile Xxx (Backup).
Determine where the PST files are located by viewing Properties on the profile. There is no standard location for PST files, so the only reliable way to find them is to open the profile (now named Xxx) and, for each PST file, click Properties and note the path.
For each PST file: Rename Yyy.pst to Yyy.new, and rename Yyy.bak to Yyy.pst.
Determine where the PAB files are located by viewing Properties on the profile. There is no standard location for PAB files, so the only reliable way to find them is to open the profile (now named Xxx) and, for each PAB service, click Properties and note the path.
For each PAB file: Rename Zzz.pab to Zzz.new, and rename Zzz.bak to Zzz.pab. The Yyy.bak and Zzz.bak files are in the same directory.
To uninstall Connector for Microsoft Outlook, use Add/Remove Programs in the Windows Control Panel.
You cannot roll back to a previous version of Connector for Microsoft Outlook. You can uninstall the current version by using Add/Remove Programs from the Control Panel, and then install the required version.
You can specify where Connector for Microsoft Outlook stores new PST files. The default location is:
C:\Documents and Settings\username\Local Settings\Sun\Outlook Connector
To change the location where Connector for Microsoft Outlook stores PST files:
On the end-user computer, using the Windows Registry Editor, locate the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\version\Outlook
Where version is the registry version value for Connector for Microsoft Outlook.
If the user is using Outlook 2010, version is 14.0. If the user is using Outlook 2013, version is 15.0.
Right-click the ForcePSTPath string and select Modify.
Change the path to point to the desired location.
Certificate-based authentication is a secure authentication method that uses digital certificates stored locally in the system (or in a smart card) to authenticate a user. Certificate-based authentication is an alternative to using passwords.
Connector for Microsoft Outlook supports certificate-based authentication for the following back-end services:
Mail access service: IMAP + SSL, IMAP + STARTTLS
Mail transport service: SMTP + SSL
Calendar service: WCAP + SSL
Address book service: WABP + SSL or REST + SSL
Corporate directory: LDAP + SSL or REST + SSL
User preferences: LDAP + SSL
Connector for Microsoft Outlook supports smart-card certificates and software digital certificates.
When logging in, Outlook determines whether the server is configured for certificate-based authentication. If the server is configured for certificate-based authentication, Connector for Microsoft Outlook searches through the local system for eligible certificates with which to authenticate.
The eligible certificates are filtered by:
Certificates issued by "trusted CA" by the back-end servers.
Unexpired certificates.
Certificates that can be used for SSL client authentication.
Connector for Microsoft Outlook prompts the user with the list of eligible certificates. The user selects the certificate with which to authenticate to back-end servers. If certificate-based authentication fails, Connector for Microsoft Outlook falls back to password-based authentication and prompts the user to enter a password. This is also the case if the user does not select any certificates from the list.
Note:
If you configure a profile to only support certificate-based authentication, then the user is not prompted for a password.If certificate-based authentication fails and password based authentication succeeds for the mail server, then certificate-based authentication is not attempted for other back-end services. If certificate-based authentication succeeds, then certificate-based authentication is attempted with other back-end services first. If certificate-based authentication fails, password-based authentication is attempted.
If a user mistakenly chooses a certificate different than the certificate used during the last login, the user is warned that a different certificate is being used to log in from the previous attempt and is given an option not to continue.
Caution:
If both certificate-based and password-based authentication fail with the mail server, Connector for Microsoft Outlook does not proceed authenticating with other back-end services.You can configure a profile such that an authentication certificate is used with the back-end services without the user having to choose the certificate.
A user can configure a Connector for Microsoft Outlook profile so that the certificate information is saved, allowing the user to log in without being prompted to select an authentication certificate.