DNS Server Enforcement across an AD Forest
Support in Active Directory for centrally enforcing client DNS settings via Group Policy Objects is at best patchy. Many of the settings work only with specific (and often legacy) versions of Windows; the “DNS Server” is one such setting. It is supported only on Windows XP Professional meaning no support is available for Windows Server 2000, 2003, 2008, Windows Vista or Windows 7. In most environments workstations receive their DNS Server configuration settings automatically via DHCP. These settings can be changed by configuring either the DHCP server global or scope settings, (note: TCP/IP settings configured locally on a computer override the settings provided by DHCP). While commonly servers have their TCP/IP settings statically configured.
One possibility as to why Microsoft has not pursued widening the DNS Server GPO setting support for newer releases of Windows is that network configurations particularly on servers are often more complex, for example multiple network interface cards (NICs) or multiple VLANs trunked into a single NIC. In such scenarios it would be difficult to apply settings in a GPO to a specific targeted NIC on a server. Read more
Before jumping into this post the following,
Ensuring replication is running smoothly across an Active Directory forest is a primary Administration task. Best practice recommends the ongoing monitoring of Active Directory replication using SCOM or another enterprise management tool, monitoring can also be performed using repadmin (repadmin /showrepl * /csv) together with a little scripting to interpret the output. Typical symptoms of replication issues are objects not being available in one or more site(s), for example a recently created user account, a printer or a directory share is not visible for a subset of users.



LINKEDIN
RSS FEED