Skip to content

Find and manage connected Windows devices

The Devices grid is the operational inventory for Windows endpoints connected to MSPControl through the Autopilot agent. It combines identity and assignment information with current or last-reported health data and the management actions available to your role.

Use this page to:

  • find an endpoint by customer, device name, friendly name, user, operating system, agent version, template, or location;
  • review connection, antivirus, disk-space, firewall, update, and device-experience status;
  • open a device’s detailed hardware, software, network, user, security, and update information;
  • download device reports;
  • run approved actions on one or more selected endpoints;
  • create or link an asset record from a connected device.

You need permission to view Devices. Each action is independently permission-gated, so two technicians can see different options for the same device.

A newly installed agent must register and report data before the endpoint appears with complete status information. An offline endpoint can still appear with its last reported values.

  1. Open the customer organization.
  2. Go to Devices > Devices.
  3. Use search, Online Only, status, health-band, property, location, or organization filters to narrow the grid.
  4. Select the device name to open its details.
  5. Review the connection status and the status indicators before running an action.

The current grid includes the device name and friendly name, current or loaded user, operating system, assigned template, update mode, agent version, security and health indicators, and a remote-connect control when that integration is available.

Filters in the MSPControl Devices grid
Use status and property filters to narrow connected endpoint inventory.
Additional device inventory filters
Filter by the properties available in the current Devices grid.
  1. Select one or more device rows.
  2. Open Actions.
  3. Choose an action available to your role.
  4. Review any confirmation dialog or required input.
  5. Start the action and wait for the product response.
  6. Refresh the grid or open device details to verify the expected result.

Depending on permissions, organization context, device state, and configured integrations, the current implementation can expose actions for:

  • repairing agent settings;
  • rebooting or deleting a device through the agent command workflow;
  • installing Windows updates or remediating update state;
  • updating the MSPControl agent;
  • remapping or unmapping configured cloud folders;
  • reinstalling the ScreenConnect client;
  • sending agent logs to an email address;
  • assigning a template or organization location;
  • adding or removing remote-access users;
  • running Windows Disk Cleanup or WinGet updates;
  • creating or linking an MSPControl asset;
  • enabling or disabling supported Microsoft Entra ID migration workflows.
Device actions menu
Only actions permitted for the current technician and context are shown.

The customer-scoped report menu can provide these report types when permitted:

  • device report;
  • missing updates;
  • unknown locations;
  • local users;
  • hardware hash export.

The main device report dialog can exclude storage details, group results by location, and restrict the report to one location.

Download Report menu in the Devices area
Choose a device report supported by the current organization context.
Device report options
Configure storage and location options before downloading the device report.

At the cross-customer administration level, report delivery can use an email-address dialog instead of a direct customer-scoped download.

Select the edit control beside Friendly Name to assign an operational label without changing the Windows computer name. Use Set Template and Set Location to keep policy and location reporting aligned with the endpoint’s intended role.

When the Documentation & Assets module and permissions are available, the actions menu can create an asset from a selected device or link it to an existing asset record. This connects automatically reported device inventory with the organization’s maintained asset lifecycle record.

Creating or linking an asset does not replace the device record. The two records serve different purposes and remain separately managed.

After an action or inventory change:

  1. Reload the grid.
  2. Confirm the device is still in the intended organization, template, and location.
  3. Open device details and verify the relevant status or data tab.
  4. For an asynchronous agent command, allow the endpoint to check in before treating an unchanged value as a failure.
  5. Review agent logs or scheduled-task history when the action does not complete as expected.
  • Use Device details for one endpoint’s full record.
  • Use Device Apps for organization-level application inventory.
  • Use Agentless Devices for synchronized Microsoft cloud device records.
  • Use Assets for maintained asset records, relationships, documents, photos, and lifecycle history.