It is becoming commonplace to disable RC4 encryption for Kerberos. This is typically accomplished with the following group policy:
When RC4 is disabled, an Exchange server will use AES with Kerberos when authenticating an LDAP connection. That works fine as long as it's talking to a DC in its own domain.
However, when Exchange tries to talk to a DC in a different domain (for example, if a GC in a different domain is in the local site), this can be a problem, because AES is not enabled on trusts by default.
Also need to include this test within SetupAssist as well, this appears to cause issues with trying to install Exchange that makes it so it would appear that you don't have the correct group membership.
It is becoming commonplace to disable RC4 encryption for Kerberos. This is typically accomplished with the following group policy:
When RC4 is disabled, an Exchange server will use AES with Kerberos when authenticating an LDAP connection. That works fine as long as it's talking to a DC in its own domain.
However, when Exchange tries to talk to a DC in a different domain (for example, if a GC in a different domain is in the local site), this can be a problem, because AES is not enabled on trusts by default.
When RC4 is disabled, and this checkbox is not checked, Exchange will experience LDAP_LOCAL_ERROR when attempting to establish an LDAP connection to a DC in that domain. A network capture will show KRB5KDC_ERR_ETYPE_NOSUPP error in the Kerberos response. This issue is also described here: https://docs.microsoft.com/en-us/troubleshoot/windows-server/windows-security/unsupported-etype-error-accessing-trusted-domain
We could potentially check for this issue with the following logic:
0/not set = RC4, 24 = AES, 28 = RC4 or AES. So if this is 0 or not set, flag it in that scenario.