Difference between revisions of "AD Topology"

From Stadm
Jump to navigationJump to search
Line 12: Line 12:
 
**Group Policy Objects(GPO) must be edited on Rumba(through Group Policy Management on a  domain joined Windows computer)
 
**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
 
***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
 
*Limbo(Centos 6)
 
*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)
 
**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
 +
 
===Windows===
 
===Windows===
 
*Daft(Windows Server)
 
*Daft(Windows Server)

Revision as of 11:57, 19 April 2016


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

Windows