Hi! MS Outlook is showing numbers on the Server Name Box instead of the correct server name. Exchange 2013 installed on Windows 2012. Any Suggestions? Thanks.

Hi This is how it should be, the numbers are the Mailbox GUID which is how Outlook locates your mailbox. Is it failing to connect? This is normally down to the need for a proper certificate on the server rather than using the self-signed one. You can use a certificate from your internal CA if you don't have a public one. Cheers, Steve

I have already purchased the certificate from Godaddy and activated. I am able to connect from outside but with manually entering proxy. Autodiscover is not working. Any suggestions? Thanks.

Do you have autodiscover.yourdomain.com as a name on the certificate and does the SCP use this name? Get-ClientAccessServer | select Name,AutoDiscoverServiceInternalUri Do you have internal and public DNS records for this name that point to your servers internal and public IP address? Steve

yes I have the records but I just noticed one thing and the external uris were not configured for owa, ews and autodiscover. Now I have configured them. When I entered the autodiscover internal uri in Explorer I got the below error after entering my credentials. One more thing I did not restart any service after entering the external uris.

Did you leave the .xml off the end of that URL? If you are getting unexpected responses when connecting to Exchange 2013 (all connections are over port 443) running an IISReset could be useful.

With .xml Secondly, should entering Get-ClientAccessServer | select Name,AutoDiscoverServiceExternalUri show the External URI for Autodiscover. When I enter it is not showing anything under External URI even after resetting IIS.

The 600 response means that it is working correctly. The ExternalURL should be blank as Autodiscover only uses DNS lookups when Outlook is not internal or domain joined.

Well if it is working then I don't know why I am getting the below error while connecting from outside. The Certificate is there as well. OWA is working fine.

after pressing ok I got this:

Run a ExRCA test and see what errors that comes back with: https://www.testexchangeconnectivity.com/ BTW: your domain name is visible in the last screenshot.

Yes thanks. Ran the tests and it says the below only for certificate but still cannot connect automatically from outside: Connectivity Test Successful with Warnings Analyzing the certificate chains for compatibility problems with versions of Windows. Potential compatibility problems were identified with some versions of Windows. Additional Details ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Was that just the autodiscover test or the Outlook Anywhere one? If it was just autodiscover can you run the OA test and see what the result is.

Well not working. It is trying to resolve my internal exchange server name. Is it required and should I ask my ISP to add this in the DNS?

You can set the External hostname for OA that Autodiscover uses either in the EAC or using this command: set-OutlookAnywhere ServerName -ExternalHostname mail.yourdomain.com

The operation couldn't be performed because object 'exserver.domain.com\ServerName' couldn't be found on 'dc.domain.com'. + CategoryInfo : NotSpecified: (:) [Set-OutlookAnywhere], ManagementObjectNotFoundException + FullyQualifiedErrorId : 159DEA6B,Microsoft.Exchange.Management.SystemConfigurationTasks.SetRpcHttp + PSComputerName : exserver.domain.com Got this error.

Here you go - "The host name could not be resolved" It means you need to carefully examine your external DNS zone for what is set up for the A (and MX) records there. Those records names should match your virtual directory names you set up in EAC. Use the guide http://technet.microsoft.com/en-us/library/jj218640.aspx in "Step 5: Configure external URLs" to check your organization settings and names. Vote if Helpful :) | MaximumExchange.ru

OK I am checking but I cannot understand one thing that why outlook is changing the servername to a number after configuring it. Is it normal? I have not seen this with Exchange 2003, 2007 and 2010. This exchange was reinstalled with the same name and connected to the same domain controller where it was connected before reinstallation. Thanks.

This is part of the changes introduced to Exchange 2013 - on of the benefits is you will not receive the "Your administrator has made changes to your mailbox" message in Outlook after you move a mailbox.

This is Autodiscover leads your outlook a wrong way, because you have some inconsistency with DNS names and virtual directories. Doublecheck it. Vote if Helpful :) | MaximumExchange.ru

Opening nslookup is showing unknown under server name in exchange and dc as well. I have doubt that there are still traces for old exchange server in my dc because when I opened properties for exchange server computer account it is showing some accounts with their SIDS and not names. How can I clean my dc from these traces? Secondly, what are the records required other than mx record that my ISP should create? Thanks.

You should be able to edit your external DNS zone, and have there at least A and MX records, for example: Contoso.com MX Mail.contoso.com Mail.contoso.com A 172.16.10.11 Owa.contoso.com A 172.16.10.11 Autodiscover.contoso.com A 172.16.10.11 see "Step 5: Configure external URLs" 2. Your Exchange computer account should be member of the following groups: Domain Computers, Exchange Install Domain Servers, Exchange Servers, and Exchange Trusted Subsystem. Is that your test lab? Vote if Helpful :) | MaximumExchange.ru

No this is not a test lab. This is a new online production server. Users are connected to this but they cannot connect using autodiscover and Mobile Devices are also not working. I was able to connect to the server from my Andriod Device using the Public IP instead of DNS Name but now it is also not working. Thanks.

The problem has been solved. There was no external URI in Outlook Anywhere. After adding mail.domain.com through ECP autodiscover started working. Thanks to everybody helped in this.

after pressing ok I got this:

You can set the External hostname for OA that Autodiscover uses either in the EAC or using this command: set-OutlookAnywhere ServerName -ExternalHostname mail.yourdomain.com

The problem has been solved. There was no external URI in Outlook Anywhere. After adding mail.domain.com through ECP autodiscover started working. Thanks to everybody helped in this.