How Does eG Enterprise Monitor the Citrix Cloud Connector?

eG Enterprise monitors the Citrix Cloud Connector in an agent-based manner. The Cloud Connector is typically installed on a machine running Windows Server 2012 R2 or Windows Server 2016. The eG agent should be installed on this box for monitoring the Cloud Connector.

The eG agent makes Cloud API calls to connect to the Citrix Cloud and pull metrics related to the availability and responsiveness of the cloud. For this purpose, you need to configure the eG agent with the following details:

  • A valid customer ID: When configuring the Citrix Cloud service, you should have created an API client on the cloud, so that any external program can communicate with the cloud. This API client is tied to a customer ID. The Citrix Cloud API requires this customer ID, when calling REST APIs. To get the customer ID for the API client that you have created in your environment, do the following:

    • Sign in to the Citrix Cloud administrator console.
    • Click the “hamburger menu” in the upper left corner of the console.
    • Select “Identity and Access Management” from the drop-down menu. An API Access page (see Figure 1 ) will open in the right panel. Look for the phrase , "use <customerID> as the customer parameter" in the right panel. The <customerID> displayed within that phrase (as highlighted in Figure 1) is the customer ID you need to configure the eG tests with.

      Figure 1 : Customer ID mapped to the API client

  • The path to the secure client file: When creating the API client on the cloud, you will be provided with an ID and a Secret for your client. Downloading this information saves a file named secureclient.csv. The eG agent uses the ID and Secret stored in this file to connect to the Citrix Cloud API. This is why, you will have to configure the Citrix Cloud Connectivity test with the full path to the secureclient.csv.
  • If a user who is currently logged on uses proxy for communicating with the Citrix Cloud Connector, then eG agent requires to be configured with proxy settings assigned for that user in Internet Explorer settings to report metrics related to user logon performance. To configure the proxy settings to the eG agent, do the following:

    • First, specify the proxy details that the user uses in the Internet Explorer settings. To achieve this, click on the icon provided at the right corner of the Internet Explorer window.

    • Clicking the icon will invoke a menu in which choose Internet Options. Then, select the Connections tab in the Internet Options window that appears (see Figure 2).

      Figure 2 : The Connections tab in the Internet Options window

    • Now, click the LAN Settings button in Figure 2. This will open the Local Area Network (LAN) Settings window (see Figure 3). In the Proxy Server section of this window, enable the Use a proxy server for your LAN check box and specify the IP address and port of the proxy server that the current user uses to communicate with the cloud connector in the Address and Port text boxes. Finally, click the OK button to register the changes.

      Figure 3 : Specifying proxy server details

    • Next, run the following command from the command prompt to import the assigned settings to the eG agent.

      C:\Windows\System32\bitsadmin.exe /util /setieproxy LOCALSYSTEM MANUAL_PROXY <PROXY_IPADDRESS/PROXY_HOSTNAME:PROXY_PORT> "<local>"

      For instance:

      C:\Windows\System32\bitsadmin.exe /util /setieproxy LOCALSYSTEM MANUAL_PROXY " <local>"

      C:\Windows\System32\bitsadmin.exe /util /setieproxy LOCALSYSTEM MANUAL_PROXY " <local>"


    You can remove the proxy settings that you provided in the Internet Explorer settings after the proxy settings are imported to the eG agent.