That’s an example of a management pack version number. As I’ve started this new position, I’ve installed numerous management packs, and those version numbers have been driving me crazy because I couldn’t figure them out.
Let’s say I was running a management pack with that version number and an updated pack was released. I expected to see 6.0.5000.13, but instead I would see something like 6.0.5000.21.
Finally, a patient PM (program manager) sat down with me and explained how it works:
The first three sections of the version (or build) number are the version number of the Operations Manager product. In our example, 6.0.5000 = Operations Manager 2007 (RTM release). A version number of 6.0.6278 = Ops Manager 2007 Service Pack 1.
Management packs draw from the same pool of version numbers. I was expecting sequential version numbers for that specific management pack — for example, DHCP would be version …2, then …3, and so on. Instead, when a management pack is going to be released, it’s assigned the next available version number in the series of 6.0.5000.# or 6.0.5278.#.
There’s a science behind it all, I’m sure, that provides a cohesive system for versioning products all across the company, that could explain which parts of the number are incremented by product and which parts are pooled. I’m satisfied just learning how the string of numbers in my little corner of the world came to be.