Regardless of whether you create a policy or define a rule group, the framework available to define rules is the same.
Supported system variables
The path specified in a rule can include system environment variables. This table lists the supported system variables.
Variable | Example value (most Windows platforms) |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These considerations apply to path-based rules.
Paths don't need to be absolute when specifying rules. For example, when defining an updater, you can specify partial or fully qualified paths.
Partial paths — If you specify partial paths, such as
AcroRd32.exeorReader\AcroRd32.exe, all programs with names that match the specified string are assigned updater rights. Similarly, when blocking a file, all programs with names that match the specified string are blocked.Fully qualified paths — When you specify fully qualified paths, such as
C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exeor\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exeonly the specified program is assigned updater rights. When blocking a file, if you specify the fully qualified path, for exampleC:\Windows\system32\notepad.exe, only the specified file is blocked.
Paths can contain white spaces.
Paths can include the wildcard characters to specify file paths and file names. When using wildcards, ensure that specified string matches a limited set of file paths or file names. If the specified string matches many files, we recommend you revise the string.
Paths can include the * and ? wildcard characters.