Exchange Server 2013 auto discover problem
We have recently migrated our mail server to a new machine and are currently running Exchange 2013 on SBS 2012.
We are running Outlook 2010 with Windows 7 Pro on the clients.
Problem: - A user logs onto a PC that they have previously not used or if a new authenticated user logs onto the network. They launch Outlook and the auto discover startup procedure begins and auto fills the username and email address. When pressing "next" it then states that Outlook Exchange is not connected or is unavailable.
When I try manually creating the account I get the same response but weirdly the server name pre-fills with a whole long string of numbers and the username pre-filled field appears something like this "=SMTP-user.name@domain
Any ideas?
We are running Outlook 2010 with Windows 7 Pro on the clients.
Problem: - A user logs onto a PC that they have previously not used or if a new authenticated user logs onto the network. They launch Outlook and the auto discover startup procedure begins and auto fills the username and email address. When pressing "next" it then states that Outlook Exchange is not connected or is unavailable.
When I try manually creating the account I get the same response but weirdly the server name pre-fills with a whole long string of numbers and the username pre-filled field appears something like this "=SMTP-user.name@domain
Any ideas?
ASKER
It was an external I.T. company that installed this for us and the technician is also struggling to fix the issue.
Apologies, we are running Windows Server 2012 Standard.
The problem only occurs with machines recently added to the domain.
Apologies, we are running Windows Server 2012 Standard.
The problem only occurs with machines recently added to the domain.
Exactly which version of Exchange 2013 is installed? Is it RTM, CU1 or CU2?
Is the old server still in production? How was the migration done?
You have said it only occurs to machines recently added to the domain - do you mean that if you take a user who doesn't work and put them on to another machine it works correctly?
Anything different between the two machines? Different OS, patch level, Office version etc?
Simon.
Is the old server still in production? How was the migration done?
You have said it only occurs to machines recently added to the domain - do you mean that if you take a user who doesn't work and put them on to another machine it works correctly?
Anything different between the two machines? Different OS, patch level, Office version etc?
Simon.
ASKER
We have Exchange Server 2013 CU2. The old server has been decommissioned as the hard drives had degraded and one failed. Hence the migration was done as an emergency with the old Exchange database (2010) being recovered and then migrated into Exchange 2013 on the new server.
If I add a new user to my Outlook, it works fine. I have brought a new machine onto the domain (exactly same OS spec, Office e.t.c.) and I have tried 3 different users on the machine, all of which suffered this particular problem.
I am going to disjoin the machine from the domain, deleted the AD entry for the workstation and then rejoin it to see if that makes a difference.
Will keep you updated.
If I add a new user to my Outlook, it works fine. I have brought a new machine onto the domain (exactly same OS spec, Office e.t.c.) and I have tried 3 different users on the machine, all of which suffered this particular problem.
I am going to disjoin the machine from the domain, deleted the AD entry for the workstation and then rejoin it to see if that makes a difference.
Will keep you updated.
ASKER
I can't get my head around this problem. Having added some more new PC's to the domain, each one presents us with this same issue. See attached screenshots:-
screenshot1.jpg
screenshot2.jpg
screenshot1.jpg
screenshot2.jpg
What you are seeing is what tends to happen when Autodiscover isn't working correctly.
On the Exchange 2013 server, run this command:
get-clientaccessserver | select identity, AutodiscoverServiceInterna
Ensure that the host name mentioned
a. resolves to Exchange.
b. is listed in the SSL certificate
You need to be using a trusted SSL certificate.
If you have non-domain clients on the network, then you will need to have autodiscover.example.com resolve to the Exchange server via a split DNS system.
Simon.
On the Exchange 2013 server, run this command:
get-clientaccessserver | select identity, AutodiscoverServiceInterna
Ensure that the host name mentioned
a. resolves to Exchange.
b. is listed in the SSL certificate
You need to be using a trusted SSL certificate.
If you have non-domain clients on the network, then you will need to have autodiscover.example.com resolve to the Exchange server via a split DNS system.
Simon.
ASKER
Our server is called Exserv. As far as I am aware we have a trusted SSL certificate installed.
Here's the results of the command.
Identity AutoDiscoverServiceInterna
-------- --------------------------
EXSERV https://exserv.noeas.local/Autodiscover/Autodiscover.xml
Here's the results of the command.
Identity AutoDiscoverServiceInterna
-------- --------------------------
EXSERV https://exserv.noeas.local/Autodiscover/Autodiscover.xml
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Simon, This issue is more prevalent with newly installed machines on the domain. For example, I can add a users email account into my Outlook with a problem. Yet, when I go to one of the newly installed PC's and log on as that same user, Outlook will not connect.
The problem has to be relevant to the machine?
It didn't happen prior to installing the new server and Exchange 2013.
The problem has to be relevant to the machine?
It didn't happen prior to installing the new server and Exchange 2013.
Patch difference with the new machines perhaps? Something different with the configuration?
Simon.
Simon.
ASKER
Solved the issue. It was the security certificates. We installed Windows 8 on some PCs and Office 2013. On launching Outlook 2013 it asked for the installation of some certificates (which we installed on the local machine) and after this procedure, Outlook worked for all users.
There is an SBS Essentials, but installing Exchange on to that product isn't supported.
With Exchange 2013, the server name is unique for every user, so that is correct. However what isn't correct is the SMTP bit. That could be an indication of permissions issue.
Simon.