Re: Migrating to SBS 2003

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

Your plan is workable. The advantages of Swing are that if you keep the same
Server name and Domain name on the new server you can simply plug in your
Workstations when you are done. In any case if this is your first install I
recommend you spend a lot of time on preplanning and Install at least twice
(3 is best) to get the server like you want before putting into production.
Be sure and get SBS SP1 CDs if the version you have is not already
Slipstreamed.

--
Frank McCallister SBS MVP
COMPUMAC
<surpressed@xxxxxxxxx> wrote in message
news:1125398304.135870.277750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I'm planning on doing my first SBS deployment next week for the company
> where Im working at and thought that I would throw my migration plan up
> onto the Forum to get some feedback or suggestions. Appreciate any
> input or help.
>
> We currently have 10-20 users and a lot of mailgroups on 1 Windows
> Server 2000 (DC) deployed with Exchange 2000 on it. Next to e-mail the
> server is being used for backup runs and file/printer sharing. We have
> purchased a new server as well as SBS 2003 Premium Edition, and have to
> migrate all data to the new server.
>
> We think the migration could be as follows:
>
> 1) Install SBS 2003 on the new server.
> 2) Export the Exchange 2000 data from the old server onto an additional
> external disk using the ExMerge extraction tool.
> 3) Create the users and groups manualy on the new domain
> 4)Manually import the PST files into Exchange 2003 on the new SBS
> Server
>
> My thought process is that as we are only dealing with 8 users (and
> their data) that manually doing the export and import for Exchange data
> as well as setting up a new AD, will not be too cumbersome, time
> consuming or risky.
>
> I am a bit familiar with "swing" migrations, but am thinking that due
> to the number of users and data we're talking about that the risk is
> minimal in doing it the way Ive mentioned above.
>
> Im interested in hearing any feedback or advice on things to keep in
> mind if we do go ahead and do it the export/import way. I'm also
> open to hearing any comments as to why we should not do it that way,
> and which way would be recommended (and why)?
>
> Appreciate your feedback.
>


.

Relevant Pages

  • Re: Server Migration SBS 2000 to New Server Box
    ... It's not my goal to talk you or anyone else into purchasing a Swing It!! ... Kit, not at all, not if it doesn't make sense to both of us. ... I also owe a lot of favors to a bunch of SBS ... You will run in to SFN breaks on the new server as soon as you do the ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: From NT4 to SBS 2003 - 6 users
    ... Server media to use. ... Not specifically in just the SBS ... I think that Swing Migration makes far more sense than any other ... You could decide that an upgrade of a domain would be ...
    (microsoft.public.windows.server.sbs)
  • Re: SP1 finished successfully... or did it?
    ... Regarding the SP updates to an SBS 2003 Server: ... - If you have SP1 slipstreamed media, ... does without a Swing involved. ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2K Server to Win SBS 2003 migration
    ... Thanks for your confirmation about a the Swing Migration. ... Actually this copy of SBS 2003 is the R2 ... to simply x-fer all the AD data from the Win2K server to the SBS 2003 box, ... manage the AD for the business, and the Win2K server will have the DC ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs migration gurus
    ... know any other IT PROs who know SBS here. ... I could really only take the current production server offline late ... You mentioned that 80%+ of the swing ... migration involves installing SBS fresh on the new server? ...
    (microsoft.public.windows.server.sbs)