Clients

The Clients page displays all PowerShell Orchestrator Agent instances that have registered with the server. It is the primary place to confirm that agents are online and available to receive jobs, review agent details, and manage registered agent records.

Accessing the Clients page:

1. Log in to the PowerShell Orchestrator Server web interface at https://<server-name>:52866
2. Navigate to Clients in the main navigation

Client list overview:

The Clients page displays the following information for each registered agent:

Client status indicators:

Agent status is determined by heartbeat activity:

The agent sends a heartbeat to the server on a configurable interval (default: every 60 seconds). If no heartbeat is received for 5 minutes the agent is marked Offline.

If a client shows as Offline:

• Confirm the agent service is running on that machine:

Get-Service PowerShellOrchestrator.Agent

• Verify the ServerUrl in the agent appsettings.json is correct
• Test network connectivity from the agent to the server:

Test-NetConnection -ComputerName <server-ip> -Port 52866

• Review the agent logs for connectivity or certificate errors:

C:ProgramDataPSOrchestratorAgentlogs

Viewing client job history:

To review the job execution history for a specific agent:

1. Navigate to Clients
2. Click on the client name or Agent ID
3. Review the job execution history for that agent including job names, scripts executed, statuses, and timestamps

This is useful for confirming that a specific agent has been executing jobs correctly and for investigating execution issues on a particular machine.

Agent registration behavior:

Agents register automatically with the PowerShell Orchestrator Server on their first connection — no manual registration step is required. The agent’s hostname, IP address, and version are recorded at registration and updated on each subsequent heartbeat.

If an agent is reinstalled or its AgentId is reset to AUTO, it will register as a new client entry on next connection. The previous client record will remain in the Clients page until manually deleted.

Managing clients:

Deleting a client:

To remove a disconnected or decommissioned agent from the Clients page:

1. Locate the client in the list
2. Click Delete
3. Confirm the deletion

If the deleted agent’s service is still running on the target machine it will automatically re-register with the server on its next connection and appear as a new client entry.

Confirming agent availability before creating jobs:

Before creating a job confirm the intended agent is showing as Online in the Clients page. A job assigned to an Offline agent will remain in Pending status until the agent comes back online and polls for work (default poll interval: 20 seconds).

Best practices:

• Check the Clients page before creating jobs to confirm the intended agent is Online
• Use the Last Seen timestamp alongside the Online/Offline status for a more complete picture of agent health — an agent that has not been seen for an extended period requires investigation even if it briefly shows as Online
• Investigate any agent showing as Offline promptly — an offline agent cannot execute jobs
• Remove stale client records for decommissioned machines to keep the client list accurate
• Confirm all expected agents are represented in the client list after deploying new agent installations

[Your administrator should maintain a reference list of all machines with the PowerShell Orchestrator Agent installed and cross-reference it against the Clients page regularly to confirm all expected agents are registered and reporting.]