The Active Directory Topology service on server '{0}' is hard-coded to use these Active Directory global catalog servers: '{1}'. This configuration isn't recommended because it has limited failover options. Having multiple domain controllers configured is recommended for redundancy. Click 'get help fixing this issue' in the actions pane located on the right side of the screen for assistance.
The Active Directory Topology service on server '{0}' didn't detect any Active Directory global catalog servers in the local ...
The Active Directory Topology service on server '{0}' is hard coded to use Active Directory domain controller servers '{1}' ...
The Active Directory topology service on server '{0}' is hard-coded to exclude these Active Directory domain controllers: ...
The Active Directory Topology service on server '{0}' is hard-coded to use these Active Directory domain controllers: '{1}'. ...
The Active Directory Topology service on server '{0}' is hard-coded to use these Active Directory global catalog servers: ...
The Active Directory Topology service on server '{0}' isn't hard coded to use Active Directory domain controller servers ...
The AD FS deployment advisor walks you through the steps to deploy an on-premises Active Directory Federation Services (AD ...
The AD FS namespace (for example, fs.contoso.com) is listed in the Local intranet zone in %BRAND_INTERNET_EXPLORER%. For ...
The AD FS SSL certificate must include the AD FS Farm Name in order to process user requests. The certificate configured ...