Table of Contents
Advertisement
25.9.2 Delivering Specific RPM Packages (Pushing)
If you want to provide specific RPM packages, you can create a custom bundle by selecting the
desired subset of RPM packages from the initial bundle that was created when mirroring the Red
Hat Network. Or, you can create several custom bundles, each containing one or more RPM
packages. It is best to test your custom bundles on a single device to verify that there are no conflicts
within a bundle. If the test is successful, you can then assign the bundles to your managed devices.
To ensure that the packages contained in the custom bundle can meet all of their dependencies, you
can create a catalog containing the mirrored Red Hat Network bundle and make it available to the
desired managed devices. During the catalog creation process, you can hide this catalog from users.
After you assign the custom bundle to devices, if a package requires other packages for dependency
resolution, the device has access to the packages in the hidden catalog. For more information, see
Section 22.2, "Creating Catalogs," on page
271.
Managed devices refresh on a schedule. Also, an administrator can trigger a device refresh through
the ZENworks Control Center. When a device refreshes, it downloads the bundle automatically from
the server and installs it.
The managed device requests one or more bundles from the server. In other words, the server does
not actually push the bundle. However, the server can tell the managed device to refresh
immediately. You can also modify the refresh interval centrally from the server for one or more
managed devices. Otherwise, the client refreshes on its own schedule to look for a scheduled action.
From a managed device, you can use rug to force a refresh by entering the
command.
rug refresh
For SUSE Linux Enterprise Server 10 (SLES 10) and SUSE Linux Enterprise Desktop (SLED 10)
devices:
/usr/bin/rug refresh
For other managed devices:
/opt/novell/zenworks/bin/rug refresh
For more information, see
rug (1) (page
586).
25.10 Encoding the ZENworks Server Password
When you configure the XML configuration file prior to performing a mirroring operation, you
specify your ZENworks Server's password in the
section. To provide enhanced
LocalServer
security, you can encode the password before placing it in the configuration file.
To encode the ZENworks Server's password, execute the following command:
echo mypassword | recode ../b64
where
represents your ZENworks Server's password. You can then use the resulting
mypassword
text in place of the clear text password.
Mirroring Software 319
Advertisement
Table of Contents
