Secrets of ZENworks® Imaging and Preboot Services – TUT214

Secrets of ZENworks® Imaging and Preboot Services – TUT214
Drake Backman Senior Development Engineer Tim Harris Senior Systems Engineer Michelle Escalante System Engineer Slide Workstation E & F & G & bash prompt Policy to CTRL-ALT F should have workto do next boot Outline – Only imaging session we will cover components that make up imaging to get a level set of knowledge then advanced configuration options Have 2.5 hours – scheduled to run from ___________ to ___________. We will take a quick break mid-way through to let yall blow off some steam. Questions until end – please write down. Introductions

Agenda – TUT214 Introduction Imaging Components Initiating Imaging
eDirectory and ConsoleOne Initiating Imaging PXE Maintaining Current Versions Multi-cast Under the Hood Scripted Images Hardware Independent Images Build scripts Customizing Bootable CD’s Resources Q&A Slide Introduction: How ZEN fits into Novell’s vision ZEN family of products ZEN Imaging – high level versus other options Components: Establish baseline- Level set terminology and concepts so we can discuss advanced features Initiating: Once we talk about components and how to configure imaging – how does the workstation get work-to-do BREAK Under The Hood Scripting to do more advanced imaging than just completely overlaying the desitnation WS Images tolerant of different hardware Customize some of the IMG functions themselves Boot CD’s Resources: Tools available Q&A

Vision…one Net Mission
A world where networks of all types—corporate and public, intranets, extranets, and the Internet—work together as one Net and securely connect employees, customers, suppliers, and partners across organizational boundaries. Mission To solve complex business and technical challenges with Net business solutions that enable people, processes, and systems to work together and our customers to profit from the opportunities of a networked world. Slide You can see Novell’s Vision – a world where networks of all types – corporate and public, intranets, extranets and the Internet work together as one net…. Reflected in the technologies Novell has developed and that you’ll hear announced throughout the week. ZENworks has always been about solving the complex business challenge of desktop management – Work at Home / Remote Access / Laptops – Promethius firewall friendly Managing cost of desktop maintenance in distributed environments – PXE

one Net business solutions model
One Net Business Strategy Practices Suppliers Employees Customers Professional Services Rapid Technology Rationalization BPM for Local Govt Active Information Portals Secure Partner Portal Identity Provisioning for PeopleSoft … Solutions Product Groups Networking & Storage Access Security Application Provisioning User Provisioning Collaboration Integration Services Management Resource Storage File Print Web Access Content Delivery Portal Services Messaging … Slide By having this clearly defined Vision of OneNet, the technology is built upon this idea of solving our customers business problems in their environment. This means that eDirectory runs on the most common server platforms our customers are using. All core services leverage eDirectory. So that once you’ve built that solid foundation once – now we have a world of possibilities. Our professional services team has always been there for the point solutions – like the ZENworks deployments, to help rapidly deploy and integrate new features. They’ve also put together solution sets for ways to analyze your specific environment and built custom solutions or integrate multiple technologies together to solve the complete business end-goal. Services Software Net Core Services Platform eDirectory Operating Systems NetWare Windows Solaris Linux AIX …

The Novell ZENworks Family
ZENworks for Desktops Manages the complete workstation lifecycle and provides personalized workstation service to end users ZENworks for Servers Provides cross-platform server consistency, content distribution, and management of critical resources, alarms, SNMP, and inventory assets ZENworks Preboot Services Enables PXE integration for ZENworks for Desktops workstation disk imaging ZENworks for Handhelds Automates management for wireless and handheld devices ZENworks OnDemand Services Automates digital asset provisioning to users wherever they are; tracks and reports usage; manages and personalizes terminal services ZENworks Synergy Extends the managed, personalized work environment to any location from any Windows machine Slide ZEN family of products is ever-growing. We are focusing on Imaging portion of ZEN for DESKTOPS and PREBOOT services

Why ZEN Imaging Rocks Provides flexible, NDS based imaging
Reduced image management Customizable Base images Add-on application imaging Workstation identity management Scripted image deployment Intelligent deployment of new OS Slide Over 40 Million ZEN users today Most IT organizations today are using imaging of some shape or form. The basic premise is the same across solutions, a way is needed to quickly deploy a new workstation using an existing “image” or picture of a standard machine. Also with the cost of troubleshooting workstations today many helpdesks have quotas imposed on them where if they can’t solve a user problem in say 20 minutes or so – it is more economical for the company to completely restore the image than troubleshooting it for hours find the stat to quote a source and #’s. Finally imaging is playing a major role as companies upgrade from on version of an operating system to another on a mass scale. So why ZEN imaging…. NDS integration – ability to have cetralized intelligent-granular control using the WS, Image and Policy objects in NDS. Don’t have to build complete unique images for every different job type in company – image for sales, secretary, engineering.. Create one W2K base images and then add on application images based on roles. Fewer images to manage – less space taken One image to update!!!!! Image Safe Data – maintain workstation identity to automate steps required after restoring a workstation of customizing the identity. NetBios Name, IP information, SID, Tree, Workgroup/Domain, Workstation NDS distinguished name, Image history info (last image, last image date, last image size, just imaged flag) Image scripting: Advanced customization on how and when to deploy an image… time, partition to partition OS Roll-outs: need more info here on what we can do exactly Edit base image and leverage existing ZEN applications and application methodology customers are familiar with

