Is it possible to install Exchange 2010 CAS role to test before it becomes proxy for Exchange 2003 mailboxes?
We're running into a lot of questions on exactly the CAS redirects traffic. Here's what I know: It becomes a proxy for all 2003 Mailboxes during coexistence with Exchange 2010/2003. External traffic is seamlessly pushed to the 2003 front-end and mailboxes FROM CAS.
How does it route internal traffic?
Also, is it possible to install CAS without it touching the 2003 environment and simply doing a DNS change to switch it over to our production environment?
How does it route internal traffic?
Also, is it possible to install CAS without it touching the 2003 environment and simply doing a DNS change to switch it over to our production environment?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@GreatVargas
This is extremely helpful as far as internal/external users is concerned.
@Akhater
I love the article and I have printed a copy for reference, but my boss needs to know if we can actually get away with installing the CAS without redirecting traffic initially or if that happens no matter what. With such a large organization, we really need to make sure we're good to go before jumping into this.
Essentially, we're scared that we are being forced to throw this into production without being able to test it first. That being said, no, we're not currently able to replicate the environment in a sandbox to test.
We'd like to install the CAS, validate the install before applying the proxy to force it to the front-end.
This is extremely helpful as far as internal/external users is concerned.
@Akhater
I love the article and I have printed a copy for reference, but my boss needs to know if we can actually get away with installing the CAS without redirecting traffic initially or if that happens no matter what. With such a large organization, we really need to make sure we're good to go before jumping into this.
Essentially, we're scared that we are being forced to throw this into production without being able to test it first. That being said, no, we're not currently able to replicate the environment in a sandbox to test.
We'd like to install the CAS, validate the install before applying the proxy to force it to the front-end.
no one will force you to put it in production
you can install your cas server and fix all the urls on it then bring in a test station and change on it the host file so it resolves the FQDNS entries to different ips than the one in the DNS and then, when all is working put it in production
you can install your cas server and fix all the urls on it then bring in a test station and change on it the host file so it resolves the FQDNS entries to different ips than the one in the DNS and then, when all is working put it in production
yes you can install the Client Access Server and still have the 2003 envoirement functioning without problems.
I advise you to start thinking on a migration and coexistence plan, since you are on a big organization i assume that you will be using all exchange features to access mailboxes (owa, activesync, rpc over http)
I advise you to start thinking on a migration and coexistence plan, since you are on a big organization i assume that you will be using all exchange features to access mailboxes (owa, activesync, rpc over http)
get one mail2.domain.com url and assign it to 2010, for test purposes. also configure on 2010 the legacyurl as it is now, for example mail.domain.com
publish a rule for owa 2010 using the mail2.domain.com name
test the access from outside using mail2.domain.com and seeing if your redirected to mail.domain.com (use 2003 mailbox and i'm assuming that you have forms based on 2003. if you dont have you cant get double authentication but test anyway)
this tests that i recomended wont affect 2003 envoirement.
publish a rule for owa 2010 using the mail2.domain.com name
test the access from outside using mail2.domain.com and seeing if your redirected to mail.domain.com (use 2003 mailbox and i'm assuming that you have forms based on 2003. if you dont have you cant get double authentication but test anyway)
this tests that i recomended wont affect 2003 envoirement.
http://www.zerohoursleep.com/2010/01/installing-your-first-exchange-2010-cas-or-the-truth-about-exchange2003url-part-1/