Well, if a users at branch37 logs in, and begins getting the "office
2003 full install" GP software deployment package, he needs to be
pulling it from his local file server (site37)(on his LAN), not one of
the central office site servers (CODC3)(one T1 WAN hop away) or heaven
forbid one of the other branches (site21)(2 T1 WAN hops away) because:
1. he will be tying up the WAN
2. the package will take forever to install
3. the package may fail
4. he may be tying up 2 wan links

This is why I need to find out why / HOW DFS determines WHICH server a
user will pull the packages from.

I thought about this, and to get around it, I could create separate
Group Policies for each site, but that would be alot of administrative
overhead, and alot (remember, I have ~70 sites, plus my CO) of Group
Policies floating around out there.

Thoughts or best practices?



--
troy12n
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message2553337.html