Imaging Components Slide

Imaging Mechanism Imaging Engine img Image Proxy Server
ZEN Image Safe Data (ZISD) ZISWIN.exe identity, history hardware Image Proxy Server IMGSERV ZENIMGDS Slide WorkstationE at bash (img I z) (img I h) (zisedit) (zisedit edit) Workstation side components and server side components Like ghost or pqdi - Manual mode – automatic mode ZEN Image Safe Data (ZISD) Maintain the “unique workstation identity” WS Object name , IP address & NETBIOS name Workgroup, SID (NT/W2K), Tree Last Base Image Date & Size Just Imaged Flag Imaging agent – ZISWIN.exe Novell client – Imaging Services Option ZISD-9x or ZISD-NT application objects Manually install agent Area on a harddrive after the masterboot record but before 1st active partition. Not re-written each time images. The IMG engine reads this ZISD area when contacting the imaging server in order to check for WS Object name and Hardware information. This information is used to determine what work should be sent to the workstation. IMGSERV.NLM Imaging Proxy Server Receives requests from imaging engine (IMG) Calls helper ZENIMGDS.NLM Accesses NDS for Proxy to read policies Accesses file system Server based multicasting Uses ports UDP 997 & TCP 998 Debug flag can be set in ZFDSTART Imgserv.nlm -debug Just Imaged Flag controls when information is being written from or to the Image safe data area. The last thing after a ZEN image is placed on a workstation – is that this flag is set to a “1” – meaning just imaged. The next time the workstation boots – ZISWIN.exe reads that “1” and will restore ZISD info to the workstation and change flag to “0”. When ZISWIN reads flag as “0” it checks WS information and writes it to the ZISD info – thereby keeping it updated.

Initiating Imaging Engine
Booting from a set of floppies public\zenworks\imaging\zimgboot.exe Booting from a CD Booting from the Network (PXE) Booting from a local ZEN partition Slide C1 PXE bootstrap PXE boot adds ~10 seconds to normal boot Single boot when there is no work scheduled for the device Imaging engine centrally stored Enables non-intrusively; preserves local drive data ZENworks Imaging partition Adds >20 seconds to normal boot Requires double-boot at each startup, regardless of scheduled work. Imaging engine stored on each device Adding Linux partition destroys local data

eDirectory & ConsoleOne
Application Object Create add-on images (.zmg files) Image Object Base image, variants, add-on images, scripts Workstation Object Specific work-to-do behavior PXE menu & ZEN Imaging Partition behavior Slide Use compression level 5 (balanced) no more Any higher slows down a lot Disk space saved above 6 is minimal 1 for speed – 6 for balanced – 9 for space Single base image with add-ons for customization Base image is HAL, disk type, specific based on OS Add-ons can be applications, drivers, etc. W2K average image size of ~650 MB (without compression) Image object – base file (destructive), add-on image files, file sets, imaging script

eDirectory & ConsoleOne
Workstation Policy Object Imaging rules for known workstations (Image Safe Data / NDS) PXE menu & ZEN Imaging Partition behavior Server Policy Object Imaging rules for unknown workstations (no ISD) Image Safe Data configuration info (IP, NETBIOS name) Security – image upload restrictions Server Object Multicast Session Slide ConsoleOne administation WS Object: controls imaging action that will occur to a specific workstation, Linux partition, …scenario – HD person troubleshooting.. Image object – base file (destructive), add-on image files, file sets, imaging script WS Policy object – Imaging Partition, to show PXE menu or not, Multicast information Server policy objects – rules for workstations without a WS object (ie new), Multicase session – Specifies multicast master, session start behavior, clients & image rules – cover in detail in Advance Imaging section Use compression level 6 (balanced) no more Any higher slows down a lot Disk space saved above 6 is minimal 1 for speed – 6 for balanced – 9 for space Prevent Denial Of Service attacks By default anyone can upload images anywhere Configure server policy to restrict uploads to specific directories Place quota restrictions on those directory

PXE: Pre eXecutable Environment
Boot From Network

