SBS 2008 server autoreboots after motherboard change
I had an epic failure in Windows SBS 2008 Server due to a battery leak inside my motherboard caused by a faulty Areca Raid. Since my MB was fried I had to put together a new moterboard, cpu and memory, obviously my Windows SBs 2008 gave me license troubles, and right now I can boot only on safe mode, when I try to boot normally after some time it begins to shutdown and restart alone.
Any ideas to help me troubleshoot and correct this? Thanks!
Any ideas to help me troubleshoot and correct this? Thanks!
Hi,
This can also be a faulthy driver issue. Check in safe mode if there are wrong drivers installed for the old mainboard and delete them, after rebooting Windows should install the correct drivers. (Start with display and chipset drivers)
This can also be a faulthy driver issue. Check in safe mode if there are wrong drivers installed for the old mainboard and delete them, after rebooting Windows should install the correct drivers. (Start with display and chipset drivers)
I don't expect points because diggisaur already mentioned, to add it it I was asked to troubleshoot a server that restarted like yours and found out later they old IT created a license issue somehow. In your case you should be able to contact MS and explain the problem they will grant you a new license or remedy it on their end.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
until now I tried to remove every phantom piece of equipment, and it is not an easy task! I tried to activate from safe mode but it does not finish!
I will keep trying, thanks!
I will keep trying, thanks!
Insert a Windows Server 2008 disk. Restart the computer and then load System Recovery Tools.
Click Command Prompt. At the command prompt, type Notepad %windir%\ntbtlog.txt. Notepad opens and displays the boot log.
The last lines tell you what stopped the server from booting. If it is drivers, locate and delete them and boot normal again.
Click Command Prompt. At the command prompt, type Notepad %windir%\ntbtlog.txt. Notepad opens and displays the boot log.
The last lines tell you what stopped the server from booting. If it is drivers, locate and delete them and boot normal again.
Should not do it from safe mode.
In safe mode most will be greyed out ... thats what safe mode is: Minimal drivers active.
Olaf
In safe mode most will be greyed out ... thats what safe mode is: Minimal drivers active.
Olaf
ASKER
This solution solved my problem and turned out to make my system a lot faster!
Otherwise you will need to call the Microsoft Activation team.