This error can be cause by one or more of the following issues within the Exchange and/or migration environment.
1. GAL or BPOS account is hidden.
Resolution: The user account must be enabled and not hidden, or you do not have Full Access permission set for this account.
2. Migrating to Exchange 2010, the migrations do not complete, and there are errors in the log. CAS server not configured.
Resolution: Did you originally run the "Match Selected users on CAS server" process in CMTe, or did you run "Match Users" process?
In order for CMTe to migrate successfully to Exchange 2010, you must use the "Match Selected users on CAS server" process, after configuring the CAS settings per the CMTe user guide.
If you ran a migration, and realized there was a problem, and tried to run the "Match Selected users on CAS server" process, this will still fail since the updates do not get pushed down to an existing user's backend document.
You must open the CMTe.exe
Click the "Users" tab, and delete the users that need to be migrated. CMTe will see there is no matching record and create a new record with your new Notes CAS server information. This will also use an additional license. We can provide you additional licenses if needed.
3. Migrating to Exchange 2010, "BPOS" Outlook profile not set as default.
Make sure you are using an Outlook profile called "BPOS" as the default migration profile on all migration workstation? The cmt temp profile is copied from the default profile. BPOS must be the default profile of which CMT temp profile will be created. From the 3.1 comprehensive users guide:
Appendix H: Exchange Unable to migrate because mailbox server doesn‟t have CAS role
If you are using Exchange 2010, you may not be able to migrate successfully if your Exchange mailbox is created on the server with no CAS (Client Access Server) role installed on it. Follow these steps to resolve the issue:
1. You need to configure the Migration Workstation to point to the CAS server. To do this, you need to first log into the Migration Workstation with the account that will be moving the data.
2. Next, configure the Outlook client to connect to that migration account, just as it is done in a standard deployment. This creates the default Outlook mail profile.
3. Go to the Control Panel, click Mail, copy the default Outlook profile, create a new profile, and name it BPOS.
The BPOS profile must not be using cached mode, or the migration profile will be created as cached
also. If this happens, the data will be migrated to a local cache and only part of the data will make it to
Exchange before the migration finishes.
4. Follow steps 1-3 on every Migration Workstation.
When CMT for Exchange comes across a profile called BPOS, it recognizes that the BPOS profile is to be used to create the CMT Temp Migration Profile instead of generating a new one.
The application then simply replaces the name.
Once the CMT Temp Migration Profile is created, you can successfully migrate data to the Exchange mail server.
4. Room or Resource not properly configured in CMTe
Unlike users; rooms, resources, and other databases cannot be automatically resolved by the CMT for Exchange migration engine.
You need to manually resolve them by providing their Exchange information.
It is recommended that the Exchange Display Name of a room mailbox in AD should preferably match the corresponding Domino room CN.
This will help in identifying and matching the accounts manually.
To do this, you edit the control document.
Double-click an item in the Data Pane.
When the document opens, double-click inside the document to open it in the Edit mode.
The Exchange server field properties are edited. These fields should now point to the corresponding mailbox created in Exchange for this item. Close the tab and save the changes.
Next, select all imported rooms and the resources and set their migration status, group, and workstation using the Set Migration Status tool in the Advanced document.
Click Advanced in the Navigation Pane.
Click the Set Migration Status button in the Data Pane.