Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
When managing UNIX servers with System Center 2012 R2 Configuration Manager, the ability to configure collections, maintenance windows, and client settings are enabled to help management of said servers. Although the Configuration Manager client for UNIX does not have a user interface, you can force the client to manually poll for client policy. Niel Orcutt, Senior Software Development Engineer, has recently provided further insight as to creating a custom UNIX provider for System Center 2012 R2 Configuration Manager. This Step-By-Step is a derivative of that article which details the process for setting up a development environment for creating and deploying a custom provider for AIX, HP-UX and Solaris (UNIX) clients for System Center 2012 Configuration Manager Service Pack 1.
Configuration Manager providers are developed using the open-source Open Management Infrastructure (OMI) development environment (http://collaboration.opengroup.org/omi). Code sample provided utilize the OMI software to illustrate this process.
The tasks that need to be done to develop and deploy a new provider are:
Note: The same process can be used to develop custom providers for System Center 2012 Operations Manager R2 clients for UNIX computers.
Step 1: Installing and configuring the OMI development environment Custom providers for Configuration Manager UNIX clients are developed using the open source OMI environment.
Step 2: Creating and Compiling the Provider
Step 3: Installing the New Provider on the Client
Step 4: Registering the Provider with the Configuration Manager Server
The next time the Configuration Manger server received an inventory from my UNIX client, you are now able to view the Frog information when before the Resource Explorer was used to view details about the client computer.
Note: There are two different items called namespaces in the CIM environment:
1. An identifier for the place where data about a class and its objects is stored. In Configuration Manager this is usually root/cimv2.
2. The part of a class name before the first underscore character. In the case of the XYZ_Frog class, this would be XYZ. The first character in a class name must be alphabetic. Some CIM tools require that all class names begin a namespace name followed by an underscore and that the character after the underscore also be alphabetic. You may need to follow this convention in naming your custom classes.
Note that this posting is provided "AS IS" with no warranties and confers no rights.