As of today, my company has one server running W2K SBS.

We have bought a new server and are now going to upgrade to W2K3
Server.

I was wondering if anybody has suggestion to do the following:

* We want the new server to be the domain controller, with W2K3
Enterprise edition running on it.

* We want to install W2K3 Standard Server on the old server, and
install Exchange 2003 Enterprise Edition on this one as well. This
server becomes a member of the new domain server which will be running
on the new server.

How would you guys out there approach this scenario?

Hope you can be a little detailed here, so I don't get anything wrong.

Thanks in advance!!

Re: Upgrade from one W2K SBS to one W2K3 Enterprise Server and one W2K3 Standard Server by Jeff

Jeff
Fri Aug 13 08:42:16 CDT 2004

It sounds like you are trying to exit the SBS product, so the first thing
you would want to look at is the Transition Pack for the
licensing/migration/upgrade options:

http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/generalfaq.mspx

What you do from there becomes whatever you want. It's not an SBS issue
anymore. You would follow the documentation for the products you are
shifting to. Among the options would be to use ADMT, or to do an Exchange
Swing migration.

You don't explain why you are doing this rather than an upgrade to SBS 2003,
but I'll assume you have a reason to want to pay more for basically the same
products. :)


"Tom Hagen" <nikko@netcom.no> wrote in message
news:uVxjoBQgEHA.3964@TK2MSFTNGP12.phx.gbl...
> As of today, my company has one server running W2K SBS.
>
> We have bought a new server and are now going to upgrade to W2K3
> Server.
>
> I was wondering if anybody has suggestion to do the following:
>
> * We want the new server to be the domain controller, with W2K3
> Enterprise edition running on it.
>
> * We want to install W2K3 Standard Server on the old server, and
> install Exchange 2003 Enterprise Edition on this one as well. This
> server becomes a member of the new domain server which will be running
> on the new server.
>
> How would you guys out there approach this scenario?
>
> Hope you can be a little detailed here, so I don't get anything wrong.
>
> Thanks in advance!!
>
>



Re: Upgrade from one W2K SBS to one W2K3 Enterprise Server and one W2K3 Standard Server by Tom

Tom
Mon Aug 16 04:30:28 CDT 2004

Thanks for replying.

One of the main reasons we are leaving SBS is that we have reached the limit
of allowed users on SBS...


"Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
news:%23iy0InTgEHA.3944@tk2msftngp13.phx.gbl...
> It sounds like you are trying to exit the SBS product, so the first thing
> you would want to look at is the Transition Pack for the
> licensing/migration/upgrade options:
>
> http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/generalfaq.mspx
>
> What you do from there becomes whatever you want. It's not an SBS issue
> anymore. You would follow the documentation for the products you are
> shifting to. Among the options would be to use ADMT, or to do an Exchange
> Swing migration.
>
> You don't explain why you are doing this rather than an upgrade to SBS
> 2003,
> but I'll assume you have a reason to want to pay more for basically the
> same
> products. :)
>
>
> "Tom Hagen" <nikko@netcom.no> wrote in message
> news:uVxjoBQgEHA.3964@TK2MSFTNGP12.phx.gbl...
>> As of today, my company has one server running W2K SBS.
>>
>> We have bought a new server and are now going to upgrade to W2K3
>> Server.
>>
>> I was wondering if anybody has suggestion to do the following:
>>
>> * We want the new server to be the domain controller, with W2K3
>> Enterprise edition running on it.
>>
>> * We want to install W2K3 Standard Server on the old server, and
>> install Exchange 2003 Enterprise Edition on this one as well. This
>> server becomes a member of the new domain server which will be running
>> on the new server.
>>
>> How would you guys out there approach this scenario?
>>
>> Hope you can be a little detailed here, so I don't get anything wrong.
>>
>> Thanks in advance!!
>>
>>
>
>



Re: Upgrade from one W2K SBS to one W2K3 Enterprise Server and one W2K3 Standard Server by Jeff

Jeff
Mon Aug 16 12:50:22 CDT 2004

That's a pretty good reason. I'm going to mention that you should know that
SBS 2003 raised the user limit to 75, and that can be Device CALs, User
CALs, or a combination. Therefore, someone with a desktop and a laptop needs
just 1 CAL. Three people using one computer uses just one CAL.


"Tom Hagen" <nikko@netcom.no> wrote in message
news:um4mmP3gEHA.536@TK2MSFTNGP11.phx.gbl...
> Thanks for replying.
>
> One of the main reasons we are leaving SBS is that we have reached the
limit
> of allowed users on SBS...
>
>
> "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
> news:%23iy0InTgEHA.3944@tk2msftngp13.phx.gbl...
> > It sounds like you are trying to exit the SBS product, so the first
thing
> > you would want to look at is the Transition Pack for the
> > licensing/migration/upgrade options:
> >
> >
http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/generalfaq.mspx
> >
> > What you do from there becomes whatever you want. It's not an SBS issue
> > anymore. You would follow the documentation for the products you are
> > shifting to. Among the options would be to use ADMT, or to do an
Exchange
> > Swing migration.
> >
> > You don't explain why you are doing this rather than an upgrade to SBS
> > 2003,
> > but I'll assume you have a reason to want to pay more for basically the
> > same
> > products. :)
> >
> >
> > "Tom Hagen" <nikko@netcom.no> wrote in message
> > news:uVxjoBQgEHA.3964@TK2MSFTNGP12.phx.gbl...
> >> As of today, my company has one server running W2K SBS.
> >>
> >> We have bought a new server and are now going to upgrade to W2K3
> >> Server.
> >>
> >> I was wondering if anybody has suggestion to do the following:
> >>
> >> * We want the new server to be the domain controller, with W2K3
> >> Enterprise edition running on it.
> >>
> >> * We want to install W2K3 Standard Server on the old server, and
> >> install Exchange 2003 Enterprise Edition on this one as well. This
> >> server becomes a member of the new domain server which will be running
> >> on the new server.
> >>
> >> How would you guys out there approach this scenario?
> >>
> >> Hope you can be a little detailed here, so I don't get anything wrong.
> >>
> >> Thanks in advance!!
> >>
> >>
> >
> >
>
>