Postby AussieOwner » Wed Mar 01, 2006 4:27 pm
Nathan
Option 1: If you are only interested in "syncing" Scalix with AD, there is another option. Sync ID 11 can be "tweaked" such that it is not necessary to extend the AD Schema. This is more of a "Provision Only" option, but it sounds like what you are looking for.
Option 2: If you *do* want to use the standard sync ID 11, they you will need to extend the AD schema to create the extended attributes. This gives you the ability to provision and administer from AD Users and Computers. Pros: This option gives you the ability to manage your Scalix Users from AD U&C. Cons: Entries are locked in SAC.
If you choose Option 1, then contact me out of band and i will send you the updated sync agreement that does not require AD Schema extension. darrell at scalix dot com.
If you choose Option 2, then you need to extend the Schema and create a Scalix tab on AD U&C. This is done from by installing the two .msi files on the Scalix 10.0 distribution located in /software/scalix-ade. Run both files on the GC Master of your AD Domain. If you only have one DC, then its the GC Master. Make sure you are logged in as Administrator. Not just an account that is part of the Domain Admins group. It must be a Schema Admin and typcally Administrator is the only member of this group. Once you install both of these .msi files, there will be a directory created called /Program Files/scalix/administrator. This directory will contain an .exe and .dll file. Run the ForestPrep.exe. This will extend the schema and add the new DLL to AD U&C. You will need to wait up to 15 minutes for this to be replicated, even if you only have a single DC. Once you (reload) AD U&C and see a "Scalix" Tab when you go to properties of a users, then you know that the schema has been extended successfully. You will need to click the "Scalix Maillbox" on the Scalix tab to have a mailbox created on the Scalix Server. Be sure to setup your omldapsync to run as a cron job.
Darrell Sturdivant