02-01-2011, 09:44 AM
Join Date: Feb 2011
Location: NE Ohio
Post Thanks: 0
Thanked 0 Times in 0 Posts
| | Migrated GW calendar items not syncing to new BES Express / Exchange devices
Please Login to Remove!
Here's the backstory...
We currently run a Novell GroupWise 7.0 email system. Linked to that is a BES 4.1 system that's been working fine for several years. There are less than 50 users on it, primarily our Adminstration personnel.
We are currently in the process of migrating 3500 email users to a brand new Exchange 2010 email system, and as part of that system we have installed a new BES Express 5 system and connected it to the Exchange system.
When users are migrated from GroupWise to Exchange, their email and calendar items are converted and transferred to the new system. Those that have BES accounts get their devices wiped, and then are synced to the new BES Express server. When this is complete, everything appears to be working properly, except that any calendar items that were transferred over from the old GroupWise system are not pushed out to the devices.
This is an issue for our higher ups, since some of them have appointments entered up to a year in advance and those appointments do not show on their devices.
Any calendar items entered into their new Exchange accounts sync perfectly.
My thoughts as to a possible cause are:
1) Could there possibly have been a message flag that the conversion utility did not set when it migrated the calendar items, so that the BES server doesn't pick them up as calendar items?
2) Would this possibly have anything to do with the fact that as part of our migration project, we have changed our users' email address format and domain? In our old system we used
first initial+lastname at olddomain dot com
In the new system we've switched to
firstname.lastname at newdomain dot com
Could it have something to do with the old appointments being addressed to what amounts to a different user?
Anyone have any other theories, experience with this, or possible solutions? Our CIO was the first to go and is driving this inquiry.