Test Your Network Connections

To deploy ControlUp, it is important that all of our networking requirements are in place. Our networking requirements are described in these articles:

• Communication Ports for VDI & DaaS (US Region)
• Communication Ports for VDI & DaaS (EU Region)
• Synthetic Monitoring (formerly Scoutbees)
• ControlUp for Desktops

To make sure these requirements are met you can use our network tester tool. If there is an issue, the tester lets you know whether the issue is related to:

• Network communication failure
• Proxy/network filtering
• TLS handshake failure

Download the tester

ControlUpTester.zip

Current version: 3.2

How to use the tester

1. After downloading the tester, extract the .zip folder and run ControlUpTester.exe:

   • To test ControlUp for VDI, run the tester from Monitor machines and machines that run the Real-Time Console desktop application. Optionally, if you are using Agent outbound communication, you'll also need to run the tester from a machine where the Agent will be installed.
   • To test ControlUp for Desktops or Compliance, run the tester from machines where the Agents will be installed.
   • To test ControlUp Synthetic Monitoring, run the tester from machines where Custom Hives will be installed.

2. Select the Region for your ControlUp organization.

3. In the Platform field, select which ControlUp product/feature you want to test, and then click Run Test.

   • ControlUp for VDI - Tests required URLs for ControlUp for VDI.
   • ControlUp for Desktops - Tests required URLs for ControlUp for Desktops. When you run this test, you must enter your ControlUp tenant name. To get your tenant name, open ControlUp and go to ControlUp for Desktops > Configuration > Downloads. For example, if your tenant URL is https://controluptechmarketing.sip.controlup.com, you should enter controluptechmarketing.
   • Agent Outbound - Tests required URLs for the Agent outbound communication feature for ControlUp for VDI. This test must be run from the Agent machine.
   • Websockets - Tests required websocket connections for both ControlUp for VDI and ControlUp Synthetic Monitoring.
   • ControlUp for Compliance - Tests required URLs for ControlUp for Compliance.
   • ControlUp for Synthetic Monitoring - Tests required URLs for ControlUp Synthetic Monitoring.
   • Generic API URL - Lets you test a custom API URL. For example, if you are using ControlUp for VDI & DaaS to connect to a Citrix delivery controller, you can test whether the Odata API can be reached from your machine.

Note that the App Launched under User: field at the top of the tester window displays the user running the app.

Export results

After running a test, you can click Export to save the results. If you ran the test under the Network Service account, make sure you save the file to a location that is accessible by other users.

Proxy server

You configure the tester to use a proxy. Currently, only HTTP proxy is supported.

1. Open ControlUpTester.exe.config

2. Add the proxyAddress and proxyPort values. Optionally, you can add a username and password if needed.
   

3. Save the config file and run the tester.

Run the tester under the Network Service account

The ControlUp Monitor runs under the Network Service account. If you are running the tester from a Monitor, you can run it as "Network Service" to exactly simulate Monitor communication.

To run the tester under the network service account:

1. Copy the tester into the Temp folder. Note that the Temp folder path will be added to PATH SYTEM environment variables.
2. Open PowerShell elevated with administrative privileges.
3. Run the script RunAsNetworkService.ps1 in the ControlUpTester file. To confirm that it is working correctly, the App Launched under User field in the tester should now display "NETWORK SERVICE".