Having a bit of a problem with my greenfield installation of Exchange Server 2013. Environment: Windows Server 2012, 4 Exchange Servers (collocated CAS/MBX roles), Outlook 2010.
HLB is arriving next week, until then I have configured DNS RR for both autodiscover.company.com and mail.company.com.
If starting outlook on a domain joined pc, autodiscover and outlook anywhere is working perfect. If starting outlook on a non-domain joined pc and enter my email address it does an autodiscover lookup using A record (autodiscover.company.com) and it resolves the guid. but I cannot logon to the server. If I do it manually I cannt enter the proxyname (mail.company.com) I have to enter a exchangeservernamefqdn, then it works.
- Certificate: 3rd party wildcard, stampled on IIS services on all servers. OWA/ECP works perfect.
- Outlook Provider: EXPR mail.company.com msstd:*.company.com
- Outlook Anywhere (RPC vDir): InternalUrl/ExternalUrl: mail.company.com (External=Negotiate, Internal = NTLM)
- Exchange WebServices (EWS vDir): InternalUrl/ExternalUrl: https://mail.company.com/EWS/Exchange.asmx, InternalNLBBypassUrl: https://srvfqdn.company.com/EWS/Exchange.asmx (tried $null and mail.company.com as well)
- ClientAccessServer/AutodisocverServiceInternalUri: https://mail.company.com/Autodiscover/Autodiscover.xml
1) So domainjoined pc works perfekt, but not non-domain joined (never gets pass the basic screen).
2) Test-OutlookWebServices = Autodiscover: Outlook Provider failure (if using -debug I cannot see any errors).
3) How come if using netstat on a client computer I can see the connection towards the server hosting the active mailboxdatabase. Should'nt I see the proxy (mail.company.com?)
4) Shall InternalNLBBypassUrl be serverfqdn, proxy fqdn or $null? When first installed it was empty, but after a reset of ews vdir it got the serverfqdn field configured!