10,000 foot view, what is…PXE What is it… Spec developed by Intel
Support of Wired for Management 2.0 ftp://download.intel.com/labs/manage/wfm/download/pxespec.pdf Uniform protocol for a client to… Request the allocation of a network address Then request the download of a network boot program from a network boot server Set of APIs in the machine’s pre-boot firmware environment that constitutes a consistent set of services that can be employed by the Network Boot Program or the BIOS. Slide What is it Spec developed by Intel in support of Wired for Management 2.0 ftp://download.intel.com/labs/manage/wfm/download/pxespec.pdf A uniform protocol for a client to request the allocation of a network address and subsequently request the download of a network boot program from a network boot server. A set of APIs available in the machine’s pre-boot firmware environment that constitutes a consistent set of services that can be employed by the Network Boot Program or the BIOS. Why do you want it Automatic remote configuration of workstation hardware within a heterogeneous network environment. Boot to a diagnostics/reporting system in the event of a hard disk subsystem failure* “Diskless” workstations to be able to boot* * These are generic attributes of PXE, but not necessarily uses of Novell’s Preboot Services Product

10,000 foot view, why…PXE Why do you want it…
Automatic remote configuration of workstation hardware within a heterogeneous network environment. Boot to a diagnostics/reporting system in the event of a hard disk subsystem failure* “Diskless” workstations to be able to boot* These are generic attributes of PXE, but not necessarily uses of Novell’s Preboot Services Product Slide What is it Spec developed by Intel in support of Wired for Management 2.0 ftp://download.intel.com/labs/manage/wfm/download/pxespec.pdf A uniform protocol for a client to request the allocation of a network address and subsequently request the download of a network boot program from a network boot server. A set of APIs available in the machine’s pre-boot firmware environment that constitutes a consistent set of services that can be employed by the Network Boot Program or the BIOS. Why do you want it Automatic remote configuration of workstation hardware within a heterogeneous network environment. Boot to a diagnostics/reporting system in the event of a hard disk subsystem failure* “Diskless” workstations to be able to boot* * These are generic attributes of PXE, but not necessarily uses of Novell’s Preboot Services Product

5,000 ft view, what is Novell’s Preboot Services Product?
Customized implementation of PXE software from PreWorx PXE integrated with eDirectory Directory policies determine what work there is to do PXE integrated with ZENWorks Imaging Boot images are “hard coded” around ZENWorks imaging Customization of boot programs requires purchase of additional software from PreWorx Processes are optimized for hard disk imaging Slide Normal PXE will present user with Menu asking them what they want to do……not ideal for the masses We’ve worked with PreWorks to allow our implementation of PXE to check Policies configured by knowledgeable help desk people to determine imaging work to do.

Preboot Services Requirements
DHCP environment PXE compliant client hardware NIC support Motherboard BIOS PXE on disk (if NIC is supported) Servers to act as image proxies and PBS servers slide P 450- need to edit slide a bit How far into this do we want to plan to go – or should we defer to the PXE session? Determine servers to act as image proxies & PBS servers

On the deck - PBS Components
Di-NIC Proxy DHCP Server Responds to modified DHCP requests Provides addresses of other PXE services Di-NIC Trivial FTP (TFTP) / Multicast TFTP Server Provides file services to PXE client Sends Linux boot images down to PXE client Di-NIC Transaction Server (DTS.NLM/VSP.EXE) Provides PXE client with tasks to be performed Requires ZENPXE.NLM on same server Slide

On the deck - PBS Components
ZENworks PXE Module ZENPXE.NLM Acts as image client on behalf of DTS server Requires Image Proxy on same server Queries eDirectory policies Di-NIC Client Provides interface to Transaction Server Checks for PXE tasks to be performed Linux Boot Image & DOS Executable slide

PXE… WITH work to do PXE… How it works PXE… with no work to do
Client DHCP Server PDHCP Server Di-Nic Client does Hardware Detection and reads ZEN Image Safe Data (ZISD). Sends results to DTS requesting Work to do. DTS Passes request to ZENPXE Di-Nic Client returns failure code to PXE firmware. Firmware generates status/error message. BIOS passes control to next boot device. DOS image boots and downloads linux.1 (kernel) and linux.2 (filesystem) from TFTP server ZENPXE queries eDirectory for work to do and informs DTS. DTS informs Di-Nic Client Di-Nic Client downloads DOS image contained in bootzen2.bin from TFTP server. DHCP Server Responds with Client IP information. PDHCP Server responds with address of TFTP Server. PXE Firmware Downloads Di-Nic client image from TFTP Server DOS image runs loadlin.exe to boot Linux into ZENworks Imaging system. Di-Nic Client requests Di-Nic Transaction Server (DTS) address from PDHCP Server PXE Firmware issues modified DHCP Request BIOS Boot Order gets to “boot from network” Workstation BIOS Post Workstation Powers On DTS Server ZENPXE Agent TFTP Server

