WolfPrep

1
WolfPrep

• http//microsys.unity.ncsu.edu/wolfprep
• Please set your cell phones and pagers to
• SILENT ALERT out of courtesy to your colleagues.
• Did you sign in?

2
What were going to cover

• What is WolfPrep, and why do I want it?
• Imaging vs. scripting when is each appropriate?
• How do I get started?
• How do I customize WolfPrep?
• How can I use just the scripting portion?
• How can I set up an entire lab at once?
• How do I handle restore images?
• When should I make my own image?
• Where can I get more information?

3
What is WolfPrep, and why do I want it?

• WolfPrep is ITDs way to configure and maintain
  one or more Unity/Windows workstations
• It is intended to provide hands-free installs
  set up your configuration, start the process and
  walk away, return to fully configured
  workstation.
• WolfPrep separates imaging and scripting.
• It efficiently delivers a consistent image
  suitable for large deployment of similar machines
  (like labs).
• It allows common settings to be applied
  NON-DESTRUCTIVELY to existing workstations with
  scripting.
• The scripting phase runs for both imaged and
  non-imaged installs, ensuring consistency for
  core components and customizations.

4
Maintains current features, and gets better

• We introduced the ability to create a local
  restore image on each PC in 2001 using Ghost.
• Now, with Zen imaging, you can have multiple
  local restore images, that you control remotely.
• In the Ghost/DOS environment, the restore
  partition was limited to 2 GB.
• Now, with Linux-based Zen imaging, you can have a
  restore partition of any size. The new default
  is 4 GB recall there is compression.
• We now support both Windows 2000 and (starting
  Summer II 2004) Windows XP.

5
Better hardware support

• The WolfPrep CD-ROM uses Linux to detect what
  devices are installed on a workstation, and copy
  the appropriate Windows drivers to the C drive.
• Windows XP should quietly just install any new
  hardware found by Linux.
• Windows 2000 will still launch the Found New
  Hardware Wizard, but at least you wont have to
  use a separate driver CD/Zip/floppy.

6
WolfPrep updates this core software (on both
imaged and script-only installs)
7
Software available in the NAL

• Over 200 software products associated with
  OUsers in NCSUNDS
• Licensed for students, faculty and staff
• Not limited to ITD offerings

some exceptions include MS Office, Nero, and
other per seat licenses
8
How do I get started?

• Review the documentation -) http//microsys.unit
  y.ncsu.edu/wolfprep
• Subscribe to the WolfPrep email
  listhttp//lists.ncsu.edu
• The first step is always to register an IP
  address range to get a WolfPrep template!

9
Templates
10
Getting started with templates

• Step zero is requesting a WolfPrep template for
  each lab/group of similar machines
• You must provide the IP addresses for each of
  your WolfPrep templates
• WolfPrep does all customization based on IP
  address
• See Getting a new config at http//microsys.uni
  ty.ncsu.edu/wolfprep/newconfig.html
• If you do not have a template, you will have a
  mess.

11
What happens with no template?

• Bad things.
• The workstation gets lost and is placed in the
  Lost and Found NDS container.
• It gets a default, Unknown template.
• Wrong (or no) admin password.
• End user can see that its set up incorrectly!
• Youll need to perform special steps (or
  re-image) in order to apply a different template
• Fix is detailed in Remedy solution 3015

12
What's in a template?

• A template lets you customize a machine or group
  of machines.
• Customizations include
• Administrator password custom security settings
• Appearance of the Ctrl-Alt-Del bitmap and the
  information displayed on the background bitmap
• Printers that get installed the default printer
• Registry changes you'd like to make
• Files you'd like to copy
• Executables you'd like to run
• Security settings, file and registry permissions
• Templates consist of 2 parts file system and
  NDS. Most customization is done in the file
  system.

13
How does WolfPrep use the template?

• When the WolfPrep script runs, it checks your
  machine's IP address and finds its associated
  template.
• The machine's template tells WolfPrep where to
  find your settings and customizations in NDS and
  in the file system
• The WolfPrep common settings are applied first,
  then your customizations on top. Your settings
  always take priority.
• Same template is used with script-only or imaged
  installs.

14
Templates File system

