Exchange 2013 CU5 admin console access redirection

Hi All,
We have a 2 site exchange system, 1 in UK and the other in USA. UK Serves our UK customers and USA serves our american customers respectively. No clients in yet. Each site has X2 MBX servers and X2 CAS servers. All running on 2012 R2.
The problem we're having is when trying to access the exchange admin center from our UK CAS servers, we are being redirected to the US site's OWA. This has happened just recently after bring up the USA exchange site.
I can still access the exchange admin center from the USA CAS servers but not the UK CAS servers

Hello,
There is no problem with your design of the topology.
Can you just access the EAC by entering the ip address of the local cas?
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

Exchange 2013 CU5 - Outlook Web Access - Error 9646 with HTTP - No error with HTTPS

Hello everyone
i have a strange issue which i actually do not have an idea about what is going wrong.
- Exchange 2013 CU5
- SSL Offloading enabled - Virtual directories configured accordingly
When a user logs in to OWA via HTTP - after a while he sees the inbox but does not see any mail details.
He only sees "Error: Your request can't be completed right now. Please try again later."
After a while i also get an eventlog "9646" with too many open OWA sessions for that user.
Regardless which limit i set in the registry for this - the error does come back - even with 512 sessions allowed.
Working with HTTPS instead of HTTP then EVERYTHING works fine ... ?
Any idea on this?
Actually i am totally lost ...
Best regards
Jörg
Ihr zertifizierter VMware Partner Enterprise Solution Provider, IBM Advanced Partner, Datacore Partner, Microsoft Silver Partner / Solution Provider und Microsoft Small Business Partner. HEGO Informationstechnologie GmbH Telegrafenstrasse 8 D 42929 Wermelskirchen
Geschäftsführer: Jörg Hermanns, Ralf Gogolin Amtsgericht Köln HRB 36509 Fon: +49 (0) 21 96 / 8 82 97 - 0 Fax: +49 (0) 21 96 / 8 82 97 - 23 Web: www.hego-it.com

Hi,
Please confirm if the following features are added in your server manager:
•.NET framework 4.5 -> WCF Services -> HTTP Activation
•Windows process activation service -> Process model
•Windows process activation service -> Configuration APIs
If not, please add these features. Then ran IISReset \noforce from a Command Prompt window to restart IIS service. Also recycle Application Pools in IIS manager.
For more information about the IIS Prerequisites for Exchange 2013, please check the windows feature listed in the following article:
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 CU5 fresh install suffering issues with services not starting and coexistence with 2007

Hi everyone,
Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.
On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.
The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's
The main problems are as follows:
There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport
Service.
The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long... It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
I receive an error in the Event Log regarding RPC over HTTP Proxy
to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down
this post
The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs
for over chatty warnings about disk space (the warning is that we have loads of space...)
This is a brief outline of the environment:
Exchange 2007 SP3 RU13
UK - Two physical locations in a stretch LAN (100Mb WAN)
4 x CCR Cluster Mailbox Servers in two separate CCR Clusters
Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.
Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.
Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.
2 x Virtual Windows 2003 R2 - Hub Transport Servers
2 x Virtual Windows 2003 R2 - Client Access Servers
1 x Virtual Windows 2003 R2 - Unified Messaging Server
1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)
US - One physical location
1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server
Exchange 2013 CU5
UK - Installed into same site along side Exchange 2007 servers
1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server
Problem 2 Error Message - Please note, server names and domain name changed:
Log Name:      Application
Source:        MSExchange Front End HTTP Proxy
Date:          18/07/2014 10:00:37
Event ID:      3005
Task Category: Core
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EXC2013.domain.local
Description:
[RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
Event Xml:
<Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
<System>
    <Provider Name="MSExchange Front End HTTP Proxy" />
    <EventID Qualifiers="32768">3005</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
    <EventRecordID>64832</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EXC2013.domain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>RpcHttp</Data>
    <Data>EXC2007CAS1.domain.local</Data>
    <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
    <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
</EventData>
</Event>

Hi Off2work,
I've gone through the article and the Get-OutlookAnywhere commandlet looks fine (especially when compared with our working CAS).
Having looked through IIS I have spotted two additional misconfigurations with a missing setting to require SSL on the RPC folder and also the .NET version was not set.
I've now set those to Require SSL and .NET 2.0.5072 however this has made no difference following restarted of both 2007 CAS and 2013 servers.
I could potentially reinstall the CAS server or additionally decommission it as we have two of them and the other is not causing any errors with the 2013 server. This broken CAS server doesn't even have DNS records (except it's own hostname) or firewall
rules pointing to it, nor does it have any active client connections if I check with a quick netstat -a
As for UM, it's next on my list following some client/server connectivity testing so I have not yet assigned the SSL to the services or setup the dial plans, etc.
The services do start most of the time, but others then don't so it's not a consistent issue with just this service. On my current boot, the DAG Management service failed to start, but again I don't have a DAG implemented yet.
I will see if UM drops out of that list once I've configured it shortly
Thanks for taking the time to respond (and that goes to DareDevil too)

