Netherlands: Software

Introductie Windows Server 2016

Issue link: http://hub-nl.insight.com/i/692748

Contents of this Issue

Navigation

Page 110 of 173

102 C H A P T E R 4 | Networking Figure 4-27: Viewing Details from the Best Practices Analyzer The table on TechNet offers the following suggestion for event 12021: Make sure that the certificate thumbprints that are configured for Web Application Proxy applications are installed on all the Web Application Proxy machines with a private key in the local computer store. Armed with this information, you can review the certificates on the Web Application Proxy server to ensure that they have the correct names and expiration dates, and that the thumbprint matches the one on the server. Then, you can review the certificates on the server, ensure that they are correct, and reissue them if they are incorrect. Certificate issues Certificates play an important role in AD FS and Web Application Proxy. Getting the proper certificates, with the correct names in the certificates on the appropriate machines, is therefore critical to getting Web Application Proxy to function correctly with AD FS. You might see issues with certificates manifested in error messages like the following: The trust certificate ("ADFS ProxyTrust – WAP01") is not valid. There are several possible causes of this issue: There might be some sort of network interruption between the Web Application Proxy server and the AD FS server. The Web Application Proxy server might have been down for an extended period of time. There might be an issue validating the certificate due to problems in the CA infrastructure. Time synchronization issues between the Web Application Proxy and AD FS servers might cause them to be out of synchronization. To resolve these problems, verify the time settings on the Web Application Proxy and AD FS servers and rerun the Install-WebApplicationProxy cmdlets. Configuration data in AD FS is inconsistent or corrupt You might also encounter errors for which the configuration data in AD FS could not be found or the data is unusable to the Web Application Proxy server. This can result in errors such as Configuration data was not found in AD FS. or The configuration data stored in AD FS is corrupted or Web Application Proxy was unable to parse it. or: Web Application Proxy was unable to retrieve the list of Relying Parties from AD FS. Several things can cause these errors. It's possible that Web Application Proxy was never fully installed and configured, or there were changes that occurred on the AD FS database that resulted in

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016