Has anyone had a problem whereby when opsman ids does a sync with AD it does not pick up changes. We have found that by changing the ldap path in ids to point to a specific AD folder where a change is sitting then it will be picked up. However, the ids ldap search is not searching subfolders. When set to the normal search path, it's not hopping past more than one folder.
It used to work, I'm told that it stopped working when the AD server was migrated to windows2003 but I don't know that for sure.
We have also proved that the AD limitation on allowed object searches is not the cause, we changed that from 1000 to 50,000 to prove the point to Mitel.
