StifleR
2.6
2.6
  • Start Here - StifleR 2.6
  • StifleR 2.6.x.x
    • StifleR - Release Notes
    • What's New
    • QuickStart Guide
      • Installation
        • Manual Server Installation
        • StifleR Client Installation
        • StifleR Network Locations
        • Example StifleR Rules Definition
    • Planning & Deployment Guide
      • TL;DR version
      • StifleR Overview
        • The StifleR Solution
      • Features Overview
        • Other Features
      • Technical Overview
        • StifleR Standard Features
        • StifleR Enterprise Features
      • Planning Your StifleR Implementation
        • Firewall Ports
        • Supported Clients
        • Networks in StifleR
        • Permissions
      • Installation
        • StifleR Server Installation
        • Dashboards, Client and Beacon Server Installation
        • Post Installation Checks
        • Testing Quick Start Guide
      • Troubleshooting
        • BranchCache across Subnets
      • StifleR Generic Concepts
        • Red Leader
        • Enterprise Environment - Blue Leader
      • Bandwidth Management
        • Bandwidth Tuning Monitoring and Control
      • StifleR WMI Provider
      • StifleR Feature Details
        • StifleR Enterprise Edition Features
      • Further Reading
    • StifleR Operations
      • Maintenance tasks
      • Backup and Recovery
        • Moving the StifleR Server Databases to a New Drive on the Same Server
    • StifleRulez.xml Configuration Guide
      • The Match – TypeData
        • When the Job Title Isn’t Suitable
        • ConfigMgr Specific Rules
      • The Setting - DownloadTypes
        • Delivery Optimization Jobs
      • Sample StifleRulez.xml
    • Securing StifleR Operations with SSL
      • Pre-Requisites
      • Securing the StifleR SignalR Endpoint
        • Binding certificates to SSL Ports for SignalR/StifleR
      • Running SignalR with SSL
      • IIS Configuration
      • Appendix A: Certificates
        • Using IIS to create a self-signed Certificate
        • Using a full IIS Certificate
      • Appendix B:Finding the CertHash
Powered by GitBook
On this page
Export as PDF
  1. StifleR 2.6.x.x
  2. StifleRulez.xml Configuration Guide
  3. The Match – TypeData

ConfigMgr Specific Rules

Matching specific Configuration Manager download types can be a little complicated. We shall use the following XML file line as an example:

<Type TypeID="256" Match="Equals" WellConnected="0" UserInitiated="1" CCMDTSType="4" WinPE="1">CCMDTS Job</Type> <!--Task Sequence in WinPE : User Initiated Low Bandwidth -->

WellConnected="1"/”0”

Used to match for Well Connected sites

In our example WellConnected="0" is a match for a normal StifleR bandwidth-controlled site,

CCMDTSType=

Used to identify a specific type of ConfigMgr deployment

0 = Package/Program

4 = Task Sequence

5 = Software Update

8 = Application

In our example CCMDTSType="4" matches a ConfigMgr Task Sequence download.

UserInitiated="1"/”0”

Specifies whether the download job was started by a user (“1”) or not (“0”)

In the example UserInitiated="1" would only match ConfigMgr downloads which were triggered by the user.

WinPE="1"/”0”

Specifies if the download is coming from WinPE.

In our example WinPE="1" will only match if the download is running in WinPE

Putting all three of the above rules together we can see that this line will match to Task Sequence Download, initiated by the user, running in WinPE.

DownloadOnDemand="1"/”0”

Identifies Task Sequence download behavior

<Type TypeID="209" Match="Equals" DownloadOnDemand="1" CCMDTSType="4">CCMDTS Job</Type> <!--Task Sequence in Full OS : Required Deployment : Download on Demand -->

This rule will apply for a TS which has been set to Download Content as required rather than before execution of the Task Sequence ( CCMDTSType="4" )

PreviousWhen the Job Title Isn’t SuitableNextThe Setting - DownloadTypes

Last updated 2 years ago