Configuring the eG VM Agent to Communicate with the eG Manager

The eG VM Agent, once installed and started, will begin collecting metrics on internal performance of the target Windows virtual desktop. However, the VM agent has no knowledge of the remote agent to which it needs to send the metrics; nor does it know to which Cloud Desktop component these metrics pertain. Without this knowledge, the eG VM Agent will not be able to transmit the right 'inside view' metrics to the right eG remote agent.

For this purpose, the eG VM agent has to be configured with the nick name of a Cloud Desktop component that has been managed in the eG manager. Also, to determine the remote agent that has been assigned to this Cloud Desktop component, the VM agent has to be configured to communicate with the eG manager and download the details of that Cloud Desktop component

To achieve this, follow the steps below:

  1. Login to the Windows virtual desktop hosting the eG VM agent.
  2. Go to the command prompt and switch to the <EGVMAGENT_INSTALL_DIR>\lib directory.
  3. Run the following command:

    SetManagerInfo.bat

  4. The script will first request you to enter the nick name of the Cloud Desktop component for which this VM agent collects metrics. Make sure that this name matches the nick name of the Cloud Desktop component that has been managed in the eG manager.

    This script will configure the eG Manager to which the VM agent will connect to.

    Please enter the Nickname of this VM Agent: eGDevCloudAcc

    This name should match the nickname of the Cloud Desktop component

  5. Next, specify the IP address and then the port number of the eG manager with which this VM agent should communicate.

    Please enter the eG Manager IP/Name to which the VM Agent should connect: 192.168.8.149

    Please enter the Port on which the VM Agent connects to the eG Manager: 7077

  6. Then, indicate whether/not the eG manager is SSL-enabled. If it is, then specify Yes at this prompt. If not, enter No.

    Is the eG Manager SSL enabled (Yes/No)? No

  7. If the VM agent should use a proxy server to communicate with the eG manager, then specify Yes at the next prompt. If not, then enter No.

    Should the VM Agent use a proxy server to connect to the eG Manager (Yes/No)?No

  8. If you entered Yes at step 7, then you will be required to provide the IP and port number of the proxy server via which the VM agent and manager should communicate.

    Please enter the proxy IP/Name: 10.10.1.13

    Please enter the proxy port: 6789

  1. Then, specify Yes at the next prompt if the proxy server to be used requires authentication. If the proxy server does not require authentication, enter No.

    Does the proxy require user authentication (Yes/No)? Yes

  2. If you had specified Yes at step 9, then you will be required to mention the proxy user name and password for authentication.

    Please enter the proxy username: egtest

    Please enter the proxy password: w3lc0m3

  3. Once the details are provided, the script will then try to connect to the eG manager specified at step 5, download the details of the managed Cloud Desktop component from the eG manager, and write it to a eg_managersetup.ini file on the VM agent host. Then, the script will restart the eG VM Agent service.

    Trying to connect to the eG Manager...

    Connected to http://192.168.8.149:7077

    Details of the eG Manager have been successfully configured in the file: C:\eGVmAgent/lib/eg_managersetup.ini

    The eGVmAgent service is stopping.

    The eGVmAgent service was stopped successfully.

    The eGVmAgent service is starting.

    The eGVmAgent service was started successfully.