About rules
The power of Data Translation Services (DTS) is found in its rules, which enable you to scan for much of the device data that's important to your IT work. DTS installs with numerous rules that will address most of your IT needs, though you can configure your own rules to perform customized tasks as well. For a comprehensive list of supported rules, see Supported rules, connectors, and vendors.
When you configure a rule and run it, you're enabling DTS to perform a task such as retrieving warranty data from a vendor website, pulling data from Active Directory, and so on. Once that information is in the inventory database, you can use it for customized reporting.
Each rule type has a wizard that steps you through the rule-making process. Some rules are complicated enough that overviews are provided. For details, see the following topics:
Rule Name | |
---|---|
Normalize wizard | |
Software-license import wizard / Software-license importing overview |
|
|
Learn more
Each rule has a specific wizard that steps you through the configuration process.
The first page of each wizard requires you to provide a name and description for the rule. Each rule of any type must have a unique name. The description you enter will display in the DTS tree next to the rule name.
The second page of most wizards requires you to select the database where the rule will store the data it gathers. Depending on what you have installed, the database options are Management Suite, Asset Manager, Asset Control, or Asset Lifecycle Manager. In most cases, you'll want to select Management Suite, so that the gathered data is imported into your inventory database.
All rules that are set to "active" are executed by the Data Analytics core scan processor service as scan files. The service actually does the processing of the scan files by moving them to different directories:
- The Ivanti inventory service receives the scan file and puts it in the ManagementSuite\ldscan directory with an extension of .MP.
- The Data Analytics core scan processor service moves the scan file to the ManagementSuite\MP_TEMP directory and changes the extension to .SCN.
- All active rules are applied to the scan file.
- Next, the core scan processor service moves the scan file from the ManagementSuite\MP_TEMP directory back to the ManagementSuite\ldscan directory.
- Finally, the Ivanti inventory service processes the scan file into the inventory database.
The core scan processor service processes multiple scan files simultaneously (by default, 10 at a time). You can increase or decrease this number with a registry value. Increasing the value can increase performance if Data Analytics rules spend a lot of time waiting for other resources, such as LDAP queries or other computers.
Change the number of scans processed simultaneously
1.Set the following registry value:HKLM\Software\Managed Planet\Core\ThreadCount
This value is a DWORD. Set it to the number of simultaneous scan files to be processed.