|The information in this topic applies only to System Center 2012 Configuration Manager SP1.|
Before you can manage a Linux or UNIX server with Configuration Manager, you must install the Configuration Manager client for Linux and UNIX on each Linux or UNIX computer. You can accomplish this manually or by use of a shell script that installs the client remotely. Configuration Manager does not support the use of client push installation for Linux or UNIX servers. Optionally you can configure a Runbook for System Center 2012 Orchestrator to automate the install of the client on the Linux or UNIX server.
The install script for the Configuration Manager client for Linux and UNIX supports command line properties. Some command line properties are required, while others are optional. For example, when you install the client, you must specify a management point from the site that is used by the Linux or UNIX server for its initial contact with the site. For the complete list of command line properties, see Command Line Properties for Installing the Client on Linux and UNIX Servers.
After you install the client, you specify Client Settings in the Configuration Manager console to configure the client agent in the same way you would windows-based clients. For more information, see the Client Settings for Linux and UNIX Servers section in the Operations for Linux and UNIX Servers for Configuration Manager topic.
Install the Client on Linux and UNIX Servers
To install the client for Linux and UNIX, you run a script on each Linux or UNIX computer. The script is named install and supports command line properties that modify the installation behavior and reference the client installation package. The install script and client installation package must be located on the client. The client installation package contains the Configuration Manager client files for a specific Linux or UNIX operating system:
The client installation package contains all the necessary files to complete the client installation and unlike Windows-based computers, does not download additional files from a management point or other source location.
After you install the Configuration Manager client for Linux and UNIX, you do not need to reboot the computer. As soon as the software installation is complete, the client is operational. If you reboot the computer, the Configuration Manager client restarts automatically.
Following is the command format: ./install -mp <computer> -sitecode <sitecode> <property #1> <property #2> <client installation package>
./install –mp smsmp.contoso.com sitecode S01 ccm-RHEL5x86.tar
You can insert additional command line properties before the command line property that specifies the client installation .tar file. The client installation .tar file must be specified last.
For a list of command line options, see Command Line Properties for Installing the Client on Linux and UNIX Servers.
Use the following procedure as an example of how to install the client for Linux and UNIX.
|The following example procedure installs the client for Linux and UNIX on a Red Hat Enterprise Linux 5 (RHEL5) x86 computer. To adjust this procedure for the operating systems that you use, replace the client installation file (ccm-RHEL5x86.tar) with the appropriate file each operating system. Also plan to use additional command line properties to meet your requirements.|
To install the Configuration Manager Client on Linux and UNIX servers
Command Line Properties for Installing the Client on Linux and UNIX Servers
Uninstalling the Client from Linux and UNIX Servers
Configure Request Ports for the Client for Linux and UNIX
Similar to Windows-based clients, the Configuration Manager client for Linux and UNIX uses HTTP and HTTPS to communicate with Configuration Manager site systems. The ports that the Configuration Manager client uses to communicate are referred to as a request ports.
When you install the Configuration Manager client for Linux and UNIX, you can change the clients default request ports by specifying the -httpport and -httpsport installation properties. When you do not specify the installation property and a custom value, the client uses the default values. The default values are 80 for HTTP traffic and 443 for HTTPS traffic.
After you install the client, you cannot change its request port configuration. Instead, to change the port configuration you must reinstall the client and specify the new port configuration. When you reinstall the client to change the request port numbers, run the install command similar to the new client install, but use the additional command line property of -keepdb. This switch instructs the installation to retain the client database and files including the clients GUID and certificate store.
For more information about client communication port numbers, see How to Configure Client Communication Port Numbers in Configuration Manager.
Configure the Client for Linux and UNIX to Locate Management Points
When you install the Configuration Manager client for Linux and UNIX, you must specify a management point to use as an initial point of contact.
The Configuration Manager client for Linux and UNIX contacts this management point at the time the client installs. If the client fails to contact the management point, the client software continues to retry until successful.
For more information about how clients locate management points, see the section Locating Management Points section in the How to Assign Clients to a Site in Configuration Manager topic.