• Templates are stored in NetWare file space.
• In the file system, you get a departmental
  folder. For example \\it_dept2_server\dept2\LabSe
  tup\MyCollege\MyDept
• Within that folder, you can have multiple
  templates, one for each lab/group of similar
  machines. For example\LabSetup\MyCollege\MyDept
  \Room101\LabSetup\MyCollege\MyDept\Faculty

15
Templates File system details

• We set you up with default files/folders in this
  directory
• You customize as you like
• Details on each file/folder, what it does, and
  how you can customize it are documented at
• http//microsys.unity.ncsu.edu/wolfprep/setup.html
  
• Lets take a look at some of the things you can
  customize in the file system.

16
Default Administrator Password

• If an encrypted password file called
  "admin-Win2k.ssp" or "admin-WinXP.ssp" exists in
  the template directory, the "Administrator"
  password will be set to the contents of the file.
• Encrypted password files are created with the
  Generate Password utility. This utility is
  located at L\ITD\Tools\genpass.exe
• The passwords encrypted with Windows 2000
  workstations cannot be used to set passwords on
  Windows XP workstations, and vice versa. This
  will be addressed in a future WolfPrep update,
  but for now, you need to encrypt the password on
  the platform you intend to use.

Our gratitude to Jason Young in COE for creating
the genpass program.
17
Login Prompt

• You can customize the image that appears before
  users log in. This is the image that asks the
  user to press Ctrl-Alt-Delete.
• If a bitmap image file called "login.bmp" exists
  in the home directory, that image will be
  presented to users when they log in to the
  workstation

18
Support Information

• The information that appears when the "Support
  Information" button is clicked from the System
  Properties page can be customized. If a file
  called "oeminfo.ini" exists in the home
  directory, the information it contains will
  appear when "Support Information" is clicked.
• The file OEMINFO.BMP is used for the graphic

19
Background Info During Login

• The file login.bgi controls what is displayed
  on the computers background BEFORE a user logs
  in, and can contain information like the support
  pack installed, the computers name, as well as
  static contact information.
• To build "login.bgi" run L\itd\tools\bginfo\bginf
  o.exe .
• You need to be sure that the "Display at login"
  checkbox is checked. BGInfo seems to fail at
  overwriting an existing .bgi file, so I always
  delete the existing file before saving.
• The file LOGIN.BGI is only read by WolfPrep
  during the setup process, so to update the
  background after a new service pack was applied
  one would need to login as "WolfPrep" again.

This is computer BLOSSUM from image dated
20040606Its a 1.5 GHz Intel Pentium 4 with 768
MB of Memory running Windows XP Service Pack
1For help, send e-mail to Help_at_ncsu.edu or call
515-4357
20
Install Printers

• PRINTERS.TXT
• This plain text file (you can create it with
  "Notepad") contains a list of all the WolfCopy
  (or other NDPS) printers you want configured. A
  line starting with a semicolon () is considered
  a comment, and ignored. The queue names for
  WolfCopy printers are listed at
  http//print.ncsu.edu/listofprinters.php
• These short queue names are combined with the
  "context" identified in PRINTCFG.BAT described
  below to locate the NDS object and install the
  NDPS printer.
• If you dont specify a context,
  .Printing.Services.NCSU is assumed.
• For non-NDPS printers, you can script their
  installs with commands in the "CustomRun"
  directories

• lines with semicolons are comments for
  humans 2413 D.H. Hill Library Printer 1
  hp8100 6 cents/pagedhl-2413-1 2413 D.H.
  Hill Library Printer 2 hp8100 6 cents/page
  dhl-2413-2 2413 D.H. Hill Library Color
  Printer 1 hp8500 60 cents/pagedhl-2413-color1

21
NDPS Details

• File PRINTCFG.BAT
• This file controls which printer should be setup
  as the default, and where to locate NDPS printers
  in the NCSUNDS directory tree. It's an
  old-fashioned DOS batch file (.bat) that sets two
  environment variables, PRINTCX and DEFAULT. The
  PRINTCX variable should be set to the fully
  qualified (beginning with a "dot") NDS context to
  look for printers. Unless you are hosting your
  own NDPS printers, this will be
  .Printing.Services.NCSU, which is the default and
  can be safely omitted. In a .bat file, lines
  begining with REM are REMarks, ignored by the
  computer and intended for humans to use in
  documentation.
