Hi all, i've had a bit of a head scratcher for a few days!
I’ve got all the way through to having the my existing exchange 2010 cas and mailbox servers running alongside the new exchange 2013 cas and mailbox servers.
my problem seems to be somewhere in the transport or dns between the two… its very odd!
If i create a test mailbox on 2010 and open within outlook (using online mode), it still resolves fine to the old 2010 environment, even though i have now modified the DNS records to point at the new 2013 servers.
if i then migrate that mailbox, and open it within outlook, again, no problem, and when viewing the connection status you can see it connected via the new GUID format.
If i then try either creating a brand new mailbox from scratch on 2013, or deleting the existing migrated mailbox profile, and recreating manually to ensure the process, the new 2013 cas server will not resolve, but the old 2010 will.
for example typing in 2013cas.domain.local does not resolve, however if i then type in 2010cas.domain.local, it does resolve it to 2013cas.domain.local! i might also add at this point it doesnt resolve it to the cas server but the new mailbox server, but this i believe to be correct.
i cant for the life of me work out why this is. i’ve gone back through all settings again, checked all permissions, virtual directories, URLs, DNS, its got to be something simple, but i am fresh out of ideas!
There was one other thing which I cant for the life of me remember what cmdlet I ran, but it threw up an error about not finding an object or unable to create an object for the mailbox server in the directory… is there a command i can run to check this also?
Sorry for so much here, i really dont know where to turn as everything else tests perfectly!