Red Hat NETWORK 3.2 - PROVISIONING Reference Manual page 60

50
Include system in daily summary report calculations — This setting includes the system
•
in a daily summary of system events. (By default, all Management and Provisioning systems
are included in the summary.) These are actions affecting packages, such as scheduled Errata
Updates, and system reboots or failures to check in. In addition to including the system here,
you must choose to receive email notifications in the Your Preferences page of the Your RHN
category. Refer to Section 4.3.2 Your Preferences for instructions. Note that RHN will send
these summaries only to verified email addresses.
Automatic application of relevant errata — This setting allows you have all Errata Updates
•
automatically applied to a system. This means packages associated with Errata will be updated
without any user intervention. Customers should note that Red Hat does not recommend the
use of the auto-update feature for production systems because conflicts between packages and
environments can cause system failures. The Red Hat Network Daemon must be enabled on
the systems for this feature to work.
Hardware — Detailed information about the system, including networking, BIOS, storage, and
•
other devices. This appears only if you selected to include the hardware profile for this machine
during registration. If the hardware profile looks incomplete or outdated, click the Schedule
Hardware Refresh button to schedule a Hardware Profile update for your system. The next time
the RHN Daemon connects to RHN, it will update your System Profile with the latest list of
hardware.
Notes — A place to create notes about the system. To add a new note, click the create new note
•
button, type a subject and details, and click the Create button. To modify a note, click on its
subject in the list of notes, make your changes, and click the Update button. To remove a note,
click on its subject in the list of notes and then click the delete note button.
Custom Info — Completely customizable information about the system. Unlike a note, infor-
•
mation included here is more formal and can be searched upon. For instance, you may decide to
identify the cubicle in which each system is located. To do this, you must first create a cubicle
key within the Custom System Info page. Refer to Section 4.4.9 Custom System Info for instruc-
tions. Once the key exists, you may assign a value to it by clicking create new value here. Click
the name of the key in the resulting list and enter a value for it in the Description field, such as
"Cube #456." Then click the Update Key button.
Reactivation — A System Profile-specific activation key. This allows you to create an activation
•
key encompassing this system's ID, history, groups, and channels. You may then use this key with
the
rhnreg_ks
settings. Refer to Section 2.5 Registering with Activation Keys for instructions. Unlike typical
activation keys, which are not associated with a specific system ID, keys created here do not
show up within the Activation Keys page.
Remote Command — The method for running a remote command only on the selected system.
•
You must have created a
the description of the Configuration subtab of the Channels tab for instructions. You may then
identify a specific user, group, and timeout period, as well as the script itself on this page. Select
a date and time to begin attempting the command, and click Schedule Remote Command.
Connection — The system's path to the package repository. Regardless of whether your client
•
systems receive updates from the central RHN servers or an RHN Satellite Server, it is important
to know if packages are being routed through any RHN Proxy Servers. This subtab identifies the
proxies being used and the order in which they receive updates. A one (1) indicates the top proxy
connected to either RHN or a satellite. If no proxy is used, you receive a message stating, "This
system connects directly and not through a proxy."
Errata — Contains a list of Errata Alerts applicable to the system. To apply updates, select them
•
and click the Apply Errata button. Double-check the updates to be applied on the confirmation
command line utility to re-register this system and regain all Red Hat Network
file on the client system for this function to be allowed. Refer to
run
Chapter 4. Red Hat Network Website