The NT side
Making an easy to refresh machine using GHOST, NT and
Z.E.N.works
This Document is a work in progress. It is as accurate as I can make
it without people having used the method to create a Lab Machine. If you
use this document and you have any comments, both positive and negative,
please let me know by mailing
me.
This document is in two parts. This is the NT side of things, there
is also a Z.E.N.works / NAL side
to the story.
This document assumes that you're using the other half of this document.
If not, read it so you know what I'm on about, then ignore it when you
know better. If I made any mistakes, let me know
by mailing
me, otherwise I'll just sit here thinking I invented the best thing since
sliced fruit bread in the morning.
Now the story.
This system was created to make student labs manageable. Students break
things often, either maliciously, or because of lack of knowledge. This
system aims to stop that.
First we create a PC that has only the operating system on it together
with the Netware Client. (Currently I'm using the one that comes with the
first release of Z.E.N., v4.30.410) The machine is created in such
a way that a user can choose to either start the OS, or refresh the computer
(using ghost). The refresh copies the image of the OS onto the OS partition
and reboots, giving the user the same choice.
This system will also work if you have applications installed on the
machine. The only down side is that the refresh will take longer. The method
I currently use takes three minutes. There is no network utilisation, so
you can refresh 500 machines in one go in three minutes.
If you were to install applications on the image, you will have to update
the image regularly, since updates come and go all the time :-( Different
users have different priveledges and needs, so we let NDS sort that out
with NAL, rather than let NT take care of it.
In fact as I write this, the user logging into one of these systems
is doing so with full administrator access, only they cannot run anything
other than what NAL gives them. (I am still attempting to find a file manager
solution, so the user can copy files between transfer volume, drive A:
and their home directory, I'm open to suggestions.)
This document describes the process of creating the OS.
Setting Up a Lab Machine:
- What You Need Before You Start
- Create A Partition for NT
- Install NT
- Install the Service Pack
- Install the Video Drivers
- Set Preferences
- Install NetWare Client (Z.E.N.works
client!)
- Setup DOS partition
- Setup NT so it can boot it
- Modify BOOT.INI
- Install DOS
- Make a BOOTSECTOR file &
Copy it into NTFS
- Remove Microsoft Networking
- Install GHOST
- Make
an Image
- Lock up the DOS files
- Test it all
Modifications to this document:
7 July 1998 - Added comments about files and preferences,
added LegalNoticeCaption and LegalNoticeText, added marker file, added
comment about Ghost of whole disk
12 June 1998 - Added how to remove Microsoft Networking,
updated version number to 1.1
- [Top] Getting
Started
- Windows NT workstation CD
- Windows NT boot floppies
- You can create these by running {NT CD}:\i386\WINNT /OX
- Access to Service Pack 3
- Access to Z.E.N.works client
- Bootable DOS Floppy with GHOST.EXE, FDISK.EXE, ATTRIB.EXE,
SYS.COM
- Video Drivers Disk
- About 1 hour (mostly for the NT install)
- [Top] Boot
from DOS
- Run FDISK
- Delete all partitions
- Create a PRIMARY DOS partition, 75% of the total size
- Insert NT Disk #1 and exit FDISK
- [Top] Install
NT
- Ignore the Video Drivers
- Install onto 75% partition
- Ignore 'Disk Damaged' errors and format as NTFS
- Choose "Custom Install"
- Don't create an Emergency Disk
- Choose All Components *except* "Windows Messaging" and "Communications"
- Install TCP/IP and IPX/SPX
- Add Client Services for Netware
- Use DHCP
- Make it part of a Workgroup (You'll remove MS networking later)
- GMT+8 (HongKong, Perth...)
- Boot Up after Install
- Don't worry about the Novell Login Stuff at this point.
- [Top] Install
SP3
- Don't Create an Uninstall Directory
- [Top] Boot
in VGA-mode
- Install S3-Virge_DX video Drivers
- [Top] Boot
in Normal Mode
- Set the Video Preferences
- Untick the Show Welcome Box and close it
- Close all Open windows, set preferences etc.
- Set Minimum Paging File Size to 100 Mb
- Set Maximum Paging File Size to 100 Mb
- Set Hardware Profiles wait to 1 Second
- Set Startup boot menu wait to 15 seconds
- Set "Automatically Reboot on STOP event" to ON
- [Top] Install
ZEN Netware Client
- Choose Custom Install
- Add the Remote Control Client (we may need it later)
- Trusted Tree: CURTIN_LAB (or CURTIN_UNI at a later stage)
- [Top] Boot
in Normal Mode
- Login to Workstation Only
- Launch Disk Administrator
- Create Primary Partition with the remaining 25%
- Commit Changes
- Assign Drive Letter I:
- Format it FAT
- [Top] Clear
READ-ONLY attribute for C:\BOOT.INI
- Modify C:\BOOT.INI so it looks like:
[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="ABACUS Lab - CEA"
C:\WINNT\BOOTSECT.DOS="Refresh Computer"
- Set READ-ONLY attribute for C:\BOOT.INI
- Modify settings for ABACUS Lab implementation
- The machine needs to have Workstation Manager setup and configured after
a refresh. To do this, a user must login at least once. The problem is
that this user has full priveleges until the setup is complete. Solution,
log the user out the moment they login for the first time. It's not pretty,
but after three months of attempting to make this work, I can only make
it work this way.
- Create a file C:\WS1STGO.ZEN
- echo.>c:\ws1stgo.zen
- Using REGEDT32 add the following values:
- LegalNoticeCaption:REG_SZ
- LegalNoticeText:REG_SZ
The text I have used for the caption is: Don't Panic...
The text I used for the text contains a line-feed. You need to paste
the content of the file lfcr.txt to make it do a
line-feed. This file contains two bytes and needs to be saved onto your
workstation in order for it to work properly...
The text itself is:
This computer has just been refreshed.
To complete the refresh you will need to log-in
twice."
- I copied three bitmaps to indicate that the machine is in refresh-state,
C:\WINNT\WINNT.BMP, WINNT256.BMP, NWELCOME.BMP. They basically contain
the normal image with "refreshing computer..." superimposed.
- Boot into DOS
- Transfer DOS to the disk
- SYS C:
- [Top] Copy
GHOST.EXE to C: (the FAT partition)
- Make C:\AUTOEXEC.BAT (Whole command on ONE line) (You can use: COPY
CON AUTOEXEC.BAT and type the line, press [Return], [F6], [Return]
to save.)
@GHOST -RB -NTN -NTIL -NTIC -BATCH -QUIET -SURE -CLONE,MODE=PLOAD,SRC=NTFS.GHO:1,DST=1:1
- Make C:\CONFIG.SYS
SWITCHES=/F/N
- [Top] Create
the file A:\BOOTSECT.DOS
- Create C:\TMP with the following text:
L 100 2 0 1
N A:\BOOTSECT.DOS
R BX
0
R CX
200
W
Q
- A:DEBUG < C:\TMP
- DEL C:\TMP
- Boot the machine into NT
- Copy A:\BOOTSECT.DOS C:\WINNT\BOOTSECT.DOS
- Remove Microsoft Networking
- Right Click on the Network Neighborhood
- Select Properties
- Select Services - Tab
- Remove Workstation Service - This also removes "Computer Browser"
- Remove Server Service
- Remove RPC Service
- When you close the Network Properties, it will ask you if you want to reboot,
say NO.
- [Top] Logout
(We're doing this, so the preference for the Student is to log-out, not
shutdown!)
- Insert a Bootable DOS floppy
- Press [Ctrl] + [Alt] + [Del]
- Choose Shutdown & Restart
- [Top] Run
GHOST to create an NTFS image of your machine
- Local/Server
- Dump partition(s) to image file...
- Set NTFS to Y
- Save As: NTFS.GHO
- Compress FAST
- Proceed
- Run GHOST again to verify the image (you're going to be using it for a
long time)
- Local/Server
- Check image file integrity...
- Choose NTFS.GHO
- Proceed
- [Top] Lockup
all the files on the DOS partition
- ATTRIB +s +r +h C:\*.*
- ATTRIB -s C:\GHOST.EXE
- [Top] Done
(actually, you'll want to boot off a DOS network floppy and copy your ghost
image to a server. (So when all hell breaks loose, you can recreate the
system :-)
v 1.2