• The DEFAULT environment variable identifies the
  printer to use as the default. It will place a
  small command in the "Startup" folder for "All
  Users" to force this printer to be the default at
  login.

• _at_echo off rem SAMPLE printer configuration
  forrem labsetup accountsrem Copy this file to
  your lab setuprem account's home dir (M\)rem
  and modify to your satisfaction
• rem You will also need a file namedrem
  PRINTERS.TXT in yourrem lab setup accounts
  homerem directory (M\) that has a listrem of
  printers to install, one perrem line
• rem Where to look for printers byrem
  defaultset printcx.Printing.Services.NCSU
• rem What printer do you want to berem the
  default?set defaultdhl-2413-1

22
Video Resolution

• You can control the default video resolution and
  refresh frequencies for multiple monitors by
  configuring a multires.ini file.
• More information about the "Multires" application
  used here can be found on the web at
  http//entechtaiwan.com/multires.htm
• In the section names in multires.ini, the number
  indicates which monitor the section controls. So,
  Refresh1 and Last-1 refer to the first
  monitor, Refresh2 and Last-2 would refer to a
  second monitor, and so on.
• You can require that a human click "OK" and
  accept the new settings by setting
  Confirmation1.
• The values in Last-1 control the settings for
  the first monitor. The BPP32 in the example
  above sets the Bits Per Pixel for the 1st display
  to 32.

• Refresh1Confirmation0
• Last-1X1280Y1024BPP32Hz60

BPP Number of Colors32 Millions16 Thousands
(HiColor)8 256 colors
23
Programs/Script to Run

• You can launch any program or script by placing
  it (or a shortcut to it) in a directory named
  "CustomRun
• If possible, you should configure anything
  launched from CustomRun for a silent, unattended
  install. You should also configure to not do a
  restart, if possible (some installers don't offer
  the option, and just reboot if they need one). If
  an installer does need a reboot, you can indicate
  to Wolfprep that a reboot is needed by creating a
  file C\RebootMe.txt When Wolfprep completes it
  will automatically reboot if it sees this file.
• Be aware that your script or installer may be
  called several times. You may want to set a
  registry key under HKLM\Software\NC State
  University\WolfPrep\AlreadyRun and check to see
  if your installer/script/app has already run to
  avoid running it more than once.
• In addition to "CustomRun" there are
  "Win2k\CustomRun" and "WinXP\CustomRun" folders.
  The programs and scripts held in these
  directories are executed ONLY for the particular
  operating system (WinXP or Win2k). This allows
  you to apply a patch intended only for a
  particular OS.

24
Processing Order

• Wolfcall runs L\itd\labsetup\CommonRun first,
  then runsyour CustomRun files.
• "RUN" is run before "Reg.
• ALL WolfPrep changes can be found under
  L\ITD\LabSetup
• Your settings take precedence.
• You dont have to do anything to just take the
  ITD defaults.

25
Making Registry Changes

• Wolfcall reads everything in L\itd\labsetup\Commo
  nReg into the registryfirst, then reads your
  CustomReg, so CustomReg overrides the general
  settings.
• This is an excellent place to set your ZENLAB
  environment variable to control custom login
  scripts, or perform any (HKLM) registry tweaks.
• In addition to "CustomReg" there are
  "Win2k\CustomReg" and "WinXP\CustomReg" folders.
  Any .reg files held in these directories are read
  ONLY for the particular operating system (WinXP
  or Win2k). This allows you to apply a
  configuration intended only for Windows 2000 for
  example.

26
Installing Files or Data

• If you have any data or program files that you
  want installed on every workstation in a
  particular configuration group, you can place
  them under the "CopyFiles" directory to have them
  automatically installed.
• A subdirectory for each drive letter to which you
  want files copied is created under the main
  "Copyfiles" directory. If you've partitioned your
  target computers for multiple drive letters, you
  can enumerate them here -- most folks will have a
  single directory "C" to represent the C drive.
• There is a special directory SystemRoot which
  can be used to place files in the Windows System
  Root directory. CopyFiles\SystemRoot is
  preferred to CopyFiles\C\WinNT or
  CopyFiles\C\Windows because it will always place
  files in the desired location regardless how the
  machine was initially installed.
