troy12n
10-12-2006, 06:57 PM
I have also set up Active directory "SITES" and each branch office is
its own "SITE". Users at that site log in to their LOCAL domain
controller, which also hosts their files, printers, etc...
Since AD is somewhat different than NDS/edirectory in this regards
(security boundaries) all the users for each department, regardless of
physical location will be in a single departmental OU, but there will
also be a "workstations" OU where ALL workstations will be housed.
Inside this OU, things are separated by department, and site, looking
more like our current NDS tree.
The reason for all of this, and perhaps I am just over-thinking it, is
due to different group policies being applied to computers versus
users.
For instance, I have a "domain wide" login script at the root which
does things like maps drives and printers, sets other variables, etc,.
However, I have software deployment group policies which apply to ONLY
workstations, and need to be applied at the "workstation OU" level.
This is where I am at for the question.
I have set DFS (and it seems to be actually working!) and all my
software deployment group policies are set to use DFS root paths,
versus hard coded share paths.
This is working fine. BUT!!!
I have no idea where the users are getting their software installs
from.
IE: which specific server is serving up the software deployment.
You might say "well who cares".
--
troy12n
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message2553337.html
its own "SITE". Users at that site log in to their LOCAL domain
controller, which also hosts their files, printers, etc...
Since AD is somewhat different than NDS/edirectory in this regards
(security boundaries) all the users for each department, regardless of
physical location will be in a single departmental OU, but there will
also be a "workstations" OU where ALL workstations will be housed.
Inside this OU, things are separated by department, and site, looking
more like our current NDS tree.
The reason for all of this, and perhaps I am just over-thinking it, is
due to different group policies being applied to computers versus
users.
For instance, I have a "domain wide" login script at the root which
does things like maps drives and printers, sets other variables, etc,.
However, I have software deployment group policies which apply to ONLY
workstations, and need to be applied at the "workstation OU" level.
This is where I am at for the question.
I have set DFS (and it seems to be actually working!) and all my
software deployment group policies are set to use DFS root paths,
versus hard coded share paths.
This is working fine. BUT!!!
I have no idea where the users are getting their software installs
from.
IE: which specific server is serving up the software deployment.
You might say "well who cares".
--
troy12n
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message2553337.html