Once you have deployed the pilot Administration Service and updated its configuration, you can deploy the Web Interface for your pilot project. You have to ensure that your pilot instance of the Web Interface meets the following conditions:
You can address these conditions as follows:
You can identify your existing site configuration objects by using the Web Interface Sites Configuration wizard on the computer running your production Web Interface. For detailed instructions, see Upgrading the Web Interface earlier in this document.
You can install the Web Interface of version Active Roles side-by-side with the Web Interface of version 6.9, on the same computer. Another option is to install the new Web Interface on a different computer.
Optionally, delete the default sites that were created when you configured the Web Interface in Step 2. The default sites are unaware of your existing site customizations, and have the default configuration of menus, command, forms and other elements. For instructions on how to delete the default Web Interface sites, see Upgrading the Web Interface earlier in this document.
You need the Active Roles console of version 7.4 if you want the console to connect to the Administration Service of version Active Roles. As the console of version 7.4 does not connect to the Administration Service of earlier versions, the use of the console version Active Roles for your pilot project ensures that the console automatically connects to the pilot Administration Service.
For installation instructions, see Steps to install the console earlier in this document.
There are no technical requirements for installing many Administration Services in a location or in different locations. The number of Administration Services in a location and the number of locations with Administration Services depends on an organization’s needs and expectations, the current infrastructure and hardware, and the business workflow. When considering an To add the Active Roles console (MMC Interface) to the pilot deployment, simply install the new version of the console on an appropriate server and have the console connect to your pilot Administration Service. deployment, administrators should consider the following issues:
When an organization has gathered and assessed the information above, it will be able to determine the locations and number of Administration Services to be installed. The last sub-section provides network diagrams that illustrate potential Active Roles deployments.
This factor focuses on Active Directory (AD) data management processes and practices, including who will perform these tasks and from where they access the management services. Generally, these tasks will be divided among several groups, which might include both high- and low-level administrators, a Help Desk, HR personnel, and work group managers.
Possible business workflows for AD data management processes might be:
Organizations should diagram the locations/sites at which AD data management is done, their network connections, the number of users performing tasks, the type of work they do. For example, Help Desk personnel will make more use of the Administration Service than regular employees who are occasionally changing their personal information.
Finally, the number of users at each site should be added to the diagram. Current customers report that there has been no need to install additional services in order to improve Active Roles performance. Adding the number of users is not intended to indicate the workload on or the performance of the Administration Service. The number of users is intended to help organizations to estimate and understand their own administration workload and how Active Roles will fit into that workload.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책