The Jumpstart Deployment Web Service (JS DWS) is filled with so much more functionality that can be used to customize your task sequence in order to fit you needs. This blog post will explain how you can extend the existing task sequence that comes with Jumpstart 2012. The following example will execute a PowerShell script that is located at the server that hosts the JS DWS.

The figure below shows the logical flow of how a call is made.


Copy the PS script to the correct location

What you need before you start is the PowerShell script that you want to execute. In my case it is called “Write-JumpstartEventLog.ps1”. This script should be located in the script folder for JS DWS. This folder is a configuration setting in the web.config for the JS DWS. Open the web.config file and locate the add-element with the key-attribute PowerShellScriptFolder. It should look like this:

Here is your script folder path for JS DWS. In my case it is C:\Jumpstart\Scripts. Copy the PS script into that folder.

Add the Windows Script File

The script that makes the actual call from the task sequence to the JS DWS must be available. This script is called JumpstartExecutePS.wsf and can be copied in to the folder


Update the task sequence

Now it is time to add a Run Command Line action to the task sequence to execute the script that calls the JS DWS.

Edit your task sequence by right clicking and select “Edit”.


Add a “Run Command Line” action to the task sequence by clicking Add – General – Run Command Line.


Enter a name for the Run Command Line action and in the command line text box type the following:

cscript “%deployroot%\scripts\JumpstartExecutePS.wsf” /WebServicePrefix:”http://%_SMSTSMP%:54224″ /ScriptName:”Write-JumpstartEventLog.ps1″ /NamedArguments:”-Message:’Jumpstart Rocks'” /debug:true

Apply the settings and test your task sequence.


My PowerShell script writes to the eventlog and when I look at the eventlog on the server I see this. Great Success!


Contact us to get the files required.