0 votes

Is there a way to grey out the 'Password never expires' option when a admin creates a new user in the Adaxes admin portal?

I'm in a closed environment and need to make sure that accounts are not created with this option set.

Thanks for any information!

-Chad

by (50 points)

1 Answer

0 votes
by (216k points)
selected by
Best answer

Hello,

Actually, you can completely remove this option from the form that is used for creating users. To do this:

  1. Launch the Web interface Customization tool.
  2. In the Interface type drop-down list, select the Web Interface you want to configure.
  3. Switch to the AD Management tab.
  4. Click Customize Forms and Views. The Forms and Views dialog brings up.
  5. In the Object types list, select the User object type.
  6. Activate the Create tab.
  7. In the list of sections that's located in the upper portion of the Create tab, select the section that contains the Account Options field. By default, this is the Account section.
  8. In the Section fields list located below, click the Configure link located next to the Account Options field.
  9. Uncheck the Password never expires option.
  10. Click OK 3 times.
0

I do not have the configure option....

0

Chad,

This functionality was introduced only in Adaxes 2014.1. You need to upgrade. You can get the latest build here.

Upgrade Instructions

Alternatively, if you don't want to upgrade, you can workaround with the help of a Business Rule. You can create a Business Rule triggered upon creating a new user that will clear the Password never expires option if it was set. To create such a rule:

  1. Create a new Business Rule.

  2. On Step 2 of the Create Business Rule wizard, select User and After Creating a User.

  3. On Step 3, add the Run a program or PowerShell script action and paste the following script in the Script field. The script will remove the Password never expires option.

    
     $Context.TargetObject.Put("userAccountControl", 0)
     $Context.TargetObject.PutPropertyItemMask("userAccountControl", $passwordNeverExpires)
     $Context.TargetObject.SetInfoEx(@("userAccountControl"))
    
  4. Enter a short description for the script and click OK.

  5. Right-click the action that you've just added and click Add Condition.

  6. Select the If certain Account Options are enabled/disabled condition.

  7. Check the 1st and the 2nd checkboxes for Password never expires.

  8. Click OK

  9. Finish creation of the Business Rule.

0

Excellent, thanks guys. I'm going to upgrade this weekend.

Related questions

0 votes
1 answer

Good Afternoon, Currently as far as I can tell when defining a new user we are forced to select a location for a newly created user before defining information like the ... If not, is there a better way of applying this sort of functionality? Regards Josh

asked Apr 21, 2014 by jtop (680 points)
0 votes
1 answer

I'd like to be able to either send an email report or export a CSV of all of the business rules carried out when a user is disabled. This would be ... Management Activity section but this includes things that weren't part of the disable operation. Thanks

asked Feb 19, 2020 by bavery (250 points)
0 votes
1 answer

Hello, I am having trouble updating adaxes custom attributes when creating a new user with the powershell module, would running the New-AdmUser also ... -EmployeeID $EmployeeID -MobilePhone $MobilePhone -OtherAttributes @{adm-CustomAttributeText1 = $title }

asked May 11, 2020 by bbartlett (20 points)
0 votes
1 answer

Hi, I would like to setup the self-service with a list of required hardware, printers applications etc for someone to select when creating a new user. Then when the user is ... this can be done under custom forms but im not exactly sure how to do this.

asked Dec 4, 2023 by STIG (40 points)
0 votes
1 answer

Hello, I am scripting user creation. I have created a custom command where an end user will submit info for the user to be created from: Here is the scirpt: # Import the ... Schema. I have tried using "Employee Type" as in the screen shot above but same error.

asked Apr 6, 2023 by mightycabal (1.0k points)
3,326 questions
3,025 answers
7,724 comments
544,678 users