The Asset ManagementPack – currently named WindowsManagementExperts.Win32_Product.ManagementPack – combines Win32_ComputerSystem with the Win32_Product to create an instant visual profile of any Server an SCOM Agent is installed on.
The Win32_CompiterSystem class, according to Microsoft documentation, is described as: The Win32_ComputerSystem class represents a computer system operating in a Win32 environment.
The Win32_Product class, according to Microsoft documentation, is described as: The Instances of this class represent products as they are installed by MSI. A product generally correlates to a single installation package.
When these two are combined. they can be combined with Active Directory information to complete an informational package that identifies user with the ownership of hardware and installed software.
The two classes are used to create tables and the discovery used to populate them. This is then displayed through a view inside System Center Operations Manager (SCOM).
It also includes a dedicated Asset Management Report in SRS format
While the ManagementPack targets Server Computers, it could also be built to target Client Computers.
- Why was this ManagementPack created?
- This ManagementPack was created to support cross Enterprise collection of vital asset information that explores and displays the integrity, security, and comparative accuracy of each server’s Network Login accounts.
The beauty of this ManagementPack is its ability to collect all the information for all the servers in one table.
Using SQL Server, a connection string and a SQL Query can be created to reacquire the data and be mined to support a wide variety of outputs including Access, Excel, HTA, HTML and XSL – just to name a few.
Once the information is transformed into a reporting tool, the ManagementPack can be deleted from SCOM and the table it produced will no longer exist.
- How Often should it be used?
- Because of the way the ManagementPack works, it is strongly recommended to use it once to build an informational foundation and then use it once a month thereafter to determine if any of the accounts have changed or are about to expire.
There are also two other times when you may want to consider this ManagementPack would deem necessary. When an account has been suspect of being tampered with and when an account should no longer be on the server.
- How much time does it save?
- In terms of development and testing, about a week.
- How long does it take for the data to show up in the operations manager console?
- There are a lot of factors that could stop this from happening immediately. Normally, by design, since the discovery is run almost immediately, the data can be viewed just as fast.
- Are there any customizations for my environment that I need to add to the management pack?
- No, there are no customizations required.
- Can I customize the discovery Interval?
- Yes, you can. By default, the interval is set to 86,400 seconds or once a day. You can adjust the interval as well as the timeout interval to the desired response and timeout conditions through the SCOM Console.
- How often does the data get updated?
- When the ManagementPack is installed, the discovery gets run after that it will be based on the frequency set for it to run—which is currently once a day.
- How will I know when a new version of the management pack is released?
- There are two ways this can happen. Provide us with your E-mail address or come to the site and look for the words “Updated Release” beside the name of this ManagementPack.
- Can you supply us with a custom report?
- With a great amount of pride and enthusiasm, we certainly can.
Unfortunately, while not problem for us, this may be a SQL Server security issue for you.
So many times it works for us, but doesn’t work for our customers.
If it isn’t an issue, then E-mail us.