Re: Upgrading SBS 2000 to Enterprise versions

Tech-Archive recommends: Speed Up your PC by fixing your registry

Think you are spending more money than necessary

You can introduce your Win2k3 enterprise server directly in to the SBS 2000 domain
run ForestPrep and Domainprep from the Win2k3 software on the SBS server then add your enterprise server.
Then proceed as you suggested.

you may also want to check out sbsmigration.com for thoughts.

We are always curious as to why people are leaving SBS if you don't mindsharing

--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
"James" <potnoodle23@xxxxxxxxxxxxxxxxxx> wrote in message news:eaqbgk$6fm$1$830fa7a5@xxxxxxxxxxxxxxxxxxx
Can anyone offer some help with this one?

I have an SBS 2000 domain, and need to upgrade to Enterprise versions of
Windows Server and Exchange on new hardware, one machine for Server one for
Exchange.

My plan so far is:-

1. Upgrade SBS2000 to SBS 2003.
2. Use a transition pack to obtain seperate server CALS and remove
restrictions of SBS.
3. Install a new Windows 2003 Enterprise Server into the domain on new
hardware, and install Exchange 2003 Enterprise Server on this box, adding it
as an
additional Exchange Server in the existing Exchange organization.
4. Move users mailboxes from the original Exchange Server to the Exchange
Enterprise Server, then remove the first Exchange server from the
organization as per
KB822931.
5. Install a second Windows 2003 Enterprise Server into the domain on new
hardware, promote to be an additional domain controller, transfer all FSMO
roles to
this new machine, and remove the original server from the domain.

If anyone can offer me a better plan or any advice on licensing, that would
help, my usual contacts in the channel are being useless with licensing
information at the moment.

I am guessing I need one Windows CAL for each user, and one Exchange CAL for
each user (there will be over 100 to begin with, growing to 400 in next 2
months). Have I missed anything?

Cheers,

James

Relevant Pages

  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email for second domain
    ... The Microsoft Exchange MTA Stacks service is normally disabled on Exchange 2003 Servers on SBS 2003. ... You can safely ignore the MTA warning messages on the SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Configuring exchange 2003 in SBS
    ... As I know, this is not related to per user mailbox, it refer to the mailbox ... store on the whole Exchange server. ... This newsgroup only focuses on SBS technical issues. ... What minimum requirement if I want this server for a fileserver? ...
    (microsoft.public.windows.server.sbs)