When you need to troubleshoot desktop analytics you can use DesktopAnalyticsLogsCollector.ps1 but then you have collect the log files or have remote access to the clients.

Can you integrate the Desktop Analytics Logs Collector into the Client Diagnostics work being taken as part of TP 1912).

Add a vendor parameter to Get-CMSoftwareUpdate

This will help identify updates from specific vendors that have been provided through Third-party Software Update Catalogues.

In our environment SCCM Server installs client on discovered resource but they failed to install due to machine specific issue, could you prepare a tool which we can give it to floor support technician to run on machine which have SCCM Client issue or Installation failure, the tool should check for all prerequisites for client install also firewall issues like (WMI and File and Print sharing not allowed ) it should the issue with which it becomes easy to fix the underlying problem and get the sccm client successfully deployed

The new Model field on drivers is useful, but needs to be extended to other content types, like Packages & Applications, where Model specific items need to be installed (e.g. specific HP SoftPaqs, or video drivers that need to run from .EXE etc).

Currently, Get-CMPackage only returns “ordinary packages”, not software update packages or task sequence packages or other types. If you run the command in verbose mode, you can see the WQL query filters PackageType=0 and activity <>3.

Documentation for this cmdlet states “Get-CMPackage returns all packages” and this is wrong. It returns all packages where type = 0. Can we please create PackageType as a parameter so all packages can be managed with one cmdlet?

Take the OU path from 'Network Settings" and turn it into a variable e.g. _SMSMachineOUpath
I use dynamic variables to determine the OU based on location and device so my Domain OU path has OU=%devicetype%,OU=Location,OU=workstations,DC=Contoso,DC.com
so it would be nice to have the actual value in a variable that I can reference later say in a script to move existing object to the above created OU. I can see the full path in the SMSTS.log, but not in a variable. Also removing the LDAP:\ from the start could be handy in some situations I guess.

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.

The task sequence has a 32MB size limit for all policy. But for some reason they are actually limited to 16MB. But the Product Group is aware of the problem. I know they are working on fixing the 16MB limit.

This will help us troubleshoot and determine when the task sequence has reached this size.

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.

The 'Pre-provision BitLocker' step has an option to skip the step when the devices does not have a TPM or when the TPM is not enabled.

I'd like to see that option added to the 'Enable Bitlocker' step. Whether it's enabled by default is another question I guess. However, this is one of the many things that hang up new admins trying to get their first Task Sequence off the ground. Just spent an hour or so trying to get past this step.

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>