Update Exchange 2013 CU5 to CU7 - Installation Order

Hi,
I have a multi-site, multi-DAG, Exchange 2010 and Exchange 2013 CU5 installation. All servers are multi-role. We are about to commence a server update to CU7 for all of the Exchange 2013 Servers.
What is the Microsoft supported order in which to upgrade the servers?
Can I do the upgrades over a number of nights, does everything need upgrading together, should I do it site at a time or a DAG at a time?
Are there any TechNet articles which explain the supported method? It is important that during the update to CU7 the installation stays in a supported configuration.
Thanks in advance.

Hi,
As Andy suggested, you need to upgrade Mailbox servers and then upgrade Client Access servers. What's more, if your DAG have more nodes, at first, you need upgrade all non-PAM nodes and then upgrade PAM node.
Here is a helpful blog for your reference.
How to Apply Exchange Server 2013 RTM to Cumulative Update 1 (Note: Though it is upgrading from Exchange RTM to CU1, it also applies to upgrading from Exchange 2013 CU5 to CU7 about the required order issue.)
http://blogs.technet.com/b/justin_gao/archive/2013/04/09/you-need-to-know-how-to-apply-exchange-server-2013-rtm-to-cumulative-update-1.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 with CU3 and silent redirection to different AD site

After updating
Exchange 2013 CU2 to Exchange 2013 CU3, OWA silent site redirection feature become not available. The customer has two Exchange 2013 sites. Before we updated to CU3, user whose mailbox located on site A, could be automatically redirected to OWA on
site A, after he logged on to OWA on site B. IE gives Error page and bring out link to the OWA page on site A. Here is screenshot about issue workaround.
Hopefully someone will help with some hint because it is quite anoying.
All other stuff works good, Outlook anywhere, autodiscover, only this remained.
Thanks in advance,
Fajar

Hi Angela,
According to your description, OWA request cannot be automatically redirected after upgrade.
YESS after upgrade Exchange 2013 CU2 to CU3. CU2 not problem.
1. Will OWA work well if you manually click the OWA URL in the web page?
If i click manual, OWA Url in web page, OWA work well...
PS Command "Get-OWAVirtualDirectory | fl CrossSiteRedirectType"
ONLY HAVE ON EXCHANGE 2010 NOT ON EXCHANGE 2013.
2. Do you can login OWA in site A?
My Mailbox on Site-A, if i login OWA Site A (owa-A.domain.com), OWA work well & i can access my email.
But... if i login from OWA Site-B (owa-B.domain.com), OWA not automatic silent redirect to Site-A, and i must click link below "Use following link to open to mailbox with the best performance https://owa-a.domain.com/owa/auth.owa
My friend Mailbox on Site-B, if he login to OWA Site B (owa-B.domain.com), OWA-B work well & he can access email.
But.. if he login from OWA Site-A (owa-A.domain.com), OWA not automatic silent redirection to Site-B, and he must click link below "Use following link to open to mailbox with the best performance https://owa-b.domain.com/owa/auth.owa
3. Check the IIS log on site B CAS server and find if there is any error about the redirection.
whether there is a bug in CU3?
Hopefully someone will help with some hint because it is quite anoying on our custommer.
Regards,
Fajar

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1
site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)
Problem
EMS on CU5 return very slow result.
EMS on SP1 still ok.
Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
reply from Social.technet

