After the default installation completes ADFS, AD FS R2 and 2016 has the Ldpinitiatedsignon.aspx page,
Address: https://sts.focuswincloud.cn/adfs/ls/idpinitiatedsignon.aspx
But it's normal in Windows Server R2.
Windows Server 2016 opens an error by default:
Usually after building an AD Fs/wap farm I test locally from the Internet and the Intranet using (to-date) a fairly Reliab Le Source of verification the service is up and running. I ' m referring to, of course, the IdP sign-in page (.. /adfs/ls/idpinitiatedsignon.aspx). This offers a simple to validating login via AD FS.
With Windows Server, this page is no longer surfaced "Out-of-the-box". If you want to does a SAML 2.0 idp-initiated sign-on, this functionality would need to be enabled. Otherwise, connecting to the obligatory sign-in page, would produce an error similar to the following:
Testing from the WEB application Proxy itself directly, pointing to the AD FS Farm, we'll see a HTTP 503 Service not Av Ailable error.
Via Powershell, it can switched back on:
Set-adfsproperties-enableidpinitiatedsignon $True
Windows Server AD FS Test Login Interface Configuration Error