Remote Sites

  • Thread starter Thread starter Simon B
  • Start date Start date
S

Simon B

I have a number of small remote sites I look after, I
would offer you the following advise.

If you only have a 128K link put a DC at the remote site
even an old PIII PC is beter than nothing.

If the line speed is 512 K + you can avoid haveing DC on
site but the logon / PC startup takes a bit longer. With a
512K + link if you use Roaming profiles saved locally you
can get a way with it for a few users.
 
In
Simon B said:
I have a number of small remote sites I look after, I
would offer you the following advise.

If you only have a 128K link put a DC at the remote site
even an old PIII PC is beter than nothing.

If the line speed is 512 K + you can avoid haveing DC on
site but the logon / PC startup takes a bit longer. With a
512K + link if you use Roaming profiles saved locally you
can get a way with it for a few users.
Click to expand...

To add, among many other things to optimize this, install DNS on this server
(either using AD Integrated zones, Secondary zone or just a caching server)
so the clients use this DNS instead of querying across the WAN.

FYI: AD uses an algorithm to check the link speed in order to determine if a
certain GPO settings will apply or not. The magic number, be default, is
500k, which is adjustable in the Default Domain GPO.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
If you use WINS and have such "single segment sites" then it is also
a good idea to make the computers "M-node" NetBIOS resolvers
so that no WINS server is needed at (a lot of) all these sites -- local
resolution will happen by broadcast first and you configure the WINS
server at the upline site for those times the clients need to go "cross
WAN."
 
Back
Top