• Once again, in addition to "CopyFiles" there are
  "Win2k\CopyFiles" and "WinXP\CopyFiles" folders.
  Anything held in these directories are copied
  ONLY for the particular operating system (WinXP
  or Win2k). Don't forget to include the drive
  letter or SystemRoot subdirectories!

27
Controlling Windows Security

• To apply custom security configurations to your
  workstations, place a file named "Security.INF"
  into the operating system directory (Win2k or
  WinXP) of your configuration template.
• You create security INF files using the Microsoft
  MMC tool, and the "Security Templates" plug in.
• Be sure that you create your security templates
  with the same operating system (Win2k or WinXP)
  that the target computers will be using.

28
Common Security Settings

• In most cases, you will not need to apply
  additional security settings beyond the defaults.
  
• WolfPrep will apply the security settings in
  L\ITD\LABSETUP\OSNAME\MinZenRights.INF first,
  and then your customized OSNAME\Security.INF
  file. This allows you to override any settings
  you desire.
• The MinZenRights.INF is the minimum rights needed
  to successfully use the Zenworks desktop. It
  includes granting rights to users to start and
  stop the NAL services, registry rights the
  HKLMSoftware\Novell\Workstation Manager, and
  file system rights to NALCache. Refer to the
  actual INF file for specifics.

29
Templates NDS

• We set up a container for your workstations in
  NDS based on your template's name
• Container is located under .Computer.UsersIn our
  example, the NDS containers for MyDept would be
• .Room101.MyDept.MyCollege.Computers.Users.Faculty
  .MyDept.MyCollege.Computers.Users
• Every workstation is represented by a workstation
  object in NDS (automatically)
• This allows your workstation to get access to Zen
  applications (Unity or your own), and to use
  remote Zen imaging if you choose

30
Recap

• Configure files in your template directory, and
  they will be applied to all computers whose IP
  addresses match that template when the WolfPrep
  scripts run.
• If possible, have your programs install in
  silent or unattended mode.

31
Ready to Move On?

• Questions on how to accomplish tasks using a
  WolfPrep template?

32
Script-only installs

• This is so easy

33
Running just the scripting

• To run WolfPrep scripts without using any
  imaging, you must have Client-32 installed
• Dont forget to request a template first!
• Login to NCSUNDS as
• Username WolfPrep
• Password setmeup
• A version of WolfPrep that doesnt require
  Client-32 be pre-installed is coming in version
  2.0 (Due Fall 2004).

34
Imaging
35
When should I use imaging?

• Imaging is good for new machines, lab machines,
  or any machine without data someone loves. It
  completely wipes the hard drive and installs
  fresh.
• Imaging is good when you have large numbers of
  similar machines you wish to get going quickly
• Imaging is required to create a restore
  partition
• The WolfPrep scripting phase runs at the end of
  the WolfPrep imaging process, for updates made
  after the image was burned.

36
When should I use script-only installs?

• The WolfPrep script allows you to give an
  existing machine access to Unity resources
  without a reinstall, preserving local data and
  software
• You can use the WolfPrep script in situations
  where hardware support is an issue with imaging
  (HAL types)
• Scripting is a good way to be sure all core
  software is updated to the latest release can
  use to update imaged systems too.

37
The WolfPrep Images

• The traditional Lab Kit comes in four flavors

The image ITD is using in a particular semester
is also known by default
38
Can I use my own Zen imaging server?

• Yes, if you like.
• You will need to override the setting BASE in
  the settings.txt file, which is located on the
  WolfPrep CD-ROM.
• settings.txt is a misnomer, it's really a bash
  script. Novell folks wanted something to open in
  Notepad when they double-clicked it.
• Zen patch levels are critical for success.
  Requires attention.

39
Imaging with the WolfPrep CD-ROM

• You will need a WolfPrep CD-ROM to boot from.
• An ISO is available on the ITD SiteLicense
  volume\\ncsunds\ncsu\services\sitelicense\ITD
• The file name is WolfPrepYYYYMMDD.isoExample
  WolfPrep20050608.iso
• Details on access to SiteLicense can be found at
  in Remedy solution 2575
