Fundamentals of ZENworks Configuration Management Imaging Lecture

Transcription

1 Fundamentals of ZENworks Configuration Management Imaging Lecture ZEN01 Novell Training Services ATT LIVE 2012 LAS VEGAS

2 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 ( for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals. Copyright 2012 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., has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page ( and one or more additional patents or pending patent applications in the U.S. and in other countries. Novell, Inc. 404 Wyman Street, Suite 500 Waltham, MA U.S.A. Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page ( Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list ( Third-Party Materials All third-party trademarks are the property of their respective owners. 2

3 SECTION 1 Fundamentals of ZENworks Configuration Management Imaging Novell Training Services (en) 15 April 2009 Introduction This class is designed to give you a solid overview of the imaging feature and its capabilities of ZENworks Configuration Management (ZCM). This class will explain ZCM imaging using both lecture and hands-on exercises. Imaging was first introduced with ZENworks for Desktops version 3. This feature has matured and become more flexible and extensible with each major version. ZCM imaging provides the most full-featured imaging solution for Windows workstations on the market today. 1

4 Novell Training Services (en) 15 April 2009 The following objectives are covered in this course: Objective 1: Understanding the ZCM Imaging Environment on page 4 Our coverage of ZCM imaging will begin with an overview of the imaging environment. This is designed to cover the reasons why ZCM Imaging is a superior solution and understand the services that comprise ZCM Imaging. Objective 2: Introduction to the ZENworks Control Center (ZCC) on page 16 ZCM uses a web-based management console called the ZENworks Control Center (ZCC). This console is used to configure the imaging capabilities of ZCM. It is important to get a feel for the ZCC prior to using it to configure imaging operations. Objective 3: Creating Multicast Imaging Bundles on page 30 ZCM imaging provides a built-in mechanism for deploying one or more images to multiple workstations at one time. This can be accomplished by creating and configuring Multicast Imaging Bundles. 2

5 Novell Training Services (en) 15 April 2009 Objective 4: Performing Manual Imaging Operations on page 44 There are situations when it is beneficial to be able to take or restore images manually. This objective explains those situations and how to perform manual imaging operations. Objective 5: Performing Basic Troubleshooting of ZCM Imaging on page 58 This objective covers some basic troubleshooting steps to follow if you can not successfully perform imaging operations on workstations. 3

6 Novell Training Services (en) 15 April 2009 Objective 1 Understanding the ZCM Imaging Environment This objective will cover the following topics: Why use ZENworks Configuration Management imaging? on page 5 Services that comprise the ZCM Imaging Environment on page 7 Determining if ZCM Imaging Services are running on page 11 4

7 Why use ZENworks Configuration Management imaging? Novell Training Services (en) 15 April 2009 Many Novell customers already own ZENworks Desktop Management 7.x or ZCM 10. However, some of these same customers use another workstation imaging solution like Ghost. If you have ZCM you do not need to spend the annual renewal subscription costs for another imaging product; you already have the best of breed imaging solution built into something you already own. All configuration data required to do ZCM Imaging is stored in the central ZENworks Data Store. This means that as a support person you can configure imaging operations to occur on any device right from your desk. You don t have to go visit the user s desktop and slap in a DVD to image their machine. Plus ZCM employs a user friendly web-based management console to configure all capabilities of ZCM. This console is called the ZENworks Control Center (ZCC) and can be launched using either Internet Explorer version 7.x or FireFox version 2.x. If you have ZCM version to 10.3.x, you can use Internet Explorer version 8 and Firefox version 3. For ZCM 11.0 and 11.1 Internet Explorer version 8 is supported along with FireFox versions , 3.5.x, 3.6.x, 4.0.x, and 5.0.x. Internet Explorer version 9 is not yet supported, but support is targeted for the ZCM 11.2 release. 5

8 Novell Training Services (en) 15 April 2009 One of the biggest benefits of ZCM Imaging from the administrator s standpoint is the extensibility of ZCM Imaging. ZCM Imaging is not tied to the limitations of MS DOS as are other vendor s imaging solutions. ZCM Imaging is based on the SLES 11 SP2 distribution. The extensibility of the ZCM Imaging environment can be seen in the following capabilities: NOTE: ZCM 10.3.x releases of the ZENworks Imaging Distro are based on the SLES 10 SP3 distribution ZENworks Scripted Imaging gives the administrator the ability to address any imaging challenge by leveraging the rich scripting capabilities of bash. Beginning with ZCM 10.1, ZCM Imaging supports using Microsoft s WinPE environment to image Vista and Windows 7 workstations. ZCM s Multicast Image bundle type allows the administrator to multicast one or many images to multiple workstations at one time. Lastly, ZCM Imaging can distribute base images or add-on images. Laying down a base image is a destructive process which creates a new partition and lays down a bootable operating system. Add-on images add content to the existing partition. 6

9 Services that comprise the ZCM Imaging Environment Novell Training Services (en) 15 April 2009 The following services must be available to the workstations on a given subnet in order to support all aspects of ZCM Imaging: DHCP Service - This is not specific to ZENworks but is required in order to do Preboot Imaging work. PXE booting a workstation requires that DHCP be implemented in your environment. The PXE boot process allows you to control a device prior to the booting of the operating system installed on that device. Proxy DHCP Service - In order to successfully PXE boot a workstation certain additional tag information must be provided to the workstation that is not provided by the DHCP Service. TFTP Service - During the PXE boot process a small UNDI LAN Driver referred to as the PXE Client is downloaded to the workstation from the ZCM Server hosting the TFTP Service. The TFTP Server will also provide the ZENworks Imaging Distro to the workstation if the Preboot Process determines that the workstation has imaging work to do. Preboot Policy Service - The Preboot Policy Service acts as a protocol converter between the PXE Client and the Preboot Server. Preboot Service - The name for this service is a bit misleading. This service is active during both the preboot phase and the actual imaging process. 7

10 Novell Training Services (en) 15 April 2009 ZCM s Preboot Services software is designed to be deployed in your environment without making a single modification to your existing DHCP Server. However if both the DHCP Service and the Proxy DHCP Service are running on the same server a change must be made to the DHCP Service. For instance, this would be case in the event that a SLES 11.x server provided both DHCP and ZCM back-end services. If this is the case, then the Vendor-class-identifier tag must be implemented in your DHCP Server. The value for this tag must be PXEClient WARNING: When implementing this tag on a SLES 10.x server be sure to include the double quotes around PXEClient. If you don t the DHCP Services will fail to start. If however implementing this tag on SLES 11 server the double quotes are not used. The Proxy DHCP Server will provide the following information to the workstation during the Preboot Process: the IP address of the TFTP Service the name and location of the file that is the PXE Client. In ZCM the PXE Client is implemented in a file named nvlnbp.sys. This file is downloaded from the TFTP Service during the PXE boot process. 8

11 Novell Training Services (en) 15 April 2009 The TFTP Service stores the following files that are important to the Preboot and the imaging processes: nvlnpb.sys - is the PXE Client which does a basic hardware scan of the workstation and gathers up any ZCM Zone identity information. This information is sent through the Preboot Policy Server to the Preboot Server so that the Preboot Server can determine if there is any imaging work to do. pxelinux.0 - is the ZCM Imaging Distro s boot loader. If there is imaging work to do, pxelinux.0 will download the rest of the ZCM Imaging distro. pxemenu.txt - is the default PXE menu that is displayed by pxelinux.0 when the user presses the Ctrl-Alt keys during the preboot process. The Preboot Policy Service acts as an imaging client to the Preboot Server on behalf of the workstation with imaging work to do. The Preboot Service only speaks TCP. The PXE Client speaks only UDP. Therefore, the Preboot Policy Service converts UDP traffic to TCP traffic and TCP traffic to UDP traffic. 9

12 Novell Training Services (en) 15 April 2009 The Preboot Service is responsible for receiving the contents of a workstation s hard drive and creating a zmg file in the file system of the Primary Server, and to send zmg image files from its file system down to the workstation to be restored. The Preboot Server is also responsible for requesting that Zone configuration information be analyzed to determine if the device has any imaging work to do. 10

13 Determining if ZCM Imaging Services are running Novell Training Services (en) 15 April 2009 If you are running DHCP Services on a SLES 10.x server you can determine if DHCP is up and running by completing the following: 1. Right-click the desktop of the SLES server where DHCP Services should be running and select Open Terminal 2. From the command prompt enter: su You will be prompted for the root user s password. 3. From the command prompt enter: /etc/init.d/dhcpd status If DHCP Services are up, a status of running will be displayed. If the status is not running, the start or restart parameters can be used on the above command. 11

14 Novell Training Services (en) 15 April 2009 All the commands to check the status of, start, or stop any of the ZCM Imaging related services can be found in the /etc/init.d directory on your ZCM Primary Server. The graphic above shows the syntax of the commands necessary to manage all the ZCM Imaging related services. NOTE: When installed on Windows Server platforms all the ZCM Imaging-related Services are controlled through the Windows Services Applet. 12

15 Novell Training Services (en) 15 April 2009 The examples above show how to determine if the Proxy DHCP Service is running and how to start the TFTP Service. You can see the status of all ZCM services including the imaging services by issuing the command: /opt/novell/zenworks/bin/novell-zenworks-configure -c SystemStatus The output of the novell-zenworks-configure command for ZCM 10.x is shown in Figure 1-1 on page 14. The output from ZCM 11 s novell-zenworks-configure command is shown in Figure 1-2 on page

16 Novell Training Services (en) 15 April 2009 Figure 1-1 novell-zenworks-configure command in ZCM 10.x 14

17 Figure 1-2 novell-zenworks-configure from ZCM 11.x Novell Training Services (en) 15 April

18 Novell Training Services (en) 15 April 2009 Objective 2 Introduction to the ZENworks Control Center (ZCC) Before understanding how to configure ZCM for imaging operations you must first obtain some background on the management console used to configure imaging information in the Zone. The tool is called the ZENworks Control Center (ZCC). The following topics are presented: Understanding the structure of the ZCC on page 17 Introduction to Imaging Bundles on page 22 Configuring Imaging related Zone Settings on page 26 16

19 Understanding the structure of the ZCC Novell Training Services (en) 15 April 2009 First you must understand a few terms that are related to the ZCC: ZCC - Web-based management console that is used to configure all aspects of ZCM. Zone - During the installation of the first Primary Server the ZCM Zone is defined. The zone is the administrative unit managed with the ZCC. All policies, bundles, devices, and groups are objects defined in the zone. The zone can be thought of as being roughly equivalent to an edirectory tree. Image Bundles - Imaging Bundles describe the type of imaging work that should be done to a device. Imaging Bundles come in different types. The Imaging bundle may specify one or more image files (.zmg files) that should be restored to a device, or they can specify that a bash script should be executed on the device. Image Bundles can also specify a list of image files that should be multicast out to multiple machines. 17

20 Novell Training Services (en) 15 April 2009 In order to configure imaging work in the Zone, the administrator must launch the ZCC and authenticate to the Zone. Launch either FireFox or Internet Explorer and enter the following URL: <ZCM-server> can be either the IP address or DNS name of a Primary Server. If your organization has implemented a multi-zone ZCM environment, the URL of the Primary Server dictates which Zone is being managed. A Primary Server can be in one and only one Zone. So whichever Primary Server the ZCC is pointed to, is the Zone whose information is being managed. 18

21 Novell Training Services (en) 15 April 2009 In the example pictured above, the Zone that will be managed (after the administrator authenticates) is the Zone that contains the Primary Server whose DNS Name is sles1164b.digitalairlines.com. When the URL is entered into the browser, the browser is automatically redirected to the ZCC Authentication Screen. 19

22 Novell Training Services (en) 15 April 2009 The graphic above highlights the upper left pane of the ZCC. This pane contains the links that list the major areas of management and configuration within the Zone. 20

23 After selecting an area of ZCM management/configuration in the upper left pane, the specific types of tasks that can be performed within that area of management are displayed in the lower left pane. In the above example, Bundle management was chosen in the upper left pane and the different bundle management tasks are shown as links in the lower left pane. Novell Training Services (en) 15 April 2009 The ZCC keeps track of those objects you create in the Zone. They are shown as Frequently Used objects and can be accessed via a single click. 21

24 Novell Training Services (en) 15 April 2009 Introduction to Imaging Bundles 22

25 To do automated imaging operations an Image Bundle of some type must be created and configured using the ZCC. There are eight types of Image Bundles: ZENworks Image Bundle Multicast Image Set Bundle Imaging Script Bundle 3rd Party Image Bundle AutoYast Bundle Kickstart Bundle Dell DTK Configuration Bundle Empty Bundle Novell Training Services (en) 15 April 2009 IMPORTANT: This course does not focus on ZCM s Third-Party Imaging capability. Novell Technical Learning does offer a six-hour on-line course entitled Course ZENworks Configuration Management 10 Third-Party Imaging. The different types of Image Bundles are designed to meet certain imaging needs. Multicast Image Set Bundle is great for sending one or more image files (.zmg files) to multiple workstations at a time. Image Script Bundles offer the greatest degree of control and flexibility. This type of Image Bundle contains a bash script that is run on each workstation. This 23

26 Novell Training Services (en) 15 April 2009 allows the administrator to run a script on the workstation that may contain any valid Linux or imaging command. ZENworks Image Bundle is simplest mechanism for restoring a single image file down to a managed device. Empty Bundle is essentially a blank slate. You can configure any number of imaging actions. For instance you could configure a script to be run on all devices followed by those same devices joining a multicast session. After an Imaging Bundle of any type has been created you can modify the actions in the bundle or add new imaging actions to suit your needs. The general process you will follow to image multiple workstations at a time is outlined below: 1. First you need to create the image or images you want to lay down on your workstations. You could employ either of these philosophies: Build a model machine that has the operating system of choice, patches, applications, and possibly the ZENworks Adaptive Agent. This process creates a hardware specific image. Also make sure that if you use this approach and you include the ZENworks Adaptive Agent, that the device is not registered in a Zone before you take an image of the model machine s hard drive Create a hardware independent base image and add-on images that contain the drivers that are specific to a particular model of PC or laptop. This 24

27 technique involves creating images that are part of what is referred to as your image stack. This process involves using Microsoft s SYSPREP utility to force Windows to go through a mini-setup process once the imaging process has completed and the device reboots. Driver add-on images could be created using ZCM s Image Explorer utility. TIP: Novell Training Services offers an on-line training class in hardware independent imaging techniques. 2. Once your images have been built, you would use the ZCC to create a Multicast Image Set Bundle that specifies the images you built. You would need to launch the ZCC and authenticate into the Zone. Then select the Bundles link in the upper left pane of the ZCC to begin the bundle configuration process. 3. Configure your Image Bundle. This would involve giving the bundle a name and specifying the images you made by creating a model workstation or building an image stack. 4. Configure the Preboot Zone related settings. Click the Configuration link in the upper left pane of the ZCC. Then expand the Device Management category and click the Preboot Services link to build the hardware rules that meet the hardware you want to image. After your hardware rules are complete, simply power up the workstations so that: 1. the Preboot process can discover that there is imaging work to do, 2. then the ZENworks Imaging Distro will be downloaded into the memory of each device 3. and all the images listed in your Multicast Image Set Bundle will be delivered to each device. Novell Training Services (en) 15 April

28 Novell Training Services (en) 15 April 2009 Configuring Imaging related Zone Settings There are zone-wide settings that can be configured that impact the imaging feature in ZCM. The first setting discussed controls the displaying of the Default PXE (Preboot) Menu. By default, this menu is not displayed unless the user presses the Ctrl-Alt keys during the PXE boot process. However this Zone setting can be configured to display the Default PXE Menu every time a device goes through the PXE boot process. If the menu is successfully display on the device to be imaged you know that it has successfully contacted your ZCM Image Server. To configure the PXE Menu setting: 1. Launch the ZCC and authenticate into the Zone. 2. Click the Configuration link in the upper left pane. 3. Expand the Device Management category of settings. 4. Click the Preboot Services link. 5. Expand the Imaging Menu Options category. 6. Click your desired setting. In the example above Always show imaging menu is selected. 26

29 Novell Training Services (en) 15 April 2009 Shown in the graphic above is the Zone setting for Allow Preboot Services to overwrite existing files when uploading. By default this setting is not enabled. If enabled, this setting would permit a device to create an image file on the Primary Server despite there being a file of the same name already existing in the file system of the Primary. This setting is useful when you are first building and testing the images that you will ultimately deploy to your production machines. 27

30 Novell Training Services (en) 15 April 2009 ZCM allows the administrator to define Custom Hardware Types. Custom Hardware Type is the ability to define string that represents a model or machine type based on information found in the machine s BIOS. In the example shown above, the string VMwareBox will be assigned as the Hardware Type if in the BIOS of the machine either the string VMware or VMware Virtual Platform is found. So for instance, an administrator could define a Custom Hardware Type called Opti745 if the string Dell Optiplex 745 is found in a machine s BIOS. The benefit of Custom Hardware Types is that they can be used in the building of rules that dictates whether or not a given machine has imaging work to do. 28

31 Novell Training Services (en) 15 April 2009 Shown above is an Imaging Rule that uses a Custom Hardware Type as one of the filters that comprise the rule. This particular rule specifies three different filters: the Hardware Type of the machine must be of the type VMwareBox and the machine must have greater than or equal to 256 MB of RAM and the machine must have a hard drive that is greater than or equal to 6 GB. The Hardware Type filter will not be displayed in the drop-down when configuring a rule unless you have defined at least one Custom Hardware Type. 29

32 Novell Training Services (en) 15 April 2009 Objective 3 Creating Multicast Imaging Bundles Before understanding how to leverage Multicast Image Bundles in ZCM you need to understand the following topics: Understanding Hardware Rules - in depth on page 31 Creating Multicast Image Set Bundles on page 37 30

33 Understanding Hardware Rules - in depth Novell Training Services (en) 15 April 2009 During the Preboot process, the PXE Client running on a workstation sends basic hardware and ZENworks identity information to the Preboot Service component mentioned earlier. The Preboot Server will take the information received from the device and compares it to Hardware Rules that have been configured in the Zone using the ZCC. The device has imaging work to do if the information received from the device matches the information configured in one of the Hardware Rules. The following information is configured for each Hardware Rule created by the administrator: Rule Name - Each rule created must have a unique name. Criteria - Is comprised of one or more filters. When a rule s criteria consists of multiple filters, the filters are logically joined by logical AND or logical OR operators. Image Bundle name - If a workstation meets a rule s criteria, the workstation will be imaged using the Image Bundle mentioned in the rule. The Image Bundle specifies the imaging work to be done. Whether or not the rule has been enabled. The administrator can create rules without having them be active. Disabled rules exist in the Zone it is just that a rule can not be used for imaging until it is enabled. 31

34 Novell Training Services (en) 15 April 2009 It is typical that most organizations will have multiple enabled Hardware Rules defined in their Zones. When multiple rules are enabled, the information received from the workstation during the Preboot process is compared against the hardware criteria listed in the rules in a top-down fashion. The Image Bundle used to image the workstation will come from the first Hardware Rule whose criteria have been met. This top-down evaluation of the criteria in all enabled Hardware Rules has an impact on how you as the ZCM Administrator should organize this list. Make sure that the rule whose criteria is most specific is at the top of the list. The rule at the bottom of the list should have the most general criteria. 32

35 Novell Training Services (en) 15 April 2009 Each Hardware Rule consists of at least one filter. And each filter has the following three components: Criterion Operator Value The graphic above highlights all the criteria that can be used in a filter. The Hardware Type criteria will not show up in this drop-down unless a Custom Hardware Type has been configured in the Zone. 33

36 Novell Training Services (en) 15 April 2009 Within a filter of a rule, operators are used to join the selected criteria to a value. Operators can be used to evaluate string values or numeric values. When evaluating string values operators can be: Equal to - This means an exact match, including case, must exist between the value sent up by the workstation and the value specified in the filter. Contains - This is a substring match. The string specified in the filter must be somewhere in the string value sent up by the workstation. Starts with - The value sent up from the workstation must begin with the character string specified in the filter. Ends with - The value sent up from the workstation must end with the character string specified in the filter. 34

37 Novell Training Services (en) 15 April 2009 The graphic above shows a Hardware Rule with two filters; one testing the workstation s IP address, the other testing the size of the workstation s hard drive. Since these filters are joined with a logical AND operator, both filters must evaluate true before this rule will be used to image a workstation. A filter can be inverted by selecting the NOT operator in the first drop-down of the filter. 35

38 Novell Training Services (en) 15 April 2009 To accurately build your Hardware Rules, you must know how ZCM will report the hardware information for your different machine models. This can be determined by: 1. PXE booting the workstation and pressing the Ctrl-Alt keys. The Default PXE Menu shown above will be displayed. 2. Select Start ZENworks Imaging Maintenance and press Enter. The ZENworks Imaging Distro will be downloaded from the TFTP Service and established in a RAM drive of the workstation. 3. From the bash prompt enter the command: img i 4. Record the information displayed. Press the Alt-x keys to exit the img display. 36

39 Novell Training Services (en) 15 April 2009 The graphic above displays output from the img i command. This command was executed from a VMware Virtual Machine that was PXE booted to the bash prompt. Creating Multicast Image Set Bundles 37

40 Novell Training Services (en) 15 April 2009 Now that Imaging Bundles and Hardware Rules have been presented, you are ready to learn the step-by-step process to create a Multicast Image Set Bundle using the ZCC. Create a Multicast Image Set Bundle by following this procedure: 1. Launch your browser and enter the URL: Authenticate to the Zone using the Zone Administrator s user name and password. 2. From the upper left pane click Bundles. 3. Under the Bundles Task pane click the New Bundle link. 4. On the Step 1: Select Bundle Type screen select Preboot Bundle; click Next. 5. On the Step 2: Select Bundle category screen select Multicast Image Set; click Next. 6. On the Step 3: Define Details screen type in a name for the bundle. The Description field is optional. But this can be useful for documenting how the bundle is to be used or the type of workstations that will be imaged using the bundle. Click Next. 7. The Step 4: Multicast Details screen is used to specify the number of workstations involved in the multicast (multicast clients) and the names of the image files (.zmg files) that should be multicast out to the client. 38

41 Novell Training Services (en) 15 April 2009 In the Number of clients needed in order to start the multicast session field type in the number of workstations that should receive the images. 8. In the Time to wait to start the multicast session if not enough clients connect field type in the number of minutes that have to pass since the last multicast client has joined the session before the Primary Server will start multicasting. These two fields are used to say for instance, I want 10 workstations to receive the images. But only allow 5 minutes to pass since the last workstation has joined the session before starting the multicast without all 10 clients. 9. Now you can begin selecting the image files that should be part of the multicast session. 39

42 Novell Training Services (en) 15 April 2009 Click the Add image button. 10. Click the Magnifying Glass icon to begin browsing for the first image file of the multicast image set. This image could be a base image or an add-on image. 11. On the Server and Path Information dialog there are two browser buttons. One to select the object of the Primary Server were the image file resides; and the second to browse the file system of the chosen Primary to select the image file itself. Click the Magnifying Glass icons to select the Primary Server s object and the image file on that server. 12. Click the OK button; click OK again. 13. Add additional image files to the multicast if required by repeating Step 9 on page 39 through Step 12 on page 40 inclusive for each image file. 40

43 Novell Training Services (en) 15 April Click Next. 15. Click Finish. 16. Now you need to configure the Preboot related information. 41

44 Novell Training Services (en) 15 April 2009 Click the Configuration link in the upper left pane of the ZCC. 17. Expand the Device Management category. 18. Click the Preboot Services link 19. Expand the Device Imaging Work Assignment category. 20. Under the Hardware Rules heading click the Add button. 21. Use the Rule Construction dialog to build your Hardware Rule. 42

45 Novell Training Services (en) 15 April 2009 In the graphic above, the Hardware Rule contains five filters. When devices boot up and check for preboot work to do, the devices must meet all of these filters in order to join the multicast session. 22. Click OK to close the Rule Construction dialog. Now power up all the workstations you want to be part of the multicast session. When the number of clients specified back in Step 7 on page 38 join the session or the amount of time passes that was specified in Step 8 on page 39 the Primary will begin multicasting the first image file specified. 43

46 Novell Training Services (en) 15 April 2009 Objective 4 Performing Manual Imaging Operations This objective teaches you how to perform manual imaging operations. The following topics are covered in this objective: Why do manual imaging? on page 45 Where are images stored? on page 46 Taking a manual image of a machine on page 47 Restoring an image manually on page 51 Setting up Multicast Sessions on page 54 44

47 Why do manual imaging? Novell Training Services (en) 15 April 2009 There are times when knowing how to do a manual imaging operation can be very useful. The following are examples of why you might need to do a manual imaging operation: You have built a model machine that contains the exact configuration you want other machines to have. You could do a manual operation to upload the contents of your model s hard drive to a zmg file on your Primary. Then you can use the ZCC to create a Multicast Bundle that will multicast the image of your model to multiple machines at one time. Rather than using the Primary Server as the multicast master, you can use the model machine itself as the multicast master. Or maybe a problem occurred on one of the machines that had joined the multicast session. So now you simply want to do a manual imaging operation to the machine that dropped out of the multicast session prematurely. 45

48 Novell Training Services (en) 15 April 2009 Where are images stored? To do manual imaging operations it is important to know where images are stored on your Primary Server. In ZCM Primary Servers, image files are stored in a location that is relative to the location of the Content Repository. On a Linux Primary Server the Content Repository is located in /var/opt/novell/zenworks/content-repo. Image files are stored in an images directory under the content-repo directory. So if you used a manual img command and simply specified the name of an image file named mybase.zmg. The actual file name created would be /var/opt/novell/zenworks/ content-repo/images/mybase.zmg. 46

49 Taking a manual image of a machine Novell Training Services (en) 15 April 2009 Complete the following to manually image the contents of a workstation s hard drive up to a zmg file on the Primary Server: 1. Boot the workstation. During the PXE boot process press the Ctrl-Alt keys. 2. From the Default PXE Menu select Start ZENworks Imaging Maintenance. This will take the machine to the bash prompt of the ZENworks Imaging Distro. 3. Enter the following command from the bash prompt: img mp relative_path/filename.zmg -comp=c-level For example the command: img mp modelboxes/opti745.zmg -comp=1 creates an image file named opti745.zmg under the /var/opt/novell/zenworks/ content-repo/images/modelboxes directory on the Primary using a compression level of 1. 47

50 Novell Training Services (en) 15 April 2009 More examples of the img mp command. Rather than issuing img commands from the bash prompt, you can also take a manual image of machine s hard drive by using the menu system that is built into the img command. Complete the following procedure to use img s menu to take an image of a machine s hard drive: 48

51 Novell Training Services (en) 15 April

52 Novell Training Services (en) 15 April 2009 End of the procedure to take an image of a workstation s hard drive using the img menu system. 50

53 Restoring an image manually Novell Training Services (en) 15 April 2009 Just as you can issue img commands from the bash prompt of a workstation to image up a machine s hard drive, you can issue an img command to bring down an image from a Primary to a workstation. You can use the img rp command to restore an image down to a machine s hard drive. Once again you will need to PXE boot the machine and bring up the Default PXE Menu. 51

54 Novell Training Services (en) 15 April 2009 Examples of the img rp command. 52

55 The menu system built into the img command can also be used to restore an image to a machine s hard drive. Novell Training Services (en) 15 April

56 Novell Training Services (en) 15 April 2009 Setting up Multicast Sessions Before learning how to set up Multicast Sessions in ZCM there are a few terms you need to understand. Session Name - Each Multicast Session must have a unique name that identifies that multicast session from any other that may be going on in the network. The name is simply a character string. The Multicast Session Name is used to calculate a unique 231.xxx.xxx.xxx address to which the frames of the multicast will be sent. Multicast Master - This is the machine where the name for the session is assigned The Multicast Master is the machine whose hard drive contents you want sent to other workstations. Multicast Client - These are the machines that receive the contents of the Multicast Master s drive. These machines must specify the name of the Multicast Session they wish to join. 54

57 Novell Training Services (en) 15 April 2009 If you need to set up a workstation as a Multicast Master complete the following steps: 1. Boot the workstation that will serve as the Multicast Master. During the Preboot process press the Ctrl-Alt keys to display the Default PXE Menu. 2. From the Default PXE Menu select Start ZENworks Imaging Maintenance 3. From the bash prompt issue the command: img -s <sess-name> -master -clients=n -timout=m where <sess-name> is the name you want to assign to your Multicast Session n is the number of multicast client workstations you want to receive the multicast and m is the number of minutes to wait since the last multicast client has joined before starting the multicast session. If you do not specify the clients and timeout parameters you will need to press g on the multicast master after all you multicast clients have joined the session. 55

58 Novell Training Services (en) 15 April 2009 Examples of the img s command to designate a workstation as a multicast master. 56

59 Issue the above img s command with the -client parameter from the bash prompt of the workstations you want to participate as multicast clients. Novell Training Services (en) 15 April

60 Novell Training Services (en) 15 April 2009 Objective 5 Performing Basic Troubleshooting of ZCM Imaging This objective provides some basic troubleshooting steps to take if the imaging process does not start at the workstations. 58

61 Trying to display the Default PXE Menu is an easy way to verify whether or not the workstation can receive information from the Proxy DHCP and TFTP Services. If the Default PXE Menu can not be displayed on the workstation check the following: Verify that the workstation s network adapter is enabled as a boot device in the machine s BIOS. Verify that the TFTP and Proxy DHCP Services are running. (See Section, Determining if ZCM Imaging Services are running, on page 11 on how to determine this.) Results will be unpredictable if you have multiple DHCP Servers in your environment and workstation doing a PXE boot gets a response from more than one DHCP Server. If you can use the Ctrl-Alt keys to display the Default PXE Menu on a workstation, but no automatic image work to do is detected, verify the Preboot Policy Service is running on the Primary. Novell Training Services (en) 15 April 2009 Configuration issues can be another problem area for why automatic imaging operations do not occur. Use the ZCC to verify that your: Hardware Rules specify the correct Imaging Bundles Workstation hardware matches the filters defined in your Hardware Rules Image files (zmg files) have the actual name and location in the Content Repository as defined in the Image Bundles. 59

62 Novell Training Services (en) 15 April 2009 If you are having trouble imaging unmanaged devices check to make sure that there is no Image Safe Date already on the machine. This would be a problem for instance if a machine had been registered in one zone and then was moved to another zone. The Primary Servers in the second zone would never image the machine that contained ISD information that stated the machine was in a different zone. The following commands can be run from a bash prompt on a machine to show if this issue exists: zisview This command will show if the machine has information configured in ISD. zisedit -c This command will clear all ISD information. If your DHCP and Proxy DHCP Services are running on the same server you need to make a few changes to ensure that both of these services are listening on separate unique ports. The required changes are shown above. The last quick troubleshooting technique to use is to ensure that none of the imaging or PXE related ports are blocked by the server s firewall. 60