Hi,
Have you used the above cmdlets to check your Exchange server health?
"all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Unable to manage/create Resources, Room/Equipment, Exchange 2013 CU5

Hi
We have a mixed 2007SP3 and Exchange 2013 CU5 eviroment.
Pretty much since CU3 (first version we installed) we have had problems with resources, but since SP1 we cannot create or edit resources.
We have a root domain and three child domains, all Exchange 2013 servers are in the root domain. The Exchange 2007 servers are located in the root and two of the child domains.
When creating a Room we get this:
Note: Pulsar is the E2013 CU5 Mailbox-server, Panerai is a Domain Controller in a child domain.
The Room is the listed but when trying to open it we get this:
In the mailbox-server log we get this log: ID 4 Source MSExchange Control Panel
Current user: 'newsec.se/Consultants and Commons/IT-Stureplan/ADMINISTRATOR'
Request for URL 'https://pulsar.newsec.se:444/ecp/UsersGroups/EditRoomMailbox.aspx?pwmcid=37&ReturnObjectType=1&id=638db8e2-355c-4e44-9e01-f577c470f297(https://owa.stronghold.se/ecp/UsersGroups/EditRoomMailbox.aspx?pwmcid=37&ReturnObjectType=1&id=638db8e2-355c-4e44-9e01-f577c470f297)'
failed with the following error:
System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException:
Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Data.Directory.Recipient.NonUniqueRecipientException: Multiple objects with Sid S-1-5-32-548 were found.
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.FindMiniRecipientBySid[TResult](SecurityIdentifier sId, IEnumerable`1 properties)
at Microsoft.Exchange.Management.ControlPanel.RecipientObjectResolver.ResolveSecurityPrincipalId(IEnumerable`1 sidPrincipalId)
at Microsoft.Exchange.Management.DDIService.MailboxPropertiesHelper.FilterEntSendAsPermission(DataRow inputRow, DataTable dataTable, DataObjectStore store)
We tried to put the AD-account in different domains/OUs... but the same problem occurs.
I have a case with MS-support (114051511444067) but I throw it up here also.
Regards
Robban

Hello Robban,
I didn't see your answer... (no mail notification ?)
I opened a MS ticket (114081411702089) and I got an answer :).
If you check security in ADSIedit.msc on your mailbox database object, you may find ACL entry for the group with the SID reported in the "application error event"
example : (CN=YourBDD,CN=Databases,CN=Exchange Administrative Group (FYDBOHF23SPDLT),CN=Administrative Groups,CN=YourOrganizationName,CN=Microsoft Exchange,CN=Services,CN=Configuration,CN=YourDomain,CN=local)
* "Domain\administrators" (SID S-1-5-32-544
for me )
* "Domain\account
operators" (SID S-1-5-32-548
for you )
Sources : http://support.microsoft.com/kb/243330/en
The "Domain\administrators"
group is not present by default on the exchange organization AD arborescence. I 've checked my customer exchange installation, it seem's the same for "Domain\account operators" group.
To check, you can :
* create a new
mailbox database, and modify the security on these database AD object to remove "Domain\account
operators" ACL (You may have to disable inheritance and copy existing security before)
* Create a ressource mailbox on the new database and edit it using EAC. If your are like me, you
will also be able to edit mailbox permission in EAC for a mailbox on the new database.
If it works, you can validate with MS support that "Domain\Account Operators" group should not have acl on your exchange organisation AD object, and remove the ACL
after a good Active Directory backup
I hope it may help you,
Regards,
Florian

Exchange 2013 + 2007 OWA coexistance not redirecting properly (HTTP 400)

