Windows Server 2003

1. WINDOWS SERVER 2003 2. Windows Server 2003 different Versions 3. Hardware requirement for Windows Server 2003 4. HCL - Hardware Compatibility List 5. Keep following points in mind before Upgrade Migrate 6. Upgrade from previous OS 7. WINDOWS SERVER 2003 INSTALLATION 8. Windows Server 2003 Activation 9. MANAGING LICENSING 10. Administrating License Logging Services 11. Managing Software Installation and Maintenance 12. Essential Administration Tools 13. Difference between RAID & WINDOW BACKUP 14. RAID – Redundant Array of Inexpensive DISK 15. Disk Mirroring & Disk Duplexing 16. Disk partition and File System – FAT, FAT32, NTFS 17. Remote Desktop for Administration & Terminal services 19. To connect to Remote Desktop Pc from Client PC do as follow 20. Remote Assistance 21. Difference between RAID & WINDOW BACKUP 22. SYSTEM STATE DATA 23. IP-ADDRESSING and IPV4 24. IPV6 [Internet Protocol Version 6] 25. Signed & Unsigned Driver 26. Hardware Profile 27. CHKDSK.EXE (Check Disk) 28. Disk Defragmenter(DFRG.MSC) 29. Introduction to AD [Active Directory] 30. Difference between WORKGROUP & DOMAIN 31. Operating System that support Active Directory 32. FSMO [Flexible Single Master Operation] 33. GC (GLOBAL CATALOG) Server 34. Site 35. Disk Defragmenter (DFRG.MSC) 36. AD replication 37. AUTHORITATIVE Restore 38. TOOLS to Troubleshoot Active Directory Installation 39. Understanding USER, GROUP & COMPUTER 40.GROUP ACCOUNTS 41. User Profile 42. Roaming User Profile 43. Mandatory User Profile 44. Attrib (Attribute) 45. Taking Ownership 46. Copying and Moving Files and Folders 47. Server Roles for WINDOWS SERVER 2003 48. AVAILABILITY & SECURITY 49. General Server Security Issues 50. OSI MODEL 51. Data Encapsulation 52. TCP/IP or DoD Model 53. Protocol Working at Host to Host (Transport) layer 54. NETWORK MONITOR 55. Internet Information Services 55. Monitoring Tools 54. DNS [Domain Name System] 55. DNS ZONE 56. Remote Access Authentication Process 57. Remote Access
Pr.Pg Next Pg

FSMO [Flexible Single Master Operation] tutorials


  • FSMO role are defined based on AD installation. It keeps integrity of AD database

  • It is called Flexible cause we have Flexibility to transfer role on any DC or ADC, and thereby we can take advantage of Load Balancing.

  • AD is a multi master replication model. Each DC and ADC is Read/Write Capable.

  • Earlier NT model PDC [Primary Domain Controller] was Read/Write Capable while BDC [Backup Domain Controller] was Read only.


We have 5 FSMO role. They are grouped in two partition

  • Forest Wide Masters

  • Schema Master

  • Domain Naming Master

  • Domain Specific Masters

PDC [Primary Domain Controller] emulator

  • RID [Relative Identifier] master

Infrastructure master



  • It define attributed of object. Each object is based on some class and have attributes assigned to them.

  • For e.g. USER (Object) class may have attributes such as First name, Last name, email, address, AccountExpires, ….. SID [Security Identifier]

  • At Run – cmd – WHOAMI /ALL will show SID of object.

  • There can be only one Schema master in entire forest.

  • By default it is loaded on the First DC in the forest.


To know or change Schema Master role to another DC

  • Run – MMC – File – Add/Remove Snap in –Again select “ADD”

  • From there select Active Directory Schema Master Role – Add – Close – Ok

NOTE:- This role if not found, click on RUN – ADMINPAK.MSI

  • Right click on Active Directory Schema role, Select “Operational Master” and it will show you name of DC where Schema Master is assigned.

  • To change, click in “Change” button and assign it to another DC.


Domain Naming Master

  • It controls the addiction or removal of domains in the forest

  • There is only one domain naming master in a forest.

  • It keeps master database which keeps host of entries of domains name which are already created in domain. It ensures that the namespace is updated for these changes.

  • It keeps database of all domain already in forest so no duplicate name will occur.



  • It manages the integrity of objects moved within the domain and forest.

  • for e.g. as and when you create any user at any domain, this will check the consistency of Local AD database.

  • To check or change Infrastructure Master FSMO -

Start – All Programs – Administrative Tool - Active Directory User and computers

Select Domain – Right Click -- Operations Masters



  • It stands for Primary Domain Controller. It emulate PDC in interim mode.

  • When we install AD onto the PDC of NT 4.0 domain, it will automatically become the PDC emulator. SAM on PDC will become AD on DC.

  • when we migrate from PDC to DC, within overnight we cannot migrate rest of all BDC to DC. There for PDC emulator is used to communicate with BDC that are still in an NT 4.0 domain environment.

  • Once NT 4.0 domains are fully upgraded to Windows Server 2003 Domains, then there is no role for PDC Emulator.


To check or change PDC Emulator FSMO -

  • Start – All Programs – Administrative Tool - Active Directory User and computers

  • Select Domain – Right Click -- Operations Masters


RID Master

  • It stands for Relative Identifier.

  • When we create any leaf object it is associated with SID (Security Identifier)

  • SID consist of = Domain SID + GUID

  • Domain SID will remain same for every object in domain.

  • GUID (Globally Unique ID) is 128 but unique no that keeps on changing over a network. When you rename the object GUID never changes

  • RID master is responsible to generate unique GUID to avoid duplicate SID.

  • If any account is deleted and then recreated again it will be assigned new SID

  • You check SID do as follow

  • Start -- Run -- Cmd

  • WHOAMI /ALL to check SID of all objects.



To check or change RID FSMO -

  • Start – All Programs – Administrative Tool - Active Directory User and computers

  • Select Domain – Right Click -- Operations Masters


Locating FSMO

You can determine the current operations master for your logon domain by typing following command at

  • Start – Run – netdom query fsmo

  • It may give output which list each role owner by its FQDN

  • For e.g. Schema owner

  • Domain Role owner

  • PDC Role

  • RID pool manager

  • Infrastructure owner


Pr.Pg border                                              Next Pg