CAS server placement

Is it mandatory to have CAS server in each AD site where mailbox server is present, can we have following setup in exchange 2013.
AD Site A
Mailbox server
CAS Server
AD Site B
Mailbox Server
All Client request for the mailbox hosted on AD Site B mailbox server will be redirected by Site A CAS server to Site B mailbox server

Yes.
http://technet.microsoft.com/en-us/library/aa997281(v=exchg.150).aspx
Each organization requires at a minimum one Client Access server and one Mailbox server in the Active Directory forest. Additionally, each Active Directory site that contains a Mailbox server must also contain at least one Client Access server. If you're
separating your server roles, we recommend installing the Mailbox server role first.
Why not simply make the SiteB mailbox server multi-role? That is recommended.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Do i need a CAS server per AD site?

Hi!
So I have been browsing through a lot of Exchange Server documentation, guides and best practice but I have not found (or misunderstanding) the CAS placement for my situation.
We are currently in the process of upgrading to Exchange server 2013. As we have an Exchange 2003 only deployment, we will first need to move to Exchange 2010 and get rid of all the Exchange 2003 servers and then move on to Exchange 2013. We have a
single domain with 21 AD sites. 8 of these sites (Vessels at Sea) are connected by vSat the other 13 of these sites a remote offices with a more stable connection than vSat.
We want to have a MBX server at every site and what I get from the available documentation on the internet I will also need a HUB server per AD site. What I am not sure about is, do I also need a CAS server per site? What I get from this excerpt:
"A new service was introduced with Exchange Server 2010 to allow these MAPI connections to be handled by the Client Access
server. The RPC Client Access service provides data access through a single, common path of the Client Access server, with the exception of public folder requests, which are still made directly to the Mailbox server. This change applies business logic to clients
more consistently, and provides a better client experience when failover occurs." (ref Understanding RPC Client Access.), is that I also
need a CAS server per site.
Can somebody give me any definite insights in this one?
To summarize the question:
In a multi site AD with a MBX server per site, do I also need a CAS server per site?
Your help is much appreciated!
Regards,
Erik

(for Exchange 2010) You need CAS and Hub role in each site where Mailbox role deployed
Understanding Client Access
"You must install the Client Access server role in every Exchange organization and every Active Directory site that has the Mailbox server role installed"
Overview of the Hub Transport Server Role
"You must deploy a Hub Transport server role in each Active Directory site that contains a Mailbox server role"
Blog - Smtp25.ru

Can i use same certificate on 2 different CAS Server across sites

Hi All
I have a question I have been playing with for a few days,
I have the following setup,
2 sites connected via a VPN and a DAG configured between sites.
Site 1-Head Office
2 exchange 2010 servers,
1 running CAS and Mailbox (this server is entry point to all clients for owa etc.)
1 running Hub, CAS, Mailbox. (this is the main server and a DAG Member)
We have a UNC certificate associated with all records pointing to remote access and its installed on both servers.
** Everything in this site works fine.
** The AD DNS server does not have a zone for the public domain with all the external records only the .local domain. Planning to change this soon.
Site 2.
1 exchange 2010 servers,
1 running Hub, CAS, Mailbox. (this is the main server for this site, a DAG Member and no entry point at this time but we intend to use it for redundancy)
** Currently all BD are on server in site 1.
** The AD DNS server does not have a zone for the public domain with all the external records only the .local domain. Planning to change this soon.
My questions are as follows:
1      on site 2’s the cas server can I use the same certificate I’m using onsite 1. in other words all clients currently use mail.domain.com which has an IP pointing to site 1, can I use that same certificate in site 2 and associate
it with the CAS server there? (in the event of a failover I just change the records IP)
2      All smtp traffic come through site 1, when I test moving active databases to site 2, all email stay in the ques of exchange server in site one, they don’t get delivered. (I have not set AD replication through smtp so don’t know
if this is a factor)
3      When I do set the active databases to site 2, webmail and remote services stop working, I get the infamous error when logging onto webmail, service unavailable because it’s been moved. I have read a lot about this being an internal
external url issue.
All these issues im starting to think they all interlinked, and would like some help.
Cheers

