- 1 Product Description
- 1.1 Known Versions
- 2 Software Pattern Summary
- 3 Platforms Supported by the Pattern
- 4 Identification
- 4.1 Software Instance Triggers
- 4.2 Software Instance type attributes created
- 4.3 Simple Identification Mappings
- 5 Versioning
- 5.1 Registry Versioning
- 5.2 Package Versioning
- 5.3 Alternative Versioning Approach
- 5.4 Future Considerations
- 6 Application Model Produced by Software Pattern
- 6.1 Product Architecture
- 6.2 Software Pattern Model
- 6.2.1 SI Depth
- 6.2.2 Relationship Creation
- 7 Subject Matter Expertise
- 8 Testing
- 9 Information Sources
- 10 Open Issues
- Discover with Foundation
-
This product can be discovered by Professional or Enterprise editions of Tideway Foundation, but you can still Download our free Community Edition to discover other products!
- What is this?
- This is a product information page, containing details of the information that Tideway Foundation gathers about a product and how it is obtained.
- Product Name
- System Center Configuration Manager
- Publisher Page
- Category
- Release
- TKU 2008-May-1
- Reports & Attributes
Microsoft System Center Configuration Manager - Reports & Attributes
- Publisher Link
- Microsoft
Product Description
Microsoft System Center Configuration Manager (SCCM) 2007, the successor to Microsoft Systems Management Server 2003, is the solution to comprehensively assess, deploy and update your servers, clients, and devices - across physical, virtual, distributed and mobile environments. Optimized for Windows and extensible beyond, it is the best choice for gaining enhanced insight into and control over your IT systems.
Known Versions
- 2007
Software Pattern Summary
| Product Component | OS Type | Versioning | Pattern Depth |
|---|---|---|---|
| SiteServer | Windows | Package | Instance-based |
| Console | Windows | Registry, Package | Instance-based |
| Client | Windows | Package | Instance-based |
Platforms Supported by the Pattern
Each of the three patterns support the Windows platform.
Identification
Software Instance Triggers
| Component | Trigger Node | Attribute | Condition | Argument |
|---|---|---|---|---|
| SiteServer | DiscoveredProcess | cmd | matches | regex '(?i)\bsmsexec\.exe$' |
| Console | cmd | regex '(?i)\bmmc\.exe$' | ||
| args | regex 'Microsoft Configuration Manager.*\badminconsole\.msc' | |||
| Client | cmd | regex '(?i)\bccmexec\.exe$' |
Software Instance type attributes created
The patterns in this module will set the following attributes:
| Pattern Name | SI type |
|---|---|
| SiteServer | Microsoft System Center Configuration Manager Site Server |
| Console | Microsoft System Center Configuration Manager Console |
| Client | Microsoft System Center Configuration Manager Client |
Simple Identification Mappings
The following components/processes are identified using the combination of pattern definitions and simple identity mappings which map other known (but deemed less important in terms of application modeling) processes.
| Name | Command | Arguments |
|---|---|---|
| Microsoft System Center Configuration Manager Courier Sender Manager | (?i)\bcoursend\.exe$ | |
| Microsoft System Center Configuration Manager Setup Wizard | (?i)Microsoft Configuration Manager\\.*\\setup\.exe | |
| Microsoft System Center Configuration Manager Site Repair Wizard | (?i)Microsoft Configuration Manager\\.*\\repairwizard\.exe | |
| Microsoft System Center Configuration Manager SMS Site VSS Writer | (?i)\bsmswriter\.exe$ | |
| Microsoft System Center Configuration Manager SMS Site Backup | (?i)\bsmsbkup\.exe$ | |
| Microsoft System Center Configuration Manager SMS Site SQL Backup | (?i)\bsmssqlbkup\.exe$ | |
| Microsoft System Center Configuration Manager SMS Site Component Manager | (?i)\bsitecomp\.exe$ | |
| Microsoft System Center Configuration Manager SMS Agent Host | (?i)\bccmexec\.exe$ | |
| Microsoft System Center Configuration Manager SMS Executive | (?i)\bsmsexec\.exe$ | |
| Microsoft System Center Configuration Manager SMS Server Locator Point | (?i)\bslpexec\.exe$ | |
| Microsoft System Center Configuration Manager SMS Reporting Point | (?i)\bsmsrph\.exe$ | |
| Microsoft System Center Configuration Manager Service Manager | (?i)\bcompmgr\.exe$ | |
| Microsoft Systems Management Server Client Advertised Programs Manager (Win32) | (?i)\bsmsapm32\.exe$ | |
| Microsoft Systems Management Server Client Service | (?i)\bclisvcl\.exe$ | |
| Microsoft System Center Configuration Manager Console | (?i)\bmmc\.exe$ | Microsoft Configuration Manager.*\badminconsole\.msc |
Versioning
Version information for the product is currently collected using one of two possible methods.
The methods are tried in an order of precedence based on likely success and/or accuracy of the information that can be gathered. Once a result is obtained, the methods lower in precedence are not attempted. In order of precedence the methods are:
Registry Versioning
For the Console pattern only, an attempt is made to extract versioning information from the Windows Registry by searching for the following entry:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr\Setup\Full UI Version
If found, versioning information, normally to four levels, is extracted.
Package Versioning
All three patterns get the packages from the Package Manager and compare them against the following regex:
- ^Microsoft System Center Configuration Manager
The first package which matches will have its versioning information extracted.
Alternative Versioning Approach
Future Considerations
Application Model Produced by Software Pattern
Product Architecture
Microsoft System Center Configuration Manager runs on the Windows platform only.
Software Pattern Model
The SiteServer pattern triggers on the Microsoft System Center Configuration Manager SMS Executive (smsexec.exe) process.
The Console pattern triggers on a mmc.exe process having 'Microsoft Configuration Manager.*\badminconsole\.msc' as its arguments.
The Client pattern triggers on the Microsoft System Center Configuration Manager SMS Agent Host (ccmexec.exe) process.
SI Depth
The SiteServer pattern creates an instance-based Software Instance, its key being based on instance (if available), type (Microsoft System Center Configuration Manager Site Server) and host key.
The Console pattern creates an instance-based Software Instance, its key being based on site_server name (if available), type (Microsoft System Center Configuration Manager Console) and host key.
The Client pattern creates an instance-based Software Instance, its key being based on full version (if available), type (Microsoft System Center Configuration Manager Client) and host key.
Relationship Creation
The Console pattern gets all the trigger process' child processes and associates them to the generated Software Instance.
The Server pattern attempts to create a client-server communication link with its associated Microsoft SQL Server Software Instance running on the same or a different host.
Both the Console and Client patterns attempt to create a client-server communication link with its associated Microsoft System Center Configuration Manager Site Server Software Instance running on the same or a different host.
Subject Matter Expertise
Any SME input would be welcome on any other potential approaches to improving Microsoft System Center Configuration Manager versioning coverage and depth.
Testing
The patterns and simple identifiers have been compared against a Windows installations.
The patterns and simple identifiers have also been tested using test data for the Windows platform. Such test data was unable to prove that the Registry entries were indeed retrievable.
Information Sources
Open Issues
| TOP |
|---|
Created by: [Rebecca Shalfield] 15:00, 18 April 2008 (GMT)
Reviewed by: [Luke Stedman] 13:30, 28 April 2008 (GMT)
RSS
Tideway Blog