When the Job Title Isn’t Suitable

Issues can arise where, for instance, some jobs are created using only a GUID ID as the name, making it hard for an administrator to classify the job. StifleR solves this by looking at the URL of the files within the job.

URLContains

This checks if the URL of the active file being downloaded contains the Value contained within the > < . Use this to track hostnames or even ConfigMgr package ID’s etc.

<Type TypeID="204" Match="URLContains">sms_pol</Type>

The above rule is used to match all ConfigMgr Policy Traffic as the URL always contains “sms_pol”

Internet="1"/”0”

This can be used to match a download whose source is a public IP address. StifleR Classes 192/172 and 10 subnets as internal and anything else as external.

“0” equates to a non-internet download.

<Type TypeID="303" Match="URLContains" Internet="1">adobe.com</Type>

This line will match any download with a URL containing “adobe.com” that originates from an external address.

BranchCache="1"/”0”

Used to distinguish BranchCache Enabled downloads from non-BranchCache jobs.

<Type TypeID="904" BranchCache="1" Internet="1" />

This would match a job that was BranchCache aware, AND came from an external URL. You might use this type of rule as a ‘Catch-All’ rule further down the TypeID section to match any other job types.

SmallerThan/LargerThan

Catch-all values that simply compare the size of the download file with the value between the > < and match accordingly.

Identifying Microsoft Configuration Manager Job Types

Because ConfigMgr assigns the same name to ALL content downloads, i.e. “CCMDTS Job”, this can make it impossible to identify the job any further. To provide more granularity with these ConfigMgr jobs, the StifleR Client can identify a certain type of download, and this is expressed within the rules. You can also identify and differentiate a job that is a ‘Required’ installation from an ‘Available’ installation performed by the user within ConfigMgr Software Center or Company Portal, along with Jobs that are running within WinPE. This can be extremely useful in allocating priority and/or bandwidth to differing types of ConfigMgr download.