• Use your favorite CD burning application to make
  a physical disk.

40
WolfPrep Imaging CD-ROM Preboot Menu
Choose system/configuration to boot... tools
DOS tools and utilities mem Start Memtest86
v3.0 a Boot from first floppy drive (drive
0h) q Skip CD-Rom boot (boot next
device) The following could nuke your primary
disk! manual Manual Zen Imaging (4.0.1sp1b)
lilo Reinstall ZEN Partition boot loader
install Install Zen Boot Partition disable
Disable Zen Boot Loader enable Enable Zen Boot
Loader backup Backup to imaging partition
wolfprep Install Default WolfPrep
image Pressing Enter defaults to item
"wolfprep Timeout 20 secondsF2Help
41
Installing an image on one machine
42
Initial boot

• Insert the WolfPrep CD-ROM, and boot youll get
  the WolfPrep CD-ROM Preboot Menu.
• Wait 20 seconds, and option wolfprep will run,
  downloading the default image and drivers. ?
• To override the image, use something like
• wolfprep IMAGEwinxp
• IMAGE is uppercase, no spaces surrounding
• After the image is downloaded, youll get
  instructions to reboot, followed by a Linux
  prompt.
• Eject the CD-ROM, then reboot to continue (enter
  reboot, or press Ctrl-Alt-Del) NOTE You
  should NOT eject the CD-ROM before rebooting if
  you are going to make this machine be a multicast
  master. Well talk about that shortly.

43
After the first reboot

• Sysprep factory will run, to detect any and all
  new Windows drivers install by linux
• Dont interrupt this process, even though a
  desktop appears, things have just begun!
• The system will reboot itself at the end of
  factory mode.

Factory Preinstallation
?Updating Installed Drivers?Optimizing Shell
Recording OEM preferences Waiting for Plug and
Play Launching Sysprep
44
After the second reboot

• Microsoft Sysprep will run and
• Assign new security identifiers
• Install Plug and Play hardware
• Prepare to run WolfPrep scripts on the next reboot

45
During subsequent reboots

• Wolfprep will login to the network, and run the
  scripting phase.
• This will update anything changed since the image
  was made. Sometimes, multiple reboots are
  required!
• Passwords, bitmaps and other customizations are
  all set during this step.
• All actions are recorded in C\WolfPrep.log
• Last reboot? prompt often hidden under NAL
  (will time out in 5 min)
• On final reboot, you have a completely setup
  workstation.

46
Local Backup Images
(A short hypertext moment)
47
Making a local backup an optional additional
boot

• If youre using a restore partition, you should
  re-insert the WolfPrep CD-ROM at this point
• Boot it, and choose backup from the WolfPrep
  CD-ROM preboot menu
• This will create a backup of the pristine hard
  drive that can be restored from at any time.
• Backup is automatically named with todays date.
• NOT A GOOD IDEA to start all your workstations
  with the CD and walk away! (remember that 20
  second timeout!)

48
Background The backup partition

• Zen imaging is controlled by NDS. You can make
  and restore images remotely using the ConsoleOne
  utility.
• On every bootup, Zen boots its linux partition
  and checks to see if youve commanded it to
  perform a task, such as restoring from a backup
  image.
• If one or more backups are detected, the user
  will get a menu similar to the following

• Select an option by typing a number followed by
  return
• 0 Continue booting1 Backup-Made-2004-03-202
  Backup-Made-2004-06-06
• Please make a selection
• Bootup will continue automatically after 15
  secondsselect

49
Why have a backup? Uptime!

• Any computer user can verify any NAL
  application to re-install it, and this keeps
  even busy labs running most of the time.
• Sometimes, you want to restore the machine to
  just like when it was installed. The backup
  partition allows this, even when labs arent
  staffed or monitored.
• With multiple backups and remote control of
  imaging, we can have multiple OSes or
  configurations and automagically install them
  from afar.
• Backup partitions are not available on scripted
  upgrades.

50
Summary Installing an image on one machine

• Boot Wolfprep CD-ROM
• Wait 20 seconds for preboot loader to default to
  WolfPrep (or hit return, or select an image)
• After the images load, eject the CD-ROM and
  reboot
• Find something to do while the machine reboots
  itself at least three times. (Youre done when
  you see your custom login bitmap.)
