Sounds like a pretty straight forward process. Question for you, how much of the process could be skipped, or avoided, in the case of a requirement to rebuild the original SBS server. I reckon you could take this process and apply it to a swing server scenario, where you would migrate settings to the new ( temp ) server, them rebuild the original server and migrate back, performing a cleanup along the way. Is there an MS document for best practice around disaster recovery in 2003, or something that might provide a shortcut to the above method?

thanks

i have seen many documents outlining swing migrations etc. but now i am faced with a new challenge. i need to migrate a client from sbs 2003 premium to a new domain with exchange server 2007, ultimately decomissioning the sbs server and reinstalling with isa server std 2006. any ideas on how to achieve this as one cannot use exmerge to import into exchange 2007? msexchange has an article on making the new exch 2007 svr a dc in sbs domain, transferring fsmo roles to new dc, moving mailboxes and then transferring roles back to sbs, so that exch 2007 can co exist in a sbs domain.

i need to migrate away from sbs to a new dc running E2K7

thanks

Yusuf

Could you tell me if your start  the  process used in the White Papers , is it possible to reverse the

dcpromo of the destination server back to the source ?

and also do I have this right- you need to change the name of the new(destination )computer ie

old sbs 2003 =A.mydomain.local

new sbs 2003= B.mydomain.local

they cannot both be the same surely ...

how much downtime is  excpected for users , will they continue to be authenticated by the destination

server once the destination server is joined to the domain.????

thanks

David

thanks for your reply - my mistake - what I meant was : will clients continue to authenticate to server A

when server B has  been joined to the domain- obviously they will auth.to server B when after the DNS

server address is set to point to the destination server(step 2)However , according to the white paper,

shared folders do not get copied across until step 4 - so there will be a time when users will not be

able to access shares on source server(server A) as you pointed out.

would I not be better off to back up the shared  data to external harddrive late in evening and then copy it

to server B after making dns change so they can access it from server B next day ??

thanks again

If I wanted to have the migration done by a professional what category should I be looking for? Microsoft Certified professional? MCSE? Please advise

I'm attempting to follow the MS technet guide but wondered if someone could clear up a few things for me?

In the guide it mentions installing SBS 2003 on the destination server and once it boots in to windows click cancel on the continue sbs setup box.

At this point its just a standard server with no exchange or sharepoint etc.

I then did the following:-

Configure static ip

Install Server 2003 service pack 1 (WindowsServer2003-KB889101-SP1-x86-ENU.exe)

Install XP SP2 for client deployment (pre-req for SBS SP1)

Install SBS 2003 SP1 (wouldn't install)

Install Server 2003 SP2 (didn't attempt to as SBS SP1 wasn't installed)

Turn off firewall (not present anyway)

Join domain

Tried to install SBS 2003 SP1 again but I get an error "This computer is configured as a domain member server"

Has anyone come across this before? I'm wondering if maybe I stopped the continuation of SBS setup too early?

Many thanks

Jon