PXE Design and Optimization
Deploy only 1 Proxy DHCP server per subnet Discovered via broadcast so multiples will result in intermittent behavior TFTP server(s) local to client for performance Deploy at least 1 image proxy at each site Image proxies can refer clients to other image proxies Multiple proxies can be used to distribute load If using PXE this MUST be your DTS server Use DNS names for image proxies No need to touch workstations if you change the IP address or move to a new server Case Study: ZENworks Development Team Slide TFTP consideration: DiNic client, linux.1, linux.2, bootzen2.bin, approx 5-6 meg data

Maintaining Current Versions
slide

How to Keep Up-To-Date PXE Diskette CD ZEN Partition
linux.1, linux.2 in TFTP Diskette CD ZEN Partition Slide Workstation G – bash prompt ….zisupdate.sig Zupdate.sig controls both initiating an update and which files are updated

Automated ZEN Partitions Updates
Deploy changes to existing ZEN partitions without having to visit each workstation Version stored on the ZEN partition & Imaging proxy service Server loads the version information at load time Client queries version information at “GetWorkToDo” If needed, updates downloaded and deployed (lilo.s) Update requires reboot Update process only occurs if booted from an installed ZEN partition Slide Workstation G – bash prompt ….zisupdate.sig Zupdate.sig controls both initiating an update and which files are updated

Multicasting Slide One to many Deliver single stream of information from the source to multiple clients

Multicast Scenarios Configure & Launch Multicast session
Classrooms & Testing labs (ZWAKE) Deployment areas (ZEN Computer Name Changer) Mass OS upgrades (iFolder) Mass application .zmg distribution Configure & Launch Multicast session Automatically via ConsoleOne (PXE) Manually by visiting the workstations (IMG) Manually on Server side (Prometheus) Simultaneous Multicast Slide Internet Protocol designed to conserver bandwidth Delivers single stream of information from the source to multiple receivers without adding additional burden on source. Uses the least network bandwidth of any competing technology. Ex: videoconfrencing Classrooms- schools using today – easier to level set machines back clean once a week than troubleshoot configuration issues Deployment areas – attach new machines to imaging server – set up rules for if no ZISD data exist based on hardware for which images to use. Set up configuration for IP address, NetBIOS name – ZCNC Testing Labs – changing constantly quickest way to keep resetting clean workstations and trying out changes Mass Upgrades – depending on how you manage user data. Multicast is a destructive imaging process – but if combined with iFolder or other similar technology…. Demo the console one configuration – then in the lab demo will show via disks Defining an Automatic Session (Optional) Install the ZfD imaging agent on each of the participating computers. See Why Use Multicast? for the reasons and for further instructions. In ConsoleOne, right-click the Server object > click Properties > the ZENworks Imaging tab. Click Add > type a name for the multicast session > click OK. On the Multicast Session Settings page, specify the Master Image Source. You can specify an image file or a master workstation. A workstation cannot be the master if it is being used as a master in another multicast session or if it explicitly participates in any other session. Decide how many participating workstations you want to have booted up before the multicast session begins. Specify this number in the Clients Have Joined text box. The default if you do not specify a number is 5 workstations. If not enough workstations have booted up to fulfill the Clients Have Joined requirement, the multicast session will begin if a participating workstation boots up and certain amount of time passes without another participating workstation booting up. Specify this amount of time in the Minutes Have Elapsed Since a New Client Has Joined text box. The default if you do not specify a time is 15 minutes. To delete the session after it has finished, select the last check box. On the Multicast Session Participation page, click Add under Include the Following Workstations to explicitly add the workstation objects that you want to include in this multicast session. or To create rules to select the workstations you want to participate in this multicast session, click Add under Include Machines Which Meet Any of These Criteria. Click Help on the Participation page for more information. Click OK to return to the ZENworks Imaging Multicast Sessions page. The check box next to the multicast session name is automatically selected, showing that the session is enabled. If you want to disable a multicast session, deselect the check box next to the session name. If multiple multicast sessions are defined that use rules to select participating workstations, it is possible that a workstation could qualify to participate in more than one session. If this occurs, the first enabled session in this list for which the workstation qualifies takes precedence over the other enabled sessions. If you want to change the position of a session in the list, select the multicast session name > click Move Up or Move Down. Click OK. Physically Visiting Each Computer Create a set of ZfD imaging boot diskettes or an imaging boot CD for each person who will assist with the multicast session, or enable PXE on the participating computers. If you don't know how to do this, see Creating Imaging Boot Diskettes in Preparing for Basic Imaging Operations in Workstation Imaging in Getting Started, or Preparing an Imaging Boot Device or Method in Deployment. At each computer, including the master computer, access a Linux prompt by using the imaging boot diskettes, imaging boot CD, or if it is PXE-enabled, boot it up. Depending on the method you used in Step 3, enter manual at the boot prompt or select to start in Maintenance Mode from the PXE menu. To start the multicast session, you have two choices: You can enter the following command at the bash prompt of every computer: img session name where name is any string that uniquely identifies this multicast session from other multicast sessions that might be in progress on the network. Use the same session name on each of the participating computers in this multicast session. You can specify any multicast session, including one that originates from the proxy server (as long as you specify the session name used by the proxy server). Example: img session doug The img session command can take other parameters that allow you to designate the master computer and the imaging start time beforehand. See Imaging Engine (img: Command Line and Menu) for details. You can type img at the bash prompt to display a menu > select Multicast Session > select Client if this is a participating computer or Master if this is the session master. Fill in the Session Name, Number of Clients (applies only to session master), and Timeout (applies only to session master) fields. See Imaging Engine (img: Command Line and Menu) for details. At the master computer, type m > press Enter. At the master computer, after all the other computers have registered as participants, type g > press Enter. The imaging engine begins creating the image of the master computer and the image is sent to and laid down on each participating computer. Any problems are reported back and displayed on the master computer. At each participating computer, when the imaging is done, do the following to boot the computer with the new operating system: At the Linux prompt, type lilo.s > press Enter. Press Ctrl+Alt+Delete. HINT: If the computer doesn't boot to the new operating system (that is, if the Linux prompt reappears), enter the lilo.s command again and reboot the computer a second time.

