Outlook 2010, Outlook 2007 - Exchange 2013

I am getting mixed results on trying to get Exchange 2013 connected to clients.

I have 1 x Outlook 2007 client connected to Exchange 2013
I have 1 x Outlook 2013 client connected to Exchange 2013

but I have about 25 2007 clients and 1 other 2013 client that will not connect despite checking and rechecking all settings.

Anyone got any suggestions?

November 14th, 2013 1:35pm

No obvious suggestions for the 2013 client, but for the 2007 clients have you checked that they have Service Pack 3 with the Outlook 2007 November 2012 update installed on them as that's required for use with Exchange 2013? See the Supported Clients section of http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx for details of all compatible clients and the link to the November update.
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2013 3:37pm

Thanks for reply.

Yes checked all of those.

I am at a total loss and would appreciate the help of anyone that can help me work through this.
Totally stumped at the moment.

November 14th, 2013 5:57pm

Hi,

Please have a test to log on a problematic users profile on a good machine. Does it work?

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Free Windows Admin Tool Kit Click here and download it now
November 18th, 2013 3:03am

I appear to have resolved it.
I created a self signed cert and ensured that the server name being requested was inside the cert.  

Then I logged on as the user and i imported the certificate in the trusted CA
BUT and its a BIG BUT
when I checked the CA area I could not see it.
After much research I found that when I was logged on as a roaming user that the certificate did not go into the CA.
I had to log on as a domain admin and then import the certificate by going running MMC adding the certificate snap in and then importing the certificate.  
It then showed up and I was able to log back in as the user and complete the outlook setup making sure to utilise the RPC over HTTP in security and using NTLM.

Looking back, I also found a MS article http://support.microsoft.com/kb/2264398#appliesto
that refers to a similar missing registry key causing a similar problem to that lots of others have reported but this looks to be relevant only to LOCAL profiles and not roaming profiles and when I navigated to the key it showed 'Roaming'.

Hope this helps someone.  
I am on a mission to help others now as this has sucked so much of my time.
  • Marked as answer by MrNewbie 3 hours 51 minutes ago
November 18th, 2013 3:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics