Re: Moving from NT4 DC to Active Directory 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello,
If you not going for a single domain solution it should be because you have
bad bandwidth between your branches and much data to replicate, I don't
think that is the case so I should go for a single forest, with a single
domain. I'm strongly recommend to have the domain controllers running DNS
for AD. Your past authentication issues should not be a problem with AD
since you can define sites and subnets and decide that the local office
connects to its own DC.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
----------------------------------------------------------------
"Newbie" <newbie@xxxxxxxxxxx> skrev i meddelandet
news:#4ppoa4GGHA.532@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I'd like to gather some information how to best implement our domain
> migration. We have about 1000 employees in 3 local offices (fiber among
the
> local offices), 1 remote office with about 40 employees (BC Canada), 2
> remote offices with about 10 employees in each office (France).
>
> All offices have BDC except one branch office in France - it's running SBS
> 2003 Premium with its own Exchange mail server.
>
> Currently, we're having issues with the other remote office in France
where
> the BDC will kill the connection with the authentication traffic. We have
> blocked the firewall from authenticating and we do a manual sync roughly
> once a week. However, the clients are noticing slow logins.
>
> We'd like to migrate to Exchange for mail/calendar along with the domain
> migration. Our DNS servers are Unix based and not sure if we should keep
it
> the way it is?
>
> Should we sub-domain the branch offices to ease on the traffic going
through
> the pipe? Your help is much appreciated.
>
> Simon
>
>


.



Relevant Pages

  • Moving from NT4 DC to Active Directory 2003
    ... remote offices with about 10 employees in each office. ... All offices have BDC except one branch office in France - it's running SBS ... 2003 Premium with its own Exchange mail server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Authenticating against a user/pwd list on another server?
    ... Not quite sure why you are talking about a BDC? ... the BDC) will be used to handle the authentication handshake. ... >> You can't authenticate against another servers local SAM. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Authenticating against a user/pwd list on another server?
    ... you are correct, if I logon within the local network, then there is no popup ... they logon to theire computer (we have a local BDC, the PDC is at a remote ... > the BDC) will be used to handle the authentication handshake. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Moving from NT4 DC to Active Directory 2003
    ... We only have slow links across the ... the bandwidth is like 2mbps. ... Your past authentication issues should not be a problem with AD ... >> remote offices with about 10 employees in each office (France). ...
    (microsoft.public.windows.server.active_directory)
  • Re: upgrading domain/forest function level question
    ... A NT 4.0 BDC only hold a writeable copy of the SAM. ... not be able to manually add this user account to the NT 4.0 BDC. ... authentication is used the NT4 BDC would not be used for authentication. ...
    (microsoft.public.win2000.active_directory)