Multicast Sessions Check work to do determines there is multicast work
Automated through policy, specify master or client The session name is hashed to create a multicast address Always start with 231.x.x.x for sniffing simplicity The workstations register to the multicast master Unique ID that will maintain if lose connection When conditions to start are met image is sent “g” typed on master cl=<#> criteria met time=<# in minutes> criteria met img session doug m cl=5 t=15 Just Imaged flag of client workstations are reset after completion Slide & workstationE (reboot 3 machine to kick off session configured 2 slides ago) after cover first section – reboot last machine

Server Based Manual Multicast
Slide C1 manual server kick off We could manually configure multicast session to push from a Workstation as a source. Prometheus is was request to be able to manually multicast image files from the server Reset workstation policies to Menu Talk about PXE menu here Set up multicast session from ZIS Reset 3 workstations

Multicast Environment
Routers & switches must have multicast features configured ftp://ftpeng.cisco.com/ipmulticast/whitepapers/technology_overview/index.html IGMP Server Object Multicast session fully configured BUT needs query to start Img s <fully qualified name> is NOT a query Img auto IS a query Slide If you’re multicasting from one segment to another you’ll need to configure your switches to pass multicast packets. Some routers treat multicast packets like broadcast packets and some of our competitors actually do broadcast packets and just glaze of and say they are multicasts We are actually doing IGMP – I__________Group Multicast Protocol If you’re switch supports IGMP you can enable it which should reduce bandwidth by passing multicast packets only onto session member. Most common issues – and these are very common that folks hit Server Object configured but not active Img s <fully qualified name> NOTE: For multicasting to work properly, the routers and switches on the network must have multicast features configured. Otherwise, multicast packets might not be routed properly.

break Slide SET WS Policy back to CTR- ALT BOOT 3 WS to Windows

Looking under the hood…..
slide

Advanced Scripted Images
Slide

Scripting: Beyond Cloning
All imaging products have certain functionality Create/delete partitions Insert files… What do you need? Low level control to automate your imaging Freedom to customize / design your imaging solution What ZENworks provides Full bash scripting capabilities from the directory Granular control of the imaging engine from scripts Slide 508 – customize based on who takes this section Above and beyond sheer cloning…. Fundamental set of things imaging does. Exposed those commands and gave users granular access to functionality like partition control (size, location, where, Partition mapping on restore). White paper Changing image size Full bash shell scripts DEMONSTRATION BASIC MODES OF OPERATION There are several basic modes of operation, which are detailed in this section: help, information, partition dump, automated, partitions manipulation, creating archives, restoring archives, and multicast. This section will briefly describe the standard features and syntax for each mode of operation.

img Command Line Options
Auto – Query an imaging proxy server for work to do. Make – Read the contents of this computer’s hard drive(s) and send it to an image archive Restore – Place the contents of an image archive onto this computer’s hard drive(s) Session – Participate in a multicast imaging session Partition – Perform various partition operations ZENPartition – Manage an installed ZENworks imaging partition Dump – Show the partitions and storage devices of this computer Information – Show the detected hardware devices and image-safe data Slide WorkstationE (img help) 508 – customize based on who takes this section Above and beyond sheer cloning…. Fundamental set of things imaging does. Exposed those commands and gave users granular access to functionality like partition control (size, location, where, Partition mapping on restore). White paper Changing image size Full bash shell scripts DEMONSTRATION

IMG Auto Command Lines – None
Contacts the proxy server indicated by the environment variable PROXYADDR and asks if there is any imaging work to be done. Any tasks assigned through the current policy packages are then executed PROXYADDR is set in the settings.txt file of setup disk 3 and can be changed using the config option of the boot disks PROXYADDR may be an IP address, DNS name, or a name from the local hosts file Slide

