Difference between revisions of "AD Topology"

From Stadm
Jump to navigationJump to search
(Created page with "Category:Projects Category:Samba Category:Samba4AD =Topology= ==Servers== *Rumba(CentOS 7) **Services: AD Controller *Limbo(Centos 6) **Services: AD Controll...")
 
Line 8: Line 8:
 
==Servers==
 
==Servers==
 
*Rumba(CentOS 7)
 
*Rumba(CentOS 7)
**Services:
+
**AD Controller
  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
 
*Limbo(Centos 6)
 
*Limbo(Centos 6)
**Services:
+
**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
 
  
 
*Daft(Windows Server)
 
*Daft(Windows Server)
**Services:
+
**Windows Server Update Services(WSUS) - provides domain joined computers update management if GPO is applied
WSUS
+
**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

Revision as of 11:24, 12 April 2016


Topology

Servers

  • 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
  • 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)
  • 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)