Managing Windows computers

Choose how to work with a Windows computer#

A question about a computer can mean several things: read its software inventory, run a diagnostic command or interact with a program on its desktop. These require different connections. Start by choosing the path that can actually perform your task, whether the computer is your own or part of an organization.

Choose the right path#

1. For an Action1-managed computer, use the configured Action1 module to inspect its actual record and supported operations.
2. For directory account information, use the AD module; an enabled directory account does not establish an online PC.
3. For Agent commands, sessions or graphical work, first review the Agent release and acceptance limits. Its inspected source includes PowerShell and CMD.
4. Establish the exact target and execution account before running a command. A service context and the signed-in user’s desktop are different.

Start with real endpoint inventory#

Resolve the organization and exact endpoints using Action1 tools. Inspect connectivity with endpoint status tools; directory account state does not establish whether a workstation is online.

Run diagnostics with the right context#

Search authorized library scripts first. When ad-hoc PowerShell is appropriate, use action1.run_powershell with exact resolved targets and required permission action1.powershell.run. Routine and critical impact affect approval policy; access checks still apply.

Understand Windows execution context#

Action1 scripts normally start as LocalSystem in Session 0. That is not the signed-in user's interactive desktop. User-specific paths and sessions must be resolved rather than guessed. Script execution does not prove full visual desktop control.

Action1 tools and configuration · Practical examples · Screen interaction

Endpoint inspection workflow#

1. List the relevant Action1 organizations and select the intended one.
2. Retrieve endpoints and identify the exact record, not only a similar hostname.
3. Inspect status and installed software with the appropriate read permissions.
4. If a diagnostic is needed, search/read a real library script before requesting execution.
5. Review the execution permission and actual approval policy, then inspect provider output and status.

A useful first request is “Show the current status and installed software of this endpoint.” Where data comes from cached provider inventory, the answer is not proof of a new live scan. A disconnected endpoint or rate limit can prevent a new operation.

Choose the right connection#

Action1 enrollment is maintained through Action1. Personalized YAADMIN Agent enrollment is a different workflow and remains subject to checkpoint acceptance limits. Neither AD computer records nor a matching display name establish a trusted Agent identity.

If an operation times out after submission, inspect the provider/job result before retrying. Cancellation in chat does not reverse a submitted action. See Troubleshooting for known failure distinctions.