Answers to your questions:
Yes. Understand that until you swap your external DNS so it points to Site 2, the mail.domain.com won't be accessed, but it will be there for when you want it to be.
AD replication is not the issue, so don't try to set it to use SMTP. If you have hub servers in both sites, your inbound Internet email should be delivered from the Site 1 hubs to the Site 2 hubs. We may need more information before we can give
you a good answer for this question. However, you may check the following TechNet article (and its links) for assistance.
http://technet.microsoft.com/en-us/library/aa998825(v=exchg.141).aspx
Web access requires that the CAS you connect to be either externally accessible and in the same site as your mailbox server, or that the CAS in the inaccessible Windows site needs to be configured as internal only and the accessible CAS needs to be configured
to proxy connections. For this, make sure you have followed the directions in the following TechNet article.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
HTH ...

Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

Hi all,
I could really do with your help!
We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site. Site C has links to both sites A & B, but the link is a lot slower.
We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites. Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
however we can have both roles on the same server if required.
What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
Has anyone else come across this situation and how did you get round it?
Thanks in advance :)

Hi Johnson,
Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
Please check whether the CAS server that in site C is healthy.
If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
Also found a useful blog for your reference:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 - CAS Server Multi Namespace & Site Deployment

Hello,
I am
currently designing the new Excahnge 2013 environment that I am looking to deploy by the end of the month. And I have come up with two designs on what could be deployed. The first being an active/passive design with a single namespace across two sites.
One site being the primary site and the other being the secondary DR site in a single DAG. Now this is a common design and similar setups are documented in detail online on many blogs and such.
Where my trouble is with the second design I have come up with which is an active/active model using a multi namespace across the same two sites utilizing two DAGs. The idea here being the first
site is the corporate head office which would only contain those users. While the second site would contain everyone else not based out of the head office. The goal being to cut out internal users from connecting all of the way into the primary site when they
are external to it.
Now the way in which the network is setup between the two sites. Accessing the internet from the primary site requires you to go through the secondary. So for the second design my idea would
be for external Outlook, OWA and ActiveSync connections would connect into the secondary site for it to then proxy over to the primary. Now I am used to how Excahnge 2010 did its proxying and if the ExternalUrl property was blank is knew to proxy to the other
site. Is that still the case with Excahnge 2013 or it does not care at all and I can just populate both the internal/external url properties for all of the CAS servers at the primary site?
Now assuming I do populate both the internal/external url property in Excahnge 2013 for the primary site. And for this example I am going to use mail01.domainname.com for the primary site and
mail02.domainname.com for the second. To get Outlook, OWA and ActiveSync to connect for users of the primary site externally would it be as simple as having that external internet DNS entry for mail01.domainname.com point to the same IP as mail02.domainname.com
would be? With mail02.domainname.com pointing to a externally accessible load balancer for the second site.
Now applying the above logic and assuming as long as you hit a CAS server. And it will find your mailbox for you does that mean I can could also use the same namespace in both locations for
say OWA and ActiveSync? So the idea being we want to keep using webmail.domainname.com for OWA access. So if I set that URL for both the primary and secondary site as long as I hit a CAS server in the secondary site. It will be able to connect over to the
mailbox in the primary site for OWA?
Nicholas

Hello Angela,
I need some clarification to your reply as it has left me a little more confused. Where you start by saying “all client requests will firstly access the internet-facing server”.
Are you talking about when the client is connecting in externally or when the client is internal? As this would make it seem like in my second design where only the secondary site would have internet facing CAS. That clients in the primary site internally
would connect over to the secondary site then be proxyed back to the primary.
Then for the separate namespace portion of your reply. I am assuming you mean the secondary site form my example which will have the internet-facing CAS server? If that is
the case my public DNS entry would be mail02.domain.com only but then how would the client from the primary site who use mail01.domain.com which is not on an internet facing CAS server. Then figure out they can connect in on mail02.domain.com externally from
the internet?
And when you talk about both sites using the same namespace. And using two public DNS entries pointing to the CAS servers in both datacenters. Is that not just going to do
DNS round robin? As described in this technet blog?
http://blogs.technet.com/b/exchange/archive/2014/02/28/namespace-planning-in-exchange-2013.aspx
Or is it because both datacenters will be hosting active mailboxes. Will the clients query each CAS server till it finds one in its site? I do also plan to deploy a load balancer with my CAS servers. So I would think that would cancel our using the two public
DNS option.
Nicholas

