Do you need a CAS Server in Order to Use OWA in Exchange 2010 (E14)?

Status
Not open for further replies.
S

systmstech

We currently utilize Exchange 2003 Standard, and have OWA services. We do not have a CAS Server; therefore weren't sure if the same could be accomplished with Exchange 2010 Standard without a CAS Server.
 
C

Chris Morgan -

you can install the CAS, HUB, and MBX role (all required) on the same box, but yes it's required.Chris Morgan
 
P

Pantherfan

to put it even more bluntly, a cas server is required for exchange 2010 PERIOD, even if you arent doing owa hehe
 
S

systmstech



Well we are using a single box, and all we need is to manage a handful of mailboxes with OWA access.

So we DO have to install a CAS Server? Do you recommend a VM?
 
P

Pantherfan

you just need the role itself, it doesnt have to be a seperate server if you arent concerned about high availability (i.e. setting up a DAG and cas array), you just need to have the cas role installed on your exchange 2010 server. As Chris said put the cas, hub, and mbx role all on one server to "mimic" the older methodology of exchange 2003
 
C

Chris Morgan -

Just in case....Yes...you HAVE to install the CAS. Unless you understand the requirements and considerations for putting Exchange in a VM (it's not a small list) I would not recommend it. Virtualization can definitly benefit a smaller company, considering the budgets usually dont allow for amount resources needs to split out services and provide a proper infrastructure. But the impact of a poorly configured (taking all the defaults and just dropping VM's on a large pool of disks) virtualized environmnet can be ugly for an organization. Not trying to discourage it, just tossing out the cautions.Chris Morgan
 
M

MaliStane



There is one consideration. I have to check if there is the same problem with OWA proxy-ing as with Exchange 2007, when Mailbox role and CAS roll is install on the same Server. But in Exchange 2007 if both roles are install on server, CAS cannot proxy request for mailboxes located on Exchange server 2003.
 
C

Chris Morgan -

that problem doesnt exist with 2010. You have to use the legacy exchange url for that. And with the number of users they are talking about I would recommend dealing with coexistence. should be easy enough to just cut it all over at once.Chris Morgan
 
S

systmstech



I appreciate that info. We will be migrating (transitioning) from Exchange 03 Standard to 2010 Standard within the next couple of weeks.

We do have the basic documentation on trasitioning from 03-10; however it doesn't say anywhere on the doc that the CAS and Hub have to be on it's own dedicated Server. Have any of you performed this type of maintenance, and if so; would you be able to answer the following:

1. What type of maintenance window (downtime) will we need to perform the switchover?

2. Any known issues w/ mailbox migration?

Thanks!
 
S

Sembee [MVP]



You do not have to have the roles on separate machines. In a small environment placing everything on the same box is fine.
Just to clarify the points above about OWA - Exchange 2010 doesn't proxy OWA for any older versions period. All it does is redirect. Therefore the issues of proxying from older versions of Exchange don't occur. If your mailbox is on another version and you login to Exchange 2010, then you will be redirected to the legacy URL.

There is no need for any downtime at all. Simply move the mailboxes when the users aren't around. Leave both the old and the new server active for a week or so, then remove Exchange 2003 correctly. Outlook will redirect to Exchange 2010 automatically.

Mailbox migration using the wizard is usually straight forward. Biggest issue is corrupt items, but you can't do much about that until it happens.

Simon.

Simon Butler, Exchange MVP
Blog | Exchange Resources
 
Status
Not open for further replies.
Top