IMG Make Command Lines img makel [<pNumber>] <filepath> <xpNumber> img makep <address> <filepath> <xpNumber> Makel – Stores the image archive locally either on the ZENworks partition or othe partition indicated by <pNumber>. Makep – Stores the image archive on the proxy server indicated by <address> pNumber – Local partition where the image archive will be stored. Must be a PRIMARY partition of type FAT16 or FAT32. Filepath – file name and path where the image archive will be created xpNumber – Local parition(s) you want to exclude from the image you are making Slide

IMG Restore Command Lines img restorel [<pNumber>] <filepath> <sfileset> <apNumber:ppNumber> img restorep <address> <filepath> <sfileset> <apNumber:ppNumber> Restorel – Restores a local image archive from either the ZENworks partition or the partition indicated by <pNumber> Restorep – Restores the image archive from the proxy server indicated by <address> pNumber – Local partition where the image archive is stored. Must be a PRIMARY partition of type FAT16 or FAT32. Filepath – file name and path where the image archive is stored. Sfileset - The number of the image fileset (variant) to lay down. Valid values are 1 through 10. If you omit this parameter, fileset 1 is used. apNumber:ppNumber - A mapping between a partition in the image archive (apNumber) and a target physical partition on the local machine (ppNumber). Use this parameter to selectively restore a specific part of the image to a specific local partition. If you use this parameter, none of the existing local partitions are removed, and only the target local partition is updated. The update process does not remove any existing files or overwrite any existing files of the same names if they are newer. For apNumber, use the partition number displayed for the source partition in the Image Explorer utility. For ppNumber, use the partition number displayed by img dump for the target partition. Slide

IMG Session Command Lines img session <name> [master|client] [clients=<count> time=<minutes>] Name – Unique name of the multicast session Master|client – Indicates that this computer will be session master, or a session client Count – Number of clients the master will register before starting the session. Default action is to wait for the user to start the session manually Minutes – The number of minutes the master will wait for a new client to register before starting the session with less than <count> registered clients Slide

IMG Partition Command Lines img pa<pNumber> img pc[<pNumber>] <type> [<size>] [cluster=<clustersize>] Img pd<pNumber> pNumber – Local partition to be modified. Pa - Makes <pNumber> the active partition. Pc – Creates a new partition of <type> and <size> at pNumber. Valid types are FAT12, FAT16, FAT32, NTFS and Extended. Valid sizes depend on the chosen type. Choose an appropriate <clustersize> for the <type> and <size> of parition being created. If this parameter is omitted, the imaging engine uses a reasonable cluster size for the parition size. <size> should be expressed in megabytes. Pd – Deletes the partition at <pNumber> Slide

IMG ZenPartition Command Lines img zenPart enable|disable|remove
Disable – Disables an installed ZENWorks partition so that the computer will no longer boot inmto Linux by default. You must run ‘lilo.s’ after disabling an installed ZENworks partition. Enable – Enables a disabled ZENWorks partition so that the computer will boot into Linux by default. You must run ‘lilo.s’ after enabling the ZENworks boot partition. Remove – Removes an installed ZENworks partition from the hard disk. If you remove the ZENworks partition from a Windows NT, Windows 2000, or Windows XP machine windows will no longer boot. You should only remove the ZENworks partition if you are restoring a new base image to the workstation. Slide

IMG Dump Command Lines img dump [geo]
Displays all partitions on all supported drives on the computer. Some partitions, such as the ZENworks partitions and COMPAQ configuration partitions, are protected and will not be displayed. Geo – Optionally displays the geometry and capacity of all supported storage devices on the computer. Slide WorkstationE (img dump geo)

IMG Information Command Lines img info hardware img info zisd
Hardware – Displays all detected hardware on the computer. This information is sent to the proxy server during automated operation and is used to determine which (if any) server package policy will be applied to this computer. Zisd – Displays the image-safe data stored on the computer. This information is assigned by the proxy server according to the active policies. It is restored to the Windows registry by the Image-Safe Data Agent the next time the computer boots to its operating system. Slide workstationE (img I z)(img menu)

Scripted Images 1 OS Upgrade with Data partition (98-XP)
Re-Image OS Partition Data Partition remains intact Custom file from audience #This script will upgrade the system partition to Windows XP # but preserve the user data on drive D: #First, we delete the existing system partition img pd1 #Second, we create a new, empty partition and set it active img pc1 fat32 img pa1 #Finally, we fill the new system partition with Windows XP img rp //img_demo/sys/images/winxp a1:p1

Show 98 Show edit user data Reimage partion 1 Show now 2000 and still can access user data