• Re-boot with the CD-ROM, and select backup if a
  backup is desired.

51
Common Problems

• No template established (remedy solution 3015)
• Didnt set an admin password in my template
  (remedy solution 2927)
• No DHCP (really need DHCP)
• SATA hard drives (not yet supported)

52
Can I make my own images?

• Yes!
• Sysprep is a pain. Explore customizing first,
  using CustomReg CustomRun components of your
  WolfPrep templates in particular.
• http//microsys.unity.ncsu.edu/wolfprep/makeimage
  .html has complete info on making your own image,
  while including all expected settings.
• You'll need to arrange for space with us if you
  don't have your own Zen Imaging server.

53
Can I use my own Zen imaging server?

• Yes!
• You will need to override the setting BASE in
  the settings.txt file, which is located on the
  WolfPrep CD-ROM.
• settings.txt is a misnomer, it's really a bash
  script. Novell folks wanted something to open in
  Notepad when they double-clicked it.
• Zen patch levels are critical for success.
  Requires attention.

54
Installing an image on multiple machines

• Multicast!

55
Images delivered via multicast
Many, Many Workstations

• Images are large. For a 1.2 GB image to be
  delivered to 10 workstations, 12 GB must be sent
  on the wire.
• Multicast cuts traffic tons by sending the data
  once, to all the stations that want it.
• With multicast, for a 1.2 GB image to be
  delivered to 10 workstations, closer to 1.2 GB
  must be sent on the wire.
• You will notice a big difference in imaging times
  if you multicast!

Multicast Server
56
How to multicast

• Bring down an image on one machine, as discussed
  previously in the Initial boot slide. This
  will be the multicast master
• Remember not to eject the CD-ROM!
• Boot the "master" again from the WolfPrep CD-ROM.
  This time select "manual" mode.
• From the prompt (bash or ash) type img and
  press return to start the imaging menu.
• From the img main menu, choose "Multicast" and
  then "Master"

57
Make a session name

• Provide a unique "session name" that clients will
  use to locate the multicast master. If many
  multicast masters are running at once, the
  "session name" is used by the client to decide
  among them.
• Select how to start the transfer. You can have
  the multicast master start sending the image
  automatically either after a specified amount of
  time (e.g. after 10 minutes) or after a certain
  number of multicast clients attach (e.g. once 10
  clients are ready).
• We recommend you use the name of the lab you're
  imaging, or your login ID, or something else both
  unique and easy to remember.

58
Boot the client machines

• Once the master is ready, boot each client with
  the WolfPrep CD-ROM and select manual mode.
  Remember the 20 second timeout!
• Use the img command on each client to connect to
  your master session name. You can bypass the
  menus if you prefer, using a command like
• bash img session session_name
• Here, session_name represents the unique session
  name you've choosen for your master. Once the
  master starts the session (you can do this with a
  keystroke 'G' for Go from the master) the image
  will transfer to all the clients using multicast.

59
Multicast Summary

• Image one machine, the multicast master
• Boot master with CD-ROM in manual mode, select
  multicast master and set unique session name
• Boot remaining machines with CD-ROM in manual
  mode, and choose multicast slave from menu or
  use command line.
• After images are down, remove CD-ROMs, reboot,
  wait and make backups as in the single machine
  process.

60
Ready to Move On?

• Questions on how to get images onto workstations?

61
Final Few Slides
62
TimeLines

• Fall 2004, version 2.0Web ManagementNo
  Client-32 needed
• Jan 2005, version 2.5App Management via WebPXE
  (Boot from Net)
• Spring 2005, version 3.0Inventory management via
  web

63
Current Issues

• Linux CD-ROM doesnt support SATA hard drives.
  Working to build a custom kernel to address this.
• Need process to quickly match PnP id numbers to
  Windows drivers. New hardware is still a mystic
  process.

64
More Information

• The main WolfPrep docs are on http//microsys.unit
  y.ncsu.edu/wolfprep
• You can join the WolfPrep list on
  http//lists.ncsu.edu
• Info on creating your own Sysprep images, in case
  scripting just isnt enough for you, can be found
  at http//microsys.unity.ncsu.edu/wolfprep/makeima
  ge.html