Novell ZENWORKS 10 Preboot Services and Imaging Reference
Novell®
www.novell.com
AUTHORIZED DOCUMENTATION
Preboot Services and Imaging Reference
ZENworks® 10 Configuration Management SP3
novdocx (en) 16 April 2010
10.3
April 16, 2010
ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
novdocx (en) 16 April 2010
Copyright © 2007-2010 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.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
novdocx (en) 16 April 2010
novdocx (en) 16 April 2010
4 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Contents
About This Guide 11
1Overview 13
1.1 Brief Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.1 Preboot Services Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.2 Preboot Services Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.3 Imaging Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.4 Configuring Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1.5 Setting Up Devices to Use Imaging Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2 What Is the Preboot Execution Environment (PXE)?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.1 Understanding How Preboot Services Uses PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.2 Understanding the ZENworks NBPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.3 Preparing to Use PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3 Preboot Services Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.1 Imaging Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.2 Novell Preboot Services Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.3.3 Non-Registered Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.3.4 Device Imaging Work Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.3.5 Server Referral List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.3.6 Intel Active Management Technology (AMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.4 The Preboot Services Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.4.1 A Typical Preboot Services Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.4.2 Illustrating the Preboot Services Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.5 Preboot Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.5.1 Automating Imaging Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.5.2 Creating, Installing, and Restoring Standard Images . . . . . . . . . . . . . . . . . . . . . . . . 35
1.5.3 Reimaging Corrupted Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.5.4 Restoring Lab Devices to a Clean State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.5.5 Setting Up Devices for Future Reimaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.5.6 Multicasting Device Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
novdocx (en) 16 April 2010
2 Setting Up Preboot Services and Imaging 41
2.1 Preparing a Preboot Services Imaging Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.2 Preparing a Satellite with the Imaging Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.2.1 Understanding the Imaging Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.2.2 Configuring the Imaging Role to the Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.2.3 Illustrating the Preboot Services Processes on the Imaging Satellite . . . . . . . . . . . . 43
2.3 Setting Up the Preboot Services Methods for ZENworks Imaging. . . . . . . . . . . . . . . . . . . . . . 46
2.3.1 Using Preboot Services (PXE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.3.2 Preparing Imaging Boot CDs or DVDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.3.3 Configuring with ZENworks Imaging Media Creator . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.3.4 Managing ZENworks Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.4 Deploying and Managing Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.4.1 Checking the Preboot Services Imaging Server Setup . . . . . . . . . . . . . . . . . . . . . . . 59
2.4.2 Deploying Preboot Services in a Network Environment . . . . . . . . . . . . . . . . . . . . . . 60
2.4.3 Administering Preboot Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.4.4 Editing the Novell Preboot Services Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.5 Configuring Preboot Services Defaults for ZENworks Imaging . . . . . . . . . . . . . . . . . . . . . . . . 73
2.5.1 Configuring Novell Preboot Services Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . 74
Contents 5
2.5.2 Configuring Non-Registered Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.5.3 Configuring Device Imaging Work Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.5.4 Configuring the Server Referral List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
2.5.5 Configuring Intel Active Management Technology (AMT) . . . . . . . . . . . . . . . . . . . . . 94
2.6 Overriding Preboot Services Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.7 Enabling PXE on Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
2.7.1 Enabling PXE on a PXE-Capable Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
2.7.2 Verifying That PXE Is Enabled on a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2.8 Setting Up Devices for ZENworks Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2.8.1 Device Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2.8.2 Enabling a Device for Imaging Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3 Using Imaging 99
3.1 Imaging Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.1.1 Using ZENworks Control Center for Imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.1.2 Using the Command Line for ZENworks Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1.3 Setting Up Disconnected Imaging Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.2 Multicasting Images for ZENworks Imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.2.1 Using ZENworks Control Center to Multicast an Image. . . . . . . . . . . . . . . . . . . . . . 122
3.2.2 Using the Command Line to Multicast an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
3.3 Configuring Imaging Script Bundles for ZENworks Imaging . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.4 Assigning Imaging Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
3.4.1 Using the Devices Tab to Assign Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
3.4.2 Assigning Devices to Bundle Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.4.3 Using the Bundles Tab to Assign Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
3.4.4 Assigning Bundles to Non-Registered Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.5 Editing Imaging Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
novdocx (en) 16 April 2010
4 Imaging Operations in a ZENworks Asset Management Agent and ZENworks
Desktop Management Agent Coexistence Environment 143
4.1 Taking an Image of a Device that has the ZDM 7.x Agent and the ZENworks Adaptive Agent with
Asset Management Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4.2 Restoring the Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4.2.1 Restoring the Image on the Same Device Whose Image was Taken . . . . . . . . . . . 144
4.2.2 Restoring the Image to Another Device that Has Only the ZDM 7.x Agent Installed 144
4.2.3 Restoring the Image to a Non-Registered Device . . . . . . . . . . . . . . . . . . . . . . . . . . 145
A Preboot Actions 147
A.1 Action - Imaging Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
A.1.1 Adding a New Imaging Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.1.2 Editing an Existing Imaging Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.2 Action - Linked Application Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.3 Action - Multicast Image Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.3.1 Adding a Multicast Image Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.3.2 Editing a Multicast Image Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.4 Action - ZENworks Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
A.4.1 Adding a ZENworks Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
A.4.2 Editing a ZENworks Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
A.5 Action - Third Party Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.5.1 Adding a Third-Party Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.5.2 Editing a Third-Party Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
B File Sets and Image Numbers 155
B.1 File Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
B.2 Image Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
C Replicating the TFTP Directory 157
C.1 Configuring the TFTP Directory Replication Settings at the Management Zone Level . . . . . 157
C.2 Configuring the TFTP Directory Replication Settings at the Folder Level . . . . . . . . . . . . . . . 160
C.3 Configuring the TFTP Directory Replication Settings at the Device Level . . . . . . . . . . . . . . . 161
C.4 Understanding the TFTP Replication Schedule Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
C.4.1 Date Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
C.4.2 Recurring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
C.5 Resolving Circular Dependency on the Master Primary Server. . . . . . . . . . . . . . . . . . . . . . . 164
C.5.1 Resolving Circular Dependency at the Management Zone Level . . . . . . . . . . . . . . 165
C.5.2 Resolving Circular Dependency at the Folder Level . . . . . . . . . . . . . . . . . . . . . . . . 165
C.5.3 Resolving Circular Dependency at the Device Level . . . . . . . . . . . . . . . . . . . . . . . . 165
D Third-Party Imaging 167
D.1 Things to Know Before Working on ZENworks Third-Party Imaging . . . . . . . . . . . . . . . . . . . 167
D.2 Performing ZENworks Third-Party Imaging by Using ZENworks Control Center. . . . . . . . . . 168
D.3 Setting Up Preboot Services for ZENworks Third-Party Imaging. . . . . . . . . . . . . . . . . . . . . . 168
D.4 Performing ZENworks Third-Party Imaging in the Maintenance Mode . . . . . . . . . . . . . . . . . 169
D.4.1 Launching the . . . . . . . . . . . . . . . . . . Novell ZENworks Third Party Imaging Utility170
D.4.2 Taking an Image of a Device and Storing it Locally. . . . . . . . . . . . . . . . . . . . . . . . . 170
D.4.3 Taking an Image of a Device and Storing it in a Remote Repository . . . . . . . . . . . 171
D.4.4 Restoring a Locally Stored Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
D.4.5 Restoring an Image to a Device on a Shared Network Location . . . . . . . . . . . . . . . 174
D.4.6 Adding, Deleting, or Activating Disk Partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
D.4.7 Querying for the Third-Party Imaging Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
D.5 Configuring the Destination Disk Structure Before Restoring a WIM Image . . . . . . . . . . . . . 177
novdocx (en) 16 April 2010
E Imaging Utilities and Components 181
E.1 Image Explorer (zmgexp). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
E.1.1 Starting Image Explorer on ZENworks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
E.1.2 Installing and Starting the Image Explorer on a Standalone Device . . . . . . . . . . . . 182
E.1.3 Determining the Image Explorer Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
E.1.4 Image Explorer versus Windows Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
E.1.5 Opening an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
E.1.6 Saving Image Changes and Exiting the Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
E.1.7 Managing Image Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
E.1.8 Image File Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
E.1.9 Modifying Image Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
E.1.10 Creating a New Image File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
E.2 Novell ZENworks Configuration Management Imaging Agent (novell-ziswin) . . . . . . . . . . . . 194
E.3 Novell ZENworks ISD Service (novell-zisdservice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
E.3.1 Understanding the SID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
E.3.2 Understanding the ZENworks SIDchanger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
E.3.3 Disabling the SIDchanger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
E.4 Image-Safe Data Viewer and Editor (zisview and zisedit) . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
E.4.1 Information Displayed by the Image-Safe Data Viewer . . . . . . . . . . . . . . . . . . . . . . 199
E.4.2 Using the Image-Safe Data Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
E.4.3 Using the Image-Safe Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
E.5 ZENworks Imaging Floppy Boot Disk Creator (zmediacreator) . . . . . . . . . . . . . . . . . . . . . . . 202
Contents 7
E.6 Imaging Configuration Parameters (settings.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
E.7 Imaging Boot Parameter for PCMCIA Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
E.8 Imaging Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
E.8.1 Initiating the Imaging Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
E.8.2 Viewing Information About Imaging Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
E.8.3 Starting a Manual Multicast Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
E.9 TFTP Client for WinPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
F ZENworks Imaging Engine Commands 217
F.1 Help Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
F.1.1 Using the ZENworks Imaging Engine Menu for Help . . . . . . . . . . . . . . . . . . . . . . . 218
F.1.2 Using the Imaging Maintenance Mode Prompt for Help . . . . . . . . . . . . . . . . . . . . . 218
F.2 Automatic (Query for Work) Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
F.2.1 Using the ZENworks Imaging Engine Menu to Query for Work. . . . . . . . . . . . . . . . 219
F.2.2 Using the Imaging Maintenance Mode Prompt to Query for Work . . . . . . . . . . . . . 219
F.3 Make Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
F.3.1 Make Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
F.3.2 Make to Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
F.4 Restore Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
F.4.1 Restore from Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
F.4.2 Restore from Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
F.5 Session Mode (Multicast Image Set) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
F.5.1 Multicasting Using the ZENworks Imaging Engine Menu . . . . . . . . . . . . . . . . . . . . 231
F.5.2 Multicasting Using the Imaging Maintenance Mode Prompt . . . . . . . . . . . . . . . . . . 231
F.6 Partition Operations Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
F.6.1 Using the ZENworks Imaging Engine Menu to Partition . . . . . . . . . . . . . . . . . . . . . 234
F.6.2 Using the Imaging Maintenance Mode Prompt to Partition . . . . . . . . . . . . . . . . . . . 234
F.7 ZENworks Partition Management Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
F.7.1 Using the ZENworks Imaging Engine Menu to Manage a Partition. . . . . . . . . . . . . 236
F.7.2 Using the Imaging Maintenance Mode Prompt to Manage a Partition . . . . . . . . . . 236
F.8 Dump Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
F.8.1 Using the ZENworks Imaging Engine Menu to View Partition Information . . . . . . . 237
F.8.2 Using the Imaging Maintenance Mode Prompt to View Partition Information . . . . . 237
F.9 Information Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
F.9.1 Using the ZENworks Imaging Engine Menu to View Device Information . . . . . . . . 239
F.9.2 Using the Imaging Maintenance Mode Prompt to View Device Information . . . . . . 239
novdocx (en) 16 April 2010
G Updating ZENworks Imaging Resource Files 241
G.1 The Linux Distribution for Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
G.2 Understanding Device Boot Processes in a ZENworks Imaging Environment . . . . . . . . . . . 241
G.2.1 linuxrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
G.2.2 zenworks.s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
G.3 Understanding ZENworks Partitions and Command Line Parameters . . . . . . . . . . . . . . . . . 243
G.3.1 The ZENworks Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
G.3.2 Command Line Parameters and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
G.4 Modifying ZENworks Imaging Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
G.4.1 Adding Files to an Imaging Boot CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
G.4.2 Adding Files to the Initrd or Root File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
G.4.3 Using the Driverupdate File Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
G.5 Adding or Updating LAN Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
G.5.1 Obtaining Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
G.5.2 Building Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
G.5.3 Loading Drivers with Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
G.6 Variables and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
8 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
G.6.1 Imaging Script Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
G.6.2 Linuxrc Parameters Specified in Settings.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
G.6.3 Image Engine Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
G.7 Troubleshooting Linux Driver Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
G.7.1 Troubleshooting During the Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
G.7.2 Troubleshooting at the Imaging Maintenance Mode Prompt . . . . . . . . . . . . . . . . . . 254
H Supported Ethernet Cards 255
I Accessing IP Addresses for Devices Running Dual NICs 257
J Troubleshooting Preboot Services and Imaging 259
J.1 Preboot Services and Imaging Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
J.2 Troubleshooting Preboot Services and Imaging Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
K Documentation Updates 271
K.1 April 16, 2010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
K.2 March 30, 2010: SP3 (10.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
novdocx (en) 16 April 2010
Contents 9
novdocx (en) 16 April 2010
10 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
About This Guide
novdocx (en) 16 April 2010
This Novell ZENworks 10 Configuration Management Preboot Services and Imaging Reference
®
includes information to help you successfully use Preboot Services and Imaging in a Novell
®
ZENworks
10 Configuration Management SP3 system.
The information in this guide is organized as follows:
Chapter 1, “Overview,” on page 13
Chapter 2, “Setting Up Preboot Services and Imaging,” on page 41
Chapter 3, “Using Imaging,” on page 99
Chapter 4, “Imaging Operations in a ZENworks Asset Management Agent and ZENworks
Desktop Management Agent Coexistence Environment,” on page 143
Appendix A, “Preboot Actions,” on page 147
Appendix B, “File Sets and Image Numbers,” on page 155
Appendix C, “Replicating the TFTP Directory,” on page 157
Appendix D, “Third-Party Imaging,” on page 167
Appendix E, “Imaging Utilities and Components,” on page 181
Appendix F, “ZENworks Imaging Engine Commands,” on page 217
Appendix G, “Updating ZENworks Imaging Resource Files,” on page 241
Appendix H, “Supported Ethernet Cards,” on page 255
Appendix I, “Accessing IP Addresses for Devices Running Dual NICs,” on page 257
Appendix J, “Troubleshooting Preboot Services and Imaging,” on page 259
Appendix K, “Documentation Updates,” on page 271
Audience
This guide is intended for ZENworks Configuration Management administrators.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to the Novell Documentation Feedback site (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Additional Documentation
ZENworks 10 Configuration Management is supported by other documentation (in both PDF and
HTML formats) that you can use to learn about and implement the product. For additional
documentation, see the ZENworks 10 Configuration Management SP3 documentation (http://
www.novell.com/documentation/zcm10/).
About This Guide 11
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
®
A trademark symbol (
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux*, should use forward slashes as required by your software.
novdocx (en) 16 April 2010
12 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
1
Overview
In Novell® ZENworks® 10 Configuration Management, Preboot Services provides functionality
that allows you to perform automatic imaging tasks on managed devices (Windows* Primary
Servers and Windows workstations) before their operating systems boot. You can also perform
manual imaging operations on these devices, as well as any other device with the supported file
system, such as legacy Windows workstations, Linux Primary Servers, and Linux workstations.
The following sections provide an overview of Preboot Services:
Section 1.1, “Brief Overview,” on page 13
Section 1.2, “What Is the Preboot Execution Environment (PXE)?,” on page 17
Section 1.3, “Preboot Services Functionality,” on page 19
Section 1.4, “The Preboot Services Processes,” on page 26
Section 1.5, “Preboot Strategies,” on page 34
novdocx (en) 16 April 2010
1
1.1 Brief Overview
The following provides a brief overview of Preboot Services:
Section 1.1.1, “Preboot Services Functionality,” on page 13
Section 1.1.2, “Preboot Services Strategies,” on page 14
Section 1.1.3, “Imaging Bundles,” on page 14
Section 1.1.4, “Configuring Preboot Services,” on page 15
Section 1.1.5, “Setting Up Devices to Use Imaging Bundles,” on page 16
1.1.1 Preboot Services Functionality
Preboot Services allows you to automatically or manually do any of the following to a Windows
device when it boots:
Make an image of the device’s hard drives and other storage devices
Restore an image to the device
Apply an existing image to multiple devices
Run Imaging scripts on the device
To accomplish these tasks automatically using ZENworks Control Center, you simply need to have
PXE (Preboot Execution Environment) enabled on your devices, then have Imaging bundles
configured and assigned to the devices. The devices automatically execute these bundles when they
boot.
Preboot Services utilizes the following to make its imaging functions possible:
PXE (Preboot Execution Environment): An Intel* specification that allows a device to boot
from the network, instead of its hard drive or other local media. ZENworks Configuration
Management can use PXE to launch Preboot Services.
Overview
13
Preboot Services Bootable CD or DVD: Used where PXE is not installed or where you want
to manually perform a Preboot Services operation. This is applicable only for ZENworks
Imaging.
Preboot Services Bootable Diskette: Enables using the Preboot Services bootable CD or
DVD when the device doesn’t support booting from a CD or DVD. This is applicable only for
ZENworks Imaging.
ZENworks Partition: Enables you to set up a device for unattended imaging operations where
the device is not PXE-enabled or does not have access to PXE network services. This is
applicable only for ZENworks Imaging.
For more information on these methods, see Chapter 3, “Using Imaging,” on page 99.
1.1.2 Preboot Services Strategies
Following are some of the uses of Preboot Services:
Create and Restore Standard Images: Create base images from existing devices, as well as
restore images to any manageable device.
Set Up Devices for Future Reimaging: Set up devices so that the next time they reboot, they
do the imaging work that is contained in their assigned Imaging bundle.
novdocx (en) 16 April 2010
Multicast Device Images: Apply an image of one device to many other devices. This is an
excellent feature for initially setting up a lab.
Restore Devices to a Clean State: Quickly and efficiently reset devices to an initial state, such
as in a lab.
For more information on these strategies, see Section 1.5, “Preboot Strategies,” on page 34.
1.1.3 Imaging Bundles
In ZENworks Control Center, Preboot Services tasks are contained in Imaging bundles. The
following Imaging bundle types are available:
Empty Bundle: A bundle with no initial tasks. You can quickly create this bundle without
performing all of tasks in the Create New Bundle wizard. Later, you can edit its details to add
assignments, actions, and so forth.
Imaging Script Bundle: Allows you to write a custom Imaging script. This provides detailed
control over ZENworks imaging operations, as well as most Windows-based preboot tasks.
This is applicable only for ZENworks Imaging.
Multicast Image Set Bundle: Specifies an image that can be sent through the multicast
protocol. This bundle allows you to send an image to a large number of devices in a single
operation, which minimizes network traffic. It is ideal for labs, classrooms, and staging areas.
This is applicable only for ZENworks Imaging.
Third-Party Image Bundle: Allows you to specify the third-party images that can be restored
on a device.
ZENworks Image Bundle: Lists one or more ZENworks images (base plus add-ons) that can
be restored on a device. This bundle allows you to define simple imaging operations.
To create one of these bundles: in ZENworks Control Center, click Bundles in the left pane, in the
Bundles panel click New > Bundle > Imaging Bundle > Next, then select a bundle type.
14 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
For more information on these bundles, see Section 1.3.1, “Imaging Bundles,” on page 19.
1.1.4 Configuring Preboot Services
In ZENworks Control Center, you can set up default Preboot Services configurations for all of your
devices. Some settings can be overridden at the device, group, and folder levels.
You can configure the following settings per ZENworks Management Zone:
Novell Preboot Services Menu Options: The menu contains five options: 1) Start ZENworks
Imaging (automatically executes the bundle); 2) Start ZENworks Imaging Maintenance
(accesses the imaging maintenance mode prompt); 3) Disable ZENworks Partition; 4) Enable
ZENworks Partition; and, 5) Exit (resumes booting). You can configure whether the menu is
displayed upon booting, not displayed, or displayed only when Ctrl+Alt is pressed during
booting.
Non-Registered Device Settings: You can use Preboot Services to automatically name your
non-registered devices, using such criteria as prefixes, BIOS information (such as asset tags or
serial numbers), DNS suffixes, and you can set up DHCP or IP addresses.
Device Imaging Work Assignment: Work assignment rules are used to determine which
bundle should be applied to which device. The work rules use logic to determine whether a
device meets the requirements for applying the Imaging bundle. A rule is made up of filters that
are used to determine whether a device complies with the rule. The AND and OR logical
operators are used for creating complex filters for the rule.
novdocx (en) 16 April 2010
Server Referral List: When a device boots, it is necessary for it to find its home Management
Zone to get its assigned imaging work. If multiple Management Zones exist on the network,
server referral lists provide a method for allowing a managed device to find its home zone.
Intel Active Management Technology (AMT): Intel AMT provides Preboot Services with
persistent device identification.
Third-Party Imaging Settings: You can upload WinPE (Windows Preboot Environment) and
third-party Imaging tools such as Microsoft Imaging engine (imagex.exe) and Symantec Ghost
ghost32.exe
(
). Before configuring the third-party Imaging settings, ensure that Microsoft
Windows Automated Installation Kit (WAIK) is installed on the device running the ZENworks
Control Center.
TFTP Replication Settings: You can replicate the changes made to the
other Imaging servers (Primary Servers or Satellites with the Imaging role). The
tftp
directory on
tftp
directory
contains files such as configuration files and binaries used by ZENworks Configuration
Management to perform imaging tasks. The directory is located on the Imaging server in
on Linux and in
%ZENWORKS_HOME%\share\
on Windows.
/srv/
To configure these settings, click Configuration in the left pane to display the Configuration tab. If
it’s not expanded, click Management Zone Settings, then click Device Management > Preboot
Services to display the Preboot Services page.
For more information, see Section 1.3, “Preboot Services Functionality,” on page 19.
Overview 15
1.1.5 Setting Up Devices to Use Imaging Bundles
In order for a device to automatically use an assigned Imaging bundle, you must complete two tasks:
“Setting Up the Device to Apply the Bundle” on page 16
“Assigning a Bundle” on page 16
Setting Up the Device to Apply the Bundle
Preboot Services utilizes PXE and other boot mechanisms and media to trigger the imaging work.
For information, see Section 2.3, “Setting Up the Preboot Services Methods for ZENworks
Imaging,” on page 46.
Assigning a Bundle
You can assign an Imaging bundle to devices, their parent folder, or a device group.
The following paths represent many of the methods for assigning bundles to devices, or devices to
bundles:
novdocx (en) 16 April 2010
“To Device Folders” on page 16
“To Device Groups” on page 16
“To Individual Devices” on page 16
To Device Folders
Click Devices > select the check box next to a folder, then click Action > Assign Bundle.
Where you have selected the Servers and Workstations folders’ check boxes, you can assign
bundles to all of the devices contained under the Servers and Workstations folders.
Click Devices > select the check box next to Servers, then click Action > Assign Bundle.
You can assign bundles to all of the devices in the Servers folder.
Click Devices > select the check box next to Workstations, then click Action > Assign Bundle.
You can assign bundles to all of the devices in the Workstations folder.
To D ev i ce Gr o up s
Click Devices > Servers > select the check boxes next to one or more server groups, then click
Action > Assign Bundle.
You can assign bundles to all servers that are members of the selected server groups.
Click Devices > Workstations > select the check boxes next to one or more workstation groups,
then click Action > Assign Bundle.
You can assign bundles to all workstations that are members of the selected workstation
groups.
To Individual Devices
Click Devices > Servers > select the check boxes next to one or more servers, then click Action
> Assign Bundle.
You can assign bundles to all selected servers.
16 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Click Devices > Workstations > select the check boxes next to one or more workstations, then
click Action > Assign Bundle.
You can assign bundles to all selected workstations.
Click Devices > Servers > select a server, then click Advanced (in Imaging Work on the
Summary tab).
You can assign a specific bundle to the server.
Click Devices > Workstations > select a workstation, then click Advanced (in Imaging Work on
the Summary tab).
You can assign a specific bundle to the workstation.
Click Bundles > Servers > select the check box next to a server, then click Action > Assign
Bundle.
You can assign multiple bundles to the server.
Click Bundles > Workstations > select the check box next to a workstation, then click Action >
Assign Bundle.
You can assign multiple bundles to the workstation.
Click Bundles > select the check boxes next to one or more bundle names, then click Action >
Assign Bundle to Device.
You can assign the selected bundles to the devices that you select in the wizard.
novdocx (en) 16 April 2010
1.2 What Is the Preboot Execution Environment (PXE)?
The following sections provide information on using PXE in Configuration Management:
Section 1.2.1, “Understanding How Preboot Services Uses PXE,” on page 17
Section 1.2.2, “Understanding the ZENworks NBPs,” on page 17
Section 1.2.3, “Preparing to Use PXE,” on page 19
1.2.1 Understanding How Preboot Services Uses PXE
PXE uses DHCP (Dynamic Host Configuration Protocol) and TFTP (Trivial File Transfer Protocol)
to locate and load bootstrap programs from the network. The PXE environment is loaded from the
BIOS on the NIC.
Preboot Services uses PXE to discover if there is Preboot Services work specified for a device and to
provide the device with the files necessary to execute the assigned work.
Using Preboot Services, you can automatically place an image on a device, even if the device’s hard
disk is blank. You do not need to use the CD or DVD, or a ZENworks partition on the device.
1.2.2 Understanding the ZENworks NBPs
The Intel PXE specification defines mechanisms and protocols that allow PXE devices to use their
network interface cards (NICs) to find bootstrap programs located on network servers. In the PXE
specification, these programs are called Network Bootstrap Programs (NBPs).
Overview 17
NBPs are analogous to the bootstrap programs found in the Master Boot Records (MBRs) of other
boot media, such as hard drives, floppy disks, CDs, and DVDs. The purpose of a bootstrap program
is to find and load a bootable operating system. MBRs on traditional boot media accomplish this by
locating the necessary data on their respective media. NBPs accomplish this by using files found on
network servers, usually TFTP servers.
ZENworks Preboot Services uses two separate NBPs working together:
“nvlnbp.sys” on page 18
“pxelinux.0” on page 18
nvlnbp.sys
This NBP has the following responsibilities:
Detect various SMBIOS parameters and local hardware
Read the ZENworks identity information from the hard drives
Communicate with novell-zmgprebootpolicy to determine if there is any preboot work
applicable to the device
novdocx (en) 16 April 2010
Present and manage the Novell Preboot Services Menu
If necessary, launch
pxelinux.0
to execute the assigned preboot work
pxelinux.0
The primary purpose of this NBP is to load the operating system that is required to execute the
assigned preboot work.
The
pxelinux.0
Although
pxelinux.0
file is a modified version of part of an open source project called syslinux.
is primarily a Linux loader, it is capable of loading other operating systems.
It operates by using configuration files located on a TFTP server to provide boot instructions. The
various
pxelinux.0
Imaging Server in the
directory on Windows, where
configuration files used by Configuration Management can be found on your
/srv/tftp
directory on Linux or the
%ZENWORKS_HOME%
is the complete path of the ZENworks installation
%ZENWORKS_HOME%\share\tftp
directory.
In Configuration Management, when PXE devices are assigned preboot work, they are also told
pxelinux.0
which
the Novell Preboot Services Menu, each menu option corresponds to a
configuration file they should use to execute that work. Similarly, when using
pxelinux.0
configuration
file. For more information, see Section 2.4.4, “Editing the Novell Preboot Services Menu,” on
page 71.
For more information on
pxelinux.0
and its configuration files, see the syslinux home page (http:/
/syslinux.zytor.com/pxe.php).
For a copy of the Novell modifications to the syslinux open source project, see Novell Forge (http://
forge.novell.com).
18 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
1.2.3 Preparing to Use PXE
Before you can use Preboot Services with PXE, you need to do the following:
1. Install Novell ZENworks 10 Configuration Management SP3. For more information, see the
ZENworks 10 Configuration Management Installation Guide.
2. Enable PXE on your Configuration Management devices. For more information, see
Section 2.7, “Enabling PXE on Devices,” on page 96.
3. Have a standard DHCP server, either on your ZENworks Imaging Server or on another network
server where ZENworks is not installed. For more information, see “Configuring LAN
Environments for Preboot Services” on page 64.
NOTE: The PXE boot option is not supported on the XEN systems. Consequently, ZENworks
Imaging and ZENworks Third-Party Imaging in the PXE mode is not available on the XEN systems.
1.3 Preboot Services Functionality
Review the following sections to understand Preboot Services functionality:
novdocx (en) 16 April 2010
Section 1.3.1, “Imaging Bundles,” on page 19
Section 1.3.2, “Novell Preboot Services Menu,” on page 22
Section 1.3.3, “Non-Registered Device Settings,” on page 22
Section 1.3.4, “Device Imaging Work Assignment,” on page 23
Section 1.3.5, “Server Referral List,” on page 25
Section 1.3.6, “Intel Active Management Technology (AMT),” on page 26
1.3.1 Imaging Bundles
Configuration Management uses Imaging bundles to apply Preboot Services work to devices. For
example, Imaging bundles can contain tasks, such as restoring an image, that are performed at the
time a device boots.
In order for a device to utilize an Imaging bundle, the bundle must be assigned to the device, its
group, or its folder.
The available Imaging bundles are:
“Empty Bundle” on page 20
“Imaging Script Bundle” on page 20
“Multicast Image Set Bundle” on page 20
“Third-Party Image Bundle” on page 20
“ZENworks Image Bundle” on page 21
Overview 19
Empty Bundle
This bundle contains no initial tasks. You can quickly create this bundle without performing all of
tasks in the Create New Bundle Wizard. Later, you can edit its details to add assignments, actions,
and so forth. For example, you could create an empty bundle, then in the bundle’s properties add the
Linked Application Bundle action as its only action.
Imaging Script Bundle
Allows you to write a custom Linux script that is executed on PXE-enabled devices. This provides
detailed control over ZENworks imaging operations, as well as most Linux-based preboot tasks.
For more information, see Section 3.3, “Configuring Imaging Script Bundles for ZENworks
Imaging,” on page 132.
Multicast Image Set Bundle
Specifies an image that can be sent using the multicast protocol. This bundle allows you to send an
existing image to a large number of devices in a single operation. It is ideal for labs, classrooms, and
staging areas.
novdocx (en) 16 April 2010
For more information, see Section 1.5.6, “Multicasting Device Images,” on page 37 and Section 3.2,
“Multicasting Images for ZENworks Imaging,” on page 122.
Benefits
You can image multiple devices with the least amount of overhead. Devices to be imaged can have a
variety of operating systems installed on them, or even no operating system installed.
Using the multicast capabilities of your network, you minimize network traffic by sending the image
file across the network once for all devices to be imaged, rather than individually per device.
Limitations
Using the same image on multiple devices means they all have the same network identities.
However, you can install the ZENworks Configuration Management Imaging Agent (novell-ziswin)
on these devices prior to performing the multicast, because this agent saves each device’s network
identity settings and restores them after the multicast image is applied.
Third-Party Image Bundle
Allows you to specify the third-party images to be restored on a device. ZENworks supports:.
Microsoft* ImageX that uses the WIM image file format and WinPE as the distro.
Microsoft* ImageX that uses the WIM image file format and WinPE as the distro. The distro is
available as WAIK (Windows Automated Installation Kit) that can be downloaded from
Microsoft Download Center Web site (http://www.microsoft.com/downloads/
details.aspx?FamilyID=c7d4bc6d-15f3-4284-9123-679830d629f2&displaylang=en) or
through Microsoft’s Business Desktop Deployment (BDD).
Symantec* Ghost* that uses the GHO image file format and WinPE as the distro
The ZENworks Third-Party Imaging supports only PXE as the boot mechanism.
20 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
For more information, see Section 3.1.1, “Using ZENworks Control Center for Imaging,” on
page 99.
ZENworks Image Bundle
Lists one or more ZENworks images that can be restored on a computer. This bundle allows you to
quickly define simple image restoration operations.
For more information, see Section 3.1.1, “Using ZENworks Control Center for Imaging,” on
page 99.
Scope
You can restore the image of hard disks, specific add-on images, and file sets of a device.
Boot Manager Limitation
If the device you want to image has an unsupported boot manager running, such as System
Commander, you must disable or remove it before attempting to image those devices. This is
because boot managers create their own information in the MBR and overwrite the ZENworks boot
system, preventing ZENworks imaging from being performed.
novdocx (en) 16 April 2010
Base Images
A base image contains descriptions of all partitions and files on a hard drive. When it is restored, all
existing partitions are deleted, new partitions are created from the descriptions in the base image,
and all files are restored from the image.
Base images are created by taking an image of a device. You can use an option in ZENworks
Control Center or you can use imaging commands at the imaging maintenance mode prompt to
create a base image.
In ZENworks Configuration Management, image files are automatically saved to the following
location, which cannot be changed:
Windows:
%ZENWORKS_HOME\work\content-repo\images
where %ZENWORKS_HOME% is the complete path of the ZENworks installation directory.
Linux:
/var/opt/novell/zenworks/content-repo/images
If you need more disk space for large imaging files than is available in your current content
repository location, you can change this location to a different partition. For more information, see
“Content Repository” in the ZENworks 10 Configuration Management System Administration
Reference.
Add-On Images
These images are a collection of files added non-destructively to existing partitions. The existing
partitions and files are left intact, except for any files that the add-on image might update.
Add-on images allow you to customize a device after a base image is restored. This allows you to
use a base image for multiple purposes.
You can create add-on images by using the Image Explorer utility.
Overview 21
1.3.2 Novell Preboot Services Menu
Where PXE is enabled on a device, the Novell Preboot Services Menu can be displayed during the
boot process. The following menu choices are displayed on the menu:
Start ZENworks Imaging: Executes the effective Preboot Services imaging bundle.
WinPE Maintenance Mode: Loads WinPE and starts the ZENworks Third-Party Imaging
utility. You can use the utility to perform the third-party imaging operations.
Start ZENworks Imaging Maintenance: Displays the imaging maintenance mode prompt,
where you can execute imaging commands.
Disable ZENworks Partition: Prevents an existing ZENworks partition from being used
during booting to execute the assigned Imaging bundles.
Enable ZENworks Partition: Allows an existing ZENworks partition to be used during
booting to execute the effective Imaging bundle.
Exit: Resumes normal booting of the device.
You can use ZENworks Control Center to configure whether this menu should be displayed on a
PXE-enabled device by selecting one of the following options:
novdocx (en) 16 April 2010
Always Show Imaging Menu
Never Show Imaging Menu
Show Imaging Menu if CTRL+ALT Is Pressed
For the procedures in configuring the menu’s display, see Section 2.5.1, “Configuring Novell
Preboot Services Menu Options,” on page 74.
1.3.3 Non-Registered Device Settings
Devices that are new to the Management Zone and have received their first image need certain IP
configuration information to successfully access the network and network services. You can use
Preboot Services to automatically name your non-registered devices, using such criteria as prefixes,
BIOS information (like asset tags or serial numbers), DNS suffixes, and you can set up DHCP or IP
addresses.
For example, the device needs a unique IP address and the address of at least one DNS name server.
In many networks, this information is distributed through the DHCP services, but it can also be
configured through the default Preboot Services configuration settings in ZENworks Control Center.
After a device has registered with ZENworks, its configuration is set and the non-registered device
settings in the Management Zone no longer apply to it, because the ZENworks server now knows its
identity. Whether it becomes a member of the zone or continues to be a non-registered device
depends on whether the image applied to the device contains the ZENworks Configuration
Management Imaging Agent (novell-ziswin).
The settings that can be adjusted for a Management Zone are:
DNS suffix: Provides a suffix for all of your devices’ names. For example, provo.novell.com.
Workgroup: The Windows workgroup that you want the device to be a member of.
Name Servers: Controls which DNS servers a device uses. You can specify multiple DNS
name servers.
22 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Device Name: Configured device names can include a prefix, the BIOS asset tag, the BIOS
serial number, or none of these.
IP configuration: For the IP configuration, you can specify to use DHCP or a specific IP
address. If you select to use IP addresses, you can provide a range of addresses in a list, or you
can specify certain IP addresses. As devices are registered, they assume one of the available
addresses. For IP addresses, you can also specify a subnet mask and a default gateway.
For the procedures in configuring defaults for non-registered devices, see Section 2.5.2,
“Configuring Non-Registered Device Settings,” on page 75.
1.3.4 Device Imaging Work Assignment
You can determine what imaging work is to be performed on a device when it boots, based on a set
of hardware rules. This configuration section lets you specify a particular bundle for each set of
hardware rules. The Custom Hardware Types section allows you to provide specific data for a
Hardware Type hardware rule option.
Rules and custom types configured here are applied globally to all non-managed devices. You can
also apply them to managed devices in the Management Zone by assigning those devices to the
bundle that is selected for the rule. Only those devices that exactly match the rule and its custom
types have the assigned bundle applied to them when they boot.
novdocx (en) 16 April 2010
“Hardware Rules” on page 23
“Custom Hardware Types” on page 24
“Allowing Overwrites” on page 25
For the procedures in configuring work assignment rules, see Section 2.5.3, “Configuring Device
Imaging Work Assignments,” on page 79.
Hardware Rules
You can set up hardware-based rules for your Imaging bundles. Work assignment rules are used to
apply bundles to devices with specific hardware, or to match a broad set of hardware requirements.
For example, you can create a rule that applies a bundle to any device with a specific MAC address
or BIOS serial number. Rules like this can only match to a single device. On the other hand, you can
create a rule that applies to any device with at least 512 MB of RAM and 150 GB of hard drive
space.
A work rule is comprised of filters that are used to determine whether a device complies with the
rule. The rules use logic to determine whether a device meets the requirements for applying the
Imaging bundle. The AND and OR logical operators are used for creating complex filters for the
rule.
When a device is seeking work to be done, it scans the rules until it finds a rule where all of the
rule’s filters match the device, then executes the bundle assigned to the rule.
Filter information that you can provide:
Device component: Any of the following:
BIOS Asset Tag
BIOS Serial Number
Overview 23
BIOS Version
CPU Chipset
Hard Drive Controller
Hard Drive Size
Hardware Type
IP Address
MAC Address
Network Adapter
Product Name
RAM
Sound Card
System Manufacturer
Video Adapter
Relationship: This defines the relationship for a filter between the Device component field and
the value you specify for it.
Possibilities for the Hard drive size and RAM fields:
novdocx (en) 16 April 2010
< (less than)
> (greater than)
= (equal to)
>= (greater than or equal to)
<= (less than or equal to)
<> (not equal to)
Possibilities for all other device components:
Contains
Equal To
Starts With
Ends With
Component Value: This corresponds to the match you want for the component. For example,
you select RAM (in MB) for the filter and enter 512 for its value. Then, the relationship you
select determines whether it’s less than, less than or equal to, equal to, not equal to, greater than
or equal to, or just greater than 512 MB.
You can have multiple filters and sets of filters in a single rule, using the AND and OR operators,
and you can have multiple rules associated with the same Imaging bundle. This allows you to
specify exactly which can receive a particular Imaging bundle.
Custom Hardware Types
Custom hardware types enable you to include any devices matching your custom type to have the
bundle assigned to the hardware rule applied to them when the devices boot. For example, you can
create a rule that applies the bundle to any device that is a laptop by entering the applicable string as
a custom hardware type, selecting Hardware Type in the Rule Construction dialog box, then
selecting your custom type.
The Hardware Type option does not display in the Rule Construction dialog box until at least one
custom type has been configured.
24 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Allowing Overwrites
Select the Allow Preboot Services to Overwrite Existing Files when Uploading check box if you
.zmg
want existing
files to be overwritten by a newer version when the image is taken.
1.3.5 Server Referral List
When a PXE device boots, it makes a broadcast request on the network for PXE services. The
ZENworks Proxy DHCP server (novell-proxydhcp) responds to this request with information that
includes the IP address of an Imaging Server where the device can send requests for assigned
imaging work.
Because PXE devices can exist in an environment with both newer and older ZENworks systems
running concurrently, the device can fail to determine its assigned imaging work if it cannot find the
Imaging Server for its own ZENworks version.
In ZENworks Configuration Management, devices can exist in multiple Management Zones. It is
essential that the PXE device contact PXE services assigned to its home zone so that it can correctly
determine if there is any imaging work assigned to it. When there is only a single Management
Zone, this is easy to do because all Proxy DHCP servers provide addresses to services that belong to
the same zone. Any device can request imaging work from any Imaging Server in the same zone and
get the same response.
novdocx (en) 16 April 2010
The PXE device’s initial request for PXE services is sent as a broadcast to the network, and all
Proxy DHCP servers respond with information pertaining to their respective zones (in ZENworks
Configuration Management and ZENworks Linux Management) or Proxy DHCP servers in their
®
trees (in traditional ZENworks versions using Windows or NetWare
Imaging Servers). Because it
is impossible to determine which Proxy DHCP server responds first (if multiple Proxy DHCP
servers respond), or which server’s response is used by the device, it is impossible to ensure that
each PXE device will contact servers in its home zone or tree.
For a ZENworks environment that has PXE services, the Server Referral List configuration section
provides a method for getting PXE devices to connect with their proper Imaging Servers. Server
referral lists are only used by PXE devices, and in ZENworks Configuration Management only one
Management Zone needs to have an active Proxy DHCP server and server referral list. Because you
can only have one referral list active in a network segment, if you have ZENworks Linux
Management running with a referral list configured, you’ll need to disable the Proxy DHCP service
for Linux Management. This allows the Configuration Management referral list to be used by all
PXE devices.
A server referral list allows you to ensure that all devices contact their home zone or tree for device
imaging work assignments. The list should contain the IP address of an Imaging Server in each
known Management Zone or older ZENworks system’s tree. When a device requests device imaging
work from a server, the server first determines if the device belongs to the same zone or tree as the
server. If it does not, that server refers the request to each server in its server referral list until it finds
the device’s home zone or tree. The device is then instructed to send all future requests to the correct
novell-proxydhcp.
For the procedures in configuring referral lists, see Section 2.5.4, “Configuring the Server Referral
List,” on page 90.
Overview 25
1.3.6 Intel Active Management Technology (AMT)
The Intel AMT functionality allows you to accurately identify devices, even if they have had
physical drive replacements. This provides ZENworks Preboot Services with persistent device
identification by providing ZENworks with nonvolatile memory for storing the unique device
identity.
With AMT and Preboot Services, if a device has a new, unformatted hard drive, ZENworks can
instantly and accurately identify the device and apply the appropriate Imaging bundle. If a device’s
hard drive is inactive or its drive is replaced, ZENworks can automatically identify the device in a
preboot environment and provide the appropriate ZENworks-created image during a system rebuild.
AMT with ZENworks also provides easier hardware upgrading capability. For example, to upgrade
applications, some of your device hardware might not meet the minimum requirements. With AMT
and Preboot Services, as soon as the hard drives are replaced and before any agents or operating
systems are installed, you can continue to assign Imaging bundles using the device’s ZENworks
identity without having to re-register the device.
novdocx (en) 16 April 2010
If you are using Intel AMT, support for it should be enabled in the
zmgprebootpolicy.conf
For more information on Intel AMT, see the Intel Web site (http://www.intel.com/technology/
platform-technology/intel-amt/).
file.
novell-
1.4 The Preboot Services Processes
The following sections explain how the Preboot Services processes work:
Section 1.4.1, “A Typical Preboot Services Operation,” on page 26
Section 1.4.2, “Illustrating the Preboot Services Processes,” on page 27
1.4.1 A Typical Preboot Services Operation
A typical Preboot Services operation flows as follows:
1. An Imaging bundle is created in ZENworks Control Center and assigned to a PXE-enabled
device.
2. The PXE-enabled device starts to boot.
3. The device sends a DHCP discovery request to determine the IP address of the Preboot
Services Imaging Server.
4. The DHCP server responds with an IP address for the device to use.
5. Novell-proxydhcp responds with the IP addresses of the TFTP server, as well as the filename of
the Preboot Services bootstrap program (
nvlnbp.sys
).
6. The PXE device downloads the Preboot Services bootstrap program using novell-tftp.
7. After the Preboot Services bootstrap program is downloaded and executed, the device checks
novell-zmgprebootpolicy to see if there is any imaging work to do.
8. If there is imaging work to do (as contained in an Imaging bundle that is assigned to the
device), the device performs the following task
ZENworks Imaging: Downloads the Configuration Management imaging environment
from the server so that the it can be booted to Linux.
26 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Third-Party Imaging: Downloads the WinPE environment from the server.
9. Any imaging tasks contained in the Imaging bundle are performed.
10. If there are no imaging tasks to perform, files are not downloaded and the device proceeds to
boot to its operating system.
In addition to using PXE for automation, you can also execute Preboot work manually using one of
the following:
Novell Preboot Services Menu (if enabled for the device)
Preboot Services bootable CD or DVD
ZENworks partition
For more information, see Section 3.1.2, “Using the Command Line for ZENworks Imaging,” on
page 107.
1.4.2 Illustrating the Preboot Services Processes
The following illustrations show the interaction between a Preboot Services (PXE) device and a
Preboot Services Imaging Server, starting when the PXE device is turned on and begins to boot, and
ending when imaging work begins on that device.
novdocx (en) 16 April 2010
The following example assumes that the devices and Imaging Servers are in the same network
segment.
“Phase 1: Beginning the Process” on page 27
“Phases 2 through 8: Continuing the Process” on page 30
Phase 1: Beginning the Process
Depending on whether novell-proxydhcp is configured on the same server as the standard DHCP
server or on a different server, the imaging process begins differently. The following sections
illustrate how the process begins for each configuration, then the phases illustrated in “Phases 2
through 8: Continuing the Process” on page 30 are the same for them.
“Standard DHCP and Novell Proxy DHCP Configured on Separate Servers” on page 27
“Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part A” on page 28
“Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part B” on page 29
Standard DHCP and Novell Proxy DHCP Configured on Separate Servers
For this example, the DHCP server and the Preboot Services Imaging Server are two separate
servers on the network.
Overview 27
Figure 1-1 DHCP Configuration on Separate Servers
2
Imaging
Server
PXE Device
novell-proxydhcp
novell-tftp
novell-pbserv
PXE
BIOS
Data
Model
nvlnbp.sys
2
1
DHCP
Request
Network
DHCP
novell-zmgprebootpolicy
port
67
port
68
port
68
IP Configuration
novdocx (en) 16 April 2010
Processes:
1. When the device boots, the PXE BIOS issues a DHCP request with PXE extensions. The
request is broadcast on port 67.
2. The DHCP server responds with IP configuration information on port 68, and the Proxy DHCP
server responds on port 68 with the name of the bootstrap program (
address of the TFTP service or daemon where it can be found.
3. Continue with “Phases 2 through 8: Continuing the Process” on page 30.
Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part A
For this example, the DHCP server and the Preboot Services Imaging Server are configured on the
same server on the network. See “Standard DHCP and Novell Proxy DHCP Configured on the Same
Server: Part B” on page 29 for the second part of this example.
nvlnbp.sys
) and the IP
28 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Figure 1-2 DHCP Configuration on the Same Server, Part A
2
Imaging
Server
PXE Device
novell-proxydhcp
novell-tftp
novell-pbserv
PXE
BIOS
Data
Model
1
DHCP
Request
Network
DHCP
novell-zmgprebootpolicy
port
67
port
68
IP Configuration &
Tag 60: PXEClient
Imaging
Server
PXE Device
novell-proxydhcp
novell-tftp
novell-pbserv
PXE
BIOS
Data
Model
nvlnbp.sys
2
1
DHC P
Request
Network
DHCP
novell-zmgprebootpolicy
port
4011
port
68
novdocx (en) 16 April 2010
Processes:
1. When the device boots, the PXE BIOS issues a DHCP request with PXE extensions. The
request is broadcast on port 67.
2. The DHCP server responds with IP configuration information on port 68, including tag 60 for
PXEClient, which indicates that novell-proxydhcp is running on the same server.
Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part B
Figure 1-3 DHCP Configuration on the Same Server, Part B
Overview 29
Processes:
3
1
2
Imaging
Server
PXE Device
Data
Model
novell-proxydhcp
novell-zmgprebootpolicy
novell-tftp
novell-pbserv
nvlnbp.sys
nvlnbp.sys
PXE BIOS
1. When the device sees tag 60 in the DHCP response, the PXE BIOS reissues the DHCP request
on port 4011.
2. The Proxy DHCP server responds on port 68 with the name of the bootstrap program
(
nvlnbp.sys
) and the IP address of the TFTP service or daemon where it can be found.
3. Continue with “Phases 2 through 8: Continuing the Process” on page 30.
Phases 2 through 8: Continuing the Process
The following sections explain how the Preboot Services process continues after Phase 1:
“Phase 2” on page 30
“Phase 3” on page 31
“Phase 4” on page 31
“Phase 5” on page 32
“Phase 6” on page 32
novdocx (en) 16 April 2010
“Phase 7” on page 33
“Phase 8” on page 33
Phase 2
Figure 1-4 Phase 2 of the Preboot Services Process
Processes:
1. The PXE BIOS requests
2. The TFTP server sends
3. The PXE device loads
nvlnbp.sys
nvlnbp.sys
nvlnbp.sys
from the TFTP server.
to the PXE device.
into memory.
30 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
Loading...