DeskGate Deployment Planning Guide

Start with the deployment you need to operate

A self-hosted rollout combines the management application, server services, database, endpoint software and an operational support plan. Before installation, define who owns each component and how devices will reach the services from the office, branches and approved remote locations.

The campaign illustration is conceptual. It does not specify firewall ports, routing, supported scale or a mandatory physical topology. Use the installation instructions for the exact package and version being deployed.

Build a version-specific requirements checklist

Requirements vary with the selected components, number of endpoints, reporting workload and recording policy. Obtain a current compatibility and sizing recommendation for your planned version instead of applying a historical minimum to every deployment.

Size storage around collection and retention

Screen recordings, detailed evidence and ordinary activity records can have very different storage requirements. Measure representative pilot data and separate live database, recording storage, exports and backup copies.

• Estimate daily measured growth for each enabled data category.
• Multiply the measured growth by the proposed retention period.
• Add capacity for indexes, working space, exports and backup copies as appropriate.
• Allow operational headroom and test report performance under the expected load.

This is a sizing method, not a product capacity guarantee. Avoid choosing a fixed disk size solely from the number of employees.

Pilot before a wider rollout

Choose a small representative group covering the devices, departments and network conditions you expect to support. Configure the approved collection policy and authorized reviewer accounts before expanding the rollout.

1. Prepare the licensed installation package and confirm the server/database prerequisites.
2. Configure the documented service endpoints and only the required network access.
3. Install the pilot endpoints and verify that devices appear in administration.
4. Check reporting timestamps, group membership, schedules and the intended data collection.
5. Test an authorized support workflow, reporting access and an example alert rule.
6. Document issues, support ownership and acceptance criteria before deployment to the next group.

Define acceptance checks that can be repeated

• Device registration and connection behaviour match the intended deployment.
• Report data appears for the selected users and periods without granting excessive access.
• Required categories and features match the purchased licenses.
• Connection and stored-data protections have been reviewed for the deployed version.
• Backup recovery is tested and operating responsibilities are assigned.
• The team has documented update, incident and offboarding procedures.

Remote command execution, scripts and software installation should be used within the approved administration scope. Test their behaviour on pilot devices before scheduling wider work.

Keep the rollout maintainable

Roll out in manageable groups, track failures and confirm device ownership as you proceed. Recheck report scope and permissions after changes in departments or administrators. Schedule recurring reviews of capacity, retention, backups and alert ownership.

Bring your endpoint count, deployment model, required report categories and retention plan to a DeskGate technical consultation. Those details are more useful for a sizing discussion than a request for a universal minimum specification.

Continue with the security and data protection guide and report walkthrough.