Windows Server 2008

1. WINDOWS SERVER 2008 2. WINDOWS 2008 Editions 3. WINDOWS 2008 Server Core 4. APPROX. COST OF WINDOWS SERVER 2008 5. Upgrade / Migrate 6. Upgrade from previous OS 7. WINDOWS SERVER 2008 INSTALLATION 8. Windows Server 2008 Activation 9. Activation Method 10. RAID 11. BACKUP and RECOVERY 12. Wbadmin 13. BACKUP Utility 14. Windows Recovery Environment 15. Server Roles for WINDOWS SERVER 2008 16. IP-ADDRESSING and IPV4 17. IPV6 18. Remote Desktop Connection 19. Steps for Remote Desktop Pc from Client PC 20. Remote Desktops 21. MANAGING SERVER CORE 22. TERMINAL SERVICES (TS) 23. TERMINAL SERVICES MANAGER 24. MANGAING FILE AND PRINT SERVERS 25. Share Folder 26. Attrib (Attribute) 27. Windows Registry 28. Disk Quotas 29. Disaster Recovery Tools 30. MMC 31. Remote Assistance 32. Signed & Unsigned Driver 33. Hardware Profile 34. CHKDSK.EXE(Check Disk) 35. Disk Defragmenter (DFRG.MSC) 36. ACTIVE DIRECTORY REVIEW 37. Introduction to AD 38. TRUST 39. FSMO 40. GC (GLOBAL CATALOG) Server 41. Site 42. AD replication 43. Backup of Active Directory (DC) 44. Understanding USER, GROUP & COMPUTER 45. Create Local User & Multiple Users 46. GROUP SCOPE 47. Public and Private key encryption 48. Trust concept of CA working 49. ETHERNET CARDS 50. Availability and Security 51. General Server Security Issues 52. OSI MODEL 53. Data Encapsulation 54. TCP/IP or DoD Model 55. Protocol Working at Host to Host (Transport) layer 56. NETWORK MONITOR 57. Internet Information Services 58. Monitoring Tools 59. DNS [Domain Name System] 60. DNS ZONE 61. Remote Access Authentication Process 62. Remote Access Interview Question & Answer part 1 Tutorials Interview Question & Answer part 2 Tutorials Interview Question & Answer part 3 Tutorials Interview Question & Answer part 4 Tutorials Interview Question & Answer part 5 Tutorials Interview Question & Answer part 6 Tutorials Interview Question & Answer part 7 Tutorials
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