kolab ldap migration questions.

[John McMonagle]

Our current mail server is using debian sarge with postfix cyrus and openldap.

Most our servers are debian etch and am starting to switch to lenny.
Have many questions but for now will stick to my ldap concerns.
Currently have 1 master ldap server and 6 slaves at 5 sites.
Primarily using ldap account manager for management.
We are primarily linux but do run nt domain via samba, ldap and nitrobit.
Am using a combination slurp and sync replication.
Slowly switching to sync replication as I do upgrades.

After dealing with merging all the schemas and acls, was thinking I would 
import the base kolab records into our ldap.

Here is  one of our current records:
dn: uid=bradb,ou=People,dc=advocap,dc=org
uid: bradb
sambaSID: S-1-5-21-3708734655-3086812103-629500990-53054
cn: Brad Bingham
sambaLMPassword: xxxx
sambaNTPassword: xxxx
sambaPwdLastSet: 1159476966
sambaKickoffTime: 1893513600
sambaAcctFlags: [XU         ]
sambaHomeDrive: U:
sambaPrimaryGroupSID: S-1-5-21-3708734655-3086812103-629500990-5047
sambaDomainName: ADVOCAP
objectClass: sambaSamAccount
objectClass: shadowAccount
objectClass: posixAccount
objectClass: inetOrgPerson
shadowMin: 1
shadowMax: 99999
shadowWarning: 10
shadowInactive: 10
shadowExpire: 22278
shadowLastChange: 13419
uidNumber: 26027
gidNumber: 2023
homeDirectory: /home/bradb
loginShell: /bin/bash
givenName: Brad
mail: bradb at advocap.org
sn: Bingham
structuralObjectClass: inetOrgPerson
entryUUID: 838796c6-e37f-102a-9af5-ccd5da83767c
creatorsName: cn=Manager,dc=advocap,dc=org
createTimestamp: 20060928205610Z
userPassword:: xxxxxxx
entryCSN: 20061005160616Z#000001#00#000000
modifiersName: uid=bradb,ou=People,dc=advocap,dc=org
modifyTimestamp: 20061005160616Z

From kolab test:
dn: cn=Brad Bingham,dc=advocap,dc=org
objectClass: top
objectClass: inetOrgPerson
objectClass: kolabInetOrgPerson
sn: Bingham
cn: Brad Bingham
givenName: Brad
userPassword:: xxxxx
mail: bradb at advocap.org
uid: bradb at advocap.org
kolabHomeServer: mailtest.advocap.org
kolabInvitationPolicy: ACT_MANUAL
structuralObjectClass: inetOrgPerson
entryUUID: 3a1bc7f0-60cd-102d-966a-c14e19117a33
creatorsName: cn=manager,cn=internal,dc=advocap,dc=org
createTimestamp: 20081217212718Z
entryCSN: 20081217212718Z#000000#00#000000
modifiersName: cn=manager,cn=internal,dc=advocap,dc=org
modifyTimestamp: 20081217212718Z


One possible problem I see is in the People dn records.
Will kolab work with my People dn entries?

Will I have to add these for each user?
objectClass: kolabInetOrgPerson
kolabHomeServer: mailtest.advocap.org
kolabInvitationPolicy: ACT_MANUAL
I suspect yes.

Anyone have migration scripts?

I  prefer kolab to be a slave but either way that is a small issue.
I see kolab is  using slurp. Can I use sync replication instead?
I'm going to have to do a lot of editing to slapd.conf anyhow.

Looks like ldap account manager has provisions for kolab so I assume that will 
work for user administration. Any recommendation on anything else?

John