Collect diagnostics

One command gathers everything needed to find out why a probe is not reporting, into one file.

Run it

On the machine, open PowerShell as an administrator and run:

powershell -ExecutionPolicy Bypass -File "C:\Program Files\BOBcloud\Monitor\Send-MonitorPost.ps1" -Diagnostics

It prints where it saved the file - in C:\ProgramData\BOBcloud\Monitor, named after the machine and the time. Send that file.

Our scripts are not yet Authenticode-signed: the code-signing certificate is in validation. Until then Windows needs -ExecutionPolicy Bypass for this command, and an estate that enforces AllSigned by Group Policy will refuse it. Automatic updates are not affected: every update is signature-checked on the machine before it installs.

Run it as an administrator: without that, it cannot read the probe's settings or see its scheduled task, and says so in the file.

What is in the file

• Versions - the probe, and the installer that put it there.
• Configuration - the machine's device id, which collector it talks to and where that setting came from, whether it runs as SYSTEM, and whether it can write its own folder.
• Connectivity, step by step - whether the collector's name resolves, whether port 443 connects, the TLS handshake and whose certificate came back, and whether an HTTPS request gets an answer. This is what tells a firewall from a proxy from a problem at our end.
• The last check-in - when it last tried, what came back, and when it last got through.
• The scheduled task - its state, its last run and result, and its next run.
• The queue - reports waiting to be sent after a network failure.
• The log - the probe's recent log lines.

What is not in it

Before the file is written, the probe takes out the device secret, any enrolment code, Windows SIDs and user names, including user names inside folder paths. The device id stays, so whoever supports the machine can find it in the portal; on its own it cannot be used to post as the machine.

If the probe is too old for this command

If PowerShell answers A parameter cannot be found that matches parameter name 'Diagnostics', the probe installed on this machine is older than the command - machines keep the probe they were installed with until someone installs it again. The machine's page in the portal says so too. Send its log instead: C:\ProgramData\BOBcloud\Monitor\agent.log, and agent.log.1 if there is one. The Updates page shows which machines are on an older probe.

Next: Closing an account