0 votes

The past week all my scheduled tasks to move users to specific OU's have stopped working. For example I have a scheduled task set up which moves a user to an OU called "Leaving" based on specific conditions. I have another which moves a user to "Expired" also based on conditions. They have worked for months without a problem but now the users are being moved to the "Disabled User" OU which is what the previously mentioned OU's sit under. It's as if Adaxes is now ignoring the subtree level. If I look at the logs they are logged as being moved to the correct locations, but when looking via AD this doesn't reflect what the logs/task say.

Any ideas?

by (350 points)
edited by
0

Hello,

For troubleshooting purposes, please, post here or send us (support@adaxes.com) the following:

Any additional details will be much appreciated.

Please log in or register to answer this question.

Related questions

0 votes
1 answer

Hi, I have a business rule setup to perform actions after user creation. First action is to run a powershell script which works and it sets a required AD attribute ( ... new user sits in the original OU and does not move Am i missing something here?

asked Feb 6 by Lewis (40 points)
0 votes
1 answer

I have setup a form to allow HR to edit some details on AD accounts. Currently the scope is limted to only AD object under one pre-chosen OU. The other option is an ldap filter. How can I allow this action to display user accounts from two seperate OU

asked Nov 18, 2019 by ice-dog (170 points)
0 votes
1 answer

Hi team, I have a follow up to this question https://www.adaxes.com/questions/14234/business-after-adding-members-powershell-script-executed Let me explain my setup A rule- ... area% failed due to the following exception: $($_.Exception.Message)", "Error") }

asked Feb 13 by wintec01 (1.5k points)
0 votes
0 answers

Ever since upgrading to 3.16.21906.0 the script here no longer works: https://www.adaxes.com/script-repository/move-mailbox-tofrom-microsoft-365-s579.htm Not sure what the issue is as I can't find any errors in the log.

asked Nov 16, 2023 by curtisa (290 points)
0 votes
1 answer

an OU is created in the Active Directory. but when I'm trying to select that in "password policy". the Adaxes is not allow for me to choose OU. only AD users and groups can be selected. is there any way to choose OU?

asked Sep 23, 2020 by justinh (60 points)
3,538 questions
3,229 answers
8,222 comments
547,736 users