Re: SBS2003 New Hardware Migration

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hate to break this to you...but this no different than other migrations
unless there is something you haven't shared yet

You have 3 options

1. Create a New, Start from Scratch installation of SBS on the new Hardware
(Remember if the original box had the software "pre-installed" from the
factory, you can't install it on the new hardware. Create User Accounts,
Create Computer Accounts, move data, move mail. disjoin workstations from
old domain and rejoin to new domain

2. Perform a Swing Migration (preferred approach by most) found at
sbsmigration.com. You get great support on this one. Same Caveat about
OEM/Preinstalled software...can't be moved to new hardware.

3. Introduce the new Server as a DC using the SBS media (again, same caveat
about OEM). This will bring user accounts over. You can move user data,
etc Then seize the FSMO roles Clean up Active Directory to remove old SBS
from it. Complete SBS install. This is essentially the same as #2
without the documentation, support and tools.

To move mail you can use Exmerge utility which you can download from MS
site.



--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Tim Mulholland" <NoSpam.tim.SpamNo@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:ub8wGqtpHHA.3512@xxxxxxxxxxxxxxxxxxxxxxx
I've seen similar questions asked below but I feel my scenario is slightly
different from what was asked previously, enough so that it might garner
different responses.

I'm doing some work for a non-profit organization that has a SBS2003
installation on a server where they are having some hardware failures.
They have purchased new hardware to replace it and now I am tasked with
figuring out the easiest way to migrate.

They have already spent pretty much their entire IT budget this year, so I
need the cheapest route here. I don't mind time-consuming at all, but I'd
prefer "straightforward" to "roundabout."

I can get access to all of the files on the server and I might be able to
run the server for a little while (to do exports and things of that
nature) but i wouldn't count on it for any long-running tasks.

What is my best route here?

I was thinking of just doing a clean install (there are some software
problems on the old server anyway).

I know how to move the user's data over.
I know how to move SQL Server data over.
I DON'T know how to move user account/computer information over.
I DON'T know how to move exchange mailboxes over.

Can someone point me to some whitepapers or something on those specific
points (the DON'Ts)?

Are there any other serious gotcha's here?

It's a very small organization so doing some of these steps manually
wouldn't be the problem that it would be for a larger organization. But
I'd prefer to read about it some before i dove in!

Thanks in advance!





.

Relevant Pages

  • Re: Converting a Small business server
    ... If the old server software is of the type "OEM" you cannot move it to new hardware except under the special circumstance that the mobo has died and cannot be replaced. ... With just a few desktops, say 10 or less, a new install is less painful than a migration, even with preserving the profiles and exporting and importing the mail, particularly with failing hardware on the old SBS. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: VM Ware for Recovery or Migration
    ... etc) or if I can PING a server? ... and install an O/S onto a VM. ... your server, as with everything, so you've got to look at hardware. ... converter on my SBS, ran it so that it copied the machine (live mind ...
    (microsoft.public.windows.server.sbs)
  • Re: Saving and transferring AD information
    ... consultant not know about Small Business Server? ... If the server hardware is really old (say, ... I would not suggest that you install a second Domain Controller into the ... When I click on the "Install Windows Server 2003, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Help! Im new and have many questions!
    ... My next server will be real server hardware for SBS 2008. ... driver, which is all of them, will not install. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migration from Windows Server 2000
    ... the potential losses in support and just plain 'stuffin ... to near 'as-is' condition and now having a copy in virtual hardware. ... finding 'OHHH, and now _this_ is referring to the old server, how do we fix ... The SBS2k3 install can be stopped after just the OS stage and enter ...
    (microsoft.public.windows.server.sbs)