Several Groups create their own images based on the ITD offering. With Wolfprep, there are two ways to customize the software initially installed, using the CopyFiles, CustomReg and CustomRun Folders in your setup template to install software on the initial computer boot, or repackaging an image with Microsoft's sysprep to change the initial image.
Please note! It is not necessary to make your own image! This information is provide to assist folks who need to extend the WolfPrep base image, but you do not need to do so if your needs are met by the contents of the basic image!
Installing software during WolfPrep scripting
The easiest method to have small amounts of software installed is to use the CopyFiles, CustomReg and CustomRun folders in your setup template. When the scripting portion of WolfPrep is active, programs and settings can be installed to each machine using a particular setup template.
For very large packages, or for packages that are difficult to install without intervention, this method may not be sufficient. It is generally quicker to setup and more flexible than making an image.
Making a Custom Image
If you have a lot of additional software, having it installed in your "base" image can be more efficient (you can use multicast to get the image to the workstations) It's also helpful if you have applications that have to be hand "tweaked" to work in your environment, and so an unattended installation isn't desirable.
To create your own custom image, you install all the packages and settings that you desire, remove anything you don't want included in the image, use the Microsoft SysPrep utility to package the machine for distribution, and then make an image of the hard drive.
The Microsoft SysPrep utility prepares a hard disk for duplication by removing any workstation specific information (like IP addresses or security identifiers) and configuring the machine to run a "mini-setup" on the next boot. Mini-setup is quicker (but less flexible) than Windows Setup, and it's job is to identify the devices installed and re-generate a new machine identity for the imaged workstation.
Sysprep is a difficult and unforgiving process. Microsys cannot provide you support with custom images.
Process
Start from a "clean" install
Starting from either the ITD image with applications, or just the basic OS, install the packages you desire on a workstation.
On the WolfPrep CD-ROM, run the command file SysPrep\cleanit.cmd to both prepare the workstation for imaging, and to copy the appropriate Sysprep files to C:\Sysprep
The "cleanit.cmd" command file deletes unneeded files to make images smaller. These files are listed in the \Sysprep\ToDelete.txt (all platforms) , \Sysprep\WinXP\ToDelete.txt (XP only) and \Sysprep\Win2k\ToDelete.txt (2k Only) files.
Registery entries are made from the .reg files stored in "CommonReg" folders under the Sysprep directory.
Optional: add registry keys to control WolfPrep during the scripting phase.
There is an "AlreadyRun" registry key
HKLM\Software\NC State University\WolfPrep\AlreadyRun
that an installer launched from "CustomRun" can check to see if it's already been installed, and skip installation at every reboot during the WolfPrep process. This really speeds up the "CheckForWelchia" style apps which have to do involved scans of the hard drive to complete.
You can skip the installation of AFS/WolfCall/KfW, Client32, Zenworks, SAV or IE by setting the registry key listed under HKLM\Software\NC State University\WolfPrep\AlreadyRun. Create a REG_SZ key with a value of "Yes" to skip installation of a particular component. See the release notes for more information and the proper key names.
Clean up unnecessary files
The C:\Sysprep\cleanit.cmd is used to un-register the workstation from NDS, clear the event logs, and delete any unnneeded files before the image is made.
Be aware that the last step of cleanit.cmd is to set a blank password for Administrator, which is a real security issue. Sysprep needs a blank password to function. Since XP Service Pack #2, Windows won't allow network access using a blank administrator password, so this isn't the gaping hole it used to be.
Run Sysprep
This is best accomplished by closing any and all open windows, and going to Start|Run and entering the command "C:\Sysprep\dosysprep.cmd" Sysprep will shut the computer down when it is complete.
Windows XP needs special commands to prepare it to run Sysprep in "factory" mode, used to register any drivers downloaded by WolfPrep during the imaging process.
Use Zen imaging to make a disk image
Do not boot into Windows, or Sysprep will execute and run mini-setup, which you don't want to occur until you've transferred your master image to the client computers.
You can also use Ghost, ImageCast, or some other imaging product to make your disk image. If you do so, you may not be able to use the Zenworks based restore functionality. These instructions assume you're going to use Zen imaging to make your image.
Boot the computer using the WolfPrep CD-ROM. Choose "backup" to create a backup on your Zen imaging partition. It will be named "Backup-Made-YYYY-MM-DD"
Reboot with the WolfPrep CD-ROM once more, and choose "m" or "manual" from the pre-boot menu. You'll be presented with a linux bash prompt.
Issue the commands:
mount $ZENDEVICE /mnt/harddisk
cd /mnt/harddisk
to gain access to the backup on the hard disk, and change directories to where the backup image is kept.
The only utility that Novell provides us with to transfer the master image somewhere "safe" is old fashioned ftp. If you wish to transfer the master image to AFS space, you can ftp to the host "ftp.ncsu.edu" If you wish to transfter the master image to ITD provided Novell space, you can ftp to host "ftpnds.ncsu.edu" If you have your own Network Attached Storage box, file server, or desktop machine with ftp enabled, you can use that as well.
Assuming your destination is AFS, here are the command to transfer the master image off of the local machine. If you're storing the image elsewhere, adjust your ftp destination appropriately.
ftp ftp.ncsu.edu
(enter your userid and password when prompted)ftp> bin
ftp> put Backup-Made-YYYY-MM-DD.zmg
ftp> bye
Don't omit the "bin" command -- it is absolutely necessary to transfer the file in binary mode.
You can run a multicast session (with another reboot of the WolfPrep CD) right away.
Later, should you wish to multicast again, perform the ftp transfer in reverse (that is, use the command "get" instead of "put" to transfer the file from your ftp server and to the local hard disk). Restore the machine from the backup file (boot the hard disk, and select restore within the 15 second timeout). You can then either reboot and start Windows Sysprep if you're just setting up one machine, or boot the WolfPrep CD to have the newly restored data available for multicast master.
Sysnews
Unity Forums
Microsys Blog
Documentation