|The information in this topic applies only to System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager.|
The Microsoft System Center 2012 Configuration Manager client for Linux and UNIX supports software deployments that use packages and programs. You cannot deploy System Center 2012 Configuration Manager applications to computers that run Linux and UNIX.
The client supports the following functionality for packages and program deployments:
- You can install software for Linux and UNIX
servers, including the following:
- New software deployment
- Software updates for programs already on the
- Operating system patches
- New software deployment
- You can run native Linux and UNIX commands,
and run scripts that are located on Linux and UNIX servers.
- You can limit deployment to the operating
systems that you specify when you select the program option Only
on specified client platforms.
- You can use maintenance windows to control
when software installs.
- You can use deployment status messages to
Beginning with the client from cumulative update 1, the following additional functionality is supported:
- The client can throttle network usage when
downloading software from a distribution point.
When you configure and deploy packages and programs for Linux and UNIX servers, use the same methods that you use to configure and deploy packages and programs to your Windows-based computers with the following caveats:
Use only configurations that are intended for computers, and do not use configurations that are intended for users.
The Configuration Manager client for Linux and UNIX does not support configurations that are intended for users.
Configure programs to download the software from the distribution point and run the programs from the local client cache
The Configuration Manager client for Linux and UNIX does not support running software from the distribution point. Instead, you must configure the software to download to the client and then install.
By default, after the client for Linux and UNIX installs software, that software is deleted from the client’s cache. However, packages that are configured with Persist content in the client cache are not deleted from the client and remain in the client’s cache after the software installs.
The client for Linux and UNIX does not support configurations for the client cache, and the maximum size of the client cache is limited only by the free disk space on the client computer.
Configure the Network Access Account for distribution point access
Linux and UNIX computers are designed to be workgroup computers. In order to access packages from the distribution point in the Configuration Manager site server domain, you must configure the Network Access Account for the site. You must specify this account as a software distribution component property and configure the account before you deploy software.
Beginning with System Center 2012 R2 Configuration Manager, you can configure multiple Network Access Accounts at each site. The client for Linux and UNIX can use each of the accounts you configure as a Network Access Account.
For more information, see Configuring Site Components in Configuration Manager.
You can deploy packages and programs to collections that contain only Linux or UNIX clients, or you can deploy them to collections that contain a mix of client types, such as the All Systems Collection.
|When you deploy software to a mixed collection, it is likely that many clients in the collection are unable to run the software successfully because they are the wrong operating system type to understand the program files. As a result, the deployment will report failure.|
When the Configuration Manager client for Linux and UNIX receives and runs a deployment, it generates status messages. You can view these status messages in the Configuration Manager console, or by using reports to monitor the deployment status.
For information about how to use packages and programs, see Packages and Programs in Configuration Manager.
The following sections provide details about software deployment to Linux and UNIX servers.
Configuring Packages, Programs, and Deployments for Linux and UNIX Servers
You can create and deploy packages and programs by using the options that are available by default in the Configuration Manager console. The client does not require any unique configurations.
Use the information in the following sections to configure packages and programs as well as deployments.
Packages and Programs
Manage Network Bandwidth for Software Downloads from Distribution Points
Beginning with the client for Linux and UNIX from cumulative update 1, the client supports network bandwidth controls when downloading software from a distribution point.
The client uses the BITS settings that you configure as client settings in Configuration Manager, but does not implement BITS. Instead, to throttle the use of network bandwidth, the client controls the HTTP request chunk size and inter-chunk delay for the software download.
To configure a client to use network bandwidth controls, you configure client settings for Background Intelligent Transfer and then apply the settings to the client computer. To use bandwidth controls, the client must receive client settings for Background Intelligent Transfer with the following setting configured as Yes:
- Limit the maximum network bandwidth for
BITS background transfers
The client supports the following configurations for Background Intelligent Transfer:
- Throttling window start time
- Throttling window end time
- Maximum transfer rate during throttling
- Maximum transfer rate during throttling
The following configuration for Background Intelligent Transfer is not supported, and is ignored by the client for Linux and UNIX:
- Allow BITS downloads outside the
If the download of software to the client from a distribution point is interrupted, the client for Linux and UNIX does not resume the download and instead restarts the download of the entire software package.
Operations for Software Deployments
Similar to the Windows client, the Configuration Manager client for Linux and UNIX discovers new software deployments when it polls and checks for new policy. The frequency at which the client checks for new policy depends on client settings. You can configure maintenance windows to control when software deployments occur.
You can configure software deployments to Linux and UNIX servers by using package properties, program properties, and deployment properties.
When the client receives policy for a deployment, it submits a status message. It also submits status messages when it starts the installation of software and when the installation finishes, or fails.
Programs for software deployments run with the root credentials that the Configuration Manager client for Linux and UNIX runs with. The exit code of the programs command is used to determine success or failure. An exit code of 0 (zero) is treated as success. In addition, the stdout (standard output stream) and stderr (standard error stream) are copied to the log file when the log level is set to INFO or TRACE.
|If the software that you want to deploy is located on a Network File System (NFS) share that the Linux or UNIX server can access, you do not need to use a distribution point to download the package. Instead, when you create the package, do not select the check box for This package contains source files. Then, when you configure the program, specify the appropriate command line to directly access the package on the NFS mount point.|