manual push install client by IP

I would like to see devices that are online, even if they don't have a client installed. IE, they are pingable.

Please add a feature to be able to auto install the agent by device type. ie, servers, workstations, thin clients. Currently this is an all or nothing type thing, it would be nice to make it more granular.

We often found that SCCM Client is not working because SCCM client was corrupt during client.msi installation was failed due to external OS shutdown. OS shutdown during upgrade may cause corrupt SCCM client but we cannot set "Maintenance Windows" for Client Auto Upgrade in current SCCM version and so it is difficult to avoid this situation. We want to add "Maintenance Windows" for Client Auto Upgrade.

Improve on the communication windows when deploying TS, Applications or Packages. Warning the users about what will occuring before a deadline is reached. With all this MS updates for Office and Windows we need a stronger communication method

It makes absolutely no sense whatsoever to wrap the Mac SCCM client in an MSI file. All the MSI file contains is a single DMG file which then has to be copied to the Mac.

Having to install the MSI file on a Windows machine to get a DMG which has to be copied to the Mac afterwards is annoying, please just make the DMG file available for direct download.

Thanks

Button that would backup the Deployment Tool kit data and also the task sequences.

Without using MDT integration enable a Summary Report to execute at the end of a OSD Deployment to inform the end user, engineer that the Deployment has been successful.

The idea is built on how MDT OSDResults works. Enabling Configuration Manager to report the Task Sequence had completed successfully, but keeping the summary screen active until closed by the user.

The deployment guide (very rough), script, and additional files can be found at

https://github.com/Drakey2000/PowershellScripts/tree/master/OSDReport

To have a task step that would enable you to dynamically select the drive to be used as the Operating System during deployment.

This would enable hardware with multiple hard drives to make a dynamic selection...such as selecting the fastest, smallest hard drive for the OS

Deployment guide and script can be found at https://github.com/Drakey2000/PowershellScripts/tree/master/OSDReport

Currently, a second shared folder has to be created and the client installer has to be copied to this folder. Everytime an update is performed to SCCM, the client has to be re-copied as well. Granting read and execute permissions are wiped out. Manual installation of the client is needed periodically for troubleshooting purposes and the extra steps to set it up are not helpful.

When you do an upgrade from CM12 SPx , prevent people to have programs/deployments from the build-in Configuration Manager Client (xxx00003) package . When you do not look / validate closely - your clients all get updated in no-time when your 1511 site servers go's online - even when you disable site-wide upgrade .

There are well documented issues with issues when using older versions of the Windows Update Agent. The configmgr client install still just checks for the base level of the Windows Update client. The client install should include the most up to date windows update agent so that customers will not be required to deploying the updated agent after client install to resolve known scan and related issues.

Why does the SCCM client still download the 7.6.7600.256 for Windows 7 when the latest version is 7.6.7601.23453?

Would be good when the sccm installs or upgrades that it attempts to install the latest version.

Run download computer policy automatically when a computer is added to a collection with a deployment.

to avoid issues with in place upgrades the task sequence should disable the client remediation automatically
https://colinfordblog.wordpress.com/2018/07/22/disable-sccm-automatic-client-remediation-during-windows-10-in-place-upgrades/