Exchange Server Forums

Adding a new CAS server

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2010] >> Installation >> Adding a new CAS server

Page: [1]

Message

<< Older Topic Newer Topic >>

Adding a new CAS server - 21.Jun.2012 3:59:35 AM

stantheman

Posts: 42
Joined: 15.Dec.2004
From: Cardiff, Wales
Status: offline

We are currently operating an Exchange 2003-Exchange 2010 transitional setup at the moment and all is working fine. The Exchange 2010 has all the roles on it.

We are looking to add a new Exchange 2010 server with just the CAS role on it (and so create a CAS array).

How can I set up a CAS array and do this without impacting on our current setup. I do not want to add any more SANs to our certificate (for web access) nor do I want to change the DNS, which allows access to our webmail (mail.company.com/owa).

Could I just change the OWA DNS entry for our existing CAS and call the new CAS array mail.company.com ?

Post #: 1

Featured Links*

RE: Adding a new CAS server - 21.Jun.2012 8:02:43 AM

Gulab

Posts: 646
Joined: 31.Jul.2008
From: India
Status: offline

Hi,

You can't have CAS Array with single CAS Server, you have to have atleast 2 CAS server.
If you are thinking of using a CAS server ROLE which is part of all role server, it's not going to work.

Creating cas array won't disturb your environment, but make sure you run the below command after creating the cas array.

Get-MailboxDatabase | Set-ClientAccessArray -RPCClientAccessServer -FQDN "FQDN of CAS Array"

The above command will point the MAPI connection to the CAS Array and not the specific CAS Server.

Cheers,

_____________________________

Gulab Prasad,
Technology Consultant
Exchange Ranger
Check out CodeTwo�s tools for Exchange admins

(in reply to stantheman)

Post #: 2

RE: Adding a new CAS server - 21.Jun.2012 11:56:06 AM

DaDougInc

Posts: 845
Joined: 17.May2002
From: NC
Status: offline

Hmm, a CAS array can be any number of CAS servers.
If you want your CAS array to be Mail.Company.com and if you want it to resolve to 2 different CAS servers without a NLB device, you would create 2 DNS records of Mail.Company.com and each record would point to a CAS server.

If you want your CAS array to be Mail.Company.com and if you want it to resolve to 1 CAS server without a NLB device, you would create 1 DNS record of Mail.Company.com and point it to the CAS server.

If you want your CAS array to be Mail.Company.com and if you want it to resolve to multiple different CAS servers with a NLB device in front, you would create 1 DNS record of Mail.Company.com and point it to the NLB.

Personally I don't see a need to have a server with only the CAS role installed. At a minimum, put a Hub and CAS together (even virtualize it if you want).

To say that an Exchange 2003 mailbox will not be impacted is not 100% accurate because the client is a huge part of this. Keep in mind that if you have Outlook 2007/2010 and even with a 2003 mailbox, the client may initially try to connect to the URL that you defined in autodiscover. If that points to Exchange CAS and if you have not properly configured URL & certificates, the client profile creation process can be hindered.

Same goes when we talk about OAB & Free Busy lookups between the 2 Exchange versions.

At a minimum, your SAN cert should have:
Mail.Company.Com
Autodiscover.Company.Com
Legacy.Company.Com

See http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx
You can then use mail.company.com as your CAS array name, published in DNS and/or NLB, and allow clients to connect using a single namespace.

See http://blogs.technet.com/b/exchange/archive/2010/11/22/3411576.aspx for an example.

Good Luck
(Y)

(in reply to Gulab)

Post #: 3