Groupwise Migration problems
I recently upgraded from open source Zimbra 4.5.1 to 4.5.9 and stopped partway through at 4.5.6 to grab the GroupWise migration tool. The exact version is ZCSGroupwiseMigrationWizard-4.5.6_GA_1023 Version 4.5. I am attempting to run the wizard on a windows 2000 machine that has GW client 6.5.0 and Netware client 126.96.36.19951209.
The problem is that I am getting thousands of lines in the log that look similar to the following three lines:
The only thing that it appears to be doing is creating the folder structure from the users email box.
16-11-2007 01:30:55 : (MI): WARNING: Message skipped, Failed to get Appointment Interface d(Tue, 8 Mar 2005 07:30:49 -0000) fid(010)
16-11-2007 01:30:55 : Messages type not supported, skipping message mid(422F0600.aName.aNamePO.100.1713373.1.16F1.1)
16-11-2007 01:48:59 : (MI): ERROR: Failed to get a Address Book, skipping Address Book Frequent Contacts
Any ideas as to what is going on or how to fix it? I have been unable to find anything relating to this issue in the forums so far.
Tomorrow I will be trying on a Windows XP computer to see if that makes any difference.
"issues" with the GW migration util
I get the feeling that there were some issues/problems with the GW migration utility, as it was not even available in later releases (as you noticed).
Not sure if it is a good idea, but I've been using the one that was included in the 5.0 BETA 3 release. It is not perfect, and still throws some error msgs. on some to-be-migrated messages... but it seems to do a better job than previous releases. I've used it on about 5 people so far.
what I had to do to our LDAP setup
I had opened a support ticket when first trying the migration wizard... I too had some LDAP issues, in terms of what needed to be exposed. We're using the NLDAP on NetWare 5.1.... the LDAP portion of GroupWise is too limited in what needs to be see by the migration util. I'll try to detail it here, maybe it will help. LDAPBrowser is your friend for seeing what fields are exposed for each user (when you are authenticated as someone admin-equiv): From my notes at the time:
"To summarize, the "dn", "nGWGroupWiseID", "nGWPostOffice" and the "uniqueid" LDAP fields all seem to be required (I figured out the "uniqueid" one by myself with some help from the forums. These should likely be added in a TID or the documentation. The LDAP that is supported by the GroupWise GWIA is not sufficient to expose these attributes, and you must use the NLDAP that comes with the OS (NetWare in my case).
>>> Zimbra Tech <firstname.lastname@example.org> 8/1/2007 6:08 AM >>>
Here's what the developers say:
The tool expects that the user will have "mail", "dn", and "nGWPostOffice" LDAP attributes when it gets selected from the user's list before adding the user to main list and tries to fetch the same. If any one of them could not be fetched, that entry will not be added as all these attributes along with "nGWGroupWiseID" are required for selecting the user for migration. I guess the LDAP server there doesn’t expose "nGWPostOffice"(its not visible in the snapshot) and hence the tool is failing to add the user into the migration list."
- in the Other tab, make sure there is a "uniqueID" field, that equals the username... add it if it is not exposed.
- make sure there is the correct entry for "email address" (mail LDAP attribute) in General/ID tab
- in General/ID tab, Description field I have as "gnyce.MIS.ORGANIZATION" - I do this b/c when I expose LDAP attributes, I use this field... you may not have to (my changes involved two different projects, so I might be mixing them here).
- in my LDAP Group edir object, Attribute Map, I (think I) added a few mappings:
nGWGroupWiseID --------> NGW: GroupWise ID
NGWPostOffice ----------> NGW: Post Office
dn -----------------------> Description
uid -----------------------> uniqueid
At least make sure these all exist. Last, you need to expose some of them, esp. if using the LDAPBrowser java util, you cannot see what Zimbra needs on an account. For me, I added the uniqueID, dnQualifier, dn, OU, L, Description, and CN Readable for the LDAP server/user. Let me know if you're not sure how to go about that.
Should warn you - the migration utility does not seem to be the speediest thing in the world...
Post back your results