Book Image

Active Directory Administration Cookbook

By : Sander Berkouwer
Book Image

Active Directory Administration Cookbook

By: Sander Berkouwer

Overview of this book

Active Directory is an administration system for Windows administrators to automate network, security and access management tasks in the Windows infrastructure. This book starts off with a detailed focus on forests, domains, trusts, schemas and partitions. Next, you'll learn how to manage domain controllers, organizational units and the default containers. Going forward, you'll explore managing Active Directory sites as well as identifying and solving replication problems. The next set of chapters covers the different components of Active Directory and discusses the management of users, groups and computers. You'll also work through recipes that help you manage your Active Directory domains, manage user and group objects and computer accounts, expiring group memberships and group Managed Service Accounts (gMSAs) with PowerShell. You'll understand how to work with Group Policy and how to get the most out of it. The last set of chapters covers federation, security and monitoring. You will also learn about Azure Active Directory and how to integrate on-premises Active Directory with Azure AD. You'll discover how Azure AD Connect synchronization works, which will help you manage Azure AD. By the end of the book, you have learned about Active Directory and Azure AD in detail.
Table of Contents (16 chapters)

About FSMO roles

Active Directory uses the multi-master model, where domain controllers are all able to respond to client requests. When comparing to the old Windows NT 4 server-style Primary Domain Controller (PDC) and Backup Domain Controller (BDC) models, where BDCs were read-only until switched to become the only PDC, this model offers many benefits.

However, some tasks within Active Directory don't work well with the multi-master model. When designing Active Directory, Microsoft created five roles outside of the model, labeled FSMO roles, to prevent conflicting updates.

These roles can be flexibly assigned to domain controllers and seized when a domain controller holding the role fails. These roles offer single master operations within the scope of the roles. Hence the name FSMO role.

In every Active Directory environment there are five roles with two different scopes...