Examples of tasks that can be delegated using UMRA

This page provides an overview of tasks and forms commonly used by our existing customers. Please note that this is a cross-section; the actual tasks and forms may differ significantly, along with the type of network and organization. Since UMRA is based on ‘building blocks’, tasks and forms can be adapted to your specifications very easily.

Reset a password

To reset a password, a user must be selected in a table. The option to reset the password must then be enabled. Two options are available: One is to reset the password to a default, after which users are asked to specify a new password when they log in again. The other is to have a helpdesk agent specify the new password.

Create a user

When a user is created, the required input will often be limited to the users first name, last name, and in some cases a middle name, as well as their department and/or location. There is usually the ability to select a department or location from a table. General items will be linked to the location, such as the user’s address, telephone number, file server, mailbox store and group memberships. Users must typically be created entirely at one time, i.e. in the right OU, with the correct group memberships, home directory, profile directory, mailbox etc.

Set/remove group memberships

Helpdesk agents can select a user and add him or her to groups or remove current group memberships. One option is to have a limited number of groups displayed so that helpdesk agents cannot assign users to groups such as Domain Admins.

Disable a user

As it is not desirable to have users deleted completely in one fell swoop, it is possible to just disable users. Here, the user will often be transferred to a separate OU. In some cases a form may be required, with which disabled users can be re-enabled. To disable a user, helpdesk agents can select him or her from a table, confirmation will be requested, and the user will then be disabled.

Delete a user

Before users are deleted, they will often be disabled for a period of time. In this context, it is nearly always desirable that something also happens to user data (e.g. renaming or removing the home directory). To delete a user, helpdesk agents can select the user from a table, confirmation will be requested, and the user will then be deleted.

Relocate a user/changing a user profile

When a user’s position or department changes, it is often necessary to modify that user in Active Directory. Changes may include relocation to another OU, modification of group memberships, modification of the user’s location data (e.g. his telephone number and address) and the relocation of the user data to another server. The helpdesk agent will be able to select a user from a table and then select a new position or location and the appropriate actions will be taken.

Rename a user

It may be necessary to rename a user, e.g. after a wedding or divorce. Administrators can modify details using a form. This would otherwise involve a substantial effort (modifying the user’s name, email box, home directories, profile directory, display name, etc.). That said, it is also possible to assign the user an alias with their previous email address so that no email messages are lost. The helpdesk agent will select a user from a table and specify a new name and the appropriate actions will be taken.

Modify user data

This involves modifying general user details, i.e. all the details that can be entered in the Active Directory.

Update fields

Among other things, this may be used by the reception staff to manage a user’s telephone number. It is also possible to make the form available to all employees and limit the modification options to the user’s Active Directory record as well as a fixed set of fields, i.e. the user’s telephone number, room number, address details etc. It is also possible to make this form available in a web form and to frame it in the existing web portal, e.g. Sharepoint.

Create a group

New groups can be created for project groups, new departments and new applications, among others. The helpdesk agent will enter the name and group type, after which the group is created.

Migrate a user account

This involves migrating a single user account from location A to location B. This will often have consequences to the location of the home and profile directories, group memberships and distribution lists.

Create a share

This option is commonly used when a new data directory is required. This makes it possible to create a new directory share and group by simply entering a share name. The helpdesk agent will specify a name for the share and, if needed, a location. All the correct privileges will be set automatically and the matching groups will be created.

Create/relocate a computer account

When a workstation is added to the network, a computer account will be added to a default OU. This action requires domain admin privileges. If it is not possible to assign domain admin privileges to the person installing the workstation and the computer account has to be placed in the right OU, this can be solved by using a delegated form.