Skip to content

agent-installation.md

Latest commit

 

History

History
77 lines (52 loc) · 2.49 KB

agent-installation.md

File metadata and controls

77 lines (52 loc) · 2.49 KB
Raw

Windows Agent Installation

The Agent is a single self-contained exe that installs itself as a Windows service - no separate MSI/setup tool, no .NET runtime required on the target PC. This has been built and verified end-to-end (install, service registration, live reporting, offline detection, uninstall) on a real Windows machine.

1. Build the installer

From C:\Projects\OpsCommandCenter on the Windows dev machine:

.\publish-agent.ps1

Produces publish\OpsCommandCenterAgent.exe (~34 MB, self-contained).

2. Silent install (per PC)

Must run elevated (Administrator). Point it at your deployed Server (see server-deployment-ubuntu.md):

OpsCommandCenterAgent.exe --install --server=http://<server-vm-ip>:5252 --interval=10

What this does:

  • Copies itself to %ProgramFiles%\OpsCommandCenter\Agent\OpsCommandCenterAgent.exe
  • Writes an appsettings.json next to it with the given server URL and report interval
  • Registers and starts a Windows service named OpsCommandCenterAgent (auto-start on boot, auto-restart on crash)

Re-running the same command (e.g. to point at a different server, or to change the interval) is safe - it stops and replaces the existing service rather than erroring.

3. Silent uninstall

OpsCommandCenterAgent.exe --uninstall

Stops and removes the service. Installed files are left in place (harmless; a re-install overwrites them).

Deploying to 200+ PCs via Action1

Since the fleet is already managed with Action1:

  1. Upload OpsCommandCenterAgent.exe as a file/package in Action1.

  2. Create a script/deployment step that runs (Action1 scripts execute as SYSTEM, so elevation is automatic - no UAC prompt to worry about):

    OpsCommandCenterAgent.exe --install --server=http://<server-vm-ip>:5252 --interval=10

  3. Target it at the endpoint group covering your managed PCs.

To push an update or repoint every Agent at a new server address later, just re-run the same script - the installer is idempotent.

Verifying an install

sc query OpsCommandCenterAgent

Should show RUNNING. Within a few report intervals the PC should appear as a card on the dashboard.

Known limitation

Disk health reporting relies on MSFT_StorageReliabilityCounter support in the storage driver. Some SATA SSDs don't expose it (confirmed during testing on a Kingston SA400) and will show "n/a" for disk health rather than a guessed number - this does not affect the computer's overall status color.