And since SBS 2000 cals are no longer available, you'd have to get SBS 2003 cals but they don't come with a floppy any more so then you have to contact Microsoft Licensing.

 Tom regardless of the technical issues you face with this messy scenario
 understand that SBS 2000 did not come with 50 built in licenses only 5-do
 you have an additional 45 SBS 2000 CALs to install if the rest of it should
 work out?

 "Tom D." <TomD@discussions.microsoft.com> wrote in message
 news:48E8D3C1-7DE6-47BA-B254-8ACBDD532375@microsoft.com...
 > Thanks guys. I am not really going backwards, so to speak. I just want to
 > have the existing SBS 2000 member server promoted as the DC that holds all
 > of
 > the roles and the other existing 2003 DC as another DC (running in 2000
 > native mode)
 >
 > I think the root of the problem is that the 2000 SBS server needs to be a
 > DC
 > (as it was designed) and must house all the roles (licensing most
 > importantly) on it. Right now it is running as a member server and is
 > looking
 > to the other 2003 DC for the licensing service. It does not have the
 > default
 > configuration that it expects (I think 2000 SBS has 50 licenses by
 > default)
 >
 > If I promote the SBS member server to a DC, and transfer the all roles, it
 > will be looking to itself for the licensing service, the other 2003 DC
 > will
 > simply be another Domain Controller that is running in 2000 native mode.
 > (which is designed to replicate and work with other 2000 DCs).  The
 > existing
 > 2003 DC will transfer the Exchange 2000 schema changes to the promoted
 > 2000
 > SBS member server that were added during the initial installation Exchange
 > 2000, allowing me to restore the Exchange backup (see initial resolution
 > plan) after I promote it and (re) install SBS with the full suite and
 > tools.
 >
 > I assume the 50 licenses that come with 2000 SBS are not being recognized
 > because of the dumb way I tried to install it. Ala' Cart (As a member
 > server
 > with Exchange only and not running the entire SBS applications &
 > management
 > tools.)
 >
 > Bottom line I'm trying to confirm that 2000 SBS configured as the DC with
 > all the Roles can exist with an additional 2003 DC (running in 2000
 > native -
 > not 2003 native) and that having the License service role on the SBS
 > instead
 > of another DC will fix the Licensing problem.
 > --
 > Thanks for all your input!
 > I hope I am being clear with my description of the issue - I know its
 > lengthy.
 >
 > Cheers
 > Tom
 >
 > "Cris Hanna [SBS-MVP]" wrote:
 >
 >> I've never tried and to be honest, I wouldn't consider "going backward"
 >> like this for any of my clients
 >> I realize that you said the AD is showing Native 2000, and with the
 >> caveat that I've never tried this...and don't know anyone who has, it
 >> just strikes me that you can't go backward like that
 >> SBS 2000 is only in "extended support" mode by Microsoft...two more years
 >> and its at end of life.
 >> You'll only get the most critical security updates
 >>
 >> Not to mention you can't do the cool stuff with Exchange (direct push
 >> with Windows mobile devices, etc)
 >>
 >> --
 >> Cris Hanna [SBS - MVP]
 >> -----------------------------------------------------------
 >> MVPs Do Not Work for Microsoft
 >> Please do not contact me directly regarding issues
 >>   "Tom D." <TomD@discussions.microsoft.com> wrote in message
 >> news:A125AA16-623A-4A00-9C1F-58E10DB0E596@microsoft.com...
 >>   One more question...
 >>   Is there an issue to installing SBS 2000 into a existing AD domain
 >> opposed
 >>   to installing 2003 SBS into an existing AD domain?
 >>   --
 >>
 >>   Thanks
 >>   Tom
 >>
 >>   "Cris Hanna [SBS-MVP]" wrote:
 >>
 >>   > crap...I can't read either...lol
 >>   > makes even less sense to install SBS 2000
 >>   > All kind of headaches there
 >>   >
 >>   > --
 >>   > Cris Hanna [SBS - MVP]
 >>   > -----------------------------------------------------------
 >>   > MVPs Do Not Work for Microsoft
 >>   > Please do not contact me directly regarding issues
 >>   >   "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
 >> message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
 >>   >   I saw/see that Cris... just wanted him to get more feedback.  Not
 >> many come here any more.
 >>   >
 >>   >   Besides, you must mean an existing 2003 Domain... :-)
 >>   >
 >>   >   Tom, imho, you should back this out and start over with SBS 2003 as
 >> Cris suggests.
 >>   >
 >>   >   --
 >>   >   Larry
 >>   >
 >>   >     "Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net>
 >> wrote in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
 >>   >     Larry he's installing SBS 2000
 >>   >
 >>   >     Tom.   Why are you installing a version of SBS that is so old
 >> when you have an existing 2000 domain
 >>   >
 >>   >     At a minimum you should be installing SBS 2003.  there is a white
 >> paper on the SBS 2003 into an existing AD domain
 >>   >
 >>   >     --
 >>   >     Cris Hanna [SBS - MVP]
 >>   >     -----------------------------------------------------------
 >>   >     MVPs Do Not Work for Microsoft
 >>   >     Please do not contact me directly regarding issues
 >>   >       "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote
 >> in message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
 >>   >       Because more eyes are watching, you may get more response in
 >> the SBS 2003
 >>   >       Newsgroup.
 >>   >
 >>   >       SBS public Newsgroups:
 >>   >
 >>   >       SBS 4.x: microsoft.public.backoffice.smallbiz
 >>   >       SBS 2000: microsoft.public.backoffice.smallbiz2000
 >>   >       SBS 2003: microsoft.public.windows.server.sbs
 >>   >
 >>   >       if your current news server does not carry the mentioned groups
 >> you should
 >>   >       be able to connect directly to news.microsoft.com
 >>   >
 >>   >       --
 >>   >       Larry
 >>   >
 >>   >
 >>   >
 >>   >       "Tom D." <TomD@discussions.microsoft.com> wrote in message
 >>   >       news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
 >>   >       > Hello all
 >>   >       > Here is my scenario...I have installed SBS 2000 into an
 >> existing 2003 AD
 >>   >       > domain. The Active Directory is in 2000 native mode. I made
 >> the dumb
 >>   >       > mistake
 >>   >       > in assuming I could install the SBS as a member server and
 >> install
 >>   >       > Exchange
 >>   >       > from the installation binaries on Disk 3. (without the entire
 >> SBS package)
 >>   >       > All was fine until I got licensing errors as I connected more
 >> than 10
 >>   >       > people
 >>   >       > to their new mailboxes.
 >>   >       >
 >>   >       > Does anyone have an intimate knowledge of SBS's licensing
 >> architecture? I
 >>   >       > figured it would be OK because there is less than 25 users
 >> and I should
 >>   >       > have
 >>   >       > 50 and used the proper installation keys that came with the
 >> software. It
 >>   >       > smells like it's the fact that it (SBS) is not the DC and the
 >> other DC
 >>   >       > contains all of the roles (licensing in particular)
 >>   >       >
 >>   >       > My initial thoughts on fixing this issue -
 >>   >       > -Make a backup of the MS Exchange Information Store.
 >>   >       > -Promote the Win2k member server (SBS 2000) to a DC.
 >>   >       > -Transfer all Operations roles from the other 2003 DC (2000
 >> native mode)
 >>   >       > to
 >>   >       > the   SBS.
 >>   >       > -Reinstall the (entire) SBS suite.
 >>   >       > -Restore the Exchange information store
 >>   >       >
 >>   >       > Would this reset the license database?
 >>   >       > Does anyone have any suggestions other than my plan..? MVP's?
 >>   >       > Thanks in advance.
 >>   >       > --
 >>   >       >
 >>   >       > Regards
 >>   >       > Tom
 >>   >       >
 >>   >
 >>   >