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

GC (GLOBAL CATALOG) Server tutorials


When we have installed AD and created Domain Controllers, Trees, Forest and other objects. How users can finds those objects?

  • So when any query is made it will search GC.

  • The client uses DNS to find the objects which are stored on GC server

  • The client sends a request to find object. It will be sent to port no 3268

  • The GC server then returns the information, or direct the query to AD

  • GC contain partial attribute subset for every object such as USERS, GROUP, COMPUTER, PRINTER, OU etc of all Domain through out the Forest. is searched when any one want to search object in that forest.

  • When all the objects are stored on GC Server, searching will be is a fast.

  • by default the first Domain Controller installed in a new forest becomes the Global Catalog (GC) Server for that domain.


Global Catalog server store

  • Full replica for its own domain

  • Partial information for other domains in the forest such as logon name, first name and last name etc. This way it cuts down the amount of network traffic between two domain.


Designating Global Catalog Server

  • Assume you have 2 office in different Cities lets say Mumbai and Delhi. Any one who want to search AD database will issue query lets say at Delhi, it have to pass through the WAN line to locate where is GC (typically at Mumbai Server where GC is located) and again return back result to user over WAN line.

  • To resolve slow response you can designate GC server to remote DC and sites, this will speed up global searches


To do so

  • Start – All Program – Administrative Tools – Active Directory Sites and Services

  • Select Servers – and choose DC – double click on it

  • Right Click “NTDS Settings” and choose “Properties”

  • R Global Catalog option.

Note:- Depending upon AD objects and new Global Catalog server will take some time to update partial information from all DC to itself.


Global Catalogs and Universal Group Membership Caching

  • A global catalog server needs to be contacted during logon. Place a global catalog server in each site to speed up logon.

  • A global catalog server also maintains universal group membership. Group membership needs to be consulted during resource access.

  • Only one server per site needs to be a global catalog server.

  • Enabling the universal group membership caching feature for a site will let users who are members of a universal group log on in the event of a WAN link failure. If the only need is to obtain universal group membership information, enabling this feature for a site is a better solution than creating a global catalog server in the site.

  • All servers in a site must be running Windows Server 2003 for universal group membership caching to work


To do so

  • Start – All Program – Administrative Tools – Active Directory Sites and Services

  • Select Servers – and choose DC – double click on it

  • Double Click on “NTDS Settings” and

  • R Enable Universal Group Membership Caching


Pr.Pg border                                              Next Pg