The server which holds the PDC FSMO role it can be viewed by few methods
1. go to admin option->users and computers -> select domain->rt click fsmo roles gives three tabs of domain fsmo role holder.
2 for other roles go to admin option->use site -> forest level roles you can see in the properties of each fsmo role holder.
3. NTDS util will help you to see the roles.
Active Directory Schema
PDC emulator has the role to synchronize time in the domain
Pdc emulator
PDC Emulator will be responsible for time synchronization
the server which holds the FSMO role it cna be changed by few methods 1. go to admin option->users and computers -> select domain->rt click fsmo roles gives three tabs of domain fsmo role holder-> change from there. 2 for other roles go to admin option->use site -> forest level roles you can cchange in the properties of each fsmo role holder. 3. NTDS util will help you to see the roles and transfer
The ntdsutil command utility will allow you to transfer and seize a FSMO role.
Seizing an FSMO can be a destructive process and should only be attempted if the existing server with the FSMO is no longer available.
Your mum goes down
There is no releation between FSMO roles and replication. However Infrastructure master role replicate the cross domain group membership changes.
RID
Role copy
Schema Master and Domain naming master.
Windows 2000/2003 Active Directory domains utilize a Single Operation Master method called FSMO (Flexible Single Master Operation), as described in Understanding FSMO Roles in Active Directory. In most cases an administrator can keep the FSMO role holders (all 5 of them) in the same spot (or actually, on the same DC) as has been configured by the Active Directory installation process. However, there are scenarios where an administrator would want to move one or more of the FSMO roles from the default holder DC to a different DC. Windows Server 2003 Active Directory is a bit different than the Windows 2000 version when dealing with FSMO placement. In this article I will only deal with Windows Server 2003 Active Directory, but you should bear in mind that most considerations are also true when planning Windows 2000 AD FSMO roles