The Clients page displays all PII Scanner Agent instances that have registered with the PII Scanner Server. It is the primary place to confirm that agents are online and available to receive scan jobs, and to manage registered agent records.
Accessing the Clients page:
- Log in to the PII Scanner Server web interface at https://<server-name>:52766
- Navigate to Clients in the main navigation
Client list overview:
The Clients page displays the following information for each registered agent:
| Column | Description |
| Status | Online or Offline indicator |
| Name | The hostname of the machine running the PII Scanner Agent |
| IP Address | The last known network address of the agent |
| Last Seen (UTC) | The timestamp of the agent’s last check-in with the server |
| Actions | Available management actions for the client |
Client status indicators:
A client’s status is determined by how recently it has checked in with the PII Scanner Server:
| Status | Description |
| Online (green) | The agent has checked in within the last 5 minutes |
| Offline (red) | The agent has not checked in within the last 5 minutes |
If a client shows as Offline:
Confirm the agent service is running on that machine:
Linux:
sudo systemctl status LTA-Scanner
Windows:
sc query LTA_PII_Scanner_Agent
- Confirm network connectivity between the agent machine and the PII Scanner Server on port 52766
- Confirm the API_URL in the agent config.json points to the correct PII Scanner Server address
Review the agent logs for connectivity or certificate errors:
Linux:
cat /opt/bluelance/scanner/scanner.log
Windows:
C:\Program Files\Blue Lance 2-0\LTA_PII_Scanner_Agent\logs\
Client actions:
The following action is available from the Clients page:
Delete client: Removes the client record from the PII Scanner Server.
A client cannot be deleted if it has jobs in Queued or Running status. Resolve or wait for active jobs to complete before attempting to delete the client.
A deleted agent will automatically re-register with the PII Scanner Server on its next poll cycle if the agent service is still running on that machine.
Confirming agent availability before creating jobs:
Before creating a scan job, confirm the intended agent is showing as Online in the Clients page. A job assigned to an Offline agent will remain in Queued status indefinitely until the agent comes back online and polls for work.
Monitoring agent health:
Use the Last Seen (UTC) timestamp to monitor agent health beyond the simple Online/Offline indicator:
- An agent showing as Online but with a Last Seen timestamp significantly behind the current time may indicate an intermittent connectivity issue
- An agent showing as Offline with a recent Last Seen timestamp has only recently gone offline and may recover quickly
- An agent showing as Offline with an old Last Seen timestamp has been unreachable for an extended period and requires investigation
Best practices:
- Check the Clients page before creating scan jobs to confirm the intended agent is Online
- Investigate any agent showing as Offline promptly โ an offline agent cannot execute scan jobs and represents a gap in your scanning coverage
- Use the Last Seen timestamp alongside the Online/Offline status for a more complete picture of agent health
- Remove stale client records for decommissioned machines using the Delete action 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 PII Scanner Agent installed and cross-reference it against the Clients page regularly to confirm all expected agents are registered and reporting.]