Architecture

User Management Resource Administrator's architecture is centered around
4 basic themes: organization, interfaces, engine and network.
This architecture enables User Management Resource Administrator to bridge
organizational structures such as HR information systems or departmental
structures such as the Helpdesk to the network level of the Active Directory.

Organization

The organization level represents the applications or departments within an institution; this is a high level view. Large organizations usually have a Human Resources Information System for employee data storage or Phone System to store employee location and contact data. Large educational institutions have Student Information Systems to warehouse student-related data. These organizations also have departments such as Information Technology and a Helpdesk that are dedicated to operating these systems and linking them to a network environment such as Active Directory. These applications and departments require an interface to input their data for processing into Active Directory.

Interfaces

When following the separation between applications and departments within an organization, the same level of separation works for the interfaces level. The applications require an automated interface to supply employee-related data to the engine for translation into Active Directory user accounts. At the same time, departments require an interface for manual user input using either a Windows application or web browsers.

Engine

The User Management Resource Administrator engine handles the input from
the automated and user input interfaces from the previous level. The engine
itself is triple-layered: authentication - processing - execution.
The authentication layer is responsible for authenticating user accounts when utilizing the engine; it authenticates the user and downloads the list of forms that have been delegated to the user. When the user submits the form to the engine, the information from the form is processed by the engine and executed in Active Directory after validation. Forms can only be created and modified by the network administrator; the form is then published to delegated end-users by assigning it to Windows user accounts or groups. The processing layer is responsible for data processing and validation. This part of the engine is controlled through the script which has been assigned to either the automated or form-based input data. All data from the interface passes through the script, which can only be created and configured by a network administrator, and is submitted for execution. The execution layer can optionally be configured to hold jobs in a queue awaiting approval or configured to simply run as the delegated user submits them. IT staff can then approve or disapprove items in this job queue to prevent the cluttering of Active Directory.

Network

The network level represents all network resources containing user-account-related data, such as: files, mail and user accounts. The User Management Resource Administrator engine natively communicates with Active Directory and the NT SAM to score, modify or delete user account information. When a job is submitted through the engine, all user account information and resources can be created directly on the Windows level. This includes Active Directory related settings such as: user account, Organizational Unit assignment, group memberships, all attributes, Terminal Server settings, dial-in configuration and much more. User-related resources include home directories and share permissions on file servers, and also mailbox creation and configuration on Exchange servers.

Architecture Overview

I have some questions, can you guide me through?

We are absolutely confident that User Management Resource Administrator will work for your environment -whatever the size; we can show you the product and all its capabilities in just 30 minutes on our test server for free!

View 5 minutes flash movie

View the Guided Product Tour

Request Live Online Demo

Download Trial version NOW