This might not be a very common scenario, but let’s say you don’t / can’t use Client Push or GPO Deployment. Here is an Orchestrator runbook that automates the “Manual install” option of the SCCM Agent.

Let’s break it down and see how to build it.

First we’re going to use “Get Computer” activity to verify that the “Computer Name” provided in “Initialize Data” is a member of our domain. I renamed the “Get Computer” activity to “Check Computer in AD”

Next, let’s create a folder on our computer.  We should have something like this:

\\{Common Name from "Check Computer in AD"}.lab.local\C$\CMClinetSource2

Then, we are going to use the “Copy File” activity to copy all the necessary source files from the SCCM Server to the folder we created above.

I’m placing a Junction here just so my next activity won’t be executed *number of files copied* times

Next, we will use the “Run Program Activity” to start the agent deployment. I renamed this activity to “Install SCCM Agent”. For the command line you can use only “ccmsetup.exe” if you have SCCM and AD configured correctly. Otherwise, you can just specify the parameter manually like bellow:

c:\CMClinetSource2\CCMSetup.exe /mp:SRVSCCM.LAB.LOCAL SMSSITECODE=LAB MP=SRVSCCM.LAB.LOCAL FSP=SRVSCCM.LAB.LOCAL

Also, we are making sure that the “Wait for the completion of the program” option is selected.

Next, we are using a “Return Activity”, to return the computer name.

Hope this helps.

> V.