Status messages are amazingly helpful in the SCCM console, but difficult to get to. For instance, whoever wrote the status messages for Task Sequence deployments did an amazing job, yet I cannot access these without making a custom query! This is an amazing troubleshooting tool that is hidden from the average user.

I'd like to get access to status messages from the object that makes the status message. For instance, if I right click on a task sequence deployment, I want to be able to view all status messages associated with that object. If I right click on a distribution point, I want to see all messages associated with that DP. The same with content, devices, users, etc.

I've written console extensions that pass data from the console to statview.exe to add these features in myself, but really it should be something that's included by default. It'd be amazing if it just opened statview.exe and didn't redirect to another screen in the console also.

Once I wrote the extension, I couldn't live without it at any client I went to. Being able to view all the OSD status messages for a specific deployment by simply right clicking on that deployment is an amazing help!

It would be great if you could specify a Git Repository and Branch as the source of the contents of the Scripts Folder. This would allow the approvals to be managed in GitHub with all the abilities around code review and testing.
It could still require an admin approval in the console which Version of the script should be used. It would also make rollbacks to an earlier version very easy.
If you allow having "folders" in the Script folder, each of them could be a repository. You still should need to approve which version to run, but MVPs could create these repo's that others could include into their environment.

When creating stand-alone media you have the option to select which Applications,Packages and driver packages it should include onto the media or not. After clicking next on the summary page the process of starting the media launches. in the createTSMedia.log you can see that at some point the process starts to compute volume layout. It seems that the compute of the volume layout does take into account the software you selected to not be on the media. Therefore you might get the message that you do not have enough space on the USBFD media altough this is not trough. At this point the only solution is to create a copy of your task sequence and remove all tasks with content that you do not need for this specific offline deployment. IT would be nice if the compute volume layout step respects the packages/applications you selected to not be on the media.