It is not uncommon to need additional data to be stored about a server or set of servers.
- Who the responsible parties are (owners of the server or applications)
- What applications the server supports (logical business systems that span multiple servers)
- Maintenance information
- And more
SCCM does a great job of inventorying the details of a system – the hardware installed, the applications installed, etc. It does not, however, have any mechinsm built in for collecting random bits of data that identify a server as part of a "system" of servers. For instance, you may have a multi-tier app that has a database server, a web front end, and a job server. SCCM clearly identifies the software bits that are installed on each of these servers but does not identify that the servers are related in some way.
With the tool available in the attachment to this entry, you have the option to add metadata to the server that is captured and can be used in reporting as well as collection assignment for targeting.
Since this is just metadata, it doesn’t have to be limited to just logical business systems. You can include information such as who the responsible party for a server is or the maintenance window assignement for a server. You can determine which environment a non-production server is a part of. You can be as creative as you wish (or need) to be.
The attachment has four files in it:
- MetaData_v1.1.1.hta. This is the main application that should be advertised to your systems. It allows for the editing of meta data on each server.
- MetaData.SMS_DEF.MOF. This is an excerpt that should be inserted into your SMS_DEF.MOF file in order to allow SCCM to capture the metadata during hardware inventories.
- MetaData.Reports.MOF. These are some sample reports that you can use that utilize some of the metadata. Some of the reports require a particular categorization to the metadata tags, so you may need to modify them.
- Server MetaData Tool Overview.pdf. This document provides an overview of the tool and how it works. It also provides some ideas for tags and how to format them.
The HTML application, when it is run, does connect up to the management point to read in current tags. It assumes that the SCCM WMI provider is installed on the MP (since it just calls into that structure to identify the current tags). You may need to modify the query portion of the tool to connect to the correct server and if the WMI class name is different in your environment. Since it does do this connection, users who run the tool must have the right to read the SMS_site WMI repository on the site server. Usually not a big deal – just add them to the SMS Administrators group on the site server (which authorizes the ability to connect to the WMI provider but does not assign permissions within the app itself).
Let me know if this is useful to you.