If the guests belong to different domains - In this case, you might want to provide multiple domain names. If this is done, then, to access the guests in every configured domain, the test should be configured with the required user privileges; this implies that along with multiple DOMAIN names, multiple ADMIN USER names and ADMIN PASSWORDS would also have to be provided. To help administrators provide these user details quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the Click here hyperlink that appears just above the parameters of this test in the test configuration page.In the page that appears next, specify the following:

• First, provide the name of the Domain to which the VMs belong. If one/more VMs do not belong to any domain, then, specify ‘none’ here.
• The eG agent must be configured with user privileges that will allow the agent to communicate with the VMs in a particular domain and extract statistics. If ‘none’ is specified against Domain, then a local administrator account can be provided against Admin User. On the other hand, if a valid Domain name has been specified, then a domain administrator account can be provided in the Admin User text box.
• The password of the specified Admin User should be mentioned in the Admin Pwd text box.
• Confirm the password by retyping it in the Confirm Pwd text box.
• To add more users, click on the circled ‘+’ button in the page. This will allow you to add one more user specification.
• In some virtualized environments, the same Domain could be accessed using multiple Admin User names. For instance, to login to a Domain named ‘egitlab’, the eG agent can use the Admin User name labadmin or the Admin User name jadmn. You can configure the eG agent with the credentials of both these users by adding two separate specifications - one for the labadmin and another for jadmn in our example - for the same domain name using this page. When this is done, then, while attempting to connect to the domain, the eG agent will begin by using the first Admin User name of the specification. If, for some reason, the agent is unable to login using the first Admin User name, then it will try to login again, but this time using the second Admin User name of the specification - i.e., jadmn in our example. If the first login attempt itself is successful, then the agent will ignore the second Admin User name.
• To clear all the user specifications, simply click the Clear button.
• To remove the details of a particular user alone, just click the circled ‘-’ button corresponding to the user specification.
• To save the specification, just click on the Update button. This will lead you back to the test configuration page, where you will find the multiple domain names, user names, and passwords listed against the respective fields.

To add more URL, click on the Add More button in this page. To clear all the URL specifications, simply click the Clear button. To save the specification, just click on the Update button.