Outlook won't connect to CAS server in another site

Hey guys, so heres my scenario, we were testing a primary site
dag outage, and not for all the tea in China would outlook connect to the DR sites CAS server. When I look at outlook its still trying to connect to the
cas server in my primary site, when I run the
autodiscover test from the clients outlook, within the output, I see it fails on the primary and goes to DR CAS as it should, I even did a repair and that didn't work.
i had to edit the host files on the client and point it directly
to the DR server and then it connected, and by that
i mean, it kept trying to connect to EX01 instead of DR01, so
i edited the host file to make the client go to DR01 as EX01, which
worked, so I'm not sure what's going on. All of this is internally btw.
Current design:
Exchange 2010 SP2 - 1DAG (3 members)
"Primary site": 2 DC's, 2 DAG members, 2 Hub/CAS
"DRSite"; 1DC (Alternatewitness), 1 DAG member running all roles
Testing server blackout scenario at the primary site, was able to get mailboxes mounted on DR site, OWA works, able to receive mail, outlook only works if DNS is reworked.
Thanks in advance for any suggestions.

Hey guys, finally got around to testing this, it
didn't work :(.
i built a lab with same versions and it worked automatically, the clients just connected
on their own.
anythingelse
I can check?
SIDENOTE: Not sure if related... i remember once
we had a problem where users could could not login to their mailbox using SITEA CAS servers when the databases were hosted in SITEB and in ADSIEDIT was made to allow this to happen, the change had us edit the CAS server's site so that instead of being in DRSITE
it was to SITEA. (Hopefully that makes sense can't remember exactly where that change was made in ADSI).

New Exchange 2013 CAS server in existing Exchange 2007 Organization

Dear Friends,
We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
https://servername/ecp/?ExchClientVer=15
Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
Thanks in advance!!

Dear Friends,
We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
https://servername/ecp/?ExchClientVer=15
Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
Thanks in advance!!
If you have only the 2013 CAS installed and not the mailbox role, then nothing will really work. Remember, in 2013, the mailbox role does all the work, the CAS is simply a proxy for the most part.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

NAC Unable to add CAS server in the CAM manager

Hi,
We are facing the issue with adding CAS server in the CAM manager. While Adding CAS server to CAM manager ; we are getting Failed to add server: Could not connect to 172.22.105.13 error on the CAM manager.
FYI, We have added CAS server certificate on CAM and viceversa. My CAS and CAM server is working in HA mode.
Also We are getting following error on the CAM manager.
SSL Communication 2014-07-30 14:16:17 SSLFilter:access deniedCN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:No trusted certificate found
SSL Communication 2014-07-30 14:16:17 SSLManager: client's certificate chain verification failed CN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:No trusted certificate found
SSL Communication 2014-07-30 14:15:57 SSLManager: client's certificate chain verification failed CN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:No trusted certificate found
SSL Communication 2014-07-30 14:15:57 SSLFilter:access deniedCN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:No trusted certificate found
SSL Communication 2014-07-30 14:15:37 SSLManager: client's certificate chain verification failed CN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:No trusted certificate found
SSL Communication 2014-07-30 14:15:37 SSLFilter:access deniedCN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:No trusted certificate found
SSL Communication 2014-07-30 14:15:17 SSLManager: client's certificate chain verification failed CN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:Certificate signature validation failed
SSL Communication 2014-07-30 14:15:17 SSLFilter:access deniedCN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:Certificate signature validation failed
SSL Communication 2014-07-30 14:14:57 SSLManager: client's certificate chain verification failed CN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:Certificate signature validation failed
SSL Communication 2014-07-30 14:14:57 SSLFilter:access deniedCN=172.22.105.11, OU=IT, O=XYZ, L=ABC, ST=UAE, C=AE:Certificate signature validation failed

Fix Certificate Errors on the CAM/CAS:
http://www.cisco.com/c/en/us/support/docs/security/nac-appliance-clean-access/107909-416CertFix.html

Commissioning a new CAS server in existing Exchange 2013 org

I have a question about why my Outlook client would connect to a newly Exchange 2013 CAS server although not a lot of configuration has been done on it? Also, the existing CAS servers are configured with a third party load balancer and the new server was
not added to the existing array configuration?
I do understand the connectivity and the integration between the CAS and the MAILBOX servers and I would like to know if there is a maintenance mode of the CAs server that has just been deployed into an existing org and configure all the relevant info before
allowing connections to it? Thanks.
Chris

Hi,
Could you tell us your DNS settings about:
HLB
Autodisover
Outlook Anywhere internal name.
Regards,
Simon Wu
TechNet Community Support

Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

Hi people,
What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
Thanks

Hey AlbertWT,
Can you clarify exactly what you mean when you say "server patching?" Do you mean patching at the ESXi host level or something within the guest?
As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer. Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role. NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
Matt
http://www.thelowercasew.com

Exchange 2013 CAS IMAP Proxying to offline 2007 CAS Server

We're running in coexistence mode with 2013 and 2007. We had one of our 2007 CAS servers go down. We have IMAP users that keep getting a login prompt now. Looking at the IMAP logs it's failing when the 2013 CAS server tries
to proxy the IMAP session to the down 2007 CAS server. Is there any way to stop 2013 from attempting to proxy to the down 2007 CAS server? We have 3 other 2007 CAS servers that are available.

Hi,
I‘m following up this thread and if you have any question about the above information I provided, please feel free to let me know.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2013 CAS server returned '500 Message rejected'

Hi, all.
Exchange 2013 with CAS server and 2 mailbox servers. Health checks are all 100% healthy.
One of our users cannot receive email from an external user. Our CAS server keeps rejecting the message. I can trace the message and see that it did indeed hit our servers, and was rejected. But I cannot find out WHY it was rejected.
Here is the Delivery Report from the EAC:
Delivery Report for               NAME ‎([email protected])
Failed
3/30/2015 1:41 PM <CAS servername>
The message couldn't be delivered.
[{LRT=};{LED=500 Message rejected};{FQDN=};{IP=}]
The external user gets this NDR:
<our local CAS servername> gave this error:
Message rejected
In the Diagnostic information for administrator section:
<our local CAS servername> returned '500 message rejected'
followed by the Original message headers. I think I'm looking for some more verbose logging to see what rule or configuration rejected the message. Any help would be greatly appreciated!
Thanks!
Dan

My main question: how can I see what triggered my CAS server to reject this message with error 500?
Our user can receive email from other external senders ok. It seems to be just this one sender having trouble.
Our transport rules are not complex, and I see no rules that would block this sender or domain.
We use Exchange Online Protection. The message gets through EOP and hits our CAS server. The CAS server rejects the message - it never gets to the Client.
The CAS server gives the error 500 - but that's all I can find. I need a command or somewhere to look to see what triggered the 500 error.
I've posted the NDR received by the sender and scrubbed our identifying information.
Rcn.com looks like the sender's online forwarding host - the spf record for senderdomain.net points back to rcn.com. I've run an spf record check and it passes, so I do not believe that is the issue.
Here is the NDR:
From: [email protected]
To: [email protected]
Sent: Monday, March 30, 2015 1:41 PM
Subject: Undeliverable: Hello from FirstName
CAS1.our_internal_domain.local rejected your message to the following email addresses:
FirstName LastName ([email protected])
A problem occurred while delivering your message to this email address. Try sending your message again. If the problem continues, please contact your email admin.
CAS1.our_internal_domain.local gave this error:
Message rejected
Diagnostic information for administrators:
Generating server: BY1PR0501MB1112.namprd05.prod.outlook.com
[email protected]
CAS1.our_internal_domain.local
Remote Server returned '500 Message rejected'
Original message headers:
Received: from BLUPR05CA0049.namprd05.prod.outlook.com (10.141.20.19) by
BY1PR0501MB1112.namprd05.prod.outlook.com (25.160.103.146) with Microsoft
SMTP Server (TLS) id 15.1.118.21; Mon, 30 Mar 2015 17:40:54 +0000
Received: from BL2FFO11FD027.protection.gbl (2a01:111:f400:7c09::115) by
BLUPR05CA0049.outlook.office365.com (2a01:111:e400:855::19) with Microsoft
SMTP Server (TLS) id 15.1.125.19 via Frontend Transport; Mon, 30 Mar 2015
17:40:54 +0000
Received: from smtp.rcn.com (69.168.97.78) by
BL2FFO11FD027.mail.protection.outlook.com (10.173.161.106) with Microsoft
SMTP Server (TLS) id 15.1.130.10 via Frontend Transport; Mon, 30 Mar 2015
17:40:54 +0000
Return-Path: [email protected]
X_CMAE_Category: , ,
X-CNFS-Analysis: v=2.0 cv=PMSNCIWC c=1 sm=1 a=gRQJo8bc1j9+0GSSRogFxg==:17 a=NTyKUL13AAAA:8 a=ML7w5Z3_AAAA:8 a=3H5rcUylbt2uBKgiyYQA:9 a=wPNLvfGTeEIA:10 a=XQfDMMe_SRUA:10 a=SEXQnC1BqQAA:10 a=7ZjHjvgxCjAA:10 a=Wcs1mLwGzyUA:10 a=sBa8ZLUje9YA:10 a=k-GqB2yPh3IA:10
a=N4kHG9ehtKzd7-3o534A:9 a=_W_S_7VecoQA:10 a=gRQJo8bc1j9+0GSSRogFxg==:117
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
X-Authed-Username: ZHAtZm1hQHJjbi5jb20=
Authentication-Results: smtp02.rcn.cmh.synacor.com
[email protected]; sender-id=neutralourdomain.com; dkim=none
(message not signed) header.d=none;ourdomain.com; dmarc=pass action=none
header.from=senderdomain.net;
Authentication-Results: smtp02.rcn.cmh.synacor.com [email protected]; spf=neutral; sender-id=neutral
Authentication-Results: smtp02.rcn.cmh.synacor.com smtp.user=sender; auth=pass (LOGIN)
Received-SPF: neutral (smtp02.rcn.cmh.synacor.com: 69.72.92.252 is neither permitted nor denied by domain of senderdomain.net)
Received: from [69.72.92.252] ([69.72.92.252:2689] helo=FirstNameLastName)
        by smtp.rcn.com (envelope-from <[email protected]>)
        (ecelerity 3.6.2.43620 r(Platform:3.6.2.0)) with ESMTPA
        id 58/6E-17115-4AA89155; Mon, 30 Mar 2015 13:40:53 -0400
Message-ID: <011A7DBF0D954F62987032D45778AF29@FirstNameLastName>
From: FirstName LastName <[email protected]>
To: FirstName LastName <[email protected]>
Subject: Hello from FirstName
Date: Mon, 30 Mar 2015 13:40:49 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0007_01D06AEF.223E4A60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-EOPAttributedMessage: 0
Received-SPF: Pass (protection.outlook.com: domain of senderdomain.net designates
69.168.97.78 as permitted sender) receiver=protection.outlook.com;
client-ip=69.168.97.78; helo=smtp.rcn.com;
Authentication-Results: spf=pass (sender IP is 69.168.97.78)
[email protected];
X-Forefront-Antispam-Report:
        CIP:69.168.97.78;CTRY:US;IPV:NLI;EFV:NLI;SFV:SKN;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BY1PR0501MB1112;H:smtp.rcn.com;FPR:;SPF:None;LANG:en;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1112;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test:
        BCL:0;PCL:0;RULEID:(601004);SRVR:BY1PR0501MB1112;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1112;
X-OriginatorOrg: ourdomain.onmicrosoft.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Mar 2015 17:40:54.1243
(UTC)
X-MS-Exchange-CrossTenant-Id: c92ecf05-92f8-42f4-a246-24bee4988793
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1112
Dan

Exchange server 2010 Hub-Cas server role remove from organization

Dear all,
I am going to remove my one of my hub-cas(both the roles installed in same server)server from my organization.
Cas server configured into cas array. So anyone please guide me to remove safely.
Parthiban selvaraj

Hi,
From your description, I would like to clarify the following thing:
If you use NLB, you need to remove the CAS server from your NLB cluster and then remove this CAS&Hub server. If you use other sort of load balancer, you need to use it to remove the server from the CAS array and then remove the server.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

CAS server in the same Site Ex2013

As per google search, You don't need to have CAS server in the same site as the mailbox then How outlook will connect to Exchange.

Hi,
Agree with the above suggestion, there should be both CAS role and mailbox role in one site. CAS server provides authentication and proxy/redirection logic, supporting the client Internet protocols, transport, and Unified Messaging. Proxy and redirection
also need CAS server.
If you have any question, please feel free to let me know.
Best regards,
Angela Shi
TechNet Community Support

Cas server uninstall failed... Now how to reinstall?

Ok, here is the scenario a company set up an exchange server and IIS config got damaged. So I followed the microsoft guide on uninstalling IIS then the cas server only problem was the cas fail the uninstall about half way through now I can't uninstall
or reinstall.
Also can't reinstall the OS....
Any Ideas.
Output from installer:
Client Access Role
Failed
Error:
The following error was generated when "$error.Clear();
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
        " was run: "Process execution failed with exit code 1168.".
Process execution failed with exit code 1168.
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:00:01
Thanks in advance

Sadly the guys that own the server only have the one and won't let anyone onsite on the weekends but they don't want downtime so basically they want the
perfect server!
Original Log:
# Component tasks
# Tasks for 'All Roles Common Last' component
# [ID = AllRolesCommonLast___25c25f6a6e484b32bedc5d6fa5ea3699, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
5/12/2010 12:50:07 AM:remove-InstalledRoleInfo -RoleName $RoleRoleName
# [ID = AllRolesCommonLast___6f2b6624392e4f678c9b5a386a4916ae, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
5/12/2010 12:50:07 AM:
          if ($RoleRoles)
            & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoles.Replace('Role','').Split(',')
# [ID = AllRolesCommonLast___f688defc7999417ba5c8e7b4ca41a971, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
5/12/2010 12:50:07 AM:
          & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoleName.Replace('Role','')
# [ID = AllRolesCommonLast__StartWinMgmt, Wt = 5, isFatal = True] "Starting the WMI service."
5/12/2010 12:50:08 AM:
          if (Get-Service WinMgmt* | ?{$_.Name -eq 'WinMgmt'})
            Set-Service WinMgmt -StartupType Automatic
            Start-SetupService -ServiceName WinMgmt
# [ID = AllRolesCommonLast__StartRemoteRegistry, Wt = 5, isFatal = True] "Starting the Remote Registry service."
5/12/2010 12:50:08 AM:
          if (Get-Service RemoteRegistry* | ?{$_.Name -eq 'RemoteRegistry'})
            Set-Service RemoteRegistry -StartupType Automatic
            Start-SetupService -ServiceName RemoteRegistry
# Tasks for 'File distribution Service Control' component
# [ID = FileDistributionServiceControl___474b4dc5deb44f7ca748da725a0ecac3, Wt = 1, isFatal = True] "Stopping the Microsoft Exchange File Distribution service."
5/12/2010 12:50:08 AM:stop-SetupService -ServiceName MSExchangeFDS
# Tasks for 'RPC Client Access Service Control' component
# [ID = RpcClientAccessServiceControl___4b4248cce65c4ccaa92fe5f938f2aedc, Wt = 1, isFatal = True] "Stopping Microsoft RPC Client Access."
5/12/2010 12:50:10 AM:stop-SetupService -ServiceName MSExchangeRPC
# Tasks for 'Client Access Service Control' component
# Tasks for 'File Distribution Service Configuration' component
# [ID = FileDistributionServiceComponent___659b38f67e0240199f57f0c851fe7a2b, Wt = 1, isFatal = True] "Uninstalling the Microsoft Exchange File Distribution service."
5/12/2010 12:50:11 AM:uninstall-FileDistributionService
# Tasks for 'File Distribution Service Group Metrics Perf Counters' component
# [ID = FDS_GM_PerfCountersComponent___8c292d9c21af44358441a4c99baddeab, Wt = 1, isFatal = False] "Installing FDS GM PerfCounters."
5/12/2010 12:50:16 AM:remove-perfcounters -DefinitionFileName FDSGMPerformanceCounters.xml
# Tasks for 'File Distribution Service OAB Perf Counters' component
# [ID = FDS_OAB_PerfCountersComponent___103a4c1adf974591be38633f58ec1ebc, Wt = 1, isFatal = False] "Installing FDS OAD PerfCounters."
5/12/2010 12:50:17 AM:remove-perfcounters -DefinitionFileName FDSOABPerformanceCounters.xml
# Tasks for 'Enable RPC over HTTP redirector firewall exception' component
# [ID = RpcHttpRedirectorException___653184838b334e749dbc87a567e865b2, Wt = 1, isFatal = False] "Configuring the server."
5/12/2010 12:50:17 AM:
          if ([Environment]::OSVersion.Version.Major -ge 6)
          Remove-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.RpcHttpRedirectorRule)
