omldapsync and mailbox enabling a im contact

[mrrus]

Hello

I'm using omldapsync in a test environment to create all the Scalix Mailboxes and IM contacts, that currently exist in Win2k AD, in the Scalix directory.

I have configured the ldapsync agreement and the initial and update sync's work fine.

I want to migrate users over in groups.
So the plan is to set the AD Custom Attributes, 10 and 11 on a subset of users.
This will then create mailboxes for the subset of users and all the remianing users will have IM accounts in the Scalix Directory.
This will enable the migrated clients to have a fully populated address list.

Then as i want to migrate another group i want to change their 10+11 Custom Attribute to true and mailnode, to create a mail enabled account rather than an IM account. Is this supported ?

Testing so far has not allowed me to change an IM account into a Mail enabled account.

Many Thanks
Mark Rus

[florian]

Nobody picked this up, so I guess it is still me! ;-)

I gather from your description that an IM account is an Internet Mail (or Foreign) account in the address book.

At this point, omldapsync does not support conversion of a user from type Internet to type Mail. We just had an internal discussion yesterday if and how we should possibly address this and it will probably be done in a future release.

There is a workaround, however.

1. Create two agreements, one called "IM", the other "MAIL" or similar.
2. In the IM agreement, add a condition (custom10!=TRUE) to the input filter
3. In the MAIL agreement, add a condition (custom10=TRUE) to the input filter
4. make sure that both agreements are ALWAYS run in direct sequence, IM first, then MAIL

The IM agreement will ONLY ever pick up IM entries, the MAIL agreement will only ever pick up MAIL entries.

In the case of a conversion, the IM agreement will first pick up the "no longer fouind" IM entry and delete the IM user from the address book. The MAIL agreement will then newly pick up the entry and creae user account and mailbox.

This should do the trick. (Has been implemented this way at various customers!)

Thanks,
Florian.

[mrrus]

Thanks Florian.

Maybe i didn't explain the IM account well enough, as i think you have misunderstood the question.

The IM account is the non-mailbox enabled account on the Scalix Directory that is created by omldapsync when an Active Directory account does not have CustomAttributes 10 and 11 set.
This is so that whilst in the co-existance stage, mail to a user who's mailbox has not been migrated will not get picked up by Scalix SMTP, but will be forwarded to the exchange mail server via send's mailertable.

Should these Scalix non mailbox enabled accounts be able to be changed to Mailbox enabled at a later stage, via omldapsync option 3:, when CustomAttributes 10 and 11 is set on their account, as i migrate groups of users across.

So the process i intend to use is:
1. Create the sync agreement
2. Modify the CustomAttributes 10 and 11 set on an initail small group of users. This will create a small group of Mailbox enabled accounts on Scalix and the remainder of the organisation wil only have IM (non-mailbox enabled) accounts.
3. CustomAttributes 10 and 11 set on another group of users and migrate their mailboxes across.
4. Repeat this process until all accounts have been migrated.

In my current test environment when i modify the Active Dir CustomAttributes 10 and 11, and do an omldapsync Option 3:, the non-mailbox enabled account does not change to a mailbox enabled account. Should it do ?

Many Thanks
Mark Rus

[florian]

Hi Mark,

no, because what you want to do is quite exactly what I have been describing in my resolution above in this thread.

With the attributes unset, ldapsync creates what we call an "Internet User" inside Scalix, which is basically a foreign address directory object.

omldapsync currently does not support the conversion of an Internet User object to a Scalix User object. We are looking into changing this behaviour.

So, the only way to archieve this is to first DELETE the Internet User object, followed by the creation of the Scalix User object.

Unfortunately, this can not be archieved in one ldapsync template.

The two-template solution outlined above will work though.

If you send me your sync.cfg by email, I will send you back the required modifications to this template and also how sync.cfg must look like for the second template.

-- f.