Groupwise migration wizard problems

[mclark]

I am having problems using the Groupwise Migration Wizard.

I've set up the GWIA to allow LDAP access. When I watch the GWIA console after entering the LDAP settings in the wizard, I see it say LDAP connection accepted, so I know the wizard is hitting the GWIA. However, when I click "Object Picker", I get the message "Unable to perform the search". I am not sure what I am missing. Here is the PO.XML file I am using:

<PostofficeIpPortInfo>
<postoffice name="cn=GW_Post,o=Students" ip="10.12.241.14" port="1677">
</postoffice>
</PostofficeIpPortInfo>

GW_Post is the actual Post Office object in NDS, and not the POA object within GW_Post. I am entering an admin user for Zimbra, and I know the wizard is setting itself as a trusted app because I can see it in the GroupWise trusted applications dialog.

I am not sure what piece I am missing to make this work. Help!!!

EDIT:

I forgot to mention that this system is set up with a MTA/POA in one domain, then a MTA/GWIA/WebAccess in a secondary domain, if that makes any difference.
I also went into the GroupWise client and added a LDAP address book entry for the GWIA LDAP server. I did a search for a name and it came back with entries, so the GWIA is functioning as an LDAP server and returning results.

[Rich Graves]

It may not be your problem, but we got a lot farther after finding Bug 16443 - GroupWise: Postoffice information usage is case-sensitive

It is FIXED in 5.0, but not the latest 4.5 branch.

All bugs and RFEs matching "GroupWise":

TinyURL.com - shorten that long URL into a Tiny URL

[mclark]

Thanks for the tip. I checked the XML file and I had already put in the PO with the correct case, so unfortunately that does not seem to be the issue.

[Uday]

Postoffice information is used at the time of migration. It will not affect "Object Picker" or "Query Builder".

Are you facing same problem with "Query Builder" also?

[mclark]

I tried Query Builder, and when I click "OK" nothing happens. It just goes back to the selection screen with "Object Picker" and "Query Builder" buttons.

[stuartg.orion]

I'm having much the same problem. Although if I select all the users in the list I get a small percentage of the users can be selected.

I can't find any significant difference between the accounts that it will let me choose and those it won't let me choose.

I'm using version 4.5.6 of the migration tool.

[Uday]

If the users listed in object picker don't have an LDAP attribute "nGWGroupWiseID", those will not be considered for migration.

-Uday

[stuartg.orion]

Ok so browser the LDAP tree with LUMA a user I couldn't migrate had:

nGWFileID
ulq

nGWGroupWiseID
DOMAKL1.POAKL1.Paul{106}45889101-06C2-0000-A8E0-C500B4007C00

nGWObjectID
Paul

nGWPostOffice
cn=POAKL1,ou=GWise,ou=Services,o=Orion

nGWVisibility
2

and a user the tool would have let me migrate had:

nGWGroupWiseID
DOMAKL1.POAKL1.pdeb{106}45889101-06C2-0000-A8E0-C500B4007C00

nGWObjectID
pdeb

nGWPostOffice
cn=POAKL1,ou=GWise,ou=Services,o=Orion

nGWVisibility
2

Not also that both these users appeared in the object picker for the Post office. It was only we I chose each that the first wouldn't let me proceed but the second would

[nrc]

We're having a similar issue with users not available for migration. We discovered that the migration tool also seems to expect a "uid" LDAP attribute which some of our users have and some don't. Not having a uid seems to make them unavaible in object picker.

[stuartg.orion]

Ah yes, the users I can migrate do have the UID field and the one's I can't don't.

So I just manually added that field using Console One and am going to try again. Can you see a reason why that wouldn't work?