Scripted Images 2 Resizing Partition to fit
Delete all destination partitions Resize image to fill drive #This is a simple script to expand a single partition to the full drive #Delete all partitions img pd1 img pd2 img pd3 img pd4 #Create a new partition img pc1 fat32x img pa1 #Restore the image img rp //img_co/sys/images/win2k a1:p1 #This is a simple script to expand a single partition to the full drive #Delete all partitions img pd1 img pd2 img pd3 img pd4 #Create a new partition img pc1 fat32x img pa1 #Restore the image img rp //img_co/sys/images/win2k a1:p1

Scripted Images 3 Bash shell scripting
Menu to select which image to deploy Define action based on user selection #This is a sample menu to show how to write an interactive menu #for advanced users. This could be implemented as a scripted image #object. # #The user is presented with a list of suitable images for his computer. #Set a few variables export SRV= DEFAULT=9 #Paint the user menu and screen header: echo -en "\n\n\n" echo -en " Novell ZENworks Image Selection Menu\n\n\n" echo -e "Choose an image from the following menu:\n" echo -e " Complete systems:" echo -e " Windows XP with applications" echo -e " (Winzip, Adobe Acrobat, and Ftp utility)" echo -e " Windows 2000 (Professional Edition) with applications" echo -e " (Winzip, Adobe Acrobat, and Ftp utility)\n" echo -e " Operating systems (no applications)" echo -e " Windows XP" echo -e " Windows 2000 (Professional Edition)" echo -e " Windows 98se\n" echo -e " Applications" echo -e " Winzip, Adobe Acrobat, and Ftp utility" echo -e " Microsoft Visual C++" echo -e " Apple Quicktime v5.0" echo -e " Abort imaging\n\n" echo -n "Choose an option: " read userChoice #Set the default answer to the option for rebooting to the OS if [ $? != 0 ] then echo -e "\nSetting choice to default ($DEFAULT)" userChoice=$DEFAULT fi #Now define the actions, depending on the user's choice. # This structure should be easily modifiable for customization in your # network case $userChoice in 1 ) #commands for selecting option 1 img rp $SRV //img_co/sys/images/winxp img rp $SRV //img_co/sys/images/addons/winzip img rp $SRV //img_co/sys/images/addons/acrobat img rp $SRV //img_co/sys/images/addons/ftp_run ;; 2 ) #commands for selecting option 2 img rp $SRV //img_co/sys/images/win2k 3 ) #commands for selecting option 3 4 ) #commands for selecting option 4 5 ) #commands for selecting option 5 img rp $SRV //img_co/sys/images/win98 6 ) #commands for selecting option 6 7 ) #commands for selecting option 7 img rp $SRV //img_co/sys/images/addons/vc_run 8 ) #commands for selecting option 8 img rp $SRV //img_co/sys/images/addons/qt_run 9 ) #commands for selecting option 9 * ) #commands for unknown selection echo "You chose an invalid option" esac

Scripted Images 4 New possibilities with TFTP Color Menu using pdmenu
Augment Linux environment Color Menu using pdmenu - pdmenu #This script will down load the menu utility and a menu file, then execute them #Download the menu utility and the menu script (using 'here' documents) export IMG_SERVER= tftp $IMG_SERVER << !cmds! bin get extras/pdmenu /bin/pdmenu get extras/demomenu.txt /demomenu.txt quit !cmds! chmod +x /bin/pdmenu crlf /demomenu.txt /etc/pdmenurc pdmenu -c /etc/pdmenurc

Hardware Independent Images
slide

Hardware Independent Images
Verify the HAL: Q and Q216551 Install Operating System, Patches, Novell Client for Windows, and NAL Run SYSPREP /PNP /NOSIDGEN to prepare the image 1.1 allows for different drive types Create a SYSPREP.INF Create a CMDLINES.TXT Includes SYSPREP.EXE –clean to disable disk drivers not used Includes ZISWIN.EXE to restore image safe data Includes ZCNC.EXE /SN /F to pull serial number for name Create the image slide