# Tasks for 'Address Book Service Configuration' component
# [ID = AddressBookComponent___fe2c1cbb8e954dd786870cdc8b3d85e9, Wt = 1, isFatal = True] "Configuring the Microsoft Exchange Address Book service."
5/12/2010 12:50:17 AM:uninstall-AddressBookService
# Tasks for 'RPC Client Access Protocol Configuration' component
# Tasks for 'Client Access Services Configuration' component
# [ID = ServicesComponent___ca981854eaa74c1ca684178d9ea52fff, Wt = 1, isFatal = True] "Configuring Client Access services."
5/12/2010 12:50:23 AM:
     get-WebServicesVirtualDirectory -Server $RoleFqdnOrName -DomainController $RoleDomainController | remove-WebServicesVirtualDirectory -DomainController $RoleDomainController -Force;
# [ID = ServicesComponent___98bb14bb96bc43babb98f8d36183263e, Wt = 1, isFatal = True] "Configuring Client Access services."
5/12/2010 12:50:24 AM:get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | remove-ActiveSyncVirtualDirectory -DomainController $RoleDomainController
# [ID = ServicesComponent___9b5feb8e2ff64c4ebd10edb43c3a2aa9, Wt = 1, isFatal = True] "Configuring Client Access services."
5/12/2010 12:50:26 AM:
     $clientAccessServer = get-ClientAccessServer -Identity $RoleFqdnOrName;
     if($clientAccessServer)
         if(($clientAccessServer.AutoDiscoverServiceInternalUri) -and ($clientAccessServer.AutoDiscoverSiteScope))
      set-ClientAccessServer -Identity $RoleFqdnOrName -AutoDiscoverServiceInternalUri:$null -AutoDiscoverSiteScope:$null
