Guy Recommends
A solution to monitor, manage and archive thousands of
events that are generated by devices across the entire network.
Download FREE
trial
Introduction to the System State in Windows 2003 Server
In disaster recovery, planning, prevention and preparation are your watchwords. Which ever
backup software you use for Windows Server 2003, take a minute to tick the System State
box. This page also features ASR and creating a bootable system disk.
Alternatively, if your server will not boot refer to the
Boot Problems page.
Windows Server 2003 System State
Here is a list of all the components contained in the Windows 2003 System State.
- Boot files (Boot.ini, NDTLDR, NTDetect.com)
- Registry - Including COM settings
- SYSVOL - Group Policy and Logon Scripts
- Active Directory NTDS.DIT (Domain Controllers)
- Certificate Store (If the service is installed)
The System State has a specialist job namely, to restore the
operating configuration files. Before you install a new application, driver or hotfix,
think, 'what will be my fall back position
if the server crashes?'. Microsoft's best practice would say: create a System State
backup for the Windows 2003 operating system, then you can rollback if there is a problem. Murphy's 9th law states, once you
take these protective measures the application, driver or hotfix never gives any
problem. However, the one time you forget to backup the system state, 'Murphy's 1st law' says, disaster will strike your unprotected server.
 Network security is complex. As an MCT trainer, I can thoroughly recommend
TrainSignal because they
provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text material. You can either take one module, for example
Network Security or go for
a combination of modules.
See more about Network Security training here
Another alternative for a sickly machine is to repair
a dodgy driver by rolling back to, 'one that I saved earlier'. If you
suspect that your latest driver is faulty, then navigate to the Device Manager and check for a red X next to the device. To attempt a cure, select Properties, Driver (Tab), Roll Back.
Note: Driver Roll Back is a different option from Restore Point. Moreover, unlike XP, there is no Restore Point option
in Windows Server 2003.
ASR (Automated System Recovery) is Windows Server 2003's replacement for NT4.0's RDISK. I have to say that I have never had any success with
ASR. The idea is worthy, all the registry configuration
settings can be saved and later restored. The fatal flaw is that the ASR
disk has to be updated manually every time you make a change, and for ordinary
mortals that just does not happen. If there is one thing worse than not
having an ASR it is having an out-of-date disk which corrupts the system.
If you wish to create an ASR disk then Click Start, Programs,
Accessories, System Tools, then click Backup. Amateurs believe that the ASR is
bootable - wrong. However, you CAN create a bootable System Disk as
explained in the next section.
The floppy disk that I have in mind here has many names, system disk, boot
disk, startup disk. What ever the name the purpose of this simple floppy
is
to boot a broken machine. This 'get out of jail disk will help when you boot a machine and see a message saying:
'Cannot find NTOSKERNL.EXE.' The error sounds vicious even terminal but there is a simple solution - a system disk.
If you are Mr Organized then you will have your system floppy disk at the ready. However if you need to create a disk then take a blank floppy to another Windows Server. Remember to start by
formatting the floppy within Windows 2003, next, copy NTLDR, NTDETECT.COM
and Boot.ini to the floppy. The secret of getting this floppy to boot the server is understanding Boot.ini. Sample Boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect
In most instances changing the partition number will cure the problem. Partition(1) corresponding to the C:\ drive and Partition(2) to the D:\ Thus, you can make an educated guess as to
which number to try on your server.
If you have time you could add other lines to each with a different partition
number. With a little care and trouble, you could make a boot.ini with a
dozen lines that would start Windows 2003 on a large variety of disks and
partition numbers.
If you have mirrored RAID disks then edit the boot.ini to reflect the pair of disks (same partition number):
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Server 2003 (D0)" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Server 2003 (D1)" /fastdetect
| 
