There seems no logical reason why it isn't possible to manually configure phases for application deployments the way they can be for updates - changing the way maintenance windows are handled for example, or setting phases to be manually moved on to.

Integrate ola hallengren sql maintenance into configmgr console as the de facto standard as a built in mecm maintenance task which seems to be the wildly preferred solution to the current built in re-indexing Maintenon task.

Add option for "Run Script" to be able to see the machine on which the script didn't run. Example I run a signed script on a collection, some of the machine do miss the sign-script certificate. To identify those machines, I need to create another collection with machines on which script did run and exclude from original one. Which is annoying and time consuming.

Hi,
we manage Servers with SCCM CB and it came to my Attention that i can filter on Currently Logged on User, which on a Client is definetly 1 User but on a Server could be more than 1 user.

So i did a few selects on the SCCM DB to see if there is a view that would help me

select Name,CurrentLogonUser,* from dbo.v_CombinedDeviceResources CDR
where CDR.Name = ‘HOSTNAME’

but there is only 1 ROW returned even if more users are logged on.

Maybe this view and the appropriate tables could be modified?

When the SCCM toast notification for a required deployment appears, the default option is "install now". If the user clicks the "X" to close the window without making any changes, the install will begin immediately. This behavior should be changed as it is not the intended action.

Sometimes all you have as an Application identifier in a log is the AppDT Id.

For example in the AppDiscovery.log in the form of "AppDT Id: ScopeIdxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx/DeploymentTypexxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx.
At the moment you need an SQL Query to find the Deployment Type and the Application (via modelname).

There is already a "Model name" column for the Deployment in the console. It would be nice to have "Model name" for the Deployment Type also, so we can identify it inside the console.

The Wake Up functionality MECM does not work if computer is in a "Deep Sleep". NIC is still active, as AMT/vPro still function, and other wake tools are able to wake pc.