Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloud
or on-prem performance issues
|
||
|
Manually Configuring Parent and Child Domains
If you want to manage users spread across multiple domains, then, all domains, except the eG manager’s domain (which can be auto-discovered), will have to be manually configured using the eG administrative interface.
Follow the steps below to manually add parent and child domains:
Figure 1 then appears displaying the parameters to be configured for creating a new domain.
In the right panel of Figure 1, specify the following to create a parent domain:
Next, specify the fully-qualified Domain Name.
Note:
eG Enterprise disallows Domain Name duplication- i.e., you cannot assign the domain name of an existing parent/child domain to a new domain.
Then, to verify the correctness of your specifications, click the Validate button. Figure 2 will then appear indicating whether/not the Display Name, Domain Name, Domain IP, Port No, Domain User, and Domain User Password values that you have provided are indeed valid.
Figure 2 : Validating the specifications of a domain that has been manually configured
Once the parent domain is added to the eG Enterprise system, a message to that effect will appear (see Figure 3). The tree in the left panel will also change to reflect the addition of the parent domain.
Figure 3 : The tree structure indicating that another parent domain has been added
For all parent domains that are created manually, sub-domains also need to be manually created. To do so, follow the steps given below:
Right-click on the node representing the manually configured parent domain in the domain(s) tree, and pick the Add Sub-domain option from the What would you like to do? list in the right panel (see Figure 4) .
When Figure 5 appears, first provide a Display Name for the sub-domain.
Set the Discover DNS flag to Manual.
Note:
Note that if a parent domain is configured manually, then its sub-domains cannot be auto-discovered - i.e., you should not set the Discover DNS flag to Auto while configuring such a sub-domain.
In virtual environments where LDAP is used to authenticate access to the AD server, administrators may want to keep track on specific user information for e.g., location, vendor etc of the users accessing their environment through the AD server. For example, in addition to viewing the user experience with their virtual environment, if administrators are able to view the location of the user, it would help them troubleshoot location specific issues at the earliest. This approach would definitely help administrators improve the overall performance of their environment. To view such user specific information in the eG monitoring console, administrators should do the following:
First, set the Discover User Details from AD flag to Yes. By default, this flag is set to No.
Once this flag is set to Yes, the user specific information will automatically be populated in the ADUserDetails.ini file that is located in the <EG_INSTALL_DIR>/manager/config location.
If the Discover User Details from AD flag is set to Yes, then an additional Update User Details from AD option will appear in the What would you like to do? list in the right panel as shown in Figure 10. Clicking the Update button will immediately integrate the user information from the domain to the ADUserDetails.ini file available in the <EG_INSTALL_DIR>\manager\config directory.
Note:
By default, the user information available in the domain will be integrated with the ADUserDetails.ini file once in 7 days. If you wish to override this default, setting, then you can do the following:
The user specific information so updated can be viewed in the eG monitoring console in the following features offered by the eG Enterprise:
Once a sub-domain is manually added, a message to that effect will appear. The tree will also change to reflect the addition of the sub-domain.
Figure 6 : A message indicating that the sub-domain has been successfully created
Also, unlike an auto-discovered sub-domain where changes cannot be made to domain details, you can modify a manually-configured sub-domain. For this, select the node representing the sub-domain from the domain(s) tree, and choose the Modify domain details option from the What would you like to do? list in the right panel.
Note:
Whenever the configuration of a parent / child domain is modified or deleted, make sure that you restart the eG manager.
Also, you have the option of deleting a sub-domain. For this, select the sub-domain node from the domain(s) tree, and pick the Delete domain option from the What would you like to do? list (see Figure 7).
A message box depicted by Figure 8 will appear requesting your confirmation to delete the chosen sub-domain. Click the ok button to proceed with the deletion.
Figure 8 : Confirming the deletion of a manually created sub-domain
Note:
Ensure that the eG manager is restarted after deleting a parent/child domain.
To simply view the names and current configuration of the parent and child domains that have been created using the eG administrative interface, just click on the global Domain(s) node in the tree-structure. Figure 9 will appear.
Figure 9 : Viewing the names and current configuration of all domains
You can delete all displayed domains at one shot by simply clicking on the Delete all domains button in the right panel of Figure 9.
Note:
Discovery of AD and KDCs is an on-going process - a configurable time period is used to determine for how long discovered AD/KDC information is cached by the eG manager. The default period is 15 minutes. To override this default setting, do the following:
If the Discover User Details from AD flag is set to Yes, then an additional Update User Details from AD option will appear in the What would you like to do? list in the right panel as shown in Figure 10. Clicking the Update button will immediately integrate the user information from the domain to the ADUserDetails.ini file available in the <EG_INSTALL_DIR>\manager\config directory.
By default, the user information available in the domain will be integrated with the ADUserDetails.ini file once in 7 days. If you wish to override this default, setting, then you can do the following: