OWA 2013 Redirect to CAS Servers 2010 Randomly

Hello there!!
I think my case is not a problem, I just need a workaround or some fine adjustment to serve my needs. Follow my scenario:
One Exchange 2013 Server (CU3) with Mailbox and CAS role (coexisting with the 2010 Servers, ready for migration)
Two Exchange 2010 CAS Servers SP3 no rollups
Two Exchange 2010 Mailbox Servers SP3 no rollups (in a DAG)
I have two organizations who share the same exchange infrastructure, just using different smtp address, for example, some users use @yyy.com addresses and others use @zzz.com. We have two CAS servers just to use two different and customized OWA layouts (with
distinct OWA Internet addresses), one for @yyy.com users and other for the @zzz.com users
Also, I have the following database organization:
DB01 - @yyy.com mailboxes - 2010
DB02 - @zzz.com mailboxes - 2010
DB03 - @zzz.com mailboxes - will migrate to 2013
I need to do a partial migration to Exchange 2013, which is to migrate all mailboxes from DB03 database to Exchange 2013,
which will use the owa address for the @zzz.com addresses (We will point it to the new 2013 server).
The problem is that when users from DB02 try to use the 2013 OWA (@zzz.com), Exchange will bring up one of the 2010 OWA interfaces, sometimes the yyy.com customized interface and sometimes the zzz.com customized interface, and I need them to use just
the zzz.com interface.
There is any way that I can force Exchange 2013 to redirect the 2010 OWA users from a specific database to a specific CAS server? I found the command "Set-MailboxDatabase "Database Name" -RpcClientAccessServer EX2010-1.domain.local"",
but this work only for internal use (Outlook over RPC)
Best Regards Folks

Hi,
Firstly, I’d like to explain, the property RpcClientAccessServer shows the CAS server which mailbox connects to. It applies to all users and has no influence on OWA redirection. Because this value determines the location of the RPC end point and OWA request
use HTTPS protocol.
As far as I know, when there are many CAS Servers with same version in the same site, we couldn’t determine the CAS server which OWA request will redirect to.
Maybe we can take advantage of Proxy: proxy request from Exchange 2013 to Exchange 2010 and "disable" redirection:
http://social.technet.microsoft.com/Forums/exchange/en-US/999e3d3c-5919-4fa2-8e3e-a2c952214159/exchange-2010-cas-redirection
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

How to request and install 3rd Party certificate on CAS servers 2010

I have 6 CAS/HUB server installed in same AD site but located physcially at different locations. I need to renew the certificate on all of this servers. We are using Godaddy certificate. Could you please provide the steps to create CSR for all the CAS/HUB
server and how to assign services and import on all the CAS/HUB servers.
Service: IIS/Activesync/OWA/Autodiscover/SMTP/Outlook anywhere.
Note: CAS/HUB is installed on the same server.

Hi,
Generally, to renew a certificate in Exchange server 2010, we can do these steps:
1. Use the New-ExchangeCertificate cmdlet to generate a new certificate request:
New-Exchangecertificate -domainname mail.domain.com, autodiscover.domain.com
-generaterequest:$true -keysize 1024 -path "c:\Certificates\xxxx.req” -privatekeyexportable:$true –subjectname "c=US o=domain.com, CN=server.domain.com"
2. Submit the certificate request to your chosen Certificate Authority(Godaddy), then the CA issues a certificate or chain of certificates.
3. Install the issued SSL certificate on the Exchange 2010 server.
Import-ExchangeCertificate -FileData ([Byte[]]$(Get-Content -Path “c:\Certificates\xxxx.pfx” -Encoding byte -ReadCount 0))
4. Assign the new SSL certificate to the appropriate services on the Exchange 2010 server.
Enable-ExchangeCertificate -Server 'EXCH-H-868' -Services 'IMAP, POP, IIS, SMTP' -Thumbprint 'EDF57B5F9D81F1EC329BFB77ADD4465B426A40FB'
5. Restart IIS service.
Best Regards,
Winnie Liang
TechNet Community Support

How to redirect CAS servers to a new manager

Hi Guys,
We have deployed some CAS servers into our network and was managed by a 3310 NAM. Due to its limitation we decided to replace this with a 3350 NAM but didn't realize to disconnect the CAS servers to the old 3310 NAM. Now we are having issues redirecting these CAS servers to the new 3350 NAM.
Please let us know how we can deal with it. Thanks in advance

The NAC Servers get their configuration from the NAC Manager at every reboot. If the old NAC Manager is offline and you reboot the NAC Server, can you add the NAC Server to the new NAC Manager?
-Dan Laden

Problem: Mixed Exchange 2007 / 2013 CAS Servers with wildcard certificates in Europe and non-wildcard Certficate in China

Hi,
we have following problem. We have a mixed multi-domain one-forest AD environment. We also have still a mixed exchange 2007 / 2013 environment. We also have different CAS Servers for 2007 SP3 (RU15) and 2013 (CU8) in europe and one 2007 SP3 (RU15) CAS Server
in China, because of bad connection to Europe. For the Migration to 2013 in Europe we installed a wildcard-certificate *.xyz.com and used the Set-OutlookProvider EXPR -CertPrincipalName msstd:*.xyz.com, so the wildcard certificate is accepted. Everything in
Europe works fine, inside and outside also between exchange 2007 and 2013 (both CAS Server 2013 and 2007 use the same wildcard certificate). But since the change of the Set-OutlookProvider EXPR we are facing problems with our CAS Server in China, because this
server has a different non-wildcard certificate and a different domain name (cas-server.xyz-china.com instead xyz.com). Now we have the problem that this Chinese CAS server the Outlook Anywhere does not work anymore and prompts always for the username. As
I see it is because of the EXPR change. Is it possible to set the the Outlook-Provider EXPR per Cas-Server ? (They also have their own Autodiscover on this front-end server). Because I see that the Outlook-Provider can only be stored forest-wide.
If not the other solution would be to register the chinese cas server in our xyz.com domain and use the same wildcard certificate on this system right ?
Any help would be appreciate….

Yes setting the EXPR value is most likely the cause of your issue. When you set this value you are telling Outlook to only accept connections from connections that have the cert with the subject name you specify here.
Unfortunately, based on my experience I believe this is an organization wide setting and cannot be configured on a CAS by CAS basis (If I'm wrong someone please keep me honest :)).
So the only option would you have is to change all the URLs to be on *.xyz.com domain. There's no need to change the domain the server actually resides on. The other option would be to purchase a UCC Cert with all the names you need and apply
to all your CAS servers and reset the EXPR value.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Exchange 2013 SP 1 + Lync 2013 CAS servers 100% CPU Load.

Hello. Can somebody explain about one issue?
We have Exchange 2013 CU6 + Lync 2013 (5.0.8308.556) integration. After install Exchange SP1 all Client Access Servers begun to consume all CPU time. In process
explorer there are w3wp.exe (MSExchangeServicesAppPool) and lsass.exe (netlogon context). In IIS logs a lot of events about
GET /EWS/Exchange.asmx/s/GetUserPhoto email=[email protected]&size=HR648x648&CorrelationID=<empty>;&cafeReqId=07966a0b-99a4-4f0a-8a38-a8a83264e46c; 443 - 10.10.10.10 OC/15.0.4659.1001+(Microsoft+Lync) - 401 1 2148074254 46
GET /EWS/Exchange.asmx/s/GetUserPhoto email=[email protected]&size=HR648x648&CorrelationID=<empty>;&cafeReqId=c7fb9499-1dc7-48d9-add6-64156a910de6; 443 Contoso\username 10.10.10.10 OC/15.0.4659.1001+(Microsoft+Lync) - 200 0 0 437
IIS logs are grow up very quickly, about 1GB per day. Before to installing SP1 was not problems. Thanks in advance.

Hi,
From your description, you said that you have Exchange 2013 CU6 + Lync 2013 (5.0.8308.556) integration, then you install Exchange 2013 SP1 on all CAS servers.
Do you mean your Exchange 2013 Mailbox server is CU6, and all CAS servers are SP1?
We had better have the same version on Exchange servers in our environment, if that is the case, please upgrate all to CU6, Exchange 2013 latest version, to check result.
Best regards,
Belinda Ma
TechNet Community Support

Performance counters for exchange 2013 mailbox & cas servers?

what are the Performance counters for exchange 2013 mailbox & cas servers?
similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013.

Hi,
Please see this:
Ask the Perf Guy: Sizing Exchange 2013 Deployments
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Hope it is what you need.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 CAS servers cannot accept connections on Exchange ports

Exchange 2013 Enterprise SP1 / Windows Server 2008 R2 SP1
I have configured site resilience setup with the following at two sites:
- two CAS servers
- six MB servers
Traffic to the CAS servers pass through HLB.
I just discovered that the "01" CAS server at each site is not accepting Exchange traffic.
If I telnet to one of the Exchange ports, it looks like there is a connection, however the moment any character is entered, the connection dies.
For example
- telnet Site01CAS01 25
- ( screen goes blank and DOES NOT display the expected "220 servername Microsoft ESMTP ...." message )
- when I attempt to enter "ehlo" the moment I enter "e" the session is disconnected.
I can successfully perform a telnet connection to the CAS02 server and run through the complete send a test message through telnet process. The session disconnect occurs on the CAS01 server at each site for ANY port controlled by Exchange: 25, 143, 587,
717, 993
I can successfully telnet to ports NOT controlled by Exchange: 80, 81, 8080, 443
There appears to be nothing essentially wrong with IIS
The firewall is DISABLED.
I discovered this issue yesterday.
I upgraded to Excahgne 2013 SP1 10 days ago.
I cannot say for sure if this condition existed before the SP! upgrade. I upgraded from CU1 to SP1
Any thoughts?
Thanks! Tom

Well, port 25 doesnt have anything to do with IIS regardless.
Since this is the CAS, port 25 is handled by the Microsoft Exchange Frontend Transport service .
A couple of things I would check.
Check the server component state. Get-ServerComponentState -Identity <server> to ensure everything is "active".
I assume all the services are running and you have rebooted the server to ensure things start up clean.
Also ensure the NIC on this server is set to register itself in DNS.
Finally, If you have disabled the firewall service on the server, its not supported. You should enable the firewall service and then disable it logically netsh advfirewall set Allprofiles state off
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 MP - CAS servers not beeing discovered

Hi!
I have 2 CAS-servers that are not beeing discovered. Trigger on Demand discovery against these servers fails. Is there a way I can manually force these servers to this role?
Best regards
Rune Haugen

Hi,
Have you checked the option "Allow this agent to act as a proxy and discover managed objects on other computers" for all your Exchange servers?
Please also try to flush health service state and caches for the CAS servers.
More details about flush health service state and caches, please refer to the link below:
http://technet.microsoft.com/en-us/library/hh212884.aspx
Regards
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Proxy vs redirection in CAS

How does Proxy differs from redirection in CAS role in exchange 2010
Aditya Mediratta

Thanks for such a good example Jim-XU , kindly elaborate more on "manual redirection VS silent"
Aditya Mediratta
All explained in the link I posted above. Did you read it?
Silent When this setting is configured, a user’s web browser is automatically redirected whenever a Client Access server must redirect an Outlook Web App request to Client Access server or server array located in another Active
Directory site. When forms-based authentication is configured on the source and target CAS OWA virtual directories (SSL is required), then the silent redirection is also a single sign-on event. For redirection to occur, the target Client Access server Outlook
Web App virtual directory must have an ExternalURL value configured.
Manual When this setting is configured, users will receive a notification that they’re accessing the wrong URL and that they must click a link to access the correct Outlook Web App URL for their mailbox. This notification only
occurs when a Client Access server determines that it must redirect an Outlook Web App request to Client Access server or server array located in another Active Directory site. For redirection to occur, the target Client Access server Outlook Web App virtual
directory must have an ExternalURL value configured.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

OWA 2013 internal/external Untangle

I know the general topic has been touched on a few times pertaining to a internal/external setup, but I wanted to bring the topic up again to see if any new ideas are out there.
With the TMG wind-down I built up a Untangle server and so far and fairly happy with it. As most people probably have said, great in some areas but certainly lacking in some of the features TMG offered.
But... the one major feature I miss with TMG is the ability for it to handle FBA for internal sites like OWA. Since the UT appliance requires the barebones forwarding of traffic directly to the Exchange/OWA internal IP, I have to have FBA enable for
everything. That of course breaks the neat ability to have internal clients auto login with integrated auth.
I did come across a few posts of people trying to create separate OWA sites so internal users could use integrated windows auth, and the other site would continue to use FBA for external users. I tried following the general outline of what I was seeing and
created a separate OWA and ECP site, but every time I tried changing authentication settings I completely hosed the entire log ability. That was multiple headaches with every change attempt so I didn't try to push the idea past a few attempts.
So... I suppose this is a multi part question. If not using a TMG setup, can anybody offer suggestions on what is realistically possible in terms of having a internal/external option.
Thanks

I share your pain. I've set up separate OWA websites on Exchange 2007 and 2010 using port 444 or 4433 with basic authentication which TMG would connect to. When trying to do that in Exchange 2013, I experienced what you say. I've since
read that it can be done, but I haven't yet tested it myself so I can't promise that it would work. In your case, assuming your device will send to a different port, you'd want to make that new OWA web site set for forms authentication.
This thread describes the process others report that they've used.
http://social.technet.microsoft.com/Forums/exchange/en-US/9fcd360f-6658-4940-add7-2f13265cf86b/multiple-owa-sites-on-a-single-server-2012-with-exchange-2013-mailbox-cas?forum=exchangesvrclients
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

OWA 2013 and Timeout

OWA 2013 (CU6) timeout values have been set according the following article.
http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/OutlookOWA/how-configure-public-and-private-computer-settings-owa-2013.html
On the "external" or "public" side - default is 15 minutes. When 15 minutes of inactivity occurs, OWA does not exit the session. Instead the content remains on the screen - and you can browse around the information that remains
in the display. You cannot create a new message or open a message in a new window.
If a browser "refresh" is sent the logon to OWA screen appears.
Contacted Microsoft and they were also able to reproduce this same behavior.
This is not a secure way to handle timeout. Anyone else experience this?

Hi,
The time-out feature will only works with Forms-Based Authentication method enabled on CAS server.
http://technet.microsoft.com/en-us/library/bb124787(v=exchg.141).aspx
Although this document applies to Exchange 2010, it’s just the same in Exchange 2013.
In addition, is there TMG in your deployment? If yes, please refer to the following document to
configure the idle session time-out period for Outlook Web Access clients.
Before performing this task, we must have a Web listener that uses forms-based authentication for Outlook Web Access.
http://technet.microsoft.com/en-us/library/cc995140.aspx
Best Regards.

Installed 2013 into a 2007 environment, cleanly removed 2013 now trying to install 2010

So first, before you flame me, this is in QA!
We installed 2013 into a 2007 environment, then due to shifting business demand, cleanly removed 2013. Now we are trying to install 2010 CAS servers and it goes in fine, reports no errors, but I do not have 'server configuration' on the left pane of
EMC, but I can run any related EMS cmdlet (so not permissions). On the org health page all the info is listed as 'unavailable'. I'm thinking something is left over in AD's config container, but I can't find it. Help?

Hi,
From your description, it seems to be the obsolete information is cached in an EMC file in the Windows profile with whom user has logged into the server. I recommend you follow the steps below for troubleshooting:
1. Go to the following location and delete the Exchange Management Console file. (Note: Before deleting it, please do a backup.)
C:\users\<specific user>\AppData\Roaming\Microsoft\MMC\Exchange Management Console
2. Close EMC and Reopen it.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

OWA 2013 : An error occurred while signing this S/MIME message. No certificate was found.

Hi,
I've configured SMIME (certificate templates, signing/encryption certificate, etc.)
All users receive their certificate, and in Outlook (2010) everything is working as expected.
When I use the OWA 2013 however to send an encrypted message, I receive the error :
"An error occurred while signing this S/MIME message. No certificate was found. If you have a smart card-based certificate, insert the card and try again."
environment : exchange 2013 SP1, ie 9 and 10
Get-SMIMEConfig
[PS] D:\Scripts>Get-SmimeConfig
RunspaceId : 24178a41-aead-45fc-a4c2-5504b2541e7e
OWACheckCRLOnSend : False
OWADLExpansionTimeout : 60000
OWAUseSecondaryProxiesWhenFindingCertificates : True
OWACRLConnectionTimeout : 60000
OWACRLRetrievalTimeout : 10000
OWADisableCRLCheck : False
OWAAlwaysSign : False
OWAAlwaysEncrypt : False
OWAClearSign : True
OWAIncludeCertificateChainWithoutRootCertificate : False
OWAIncludeCertificateChainAndRootCertificate : True
OWAEncryptTemporaryBuffers : True
OWASignedEmailCertificateInclusion : True
OWABCCEncryptedEmailForking : 0
OWAIncludeSMIMECapabilitiesInMessage : False
OWACopyRecipientHeaders : False
OWAOnlyUseSmartCard : False
OWATripleWrapSignedEncryptedMail : True
OWAUseKeyIdentifier : False
OWAEncryptionAlgorithms : 6610
OWASigningAlgorithms : 8004
OWAForceSMIMEClientUpgrade : True
OWASenderCertificateAttributesToDisplay :
OWAAllowUserChoiceOfSigningCertificate : False
SMIMECertificateIssuingCA :
SMIMECertificatesExpiryDate :
SMIMEExpiredCertificateThumbprint :
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Smime Configuration
DistinguishedName : CN=Smime Configuration,CN=Global Settings,CN=customer,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=customer,DC=com
Identity : Smime Configuration
Guid : 1184683a-2fcd-446b-98a6-bf0fb16ca282
ObjectCategory : customer.com/Configuration/Schema/ms-Exch-Container
ObjectClass : {top, container, msExchContainer}
WhenChanged : 17/06/2014 14:21:52
WhenCreated : 17/06/2014 14:21:52
WhenChangedUTC : 17/06/2014 12:21:52
WhenCreatedUTC : 17/06/2014 12:21:52
OrganizationId :
OriginatingServer : DC1.customer.COM
IsValid : True
ObjectState : Unchanged

Have you set up a virtual certificate collection? Looks like that's new with Exchange 2013:
http://technet.microsoft.com/en-us/library/dn626158(v=exchg.150).aspx
http://technet.microsoft.com/en-us/library/dn626155(v=exchg.150).aspx
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

ACE 20 CAS servers

Hi all,
I have to load balance two CAS servers. Is this the correct way to setup the probes and serverfarm. I am using an ACE 20.
probe tcp TESTCAS-PROBE
interval 3
passdetect interval 5
parameter-map type ssl SSL-TESTCAS-FARM-ADVANCED
cipher RSA_WITH_RC4_128_MD5
rserver host TSTCAS
ip address 10.192.6.2
inservice
rserver host TSTCAS2
ip address 10.192.6.3
inservice
ssl-proxy service SSL-TESTCAS-FARM
key testcas.pem
cert testcascert
chaingroup TEST-CHAINGRP
ssl advanced-options SSL-TESTCAS-FARM-ADVANCED
serverfarm redirect HTTP-TESTCAS-FARM
rserver HTTP-TESTCAS
inservice
serverfarm host TESTCAS-FARM
predictor leastconns
probe TESTCAS-PROBE
rserver TSTCAS 80
inservice
rserver TSTCAS2 80
inservice
sticky ip-netmask 255.255.255.255 address source
STICKY-SSL-TESTCAS-FARM
timeout 720
timeout activeconns
replicate sticky
serverfarm TESTCAS-FARM
class-map match-any TESTCAS-VIP
2 match virtual-address 10.192.6.1 tcp eq https
policy-map type loadbalance first-match TESTCAS-POLICY
class class-default
sticky-serverfarm STICKY-SSL-TESTCAS-FARM
policy-map multi-match TESTCASPOLICY
class TESTCAS-VIP
loadbalance vip inservice
loadbalance policy TESTCAS-POLICY
loadbalance vip icmp-reply active
ssl-proxy server SSL-TESTCAS-PROXY
service-policy input TESTCASPOLICY

Hi Kanwal,
Firstly thanks for all your help and time spent on this. I have taken your advice and redone the hole config. I have 2 class maps and 2 serverfarms. Can you please double check my serverfarms and probes?
Below is the full config. Does it look ok to you? Am I on the right track?
probe https TESTCASHTTPS-PROBE
interval 3
passdetect interval 5
expect status 200 200
probe http TESTCASWWW-PROBE
interval 3
passdetect interval 5
expect status 200 200
rserver host TSTCAS
ip address 10.192.158.44
inservice
rserver host TSTCAS2
ip address 10.193.158.58
inservice
serverfarm host TESTCASHTTPS-FARM
predictor leastconns
probe TESTCASHTTPS-PROBE
rserver TSTCAS
    inservice
rserver TSTCAS2
inservice
serverfarm host TESTCASWWW-FARM
predictor leastconns
probe TESTCASWWW-PROBE
rserver TSTCAS
    inservice
rserver TSTCAS2
    inservice
sticky ip-netmask 255.255.255.255 address source STICKY-TESTCASWWW-FARM
timeout 720
timeout activeconns
replicate sticky
serverfarm TESTCASWWW-FARM
sticky ip-netmask 255.255.255.255 address source STICKY-TESTCASHTTPS-FARM
timeout 720
timeout activeconns
replicate sticky
serverfarm TESTCASHTTPS-FARM
class-map match-any TESTCASHTTPS-VIP
2 match virtual-address 10.192.158.60 tcp eq https
class-map match-any TESTCASWWW-VIP
3 match virtual-address 10.192.158.60 tcp eq www
policy-map type loadbalance first-match TESTCAS-POLICY-HTTPS
class class-default
    sticky-serverfarm STICKY-TESTCASHTTPS-FARM
policy-map type loadbalance first-match TESTCAS-POLICY-WWW
class class-default
    sticky-serverfarm STICKY-TESTCASWWW-FARM
policy-map multi-match TESTCASPOLICYHTTPS
class TESTCASHTTPS-VIP
    loadbalance vip inservice
    loadbalance policy TESTCAS-POLICY-HTTPS
policy-map multi-match TESTCASPOLICYWWW
class TESTCASWWW-VIP
    loadbalance vip inservice
    loadbalance policy TESTCAS-POLICY-WWW
service-policy input TESTCASPOLICYWWW
service-policy input TESTCASPOLICYHTTPS

OWA 2013 Redirect to CAS Servers 2010 Randomly

Similar Messages

Maybe you are looking for