Things to Consider When Configuring Asset Mgmt and Reporting in System Center ConfigMgr 2007 R2
The following are best practices in configuring asset management and reporting in ConfigMgr 2007 R2:
► Create and run reports from the central site to ensure data from the entire infrastructure can be seen. Site-specific reports can be created by filtering out data that isn’t needed.
► Avoid using IDMIF or NOIDMIF files to extend the hardware inventory. These files reside on the client computer and can dynamically modify the Configuration Manager database with custom data during the hardware inventory cycle. If this type of collection is necessary, ensure the risks are fully understood and the appropriate security has been implemented.
► Each Configuration Manager site can be configured with unique settings. Leverage the Transfer Site Settings option to copy configuration settings and other objects to different sites in the hierarchy.
► Similar queries are grouped together to improve performance. This is important to avoid searching the entire system multiple times when scanning for files. For example, searching all hard drives for EXEs and DLLs using the same options for the path, subdirectories, and exclusions results in a single query to find both types. If any of the options are different, multiple queries are used, which can significantly increase the time needed to complete the in-ventory.
► To exclude a drive or folders from being inventoried, create a hidden file called skpswi.dat. This file can be placed in any folder to prevent that folder from being inventoried, or at the root of a drive to prevent the entire drive from being inventoried.
► Use Desired Configuration Management to locate rouge skpswi.dat files that could be used to conceal file data.
► When editing the Configuration Manager MOF files, a backup is automatically created in the datahinvarchive folder located in the Configuration Manager installation directory. How-ever, it’s still recommended to make a copy of the MOF file before performing manual edits. Also, test hardware inventory extensions in a development environment before making changes to the production environment.
► Use the mofcomp.exe utility to compile and test custom hardware inventory classes before adding the information to the configuration.mof file.
► Don’t modify existing reports. Always make a copy of the report and make changes to the copy. During Configuration Manager service pack upgrades, the original reports can be updated by Microsoft, and if they’re customized, the changes are lost.
► Microsoft has created an extensive set of documentation detailing the Configuration Manager views needed to create custom reports. Use this information when creating custom reports.
► Use the v_R_System_Valid view when obsolete and decommissioned systems need to be excluded from the report. This view contains a subset of information that can be obtained from the v_R_System view.
► Make sure the correct view is queried for hardware data. Most current hardware inventory data can be accessed with the v_GS_ views. Historical hardware inventory data can be ac-cessed with the v_HS_ views.
► Don’t use Configuration Manager as an authoritative source for making licensing purchases. The actual counts of licenses should be tracked as systems are provisioned and deprovisioned throughout the enterprise. Configuration Manager should be used to validate those numbers.
► Each time licensing data is uploaded, the previous license data is overwritten. To avoid accuracy problems, make sure the complete list of licensing information is uploaded every time.
► Use the Installed Software node within the Hardware section of Resource Explorer to identify the correct values for the non-Microsoft software licensing CSV file.
► Use custom labels to categorize AI inventoried software. This allows customization and grouping of software based on specific business requirements.
► Software information that is uploaded and eventually categorized by Microsoft is made available to all Microsoft customers through System Center Online Services. Avoid uploading private software information that could be used to identify your business to other customers.
► Digitally sign PowerShell scripts. This allows the PowerShell execution policy to be configured for AllSigned. The AllSigned policy ensures that only authorized, signed scripts can be run in the environment. For additional information on script signing, type get-help about_signing in a PowerShell console.
This posting is 1 of a monthlong series of postings on the Microsoft System Center family of products. This is an excerpt from my book “System Center Enterprise Unleashed” with more postings on the System Center family of products up at http://www.networkworld.com/community/morimoto
