In Configuration Manager 1910 a user can uninstall an "app group" in Software Center if it is deployed as available. This is great! However the uninstall order is the same as the install order. we need the following in the uninstall space:
-Reverse order of uninstall
-Control if a application should be left instead of removed, could be needed in other app group.
-Control the order if necessary

We have had situations where the PXE Reponder service errors and stops listening to PXE requests WITHOUT the service stopping.
For example, if the service starts and the machine doesnt yet have an ip address.

Errors reported:
PXE: No valid IP addresses.
PXE::StartPXEServer failed; 0x80070490

BUT the service keeps running!

Suggest that the service should stop in this case so that other monitoring tools can detect and remediate the service failing.

When using the Run PowerShell Script task sequence, it would be beneficial to be able to pass task sequence variables in the parameters field, especially when using different credentials where PowerShell no longer has access to Microsoft.SMS.TSEnvironment.

Cluster patching feature was added in #SCCM CB 1602, but has been in prelease for a long time. It needs to:
1) Have improved/revamped UI
2) Remove dependency on collections
3) Orchestrate patching for any machines, not just servers/clusters
4) Remove the feature from prerelease

Preview SCCM versions have a basic WSUS cleanup and maintenance task. It should be evolved and expanded to include SQL index optimization, IIS configuration optimization, and deletes of declined updates.

Currently, when servicing stack updates and regular updates are deployed in the same software update group, the patches do not apply in a determinant order. This leads to cases where a cumulative update that requires a new servicing stack is installed before the servicing stack itself.

While this can be worked around by separately deploying the servicing stack update before updates that require said servicing stack, it would be much more convenient if the update installation process checked if there are any servicing stack updates to be deployed and automatically installed them first

Split this item from a bigger umbrella item.
This is to specify an icon per App Task Sequence in the Software Center.

It would be beneficial if you could set breakpoints at any line item in the task sequence, just like when coding, to stop the task sequence progress. Have a dialog pop up with which you can continue to the next break point.

Currently the folder redirection feature in SCCM doesn't take an environmental variable as a good path; it requires \SERVER\SHARE.

With OneDrive being common place in Office 365, please allow us to enter a command such as:

%userprofile%<SyncFolder>

where Sync folder is the name of your organization's onedrive folder.

as documented by the Office team.

https://support.office.com/en-us/article/redirect-known-folders-to-onedrive-for-business-e1b3963c-7c6c-4694-9f2f-fb8005d9ef12

So that we can use SCCM to manage this.

Thanks! :)

Add the complete progression status in the progress bar in order to see the current step and remaining steps.

Like in this post http://www.systanddeploy.com/2018/02/add-complete-progression-sta

I'd like primary site sizing recommendations for small to medium size environments. We have <500 client devices, your recommended specs are way too high.

At the moment there is no quick way to see which particular machines require an update. You can run a report from Monitoring, but that means identifying the update then going back to reports and running the appropriate report.

You can however see the the number of devices that require an update when looking at that particular update. A simple "More Details" button here would be useful which would show the machines that require the update or are compliant etc, without needing to run a report.

This applies to both Software Updates and Windows 10 Updates for feature updates.

Create cmdlets for the new in console Powershell scripts. Some good ones would be new Script Deployment and get script results.

EX:
New-CMPSScriptDeployment -Name "Script Name" -CollectionName "Collection Name"

Create an OSD variable for Secure Boot called _SMSTSSecureBootState. It should have three values depending on the state and the currently running OS: Enabled, Disabled, NA. This can be used during a TS to determine if Secure Boot should be enabled. Currently, a TS variable has to be defined and set based on if the registry key exists or not.

I would be great to have a between Filter for Datetime in the Support Center Logfile Viewer.
Like this:
Include: 2017-03-08 11:00:12.323 <->2017-03-09 09:00:12.323