Repair install server 2003 r2

If you are prompted to start your computer from the CD, do so. Do not select the Recovery Console option. Press F8 to accept the licensing agreement. Setup searches for previous installations of Windows. If Setup does not find a previous installation of Windows Server , you might have a hardware failure.

Use the up and down arrows to select an installation. To repair the selected installation, press R. To continue without repairing, press ESC. Do I need to use that for the restore disk? Any idea where I can get one if so? From this KB using this string of commands I was able to get it to boot:.

To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Popular Topics in Windows Server.

Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Ghost Chili. Jay This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Refer to this link and very long thread of what can happen. Jay wrote: da Beast wrote: wow - totally missed the DC in the title Br d This person is a verified professional.

Thai Pepper. Was this a SBS server or a regular server? It MUST be newer than 90 days,preferably even 30days tombstone for DC backups If it was the only DC on the network as I assume it was: Install server Configure disks to same size or bigger and server name same as backup Run NTbackup when logged in as administrator Restore the systemstate with the following settings: Leave existing files Restore security settings Restore junction points, but not the folders and file data they reference Preserve existing volume mount points When restoring replicated data sets, mark the restored data as the primary data for all replicas.

You will want to make sure the paths to the Windows directory and the paths to the AD database are the same. Also, setup any other disks you may need to restore files to. For example, if the failed machine had a D: drive with files you want to restore, make sure that is created as well.

With Windows Ntbackup, the disks don't have to be exactly the same size, but they do have to be big enough to hold everything you want to restore obviously. Install any service packs that were on the failed machine. You want to restore your backup to an identical version and build number. I don't believe you have to do any other updates such as hotfixes as these will be part of the restored system state. Also, this is very overlooked, but don't forget Internet Explorer.

You will want to make sure this is the same version that was on the failed machine before you do your restore. IE is an intricate part of the OS for better or worse. In my testing, my failed machine had IE8 installed. The Windows Server R2 x64 installation disc will not recognize your LSI perc raid card without installing third party drivers. Luckily I figured out how to get windows setup to recognize your raid drive…. This was great. I just about had a nightmare, but stumbled on this before it got out of control..

Seriously man.. Total life saver. Wonderful write up, got me through doing a repair, but my RAID 10 still would not boot after the repair finished. Sad fact is our backup is online and it will take 3 days to download the current backup, thankfully it is current. Any other advice for me? Strange thing is that LSI Logic website states that there is native support in win2k8-r2 for perc 5i adapter.

If there is not a VD or the VD is failed then windows will not see the space. Copying windows installation files to disk takes 1 second, so something is wrong there. Hope we find out today! Even though I have completed the initization. Any ideas? Optional like me, have your disc media fail and ruin your otherwise perfectly working installation.