Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XFOR: MS Mail Schedule+ Migration Requires Registry, Win.ini Configuration
Article ID: 299503 - View products that this article applies to.
This article was previously published under Q299503
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you are using the Exchange 2000 Migration Wizard to migrate Microsoft Mail Schedule+ 7.0 data, you need to take certain steps for users to be able to use the migrated Schedule+ data. If you do not follow these steps, the new mailbox owner will not be able to use the Schedule+ data. When you import the .scd file into the Microsoft Outlook client, a password prompt will appear. The password that works is the one from the source .scd file, not the target .scd file as expected. To resolve this issue, follow the steps in the "Resolution" section.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You must add the following registry entries to the Exchange 2000 server if Schedule+ is not installed and if you have not applied Exchange 2000 Service Pack 2.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.