Replacing motherboard in domain controller

  • Thread starter Thread starter Michael A. Covington
  • Start date Start date
M

Michael A. Covington

My domain controller may be about to get a new motherboard (to fix a stupid
problem with the fan controller; the fan runs but the BIOS complains that
it's not there).

This would be a (supposedly) exact match, under warranty, not a new CPU.
The MAC address would change because the network interface is on the
motherboard.

Presumably, this would require a SYSPREP. Would that take care of it?
Because it's a domain controller, do I have to do more than that?

--

Michael A. Covington - Artificial Intelligence Ctr - University of Georgia

"In the core C# language it is simply not possible to have an uninitialized
variable, a 'dangling' pointer, or an expression that indexes an array
beyond its bounds. Whole categories of bugs that routinely plague C and C++
programs are thus eliminated." - A. Hejlsberg, The C# Programming Language
 
Not sure whether you'd need to do a sysprep, but some suggestions
regardless... Make sure you do a good full backup of everything, including
system state, first. Also, if you don't have another DC, I'd set up one,
even temporarily, and even on workstation hardware, and make sure it
replicates. I'm paranoid. ;-)
 
This would be a (supposedly) exact match, under warranty, not a new
me too, i was up until 4am recently rebuilding a failed dc. it went into
a continual loop of rebooting after a windows update and reboot. it
wouldnt even get to safe mode or accept last know good or anything.

good thing was it worked fine after an in place upgrade install of win2k
then a non authoritative restore of the system state backup from the
previous week, needed to do very little after that to keep it going the
extra 2 days before it was being replaced anyway ... grrrr !

i now always have available system state backups in a folder on the data
drive at least 1 or 2 per month in addition to the nightly tape backups
by BE9.
 
Back
Top