0 votes

Hello,

I am trying to create a custom command that handles the process of converting a user account for a temp to a FTE. This needs to:

1. move the user to a new OU.
2. change properties of the user.

My problem is that the source OU and destination OU's have different User property patterns. The command moves the user fine, but when it tries to rename the user or change other properties, it errors out on the property patterns as if the user was still in the source OU.

How do I get Adaxes to use the property patterns of the new OU instead of the old?

Custom command:
Set 1:
If user is located under "expiring accounts" OU
--Move the user to "xxx" OU

Set 2:
Always
--Modify the user: set employee type to...... etc.

by (710 points)

1 Answer

0 votes
by (215k points)

Hello,

This is a bug in Adaxes that we'll fix in the next release. Thanks for the bugreport!

For now, we can suggest updating user properties using a PowerShell script. For example, in your Custom Command, you can use the Run a program or PowerShell script action instead of the Modify the User action to perform all the property modifications. To do this:

  1. Launch Adaxes Administration Console.

  2. Locate and select the Custom Command that you use for transferring users from temp to FTE.

  3. Double-click the Modify the User action that you currently use to update user properties.

  4. Select the Run a program or PowerShell script action.

  5. In the Script field, type a script that will update the properties that you need.

    For example, the following script sets Employee Type to 'FTE' and Office to 'NY Department'

     $Context.TargetObject.Put("employeeType", "FTE")
     $Context.TargetObject.Put("physicalDeliveryOfficeName", "NY Department")
     $context.TargetObject.SetInfo()
    

    For more information on how to update user properties with scripts, see Modifying User Accounts.

  6. When done with the script, enter a short description for it, click OK and save the Custom Command.

0

Hello,

Yesterday, we released Adaxes 2013.2 that contains a fix for the issue. Now, if an AD object is moved in a Business Rule, Custom Command or Scheduled Task, the object location is properly updated. You can download Adaxes 2013.2 here.

Upgrade Instructions.

For a complete list of new features and improvements, see What's New.

Related questions

0 votes
1 answer

Is there an order of precendence for Property Patterns? If I set a property pattern at a level lower than another property pattern is set what happens? Will one work and the other won't?

asked Aug 18, 2020 by ComputerHabit (790 points)
0 votes
1 answer

How can I check or run reports on an entire Property Pattern to ensure integrity? I know I can run a check on an individual property, but this is really inefficient since I have already defined a Property Pattern for a specific object to abide by.

asked Jul 16, 2014 by chazlander (120 points)
0 votes
1 answer

Given Scenario: Adaxes domain user is remote with his laptop and has adaxes self service client installed on Windows and is enrolled for self service via Adaxes. We ... get updated when a user initiates password reset/change password from the lock screen ?

asked Nov 2, 2020 by rsaran (70 points)
0 votes
5 answers

Good morning, We have been testing two separate laptops with the new off-site password change feature. We can successfully reset the password from the Reset Password option on ... accept the new password, only the old. AD is updated successfully. Please help!

asked Aug 27, 2017 by Piko (210 points)
0 votes
1 answer

Hello! We are using the new Adaxes 2014, and I have stumbled upon the two following events: * Calculated default values are not updating when we are creating a new ... also have their home drive hardcoded in their user profile is not necessary. Regards, Erlend

asked May 5, 2014 by Erlend (160 points)
2,738 questions
2,473 answers
6,471 comments
1,359,249 users