?
Solved

Exchange 2013 after migration my mail settings have changed to a hex address @domain

Posted on 2014-12-11
4
Medium Priority
?
367 Views
Last Modified: 2014-12-11
I happened to go into my mail settings working on another problem after migrating my mailbox over to the new exchange 2013 server and my server name has changed from name.domain.org to hexadecimalnumber@domain.org

If I attempt to change it to the real server name it does not see my mailbox!!!

What is going on?
0
Comment
Question by:dpcsit
[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
  • 2
  • 2
4 Comments
 
LVL 4

Accepted Solution

by:
themightydude earned 2000 total points
ID: 40494316
That's the way it works with Exchange 2013 now.

Instead of connecting to a server per say the mail server portion is the GUID of your mailbox on the server followed by the @domain.

This site briefly covers that:
https://knowledge.zomers.eu/exchange/Pages/What-are-the-strange-server-guids-in-Exchange-2013.aspx


Excerpt from Microsoft:
Second, Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP address. This simple change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013.

http://technet.microsoft.com/library/jj150540(EXCHG.150)#BKMK_Arch
0
 
LVL 1

Author Comment

by:dpcsit
ID: 40494319
So when I setup a New user in Outlook on Windows 7 how will I know what to use for server name?
0
 
LVL 4

Expert Comment

by:themightydude
ID: 40494325
Well you shouldn't really have to put in a server name as auto discover should do that for you.

However, if you put in the FQDN of your exchange server it should convert the FQDN to what you see above.
0
 
LVL 1

Author Closing Comment

by:dpcsit
ID: 40494365
Great info!
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create an Accepted Domain 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 >> Ac…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

764 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