Single Master Operation

mishoomishoo Posts: 43Member ■■□□□□□□□□
In AD what is mean by Single Master Operation.i got the term Multimaster Replication but got confused with Single Master Opertion. icon_confused.gif:
can any one clear icon_rolleyes.gif

mishoo

Comments

  • clarkyclarky Posts: 18Member ■□□□□□□□□□
    Pretty much means that you can place one of the five roles on different domain controller in the domain. Single master operations - correct me if I'm wrong.

    Every forest needs to have;
    SCHEMA MASTER
    DOMAIN NAMING MASTER

    Every domain needs to have;
    PDC
    RID
    INFRASTRUCTURE

    The infrastructure server can be on any domain controller other than a global cataloge server.
  • jmc724jmc724 Posts: 415Member
    To elaborate more on this topic:

    There can be only 1 (ONE) schema master and domain naming master in a forest.

    But there can be many pdc, rid and infrastructure master in the domain.

    But if you have only 1 domain/forest then roles arent important.

    GC can be on the same domain controller or on a diferent one if you have many dcs. You can also move roles to any dcs. But if you move the RID and Schema master, you will have to remove the dc that had those roles on it from the network (re-partion, format, clean install to use the same computer) or else you will have a corrupt AD environment.
    What next?
  • mishoomishoo Posts: 43Member ■■□□□□□□□□
    humm its means that a single Domain with the five roles???
    i am sorry if it feels annoying to you. i know abt schema master, GC and stuff but i can't figure abt single master operation in the reply ??
  • Ricka182Ricka182 Posts: 3,359Member
    Flexible single master operation (FSMO, F is sometimes floating), or just single master operation or operations master, is a feature of Microsoft's Active Directory (AD).

    FSMOs are specialised domain controller (DC) tasks, used where standard data transfer and update methods are inadequate. AD normally relies on multiple peer DCs, each with a copy of the AD database, being synchronised by multi-master replication. The tasks which are not suited to multi-master replication, and are viable only with a single-master database, are:

    One only in each AD forest

    Schema Master that manages modifications to the AD schema and its replication to other DCs.
    Domain Naming Master that manages adding, removing, and some modification operations for domains.
    One only in each domain

    Relative ID Master that allocates security RIDs to DCs to assign to new AD security principals (users, groups or computer objects). It also manages objects moving between domains.
    Infrastructure Master that maintains SIDs, GUIDs, and DNs for objects referenced across domains. Most commonly it updates user and group links.
    PDC Emulator that emulates a Windows NT Primary Domain Controller. It is also the favored DC for other DCs in replicating and confirming password information.
    FSMO roles can be easily moved between DCs using the AD snap-ins to the MMC or using ntdsutil, hence the use of the word flexible in the name.

    Some may include domain controllers holding a global catalog (GC) in this group as well. Certain FSMO roles depend on the GC. For example, an infrastructure master must not be a domain controller with a global catalog in a multi-domain forest (but should be close to a GC), while the domain naming master shouldt be a DC with a GC.

    By default AD assigns all operations master roles to the first AD DC created. This is not a satisfactory position. Microsoft recommends the careful division of FSMO roles, with standby (not active!) operations masters for each role - in the event of an unrecoverable failure other DCs can seize the lost roles. Further the PDC emulator and the RID master should be on the same DC, if possible. The schema master and domain naming master should also be on the same DC.

    Other subsidiary roles exist for AD Sites. They must have a licensing server, although it does not have to be a DC. Sites also need at least two bridgehead servers (primary and backup), through which replication data from other sites is managed.

    It seems that the term FSMO is being depreciated in favour of operations masters.
    i remain, he who remains to be....
  • jmc724jmc724 Posts: 415Member
    Ricka explained it in detail that you should understand.

    If not you will have to read or even try looking at the roles and understand the importance of them in an enterprise environment.
    What next?
  • mishoomishoo Posts: 43Member ■■□□□□□□□□
    thanks alot ricka .i have gone through a book as well and your explanation is also very well.it cleared the confusion in my mind.

    There are five Different roles of FSMO
    1.Schema Master deals with the updates and changes of schema,
    2.Domain Naming Master delas with the Domain Contollers,
    3.Relative ID manages the distribution of the RID numbers to the objects,
    4.PDC Emulator acts like a win NT PDC(mixed mode).
    5.Infarstructure Master updates group members as necessary.

    every update and changes are being synchronised by Multi-Master replictaion.
    These five roles are Single Master Operations.

    icon_cool.gif have i done it?
  • jmc724jmc724 Posts: 415Member
    Except you have to understand the pdc emulator more, creation of accounts, managing password.

    If pdc is offline, new users cant login or change password.
    What next?
  • mishoomishoo Posts: 43Member ■■□□□□□□□□
    yes i know i need to put more efforts on the way icon_idea.gif ....
  • KtatavarthyKtatavarthy Posts: 1Member ■□□□□□□□□□
    Single Master Operation is When you try to move a Single Master Operation from one domain to other domain within the forest is called FSMO.

    This Movement is called FSMO.

    Thanks
    Krishnamurthy
    Thanks & Regards
    Krishnamurthy
Sign In or Register to comment.