Solved

Exchange 2013

Posted on 2014-03-31
5
274 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

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
To show how to create a transport rule 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 >> Rules tab.:  To cr…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

628 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