# ConfigMgr-specific rules

Matching specific Configuration Manager download types can be a little complicated. We shall use the following XML element 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"

The WellConnected attribute is used to match for Well Connected sites

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

#### CCMDTSType=

The CCMDTSType attribute is 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"

The UserInitiated attribute and associated values specify whether the download job was started by a user (“1”) or not (“0”)

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

#### WinPE="1"/"0"

The WinPE attribute and associated values specify 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 a Task Sequence download, initiated by the user, running in WinPE.

#### DownloadOnDemand="1"/"0"

The DownloadOnDemand attribute and associated values identify 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 Task Sequence which has been set to download content as required rather than before execution of the Task Sequence ( CCMDTSType="4" ).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/configuration/stiflerulez.xml-2.x-definitions/the-match-typedata/configmgr-specific-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.