AD Best Practices

1 minute read


For AD DS’ DNS domain name, use a subdomain of the main web domain ( or use a dedicated web domain ( owned by the organisation.

Always assume that users will roam.

Ensure that the PDC is syncing time from an external source, not its hardware / host.

Operate according to the Principle of Least Privilege.

If certain users require administrative permissions, issue them with a seperate, dedicated administrator

Use very long passwords on service accounts.

Set ACLs using security groups.

Use SSO whenever possible. If native / direct isn’t possible, maybe via something like JumpCloud.

Use the central store for policies.

Use Microsoft LAPS.

Don’t be afraid to use advanced features of Group Policy (loopback, preferences, item-level targeting, etc).

Don’t modify the default domain policy => create a new GPO and move it higer in the linking priority.

Use Group Policy to enforce Windows’ defaults settings for UAC, firewall, etc.

Set DC servers’ DNS servers to others and itself last.

Rename the “administrator” account.

Don’t let users use generic / shared user accounts (“reception”, “goodsin”, “meetingroom”, etc).

Have at least 2 domain controllers and schedule their Windows updates so they don’t both reboot at the same