tbs_mnp
asked on
Exchange 2016 in 2010 environment issue
Just installed Exchange 2016 into an existing 2010 environment. Everything works great. I got the namespaces corrected on 2016 AD side and SSL cert going. Mail flow works and creating/migrating a user onto a 2016 DB or to 2010 DB works. OWA works. Autodiscover works. What I am testing now is where I am stuck.
If it log into a machine as a 2016 DB user and open outlook for the first time - outlook 2010 will only connect and function on cached mode. if I leave cached unchecked, it says Microsoft must be online, failed to authenticate. Not sure where to look.
Office is updated
Services and Server have been rebooted (all services are started)
If it log into a machine as a 2016 DB user and open outlook for the first time - outlook 2010 will only connect and function on cached mode. if I leave cached unchecked, it says Microsoft must be online, failed to authenticate. Not sure where to look.
Office is updated
Services and Server have been rebooted (all services are started)
Hi,
are those DNS records for autodiscover and owa (mail, webmail or how you call it) pointing to Exchange 2016?
Regards,
Ivan.
are those DNS records for autodiscover and owa (mail, webmail or how you call it) pointing to Exchange 2016?
Regards,
Ivan.
ASKER
Andy, yes.
Ivan. no. autodiscover and owa DNS point to my "master" 2010 server. (also, I am not intending on changing that anytime soon either, going to be a lot of time before I get rid of 2010)
Ivan. no. autodiscover and owa DNS point to my "master" 2010 server. (also, I am not intending on changing that anytime soon either, going to be a lot of time before I get rid of 2010)
ASKER
Where I changed autodiscover was in the AD site setting for this exchange 2010 server. changed the internal site name from the FQDN of the server to the correct entry that we use internally which would be autodiscover DNS entry which like I said about is defined and pointing to 2010.
ASKER
Also, outlook does act like it verifys/checks and finds the correct server and username. its when it tries making connection to the server it fails.... however if I make this outlook cached mode, everything works perfectly fine.
Hi,
well procedure for Exchange 2010-2016 coexistence is to point everything to 2016, since it can then proxy/ redirect to 2010.
Other way around is not possible.
Regards,
Ivan.
well procedure for Exchange 2010-2016 coexistence is to point everything to 2016, since it can then proxy/ redirect to 2010.
Other way around is not possible.
Regards,
Ivan.
Have you tried to configured new outlook profile for the migrated user? If not, try and let us know.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok ivan. I did not see this in things ive read. what exactly do I need to point to 2016?
Ill prolly have to come in on a weekend to test you think? I don't want to blow up anything with clients.
Shreedhar, yes I have tried.
Ill prolly have to come in on a weekend to test you think? I don't want to blow up anything with clients.
Shreedhar, yes I have tried.
ASKER
ok let me try that out ivan ill let you know.
Did you test your env with https://testconnectivity.microsoft.com/ ?
ASKER
ivan that did it. ill ready to make changes live across the board on my network in a maintenance weekend coming up. changing autodiscover and my mail. dns internal record to point to 2016 worked.
KB2956191 and KB2965295