Avatar of BSModlin
BSModlin
Flag for United States of America asked on

Exchange 2007 to 2013 Co-Existence Issues

I am in the middle of migrating from 2007 to 2013.  Both servers are up and running.  I have mail flowing between them successfully, as well as out to the internet.  I have moved a few users from 2007 to 2013.  My question is once I moved the user mailbox the server name in Outlook changes to a weird name (not the new server name as I would expect).  It prompts for Outlook to close and then re-open.... and then asks for credentials..... and then connects.  When I go to the server settings I see the server name changed, but it looks like a crazy Hex thing....

What is that?  and will it change again once I remove the old exchange server from the Org?  Why prompting for credentials?
ExchangeEmail ServersOutlook

Avatar of undefined
Last Comment
it_saige

8/22/2022 - Mon
BSModlin

ASKER
Here is a screenshot... The new exchange server name is exchange.abc.comOutlook
it_saige

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.
Source
This will not change when the Exchange 2007 server is taken offline.  As for prompting for credentials, this is most likely happening because of a discrepancy with the authentication methods.

-saige-
BSModlin

ASKER
Ok, so how will my SSL certificate successfully authenticate the internal Outlook users if Outlook is configured to this "connection point" rather than the name?
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
it_saige

SSL is not responsible for client authentication.
The Client Access server in Exchange 2013 functions much like a front door, admitting all client requests and routing them to the correct active Mailbox database. The Client Access server provides network security functionality such as Secure Sockets Layer (SSL) and client authentication, and manages client connections through redirection and proxy functionality. The Client Access server authenticates client connections and, in most cases, will proxy a request to the Mailbox server that houses the currently active copy of the database that contains the user's mailbox. In some cases, the Client Access server might redirect the request to a more suitable Client Access server, either in a different location or running a more recent version of Exchange Server.
Source

With regards to Exchange 2013 and prompting for credentials.  You might check here for helpful tips.

http://ilantz.com/2013/06/29/exchange-2013-outlook-anywhere-considerations/

-saige-
it_saige

Secure Sockets Layer (SSL) is a method for securing communications between a client and a server. For Exchange Server 2013, SSL is used to help secure communications between the server and clients. Clients include mobile phones, computers inside an organization's network, and computers outside an organization's network.
Source

-saige-
BSModlin

ASKER
I'm sorry for asking, but with the above copy/paste... what does that mean for me... I am still kinda confused....
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
it_saige

Not a problem.  What are you confused about?

-saige-
BSModlin

ASKER
I have a valid GoDaddy cert installed and changed all of the virtual directories to match the external URLs... I am also using split brain DNS and have the external name of the server and the autodiscover A records pointing to the exchange server.  OWA is configured and accepts the SSL certificate as expected.... Currently when I launch Outlook on a mailbox that has been migrated it is prompting to authenticate with the 2007 server SSL.... then it asks for credentials... and then it connects..... why is that?
SOLUTION
it_saige

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
BSModlin

ASKER
Windows 7 Pro 64 bit and Outlook 2013
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
it_saige

Also, on the client run outlook /rpcdiag.  When it prompts for the username and password see if the mail has an established connection but the Public Folders types has a disconnected status.

Example RPCDIAG output:Capture.JPG
-saige-
ASKER CERTIFIED SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
BSModlin

ASKER
One more question.... Can I migrate mailboxes during production..... While users are using their Outlook? What will happen during, and after the mailbox moves?
Gareth Gudger

That's a good question. I think it was only Exchange 2010 and newer that allowed you to do live migrations. I think if the source is 2007 it will take the mailbox offline during the move. Could be wrong. Memory is failing me. Let's see what other experts say.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
it_saige

Your memory serves you well Gareth.  ;)

http://blogs.technet.com/b/exchange/archive/2010/07/19/3410438.aspx

http://blogs.technet.com/b/schadinio/archive/2010/07/20/exchange-moving-mailboxes-exchange-2007-vs-exchange-2010.aspx

Online Mailbox Moves were possible starting with Exchange 2010.  This is when the Mailbox Replication Service was introduced.

-saige-