Skip to main content
DSE Support Center
DSE Customer Helpdesk

Understand Endpoint Status and Background Monitoring

Understand the five exact Machine Status states, the status-card fields, what continues in the background, and the safe checks to complete before reporting a device condition.

Device status

Understand Endpoint Status and Background Monitoring

Understand the five exact Machine Status states, the status-card fields, what continues in the background, and the safe checks to complete before reporting a device condition.

Production address https://helpdesk.dsesecurity.com/

Confirm HTTPS and the exact domain before entering account or ticket information.

Visual walkthrough

Open any visual for a full-size reference

The annotated screenshot uses numbered red boxes and arrows. Read callouts 1, 2, and 3 in order, then return to the written steps below for the complete procedure.

Customer-safe endpoint and network status intake workflow. Open full size
Visual 1 Use this visual to gather endpoint, user, site, timing, and network context before opening a ticket. All records are fictional.
Customer-safe illustration of reaching DSE support from a computer or mobile device. Open full size
Visual 2 Related workflow: Customer-safe support shortcut reference. The image contains fictional records and no endpoint identifiers.
Annotated DSE walkthrough for Understand Endpoint Status and Background Monitoring with three numbered red callouts, boxes, and arrows. Open full size
Visual 3 Annotated walkthrough: follow red callouts 1 through 3 to confirm context, complete the action, and verify the result. The screenshot is a sanitized training view with fictional records.
1
Workflow section 1 of 6

Identify the exact Machine Status state

  1. Protected indicates that Machine Status is not currently presenting a condition that requires customer action.
  2. Attention recommended indicates that one or more conditions should be reviewed; the expanded Machine Status card shows the corresponding banner CHECK RECOMMENDED. Use the risk score and open alerts as context.
  3. Action required indicates that Machine Status is presenting a condition that needs prompt review; open or update a DSE ticket with the displayed details.
  4. Offline indicates that the endpoint is not currently reporting an active agent connection; the expanded card shows AGENT OFFLINE. Compare the last check-in with the current local time and timezone.
  5. Status pending indicates that current status has not finished loading or refreshing; wait briefly, choose Refresh status, and check again before reporting the result.
Back to top
2
Workflow section 2 of 6

Read and verify the status card

  1. Review the risk score and open alerts to understand the amount of currently displayed attention.
  2. Review last check-in and compare it with the current local time and timezone.
  3. Confirm the hostname and device ID match the computer you intend to report.
  4. Confirm the organization and assignment match the expected customer and responsible assignment.
  5. Use Refresh status when the card appears old or shows Status pending, then allow time for the new result.
  6. Use Copy device info only for an authorized DSE ticket or support conversation and verify the destination before pasting.
Back to top
3
Workflow section 3 of 6

Complete safe local checks

  1. Confirm the computer is powered on and Windows is responsive.
  2. Confirm the device has normal approved network access without changing managed firewall, VPN, or security settings.
  3. Check whether the condition affects one device, several devices at one site, or all devices you can observe.
  4. Do not stop services, delete files, remove the agent, or install another remote tool unless DSE directs the step.
Back to top
4
Workflow section 4 of 6

Know what continues in the background

  1. The endpoint service can continue approved health and connection work when no customer is actively using the desktop.
  2. A signed-out Windows user does not by itself mean the endpoint is Agent offline.
  3. Selecting Exit DSE tray closes the tray application only; it does not stop the background endpoint service or background monitoring.
  4. A tray state is not a substitute for a ticket when a person, device, or business service is currently affected.
  5. DSE uses the ticket to confirm scope, authorization, communication, and the next action.
Back to top
6
Workflow section 6 of 6

Finish and verify endpoint support

  1. Confirm the endpoint status, remote-session state, and original symptom after the approved action.
  2. Save customer work, have the technician select Clear secure relay after clipboard transfer, and lock Windows when stepping away.
  3. Keep all follow-up on the same DSE-###### ticket for the same issue.
  4. Report unexpected remote activity, missing tray status, or a failed validation immediately.
Back to top
Final verification

Before you leave this guide

  1. Confirm context. Recheck the DSE domain, signed-in account, company or site, ticket number, device, and request type shown on screen.
  2. Confirm the result. Perform one harmless verification and make sure the visible status matches what you expected.
  3. Keep the reference. Save the DSE-###### ticket number, confirmation, or other safe reference needed to continue the same conversation.
  4. Stop on a mismatch. Do not repeat a high-impact action. Preserve a safe screenshot, note the time and exact error, refresh once, and update or open the correct DSE ticket.

Content owner: DSE Service Operations. Production reviewed July 16, 2026. Examples and visuals are customer-safe and use fictional data.

Please Wait!

Please wait... it will take a second!