Outlook 2010 clients can't connect to Exchange 2010 server during initial Outlook profile setup

Outlook 2010 clients can't connect to Exchange 2010 server during initial Outlook profile setup.

I run the Outlook 2010 profile setup wizard and the Outlook 2010 clients are unable to connect to the Exchange 2010 Service Pack 2 server using auto configuration.

I have checked and the operating systems that contain Outlook 2010 are able to ping the Server 2008 R2 server that is running Exchange 2010.

The Server 2008 R2 Hyper-V guest server running Exchange 2010 is also able to ping the client operating systems that are running Outlook 2010.

Furthermore, all client computers and servers are members of the same Server 2008 R2 Active Directory domain.

What needs to be done to fix this issue so that the Outlook 2010 computers will be able to connect to the Exchange 2010 server and perform the initial setup?
KnowledgeableNetwork EngineerAsked:
Who is Participating?
 
NavdeepConnect With a Mentor Commented:
Hi,

are you able to configure Outlook 2010 manually?

Kindly check if autodiscover is working and configured appropriately?
Does email field and upn suffix same?

Regards,
Navdeep [v-2nas]
ExchangeADTech
0
 
KnowledgeableNetwork EngineerAuthor Commented:
No I am not able to configure Outlook 2010 manually. I have already tried doing that.

How do I check to see if auto discover is working and configured appropriately on the Exchange server and that the email field and UPN have the same suffix name?

Please provide me with the exact steps.

I am still learning Exchange 2010.
0
 
KnowledgeableNetwork EngineerAuthor Commented:
Also, do I need to check any settings in the Exchange server 2010 receive connector?

Please provide me with the exact steps on what I need to check.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
KnowledgeableNetwork EngineerAuthor Commented:
Also, I have Outlook 2010 installed on my Hyper-V base server. I then have Exchange 2010 installed on two Hyper-V virtual Server 2008 R2 operating systems.

Both of these Hyper-V virtual operating systems have Exchange 2010 standard installed.

I have installed all of the updates on my Hyper-V base server and on the Hyper-V virtual operating systems, including Exchange 2010 Service Pack 2, and Exchange 2010 Service Pack 2 Rollup 4.
0
 
KnowledgeableNetwork EngineerAuthor Commented:
Here is a screenshot of the exact error message that I receive "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. OUtlook must be online or connected to complete this action."
Connection-to-Microsoft-Exchange.png
0
 
FdpxAP-GJLConnect With a Mentor Commented:
Hi,

You might find the following helpful

Website for testing exchange
https://www.testexchangeconnectivity.com/

Commandlet for testing autodiscover
http://technet.microsoft.com/en-us/library/bb123573.aspx
http://technet.microsoft.com/en-us/library/cc539050.aspx

manage Autodiscover
http://technet.microsoft.com/en-us/library/aa995956.aspx

Regards

Gordon
0
 
KnowledgeableNetwork EngineerAuthor Commented:
Thank you to everyone for your help.<br /><br />I resolved this issue after I discovered that the Microsoft Exchange Address Book service on the two Exchange servers wasn't started (even though the startup type was set to automatic).<br /><br />As soon as I started this service, Outlook 2010 on all client computers were immediately able to fully resolve to the Exchange servers and set themselves up.
0
All Courses

From novice to tech pro — start learning today.