Re: Migrate from SBS2003 to Win Server 2003

Charlie, Thanks for the info. I have looked at Swing Migration and
everything says it is a migration to SBS2003. This is primarily why I have
not looked to this route.

Am I wrong in what I am reading? I will contact them as well.

"Charlie Russel - MVP" wrote:

I would recommend a swing migration - www.sbsmigration.com.

As for joining the new server to the existing domain? Certainly. Use the Add
Server wizard in SBS to join it, and then use DCPromo to make it a DC.

Migrating all your information? Without losing anything? Swing migration.


--
Charlie.
http://msmvps.com/xperts64


Mitch Super wrote:
Thank you for the info. but the existing hardware we are running on is
old and needs replacing. We have purchased new server hardware, Windows
Server 2003 and exchange. I am looking to find a way to migrate all
account information and exchange to the WinSer2003 without loosing all of
the information. Then when done keep the domain name so we do not need
to touch all PC's again.

So, my question is, is there a way to have the new server as part of the
existing SBS domain then when we are completed, Promote the role of the DC
and decommision the old server?

Your immediate response is greatly appreciated.

"Charlie Russel - MVP" wrote:

You can use the Transition Pack to remove the SBS restrictions from your
existing server, and upgrade your existing CALs to standalone CALs.

If you have no desire to keep with the existing hardware at all, you can
use Swing Migration to migrate to new hardware with the same domain name
and server name. But if you'd still need to either Transition Pack your
existing server to recover the CALs and licenses, and make them able to
split to multiple machines, or start over and buy new.

You say you're outgrowing - if you could give us a few more details, we
could better help you.


--
Charlie.
http://msmvps.com/xperts64


Mitch Super wrote:
We have outgrown our SBS and the hardware it run on abd plan to install
new servers with AD. We are trying not to have to change the domain
name so users do not need to be reconfigured. How do I install the new
WinSer2003 and keep the original domain if SBS does not support the
configuration?

Thank you in advance for your assistance.



.

Relevant Pages

  • Re: Moving SBS 2003 to new hardware
    ... You're not actually going to run SBS on the TempDC, just use it to hold the AD temporarily. ... be needing 3 hardware platforms to perform for a swing migration. ... The old server and the new hardware. ...
    (microsoft.public.windows.server.sbs)
  • Re: Nt4 to do win2ksbs to win2003 sbs migration input needed
    ... You will have the same domain, same server name, same IP, same Exchange ... server and client side rules are retained. ... Swing Migration with as little as 3-4 hours downtime, ... If a problem occurs in one of those upgrades, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 R2 to SBS 2003 - to swing or not to swing....
    ... It's also important to understand how Swing Migration ... A Swing Migration for SBS 2008 is based upon the simple concept: ... new server and put the original server back online again. ... The TempDC construction is not complicated, ...
    (microsoft.public.windows.server.sbs)
  • Re: Moving SBS 2003 to new hardware
    ... be needing 3 hardware platforms to perform for a swing migration. ... The old server and the new hardware. ... We have a SBS 2003 server running with premium edition. ...
    (microsoft.public.windows.server.sbs)
  • Re: New TS on an SBS2003 network, general questions
    ... In *general* 9 concurrent users will not require much power, considering that a "typical" server today has at a minimum 4GB RAM, multi-core CPU, and 10K or 15K hard drives with hardware RAID. ... As for software you need a Server 2003 license, Windows CALs, and TS CALs for each user or device. ... Also you need proper licenses for the software that the users will be running, for example, if they will use any of the MS Office applications then you will need an Office license for each physical device. ...
    (microsoft.public.windows.terminal_services)
Loading