You add a scope to the asset import job to gather more specific asset data.
To provide a scope for the asset import, you first limit the scope to a location in the system. The location can be a site, a domain in case of Windows, or a database in case of SQL and Oracle. When you specify a scope at the location level, the asset import query returns the specified asset type from the specified location only.
After you provide the scope at the location level, you can select a specific folder, an asset group, or an asset. The asset import query looks for the specified folder, the asset group, or the asset at the specified location and returns the asset type. It is recommended that you provide asset groups or containers as scopes instead of providing individual assets as scopes.
Consider the following example:
Assume that you want to import the Windows Files. You limit the scope to Windows Machine, which is the default scope for the Windows Files. You select a folder as a scope that contains the Windows Machine and Windows Domain. In this case, the asset import query does not consider the Windows Domain as you have limited the scope to Windows Machine only.
Table: Asset import scope options explains how the default scopes and the supported scopes work in the asset import.
You can scope the assets in the following ways:
The default scope includes the primary assets for the asset type that you want to include. You import the selected asset type from the primary asset for that asset type.
Use any or all the supported scopes
The supported scopes include all the asset types or sites from which you can import the selected asset type.
Table: Asset import scope options