IT Console Purchase GoMyid Remote Desktop

DeskGate practical help

From Your First Device to Your First Report

Verify an Agent, find its station, choose the right group and export your first activity report.

Maintained by DeskGate · Updated October 6, 2026

What you will verify

This guide connects endpoint enrollment to a useful report. You need a working server or Cloud workspace, an organization-specific Agent and a reviewer with access to the relevant devices and reports. A successful installation alone does not prove that the selected report contains data.

Post-installation verification checklist

Work through these checks with one pilot device before a wider rollout. For a Cloud workspace, mark the SQL and server-service checks as not applicable; do not install SQL on an endpoint for this checklist.

Record each check as Passed, Needs attention or Not applicable in your rollout notes, together with the test time and outcome. These cards describe expected results; they do not run tests or read your server status.

  1. Self-hosted only

    1. SQL database connection

    Expected result: The setup database test completes successfully. A login page opening by itself does not verify database access.

    Check a failed database test

  2. Self-hosted only

    2. Server services

    Expected result: GoMyidServer and GoMyidCore show Running in Windows Services after setup. If either is stopped, record its state and any error before changing the installation.

    Prepare service error details

  3. All deployments

    3. Management console access

    Expected result: The authorized reviewer can sign in to the correct workspace and open the permitted management pages. For self-hosted network access, verify the configured address from an authorized computer.

    Troubleshoot access and connection

  4. All deployments

    4. First device and group

    Expected result: Station shows the intended pilot device in the correct group. The reviewer has access to that group and the assigned collection rule has been checked.

    Find a missing device

  5. All deployments

    5. First activity record

    Expected result: An agreed test activity appears for the pilot device in the selected report period after the configured collection interval. Match the identity, group and time range.

    Investigate an empty report

  6. All deployments

    6. First report export

    Expected result: The downloaded PDF opens and its device, date range and report scope match the on-screen review. Record the result before expanding the rollout.

    Review the activity report workflow

When is the pilot ready?

Every applicable check has an observed successful result, and the reviewer can explain which device and period the report covers. If a check fails, keep its exact error and time, follow the linked guide, then repeat that check after resolving the cause. A successful installer screen alone is not enough.

1. Install and identify one pilot device

  1. Follow the client installation guide using the correct Agent package.
  2. Confirm the Cloud GoMyid or On-Premise GoMyit service is running.
  3. Sign in to the assigned management workspace; complete two-step verification when enabled.
  4. Open Station and search for the expected computer, Windows user, username or remote ID. Match the device identity before changing its group.
Actual Station search and group filters. The device table is intentionally excluded.
Actual Station search and group filters. The device table is intentionally excluded. Open for original size. Example records are demonstration data.

2. Confirm group and collection settings

Check the station’s group and the associated rule. Have an authorized administrator confirm the activity collection settings and applicable working schedule. Select only the intended station before a bulk group change. Keep report access restricted to the approved reviewer.

The Default group does not automatically include devices assigned to another group. Use the group that actually contains your pilot device.

3. Produce a recent, known test record

On the pilot device, perform a short, agreed activity during the configured collection period, such as using an approved application. Record the time and allow the configured collection interval. This is a functional check, not a productivity assessment.

4. Open and filter the activity report

Actual DeskGate activity report interface.
Actual DeskGate activity report interface. Open for original size. Example records are demonstration data.
  1. Open Activities under Activities Report.
  2. Choose the pilot device’s group and relevant user.
  3. Set From and To to cover the test period, then select Apply.
  4. Inspect the user summary and daily records. Confirm the selected period and identity before interpreting a total.
  5. Use Download PDF and verify that its filters and scope match the on-screen review.

If the first report is empty

Check group membership, date range, Active users, reviewer permissions, collection settings and endpoint connectivity. For application and website records, use Work Analysis rather than assuming every dataset appears in Activities. See connection troubleshooting before reinstalling.

Record the package version, endpoint, test period, filters and outcome for your rollout checklist. The screenshots illustrate the interface; their demonstration dates are not dates to reuse in your deployment.