|
|
| |
Installing Win2k |
|
| |
By Erik
Rozman
|
|
| |
Planning
Hardware Requirements(as
provided by Microsoft)
| |
Professional |
Server |
Adv. Server |
Datacenter |
| CPU(MIN/MAX NO.) |
133/2 |
133/4 |
133/8 |
133/32 |
| Memory(MIN/MAX) |
64MB/4GB |
64MB/4GB |
64MB/8GB |
64MB/64GB |
| Hard Drive(Total/Free) |
2GB/1GB |
2GB/1GB |
2GB/1GB |
2GB/1GB |
Windows 2000 should be easier to install from the
hardware angle since Win2K is fully Plug And Play(PnP). Problems can(and do)
arise if you are still using older non-PnP devices since they will try to
acquire a hard coded(set by a setup program or jumpers) resource(such as an
IRQ) that is preferred by a PnP device causing a conflict. The fix is quite
simple yet BIOS dependent- you should enter your BIOS configuration and reserve
the resource for the older non-PnP device causing the newer PnP device to
change its own preference-this should bring harmony to your hardware kingdom.
All Hardware should be on the Hardware Compatibility List(HCL) that is provided
by Microsoft both on the installation CD (SUPPORT folder) and on the web
(www.microsoft.com/hwtest/hcl).
Partitioning
When installing Win2K you should simply partition the disk in a way
that leaves most of it empty and create only the partition for Win2K, Later you
can decided how to partition then disk depending on your needs.
File
Systems
Win2K supports the following file systems:
If you want to be able to dual boot into older
Operating Systems (OS) you should use FAT or FAT32(depending on the operating
system you use. NTFS is not usable by any other operating system than Win2K or
NT, if oyu want to enjoy all the features provided by NTFS (Active Directory)
and you only load NTFS aware systems you should use NTFS. You can convert from
FAT forms to NTFS but not Vice Versa.
Be advised that NT in it’s
pre-Service Pack(SP) 4 version can not access NTFS 5, so in ordedr to be able
to reach NTFS partitions on Win2K from NT you should install SP 4 before
installing Win2K. Naming Convention for Servers (and Workstations) When you
name your server you should stick to simplicity or actually documentation.
You can’t know the eventual role of your server at the time of
installation,(the role can change with time) so naming the server by it’s
current role can miss you point. If you keep good(current) documentation of
your network you can always know that when you refer to a server named KITO you
are talking about a server that hosts you Web Site in Peru.
|
|
| |
Protocols
Protocols are the
languages computers use when they talk to each other over the network, there
always must be that is common for communication to take place. The best thing
is to keep the number of protocols on your network to minimal, Win2K installs
TCP/IP by default although it supports other protocols too.
The
question of which protocol to use depends on your needs-(Netware servers that
use IPX/SPX, the need for connection to the Internet ect.)
Server
Role
Unlike NT 4.0 you do not have to decide on the servers role
during installation, you only have to decided whether the computer will join a
domain(a computer account is needed) or a workgroup.
Later you can
decided if you want the Server to become a Domain Controller(DC). Servers can
have additional networking services be added to them, be sure to check each
service and it’s necessity.
|
|
| |
Licensing
Microsoft has two licensing systems:
1.Per Seat-Meaning that
each computer that accesses any server must have a Client Access License(CAL).
If you have more then one server this should be used.
2.Per Servers-you
buy licenses for the concurrent number of connections per server meaning that
if you buy 25 licenses per server only 25 machines can concurrently connect to
the server, the 26th computer will be denied access. |
|
| |
Clean
install/Upgrade
A clean installation will always help you start
clean without old unresolved problems and huge registries although upgrades
will keep your user accounts. When deciding on this subject you should consult
the size of your partitions(will it be enough for Win2K) ect. You can upgrade
any Win 9.x and Windows NT Workstation 4.0 to Windows 2000 Professional and any
Windows NT server to Windows 2000 Server family.
Installation
Phase 1-Preinstallation
Before you can install the system(on a computer with no OS) you have to
be able to connect to the source files, there are a few ways you can do this:
1.Bootable CD-ROM-Just insert the CD-ROM in the drive.
2.Network
connection-Connect to share on the network created earlier with a copy of the
\I386 directory from the CD-ROM.
3.Create Boot Disks-you can create Boot
Disk by using the batch file located in the bootdisk directory on the
CD-ROM(this will create four 1.44 disks that will enable you to boot and start
the installation.
To start running Setup when an operating system is
installed you have to choices:
1. WINNT-Starting setup from MS-Dos,Windows
3.1, Windows 3.11
2. WINNT32-Starting setup Windows 9.X,Windows NT. |
|
| |
Clean Install from Within an OS
1.If you
run the setup program from an upgradeable OS then you will be given the choice
of upgrading or running a clean installation.
2.License
Agreement-Accept/Decline.
3.Insert the Product Key
4.Special Options
Screen:
- Language Options-You can choose a primary language and
secondary character sets to be installed.
- Advanced Options-Locations of source files,directory in
which to be installed,copy all source files to the hard drive,the ability to
choose the partition in which Win2K will be installed.
- Accessibility Options- allow you to use the narator and
magnifier during installation.
5.If you are using FAT you are asked if you want to
upgrade to NTFS.
6.At this stage the system restarts:
- A directory called $win_nt$.~bt has been created and all
boot critical(CD drivers,NIC drivers are copied into it).
- A file called winnt.sif is also created, this file
contains the information provided in the first step. Win2K boot files are
copied into the boot sector.
- The boot.ini file is changed/created to default to the
$win_nt$.~bt\bootsect.dat after 5 seconds-this allowes the setup to
continue.
6.The text based setup begins:You can press F^ to
provide a proprietary Mass Storage Device Driver.
7.If you chose to choose
the partition you will be allowed to choose the partition-you can erase, create
and format partitions with different(FAT/NTFS) file systems. After you choose
your disks are vrified.
8.The Setup program copies files necessary for the
installation.
9.The system restarts into the Graphical Mode.
10. A
Welcome Screen appears and goes to the PnP detection phase.
11. At this
stage the regional settings screen appears and allows you to set your
Locale(this controls how numbers,dates ect will look) and the Keyboard
Layout(which languages will you be able to use).
12. Name and organization.
13. Licensing Mode screen.
14. Enter the computer name(as it will
appear on the network) and password for the Administrator account.
15.
Windows 2000 Components-you can add optional components and network services
including Accessories.
16. Date and Time settings-you should have the
correct time zone set up one each server,the system will look for the correct
time on the root server.
17. Set up networking options(Typical or Custom).
18. Choose whether you want to joind a Workgroup or Domain(in which case
you need a computer account).
19. At this stage the installation process
takes control and copies all necessary files and makes last changes to the
boot.ini file.
Clean install on a new computer(from CD-ROM)
1.When starting setup from a bootable CD-ROM you receive the
Welcome screen that greets you and allows you to either install a new copy of
Win2K, repair an oledr installation or Quit.
2.If this is a clean
installation(un-partitioned hard drive) you are aske to confirm the situation.
3.You are presented with the End User License.
4.The integrated
partiotion tool appears and allows you to partition your new hard drive.
5.After formatting your hard drive the installation program checks your
hard drive and starts copying the files necessary for the setup to the hard
drive.
6.The computer restarts and switches into the graphical mode(same as
above).
|
|
| |
Unattended Installation Until now we spoke about
“attended” installation-an installation that someone has to sit by
and answer every question that the system asks. There are a few ways that an
installation can be configured and customized, the first is by adding command
line switches to the setup commands(WINNT/WINNT32).
|
|
| |
WINNT WINNT32 /s:[sourcepath] The
path to Win2k source files.Can include a UNC path. /s:[sourcepath] The path to
Win2k source files. /t:[temppath] The path that temporary files will be placed
on. /tempdrive:[Drive Letter] The drive to use for temporary files
/u:[answerfile] Name of the answer file. /unattend[id]:[answer file] UDF ID and
answer file /udf:id[,udb file] The ID number and the UDF file. /udf:id[,udb
file] The ID number and the UDF file. /r:[folder] Create a folder during
installation and leaves it on the system. /copydir:[folder] Copies a
folder(inside the Win2K directory) during installation and leaves it on the
system. /rx:[folder] A path to a folder that will be installed and removed.
/copysource:[foldername] Copies a folder and removes it after install.
/e:[command] Runs a command after the GUI phase of the setup is finished.
/cmd:[command-line] Runs a command after the GUI phase of the setup is
finished. /a Specifies that the Accessibility options should be turned on when
setup completes. /unattend Will upgrade an old OS without any user intervention
/debug[level]:[filename] The level of debugging and the
filename.(%windir%\winnt32.log)-Levels are 0(severe
errors),1(errors),2(warnings),3(information),4(detailed info for debugging).
/syspart:[drive_letter] Copies setup startup files to a hard drive and allows
it to be started on a different computer. Must be use in conjuction with
/tempdrive,both should point to the same partition on the secondary hard drive.
/checkupgradeonly Will create a detailed report on compatibility issues for the
installation /cmdcons Installs the Recover Console. /m /makelocalsource This
will copy the installation directory to the hard drive of the machine being
installed. /noreboot Instructs setup not to restart. |
|
| |
WINNT |
WINNT32 |
| /s:[sourcepath] |
The path to Win2k source
files.Can include a UNC path. |
/s:[sourcepath] |
The path to Win2k source files. |
/t:[temppath] |
The path that temporary files will be placed on. |
/tempdrive:[Drive Letter] |
The drive to use for temporary
files |
| /u:[answerfile] |
Name of the answer file.< |
/unattend[id]:[answer file] |
UDF ID and answer file |
| /udf:id[,udb file] |
The ID number and the UDF
file. |
/udf:id[,udb file] |
The ID number and the UDF
file. |
| /r:[folder] |
Create a folder during
installation and leaves it on the system. |
/copydir:[folder] |
Copies a folder(inside the
Win2K directory) during installation and leaves it on the system. |
| /rx:[folder] |
A path to a folder that will
be installed and removed. |
/copysource:[foldername] |
Copies a folder and removes it
after install. |
| /e:[command] |
Runs a command after the GUI
phase of the setup is finished. |
/cmd:[command-line] |
Runs a command after the GUI
phase of the setup is finished. |
| /a |
Specifies that the
Accessibility options should be turned on when setup completes. |
|
:p> |
| :p> |
:p> |
/unattend |
Will upgrade an old OS without
any user intervention |
| |
|
/debug[level]:[filename] |
The level of debugging and the
filename.(%windir%\winnt32.log)-Levels are 0(severe
errors),1(errors),2(warnings),3(information),4(detailed info for debugging). |
| |
|
/syspart:[drive_letter] |
Copies setup startup files to
a hard drive and allows it to be started on a different computer. Must be use
in conjuction with /tempdrive,both should point to the same partition on the
secondary hard drive. |
| :p> |
:p> |
/checkupgradeonly |
Will create a detailed report
on compatibility issues for the installation |
| |
|
/cmdcons |
Installs the Recover Console. |
| |
|
/m |
|
| |
|
/makelocalsource |
This will copy the
installation directory to the hard drive of the machine being installed. |
| |
|
/noreboot |
Instructs setup not to
restart. |
Ok,ok so you added a few commnd line switches-you
didn’t actually make the whole process unattended you just customized it.
The way to make the whole process automated(unattended) is by using an answer
file. An answer file is a text file that includes all of your answers to the
setup process, by providing these answers you need no interaction during the
installation. The answer file has the structure of an INI file:[HEADERS],
ITEMS=VALUES. Building such a file manually can be a very complicated task, a
tool is provided to help us overcome this problem that is calle Setup Manager
Wizard. This tool can be found in the cabinet file under
\support\tools\deploy.cab after extracting the files you can run the Wizard.
After the ‘Welcome Screen’ you get three choices:
Create a new
answer file-asks you the questions that you are asked during the different
phases of setup. Create an answer file based on your computer-provides the
answers needed to duplicate the computer you are seated at. Modify an existing
file. At the next stage you are asked which product will use this answer file:
After choosing the product you want to provide for an answer
file you have to choose the platform you want to install-Server/Professional:
At
this stage you are asked about the interaction level provided to the
user:
Provide defaults-Provide the answers and asks the user to
acknowledge or change them. Fully automated-The users has no interaction,all
answers are provided by you. Hide pages-The user can interact only where you
have not provided an answer. Read only-The choices will be shown to the user
but he can not change them. GUI attended-Only the text based protion of the
installation process will be automated
After completing this part the
wizard starts asking you questions relevant to the installation process,I
brought a few questions that are notable:
You can enter different computer
names or provide a file with computer names(one per line).
Provide the
local administrator password and instruct the system to log on as the
administrator as many times as you configure,the password is provided as clear
text so be carefull. The Setup Manager Wizard will also help you creat a
distribution folder if one is needed. A distribuion folder is a single source
that contains all the files that you need in order to install a system.
You
can specify the location of the files and the name of the share.
You can specify
additional mass storage devices(F6) that are not included with the distribution
files of Win2k.
Additional Hardware Abstraction Layers can be added to the
distribution folders for specific platforms. Additional steps allow you to run
specific commands before you log on and add OEM branding(Logo,Backgorund)
bitmaps that are also copied to the distribution folder.
Now comes
the intersting part-additional files and folders that can be added to the
distribution folder:
System Drive-The installation location for Win2K-folders and
files copied here will stay here after the install.The folders under the System
Drive are:
Windows Folder- system32 Plug and Play Drivers-This is the
folder that intersts us the most, if we have drivers for some hardware not
included in the Win2K distribution media we can use this folder to include it
int and Win2K will find them.
Other drives- copies files included to
specified drives on the target and leaves them there.
Temporary Files- Will
remove the files after the installation process.
At this stage
the wizard is ready to place your answer file at the location you will
specify,be warned that placing the answer file as recommended in the
distribution folder without changing its name from [unattend.txt] may cause
it(in some versions) to be overwritten by the sample file on the
CD.
After this stage you are asked whether you want to copy the
files from the CD and you are finished. Now lets look at the damage: Under the
folder you specified two or three additional files that are of interest are
created: Unattend.txt-the answer file. Unattend.bat-The file that will help you
launch the process,if you have more then one computer name you should add the
computer name by the end. Unattend.udf-only created if you specify more then
one computer name.
A high degree of costumization So you installed
Win2K in an unattended fashion yet something is still missing-the
applications…If you are using applications that can be installed by
scripts you are on your way but if your applications just don’t like
scripts what can you do?? The trick is done by an old application called
SYSDIFF this apllication allows you to install different application in a snap.
First of all you have to set up a baseline system(all other will be
just like it),then you shoul take a snapshot of it: Sysdiff /snap snapfile At
this stage install your apllication/s and using the snapshot you created
earlier calculate the difference(what changed on your baseline
system-files,registry entrie ect.): Sysdiff /diff snapshot differencefile At
this stage you have a difference file that includes everything that changed
that you can apply to any new system you want to be affected-the only drawback
is that the new systems confiuration must be the same as the
baselines(including drive letters): Sysdiff /apply differencefile The big
question that comes in mind is where do I gt sysdiff from?? Well you can get it
at oem.microsoft.com not on the Win2K CD.
Remote Installation
Services
Still not satisfied with your abilities to install Win2K?
You want to simply spill images on computers and get them up and running-get
GHOST!! Now seriously Win2K Provides us with a service called Remote
Installation Services(RIS)-this services allows us(among other things) to
create images and spill them onto computers. RIS has three levels of
functionality:
Simple I386-based installation-shares the directory but
allows you to boot the workstation with a special boot disk. Scripted I386
installation-same as above but in an unattended fashion. Complete system
image-spills an image onto a computer that is booted with th special RIS
bootdisk.
An interesting service is also installed on the computer that
has RIS services installed, the service is called Single Instance Store(SIS).
This service looks for duplicate files per drive and erases all but one-in all
the other instances it leaves a directory entry pointing to the intact one.
Sounds nice but not everyting is well in Narnia,here are some limitations of
this service:
Delivers only Win2K PRO. Images. Uses only 25 NIC
drivers(only PCI) no laptops may be used Images only drive C.
Can store
image files only on non-boot/system NTFS partitions/volumes
Prequisites
Before you can use Ris you must have a Win2K based domain-meaning a
Win2K domain controler(thus Active Directory) and if you have Active Directory
installed you have to have a DNS server. One more thing you need to have is an
authorized DHCP,why? The program installed on the floppy gets an IP address for
the computer you are booting from the DHCP server then it locates an Active
Directory domain controller and it asks it where can it find a RIS server.
Authoerizing RIS??
Installing RIS
From the Add/Remove
Programs applet(Control Panel) go to Windows components and mark it. After it
adds the compnent to the system you have to set it up by running the setup
program called:risetup(surprise…).
On the welcome screen you can see the
prequisites and you should click on next.
Specify the drive you want to store
images on,it has to be NTFS and not a the system or boot drive.
Choose whether you want to answer
to client requests.
Enter the path of your Win2K PRO. CD.
|
|
| |
Each image will receive a different folder so you
have to choose a name for each folder.
Enter a description clients will receive for
this specific image. At this satge you are given a last chance to check the
confguration and after you acknowledge it the process starts:
After it
finishes the whole process you can configure the service by going to the
computer proprieties(on which the service is installed) and turning it
on.(dsa.msc) Client Side After al the fuss how will the clients look like? If
you have a Preboot eXEcution enabled computer it will automatically be able to
reach the RIS server if not you can use the boot disks. You can create boot
disks with a small application located at \remoteinstall\admin\i386-an
application called RBFG.EXE
This application is quite straightforward the
only drawback is that you can use only the adpaters it supports(25 in
number):
And you might have guessed that you can not update this list
although giving it a manual try could be interesting(it only creates one file
called RISDISK)…how charming.
When you insert the disk you will
see the computer acquire an IP address and connect to a TFTP on the RIS server
tht downloads some kind of client software that displays the file located at
\remoteinstall\oschhooser\english called welcome.osc-this file looks like a
HTML wannabe that can be manipulated. When you press enter you are prompted for
a username, password and domain after that the computer starts installing the
OS and you are home free. The default setup will be:
One large
partition formatted NTFS and join the RIS servers domain. This sounds nice if
oyu are after a vanilla installation of Windows 2000 Professional but Ghost
makes this look like a bad joke…a feature that makes RIS look more then a
bad joke is one that allows it to capture images of customized Win2K PROs and
turn them into images stored on the RIS server(now that sounds better
doesn’t it).
RIS shares the REMOTEINSTALL folder as REMINST under
it you have a folder called ADMIN which houses an application called
RIPREP.EXE.This application takes a snapshot of your Windows 2000 PRO. Erases
any traces of uniqueness(SID) and transfers the image to the RIS server. This
process is called the creation of a RIPRep format image. Be advised though that
the “prototype” computer will overgo a minimal setup process after
the reboot since it has been stripped for its identity. Preventing evrybody
from installing everything You might want to have different groups to see
different images and not all images when they conncet ot a ris server,th trick
to do it is deny read premission(NTFS) from the sif files(HUH?!?!).
It
seems that for every image created the RIS service creates a .sif(answer file
for the RIS image) file under
\remoteinstall\setup\english\images\i386\templates By denying read permission
the image won’t show up to a specific user/group. System Preparation Tool
Ok,ok, I get the picture you’re a die-hard Ghost user and you are not even
going to try RIS…well Microsoft thought of you too and they came up with a
tool called the System Preparation Tool(Sysprep). Sysprep prepares your system
to be duplicated. When we say prepare we actually mean strip of the SID and any
other identifying information. After you stripped up all the info you can make
an image with a third-party tool(Ghost) and you can distribute this image.
Prequisites
1. The HAL and the mass storage devices must be the
same. The computer to be duplicated cn not be a member of a domain. How it
works Inside this cabinet file on the Win2K CD \Support\Tools\deploy.cab you
can find two files you need:
Sysprep.exe
-quiet-doesn’t
display any confirmation message.
-nosidgen- doesn’t generate a new
SID
-reboot- reboots the computer immidieatly after it finishes
-pnp-
reruns the PnP detection after setup
|
|
| |
Setupcl.exe
After you set up a
system exactly as you want to duplicate it you copy these files onto a
directory called Sysprep on the SystemDrive. You run Sysprep.exe the computer
turns off and now you can copy the image using the third party tool. Still
using the third party tool you can apply the image and then restart the
computer, at this stage you reach a minimal setup that asks you for
identification information and regenarates a new SID for the
computer(Setupcl.exe). After it finishes it erases the sysprep folder.
Sysprep.inf
If you want to automate the mini-setup
portion you can provide a file called sysprep.inf as an answer file to the
mini-setup. |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
By Erik
RozmanMCT, MCSE, MCSA, MCP+I, CCNA, CNA
©2001-2002 MCSE Magazine - All Rights Reserved Terms of Use |
|
|
 Special Promotions |
AVG Internet Security |
|
|
|
Save postage and get Key online
Weekend offer!
only 75 €
|
AVG Anti-Virus |
|
|
|
Save postage and get Key online
Weekend offer!
only 32 €
|
Get complete protection from the most dangerous threats on the internet - worms, viruses, trojans, spyware, and adware.
incl.
Anti-Spyware
"1 computer 1 year"
Get it for 32€ incl. VAT!
Save up to 15€!
PROMOTION
|
Consulting Articles 
