Examples of asset filters

You create the filter statements that are based on the asset fields when you create an asset group and an asset import job.

In case of creation of an asset import job, you need to create the filters that are based on the asset type that you select.

The following table describes certain filter statements that you can use to import assets under specific scenarios.

Table: Examples of asset filters

Scenario

Filter statement

Job result

To import assets of the Windows Directory with Machine 1 and Machine 2 as scope

((Root Path EqualTo D: Or Root Path EqualTo C:) and depth GreaterThanOrEqualTo 1) and Is Shared? = True

The job returns all the shared folders under the C:\ and the D:\ drive.

To import the Files and the Directories with name like *Accounting*

(Root Path EqualTo D:\directory and depth GreaterThanOrEqualTo 1) and Directory Name Like %Accounts%

The job returns all the directories and the files that contain Accounting in the name.

To import all the directories and the files "n" level below the directory, D:\DATA

Root Path EqualTo D:\directory and depth GreaterThanOrEqualTo 1

The job returns all the e directories under the D:\ directory as per the available depth.

To import the Windows Directories with Machine 1 and domain as a scope

(Root Path EqualTo D:\directory and depth GreaterThanOrEqualTo 1 ) and PermissionsDifferentThanParent(Include Owner) / (Ignore Owner) EqualTo Different

The job returns all the directories of which the permissions differ from the parent.

To import UNIX Files under the directory, etc and the sub-directories

Filename(With Path) like /etc%

The job returns all the UNIX files under the directory, etc and from under the sub-directories.

See Create or Edit Asset Group: Create Specific Asset Type Filters.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.