Migration | << | >> |
---|
Migrate Schedule+ version 1.0 messages with the MMF file. Calendars are migrated the first time users use 16-bit Microsoft Outlook. The new 16-bit Microsoft Outlook looks for the local copy of the CAL file.
You can also use the Migration Wizard to migrate calendars for 16-bit Microsoft Outlook. The migrated data is put in the mailbox's server calendar in Schedule+ 1.0 format. This data is converted to 16-bit Microsoft Outlook format the first time the calendar is opened. This is helpful to users who accidentally delete their local copy of the calendar file and to resource accounts that don't have a local copy of the calendar file.
Note The 32-bit version of Microsoft Outlook does not automatically convert Schedule+ 1.0 data. You can import a local copy of the .CAL file in 32-bit Microsoft Outlook.
A user's Microsoft Schedule+ 1.0 password is stored locally in the client calendar file (.CAL) on his or her computer. This password is also stored in the server calendar file, which is stored on the MS Mail (PC) postoffice. When an MS Mail (PC) postoffice is migrated to Microsoft Exchange Server, the user's Schedule+ version 1.0 information (.CAL file) is migrated, as well as his or her Schedule+ password.
Microsoft Exchange Server authenticates Microsoft Outlook users when they initially access their mailbox. After their mailbox and Schedule+ information are migrated to a Microsoft Exchange Server, their logon password provides access to both Microsoft Exchange Server and calendar data. However, when mobile users access Microsoft Outlook offline after migration, they are prompted to enter the password they used to access their Schedule+ 1.0 calendar file. Many users will have forgotten this password.
For this reason, prior to migration, administrators should tell users to make a note of their current Schedule+ 1.0 password. After migration, users can reset their password to null from 16-bit Microsoft Outlook, or continue to use their Schedule+ 1.0 password when working offline. Because user authentication is done by Microsoft Exchange Server, security is not compromised.