SBS 2003 Migration to SBS 2003 (new hardware)

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

Hello,

This is a follow up to my post linked here:
http://groups.google.ca/group/microsoft.public.windows.server.migration/browse_thread/thread/9a239801e2bdaa72#ca8235d6e844d28b

Firstly, I'd like to thank Neo and Meinolf for their prompt responses.
I was directed and asked to post my inquiry here.

I'm trying to migrate one SBS 2003 server to new hardware. I was
hoping to keep the machine & local domain name the same but i guess
this just isn't possible w/o "Swing Migration" and at the moment I
cannot spend more $$ for a solution.

Are there any draw backs to migrating to a different local domain
name?
I want this to be as painless as possible for the end users. The end
user work is mission critcal and waiting time during work hours
because they can't connect to exchange for their e-mails or are unable
to read their old ones (from before the migration) is just
unacceptable.

So i guess my questions are as follows:
1. Any drawbacks to migrating from DN old.local to new.local
2. Exchange database is still migrateable?
3. Does ADMT take care of GPO's and any security settings? Or do i
have to re-create them?
4. What about client side applications that rely on data from mapped
network drives? (if i remap the new network drives with same drive
letter as their old counter parts this shouldnt be a problem..
correct?)


Any help is appreciated :)

Thank you
.

Relevant Pages

  • RE: SBS 2003 Migration to SBS 2003 (new hardware)
    ... this just isn't possible w/o "Swing Migration" and at the moment I ... user work is mission critcal and waiting time during work hours ... Exchange database is still migrateable? ... (if i remap the new network drives with same drive ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Migration to SBS 2003 (new hardware)
    ... You have to recreate all your shares on the new server and using a USB drive or something to move data to the new drive ... The company will have lots more down time and pain if you use this method than spending the 200.00 for the Swing Migration kit. ... (if i remap the new network drives with same drive ...
    (microsoft.public.windows.server.sbs)
  • mapping network drive fails between NT and 2003 server
    ... I am halfway through an NT to 2003 migration and I ... PDC to WS2K3 as recommended, ... They fail authentication and It ... By mapping network drives I mean typing: ...
    (microsoft.public.windows.server.migration)