DeskGate installation help
DeskGate Installation Prerequisites
Prepare the deployment model, Windows hosts, database, network and pilot acceptance checks.
Maintained by DeskGate · Updated October 6, 2026
Start with the deployment model
Use this checklist before a new DeskGate deployment. A Cloud Agent package and an On-Premise Agent package are different products of the setup process. Choose the deployment associated with your organization and license before downloading an installer.
For a self-hosted deployment, prepare the server and database before rolling out clients. Cloud endpoint installation does not require you to install your own DeskGate server or SQL database.
Record the installation decisions
| Item | What to confirm before setup |
|---|---|
| Package and license | The approved release, deployment model, organization and package profile: Agent, Admin or Portable. |
| Windows hosts | The supplied customer server setup requires 64-bit Windows and administrator access. Confirm release support for the chosen Windows version; endpoint Agent requirements are separate. |
| Server capacity | Size for endpoint count, enabled collection features, retention and concurrent reporting. Validate the estimate in a pilot instead of treating a generic RAM or disk figure as a guarantee. |
| SQL Server | The customer Release installer uses the local GOMYID instance. If absent, supply SQLEXPR_x64_ENU-2022.exe beside GoMyidSetup.exe. Have the required sa password ready. |
| Network | Prepare a static IPv4 address, actual listener ports and paths from intended networks or VPNs. Have the assigned license GUID available. |
| Web console | The customer server setup configures GateCore. Prepare an available web port (default 5000), choose local or network access and keep it separate from GateServer ports. |
| Access and recovery | Assign setup, runtime, database and reporting roles. Decide backup ownership, retention and a restore test. |
Prepare the first endpoint
- Choose one representative Windows device with an authorized administrator available for installation.
- Confirm that its network can reach the selected server endpoint.
- Download the organization-specific Agent package from the authenticated setup page.
- Record the package version, deployment type and installation time.
- Agree which collection and remote-support functions will be enabled, and who can review the resulting data.
Use a small pilot before mass deployment. Include a representative VPN or branch device when those networks are in scope.
Define a successful pilot
- The matching Agent service is present and running.
- The expected device appears under the correct organization.
- An authorized reviewer can find a recent record after the configured collection interval.
- A permitted support task works with the intended access controls.
- The database and server remain healthy during the test workload.
- Recovery and package removal procedures have an assigned owner.
Continue in order
SQL Server Setup for DeskGate → DeskGate Server Installation → DeskGate Client Installation and Connection. Review Required Permissions and Firewall Configuration before opening network access.