Re: Some basic AD/2003 setup questions.



1. The company doesn't use DHCP at this time. They have about 300 PCs
and use static private IPs. This helps identify users to their
accounting package. After reading several books, I can't tell whether
AD requires DHCP. Is it necessary?

Not required but it is easier and now would be the time to make the change.
Obviously the servers should have a static IP address.


2. They have one main office(275 users) and one small office(20 users)
connected via WAN/T1. My thought is there should be 1 Domain with 2
OUs(one for each location). I would therefore think you should have
20 DCs in each city for redundancy. Is this the right way to think

I would suggest one domain and put the branch office in it's own site. 20
DCs in each city might be over kill :-), at least 2 in the main office and
you should be able to get away with one DC in the branch.


3. The first DC will also host a data directory share. It is hoped
this will get the admin department's feet wet. This shouldn't be a
load issue should it?

I would suggest creating a member server at the main office to host the
share and hosting the shared folders for the branch office on the branch
office DC.


hth
DDS


<estctech@xxxxxxxxx> wrote in message
news:ed0455d4-9a4b-4ff5-99e0-c27f5381f444@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sorry for the newbie questions. I am helping convert a Netware 6.5
network to windows 2003. I have set up two MS2003 DNS servers and
they are functioning. I am getting ready to create a first AD DC.
1. The company doesn't use DHCP at this time. They have about 300 PCs
and use static private IPs. This helps identify users to their
accounting package. After reading several books, I can't tell whether
AD requires DHCP. Is it necessary?
2. They have one main office(275 users) and one small office(20 users)
connected via WAN/T1. My thought is there should be 1 Domain with 2
OUs(one for each location). I would therefore think you should have
20 DCs in each city for redundancy. Is this the right way to think
about it?
3. The first DC will also host a data directory share. It is hoped
this will get the admin department's feet wet. This shouldn't be a
load issue should it?

Sorry again for the newbie questions, but I've also only worked Novell/
UNIX. I'm sure these will be the first of many from me and my friend
at the company.


.



Relevant Pages

  • Re: Connect to DC from branch via VPN
    ... It has been decided that there will be no server at branch office. ... it would be easier to use DHCP in both locations. ... I think it would be possible to enable DHCP at branch router. ...
    (microsoft.public.windows.server.sbs)
  • Multiple routes on LAN now I cant get DHCP addresses
    ... used to get its internet access through a VPN connection to the main office. ... Before we were able to use DHCP for this (DHCP was on an old 2000 server. ... LAN subnet: 10.10.8.x / 24 ... I need this to work dynamically on this branch office ...
    (microsoft.public.windowsxp.network_web)
  • Re: Connect to DC from branch via VPN
    ... It has been decided that there will be no server at branch office. ... it would be easier to use DHCP in both locations. ... I think it would be possible to enable DHCP at branch router. ... If the notebook is at ...
    (microsoft.public.windows.server.sbs)
  • Re: question on setting up new subnet at branch office site
    ... I wouldn't go with client options in DHCP - it's just too much ... site on it's own subnet. ... for the branch office on your existing DHCP server. ...
    (microsoft.public.win2000.networking)
  • Re: DHCP Problem
    ... DHCP management console? ... and on the right pane of DHCP management console I see: ... The DHCP server you specified cannot be located. ... >> Windows 2000 AD domain to my branch office because we lost power during ...
    (microsoft.public.win2000.networking)