Validating the state of active directory

To fix this one must manually create a new "separate"active directory integrated primary zone _msdcs.

The middleware then takes care of: - Downloading the Azure AD metadata, finding the signing keys, and finding the issuer name for the tenant. Net OWIN middleware to establish a session for the user.

Thanks in advance, Ronnie Hello, A bit of history as of why this happens Windows 2000 implemented _msdcs as a subfolder of the DNS zone.

The recommended config for 20 or 2008 R2 AD-Integrated DNS zones, is that _msdcs must be moved to a separate AD-integrated primary zone as _msdcs. However, the zones created in 2000 do not changed to this config when DNS is either upgraded or migrated 2003 or 2008/R2.

Hi all, I've three DNS servers in two locations and all are running Microsoft Windows Server 2008 R2.

All three servers have the following error: Issue: The Active Directory integrated DNS zone _msdcs.domainname.local was not found.

Search for validating the state of active directory:

validating the state of active directory-76validating the state of active directory-73validating the state of active directory-36validating the state of active directory-55

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “validating the state of active directory”

  1. For some maybe it is, but on, I think it’s worth to give it a shot. At least with you do not have to get dressed, you just need to create a kick ass profile and upload attractive photos, and voila, you’re ready for meeting people.