Re: Adding additional domain controller on member server

Greg0145 <Greg0145@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I'm taking your advice and purchasing a new server. We have too much
on the server to chance breaking it.

As Homer Simpson might say, that's S-M-R-T.



"Lanwench [MVP - Exchange]" wrote:

Greg0145 <Greg0145@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We currently have 1 Windows Server 2003 domain controller. Our
network is not huge, about 125 users so we have only used 1 thus
far. I want to add another domain controller just to be safe and
have it in case of emergency.

That's a very good thing to do - that's actually a lot of users to
have only one DC to rely on.

My dilema. I ran DCPROMO from a member server.
It asks whether this is a new or additional domain controller. Of
course it's an additional controller but right below this is an
exclamation sign that states "All local accounts will be deleted
when using this option" or something to that effect. I may be over
cautious but want to get some feedback before proceeding any
furthur.

Check to see what local accounts exist - anything created for
services, etc? Users themselves won't have accounts on here.


One, this server is running as a file server for our entire network
and also running our company email server (not exchange, third
party).

Good, because running dcpromo on an Exchange server will break it.
Frankly, if this were my network, I'd rather leave this box running
as a member server & get a cheap & cheerful little server running
w/W2003 to be a DC only, if you have that option - it's preferable,
although not mandatory.

If the local accounts are deleted, would this cause problems?

That depends - how many do you have?

Does it replace security, such as local Administrator account, with
the domain administrator acount on all files and directories?

If this is a member server in the domain, that's who should have
permissions anyway. Check first and make it so. But you can always
override the permissions with a domain admin account & re-set them
if you need to.


Any help is greatly appreciated.



.

Relevant Pages

  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)
  • RE: Strange Irregular DNS/Networking Problems
    ... Disable offloading in the network adapter properties ... After doing this on the server and the client it seems to have fixed ... Tested with just one client and the domain controller on the ... "Meinolf Weber" wrote: ...
    (microsoft.public.windows.server.dns)
  • RE: Strange Irregular DNS/Networking Problems
    ... Disable offloading in the network adapter properties ... After disabling all these things file transfers across the network are a lot ... My network is not a complicated set up and only has one domain controller. ... I tried doing a net stop server after the network stalled as from an article ...
    (microsoft.public.windows.server.dns)
  • Re: IPSec / domain isolation: confusing MS documents
    ... workstation, he is able to attach to server ressources again, but for our ... The user right for access this computer from the network ... will not work for computer accounts unless ipsec is being used. ... securing a domain controller. ...
    (microsoft.public.windows.server.security)
  • Re: How to connect the NT4 PCD from windows 2003 server
    ... internal is on top of external on the network connection ... for lmhosts files on NT4 server, ... >> type glcdom, which is my NT4 domain controller name, it ...
    (microsoft.public.win2000.security)