Home > Articles > Operating Systems, Server > Microsoft Servers

This chapter is from the book

The Common Information Model

As discussed in previous chapters, the CIM has three conceptual layers, each of which builds upon the previous one, providing a greater level of detail. Notice in Figure 4.3 that layer 3 is sometimes referred to as the "layer of extensibility."

Figure 4.3Figure 4.3 The three layers of CIM

The core and common models are referred to collectively as the CIM Schema.

The purpose of layering the model is to allow schema designers to view the model as a series of logical progressions from which they can build. The CIM Schema represents the basic classes, properties, methods, and associations of all potentially managed objects within an enterprise.

The Core Model

The core model defines a number of very general classes to describe basic structures and relationships between manageable components in an environment. This information model is independent of any product or implementation.

The Common Model

The common model defines a basic set of classes that represent specific areas of management within the enterprise. The common model consists of a number of models, each of which represents specific management areas. Currently the DMTF defines models that represent the network-, user-, system-, support-, policy-, physical-, metrics-, interoperability-, events-, device-, and application-specific aspects of the enterprise. (A number of submodels extend these models. For more information on the submodels, visit http://www.dmtf.org, the DMTF Web site.) The number of areas represented by classes in the common model are expected to increase over time, the better to represent the variety of advances in technology.

Systems Model

The systems model defines the basic characteristics associated with managed systems. A managed system can be an operating system, a network system, or an application system. It defines the root class CIM_ManagedSystemElement, from which all system classes must derive. Included as part of this model are classes that define services, file systems, threads, processes, and software features.

Networks Model

The networks model defines a series of classes, associations, methods, and properties that represent the features of a network environment. Features that are common to a network environment include protocols, services, and the topology of the network. Within the networks model, a number of submodels define the classes, associations, methods, and properties that are specific to their environment.

Devices Model

The devices model defines the physical and logical components that support the system. Examples of classes defined as part of the devices model include CIM_POTS Modem, CIM_Processor, CIM_Printer, and CIM_DesktopMonitor.

Physical Model

The physical model is not to be confused with the devices model. Whereas the devices model defines a set of classes that support the managed system, the physical model represents the physical environment. You will find that the physical environment is of surprisingly little concern in the managed environment. Under normal circumstances, you will not often need to come into direct contact with a physical element within an environment but will instead interact with its logical counterpart. Any manipulation of physical elements within the environment normally is a result of manipulation of an associated logical object. For example, imagine an Ethernet network card in an ISA slot of a personal computer running Windows XP. If you were to perform some action that resulted in a series of packets being sent out of the card to the network, it you might trigger the Tx (Transmit) LED on the network card to start blinking. This behavior was the result of the packet being sent out of the card—the Tx LED cannot be addressed directly or polled for its status.

Because the physical model represents the physical aspects of a system, the classes it contains will differ considerably, depending upon the host system (consider the differences in architecture of an HP Mainframe and a desktop computer) and will change to represent the advances in technology.

Applications Model

The applications model describes the details required to manage a set of software applications. The diversity of software applications demands that the model must be flexible enough to describe multiplatform or distributes applications. The applications model borrows heavily from the application software life cycle. The application software life cycle describes the various states of a software application from its initial purchase through its execution.

Event Model

The event model describes CIM Indications and how they are used to communicate occurrences of events in the CIM. It also describes the classes that enable clients to subscribe to CIM Indications, including how to specify a desired mode of delivery. The Specification for CIM Operations over HTTP defines the XML encoding for CIM Indications over HTTP.

Policy Model

The policy model enables application developers, policy administrators, and network administrators to represent and manage policy across a variety of technical domains that include security, networking, and system administration.

Support Model

The support model describes the object and transaction models for the exchange of  knowledge related to support activities (Solutions) and the processing of Service Incidents. The object and transaction models are referred to as the Problem Resolution Standard or PRS.

User Model

The user model provides a set of relationships between the various representations of users, their credentials, and the managed system elements that represent the resources and resource managers in system user administration. Thus, the CIM user and security models added to the preexisting set of requirements for the introduction of a "top" object class in the CIM core model.

Metrics Model

The metrics model defines classes to represent a unit of work and its associated metrics. For example, a print job could be a unit of work and the number of pages to be printed could be the metric.

Interop Model

The interop model defines architectures and mechanisms that enable WBEM implementations to interoperate in an open, standard manner, and addresses issues that prevent them from doing so.

In addition to these models is a number of submodels that include:

CIM Network Submodel—IPsec Policy Model. Defines a number of CIM extensions that represent the IP security policy model.

CIM Submodel—Storage Model. Defines the Logical Devices associated with data storage.

CIM Device Submodel—Sensor Model. Defines additional properties and methods for the classes CIM_Sensor and CIM_Numeric Sensor.

CIM Device Submodel—Printer Model. Describes the management of the functionality and protocols specific to printers.

CIM Submodel—Fault Tolerant Model. Defines a number of fault tolerant extensions to the CIM model.

CIM System Submodel—Diagnostic Model. Describes additional aspects needed for successful diagnostics under multi-tasking operating systems.

The Extended Schemas

Vendors who wish to represent the manageable aspects of their hardware or software product as part of the CIM define the extended schemas. Extended schemas typically derive from classes defined as part of the common model, although it is possible to extend from the core model. An example of an extended schema is the mechanism with which operating system vendors can model the manageable aspects of their operating systems in the CIM. Microsoft uses the Win32 extended schema to represent its Windows platform (Windows 98, NT4.0/2000/WinXP/.NET). The management information you retrieve from WMI about the Windows environment typically will be retrieved from the classes defined as part of the Win32 extended schema, because the majority of CIM schema classes defined within the CIMV2 namespace are declared as abstract.

When designing the CIM, the DMTF envisaged a number of ways to implement it. Among the proposed methods were:

  • An application Data Base Management System (DBMS)

  • A series of application objects that represent instances of CIM classes

  • A structure to pass the instances of CIM between applications

Even from a brief look at the core, common, and extended schemas, it is clear that the DMTF's task in designing the CIM was complex. Because of its complexity, navigating the CIM repository and the query response times on such a large volume of information are design concerns. Too much information to process can be as detrimental to the usability of an information model as not enough information. In addition, a CIM repository might host multiple managed environments, such as local and nonlocal devices. How can we rationalize them?

To overcome these problems, the DMTF developed namespaces, a mechanism for partitioning sections of CIM into smaller logical groupings.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020