Solved

Exchange 2013

Posted on 2014-03-31
5
271 Views
Last Modified: 2014-04-03
when I setup out look on our new exchange 2013 server the server name comes across as "7286480f-e34b-4814-887c-92f0860ddebe@mymail.com"

We moved over from exchange 2007 but i was a new server not an upgrade and we have not yet downgraded the old server.

Also in order to get outlook to connect we have to put in the old servers name that it grabs the new servers name but then saves it as "7286480f-e34b-4814-887c-92f0860ddebe@mymail.com"
0
Comment
Question by:AltaPac
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39967031
That is the correct behaviour on Exchange 2013.
Each user has a unique end point.

You need to get Autodiscover to work, rather than trying to configure the clients manually. Autodiscover isn't really an optional feature - you could get away without it on Exchange 2007, but on 2013 you need it to work.

Have you attempted to use Autodiscover rather than manual configuration?

Simon.
0
 

Author Comment

by:AltaPac
ID: 39967069
Yes AutoDiscover is not working
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39967083
In what way?

The most common reason for Autodiscover not working is SSL certificates, and then DNS resolution issues.

Internally, the clients will query the value of

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

The host name listed must
a. Resolve to the Exchange server INTERNALLY.
b. Be listed on the SSL certificate

The SSL certificate must also be trusted.

If any of those fail, then that will cause you problems. As you are migrating, the value on both servers can be the same and point to Exchange 2013.

Simon.
0
 

Author Comment

by:AltaPac
ID: 39967092
Okay I am in the middle of getting a cert from godaddy for the server so maybe this will fix our issues.
0
 
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 500 total points
ID: 39967159
Make sure that you configure the host names and the DNS records correctly, because you cannot use the internal server name on the SSL certificate.

Simon.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Large Outlook files lead to various unwanted errors and corruption issues. Furthermore, large outlook files can also make Outlook take longer to start-up, search, navigate, and shut-down. So, In this article, i will discuss a method to make your Out…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question