Exchange Server Forums

help with client access server role

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> help with client access server role

Page: [1]

Message

<< Older Topic Newer Topic >>

help with client access server role - 27.Apr.2009 3:39:36 AM

3xch@ng3

Posts: 9
Joined: 23.Apr.2009
Status: offline

our former setup which is exchange 2000 environment, involves two exchange 2000 servers and one FE (frontend) for OWA.

We successfully migrated our first site over the weekend. Yey! OWA is working. Now, my concern is how will i install the second server on our second site this coming weekend, will i install CAS also?

i have around 700 users, 600 on the first site with 100 OWA users, and 100 on the second site with 20 OWA users.

Our public IP which is 203.x.x.x is pointed to our newly installed exchange 2007 (with hub transport, mailbox, CAS server role) which is 192.99.7.107. Now, if i install our second exchange server in our second site 192.99.8.14, how will users in the second site access the owa?

am planning of single internet accessible client access server for all sites. how will i do it?

Post #: 1

Featured Links*

RE: help with client access server role - 27.Apr.2009 10:59:33 AM

Elan Shudnow

Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline

One thing to keep in mind here is that whenever a site hosts an Exchange Server, you need to have at minimum 3 roles in that site; CAS, MBX, and HUB.

When dealing with the CAS Server in multiple sites, you will want to learn about proxying and redirection. Essentially, if you have 1 internet facing CAS Server, all CAS traffic will hit that internet facing CAS Server and then either proxy or redirect the client. An important thing to note here is that the only service that allows redirection is OWA. OWA will redirect a browser to use the -ExternalURL defined for the CAS in the other site.

If you leave the -ExternalURL set to $null (blank) for the intranet facing CAS, the internet facing CAS sees the user belongs to a MBX server in another site and sees that it has a blank -ExternalURL and then starts proxying to the -InternalURL.

Check out these articles:
http://technet.microsoft.com/en-us/library/bb310763.aspx
http://msexchangeteam.com/archive/2007/09/04/446918.aspx
http://msexchangeteam.com/archive/2007/09/10/446957.aspx
http://msexchangeteam.com/archive/2007/10/12/447266.aspx

_____________________________

Elan Shudnow
Exchange MVP
http://www.shudnow.net

(in reply to 3xch@ng3)

Post #: 2

RE: help with client access server role - 27.Apr.2009 9:13:50 PM

3xch@ng3

Posts: 9
Joined: 23.Apr.2009
Status: offline

thank you very much. you hit the nail on the head. =) what i am looking for exactly

(in reply to Elan Shudnow)

Post #: 3

RE: help with client access server role - 7.May2009 4:12:16 AM

3xch@ng3

Posts: 9
Joined: 23.Apr.2009
Status: offline

hi. i cant make the proxying to work.

i keep getting the follwoing error message:

"Outlook Web Access is not currently available for the user mailbox that you are trying to access. If the problem continues, contact technical support for your organization and tell them the following: Outlook Web Access could not establish a Secure Sockets Layer (SSL) connection to the Microsoft Exchange Client Access server that should be used to access the mailbox."

i have configured as the resources has suggested. i dont know what to do next.

(in reply to 3xch@ng3)

Post #: 4