We have been using the modern driver a solution for some time now. I have recently started incorporating the info into my post-OSD reporting (emails, logs etc). I just started taking the DriverPackageId var and putting it in the email, so we can see what driver pacakge got used after the task sequence runs.
It would be nice to also get the name of the package instead of the Package ID. So if the fallback driver package got loaded instead of the one I made, then we would see that right away, and start troubleshooting from there. I imagine that the script could take the name from the object when it stamps DriverPackageId, and put it in a separate var that I can pick up.
We have been using the modern driver a solution for some time now. I have recently started incorporating the info into my post-OSD reporting (emails, logs etc). I just started taking the DriverPackageId var and putting it in the email, so we can see what driver pacakge got used after the task sequence runs.
It would be nice to also get the name of the package instead of the Package ID. So if the fallback driver package got loaded instead of the one I made, then we would see that right away, and start troubleshooting from there. I imagine that the script could take the name from the object when it stamps DriverPackageId, and put it in a separate var that I can pick up.