ProblemWe have had this problem statement at hand which requires the field engineer to validate that any engineered solution, when deployed at a customer site, is running the supported versions of the firmware and driver.
BackgroundWell, we already have Pester tests written and placed inside a validation kit which tests whether a deployment is as per the practices outlined in our deployment guide.
So this was only natural to add the driver version validation under this kit (firmware validation in the future release).
We use Pester (PowerShell unit testing framework) for the Infrastructure/Ops validation and PSRemotely to target all the nodes in our solution for these tests. So the code samples in the post correspond to that.