Importing from BO XI R2 to 3.1 problems with Favorites and User Memberships

[Former Member]

I am having a problem when using the Import Wizard to import users and groups. I marked it to import favorite folders for selected users and all groups and users. Well, the user favorites folder keeps failing with "The owner of this Favorite Folder was not found" and the groups are not associating the users in the new system under the same alias with the groups.

Old system I am using AD NTLM. New system I am using AD Kerberos.

[former_member59613 · Accepted solution]

Hi Tommy,

for importing AD users, you have to first configure the AD authentication piece on the new server. I don't think you can import the users over until the AD is setup.

Alternatively, you can convert your users accounts to Enterprise user accounts before importing them over. Once they are in the new system, you can setup the AD authentication and groups and any existing accounts with the same name should get AD aliases assigned to them.

I've never tested going from NTLM to Kerberos users but I don't think that should be a factor.

Hope this helps,

Jb

[Former Member · Accepted solution]

JB, AD has already been set up on the destination system. It is set up as Kerberos. In the source system, it is set up as NTLM AD. When I migrated the users and groups over, all of the AD users from the source system did not move over to the new system and it error out with the duplicate name found on the destination system thinking it is a different object. I need them to be moved over to match up with the same alias so that all of the group memberships can be mapped out. The favorites folders for the users also did not move over because it thinks that the users are already in the new system. This is not looking good!

[BasicTek · Accepted solution]

Just to confirm, kerberos/NTLM is a non factor in CMS group queries and is only used for user logon. Also as JB stated the AD plugin must be configured (and groups must not be mapped in the destination system)

The error message is indicating that for some reason the groups names already exists on the destination system. Mapping them in the AD plugin would cause this or having the same group name in LDAP or NT plugins. Ensure that on the destination system the groups have not already been mapped.

While creating enterprise users is an option it should not be needed. Migrating Ad groups should work fine if the requirements are followed.

Regards,

Tim

[Former Member · Accepted solution]

Tim,

Thanks for the info. However, I think I need to be clearer.

The AD plugin has been configured on the destination system with no groups mapped. It has AD enabled and updated so the initial batch of users were imported in without any further manipulation.

When migrating the users and groups from the source system, all of the groups seem to have migrated over fine. However, all of the users from the source that has AD did not migrate over to the destination system because it says there is a duplicate. That is why the groups did not map these users and the favorites did not go through.. please let me know if this is not clear.

I do not want to change all of the system users to Enterprise and then transfer them over as enterprise and then configure them as AD users... this may end up causing more problems and may not even work

[BasicTek · Accepted solution]

If you created the user in the new system then this will not work as they will have a differen CUID, you have to delete the user and migrate them over clean. The duplicate ID exists indicates the same user or group different CUID.

Regards,

Tim