OPS Manager - IDS - Active Directory Sync

[AH64Armament]

Has anyone had any experience with the AD sync?

The site has had OPSMAN for many years since OPSMAN rel 3, now it's EMAN 6.0 with OPSMAN 9.0!
They had purchased the IDS integration features for use with Novell, back in 1999 or 2000. At the time of purchase, Novell had released a new version and broke the connector. We never pursued this until this past spring.

We touched it and couldn't get it to work, time went on, and communication was misunderstood, and the project got pushed.

Yesterday we got the connector to work, but it isn't working properly. (according to Mitel support, it is working to design specs).

The ONLY container that it "pushes" to is the default container specified in the IDS configuration. However, OPSMAN will read other containers.
A user in one container with an active account, OPSMAN will poll that info on a sync, but anther sync seems to create a new account in the default container.

This is a big problem, as the site has roughly 50 containers, one for each department. Some with over 150 users.

Does anyone have any experience in getting OPSMAN to push the info into the appropriate container.

Thanks in advance,
Mark

 

[Mitel100]

Opsman can only search one OU in AD, within this OU you will / should have all other departmental OU's within this one.

What I have found with the opsman, DO NOT select Yes, in the Opsman, as some will be created in the default container, as this really annoys the AD Administrator.

I always get the AD admin's to manage it from their end.



__________________________

There is no 'I' in 'Team'
__________________________