Open source / public preview 0.1.0
Is FSLogix actually set up right on this host?
A single PowerShell script audits an FSLogix installation against Microsoft’s documented best practice. It runs 47 checks, scores the host from 0 to 100, and explains each finding in plain English with a link to the Microsoft page it came from.
It is strictly read-only. It never writes to the host.
Read-only
PowerShell 5.1
No modules
MIT licence
How the score works
0 to 100, per host
Critical counts 10, High 6, Medium 3, Low 1. A pass earns the full weight, a warning half, a fail nothing.
95-100
Healthy
85-94
Good
70-84
Needs attention
50-69
At risk
below 50
Critical
A host can score 85 and still have a critical failure, so critical fails are reported on their own. Use the score to trend a host pool over time, not as an absolute.
What it checks
Eight areas, 47 checks
Install
FSLogix is present, and its version against a baseline you can set.
Configuration
The registry settings, including the traps Microsoft warns about and per-user overrides.
Cloud Cache
Only checked when Cloud Cache is in use: cache paths, free space and provider counts.
Antivirus
Microsoft’s documented exclusion list compared with the live Defender setup.
Storage
Reachable on TCP 445, writable, free space, Kerberos settings and stale lock files.
Services
The FSLogix services and the minifilter drivers.
Groups
Include and exclude group membership. An empty include group means nobody is processed.
Runtime
Session status, temporary-profile evidence and FSLogix errors from the last 7 days.
How to run it
One command, then read the report
Windows PowerShell 5.1 is enough, with no modules to install. Run it elevated on the session host, because the checks read HKLM, services, Defender settings and event logs.
.\FSLogix-HealthCheck.ps1To collect a whole host pool in one place, write the HTML report and the JSON to a share:
.\FSLogix-HealthCheck.ps1 -ReportPath \\fileserver\fslogix-health -QuietWhy it never fixes anything
Changing registry settings across a fleet of session hosts needs change control, batching, a rollback path and an audit trail. A community script has none of those. A half-safe fix engine is worse than an honest report, so this one reports and leaves the decision to you.
Where it is today
This is a public preview, version 0.1.0. It has been tested on a real AVD session host across several configurations, but not yet across a range of customer environments. Treat the findings as advice to verify, not instructions to apply. The JSON format may change before 1.0.
Try it, break it, tell me what it missed
It is MIT licensed and built in the open. Issues and pull requests are welcome, especially from environments I have not seen.
