Link to home
Start Free TrialLog in
Avatar of Se Lai
Se Lai

asked on

Outlook Cannot Log On

Migrating MS Exchange 2010 to 2016

Installed and created a new mailbox on 2016 and i was able to configure new created mailbox on outlook 2016,
now i changed all virtual directories(Addresses) and configured receive connectors, exchange 2016 mailbox is working normally with internal and external users(receiving emails, sent connector is not yet configured) but now by configuring these mailboxes on outlook giving me a warring or error, please check the attached file:

Note: DNS is not yet modified all traffic are still pointing to exchange 2010 not 2016 but even i am not able to connect mailbox with exchange 2016 name as well.

Mail Exchanger (MX) is also not yet configured

Both Mailboxes are located on exchange 2016

Regards
outlook_Exchange2016.JPG
Avatar of Edward Pamias
Edward Pamias
Flag of United States of America image

I am not an expert in exchange, but don't you think all the things you mentioned need to be fixed first prior to connecting to the server?
Avatar of Se Lai
Se Lai

ASKER

Edward, for web-mail or active-sync we need to configure but it should worked with server name at least in outlook.

Joan, thank you for the input, relay is already configured and as i said it is working fine with receiving....

i configured outlook it works fine and asking me to reboot when i reboot it giving me that message and not allowing me to load the profile.
Did you try a new local profile and see if that works for you? After you logon try setting up outlook again.
Avatar of Se Lai

ASKER

Yes, i tried with a completely new profile.
ASKER CERTIFIED SOLUTION
Avatar of Se Lai
Se Lai

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am glad you figured this one out. I saved this for future reference.
Avatar of Se Lai

ASKER

Solved by changing MAPI internal URL, As i am in co-existing environment so the DNS name (mail.orgazaion.com) was not forwarding traffic to new exchange server.