Updating primary domain controller

09-May-2015 20:11 by 7 Comments

Updating primary domain controller

This is a must to read article for any system administrator who administers Microsoft Windows Servers.

FSMO stands for Flexible Single Master Operations, and in a forest there are at least five roles.In this article, I will be showing you how to transfer the FSMO in Windows Server 2008, Summary There are five FSMO roles in a forest, to transfer any of these roles you have to use the appropriate Active Directory snap-in.In my next article, I will be showing you the complete steps required to successfully migrate/upgrade your domain controller to a new hardware server.Here we will configure your primary domain controller (PDC) to connect to an external source to keep your time synchronized up with the rest of the world.By changing the primary DC’s time source to an external source, the changes will be replicated from the PDC to other clients in your domain; limiting the amount of bandwidth needed to synchronize with an external source.First, I am going to reference much of the information provided by Marc Weisel.

Since version 4.0, Samba can, additionally to a NT4 PDC, act as a Domain Controller that is compatible with Microsoft Active Directory.

In the following, we explain how to set up Samba as an Active Directory Domain Controller from scratch.

In addition, this documentation is the start for upgrading an existing Samba NT4-style domain to a Samba AD.

Whilst the Domain Controller seems capable of running as a full file server, it is suggested that organisations run a distinct file server to allow upgrades of each without disrupting the other.

It is also suggested that medium-sized sites should run more than one DC.

It also makes sense to have the DC's distinct from any file servers that may use the Domain Controllers.