Daily Archives: December 11, 2013

Force SCCM 2012 Deployment

Sometimes you want to immediately deploy (install) a package and you don’t want to wait for the SCCM agent to start the task.

They are multiple ways to do this, one of them is to use the tools described in my previous posts.

The other way is to go the configuration menu of the client, configuration manager and go to “evaluatiecycles voor installatie van toepassingen” (dutch) and click Nu Uitvoeren (also dutch)

In English it’s called Machine Policy Retrieval & Evaluation Cycle.


Manually install SCCM client

Yesterday a customer asked me how to manually install the SCCM 2012 client. This is how you do that. Create a network connection to your SCMM Management Point server.

For example net use q: \\SCCMSERVER\SMS_SITEIDNR.

Go to the client directory and execute the following command :



Replace sccm-mp with the name of your SCCM management server and ofcourse make sure you use the correct sitecode.

After executing you instantly see ccmsetyp.exe in your running processes :


Great SCCM 2012 tool : PoshCAT

In the past I used the SCCM Client Actions Tools (link) but there is now a new successor called PoshCAT by Kaido Jarvemets. I found this tool so useful I decided to write a blogpost about it.

First : you can download the tool here.

After starting the Powershell script you notice the following screen :


In the upper right corner you can enter your credentials :


It’s easy to force client actions, like for example a hardware/software inventory :


Or restart the service or install the ConfigMgr Client manually :


Check for WMI problems :


WSUS and Endpoint options :


APP-V configurations :


Deployment actions :


And other options like ping, reboot etc.


I found this tool easy to use and very stable. The SCMM Client Actions tool (older, see start of the post) has some options PoshCat doesn’t have. I made some screenshots of this also :

Client schedule actions :


Client health actions :

I found a minor issue with the Check client version, I was running SCCM 2012 R2 and it reported that the client agent was outdated. I didn’t look into that, but the other options are working fine.


Client agent actions :


Advertisement actions :


Other actions :SCCM005

For the SCCM administrators, consultants, troubleshooters etc. it’s easy to have hold onto these tools. You are up and running in notime 🙂