UPDATE 06/13/14 – Added Enable/Disable-CMClientDebugLogging functions.

I’m pleased to share my most recent module; CMClient! This module contains a lot of the common actions I tend to do on ConfigMgr clients all grouped into a module. At this point, it only has functions to kick off common client triggers. These triggers are Machine Policy Download, Discovery Data Cycle, Compliance Evaluation, Application Deployment Evaluation, Hardware Inventory, Software Inventory, Update Deployment Evaluation and Update Scan.

Each of these functions is simply an easy way to trigger client schedule IDs. Each function feeds back to the the function that’s doing the work; Invoke-CMClientAction. If you specify -AsJob on any function, that gets passed to the Initialize-CMClientJob. I’ve tested these functions on nearly all of my 5,000 clients so far so I believe it’s fairly bug-free. If you notice any problems, please let me know.

I intend to be adding a lot more functions to this at a later point in time. Functions like Set-CMClientBusinessHours, Get-CMClientBusinessHours, Disable-CMClientBusinessHours, Get-CMClientApplicationDeploymentState and Get-CMClientUpdateDeploymentState are coming soon! I’ve got those functions done but they haven’t been prettified yet. 🙂

For now, I’m just releasing the PSM1 file. When I get the manifest done and all of the pretty stuff available, I’ll be sure to update this post.


Download this script on the Technet Script Repository