vlaurenz wrote:Looks like the unique id for your users has changed in the new LDAP server. My first instinct tells me that you will have to run omldapsync with the -L flag to reload the Scalix directory. You'd then have to accept (either -A or -P) any errors.
Your other choice is to obtain all the new unique ids and come up with a script which will run an ommodent for each affected Scalix directory entry and change the unique id to match that of the LDAP server.
Hope this helps.
Thank you for the reply.
But it did not help, the omGlobalUniqueId did no change in scalix.
And when i run ommodent it looks like i can't change the omGlobalUniqueId...
[root@scalix ~]# ommodent -e "S=Olsson/G=Mikael/OU1=se-ka-sr020/OU2=se-ka/CN=Mikael Olsson" -n omGlobalUniqueId=79f964e2-f228-102a-9742-efbc7a07903a
omGlobalUniqueId=79f964e2-f228-102a-9742-efbc7a07903a
[OM 16073] Unknown attribute specified.
Attribute : omGlobalUniqueId
The solution that works so far is:
backup a mailbox
delete the user
remove the scalixUserClass for the user in OpenLDAP
run omldapsync
delete the user in scalix
add the scalixUserClass in OpenLDAP
run omldapsync
restore the mailbox
But this is a very slow process and might not even work for some users with big mailboxes (> 2GB), so i really need some way to modify the omGlobalUniqueId in scalix.