-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delta Import not running when AD trigger scoped to a sub OU #165
Comments
2019-04-19 10:42:43.0139| WARN|Could not map run profile DeltaImport for partition OU=ENT__MIM__Dev,OU=DoNotTouch,OU=Test__ENT,DC=domain,DC=company,DC=com because the partition was not found The partition in the MA is DC=domain,DC=company,DC=com |
Hi Ryan! |
Hi guys, sorry this one slipped through the cracks. I have a workaround for you. If you stop the autosync service, and open the config.xml file for editing, you can actually specify a specific run profile to associate with the trigger. This is just not available in the UI. Locate the management agent and trigger in question, and look for the Replace the element as follows, replacing Let me know if that solves the problem for you. Ryan |
Thanks Ryan, that worked fine! |
If the AD trigger Base DN is set to a sub OU (OU=MyOrgUnit,DC=company,DC=com) and the partition in the MA doesn't match (DC=company,DC=com), the import request gets dropped with a "no matching run profile could be found in the management aget partition OU=MyOrgUnit,DC=company,DC=com".
Using version 1.2.6995.24206
The text was updated successfully, but these errors were encountered: