Installing Windows Server

Installing Windows 2003 Server

MIS 431 –Rev. Spring 2008

MIS 431 Installing Windows 2003 Server 2

Installation is Easy!

Do your advance preparations HCL: what hardware components? Which file system Installed NIC Network protocols to install Name of server Active directory design

Setup is a step-by-step Wizard


Server Hardware Components – check HCL! CPU type & # Type of bus (PCI,ISA) Hard disk and adapter

type (manufacturer and model)

Hard disk capacity CD-ROM drive and

adapter type BIOS boot drive order

(CD, C, A)

Mouse/pointing device

Monitor and video card

Keyboard type Floppy drive type Tape drive and

adapter NIC (mfgr, model,

specs)


Decisions before Starting

Get current drivers before or have another PC that you can use to download drivers

How to partition the hard drive Which file system (FAT, NTFS) Server name and administrator password Which protocols to install Which licensing method (per server, seat) If the server is a DC, what is domain name


Decisions .. Partitioning

Decisions Use existing partition? Delete existing partition and create new? Create new partition if non exists?

Size of the partition (MS recommends min 2 GB for partition for system files)

Dual boot machine? Can boot FAT partition with Windows client OS Rest of machine is NTFS with Windows 2003


Disk Partitioning

Can use DOS FDISK program to partition the FAT area, DOS FORMAT program to format the FAT

Windows 2003 boot loader menu is specified in boot.ini file

[boot loader] … from my home server which uses SCSI timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft

Windows 2003 Server" /fastdetect


Windows NTFS File System

NTFS is superior! Best security and performance Encryption and file compression (not

available in FAT) Can use FAT now and convert

partition to NTFS later If FAT and <= 2 GB, WS03 uses FAT16

If FAT and > 2 GB, WS03 uses FAT32


Decisions – server name

Seen in Network Neighborhood (Win 9x) or My Network Places (later versions)

Use short name - easy to type and remember

Make sure name is not already used by another network computer

Name mnemonically, not numerically


Decisions – Administrator PW

Do Not Forget This Password – ever!!! User name is Administrator and has

access to all of the server’s resources Password tips for this sensitive PW

Up to 14 characters, 10 or more is good Make it difficult to guess!


Decisions - Protocols

TCP/IP is best – preferred protocol NetBEUI is OK for small networks

without routers May need NWlink if logging in to a

Novell NetWare server; will also need Client Service for NetWare


Decisions - Licensing

Per server means total # of clients that can be logged on at one time; preferred

Per seat means buying a license for each client computer; may be good if you have one user logging in to multiple servers


Decisions – Network Server Type

Standalone server – for very small peer to peer networks or when you are bringing a WS03 server into an NT 4.0 network in which it will not act as a DC

Server based network – DC or member server that joins an existing domain Member server belongs to a domain but has not

copy of the active directory and does not replicate nor authenticate logons.


Installation Options

Types of installation CD-ROM only Floppy disk and CD-ROM (when you cannot boot

from the CD-ROM) Network install Install from an existing operating system Unattended installation (via script)

In each case, run winnt.exe (in DOS) or winnt32.exe (in 32-bit Windows 9x environment) to begin the installation


Winnt command switches

/? List all switches /e:command executes a command after the Windows

portion of Setup /i:initialization filename specifies a custom initialization

file where install files are found /sdrive:\folder used for path for the installation files other

than the current file /u:scriptfile used in unattended install to specify the

name of the script (answer) file and should be used with /s command

More .. http://207.46.196.114/windowsserver/en/library/166ff001-a0a6-4ab3-8303-6c4c9596a80b1033.mspx?mfr=true


Winnt32 command switches

/? Gives all switches /checkupgradeonly creates a report that

tells if PC is compatible with WS03 /s:drive:folder uses a path for installation

files different than the current path /unattend [seconds]:script file used in an

unattended installation to specify name of file containing script for setup

More …


CD-ROM Installation

Easiest and best if your computer boots from a CD-ROM

Set BIOS to boot from CD-ROM 1st Insert CD-ROM, restart It will automatically boot from CD and

run Winnt


Floppy Disk & CD-ROM

Use this if cannot boot from CD-ROM Set BIOS to boot from floppy 1st Insert floppy #1, restart computer It will ask you to insert other three disks,

then the CD-ROM Hint: can make floppy set by running

d:\bootdisk\makeboot.exe or d:\bootdisk\makebt32.exe


Network Installation

Can install WS03 from a network share on another computer Good if you have a diskless computer or one

without a working CD-ROM drive Also useful if you have a large network and plan

to implement many WS03 servers Requires you to have a working computer

that connects to network Share the server’s drive, open from new server,

run Winnt.exe or Winnt32.exe


Install from Existing Op System

Requires DOS, Windows 3-1, Windows 9x, or Windows Server already on the server

Use this method to have a dual boot machine or if you want to upgrade to Windows 2003 Server

1st dialog will ask if you want to upgrade to Windows 2003 or do a clean install Clean is much better unless you have a reason

for doing the upgrade


Unattended Installation

Usually performed as a network install Uses a script file that contains all the

answers to the questions the setup wizard asks

winnt32 /s:\\misnt\i386 /unattend:unattend.txt Uses a share called i386 on MISNT and the

answers in a script file called unattend.txt


Unattended Install, contd.

Can create a uniqueness database file (UDF) with unique answers for each server (they cannot have same name or IP address, etc)


Stepping Through Installation

Part 1 – assumes CD-ROM install1. Setup inspects the hardware and asks you to setup

Windows 2003, repair an existing WS03 installation, and to quit Setup

2. Presents licensing agreement – press F83. Scans hard drive for previous installations of

Windows 2003; it offers to repair if it finds.4. Setup determines current partitions. Can install on

existing, delete, or make new partition.5. Choose file system – FAT or NTFS6. Copies lots of files, then reboots into WS03 (remove

CD)


Setup, contd.

Part 21. Gathers information about the computer’s HW

2. Change regional settings

3. Enter your name and organization

4. Enter product key

5. Choose licensing mode and # CALs

6. Enter computer name and admin PW

7. Select components to install

8. If modem installed, provide dialing information

9. Verify time and date accuracy


Setup, contd.

Part 2, contd.10. Configures network settings – either typical

or custom where you enter static IP information

11. Specify workgroup name if not joining an existing domain

12. Installs the components you requested13. Remove WS03 CD, restart, and go to work!


Testing New Server

Logon with Ctrl+Alt+Del Use Administrator username and PW


Creating ERD

Create one every time you install software, make a server configuration change, install a new adapter, add a NIC, or upgrade the operating system

Can start the Backup Wizard and click the Emergency Repair Disk button


Troubleshooting Installation

Ensure processor and HW is on HCL Test all HW before installing Windows 2003 Run manufacturer’s diagnostics before

installing Windows 2003 See troubleshooting tips …

http://207.46.196.114/windowsserver/en/library/0d516be6-a9be-4c1a-930d-c95c8297841b1033.mspx?mfr=true


Installing Service Packs

Back up server and make ERD Download service pack to a folder on

the server www.microsoft.com/windows

Close all active windows Run the service pack file and follow

directions


Uninstalling Windows 2000

Nah…. But it would be a good idea to prepare

a disk image of the boot drive Norton or Symantec Ghost Can be quickly restored if drive is

replaced Then can be more deliberate at restoring

data backups

Installing Windows Server

Documents

Transcript of Installing Windows Server