Monitoring task sequences in the dashboard

Monitoring a TS has a couple of requirements and implications that need to be considered when setting up. This will cover what needs to take place for the monitoring in the dasboard to be enabled.

Requirements

DeployR relies on the 2Pint StifleR Server & Client to provide the task sequence monitoring function, similar to how it monitors a ConfigMgr task sequence. The StifleR server will already be setup with enough basic settings configured for monitoring, but additional setup is required in DeployR to add the StifleR Client. Required 2Pint Software for DeployR Monitoring & Remote Tools:

• DeployR Server

• StifleR Server

• Stifler Action Hub integrated into StifleR Server

• StifleR Client configured for StifleR Server

Application Content Item

The StifleR Client needs to be added to DeployR as an Application Content Item, sample command line:

msiexec /i StifleR-ClientApp-x64.msi AUTOSTART=1 OPTIONS="%WorkingDir%\settings.2psImport" /quiet /l*v "C:\Windows\Temp\StifleRClientInstall.log"

The content in the Content Item will be the MSI installer and the 2psimport file. For more details, see the StifleR Client Installation docs

WinPE Stage Monitoring

To enable monitoring of the task sequence from start to end, including the WinPE stage, the StifleR client is required to be integrated into DeployR. This process is done for you automatically when you create a content item for the StifleR agent and add it into the Boot Media page. For additional details, see the Generate Windows PE Boot Images page.

Full OS Stage Monitoring

Non-Persistent Monitoring (StifleR Client removed after OSD)

If the StifleR Client has been integrated into the WinPE boot image, DeployR will automatically migrate the client from WinPE into the Full OS to continue the ability of monitoring the task sequence. The DeployR process will also automatically cleanup the StifleR Client at the end of the task sequence.

Persistent Monitoring (StifleR Client Persists after OSD)

In many cases, your organization will also be levarging StifleR for all of this benefits and will want the StifleR Agent to continue on after OSD is completed. To ensure this happens, use the Application Content Item and install it during the Task Sequence once in the Full OS using an "Install Application" step.

Dashboard Monitoring of the task squence

Now that the StifleR client is integrated into your process, the client will relay data to the StifleR server and data will start to populate into the dashboard. Deployments -> Running -> OSD sequences

The first screen is an overview of all the different OSD Task Sequences running currently, here is a task sequence "Windows bare metal from cloud" currently running on 9 machines accross 3 different networks.

Once you click on that little blue arrow next to the Name | GUID of the task sequence, you'll get details about each device

Each device will dispaly tha name of the computer. When it's in WinPE, it name will be OSD, then the first 12 characters of the UUID of the device. There will be different icons in the title bar

Hovering over the icons will tell you their meaning. The status bars will provide information about the current download and the overall process of OSD. By clicking on the name of a device, it will drill into specific details about that device.

This page and tab of Client details will cover information about the device's network and hardware information. To the left of the device, it will disable remote tools (if configured in the environment) that can be leveraged while in WinPE or the full OS. This device is currently in WinPE, so only a few tools are available including, Folder Explorer, Registry Explorer, WMI Explorer. Example of browing the file system, and logs can be opened directly from the endpoint remotely

There are more things that can be done, so poke around, and happy monitoring.