# [ID = ServicesComponent___a8409d9e1e024948a9cf2805368de7dd, Wt = 1, isFatal = True] "Configuring Client Access services."
5/12/2010 12:50:27 AM:get-AutodiscoverVirtualDirectory -Server $RoleFqdnOrName -DomainController $RoleDomainController | remove-AutodiscoverVirtualDirectory -DomainController $RoleDomainController
# Tasks for 'RPC-over-HTTP Proxy Configuration' component
# Tasks for 'ECP Configuration' component
# [ID = ClientAccessEcpComponent___9b61914c88354a1ca625560e0a59451c, Wt = 1, isFatal = True] "Installing/Removing the ECP component."
5/12/2010 12:50:28 AM:
          get-EcpVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | remove-EcpVirtualDirectory -DomainController $RoleDomainController;
# Tasks for 'OWA Configuration' component
# [ID = ClientAccessOwaComponent___5effe7121e1740c083904cc189687464, Wt = 1, isFatal = True] "Installing/Removing Outlook Web App Component."
5/12/2010 12:50:29 AM:
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
Current Log:
# Component tasks
# Tasks for 'OWA Configuration' component
# [ID = ClientAccessOwaComponent___5effe7121e1740c083904cc189687464, Wt = 1, isFatal = True] "Installing/Removing Outlook Web App Component."
5/12/2010 1:59:07 AM:
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
Any Ideas?

CAS server placement

Similar Messages

Maybe you are looking for