Exchange 2003 to Exchange 2010 Co-Existence Questions
Hello Experts,
I just installed 2 new Exchange 2010 SP2 RU8 servers in Co-Existence with my existing Exchange 2003 environment. Following a great guide So far so good. I just ran into a small (I hope) hiccup and have a few questions:
Hiccup/Question
In testing the creation of a new mailbox on EX2010 i am only presented with my internal AD name for the @ part i.e. my only option is @rds.contoso.com (AD ROOT) but we use @contoso.com. In EX2003 we have all domain variations listed and created for each user listed and default it to @contoso.com for new users. Is there a configuration i have to perform to get those to come over to EX2010?
****Also the other domain variations are listed under Accepted Domains****
Other Questions:
1. I am using a new public name for access for example we currently use webmail.contoso.com to access OWA/ActiveSync/RPC but i have all the CAS services publicly pointing to mail.contoso.com Since we are a fairly small business (75 users) i can easily direct folks to the new mail.contoso.com once i move this mailbox to the new exchange server. Is there any need to setup Legacy redirect then?
2. If i only have 1 CAS 1 HUB and 1 MB do i still need to setup CAS array in active directory or can i wait until i deploy to our Branch Office?
3. If i do have to perform the CAS array setup now will that impact existing RPC client connecting to the EX2003 frontend server?
Thank you!
I just installed 2 new Exchange 2010 SP2 RU8 servers in Co-Existence with my existing Exchange 2003 environment. Following a great guide So far so good. I just ran into a small (I hope) hiccup and have a few questions:
Hiccup/Question
In testing the creation of a new mailbox on EX2010 i am only presented with my internal AD name for the @ part i.e. my only option is @rds.contoso.com (AD ROOT) but we use @contoso.com. In EX2003 we have all domain variations listed and created for each user listed and default it to @contoso.com for new users. Is there a configuration i have to perform to get those to come over to EX2010?
****Also the other domain variations are listed under Accepted Domains****
Other Questions:
1. I am using a new public name for access for example we currently use webmail.contoso.com to access OWA/ActiveSync/RPC but i have all the CAS services publicly pointing to mail.contoso.com Since we are a fairly small business (75 users) i can easily direct folks to the new mail.contoso.com once i move this mailbox to the new exchange server. Is there any need to setup Legacy redirect then?
2. If i only have 1 CAS 1 HUB and 1 MB do i still need to setup CAS array in active directory or can i wait until i deploy to our Branch Office?
3. If i do have to perform the CAS array setup now will that impact existing RPC client connecting to the EX2003 frontend server?
Thank you!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please find my inputs in line.
1. I am using a new public name for access for example we currently use webmail.contoso.com to access OWA/ActiveSync/RPC but i have all the CAS services publicly pointing to mail.contoso.com Since we are a fairly small business (75 users) i can easily direct folks to the new mail.contoso.com once i move this mailbox to the new exchange server. Is there any need to setup Legacy redirect then?
Input:
Configure the Exchange 2003 URL property on the /owa virtual directory. This is necessary for Exchange 2003 and Exchange 2010 to coexist. To configure this property, use the below command.
Set-OWAVirtualDirectory <CAS2010>\OWA* -Exchange2003URL https://legacy.domain.com/exchange
2. If i only have 1 CAS 1 HUB and 1 MB do i still need to setup CAS array in active directory or can i wait until i deploy to our Branch Office?
Input:
If your planning is to use single Client access server even in future then you don't need to configure CAS Array.
3. If i do have to perform the CAS array setup now will that impact existing RPC client connecting to the EX2003 frontend server?
Input:
No it will not.
Diwakar
1. I am using a new public name for access for example we currently use webmail.contoso.com to access OWA/ActiveSync/RPC but i have all the CAS services publicly pointing to mail.contoso.com Since we are a fairly small business (75 users) i can easily direct folks to the new mail.contoso.com once i move this mailbox to the new exchange server. Is there any need to setup Legacy redirect then?
Input:
Configure the Exchange 2003 URL property on the /owa virtual directory. This is necessary for Exchange 2003 and Exchange 2010 to coexist. To configure this property, use the below command.
Set-OWAVirtualDirectory <CAS2010>\OWA* -Exchange2003URL https://legacy.domain.com/exchange
2. If i only have 1 CAS 1 HUB and 1 MB do i still need to setup CAS array in active directory or can i wait until i deploy to our Branch Office?
Input:
If your planning is to use single Client access server even in future then you don't need to configure CAS Array.
3. If i do have to perform the CAS array setup now will that impact existing RPC client connecting to the EX2003 frontend server?
Input:
No it will not.
Diwakar
ASKER
I created it with the rds.contoso.com for the email and when i checked it auto listed the accepted domains and listed the @contoso.com as the default email address so seems to be working as expected.
R-R
Thanks for the response, reviewing. thx