User manual NOVELL ZENWORKS 7.2 LINUX MANAGEMENT SCENARIOS 1 03-30-2007

[. . . ] Scenarios - 1 www. novell. com Novell® ZENworks® 7. 2 Linux Management March 30, 2007 NOVELL ZENWORKS 7. 2 LINUX MANAGEMENT Novell® ZENworks® Linux Management makes it easy to embrace and extend Linux* within your existing environment. It is the only solution that uses policy-driven automation to deploy, manage, and maintain Linux resources. These automated and intelligent policies allow you to provide centralized control across the lifecycle of Linux systems for desktop lockdown, imaging, remote management, inventory management, and software management. The result is a comprehensive Linux management solution that eliminates IT effort by dramatically reducing the required overhead needed to manage Linux systems. [. . . ] Create two RPM bundles, one containing any package you choose, and the other bundle containing an update to that package. For more information, see Creating RPM Bundles in the ZENworks 7. 2 Linux Management Administration Guide. Assign the first bundle to a device and make sure that the bundle gets installed and that the inventory scanner acknowledges that the package is installed (check on the Inventory tab of the device's Details page). Delete the second bundle so that the updated package is in the system, but it is not contained in any bundle. From the device list page, verify that an icon is shown in the Updates Available column, and that clicking it gives the explanation that an updated package exists in the system, but is not made available by any bundles. Expected Results: Verify that the Updates Available icon is shown for the following reasons: · · There is a bundle assigned to this device, whose latest version isn't currently deployed. There is a Dell system set (DUP Bundle) for this device's model in the repository, but it is not assigned to this device. p. 13 · There is a package in the repository that is an update to a package installed on this device, but the package: o is contained in a bundle not assigned to this device o is contained in a version of a bundle assigned to this device, which isn't currently deployed o is contained in a bundle assigned to this device, but simply hasn't been installed yet o is not contained in any bundle p. 14 8: LOCKING PACKAGES ON A MANAGED DEVICE Objective: Prevent deletion of a package on a managed device by locking the package. For detailed information, see Setting Up Managed Devices in the ZENworks 7. 2 Linux Management Installation Guide. Register the managed device to a Red Carpet Enterprise (RCE) or a YUM server by executing the rug sa URL_of_the_RCE_or_YUM_server command. On the managed device, list all packages installed by executing the rug pa command. Select a package you want to lock, and lock it by executing the rug la package_name command. On the managed device, list all the locked packages by executing the rug ll command. Expected Results: On the managed device, delete the locked package by executing the rug rm package_name command. Notice that the specified package is not deleted in this scenario because it is locked. The following message is displayed: "package_name is locked and cannot be removed. " For information on how to unlock a package, see rug in the ZENworks 7. 2 Linux Management Administration Guide. p. 15 9: LOCKING BUNDLES ON A MANAGED DEVICE Objective: Prevent deletion of a bundle on a managed device by locking the bundle. Ensure that you have installed the ZENworks 7. 2 Linux Management server components and ZENworks Agent. For detailed information, see Installation in the ZENworks 7. 2 Linux Management Installation Guide. In the ZENworks Control Center, create a bundle and assign it to the managed device. For detailed information, see Creating RPM Bundles in the ZENworks 7. 2 Linux Management Administration Guide. [. . . ] From the drop-down list, choose one of the settings you have already configured at the zone or folder level, and choose a new value for it. Refresh the device by clicking Refresh from the Quick Tasks list or by going to the device and executing rug ref. Expected Results: You see the value set at the device, not the value inherited from the zone or folder level. NOTE: ZMD Settings are pushed to the device on the next refresh; however, they do not go into effect until ZMD is restarted on the device. p. [. . . ]