Is it possible to provide another option to back up SCCM database during SMSBackup so that the database size can be reduced?

With 1702 was a 1gb download, secondary sites over a sat link were congested beyond their transfer windows. It would great if the next distribution used both binary differencing as well as honoring the replication schedule

Migration not happening below objects, so any possibility for upcoming new releases ?
> Custom Client Settings
> IBCM MP/DP
> Site Settings
> Maintenance Tasks

After applying an SCCM update via in-console servicing, permissions on the cd.latest folder are not retained. This requires any process/account backing up the cd.latest folder to have read access re-granted after every SCCM update.

Maintenance Mode feature is cool, but it would be nice when i upgrade or recovery secondary site, that contains DP, he had been on maintenance mode automatically.

When adding an MP, the box "Generate alert when MP is not health" is never checked by default. Should be checked by default, and why is this even an option? I don't see a scenario where an Admin wouldn't want to know the MP isn't health.

It will be a nice thing if the WOL can be done from the CAS based on the site assignment of the client.

If prerequisite checker fails with a warning there should be an option to continue with the upgrade anyway.

There seems to be a bug with the pre-req check for the MP upgrade. MSXML6 check fails then the MP fails to install. I had to run ccmclean /client then restart server. Then the MP installed and the 1702 upgrade completed.

Currently the restore process can be done only if the machine has the same name. It would be nice to have an option to restore the Primary site on a machine with a different name and higher operating system. Also provide some added intelligence for the restore process with a check list interface enabling administrators to check if the pre-requisites are met. This would also help in a DR scanario with standby servers.

Would like to ability to monitor Secondary Site upgrade in the Monitoring workspace

When installing site systems like SUP I want to have specified an template for how Windows Server should be configured like IIS, WSUS Application Pool etc. in addition to installing the WinSrv Roles. This can bed slightly different from customer to customer and would make it easier for them to deploy new Site Systems with a consistency. Stability would go up and troubleshooting would be easier. Thinking about all Site System roles, not only SUP.

Ran into an issue when upgrading from v1606 to v1610 that the SQL failed to run due to high CPU usage (SQL was being ran on a separate box). Was not noticed until after the upgrade had already started. Maybe one of the pre-req checks for upgrading to SCCM is to look at the average CPU usage by SQL to see if that host will complete the upgrade in a timely manner and reduce the risk of failing.

I’ve updates to 1706 in my lab. There are a few things that they don’t work appropriate way.
1) Log compmon.log said that “Can not get the current execution state for component CONFIGURATIONMANAGERUPDATE since it is not installed or completed installing.”. That is not true.The update process is finished. The console said all tasks were completed.
2) Configuration Manager Service Manager does not communicate with most of components. I have no idea why because they work

Please fix the text for Status Filter Rules on Write audit messsages to the site database AND AND specify...

CM Upgrade date is very large file. So, I want to resume download on Service Connection Point.

Do you think that you can bring it back to the way it was so I don't have to sign in multiple times a day and I keep getting an era I never had to do this before and it's driving me crazy you have my email address you have my phone number and my password I should not have to be signing in every day multiple times