Re: Complicated SBS Upgrade Issue

All versions of SBS have supported additional DC's 'out of the box', no reg
hack or special AD modification is required.

Don't beat yourself up over it though, it is one of the most misunderstood
areas of SBS. SBS (2000/2003) must hold all FSMO roles but additional DC's
are allowed.

What's the motivation for Exchange 2003? Even if using one of your existing
servers as base OS you are looking at significant cost to move to Exchange
2003 Standard (non-SBS). If you moved to SBS2003 you would get Exchange 2003
Standard version at a significantly lower cost. Moving to the non-SBS
version requires the Exchange Server license and CALs for all users, your
existing SBS CALs do not cover an additional Exchange.

Note that if you moved to SBS2003 R2 and _also_ still required an additional
Exchange server the 'expanded CAL rights' introduced in R2 would cover
access to the additional Exchange box.

If you keep your existing SBS2000 the AD can be at a maximum functional
level of 'Windows 2000 Native'. Exchange 2003 works fine in an AD at this
functional level (it is the normal functional level for SBS 2003).


"JamesH" <JamesH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:136B2563-B4D0-4C70-A1B9-EC08ACF84AF6@xxxxxxxxxxxxxxxx
We currently have a SBS 2000 installation, (1) Windows 2000, (2) Windows
2003
Std servers. The SBS 2000 and Windows 2000 servers are both DC's, which
I'm
not sure how this happened, because from all documentation it can't. The
previous admin stated he worked with MS Support and was able to modify the
registry or AD or whatever to allow this second DC.

The question is we are upgrading to Exchange 2003 on a Windows Std 2003
box
and am wondering if I install Exchange on the 2003 box as a member server
how
the forstprep and domainprep for Exchange will affect our current
structure?
Especially with the two DC's one being SBS.

The second issue I'm concerned with is the AD upgrade from 2000 to 2003.
Should I upgrade the AD and promote a 2003 box to DC before or after the
Exchange installation?

Thirdly, I don't have a test environment to perform any such upgrades on.
Should this be a major concern? If so what is the best way to create one?

Please advise, any help would be greatly appreciated.



.

Relevant Pages

  • Re: Transition Pack versions and availablilty
    ... It requires that you upgrade to SP2 for Exchange and SP2 for Sharepoint, both of which you should have already done. ... The good news is that once you're done, your existing SBS wizards, including RWW, will still work. ... Getting back to the original question; any experiences applying the transition pack, ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange upgrade
    ... Once the upgrade was completed I installed all of the SBS ... >> is to setup a secondary server, install Exchange server on it, move all ...
    (microsoft.public.windows.server.sbs)
  • RE: Single Server Upgrade Exchange Question
    ... Before perform upgrade process, it is greatly recommended you take a full ... Use the Exchange Migration Wizard to Migrate Mailboxes ... the Exchange 2000 server will be automatically ... it is not recommend that users access the SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: Why not POP
    ... Also handy to use if you are using an ISP that is not fond of servers being ... More people are going to SBS as a server for their ... I'm not sure I agree with him that Exchange ... >> Are there any major reason why I should not you the POP connector on ...
    (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)
Loading