Re: Migrate from regular 2003 R2 Domain to SBS?

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

backups. Plus file copies. I shoved over the exchange mdb files.

And I never keep data on my system drive. Run with 3 drives normally on a server

System
Programs
Data

makes it easy. Complete rebuild never touches anything but the system partition

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:u1q34$guHHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
Good point.

How is your data all preserved on the temp DC? Your DOMAIN (SIDs, etc) would be, but not all your data.

The only way I woul go onto the same hardware is if I had new drives.

Gregg Hill

"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0829E20A-8F5F-417E-9DA8-E8616E8DCA8B@xxxxxxxxxxxxxxxx
When was the last time I trusted an inplace MS upgrade? Hmmm. I think DOS 5 to DOS 6. Certainly I would never suggest it here. The big problem with an IPU is that if it fails, you're basically screwed. Hope you did a good backup before you started. Whereas with a swing, even onto the same hardware, you can continue to move forward. If the fresh install on the original hardware fails, you simply restart it. Your data is all preserved on the TempDC.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:%23BlSpUduHHA.2360@xxxxxxxxxxxxxxxxxxxxxxx
He later posted that he wants to do it on the same hardware. I thought that there was a direct upgrade from Windows Server 2003 with Exchange 2003 to SBS 2003. If not, then swing back to the same hardware is definitely better.

If he wanted to do it on different hardware, would the http://support.microsoft.com/kb/884453/en-us method be easier, as all he would do is implement the SBS and move mailboxes? Or perhaps I am too unfamiliar with Exchange to know any better!

Gregg Hill


"nordberg" <nordberg_73@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:00822f02$0$27311$c3e8da3@xxxxxxxxxxxxxxxxxxxx

"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:ux0z6QUuHHA.536@xxxxxxxxxxxxxxxxxxxxxxx
You already have a server 2003 domain. No swing needed.

http://support.microsoft.com/kb/884453/en-us

Gregg Hill

But doing it this way would be a lot more longwinded because of Exchange etc. Swing is the ideal way in my experience.







.

Relevant Pages

  • Re: Server/Drive Speed
    ... GB is a little light, especially if they are hosting their own Exchange ... IDE can be a problem if one of the drives is put on the same ... A new server sounds like the best approach if you have to reinstall (so you ... hardware asnd migrate the data and profiles. ...
    (microsoft.public.windows.server.sbs)
  • Moving Exchange 2k to new Exchange 2k server
    ... I have an Exchange 2k server. ... Two hard drives (one for OS ... I want to upgrade my hardware ... Also, in looking at the way this server was setup, I ...
    (microsoft.public.exchange.admin)
  • Re: Moving Exchange 2k to new Exchange 2k server
    ... How to Move Exchange 2000 to New Hardware and Keep the Same Server ... Two hard drives (one for OS ...
    (microsoft.public.exchange.admin)
  • Re: Moving my server to new hardware.
    ... We are talking hardware RAID? ... several restarts for all hardware changes to be recognised. ... You can compare the HALs ... If RAID1 I would disconnect 1 of the pair of drives and simply try to ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 DRP - Server needs boot disk....
    ... might just take the simpler approach and built the other server. ... before moving/migrating mailboxes over? ... the new server installed you can simply copy the exchange databases, ... replace the drives. ...
    (microsoft.public.exchange.setup)