Updating status to planned.
We shipped our 1905 Technical Preview today.
This preview contains the first release of the task sequence debugger. We’ll continue working on it to address more of the asks in this item.
Awesome. Reading that UserVoice entry shows other helpful ideas as well. Glad to see it's making traction.
Currently, a user can press F8 (if enabled) to bring up a Command Prompt during OSD for some debugging. It would be very helpful to take this a step further to also allow some option (maybe another F key) that would bring up a debug console that allows deeper investigation, such as viewing the current values of all TS variables, the current command line being run, status of packages, launch the log viewer, setting TS values manually for testing, disabling/skipping specific TS steps, verifying the state of the WinPE (ex: .NET/PS installed, drivers, other PE components), etc.
Right now, Compliance in SCCM has a big advantage over Group Policy: Reporting on results. Currently, and not in the foreseeable future, AFAIK, there are no plans to add such functionality to Group Policy.
Giving Compliance the ability to manage the same/more settings than GP would give admins much better insight into their environment by actually seeing the impact of changes that are deployed through reports and queries.
I think that would be an awesome addition.
Right now, the process to add registry keys or values that are not already part of WMI for inventory requires modifying MOF files, extending the hardware inventory, and enabling the new WMI classes for collection.
An interface that takes registry keys and values to automatically perform the steps necessary to import the classes, etc. would be a great help.
Expecting people to modify text files, etc for something that should be simple and is likely a pretty common need opens up the potential for errors, and requires more steps than should be necessary.