Quote:
Originally Posted by rduric  We have migrated 5 users from beta 2 to beta 3. During the migration we had a number of issues:
- enterprise activation took several attempts per user. Every time I remove and add a user in BES it creates a ZDB/IDM pair in the c:\Document and Settings\Administrator\Local settings\Application Data\Microsoft\Outlook\... So now for 5 users I have 39 of these pairs. When I remove a user in BES I think all data for this user should be purged which is not!? I think this is the reason I have so much difficulties registering users with my ZCB.
- users with big mailboxes would receive the Local failure notices during activation
- calendar synchronization incomplete
- when I restart ZCB server, Outlook 2007 would crash and after I press 'Don't send report to Microsoft' a couple of times, it appears as working... |
hmmm...let me address each issue and make a couple of comments:
1) zdb/idm files. you are correct but this is not your problem. when you mount a user in ZCB, we create the local cache of the mailbox data and an id mapper file (the two files that you see). when you unmount the user (remove the user), we do not remove those files. it is a precursor to a feature that tries to avoid an expensive initial sync if you readd the user. right now that feature isn't implemented and when you readd the user, you will see more zdb and idm files. not a problem except if you are hurting for disk space.
2) local failures are not always a problem. they will sometimes outline RPC failures which cause us to sync again. it depends on the contents of the local failures. might need to post the contents or open a support case about them. if the local failures point to calendar events that could not be processed, this could be due to issue 3/4 that i address below.
3) calendar syncrhonization incomplete. this could be a number of things and its possible that the local failures could outline why certain calendar events didn't make it to the device. could also be linked to issue 4 (below) since we use OOM for calendar conversion. if outlook crashes, the calendar event will probably not get synced.
4) outlook crashing. do you have outlook running at the same time as the controller or are you talking about outlook crashing within the controller? you should have dump files created at %temp%/zco-cores. please find these dump files and send them to support. this will tell us exactly why outlook is crashing and this could solve your calendar not syncing problem.
how did you build your environment going from BETA 2 to BETA 3? did you start from a fresh OS and install MAPI/CDO, BES, Outlook 2007 and ZCB? Or did you upgrade Outlook to 2007 and then install the new ZCB? If this is what you did, did you choose to "delete previous versions of Outlook" when you were installing Outlook 2007? Did you do something else for the upgrade to BETA 3? The cleanest thing to do is the fresh start at a clean OS install. Internally we have done that for testing but our internal corporate instance of ZCB was a straight up Outlook 2003 to Outlook 2007 upgrade and then an upgrade of ZCB to BETA 3.
also, what version of the server are you using? did you upgrade to at least 5.0.7?
--Tony