2 of 2 people found this helpful
Please use the following;
Select a step "LDAP input"
Here add a script in "Search" like;
(!(OU=Admin Accounts,OU=Corporate Administration,DC=<DOMAIN>,DC=com))
Hope this helps?
Thank you so much for your assistance and sorry about delayed in response.
I tried the script above and modified based on testing i am performing, since i am just testing for one OU called test, i have modified the script as bellow-
But it failed, though it still successful if I select Dynamic filter string, Please correct me where i am wrong.
Once again i appreciate your assistance.
Did you also push the 'whenChanged' attribute from AD to the corresponding BMC AR System form ?
If yes, then, were you able to get the correct data in the date field on the form ?
The reason I am asking this is because, when we map the whenChanged attribute from AD to a date-time field on a staging form in Remedy, the date-time field is set with an incorrect value (eg: a date-time value in the future, which is certianly wrong in case of the whenChanged timestamp) when the Spoon job runs
Do you know about this issue and happen to know the fix for the same ? Do let me know
I have a case with the customer where I need to exclude the accounts which are already disabled.
CUrrent job pulls all the profile from AD even if they are disabled.