Providing the 'MaxMessageRecievedSize' is fixed before this.. It would be grand!
+1 for this.
To come at this from a different angle / use case. The ability to define client settings as user policy would give us the ability to customise the Software Center itself per say department. Brand it so users can easily see this is a HR Department / Finance Department / Puppy Training Department etc.
Completely agree. We need the ability to drill into the pretty charts and view Device Names.
Just posted this on twitter, with any luck it will generate some support.
Whilst I've 0 voted left. I certainly support this.
All it needs to do is run exactly what the new Pre-Release Pre-Cache feature does, just in WinPE for new build machines, and in real time side-by-side the ongoing OSD.
Enabling the TS to look ahead whilst its doing other things, and download content ready for when it gets there.
Given this 3 votes as I came here to make the idea myself.
It's a feature that has been missing for some time now.
As Chris Cools has said, when I package Application A, I can then distribute it to multiple Distribution Points at once in a single Wizard. Then I go to deploy it to 3 buildings across site, each have their own Device Collection., but I can only select a single Device Collection in the wizard. Meaning, I have to right click, deploy, select device collection, next, confirm DP's, next, set required, next, set installation time, next, set notification level, next, set any alerts, next, finish the wizard... and then repeat the whole process 2 more times for the remaining Device Collections.
^I know that process like the back of my hand because of the hundreds of times I have to do it!
It's an easy enough feature.. lets make it happen.
Thanks for the feedback and suggestion. Updating status to Noted
Today we published a new article and related flowchart to provide some insight and guidance for using the Install Software Updates task sequence step.