Inventory Solution lets you gather inventory data about computers, users, operating systems, and installed software applications in your environment. You can use predefined inventory policies to collect different types of inventory. You can also modify the predefined policies or you can create new inventory policies and tasks.
Before you set up policies and tasks to collect inventory in your environment, you need to consider the following questions:
These questions help you determine how inventory collection affects performance in your environment. You need to find the balance between collecting a sufficient amount of inventory data and using your resources appropriately.
Adhering to the following recommendations lets you effectively tune the inventory performance:
Avoid to include the drive that is not necessary to be scanned. By default, all local drives are scanned.
Include only those directories that you really want to scan.
Use the Report size/file count only setting to improve performance if you do not need to collect full information about files.
Increasing the frequency of an inventory task in an attempt to hit an "online window" causes redundant data to be sent to Notification Server. The workload on Notification Server increases as the duplicate data must still be processed and then discarded. Schedule inventory tasks to occur at the desired data refresh rate, so that the Symantec Management Agent can locally manage the inventory collection process.
The perceived need to run a full inventory on a frequent basis is a common misconception. Run full inventory only when the Inventory Plug-in reports that Notification Server has more information about a computer than the Notification Server database stores.
These components separate inventory policies by geographical, departmental, or other categories. Use these components to spread the timing and receipt of inventory on Notification Server. Then, large groups of computers continue to simultaneously post their inventory data to Notification Server. But Notification Server is busy for a few minutes as opposed to several hours. SQL deadlock warnings in Notification Server log reduce. You achieve a reduction in network traffic because the Inventory Plug-in does not receive the IIS "Server too busy" message and re-post inventory data.