Define Activation Conditions for Windows Endpoints
For each condition, you can specify either an executable file path, an executable file path and file version, or a registry path that must exist on the endpoint.
Use the following workflow to create a new activation condition for a rule on Windows endpoints.
- Select. The Conditions page displays theSettingsConditionsWindowsName,Description, andPath(if applicable) for each condition.
- Click the action menu and thenAdda new condition.
- Enter aNameandDescriptionto identify the condition.
- Select the type of condition, eitherPathto match on the path of a specific executable file and optionally on a specific version or range of versions for the executable file, orRegistryto match a specific registry key:
- To match a specific executable file (or to match a specific version of an executable file), specify the fullPathof an executable file that exists on the endpoint. Optionally, you can use system variables in the path. For example, specify%windir%\system32\calc.exeto apply the rule if the calculator executable file is run from this location.
- If you specified an executable file in thePathfield, you can also set a match condition for a fileVersion(as displayed in the file properties) or range of versions of that executable file. If you specify aVersionvalue, Traps will only apply the rule if the executable is run from the location specified in thePathfield and also matches theVersionvalue. By default, the condition matches any version of the file. To narrow the number of versions, select one of the followingVersion Comparisonoptions and then enter aVersionnumber.When you configure a condition to match aVersion, Traps evaluates the version value stored in the file properties. Because this number may be different than the published version number, we recommend that you verify the version number in the file properties before creating your condition.TheVersionmust follow the standard Windows version convention and be no longer than four segments long (for example, 220.127.116.11). To match versions longer than four segments long, useRegex.
- Equal—Match an exact version.
- Greater—Match any version that is equal to or greater than the specified version.
- Lesser—Match any version that is equal to or lesser than the specified version.
- Between—Match any version inclusive of and between two values. For example, to set a condition that matches Internet Explorer versions between and including versions 8 and 9, enterC:\Program Files\Internet Explorer\iexplore.exein thePathfield, selectVersion Comparison: Between, and enter8and9in theVersionfields.
- Regex—Match a version using .NET Framework 4 regular expressions.(Refer to Microsoft’s Regular Expression Language Quick Reference at https://msdn.microsoft.com/en-us/library/az24scfc(v=vs.100).aspx).For example, to match any version of 3.1.x including 3.1, use the following regular expression:3\.1(\.[0-9]+)?To match only versions 3.1.0-3.1.9 use:3\.1\.[0-9]To match only version 3.2 and 3.4, use:3\.
- Specify a fullRegistry Pathfor a registry entry, beginning with one of the following:LocalMachine,ClassesRoot,Users,PerformanceData,CurrentConfig, orDynData.You cannot specifyCurrentUserregistry paths because Traps runs as the local system.Traps will only apply the rule if the endpoint contains the specified path in its registry. You can also configure a specific registryKeyorDatavalue (String and DWord only) as a match condition.For example, to apply a rule on endpoints that have IPv6 enabled, configure a condition that matches the following registry settings:
- Registry Path:LocalMachine\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters\EnableICSIPv6
- Savethe condition.
Recommended For You
Recommended videos not found.