i have made a migration from exchange 2010 to 2013 and every thing goes well till i reached to moving mailboxes, it moved mailboxes successfully but when the operation completed i checked the account settings and i found the server address as in attachment file (Name)
but the connectivity between the outlook and the new exchange 2013 is OK and it send and receive well.
And when i try to add the account from control panel/mail manually i got error in file (Connectivity)
the exchange 2010 v 14.03.0361.001, exchange 2013 Version 15.0 (Build 1347.2)
Is there a problem with my configuration or any connectivity problem between the active directory server and the new exchange 2013 server 1.JPG 2.JPG
ExchangeOutlookActive Directory
Last Comment
Rami Alhasani
8/22/2022 - Mon
M A
Hi Rami,
Where is your autodiscover pointing to?
Both common name and autodiscover should be pointed to Exchange2013.
Please ensure all services are started.
Thanks
MAS
Rami Alhasani
ASKER
i think its correct my new exchange server 2013 is 128.127.0.21, but i think that their a connectivity problem with DC but i don't know how to fix it.
Hemil Aquino
For what I can see your records looks OK.
Try restarting the Exchange topology services.
my users can login with normal setup of mailbox on outlook that uses the Autodiscover, but the error appears when setup the account in outlook manually by typing the name of exchange server and mailbox.
for the Questions:
1. can you logon to OWA to confirm the mailbox is assessable? i can login to OWA without any problem.
i wonder do your certificate have autodiscover as CNAME? how i can check that?
also we need to run the test command in exchange server
$TestCredentials = Get-Credential # this is the user's credential Test-OutlookConnectivity -ProbeIdentity OutlookRpcCtpProbe -MailboxId johnd@contoso.com -Credential $TestCredentials
but i noticed a weird thing that when i configure a mailbox that are existing on the new exchange 2013 server manually on outlook and type the old exchange server name its resolves the name of the new exchange 2013 server correctly
and do i need to delete default exchange 2013 certificates after importing my certificate from exchange 2010 to exchange 2013
in the new world, you are not "suppose" to type in the servername, it should pick up by autodiscover
i know that, but i do it manually to test the connectivity, even with autodiscover it gave me below error, and when complete define mailbox in outlook, the server name is incorrect in the (account settings/server settings) to check on cname
open the certificate and confirm Subject Alternative Name When you next create an outlook profile, can you untick the "cached mode"? and see whether the same message reappear?
so first, your certificate does not have autodiscover alternative name. you need to regenerate a certificate to get that working.
what do you mean by "autodiscover alternative name", and how i can regenerate my certificate?
For clarification, when i was using the old exchange 2010 i was not facing any problems about server name, the only thing i was facing is the certificate message when the user opens the outlook only: So let's go back to your ORIGINAL ISSUE, do you still have this error message every time?
no i get this error message only when i setup the mailbox manually and you clarified to me now that i cant do it manually, and when i setup via autodiscover i did not get any errors and every thing goes well, it connects perfect and i can send and receive emails but the only problem is that the server name problem Which I mentioned earlier:
and some users outlook keep asking them for authentication (user name and password)
Hi Jian An Lim
thanks for your support and sorry for late respond,
i created the request but when i complete the request and use the same valid certificate i got below error:
and when i'm trying to delete the current valid certificate i got below error:
and i'm insist for manual addition of email because some users opens two mailboxes on their outlook, the first one was added with autodiscover and the other one manual addition,
anyway am now adding it by giving the user mailbox full access "Mailbox Delegation" on the other mailbox, but in the same subject i'm in stage of Decommissioning Exchange 2010 but before that i shut down the exchange 2010 to make sure that every thing is OK and after testing everything is OK except that the delegated mailbox when i the cursor on its inbox or other folders it gave trying to connect for long time then connected and it gave that every time that i close outlook and reopen it, but when i turned on the exchange 2010 again this mailbox gave connected directly.
My certificate is from rapidssl.com, do you mean that i have to request a new certificate from them and pay again for it, even though may certificate still valid, i dont know if i can manage my certificate from that site.
I successfully imported the new certificate to the exchange server, and to test if the problem solved i shut down the old exchange 2010 server, but unfortunately the same problems appears and also new problems appears also, the problems is that outlook users on windows XP are disconnected and they get certificate error like below:
so i install the certificate on the users computer certificate store but that did not fix the problem
also outlook users on windows 7 are suffering from delay when open the outlook every time like below:
this message " updating this folder" is appears every time that user closes and reopen the outlook and it Cause of delaying messages
i think my problem is too complicated so i need an urgent help PLZ :)
i forgot to mention that they sent me also an intermediate certificate and i installed it correctly to exchange server 2013 certificates store as they instructed me,
does that changing any thing here?
Ok but should i install the root certificate under the "intermediate certification authorities" store in in the exchange 2013 server certificate store or under "personal" store?
i installed the root certificate on the exchange 2013 server but with no luck, but when i install the intermediate and root certificate on the outlook user computer (that has XP installed on it) its connected now but the delay problem still there, when you open the outlook it takes long time to get the data from the server (that's when the exchange 2010 is turned off),
but when i turn on the exchange 2010 server the delay problem disappears !!
The reason why I'm turning off exchange 2010 is to test connectivity for the new exchange 2013 before Decommissioning of exchange 2010, that was the recommendation of the article that i was processed step by step from techgenix.com site
do you mean that when i safely decommission the exchange 2010, my delay problem will be solved?
regarding to public folder i should told that my public folder on my old exchange 2010 server is corrupted and i cannot dismounted from a long time but it was not making any problems when i was using only the exchange 2010, i don't know now if it is making problems after migration or not or it will make a problems with Decommissioning i should ask you?
or should i make a new public folder on the exchange 2013 (i don't need it in my environment).
but i prefer to continue in this post because it has full details about my problem and i don't want to start from zero and my primary issue was connectivity delay in outlook after migration from exchange 2010 to exchange 2013,and we are a step away from solving the problem, and i will be thankfull for you support to end this issue.
Hi Rami,
I appreciate your support, but it is really streching your original question as we have exchanged almost 49 messages since.
You can always refer back to this post on your new question for history purpose but rest assure, whatever you done here have nothing to do with how you going to decomission your exchange 2010.
It is just good to get a closure by accepting the answer.
and onceyou post your question, i will look into it and give other expert a chance to look into this.
Rami Alhasani
ASKER
Ok thanks i have published a new post and i hope we can reach to an appropriate solution to my problem
Where is your autodiscover pointing to?
Both common name and autodiscover should be pointed to Exchange2013.
Please ensure all services are started.
Thanks
MAS