Examples of user account management you can delegate with UMRA

This page offers an overview of tasks and forms that we frequently find in use at our clients. Please note that this is an average sample. The actual tasks and forms may differ greatly with each network and organization. UMRA is based on so-called building blocks, which makes it very easy to adapt tasks and forms according to the applicable specifications.

Password reset

For this purpose a user is selected from a table, while an option for resetting the password is offered. Two preferences are available for this option. One is to reset the password to a default password, so that the user proper will have to specify a new password at the next login. The alternative is that the help desk agent proper specifies a password.

Creating a user

In this scenario, the input usually remains limited to a first name and surname (with the possibility of a middle name) and a department or location. Oftentimes, it will be possible to select the department or location from a table. General items will be linked to the location, such as an address, a phone number, the file server, mailbox store and group memberships. The creation of a user usually has to place take place in one go. This means the right operational unit (OU) has to be specified along with the right group memberships, home folder, profile folder, mailbox etc.

Setting/revoking group memberships

A help desk agent can select a user and add the latter to groups or revoke existing group memberships. It is possible to limit the display of groups to ensure that help desk agents cannot create users for groups like Domain Admins.

Disabling a user

It is preferable not to remove users straight away. For this reason users are only disabled. Users will typically be moved to a separate OU. In some cases members of the organisation may request a form for re-enabling disabled users. For this purpose, a helpdesk agent will be able to select a user from a table. Subsequently, the system will ask for confirmation, upon which the user will be disabled.

Removing a user

Before users are removed, they are often first disabled. In this scenario, it is almost always desirable that something is done to the user data as well (e.g. renaming/removing the home directory). For this purpose, a helpdesk agent will be able to select a user from a table. Subsequently, the system will ask for confirmation, upon which the user will be removed.

Migrating a user/modifying a profile

When a user’s role or department changes, it will often be necessary to modify the user in the Active Directory. This usually involves changes such as migrating the user to another operational unit, modifying group memberships, modifying the user’s location data (e.g. the phone number and address) and migrating user data to another server. For this purpose, the helpdesk agent will select a user as well as a new location/role from a table.

Renaming a user

Users are renamed for instances such as a marriage or divorce. Sometimes it can be uncomfortable for users when the name of the former husband is still contained in their e-mail address or login name. This form allows administrators to make changes to data that would normally involve a labor-intensive process (user name, mail box, home directories, profile directory, display name etc.). It is possible to assign users an alias that is associated to their previous e-mail address, so that e-mails to the former address are not lost. For this purpose, the help desk agent will select a user from a table and specify a new name.

Modifying user data

This involves modifying general user data. This includes all data that can be specified in the Active Directory.

Updating fields

Among other things, fields are updated so that the phone number can be managed by reception desk agents. It is also possible to make this form available to all employees and subsequently to limited the modification options to the users’ proper Active Directory as well as a fixed set of fields (e.g. phone number, room number, address data etc.). It is also possible to make this form available in the shape of a web form embedded in an existing web portal (e.g. Sharepoint).

Creating a group

This involves creating new groups, e.g. for project groups, new departments or new applications. For this purpose, the helpdesk agent will provide the name and the type of group, upon which the group will be created.

Migrating a user account

In this scenario, a single user account is migrated from location A to location B. This will often have consequences for the location of home and profile directories, group memberships and distribution lists.

Creating a share

Typically, shares are created when a new data directory is required. In that case, a new directory, share and group can be created by specifying a share name only. For this purpose, the helpdesk agent will specify a name for the share and optionally a location. All privileges are subsequently arranged automatically, while corresponding groups are created.

Creating/migrating a computer account

When a workstation is added to the network, a computer account will be added to a particular (default) organisational unit. This operation requires domain admin privileges. Where domain admin rights cannot be assigned to the person responsible for the installation of workstations and the computer account has to be added to the right operational unit, then the solution is to use a delegated form.