Build Scripts Slide lewing@isc.tamu.edu and The GIMP if someone asks
Here are the results of an idea acquired from discussions on the linux-kernel mailing list, and an initial suggestion by Alan Cox. Feel free to do whatever you see fit with the images, you are encouraged to integrate them into other designs that fit your need. Comments suggestions are also welcome, so please tell me what you think of these. I suggest that you look at some of the other images available with integrated text. The backgrounds of these images are random colors (if your viewer doesn't support transparent gifs). This is because I want to be able to keep the outline clean (except when blending into a scene or title bar). Each in-line image is now also a link to the corresponding gif so that they are more easily retrieved. The images I actually work from are tifs which I'll make available if there is interest. Neal Tucker was kind enough to provide a scalable vector based postscript version of the black and white penguin. Permission to use and/or modify this image is granted provided you acknowledge me and The GIMP if someone asks. Larry Ewing

ZENworks Linux Build Scripts
Made available due to user requests to modify environment Not supported by technical support However, they are extremely useful Available only from CoolSolutions Build scripts allow you to build modified resource files Must be used on a full installation of Linux Slide Modifying the resource files in linux enviroment for what we use to make CD’s and diskettes that you can use to install

Build Script Components
Build area Staging area that mirrors ZEN imaging environment Build scripts uses the build area to create resource files Bootcd.iso linux.1 and linux.2 root.tgz… Boot scripts Controls the Linux boot process Slide LinuxWorkstation A Build area: Staging area that mirrors ZEN imaging environment on a full Linux install. = Build scripts Boot scripts – controls the way linux boots

Build Script Documentation
Examples of things you’ll find documented Boot process for ZENworks Linux How boot scripts determines which Lan driver to load Where look Order searched How Self-Updating mechanism works Detailed description of boot scripts Changing the boot menu contents Slide LinuxWorkstation A How boot scripts determines which Lan driver to load Where look Order searched

Common Modifications Change bash prompt Change boot menu
Force LAN driver to load….. In 10 MB half-duplex (driver.conf) In specific order (nwDriverList) Add a utility / driver Set user environment variables Limited only by your imagination Assigned color menu to chewey Export zen

Changing the boot menu….

Determining LAN drive to load
Order of attempt /bin/driver.conf Pcmcia drivers Located in $MODPATH/pcmcia Drivers listed in /etc/nwdriverList PCI/ISA drivers Located in $MODPATH/net Force driver selection Customize driver.conf /drivers directory on CD or Disk 3 Create drivers.conf and /drivers and net??? So that can demo as go…. Demoing on Hewey

Customizing environment variables…

Customizing Boot CDs slide

Custom Boot CD’s Boot to a Linux distribution (RedHat, Caldera, etc)
Mount the ISO file mount –o loop <path to iso> <mount point> Copy contents to an empty directory Decompress the INITRD.GZ file gzip -d INITRD.GZ Mount the INITRD file mount –o loop <path to file> <mount point> Slide Workstation A

Custom Boot CD’s (Cont.)
Create your new script and make it executable, add additional files Do not add the image file This is loaded into a RAM drive when Linux boots Edit RUNME.S to load your script Unmount the INITRD file umount <mount point> Compress the INITRD file gzip INITRD Slide Workstation A

Custom Boot CD’s (Cont.)
Copy image file to the directory (if applicable) Make a new ISO image CD to your directory mkisofs -o <path and file for ISO file> -b isolinux.bin -c boot.catalog -no-emul-boot -boot-load-size 4 -boot-info-table Now cut the CD and test it Slide WorksstationA

Imaging Resources slide

ZENworks Prometheus… Multicast enhancements Speed enhancements
Simultaneous Server multicast Manually start Multicasting from server Speed enhancements XP support slide

More Information www.novell.com/coolsolutions/zenworks
Imaging Vault Lab Guide Troubleshooting imaging ZFD3 Image Engine Command-line Parameters and Troubleshooting Tips Enable Debug Logging for Imaging “Drakes Rack in Lab” slide Good place to cover some of the basic imaging tools Boot disk creator Image explore: open demonstrate, existing images compressed!! Boot disk creator: show and when would need PXE emulation disks Booting from a set of Linux boot floppies Booting from a Linux CD Booting from a local linux partition Booting to the Network Image safe data: p454 ZISD: ZISD NDS object… which DLL it’s calling, see notes from class

Advanced Technical Training
ZENworks for Desktops iFolder & OnDemand in-depth architectural reviews support issues advanced enterprise solutions highly technical training: lecture & hands-on labs slide

Imaging Tools ZENworks Image Explorer (IMGEXP.EXE)
ENGL: ZENworks Computer Name Changer (ZCNC) Change computer name of the workstation Pull serial number of the workstation (WMI) Free ENGL: ZENwork Wake on Lan (ZWAKE) ZISCLEAR - Clear workstation ZISD Downloadables ZENworks Image Explorer (IMGEXP.EXE) Compress existing images 40-60% Exclude files & folders Add/Delete files on image (applies to all variants) Edit the Registry with .REG files Slide ENGL image if have time – Workstation e assign image if created Slide Console1 (IMGEXP – trailer) Good place to cover some of the basic imaging tools Boot disk creator Image explore: open demonstrate, existing images compressed!! Boot disk creator: show and when would need PXE emulation disks Booting from a set of Linux boot floppies Booting from a Linux CD Booting from a local linux partition Booting to the Network Image safe data: p454 ZISD: ZISD NDS object… which DLL it’s calling, see notes from class

Secrets of ZENworks® Imaging and Preboot Services – TUT214

Similar presentations

Presentation on theme: "Secrets of ZENworks® Imaging and Preboot Services – TUT214"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Secrets of ZENworks® Imaging and Preboot Services – TUT214

Similar presentations

Presentation on theme: "Secrets of ZENworks® Imaging and Preboot Services – TUT214"— Presentation transcript:

Similar presentations

About project

Feedback