background image

L E G A L   N O T I C E

Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a 

retrieval system, or transmitted without the express written consent of the publisher. For Novell trademarks, see 

t  he Novell

  

 

Trademark and Service Mark list

 

(http:// www.novell.com/company/legal/trademarks/tmlist.html)

. All third-party trademarks are 

the property of their respective owners. A trademark symbol (® , TM, etc.) denotes a Novell trademark; an asterisk (*) denotes 

a third-party trademark.

THIS DOCUMENT AND MODIFIED VERSIONS OF THIS DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU 

FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT:

THE DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR 

IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE 

DOCUMENT IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NON-INFRINGING. THE 

ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION 

OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY 

RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY 

NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN 

ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS 

AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), 

CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF 

THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE 

LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF 

ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, 

COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR 

RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY 

SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.

p. 

10

Summary of Contents for ZENworks 7.2 Linux Management

Page 1: ...www novell com Scenarios 2 Novell ZENworks 7 2 Linux Management March 30 2007 ...

Page 2: ... S C E N A R I O S The purpose of these scenarios is to familiarize you with the some of new features included in ZENworks 7 2 Linux Management Breakout With the release of ZENworks 7 2 Linux Management Novell engineering has compiled scenarios that represent a number of the new features and functions of the product These scenarios are used by our test team and are now being shared outside of the ...

Page 3: ...Upgrading the ZENworks Server from a Previous ZENworks Linux Management Release 2 Upgrading a Managed Device Other Than SLES 10 OR SLED 10 from a Previous ZENworks Linux Management Release 3 Upgrading a SLES 10 OR SLED 10 Managed Device Package and Content Management Scenarios 4 Configuring the ZENworks Server to Choose the Best Package for a Managed Device 5 Software Package Rollback p 3 ...

Page 4: ...nments between them and one or more devices Be sure to use several different kinds of schedules For more information see the ZENworks Linux Management Administration Guide 5 Perform an upgrade For more information see Upgrade in the ZENworks 7 2 Linux Management Installation Guide Expected Results Objects still exist and their details can be viewed the assignments still exist between them and the ...

Page 5: ...Management Dell Edition installed Steps 1 Upgrade the server to ZENworks 7 2 Linux Management You can use the same setup as the Scenario 1 2 On the managed device perform the following steps a Lock any bundle by executing the rug bla bundle_name command b Lock any package by executing the rug la package_name command 3 Upgrade the managed device For more information see Upgrade in the ZENworks 7 2 ...

Page 6: ...nux Management You can use the same setup as Scenario 1 2 On the managed device lock any bundle by executing the rug bla bundle_name command 3 Upgrade the managed device For more information see Upgrade in the ZENworks 7 2 Linux Management Installation Guide Expected Results The managed device is upgraded to ZENworks 7 2 Linux Management All the service associations are retained All the bundle loc...

Page 7: ...d information see Setting Up Managed Devices in the ZENworks 7 2 Linux Management Installation Guide 2 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 3 On the managed device install a package that you need by executing the rug in package_name command Expected Results The ZENworks Management Daemon zmd installs...

Page 8: ...in Step 2 by executing the following command rug sub catalog_name c List all packages contained in the catalog created in Step 2 by executing the following command rug pa catalog_name d Make a note of the date and time when you enable the Rollback preference by executing the date command e Install a package by executing the following command rug in package_name f Ensure that the package is install...

Page 9: ...Expected Results The package installed in Step 3e is uninstalled To ensure that the package is uninstalled execute the rug pa catalog_name command and verify that the status of the package is blank p 9 ...

Page 10: ... THE QUALITY ACCURACY AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS WITH YOU SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT YOU NOT THE INITIAL WRITER AUTHOR OR ANY CONTRIBUTOR ASSUME THE COST OF ANY NECESSARY SERVICING REPAIR OR CORRECTION THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE NO USE OF ANY DOCUMENT OR MODIFIED V...

Reviews: