SG SealGrid Athena Docs

Remote Windows Services Control

When a service on a remote machine hangs, stops, or needs its startup behaviour changed, you don't have to open a remote session or hand the job to a local admin. From an endpoint's Agent Details page, the Services section lets you list a Windows machine's services live and start, stop, restart, pause or resume any of them, change a service's startup type, and configure its recovery (failure) actions — all from the console over the agent's existing secure channel.

Live service control is a Windows feature. For a point-in-time inventory of services collected on a schedule (including offline machines), see Inventory. To run a one-off command or script against an endpoint instead of controlling a specific service, see Remote Command Execution.

Opening the Services section#

From Agents, click an endpoint to open its Agent Details page, then choose Services in the left-hand section list. The section opens on a searchable table of the machine's services. A search box above the table filters by service name or display name as you type, and the list is sorted by display name by default.

Each row shows four columns:

ColumnWhat it shows
Service nameThe internal (short) service name, e.g. wuauserv. This is the name Windows uses.
Display nameThe friendly name, e.g. Windows Update.
StatusThe current state — Running, Stopped, Paused, or a transitional StartPending / StopPending.
Startup typeHow the service starts — Automatic, Automatic (Delayed Start), Manual, or Disabled.

Live mode vs. cached mode#

A badge at the top of the section tells you which data you're looking at:

BadgeMeaning
LiveThe agent is Online. The list was fetched directly from the machine and the control actions are available. Use the refresh control to pull the latest state at any time.
CachedThe agent is offline. You're seeing the last services list captured by the endpoint's inventory. The action buttons are hidden and control operations are unavailable until the agent reconnects.

When the agent is offline the section shows the banner “Agent is offline. Live service operations are not available.” The cached list still lets you see what services exist and how they were last configured, which is useful when you're planning work on a machine that isn't currently connected.

Quick actions from the list#

While an agent is Live, each row carries an Actions column with inline buttons so you can act without opening the service first:

ButtonActionAvailable when
StartStarts the service.The service is Stopped.
StopStops the service.The service is Running or Paused.
RestartStops then starts the service.The service is Running or Paused.
PropertiesOpens the full service properties dialog (see below).Always.

The button for an action that doesn't apply to the current state is disabled, so you can't, for example, start a service that's already running. While an operation is in flight the affected row shows a spinner; when it completes you get a brief confirmation (Service started / stopped / restarted successfully) and the list refreshes to show the new status. If the operation fails, the reason reported by the endpoint is shown instead.

The service properties dialog#

Clicking a row — or its Properties button — opens a dialog with everything about that one service. It has a General tab and, on Windows, a Recovery tab.

General tab#

The General tab shows the service's full detail and gives you its controls in one place:

Running an action from this dialog reloads the service's detail in place, so the Status and Process ID update to reflect the result.

Changing the startup type#

Pick a new value in the Startup type dropdown and an Apply button appears; click it to push the change to the endpoint. The four choices are:

Startup typeBehaviour
AutomaticStarts with Windows at boot.
Automatic (Delayed Start)Starts shortly after boot, once higher-priority services are up.
ManualStarts only when something (or someone) requests it.
DisabledCannot be started until the startup type is changed back.

Changing the startup type does not start or stop the service by itself — it only decides how the service behaves at the next boot (or the next start request). Use the control buttons if you also need to change the running state now.

Recovery tab — failure actions#

The Recovery tab configures what Windows should do if the service fails — the same settings you'd find on a service's Recovery properties tab locally. You can set a separate action for the first failure, the second failure, and subsequent failures. Each can be one of:

ActionWhat Windows does on failure
Take No ActionNothing — the service simply stays down.
Restart the ServiceAttempts to start the service again after the configured delay.
Run a ProgramRuns a program or script you specify.
Restart the ComputerReboots the machine.

Two timing fields round out the policy:

When you choose Run a Program for any of the three failures, a Run program field appears for the program or script path. When you choose Restart the Computer, a Reboot message field appears for the warning shown before the reboot. Click Apply to save; the tab confirms “Recovery options saved successfully.”

Stopping or disabling a core service, or setting Restart the Computer as a recovery action, can take a machine offline or trigger an unexpected reboot. Check the Dependencies list first, and be deliberate about disabling anything the operating system relies on.

Who can use it, and when#

The Services section lives on the Agent Details page, which is available to signed-in operators and administrators. Control actions only appear while the agent is Live (online); when it's offline you get the read-only cached list described above.

Because the endpoint carries out the operation using Windows' own service control, the result — and any error — reflects exactly what Windows would report locally. If a service won't stop because another service depends on it, or a startup-type change is refused, the message you see is the one Windows returned.

Practical tips#