SAC vs AD 2003

[mario_aac]

Hi there,

I'm in the middle of integration Scalix 11.4 with AD 2003. Everything works as described in manuals. omldapsync, with patched a little bit config, fetches any data, but... when I login into SAC any option regarding user is greyed out (disabled, unable to change value). I can change user options with ommodu, but not in SAC. Is it because I've set agreement type to 11? (import only)

Scalix 11.4 Small Business on SLES 10.2

Thanks
Mario

[Valerion]

When you are synchronizing with another source, all changes should be made in one place. Otherwise your changes will be undone at the next sync. SAC enforces this, while ommodu does not. Conflict handling is NOT pretty, if it was changed in both places.

I suggest you stick to just editing it in AD.

What kind of changes are you making?

[mario_aac]

I agree that in production state any changes should be made in one place. But during development I just wanted to change few things like SWA access or passwords just for testing purpouses.
It might be usefull to allow at least SIS index recreation from SAC in this case.

That's all I wanted to know.
Thanks

[Valerion]

I agree things like SIS re-indexing could be done from SAC, and I suggest you raise an enhancement request for that. Doesn't affect anything configuration-wise, really.

Just remember that real settings (e.g. SWA access) might very well be re-populated from the original server, even in a testing environment. You may want to temporarily disable omldapsync if you do that.