Name Change, delayed

Question

I'm looking to setup a process where the HelpDesk or another IT user will basically go through a name change for a user and the modifications will kick off later at night.

Basic workflow:

IT selects Name Change action, and changes the following fields:

Display Name First Name if applicable. Last Name User Logon Name User Logon Name (pre-windows 2000) Email Home Folder Path \server\Home\NewName

Exchange Alias SMTP Email Addresses

Then after they save it:

Email is sent out to User/Helpdesk informing them the change is scheduled.

A scheduled task is submitted to kick this off at 9pm at night.

What's the best way to accomplish this?

Answer 1

Hello,

You will need to use a custom command with parameters and a scheduled task. The custom command will save specified parameter values into Adaxes custom attributes. The scheduled task will take values of the attributes and update the corresponding AD attributes accordingly. The following tutorials will be helpful:

• Create custom command
• Schedule tasks for directory management

If you have issues configuring the workflow, we will gladly provide you with screenshot of the configuration you should have. In this case, please, specify whether all the changes will always be the same or some properties can remain unchanged. Any additi9onal details will be much appreciated.

Comments

An example to how to get started would be helpful. I've not worked with the parameters before, and don't understand how they connect yet.
The fields we normally change are these. I'll put optional next to anything that may be not changed, as it would not usually fall under a Name Change.

• Display Name
• First Name (Optional)
• Last Name
• User Login Name
• User Login Name (pre-windows 2000)
• Email
• Home Folder Path
• Exchange Alias
• SMTP Email Addresses

In this case, please, specify whether all the changes will always be the same or some properties can remain unchanged.

So, if I understand you correctly, the changes to the above fields will always happen on a Name Change, with the exception of the First Name which is unusal to change.

Also the last two fields for Exchange which is O365 fields, I don't current change these, the Exchange Admin does, but I assume on the SMTP Addresses we just need to ADD additional ones, and leave the old ones for possible later clean up.

Lastly, when you do a manual Name Change, RIGHT CLICK on the user, and RENAME, and your renaming the Display Name there, is this field called Display Name? Or is that another field?

---

Hello,

So, if I understand you correctly, the changes to the above fields will always happen on a Name Change, with the exception of the First Name which is unusal to change.

That is not correct. All the changes will have to be done using a custom command. There is no possibility to make the changes the way you want if it is done in any other way. Also, we would recommend you to disable the rename operation in the Web interface. Finally, the configuration should look like below. Pay attention that the custom attributes from the setup must not be used in any other workflows.

Custom command parameters Custom command setup Scheduled task As for the SMTP Email Addresses, if you need to be able to specify multiple values and then add them to the existing list of email addresses, it will require using a PowerShell script.

Lastly, when you do a manual Name Change, RIGHT CLICK on the user, and RENAME, and your renaming the Display Name there, is this field called Display Name?

That is the Full Name property. However, when making a change this way, after pressing Enter you will see a form with other properties that might also require changing.

---

Ahh!! I see the whole process and totally makes sense now!! Wow, I think you opened a new world for me with this method!! Thank you!

Lastly, is there a way to have a Schedules Task created specifically for the user instead of a broad one that scans every user? Like a powershell that creates it after you submit the name change?

---

Hello,

Yes, it is possible using a script. The following article should be helpful: https://adaxes.com/sdk/ManagingScheduledTasks.

---

Everything works great, thanks!