| Event Id | 2092 |
| Source | MSExchangeDSAccess |
| Description | Process <process name> (PID=<process id>). DSAccess will use Domain Controllers specified in the registry. |
| Event Information | According to Microsoft: This event will be seen if Diagnostics Logging on the Configuration category of DSAccess is set to Minimum for the server. It indicates that DSAccess will use only the domain controllers specified in the registry. This event means that the process of automatic domain controller discovery will not occur. It is dangerous because if all the servers specified in registry become unresponsive, DSAccess will be unable to fail over to another set of domain controllers. This setting does not affect the automatic discovery of global catalog servers. It does affect, however, the choice of the configuration domain controller, which is chosen from the registry specified domain controller list (unless the configuration domain controller is set to a fixed server). The relevant registry key is: HKLM\System\CurrentControlSet\Services\MsExchangeDSAccess\Profiles\Default\<UserDCName>. User Action : It is recommended that domain controller names be specified in the registry only if the automatically chosen domain controllers produce undesirable results. In such a case, determine what the problem is, fix it, and delete the registry value so that the domain controllers are discovered automatically. |
| Reference Links | Microsoft product: Exchange Version: 6.5.6940.0 Event Source: MSExchangeDSAccess Event ID: 2092 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.