It would've been nice to have the ability to resize the new "Enter a PowerShell script" window to chech that everything looks good. The default windows is quite narrow. Maybe add som nice colour formatting to get a better overview.

Get-CMScript does not provide on option to get scripts by scriptGUID. CMScripts are allowed to have the same name so we need a variable that is unique, ScriptGUID will do that. Currently I am not able to pass that value through Get-CMScript.

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.

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

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! :)

Introduce ConfigMgr Web Console and remove the need to update the console on every device with each SCCM CB Upgrade as local admin rights are needed to update the console.

The ConfigMgr Web Console might be similar to Azure Portal with Microsoft Intune.

With SCCM CB updates getting released more frequently than before, this will provide benefits and ease of management. The Admins can connect to the ConfigMgr console from any computer in the organisation without the need to install it.

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"

Please give us task sequence variables for the following because WMI can be unreliable or sometimes can't be used. These would be nice to have in order to create conditions for performing actions such as enabling/disabling TPM and SecureBoot.

TPM enabled/disabled
TPM activated/deactivated
TPM owned/not owned
SecureBoot enabled/disabled

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

New-CMDuplicateHardwareIdentifier
Set-CMDuplicateHardwareIdentifier
Remove-CMDuplicateHardwareIdentifier

Please create cmdlets to add/edit/remove duplicate hardware identifiers. We have a large organization and those pesky Lenovo Yoga's get a USB to Ethernet dongle with each one. We have over 500 dongles currently, and I don't see a way to automate importing those MAC addresses. Thanks!

I would like more space in the OSD Task Sequence description field (and possibly even include a link) so that we can adequately tell people what's required before and after running the Task Sequence and to tell them where to find help.

At the moment, we only have 2-3 lines of text available.

Perhaps replicate what's currently available in the application model with the Localised description on the Application catalog tab.

Have the ability to include/exclude certain OU's from both Active Directory User and System Discovery.

E.G. I might have an "All Users and Groups" OU at the root domain level, which may contain sub OU's containing service accounts or mailbox accounts etc. that I don't want being picked up by discovery. The ability to pick which sub OU's to discover/not discover would be really handy in this scenario. The same applies for system/computer discovery also.

Add info of the "Location" if you search for collection.
e.g. we use Folders and subfolder for companies. and each time we search for collections we dont know the Location.
we got more than 5000 collections.. where this is tricky to find out via
Eyes .

Many organizations create their own front-ends for ConfigMgr Task Sequences (or leverage popular third-party ones like OSD++, Pretty Good Front End, etc.). However, these only are able to be used when the task sequence is in WinPE.

Please add the serviceui.exe functionality into the default task sequence environment so it is possible to display Light Touch prompts when starting the task sequence from an existing operating system. Including serviceui.exe would be enough, or the functionality to launch interactive UI could be added to the environment natively.