Forest/Domain Prep & Schema Update Cause member workstation to make ldap calls

Ryan-AD 21 Reputation points
2022-05-17T01:30:32.667+00:00

I have a approx. 3000 endpoints with a small connection back to local domain controllers. Bandwidth is approx. 60mbps. We have noticed that when we run a schema update or domain/forest prep, this causes these workstations to completely saturate this connection with ldap calls. First occurrence happened during a Exchange CU update and the CU required a schema update. Second occurrence happened when we promoted the first server 2019 domain controller into the environment and a domain/forest prep was required. We cannot figure out what it is these workstations are downloading at the time of this bandwidth constraint.

Do workstations require to download a local copy of the schema? Do they require downloading a copy of the domain\forest instructions when a change is made?

Any suggestions or help would be greatly appreciated.

Thank You,

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,986 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,479 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,609 questions
0 comments No comments
{count} votes

Accepted answer
  1. Gary Reynolds 9,416 Reputation points
    2022-05-17T10:05:27.883+00:00

    Hi @Ryan-AD

    I don't know specifically what the workstations are doing, but I can speculate on what is happening. When you do a schema update, the last instruction in the update file is to flush the schema cache on DC using the UpdateSchemaNow RootDSE modify operators. It likely that this and added a domain controller to the domain will cause the Exchange servers to issue a refresh command to all connected clients, so they refresh their cached information about the Exchange environment, any newly added AD attributes, and the DC that exist in the domain.

    Gary.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.