I have a client who wants to update their wan office servers. One server has
sbs2k including exchange. Other server at remote location has windows server
2003 std installed. I would like to upgrade both servers to run windows
server 2003 std, but dont want to lose exchange settings on sbs2000. Is there
any way to upgrade sbs2000 and keep exchange, or do i need to buy exchange
server 2003, and migrate records. Also, the person who installed the network,
used wrong domain, would like to fix domain of the servers.

Anyone have any ideas how i can accomplish this besides formatting servers
and installing fresh copies of windows server 2003 on both machines.
Thanks

Re: migration from sbs2k to wserver2003 by Henry

Henry
Sat Oct 16 21:18:50 CDT 2004

Just a wild guess here, but I'd say the original IT configured the
system correctly and in the best interest of the client, with an SBS
local domain and a std server in the remote office.

Before you go changing it take some time to get to understand SBS.
You're questions here are a good start.

On your points.

If you replace the SBServer you will not only incur the cost of a
Windows Server, Exchange Server, Windows Server CALS, Exchange CALs, but
the costs of the Migration, and the loss of all the other features of
SBS. ( none of the SBS components, features ( shared Fax etc.. ) or
Servers ( Exchange SQL, ISA ) can be moved or transferred off the
SBServer. )

Doing the Migration -is- possible, but be aware of the costs involved
for your client.

As far as the Domain Name goes, it's pretty irrelevant as the Local
domain Name has nothing to do with the Public domain Name, and in fact
it's recommended that the local Domain be something like
<companyname>.local, SBS.local etc and -not- the public
<companyname>.com or .biz or whatever.

If the client does decide to wear the added cost and loss of
functionality/features in favour of your proposed "Upgrade" then as
you'll be setting up a new Domain, you can call it whatever you like,
transferring the mailboxes using exmerge.

The only reason I'd consider suggesting such an "Upgrade" to a client
would be if they were beyond the scope of managing Users and Devices
within the CAL limit, and then I'd be looking to using the Migration
Pack to unlock the existing Domain.

YMMV

--
Henry Craven {SBS-MVP}
Melbourne Australia

"ludwigvonb007" <ludwigvonb007@discussions.microsoft.com> wrote in
message news:1A6F86EE-3B7D-4643-AFBB-23D8250414AC@microsoft.com...
> I have a client who wants to update their wan office servers. One
server has
> sbs2k including exchange. Other server at remote location has windows
server
> 2003 std installed. I would like to upgrade both servers to run
windows
> server 2003 std, but dont want to lose exchange settings on sbs2000.
Is there
> any way to upgrade sbs2000 and keep exchange, or do i need to buy
exchange
> server 2003, and migrate records. Also, the person who installed the
network,
> used wrong domain, would like to fix domain of the servers.
>
> Anyone have any ideas how i can accomplish this besides formatting
servers
> and installing fresh copies of windows server 2003 on both machines.
> Thanks
>