Re: Using 2000 SBS on a 2003 Standard Domain

all versions of SBS have supported additional domain controllers.

Don't eat yourself up too much about it though, it's one of the most widely
misunderstood aspects of 'SBS limitations'. SBS has always been 'king of the
hill', MS used to use a thoroughly fictional idea about it being 'first DC
in the domain' and in the NT days (SBS 4.x) this was effectively (though
possibly not with some creative thought) true.

An SBS must hold all FSMO roles and be a GC. Additional DCs in the domain
cannot be FSMO holders (because the roles are exclusive at either the forest
or domain level and SBS supports only single domain, single forest) but can
be GCs (a non exclusive role).

You know what the funny part is? You don't need CALs to access those
additional DC (or member server) machines, SBS CALs cover access to all
Win2K or later servers in the SBS domain.

<newsgroups@xxxxxxxxxx> wrote in message
news:1156767372.103517.227820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I was under the impression that a BDC could not be added to a Small
Business Server Domain. Is this only true with SBS 2003?
Charlie Russel - MVP wrote:
You can't move the AD off of SBS. Period. But you _could_ add Server 2k3
as
a secondary domain controller, and have it do Print and File, and VPNs.
You
should keep DHCP with your SBS box, and DNS should be AD integrated and
thus
present on both boxes. You could certainly set the DHCP to have your new
server as the primary DNS for clients, though I wouldn't normally
recommend
it. But if for some reason the new, secondary, domain controller had to
be
removed, it's easy enough to deal with.

VPNs - you can put this wherever you want. So if you move it off to the
new
box, that's fine. But you won't have the CEICW to configure stuff for you
there, I'm afraid. :(


--
Charlie.
http://msmvps.com/xperts64


newsgroups@xxxxxxxxxx wrote:
I have a situation where we have outgrown a Windows 2000 SBS Server. We
have about 50 clients, 9 VPN connections, print & file sharing and spam
filtering on top of all of the other SBS functions & we are running out
of drive space fast. We have added new drives already and at this
point it is not an option to add more drives. What I would like to do
is add a new Windows 2003 Standard Edition Server as the PDC to do AD,
DHCP, DNS, VPNs Print and File sharing and then keep the 2000 SBS
server to just handle exchange and spam filtering and disable all other
features. I do understand that the 2000 server cannot run as a BDC and
will not share the AD. What sort of problems am I going to run into by
doing this?



.

Relevant Pages

  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)
  • Re: wds, how many computers can be imaged at the same time
    ... SBS itself must be the FSMO roles holder. ... you can have additional member server. ... Windows Server 2008 WDS supports multicasting. ... domain controller, ...
    (microsoft.public.windows.server.general)
  • RE: the dns service cannot open active directory
    ... SBS 2003 machine as an additional domain controller of a Windows 2000 ... The new SBS 2003 computer must be a global catalog server and must be the ... On a Windows 2000 domain, you must prepare Active Directory before you ...
    (microsoft.public.windows.server.sbs)
  • Re: Small Business Server 2003 Premium Edition automatically shuts
    ... I have had to place SBS as my internal server connecting to 'Enterprise Edition' via a hub, which is then connected to my router. ... I have been told that placing SBS on the edge of my network as a domain controller is dangerous. ...
    (microsoft.public.windows.server.general)
  • RE: Cannot access companyweb
    ... to migrate from SBS 2003 to SBS2003, in this period, you can't achieve this ... 825763 How to configure Internet access in Windows Small Business Server ... By this method, you need to manually restore Exchange data, SharePoint ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)