Re: MotherBoard Change
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Tue, 30 Oct 2007 12:40:09 +1100
no sweat.
One other thing (I forgot to mention). You might think about copying any
drivers for the new mobo and any extras onto the HDD before shutting down
the old, means they are available on HDD should they be necessary/desirable
and depending on what is needed you may not have access to CD during
hardware detection. If the system gets as far as hardware detection it is
already accessing the HDD. I throw drivers into x:\drivers\intelchip and
x:\drivers\network and x:\drivers\etc... on just about every system I touch.
Yes, it's worth a shot. YMMV. But should it work, and IME it has a more than
decent chance, you end up with a fully functional move doing little else
than choosing 'search for drivers' or 'load this driver'.
"Daniel Jewel" <cyberdudeiq@xxxxxxxxxxxx> wrote in message
news:%23srg5%23oGIHA.4296@xxxxxxxxxxxxxxxxxxxxxxx
UAU SuperGumby !!!
I'm absolutely thankful for such a valuable info...many thanks for even
taking the time to answer so detailed...
You are truly one who deserves KUDOS for this newsgroup !!!!!!!!!
Man, many thanks,
Dan
P.S. will give it a shot this coming weekend...
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> escreveu na mensagem
news:eYnrVNnGIHA.3548@xxxxxxxxxxxxxxxxxxxxxxx
There is a good chance it will work, and enough chance that it won't to
mention the possibility too.
What I would do:
Shut down.
Swap motherboards.
Power up with only one of your software mirrors connected.
DO NOT start the system normally, start only into Directory Services
Restore Mode. This will allow the system, should it successfully boot
(which is likely but not guaranteed), to get into Windows without loading
AD.
If she boots she'll start detecting hardware changes. Allow the changes
to be detected and load drivers, then restart, _again into DSRM only_.
Let the system sit there for a bit (10 min), sometimes the changes to
hardware seem to take a long time to be detected. Quite often it will
take several (3 or more) restarts before all changed hardware is
detected, this is due to certain devices not being detected until their
underlying component support has been detected and loaded. When you get a
clean restart with no further detection let her sit there for a bit
longer to be sure, then restart again, into DSRM, we're not finished here
yet.
Your networks will be trashed.
from a command window run:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
(do not run them directly from the run line, the 2nd needs to run in the
same instance of the cmd processor as the 1st)
and in the resulting devmgmt console 'View, Show Hidden Devices'. Remove
any hardware which is greyed out but BE CAREFUL about 'devices' in the
'Non Plug and Play Drivers' section, it's worth looking at your existing
setup beforehand, you'll note that some of these appear grey on a normal
system. You'll also probably have some greys under 'Sound, Video and Game
controllers', who cares? it's a server.
Get rid of the 'ghosts', and restart again, into DSRM. Time to actually
configure the NICs. However, first let the system sit there a bit, does
it detect further hardware changes? No? Go ahead, configure your NICs.
But, configure the 'internal' NIC to a different subnet than you want to
use.
Start normally.
Run the 'Change Server IP address' wiz from the SBS console to return the
'internal' NIC to your normal range.
Run the CEICW.
Feet up, cigar, smile.
Couple of preparation items.
You can save a bit of time by installing the 'LoopBack Adapter' in place
of your existing NICs. This simply makes the network changes more
predictable. The lovely M&M's have instructions on www.smallbizserver.net
but I'm not sure whether it's a 'public' or 'registered only' article.
It's worthwhile checking the 'native HAL' that would be installed on the
new motherboard during a standard install, compare it to your existing
HAL. Particularly if it is the same HAL your chances of success are
improved. If it is a different HAL you might want see if the 'Standard
HAL' can be forced and work on the new mobo (see MS about forcing HAL
during Windows install).
The other key factor is the HDD subsystem. Windows must be able to access
the drive to boot. If the RAID on the target is a plugin card and uses
the type of drive you currently run you can plug the card into your
existing system before starting the procedure, load drivers for it under
the existing system, maybe even connect one of your drives to it to make
sure the system boots OK with just this change.
The procedure for going from what was software RAID on the old system to
hardware RAID deserves as much space by itself, let's see if you get this
far. We want to be able to boot a working SBS.
If the system won't boot with the new mobo in place we can try a 'repair
installation' of Windows. This can break a few things on SBS but it can
be fixed.
If the 'repair' doesn't work. Shutdown. Put the original mobo back in and
attach only the drive which has been disconnected during the attempt.
Start, you should have your original system back. Shutdown, wipe the
drive that was used for the attempted move (to ensure we don't mix up
partitions), start up and re-establish your software RAID, time for plan
B.
Plan B may be to take an image of the existing system using a product
capable of 'hardware independent restore', say to USB, then imaging back
onto the new mobo. Before I'd spend the several hundred bucks this
requires I'd likely give the procedure above a go. Worst case is it
doesn't work. If you can get the system into Windows (DSRM) after the
mobo change just about anything gone wrong can be fixed.
Before starting HAVE A FULL, KNOWN GOOD, BACKUP.
HINT: A couple of the system imaging products will allow you to perform a
full system image in the trial version, they block restore though. That's
OK, should restore from image be necessary you buy the product.
"Daniel Jewel" <cyberdudeiq@xxxxxxxxxxxx> wrote in message
news:eCiJE0iGIHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
Larry,
this is a full blown version and the other points are : RAM amount, SATA
I only and so forth..
Dan
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
message news:OAAPWKhGIHA.3600@xxxxxxxxxxxxxxxxxxxxxxx
Hi Daniel:
Can you determine if you have OEM licensing? The legal requirements
for OEM are that you not change the MB. This would be a "new computer"
and the OEM license is for the original computer only.
It most certainly will call for a re registering/authorization of the
license. Will MS let it pass? Don't know, but it is not within the
"rules of engagement".
Otherwise, you have several ways to proceed, but I would prefer you to
install a stand alone RAID controller in your existing mobo if all you
want/need is hardware raid.
--
Larry
"Daniel Jewel" <cyberdudeiq@xxxxxxxxxxxx> wrote in message
news:eh28R9gGIHA.484@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
Please help me with the following:
this is SBS2003 R2 Premium with 2 NICs...
All I want is two things:
1-) change the motherboard and keep the rest as they are. Is it
doable? if yes, can you share some tips?
2-) right now I have software RAID1. If I'm able to change boards,
I'll have hardware RAID and will change to that. Is it possible?
thanks,
Dan
.
- References:
- MotherBoard Change
- From: Daniel Jewel
- Re: MotherBoard Change
- From: Larry Struckmeyer
- Re: MotherBoard Change
- From: Daniel Jewel
- Re: MotherBoard Change
- From: SuperGumby [SBS MVP]
- Re: MotherBoard Change
- From: Daniel Jewel
- MotherBoard Change
- Prev by Date: Re: Unix Identity Management on SBS 2003 R2
- Next by Date: Re: Can't get access to SBS03 after installed lastest patches.
- Previous by thread: Re: MotherBoard Change
- Next by thread: Forwarding e-mail to users home e-mail address
- Index(es):
Relevant Pages
|
