Profile Management

Use wildcards

August 6, 2024

Contributed by:

C C

You can use DOS-style wildcard characters such as the question mark (?) and asterisk (*) in policies that refer to files and folders. Examples include file inclusion and exclusion lists and folder inclusion and exclusion lists. The question mark (?) matches a single character. The asterisk (*) matches zero or more characters.

Starting with Profile Management 7.15, you can use the vertical bar (|) to restrict the policy only to the current folder.

Be aware of the following:

Wildcards in file names work recursively while wildcards in folder names don’t. Ensure that you specify a valid path when using wildcards.
Policies that support wildcards do not support any other type of variable, such as the use of environment variables or Active Directory attributes. You cannot use wildcards in policies that refer to registry entries.

Examples

The wildcard <path name>\h*.txt matches house.txt, h.txt, and house.txt.txt, but does not match ah.txt.

The wildcard <path name>\a?c.txt matches abc.txt, but does not match ac.txt.

The wildcard <path name>\a?c*d.txt matches abcd.txt and abccd.txt, but does not match acd.txt.

Configuring policies in the profile root folder:

*.txt specifies all files with the extension .txt in the root folder and its subfolders.
*h.txt specifies all files that match this wildcard in the root folder and its subfolders.
h*.txt specifies all files that match this wildcard in the root folder and its subfolders.
a?c.txt specifies all files that match this wildcard in the root folder and its subfolders.
*.txt| specifies all files with the extension .txt only in the root folder.

Configuring policies in non-profile root folders:

AppData\*.txt specifies all files that match this wildcard in the AppData folder and its subfolders.
AppData\*h.txt specifies all files that match this wildcard in the AppData folder and its subfolders.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Use wildcards

August 6, 2024

Contributed by:

C C

August 6, 2024

Contributed by:

C C

Use wildcards

Examples

In this article