Hello. I am using this document to funnel our new Exchange 2013 external traffic through an IIS ARR reverse proxy, much like we already do for MIcrosoft
Lync 2013 on this machine.
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
I followed this guide to a T. especially the part on the page 2 that I linked above about creating the legacy.domain.com server farm and URL rewrite rule. This
IIS ARR proxy seems to work fine for Outlook Anywhere, ActiveSync, OWA if the user's mailbox is on the Exchange 2013 server, but it does not work if an OWA user logs in with a mailbox on 2007.
When the user has a mailbox on 2007, after logging into OWA they get HTTP 400 error. The URL bar in the browser is changed to https://legacy.domain.com/owa/auth/owaauth.dll
The Exchange 2007 server IIS logs show this:
70.x.x.x, -, 11/1/2014, 9:45:48, W3SVC1, MAIL, 10.1.1.3, 0, 523, 132, 400, 0, POST, /owa/auth/owaauth.dll, -,
I can't figure out why this is happening. DNS is correct. legacy.domain.com points to the 2007 Exchange server. webm.domain.com points to the
Exchange 2013 server.
Any ideas?

Doing more testing, I almost think the Exchange 2007 server keeps redirecting. So the HTTP 400 is because when you hit legacy.domain.com, it redirects
to webm.domain.com which redirects back to legacy.domain.com and vice versa.
I put a test.txt file in the Exchange 2007 owa virtual directory and I cannot access it in any browser. I tried https://legacy.domain.com/owa/test.txt and
It redirects me to https://webm.domain.com(Exchange 2013). I can however go
one level (or more) deep on the legacy server and get a file such as https://legacy.doamin.com/owa/8.3.342.1/themes/base/logon.css and
in the browser I see the code (both externally AND internally, so I know DNS and firewall is working).
I can't find anywhere on IIS 6.0 on the Exchange 2007 server where any kind of redirection is taking place though. Virtual Directory properies for owa say
"A directory located on this computer: "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa" Enable default content page is checked with default.aspx but I looked at default.aspx in notepad and I don't see ANY code telling it to
redirect.
In Exchange 2007 management console OWA internal URL and External URL both sayhttps://legacy.domain.com/owa .
I have no idea what is causing this redirection. I did an iisreset and also recycled the OwaAppPool and no change.

Exchange 2013 and 2007 coexistence and redirects

Hi all,
I'm settings up the coexistence but i've got a problem.
I've got 3 sites:
Site A: Exchange 2013 cas and mailbox
Site B: Exchange 2007 hub/cas and mailbox
Site C: Exchange 2007 hub/cas and mailbox
The problem is the owa and active sync redirect. I can open a mailbox located in site B where the legacy.domain.com dns record points, but i cannot open a mailbox from the exchange 2013 nor 2007 owa from site B to C.
I configured only the internal url leaving the external one blank.
How do i redirect all the requests to a mailbox located in site C from site A and B?
Thanks,
D.

You need to have External URL too, so that redirection can take place.
http://blogs.technet.com/b/mbaher/archive/2009/12/17/exchange-2010-proxy-or-redirect.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 CU3 Can't Access ECP from Office365 Enabled Account

We recently upgraded our Exchange 2013 server to CU3 to fix the OWA redirection error. Unfortunately, we've now noticed that any admin mailboxes that have been 'moved' to Office365 can not access ECP and instead get a redirect warning to OWA.
I had to create a new, onprem admin account to access in the meantime. This is the message I see:
Use the following link to open this mailbox with the best performance:
http://outlook.com/owa/ACME.onmicrosoft.com
X-FEServer: EXCHANGE
Date: 12/3/2013 6:13:23 PM
more detail...
I assume this is due to the fix for OWA redirection? How do I manage Exchange with my 'oncloud' mailbox accounts?

Hi,
I think it will be more suitable to ask this question on Exchange Online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 user cann't access exchange 2013 public folder

Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
problem, thanks.
belows are information about outlook anywhere in our exchange.
exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
Identity                         : SHCAS01\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHCAS02\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : WXCAS01\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL04\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL05\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL06\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : DRPMAIL05\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : DRPMAIL06\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}

