|Bookshelf Home | Contents | Index | PDF|
If you upgrade your SSSE environment from Microsoft Exchange Server 2003 or 2007 to Microsoft Exchange Server 2010, the first time you run SSSE with Microsoft Exchange 2010, SSSE runs a number of processes to migrate previously synchronized user records so that they are compatible with Exchange Server 2010. After records have been migrated successfully, record synchronization takes place in the subsequent synchronization session.
Siebel administrator intervention is not required to run the migration processes; they are run automatically if SSSE is installed with Microsoft Exchange Server 2010 and if previously synchronized records are detected. However, understanding the migration process is helpful in troubleshooting synchronization errors that can occur if a record is unsuccessfully migrated.
Every Microsoft Exchange Server calendar, contact, or task record is uniquely identified with a MAPI identifier; SSSE stores this identifier for use in future update or delete operations on the record. With the introduction of Exchange Web Services in Microsoft Exchange Server 2010, MAPI IDs can no longer be used to identify the corresponding record in the Microsoft Exchange Server, and any update or delete operations to such records cannot be synchronized.
To address this issue, the SSSE migration process converts all MAPI IDs from older versions of Microsoft Exchange Server to identifiers that use the Microsoft Exchange 2010 format. Specifically, the SSSE migration process performs the following tasks:
|Siebel Server Sync Guide||Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.|