From my field experience I have seen many times OS Deployments which did not really succeed, because of Continue on error conditions. In most cases the reason was to not end up with systems staying in Provisioning Mode. I know some guys just "re-deploy" the TS with checks if everything was done properly. This brought up the idea - why not using Compliance Settings for this purpose? At least to check if the system meets the Desired Baseline. Everything needed should be stored in the Task Sequence anyway and it would allow a "Report" summary client side after Deployment.

Include canned scripts for creating collections applications and deployments with the ability to create a template from selections.

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.

when creating a new collection from a search result (ie. user/device). once the collection is created, the search should not be refreshed. as today, the search is cleared. if you have a custom search, you need to apply all filters or load the search again, and it can take time on large environments

Currently deployed task sequences create a lot of policy download and slow down the initialisation of a workstation. If they worked like in bootable media, or another way - I don't know if say downloading the TS policies as a zip would help?

Microsoft reports that have other reports linked, don’t work anymore with our modified folder structure. So we applied changes to those MS reports. In this case we didn’t create our own report but modified the MS reports. -> links should be added like this: ..\subfolder\reportname, not using the complete hardcoded folder structure. That way – since the linked reports are always in the same folder or in the subfolder like in the default structure – all links will work no matter in which folder the report actually sits.

When using the German version of the SCCM Console, Reports, Software Center or Control Panel Applet the word ‘compliance’ is translated with ‘Kompatibel’ which is the German word for ‘compatible’

This doesn´t really make sense and should be translated with a better German Word like ‘Konformität’

In sections like Detection rule when using different operators like between, one of, none of. Provide formatting examples on hover for single and multiple entries.

Would be good to have a PowerShell CmdLet to get information on all collections and deployment for a computer is listed for.

You should be able to create a conditional access rule that only the computers with the latest Windows 10 build can access corporate resources.

The latest version is required because it might introduce new security features or some other functionality.

When updating a package over "Update distribution point" we always have to click outside of the section/folder in order to get an updated status of the package we are updating. It would be nice to have it automatically refreshed only for that particular software.

It should be possible that extensions for Windows Intune can be installed without adminrights while opening the Admin Console after the Extension is activated.