Data collection .xml files are accumulating in the ETL file repository.
As a best practice, it is recommended to perform data collection activity as infrequently as possible. Excessive data collection activity can result in too much data being generated and the inability of the systems which support the data collection process to function properly.
There are two data collection objects available for use in Desktop Authority; one in the user based profile and one in the computer based profile.
Data collection in a user based profile can be set to a timing of logon and logoff in order to track user logons and logoffs. However, data collection in the computer based profile is for collecting inventory information. Since hardware and software inventory typically does not change on a daily basis, collecting this data once per week or once per month should be frequent enough to maintain an updated inventory.
If collecting USB/Port Security information, a separate element may need to be created and set to validate at a time when no other data collection elements are executing as these .xml files can grow very large in size and take a considerable amount of time to process.
Please Note: The following setting applies only to Desktop Authority 9.x and above:
If appropriate action has been taken regarding the considerations outlined above and .xml files continue to accumulate in the ETL file repository, change the registry value below on the Desktop Authority server:
For a 32 bit server: HKLM\Software\ScriptLogic\ETLProcessor\"ThreadProcessedFileSleepDelay" change from 250 to 0
For a 64 bit server: HKLM\Software\Wow6432Node\ScriptLogic\ETLProcessor\"ThreadProcessedFileSleepDelay" change from 250 to 0
Then restart the "Desktop Authority Operations" Service in the Windows services applet (services.msc).
NOTE: Technical Support does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 "Description of the Microsoft Windows registry" at Microsoft Support.
