• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 281
  • Last Modified:

Exchange 2013

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
AltaPac
Asked:
AltaPac
  • 3
  • 2
2 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
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
 
AltaPacAuthor Commented:
Yes AutoDiscover is not working
0
 
Simon Butler (Sembee)ConsultantCommented:
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
 
AltaPacAuthor Commented:
Okay I am in the middle of getting a cert from godaddy for the server so maybe this will fix our issues.
0
 
Simon Butler (Sembee)ConsultantCommented:
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now