Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Testing RPC/HTTP connectivity. The RPC/HTTP test completed successfully. Test Steps Attempting to resolve the host name hostedmail.domain.tld in DNS. The host name resolved successfully. Additional Details IP addresses returned: x.x.x.x Testing TCP port 443 on hosthostedmail.domain.tld to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Validating the certificate name. The certificate name was validated successfully. Additional Details Host name hostedmail.domain.tld was found in the Certificate Subject Common name. Certificate trust is being validated. The certificate is trusted and all certificates are present in the chain. Additional Details The certificate chain has been validated up to a trusted root. Root = CN=DigiCert High Assurance EV Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 10/29/2010 12:00:00 AM, NotAfter = 11/5/2013 11:59:59 PM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Testing HTTP Authentication Methods for URL https://hostedmail.domain.tld/rpc/rpcproxy.dll. The HTTP authentication methods are correct. Additional Details ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic Testing SSL mutual authentication with the RPC proxy server. Mutual authentication was verified successfully. Additional Details Certificate common name hostedmail.domain.tld matches msstd:hostedmail.domain.tld Attempting to ping RPC proxy hostedmail.domain.tld. RPC Proxy was pinged successfully. Additional Details Completed with HTTP status 200 - OK Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server mailsrv. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 279 ms. Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server. The NSPI interface was tested successfully. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server mailsrv. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 106 ms. Testing NSPI "Check Name" for user email@example.com against server mailsrv. Check Name succeeded. Additional Details DisplayName: User Name, LegDN: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=username Testing the Referral service on the Exchange Mailbox server. The Referral service was tested successfully. Test Steps Attempting to ping RPC endpoint 6002 (Referral Interface) on server mailsrv. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 70 ms. Attempting to perform referral for user /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Username on server mailsrv. ExRCA successfully got the referral. Additional Details The server returned by the Referral service: mailsrv.windowsdomain.local Testing the Exchange Information Store on the Mailbox server. ExRCA successfully tested the Information Store. Test Steps
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
|Exchange 2013 - Database Availability Group (DAG)||2||41|
|Outlook header - Return Path different to From address||2||60|
|Outlook 2016: Office365 connection "Disconnected" - which ports or protocols to open on Proxy Appliance?||4||37|
|Exchange store - size is 60GB+ is that too big? What to do about it / maintain it? How to see size of each user's folder?||10||23|
Join the community of 500,000 technology professionals and ask your questions.