DeskGate Client Installation and Connection

Choose the correct package

Use the authenticated DeskGate setup page for your organization. Select Cloud or On-Premise according to the license, then select the intended profile. Agent installs the endpoint service; Admin provides the administrator application; Portable is a separate package and is not a substitute for a managed Agent installation.

The current Agent installers select the payload matching the Windows architecture. Confirm operating-system support for your release before deployment.

Recognize the installed Agent

1. Set the On-Premise address

The On-Premise package requires a server IP address or DNS hostname. Enter the host only, without https://, a URL path or an appended port. The setup page accepts one endpoint, or two different endpoints separated by a semicolon when your deployment uses that arrangement.

For example, desk-server.example.com illustrates a hostname format; it is not a working server address. Use only the endpoints assigned by your administrator. Configure the server’s actual ports through the supported deployment configuration, not by appending them to this field.

2. Download and install on a pilot device

1. Confirm the organization, license and deployment shown on the setup page.
2. Generate the Agent EXE or Agent MSI appropriate to your rollout method.
3. Verify the downloaded file’s source and publisher before execution.
4. Run the approved installer with authorized administrative elevation.
5. Allow setup to complete and record any error message before retrying.
6. Check the matching Agent service and verify the expected files.

Admin installation uses a separate profile and does not create the Agent service. If you installed Admin by mistake, obtain the Agent package for endpoint enrollment.

3. Verify connection and reporting

Check the matching service in Windows Services. Confirm that the endpoint can reach its configured server, then locate the device under the expected organization in the management interface. Review a recent record after the configured collection interval and confirm the relevant collection settings.

With current Agent MSI packages, an Installed Apps entry is not a reliable installation check on its own. Verify the service, installed files and console connection together. Use the package’s supported uninstall procedure when removal is required.

Before a wider rollout

Repeat the pilot on the network and Windows configurations in scope. Record package version, successful installation, service state and device visibility. See Required Permissions and Firewall Configuration for firewall and antivirus checks, or Troubleshooting Client Connection Problems if the device is missing or offline.

Verify the device in the management interface

After installing the Agent, open Station and search for the expected computer or Windows user. Confirm its organization and group. This is a post-installation verification screen, not an Agent installer wizard. Continue with From Your First Device to Your First Report.