2020. 2. 14. 05:13ㆍ카테고리 없음
Hello Terran0925, the repair option to boot to the cd is no longer an option due to the changes in setup for Windows Server 2008. Since it uses a image based deployment option, the file by file copy method is no longer available. You can boot to the Windows Server 2008 and choose the repair in the lower left hand corner of the screen.
This should open a CMD prompt. From here you can run sfc and use the offline options, /OFFBOOTDIR For offline repair specify the location of the offline boot directory /OFFWINDIR For offline repair specify the location of the offline windows directory This repairs the boot files, allowing you to boot back into the OS, if you are still having issues you could try doing an upgrade with the media then. Thanks, Darrell GorterMSFT This posting is provided 'AS IS' with no warranties, and confers no rights. Hello Terran0925, the repair option to boot to the cd is no longer an option due to the changes in setup for Windows Server 2008.
Since it uses a image based deployment option, the file by file copy method is no longer available. You can boot to the Windows Server 2008 and choose the repair in the lower left hand corner of the screen.
This should open a CMD prompt. From here you can run sfc and use the offline options, /OFFBOOTDIR For offline repair specify the location of the offline boot directory /OFFWINDIR For offline repair specify the location of the offline windows directory This repairs the boot files, allowing you to boot back into the OS, if you are still having issues you could try doing an upgrade with the media then.
Thanks, Darrell GorterMSFT This posting is provided 'AS IS' with no warranties, and confers no rights. It certainly does not - that is merely the startup repair function similar to the fixboot, fixmbr commands of old (though a little extended to be fair) No point in looking - there is NO ability to repair Server 2008 or higher OSes any more. A massive setback for network administrators. As bad as the fact that you can no longer slipstream hotfixes into Outlook etc., but instead you put them in an 'updates' folder that installs Office SP0 and then installs SP1 or 2 on top.
Bizarre, your Office install now takes twice as long. Some day Microsoft will need to think of the guys on sites who actually have to care for/install their products. This coming from a Microsoft fan-boy, btw. (you'll know that I'm a fan-boy as I haven't mentioned the train-wreck that was DPM 2007 (for anyone using it, jump to DPM 2010 RC quick)). Boot from OS install disk Select next after making sure the language options are correct.
Select Repair option Select CMD CD into recovery Type Dir Run the StartRep.exe command in the list. That should do a basic repair to the OS. The instructions above also saved me.Thanks a lot Chaoticflyer. I'm getting some funky problems relating to SCCM2007 (specifically, the Management Point role) not seeing/communicating with WebDAV even though I have confirmed that WebDAV is configured correctrly for SCCM.
I am not saying that this is definitely a problem on the OS level, but the thought is beginning to cross my mind. Would this approach possibly work for me as well? How would it affect any roles/applications that are already set up on the server (like IIS, SQL server, DHCP, AD, WDS, whatever)? Would you need to run the repair on a 'vanilla' install so as to not foul up roles or back-end apps that are already on the server? -Brian McKnight. I have a server set up with Raid 5. Unfortunately I was not involved in the configuration.
It seems that I have 2 Raid 5 with virtual disks. Out of my 6 HDs two are failing (0 and 4) and I ma trying to repair the systam now.
How To Install Windows 95 Using Bootable Cd
Following the recommendation to run startrep.exe (ran it threee times already) always gives me the following diagnosis: Root cause found: A hard disk could not be found. If a hard disk is installed, it is not responding. Is that the ultimate 'Gone' for my system or are there other options to recover? Hello there, forgive me for jumping in but I am having a very related issue, my Server 2008 R1 32bit installation is hanging on crcdisk.sys.
I am trying to recover via the installation repair options. However, my hard disks, and thus my OS is not being detected. The hardware itself checks out fine and BIOS loads with no issues.
This is an inherited machine so i am unsure of where to look when I click the 'load drivers' option to detect the drives. Is there any way to solve this short of re-installation?