When parameters are provided on a 'Run Powershell Script' in a task sequence, the SMSTS.log only logs the name of the script. It does not log the full command (including parameters) that are invoked.

For example: if I call Java.ps1 with parameters -level 1 -language eng the SMSTS.log only shows...

Running powershell script: 'Java.ps1'(PkgID: SCM00000) with execution policy 'Bypass'

This would be helpful in troubleshooting what parameters were actually passed to the script that is executing. Otherwise you have to track down the task sequence and assume everything entered is passed and run. Or you have to build your PS1 to output(Write-host) those parameter inputs to force them into the SMSTS.log

The docs that exist for the CM Messaging (note, the messaging SDK is not a part of the larger CM SDK docs here https://msdn.microsoft.com/en-us/library/hh442686(v=cmsdk.16).aspx) is currently a .chm Help file, which is lovably nostalgic.

However it doesn't do justice to the power of the SDK. For instance, Discovery and hardware inventory are barely covered in the SDK docs. I'm troubleshooting an issue now with the Messaging SDK in which a fake CM Client appears with Windows 6.2 NT Workstation, even though it is a fully patched Win10 machine. Weird stuff.

Anyway, it would be great if the docs were not a .chm file, but redone in the lovely style we have here: https://msdn.microsoft.com/en-us/library/hh442686(v=cmsdk.16).aspx

It would be helpful to have the ability to select OR as a Connector Value (which only has 2 states AND, OR) for the AddDetectionClause of Add-CMScriptDeploymentType
The best example of this is when trying to create a ConfigMgr Client Update application. The client has a different GUID depending on whether it is x86 or x64.

Why am I making a separate application deployment for the client upgrade as opposed to the built in one? The built in one will not use the files local to itself and pull the entire content accross the WAN again. So building an application that uses "ccmsetup /source:%~dp0" to use local source is a better solution.

#Deployment *******NEED ABILITY TO SET OPERATOR FOR -ADDDETECTIONCLAUSE TO "OR" DEFAULT IS "AND"
$Detect1 = New-CMDetectionClauseWindowsInstaller -ProductCode $APPGUIDx64 -Existence
$Detect2 = New-CMDetectionClauseWindowsInstaller -ProductCode $APPGUIDx86 -Existence
$DeployedApp = Add-CMScriptDeploymentType -ApplicationName $APPName -DeploymentTypeName $DepTypeName `
-Comment $DepTypeComment -ContentLocation $DepContLoc -EnableBranchCache -CacheContent `
-InstallCommand $DepInstProg -UninstallCommand $DepUninstProg -UninstallWorkingDirectory $DepUninstLoc `
-AddDetectionClause($Detect1,$Detect2) -InstallationBehaviorType InstallForSystem `
-UserInteractionMode Normal -LogonRequirementType WhetherOrNotUserLoggedOn `
-ScriptLanguage PowerShell -ScriptText "#" -SlowNetworkDeploymentMode Download

Creating SCCM Collection Queries is an art, and like most art, some of us are more suited to stick-figures while others produce beautiful creations worthy of a place in the Louvre, featuring graceful sub-queries, artful tabbing and good code practices.

When creating a collection, it would be helpful to have an optional 'Community Collection Catalogue' to choose from, which could have a user-voice style 'Most useful' collections list.

Users could create collections here, possibly even having a community 'wish-list' area for those without skills to request from those who would like to share.

Contributions in the community catalog could be counted for MVP or other recognition, possibly displaying badges. Gamification elements could be added, including Facebook or Twitter links to individual contributions.

Here is the User experience for the update process as I understand it:

1. System tray balloon appears saying 'software changes are required'

2. System tray balloon appears saying 'downloading and installing software'

3. System tray balloon appears saying 'Restart required: Recently installed updates require your machine to be restarted'

4. *It is here I would like the larger temporary notification reboot window to appear but it doesn't.

5. Permanent notification reboot window appears and stays on the screen

I would like option 4 to be possible. Without this it seems quite easy for users to miss seeing the balloon notification and therefore not know that a restart is coming.

It would be good if there was an option in Client Settings > Computer Restart to automatically show the temporary restart notification window. It would also be good if there was an option here to permanently set the 'SCNotification.exe' in Notification Area Icons to 'show icon and notification' to further improve the visibility to users of pending restarts so they know to save their work before they leave their computer for lunch or when they go home.

I've attached an image of the temporary notification window I am talking about

Thanks,

Andrew

Exposing Configuration Manager functionality through RESTful web API's would open up a whole new world for interacting with ConfigMgr.
E.g. a web Admin console and easier integration with Service Management Automation (SMA).
It should also be easier for 3rd party vendors to create new web based solutions for say an self-service portal or a Windows App for tracking an OS or application deployment on a mobile device or phone.
Personally I would really like any easier way to interact with ConfigMgr. when running in Windows PE (OS Deployment) or a web portal for non-admins to provision new or existing machine for OS deployment.