Server

The following tasks contain information on performing common server operations:


Creating Activations

For a conceptual discussion of activations, see Activations: Granting Client Access.

Activations are created by clicking the Server link in the ZENworks Linux Management Web interface.

  1. Click Server, then click the activations link.

  2. Click Create to create a new multi-use (reuasable) or single-use activation.

    Multi-use activations can optionally have a key name and description. Single-use activations must have an e-mail address associated with the activation, and can optionally have a description.

  3. Your activation is now created.


E-Mailing an Activation

Select one or more activations, then click the Email Selected Activations to send the selected activations to the e-mail addresses you specify.


Managing Your Server: Licenses, News, and Organizations

The last section of the Web interface contains a number of configuration and setup items that you will use relatively infrequently, and some of which are documented elsewhere in this manual:

Activations

For information about activation management, read Activations: Granting Client Access.


Cache License Management

The cache is discussed in The Caching Server.


News Items

The News tool allows you to create news for users to read with the rug news command or in the News section of the GUI client. You can use it to announce new software, or provide additional information on particular updates.

To enter news, click the News tab in the left hand navigation bar, and then enter a headline, link, and summary for the news item. Then, select the channel to which the news entry is most relevant, and click Save.

You can do the same thing at the command line with the rcman news-add command. See the rcman man page for details.


Server Configuration

The server configuration page displays basic information about your server. These settings should not normally be changed except at install time, and are altered by editing the /etc/ximian/rcserver.conf file. In addition, there are several settings not displayed here, and available only through the configuration file. For example, the server_contact value, which sets the return address on notifications and other server mail, is set only in that file.

Database

Type of database used in this deployment.

Packages Path

The location of the package repository. The default is /ximian/red-carpet-server.

Cache Directory

Package cache location for the template engine. This will almost never need to be changed.

Language

The default language is en_US, US English. You may set this value to other standard UNIX language codes, provided that translations have been completed.

Expire

Amount of time, in seconds, that the server will wait before expiring client authentications. In most cases, it will not need to be changed.

Secret

This is a unique string used for authentication. In most cases, this should be left alone.

Custom branding theme, if any. Check with your sales representative if you have questions about custom branded software.

For detailed configuration information, check the man page for rcserver.conf(5).


Server License Administration

The server license administration page contains a list all the seat licenses you have available. If you have not purchased any licenses since your initial deployment, you will have only one entry in the table. Seat usage information is displayed here and when you log in to the Web interface.

To purchase additional seats for your organization, contact your sales representative, who will send you a two-part license key. To use the key, click the Add License link at the top of the list of current licenses. Enter the words as the first segment, and the code as the second, then click Add or press Return. The new license key will validate itself against your existing server license and add new seats to your organization.


Target Platforms

The Target Platforms page displays the target platforms recognized by the ZENworks Linux Management server. This is the same as using the command rcman targets.

From the target list page you can make two changes: hide or show a target, and delete it entirely. To hide or show a target, select the Shown or Hidden button, and click Save. To delete a target, check the box in the Delete column and click Delete.

You can also add or edit target platforms if you wish, although it is not normally suggested. To add a target, click Create new Targets at the top of the target list. To edit a target, click its name.

Target creation and editing allow you to specify the following information:

Name

Name your target. Typically this should be the name, version, and platform, separated by dashes, omitting decimal points and spaces: Red Hat 8.0 for the i386 platform is represented as redhat-80-i386.

Description

Enter a short description for your target.

Version

The version number of the operating system.

Arch

The architecture abbreviation, such as i386, i586, i686, ppc, or sparc64.

Package format

The type of packaging system used in this operating system. This is always RPM. Other formats are not supported.

Detect

This is a series of XML tags that allows the server to recognize the operating system. Most Linux operating systems can be identified from a particular file in the /etc/ directory, and in that case the appropriate value is:

<file source="[filename]" substring="[unique string in file]"/>

Other Unix-based operating systems have more complex identification procedures. For example, Solaris 8 must be identified by the output of the uname command, making the appropriate XML string as follows:

<os_name substring="SunOS"/> 
<os_release substring="5.8"/>
<command source="uname -s" substring="SunOS"/>
<command source="uname -r" substring="5.8"/>

Support Level

Select a support level for the operating system: internal, presupported, unsupported, supported, deprecated, or retired. Only supported and deprecated platforms are displayed to clients.


Organization Management

Organization management is available only for multiple organization customers. For documentation on this feature, consult the "Superadmin" manual or contact your sales or support representative.