Unable to process 512 user account control

Jay81
Tera Guru

Hi,

 

When I create user account from Ad activity in orchestration it accepts only useraccountcontrol value 544. When I directly create user account in AD it is created with user account control value 512. Please help.

 

 

1 ACCEPTED SOLUTION

Hi Priya,

 

Issue is fixed after encrypting the password using GlideEncrypter and adding "Reset AD user password" and "enable AD user account" activity. 

Thanks for sharing the steps to validate AD attributes.

 

 

View solution in original post

4 REPLIES 4

Jay81
Tera Guru

I'm getting "The server is unwilling to process the request." error message when pass value 512 in useraccesscontrol.

Priya Shekar
Giga Guru

Hi Jay,

Every normal user's  UseraccountControl set to 512  and for those user who have set Password not required and enabled, UAC set to 544.

To change the UAC , follow the steps :

  •  run the adsiedit.msc in Run ( on DC )
  • Connect the Default Naming Context
  • Browse the required user which you have want to change  
  • right click and choose properties and browse the UseraccountControl attribute
  • set the  512 instead of 544

If my reply has helped you,Kindly click the Helpful button.
If my reply is the answer you were looking for, Kindly click the Accepted Solution button.
Thanks,
Priya

Hi Priya,

 

Issue is fixed after encrypting the password using GlideEncrypter and adding "Reset AD user password" and "enable AD user account" activity. 

Thanks for sharing the steps to validate AD attributes.

 

 

PoojaB
Tera Contributor

This is super helpful, thank you for sharing this. My team was able to resolve the issue using the above solution