Exchange 07/10/13 co-existence and install

Hi All,  Need some advice on Ex07/10/13 co-existence + upgrade.  I have multiple EX servers in multiple locations, most running EX07, one running EX10 and I have recently installed 2 new EX servers running EX13.  

All on the same domain but in different locations, connected via private network.  I have followed the co-existence install and updates on all current EX servers and on the first EX13 server all installed OK.  AD has been prep'd and schema updated, etc.  All fine.  

With the 2nd EX13 server (which is in a different location from the first EX13 machine.) I have installed via the CU2 setup.exe and EX is installed successfully.  

However I ran into issues when trying to login to EAC on the 2nd EX13.  Everytime I tried to login as admin it would re-direct to OWA for the admin account.  The Admin mailbox is located in the first EX13 server.  And I tried all the other EAC and ECP urls, none work.

So do you need an admin account + mailbox on each EX13 machine to manage it?  Sounds a bit odd.  I would have thought I could manage all EX13 machines with the 1 admin account.  Eventually I created a new mailbox on the 2nd EX13 machine from the 1st EX13 machine, applied the EX admin permissions and then could login to EAC on the 2nd EX13 machine and manage it.  So currently I am using 1 login to manage EX13 1st machine and another admin login to manage EX13 2nd machine.  is this right?

Thinking this may not be correct I then reinstalled exchange with the prep AD and prep schema switches.  

This fails and says the server cannot contact the schema master and it needs to belong to the same site, etc.  I didn't think I had to run prepAD again as the domain has already been prep'd for EX13 and the first machine is currently up and running ok.

Currently the 2nd EX13 seems to be working ok, I have moved mailboxes between servers and got mailflow working.  

Have I installed this 2nd EX13 machine correctly though?  Thanks in advance.
LVL 6
rick81Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chinthaka_ShameeraCommented:
Are you getting any error message when you try to access ECP  ?

1.Log on to one Domain Controller then run

2.Adprep /Syncall /AdeP

3.Check the EAC

if its not working, run setup.com /prepareAd again

/EAC reside at client access server, there would not be any problem when you have one Admin account and locate that any mailbox server.
0
rick81Author Commented:
The AD is prep'd as i have checked the attributes on ADSI Edit on all the DC's and they are correct.

On EX13-server1 i login as admin in EAC=OK (the admin mailbox is located on this server)

On EX13-server2 i login as admin and EAC redirects to OWA.

If i do the opposite and login as admin2 on server1 it re-directs to OWA
If i login as admin2 on server2 (where admin2 mailbox lives) it logs in OK.

I receive no error messages with EAC.

Thanks
0
rick81Author Commented:
Some further reading there are many articles mentioning to change the url to https://servername/ecp/ or https://servername/ecp?ExchClientVer=15
Neither of these work it still redirects to OWA.  

And both my admins mailboxes are on the EX13 servers.  I can only login to the EAC of the server where the specific admin mailbox resides.

Is this still normal in co-existence.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Chinthaka_ShameeraCommented:
hello,

One thing you should understand, You don't want to login in to each server to manage. Any ECP will do the Organization wide configuration and administration.

You can use https://Servername/ecp?ExchClientVer=15 and try to log in. This known behavior in mixed environment. You should add the server version.

I have seen this behavior in my Labs and customers as well.
0
rick81Author Commented:
Hi as mentioned in previous post i have tried the different urls.  they all redirect to OWA

https://servername/ecp/ or https://servername/ecp?ExchClientVer=15

Neither of these work it still redirects to OWA.
0
Chinthaka_ShameeraCommented:
can you check IIS logs ?
it will tell you what is happening
0
rick81Author Commented:
ill have to review the logs later and will post back
0
Chinthaka_ShameeraCommented:
have you installed Exchange 2013 RTM CU2 on all servers ?
0
rick81Author Commented:
Hi, i have reviewed the IIS logs and no errors appear when ECP redirects to OWA.  This appears to be normal behaviour in co-existence.

Yes, CU2 has been installed on all EX13 servers.
0
rick81Author Commented:
to confirm both EX13 servers are running latest updates CU2v2
0
rick81Author Commented:
Eventually sorted this out.

IIS auth settings for ECP didnt have domain setting for basic auth option. Added the domain in and now works.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rick81Author Commented:
resolved myself
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.