Hi,
I have found an article said that we need to set the external host name the same. See more details in the following link:
http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
The following configuration is set on each Exchange 2007 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Sent By
Silver

Exchange 2013 CU5 will not install, please help

Hi everyone
Please help, I am trying to upgrade Exchange 2013 SP1 to CU5 but it just stops at the following point, please help:

Hi,
Have you disabled any third-party firewall or AV programs for a test?
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 - Proxy through client access server not working

Hello All -
I recently migrated our company to Exchange 2013 and noticed that our email was leaving through the mailbox server. I put a check mark in the Send Connector where it says "Proxy through Client Access Server" and my mail is still coming from the
mailbox server. How can I go about fixing this problem?
Environment:
1 CAS Server
1 Mailbox Server
Both server are behind the firewall with only port 25 opened to the CAS. The CAS has a Send Connector to a smart host for all messages.
Thank you!
Ryan

Hi,
Please check if the outbound messages without smart host are coming from CAS .
I doubt it send to the smart host directly if you configure smart host, and not use proxy thogh CAS.
If you have any feedback on our support, please click
here
Wendy Liu
TechNet Community Support

Admin Console access with custom providers

Hello,
I am using a custom authentication and authorization providers that
work just fine with my applications, but i have problems using Admin
Console with them (WL Server 7.0). The server is successfully started
with a user that has been given rights to '<svr>.myserver.boot' etc.
Logging into Console is successful as well and most Console pages can
be viewed as usual. But when i'm trying to save any changes, or if i
try to just view certain Console pages, i get
'weblogic.management.NoAccessRuntimeException'. For example:
weblogic.management.NoAccessRuntimeException: Access not allowed for
subject: principals=[MyPrincipalImpl: Admin Weblogic], on
ResourceType: JDBCTxDataSource Action: write, Target: PoolName
or
weblogic.management.NoAccessRuntimeException: Access not allowed for
subject: principals=[MyPrincipalImpl: Admin Weblogic], on
ResourceType: Security:Name=MyRealmMyAuthenticator Action: execute,
Target: listGroups
When viewing most console pages, the custom provider is called by
WebLogic, resource information is parsed, then found from the
Principal and permission is granted. But as seen above, in some cases
WebLogic itself tries to find something non-existing from my
Principal, totally bypassing my custom provider implementation.
Obviously i am missing something here :).
Is there a way to direct all Console security checks to my custom
provider, or could this perhaps be a matter of configuration?
Any and all help is greatly appreciated!
- Andy -

"Andy" <[email protected]> wrote in message
news:[email protected]..
Hello,
I am using a custom authentication and authorization providers that
work just fine with my applications, but i have problems using Admin
Console with them (WL Server 7.0). The server is successfully started
with a user that has been given rights to '<svr>.myserver.boot' etc.
Logging into Console is successful as well and most Console pages can
be viewed as usual. But when i'm trying to save any changes, or if i
try to just view certain Console pages, i get
'weblogic.management.NoAccessRuntimeException'. For example:
MBean operations need a user with Admin role.

Creating users for admin console access

When I install the web server onto my system part of the installation is to create an admin user and password. I'd like to create another user to log into the web server admin console with the same or limited permissions. I don't want to have to hand out the 'admin' password to multiple people, I'd prefer to create new accounts for each person that needs to administer some part of the webserver and set permissions for each. Can't seem to find out how this is done in the admin guide.

"Andy" <[email protected]> wrote in message
news:[email protected]..
Hello,
I am using a custom authentication and authorization providers that
work just fine with my applications, but i have problems using Admin
Console with them (WL Server 7.0). The server is successfully started
with a user that has been given rights to '<svr>.myserver.boot' etc.
Logging into Console is successful as well and most Console pages can
be viewed as usual. But when i'm trying to save any changes, or if i
try to just view certain Console pages, i get
'weblogic.management.NoAccessRuntimeException'. For example:
MBean operations need a user with Admin role.

Exchange 2013 CU5 admin console access redirection

Similar Messages

Maybe you are looking for