UMRA & Migration

Many companies are apprehensive about implementing UMRA when they are in the middle of a migration process to an Active Directory (AD) environment. A common misconception is that the migration must first be completed before UMRA will work properly, another is that starting a different project during the process of migration might overcomplicate matters, and delay the project deadline. However, the truth is that UMRA assists migration both pre and post project and streamlines the process. Tools4ever provides indispensable project management expertise which speeds up the migration process.

There are two common migration scenarios. The first of which is domain consolidation -multiple AD domains being collapsed into a single domain. In this scenario UMRA is able to recreate the user account and, more often than not, retain the username in the new domain. In a situation where the migration results in the duplication of names, organisations can choose to implement new naming conventions.. UMRA will create a new user name and alert end users, via email, what their new username will be along with the date from which that name will be valid. .

Not only is the user migration process streamlined, but the resources of those users are as well including items such as group memberships and home directory data. As users are migrated UMRA will retain their group memberships, if one of groups doesn't reside in the new domain UMRA will create it automatically. Home directory data can either be copied to a new server in the new domain or re-permissioned on the existing server with the SID of the newly migrated account.

UMRA also assists and eases the migration process by:

Eliminating Pollution-Most migration tools will copy 1:1 which will include erroneous and/or stale accounts. However UMRA migrates users by reconciling them against a HR/SIS system so that pollution is not included. Activity reports on un-used groups are generated so that these objects are not migrated.

Fill Attributes-When migration takes place there might be some missing information such as "title" or "Department". UMRA automatically populates this information as needed.

Single Sign On: regulating access cards

By now, many organisations are aware of the advantages of Single Sign On (SSO). Employees benefit from SSO because they only have to remember a single (complex) password rather than dozens of (complex) passwords, the IT department receives fewer password reset calls and network security is enhanced ensuring the organisation can meet auditing requirements.

Read more

Who’s speaking please?

The majority of calls received by the IT helpdesk need to be verified. After all, to protect the network, helpdesk needs to be certain that the caller is who they say they are before they can grant access rights to applications. So, how can they do this whilst protecting each end-user's personal information?

Read more

Access Management and SOX compliancy/audits

We frequently deal with companies that have to be compliant to SOX regulations. This often has a big impact on the IT department, particularly with regards to managing access rights. We find in these scenarios there are three very common issues which tend to arise:

Read more

Password Synchronisation vs. Single Sign On

Clients often ask me to advise them on reducing the number of passwords end-users need to use in order to access their account and applications. Their first approach, in order to avoid multiple passwords, is usually to ensure that passwords are synchronised over different systems.

Read more

SSO- The new software that could be the answer to NHS data protection woes

Healthcare organisations such as hospitals and surgeries operate complex networks comprising various applications running on multiple systems. Users need to have access to multiple applications for e-mail, the helpdesk and patient data, etc. In order to comply with increasingly strict security requirements, staff must enter separate username and password combinations for each application.

Read more