Difference between revisions of "AD Topology"
From Stadm
Jump to navigationJump to search| Line 16: | Line 16: | ||
**AD Controller(in case rumba goes down users can still authenticate, NFS mount points are on rumba though so anyone with a roaming profile will have issues loading and saving profile) | **AD Controller(in case rumba goes down users can still authenticate, NFS mount points are on rumba though so anyone with a roaming profile will have issues loading and saving profile) | ||
**Also running DNS forwarder that syncs w/ rumba | **Also running DNS forwarder that syncs w/ rumba | ||
| − | + | *Managing rumba and limbo: http://wiki.eri.ucsb.edu/stadm/Samba4_Administration | |
===Windows=== | ===Windows=== | ||
*Daft(Windows Server) | *Daft(Windows Server) | ||
Revision as of 13:04, 19 April 2016
Contents
Topology
Servers
Linux
- Rumba(CentOS 7)
- AD Controller
- Group Policy Objects(GPO) must be edited on Rumba(through Group Policy Management on a domain joined Windows computer)
- This is because GPO syncing is done through rsync and Limbo pulls the GPO changes from Rumba
- Running a DNS forwarder, DNS can be viewed using RSAT, nothing really ever needs to be changed there
- Limbo(Centos 6)
- AD Controller(in case rumba goes down users can still authenticate, NFS mount points are on rumba though so anyone with a roaming profile will have issues loading and saving profile)
- Also running DNS forwarder that syncs w/ rumba
- Managing rumba and limbo: http://wiki.eri.ucsb.edu/stadm/Samba4_Administration
Windows
- Daft(Windows Server)
- Windows Server Update Services(WSUS) - provides domain joined computers update management if GPO is applied
- Can be used to manage Domain(GPO's and Users/Computers)
- RSAT can as well from any domain joined machine: https://wiki.samba.org/index.php/Installing_RSAT
- atlas/quinaya/tliyel-Remote Desktop Servers that need a DC to provide Windows RDS
