Install Windows 2003 On Raid Server Configurations

Have you ever seen this error message when trying to remote desktop into your Windows Server The terminal server has exceeded the maximum number of allowed. View and Download Lenovo ThinkServer TS200 hardware maintenance manual online. Hardware Maintenance Manual for TS200. ThinkServer TS200 Server pdf manual download. MegaRAID SAS 92714i Costeffective hardware RAID data protection and performance for smaller disk configurations. Human Skeleton 3D Model Maya. Install Windows 2003 On Raid Server Configurations' title='Install Windows 2003 On Raid Server Configurations' />FAQ Switching Storage Controllers wo Reinstalling Windows. Moving Windows to a Different Hard DiskRAID Controller Without Reinstalling. Overview. One of the trends in personal computing these days is the prevelance of more options for hard disks and RAID systems than have been available in the past. As a result, many people want to move towards one of these systems as an upgrade, but at the same time want to avoid the hassle of reinstalling Windows and all applications. This has been exceedingly difficult and in some cases even impossible do to. However, with this guide, youll be able to perform this task in most cases with most hardware configurations. What You Can and Cannot Do With This Guide. This guide is applicable to the person who has Windows currently starting up from one hard diskhard disk controller combination, and wants to start that same Windows installation up from a different hard diskhard disk controller on the same computer. For instance, you may want to upgrade from a single disk installation of Windows to a RAID installation, or from an IDE drive to a SCSI drive, or from an IDE drive to a native mode SATA drive. In general, this guide will work for any situation where the mass storage controller that has to be used for Windows startup is going to change. This guide is NOT for adding another drive or controller to an existing system when the Windows installation doesnt move from its existing controller. That is a much easier task and can be done with standard driver installation and the Disk Management utility in Windows. This guide is NOT for moving a Windows installation to completely different hardware like changing your motherboard. There are some procedures posted on the Internet for that already. The guide is NOT for moving a hard drive within a system where the disk controller that is being used either does not change or uses the same drivers as the old one, or where Windows already has built in drivers for the new controller like a standard IDE controller. Windows and Mass Storage Controllers. Windows treats all mass storage controllers the same way. Whether its a standard IDE controller, SATA controller, SCSI controller, or RAID controller, Windows has to have a driver for it in order to use it. Once Windows has a driver installed for the controller, Windows can start up from a hard drive attached to that controller as long as the machines BIOS can use the controller as the boot device. When installing Windows for the first time on a system, most of the time no concern need be given to the mass storage controller, because in the past, 9. IDE controller which Windows already has drivers for on its installation CD. Windows will detect the standard IDE controller and use its own drivers for it, thus enabling Windows to start up from the IDE controller. If Windows does not have a driver on its CD for your system, the Windows text mode setup program tells you that Windows cannot find a mass storage controller in your system, and prompts you to insert a manufacturer supplied driver disk. This is the method to install mass storage controller drivers for most SCSI, RAID, and now some SATA controllers. Windows reads the driver off the floppy disk, and uses that driver to start up after installation. If any situation arises where Windows does not have a driver installed for the mass storage controller youre starting up from, you will get a blue screen STOP error, usually with the error STOP 0x. B INACCESSIBLEBOOTDEVICE. If youve ever tried to copy a Windows installation from one controller to another with one of the partition copy tools and then tried to start it up, this is probably what you got. The key item in this procedure that makes it work is that the procedure loads drivers for a storage controller that Windows will start up on before moving Windows to that storage controller. Once Windows has seen the storage controller and has had drivers loaded for it, Windows can now use that storage controller as the startup controller. Requirements to Proceed. To proceed with this procedure, you will need the following The Windows installation that you want to move must be Windows 2. Pro, 2. 00. 0 Server, 2. Server, or XP. The old hard drive controller is currently installed in the system, drivers for it are installed in Windows, and the hard drive holding the current Windows installation is attached to that controller, and Windows currently starts up in this configuration. You will need some type of tool to copy a partition from one drive to another if you will be moving the Windows installation to a different hard drive as well as a different controller. The recommended tools are Norton Partition Magic, Norton Ghost, Acronis True Image, or Boot. It Next GenerationImage for DOS. There are a few other products out there as well. Be aware that Partition Magic will only run on Windows 2. Pro or Windows XP it does not support copying partitions containing a server operating system. For copying server partitions, I recommend Norton Ghost. You need the ability to have both the old disk controller and the new disk controller installed in the machine at the same time. If you cant do this for whatever reason, there is a work around that will be addressed later in the guide. If you will be copying the startup Windows partition to a different drive, the disk controllers involved in the copy operation must support Extended INT1. Age Of Empires 2 Gold Edition. Most SCSI and RAID controllers, and all modern IDESATA controllers support this. You need drivers for the new disk controller already downloaded and decompressed if required on your C drive. You need to prepare a DOS mode startup media for the partition copy program you will be using. For Partition Magic, you can boot the Partition Magic CD. For Norton Ghost, you need to create a Ghost boot floppy. For Acronis True Image, you can boot the Acronis True Image CD. For Boot. It Next GenerationImage for DOS, create a startup floppy. Disclaimers. This procedure carries some risk. It is not possible to forsee all possible hardware combinations, and there may be some that this procedure doesnt work on. There is a risk of losing your data, all the way from minor problems to loss of the entire hard drive. As with any procedure where data loss is a risk, having a current backup of your data is strongly advised. I cant be responsible for data loss, and I dont guarantee that this procedure will work in all situations, nor that it will work at all times. Procedure. This procedure assumes youre using a different hard disk as well as a different disk controller. If youre changing the disk controller only, skip steps 1. Backup all important data. Use a different hard drive other than the ones that will be used in this procedure, or backup to a network storage device or tape drive. Shut down the system power off. Install the new disk controller in the system, but do not connect any drives to it. Power on the system, go into the system BIOS. Make sure in the boot order, that your original disk controller and hard drive are still set to be the boot device. Save changes in the BIOS if necessary, and restart the system. Allow your existing installation of Windows to start up. Once Windows is started up and has reached the desktop, the Found New Hardware wizard should start, indicating that the system wants to install drivers for the new disk controller. Install the drivers according to the manufacturers directions. Make sure youre installing the correct driver.