Also since you are moving from and old openldap 2.0.27 to a newer 2.2, that leads to the question:
Was the old server running a 2.X.X samba series?
Remember that the samba schema has been changed from 2.0 to 3.0. You may actually need to copy the appropriate samba 3 schema from the samba examples to the schema folder in ldap and then make sure slapd is loading it.
You will also need to write a script that will parse the ldif file and replace the old naming convention prior to adding it to the new openldap server.
You may have already done this, but it is worth checking.
Diego
Quoting Paul Gienger <[EMAIL PROTECTED]>:
You're right, my existing server is running OpenLDAP 2.0.27 and my lab's server is running OpenLDAP 2.2.23.
I guess the biggest concern I have is any problems that may have come into play because of the version differences. I'm using this lab as a "practice run" for the real upgrade later in the year. I'd like to resolve all o fhte issues now and not then. ;-)
Quickly, I can say that 2.2 is much more strict about what objects you put into it and I believe how the objects are defined. If this is the only thing you had complain going between the two, be happy ;) When we made this switch we had inetOrgPerson and posixAccount in the same objects which didn't play nicely together in 2.whateverwewentto, I think it was 2.1.
Basically 2.0 will let you just slap any old object class together and call it a day, 2.2 is requiring you to flesh out the object inheritance more. You're just explicitly stating what 2.0 is taking for granted or not caring about at all.
-- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Systems Architect Fax: 701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED]
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
