Actually, it is possible to create a collection with a cmdlet. But we cannot create it in a specific location. We need moving it after creating the collection. Why not just add a parameter to the New-CMDeviceCollection cmdlet?

Now that optimization of the WIM and removal of superseded updates is available as an option for offline servicing in the console, it would be great if this option could be added as a switch to the New-CMOperatingSystemImageUpdateSchedule cmdlet. I use this cmdlet to automate scheduling of updates in an ADG against all my WIMs so it would be great if I could shrink them down at the same time without needing to do this in the console.

With Bitlocker Network Unlock, a WDS server can automatically unlock your bitlockered device without requiring the user typing the PIN at boot. (https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock).
As we all go forward using the SCCM WDS-less PXE-provider instead of WDS, it would be a good idea, if it supported Bitlocker Network Unlock, too.

After uninstalling the client, anti-malware policy settings remain in the version information area of Windows security.
SCCM CB 1902
Windows 10 1903

Setting location:
1. Run ms-settings:windowsdefender
2. Clieck on [Windows Security]
3. Click the "gear mark" in the lower left
4. Click the "Version information"
5. anti-malware policy settings remain

It would be great if in the new Suppert Center Advanced Log File Viewer, there would be an option for Advanced Filters, when opening a log file, the filters load automatically and we dont need to load them manually everytime we open a log.
Same as with the other buttons, that can be activated and deactivated.

integrate sccm logs inside the console with nice view and charts

I check up on deployments every few hours, would love to be able to create a shortcut on my desktop to "Microsoft.ConfigurationManagement.exe \Monitoring\Searches\Search99"

The CMTrace tool is able to parse non-SCCM log files (e.g. 1E's Nomad logs) to properly pick up timestamps, process ID's etc. It would be very helpful if this could be added to the Support Center/Support Center Log File Viewer. It seems

The Support Center utility is a great addition but doesn't seem to support specifying a remote computer to connect to from the command line. This would allow it to be called automatically from scripts and other tools.

This is option is implemented for the remote control viewer by running: CmRcViewer.exe <remote-computer>

Likewise it would be great to be able to call the Support Center thus:
ConfigMgrSupportCenter.exe <remote-computer>

Add "Last Distribution Point" to the options for columns in the Assets list.

Phased Deployment Powershell Cmdlets

Please allow additional customization in the Task Sequence High Impact Dialog Box. Enable or Disable the Individual Comment Boxes completely, and allow Hyper Links to launch a web page with more information.

We have many task sequences, sorted into folders for multiple users, when it comes to archiving them, it's tedious, we'd like to archive multiple task sequences by user (or by folder), this would be great, right now you have to export one task sequence at a time which is tedious.

We use a multitenant SCCM environment with clients/customers in untrusted forests.
Because we target users, we also deployed the Management Point role in all untrusted forests.

At this moment Configmgr only supports up to 15 management points per primary site coming from 10 in the past.

We would like to see the maximum allowed management points per primary site bumped to a higher level.
This will give us the ability to stay with a single primary site setup and avoid CAS.

This Cmdlet does not support using a cloud distribution point as the distribution point source (and neither does the GUI).

This means that in order to use this feature we have to have an on-premise DP purely for this purpose.

Regards
Wayne

Although you can now add multiple deployments to a single Automatic Deployment Rule there a couple of options that can be read but not set. These are:

"If software updates are not available on the distribution point in current, neighbor or site boundary groups, download content from Microsoft Updates."
and
"All clients on a metered internet connection to download content after the installation deadline, which might incur additional costs"

I can successfully retrieve all Deployments associated with an Automatic Deployment Rule via the Get-CMAutoDeploymentRuleDeployment cmdlet and see the current settings for these properties by parsing the DeploymentTemplate XML.