ECP redirects to OWA in Exchange 2013

When logging into ECP 2013, the Exchange Admin Center login does not come up. A Windows Security login window comes up instead and it takes me into Outlook Web
App.
What am I missing?
July 2, 2014 Update. This has been resolved via reinstall. Thank you everyone to assist with this issue.

Have a look here:
http://technet.microsoft.com/en-us/library/jj150562.aspx
"If you’re in a coexistence scenario, where you’re running Exchange 2010 and Exchange 2013 in the same organization, and your mailbox is still housed on the Exchange 2010 Mailbox server, the browser will default to the Exchange 2010 ECP. You can access
the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server CAS15-NA, use the following URL:
https://CAS15-NA/ecp?ExchClientVer=15. Conversely, if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 Mailbox server, use the following URL:
https://CAS14-NA/ecp?ExchClientVer=14."
Try the URL modification:
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
It will show up as OWA authentication but after you provide credentials it will redirect back to EAC.
Flame to MS guys: this modification does not harm the scenario when you do not have the exchange 2010 or 2007 coexistance. Why could not you set the param by default when accessing Exchange 2013 CAS ECP application? Why make all those who attempt
to migrate from older exchange versions (2007 and 2010) stumble upon this problem? Shame on you.
Regards,
Eugene
I added the user to groups and that didnt work. But https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
as suggested in above posted worked for me. (make sure you log out 1st and then try it)

Similar Messages

  • ECP redirect to OWA after server migration

    I have an odd problem with my Exchange 2013 environment after a migration (moving of a server).
    My Exchange environment is as follows:
    2 x CAS/MBX servers (physical machines)
    1 x CAS server (virtual machine used for internal ECP access only)
    All machines were in the same site
    We have two sites and we wanted the virtual CAS server to be moved to our datacentre as part of a DR strategy (it will have the MBX role installed eventually, but initially it will remain a CAS).
    So I powered down the virtual machine, cloned it and moved the clone to the datacenter (all using VMWare). Brought it back up and re-addressed the network card with the correct IP for the new network it is now in.
    I ran tests such as accessing the ECP both from within the datacenter and from our primary site and I was able to access the ECP without issue and create mailboxes etc. However this morning when I came in and attempted to access the ECP with my admin account
    that has always previously worked I am now being redirected to OWA???
    I cannot think of a reason as to why this would be happening.
    Is anyone able to offer an advice?
    Kind regards

    Hi George,
    Agree with Sathish. Please use the following URL from Exchange CAS server and check the result.
    https://localhost/ecp/?ExchClientVer=15
    Here is a thread for your reference.
    ECP redirects to OWA in Exchange 2013
    http://social.technet.microsoft.com/Forums/en-US/34ed5347-90f9-4ab7-91c3-9665f8ace432/ecp-redirects-to-owa-in-exchange-2013?forum=exchangesvradminlegacy
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • How can i publish owa on exchange 2013 without ssl?

    hi
    i need connect to owa on exchange 2013 without ssl.
    but when i change config from https to http. my iis return internal error.
    can anybody tell me switch from https to https step by step on exchange 2013?
       regards

    Check out http://technet.microsoft.com/en-us/library/dn635115(v=exchg.150).aspx#OWA
    Bharat Suneja
    Exchangepedia.com | bsuneja
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Please do not send email directly to this alias. This alias is for newsgroup purposes only.

  • Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

    We are in the process of migrating from 2010 to 2013.  Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
    alex serdyukov

    Hi Alex,
    As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
    Cumulative Update 8 for Exchange Server 2013
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 ECP redirects to OWA

    Dear Collegues,
    after that I ve installed Exchange 2k13 on my win server 2012 std, I am not able to reach the EAC, when I tried to enter this URL: https://servername/ecp or https://servername/ecp?ExchClientVer=15 it redirects me always to OWA. I ve also tried this solution
    http://www.telnetport25.com/2012/11/quick-tipcreating-an-icon-on-the-desktop-for-the-exchange-2013-eac/ with no effect, also this http://lyncdude.com/2013/02/07/cannot-access-exchange-contorl-panel-ecp-in-exchange-server-2013/, but what really strange is,
    that my powershell cant recognize for ex. this syntax -  Get-owavirtualdirectory | fl or Set-owavirtualdirectory -identity “owa <Default Web site>” -FormAuthentication:$true at all.
    I am really confused with all of that Exchange 2k13 installation and configuration, from the beginning there are so many problems.
    Please can anyone help me?

    Hi,
    To enable the system mailboxes, I’d like to confirm how you disable them: delete the mailboxes from the Exchange management tool or delete the account from the ADUC.
    For more detailed steps to enable the system mailbox, you can refer to the following article:
    http://social.technet.microsoft.com/wiki/contents/articles/6874.how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010.aspx
    For the redirection issue, I recommend you check the result if you login with a admin account: check it’ OWA or EAC.
    Thanks,
    Angela Shi
    TechNet Community Support

  • How to enable S/MIME in OWA MS Exchange 2013?

    Hello,
    I can't find in ECP for MS Exchange 2013 function to enable S/MIME for OWA. Can somebody help me? I found only registry update for MS Exchange 2010 SP1 or download S/MIME function for IE7+ for MS Exchange 2010, but I am not sure if I can use it for 2013.
    Thank you,
    Pavel Hula

    As Martina has pointed out, no S/MIME support in 2013 yet!
    Rajith Enchiparambil |
    http://www.howexchangeworks.com |

  • Не работает OWA на Exchange 2013

    Установил обновление exchange 2013 SP1 после этого не могу попасть на OWA, при вводе логина и пароля получаю белый экран и в адресной строке: https://cas2.ru/owa/auth.owa, так же перестал цеплятся outlook пишет что не удается войти в систему,
    хотя с данными все в порядке.
    И на ECP не смог зайти как обычно только через: https://cas2.ru/ecp/?ExchClientVer=15 
    Что может быть? куда копать? Настройки виртуальных директорий проверил все в порядке

    Hi,
    I suggest we firstly run the UpdateCas.ps1 script.
    http://social.technet.microsoft.com/Forums/windows/en-US/d2cd5268-1319-48e3-be09-bb9ee2771fff/owa-problem
    If it still does not work, check all the BE server and see if a valid certificate is enabled for the IIS service.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Cannot write email body in OWA with Exchange 2013 SP1 CU6

    Hi,
    I have a problem with Exchange 2013 SP1 with CU6.
    All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
    The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
    Have you an idea ?
    Thanks in advance!
    Sebastien

    Hi, 
    After contacting Microsoft support, we have found the solution.
    The problem appear after we have recently install the patch described in this KB 2997209:
    https://support.microsoft.com/kb/2997209?wa=wsignin1.0
    But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
    So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
    No need to reboot, or restart IIS, it's working after that!
    @+
    Sébastien

  • OWA problem Exchange 2013 coexistence with 2010

    Hi all,
    I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
    successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
    to access OWA with a mailbox that is still on 2010 it fails with the following error:
    something went wrong
    A problem occurred while you were trying to use your mailbox.
    X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
    X-OWA-Version: 15.0.913.21
    X-FEServer: <name of 2013 server>
    X-BEServer: <name of 2013 server>
    Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
    Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
    This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
    Any help is greatly appreciated!
    Best regards
    Daniel

    Hi,
    How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
    Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
    According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
     for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Adding "Author" permission via OWA on Exchange 2013

    Hello,
    We're having issues with our Apple users: whenever they add access to a calender using Apple Calendar, it seems the account gets added to
    ResourceDelegates, even if you want to give them read-only access (thanks Apple...). This causes problems as the delegated users get invites and get confused as to why this is.
    So we want to recommend they only set calender sharing permissions using Outlook Web App... but the problem is, the
    Author permission isn't available in the drop down menu, only
    Reviewer or Editor are.
    My question is, how can I add this option to the OWA drop down list?
    Thanks for your assistance.

    Hi,
    Author permission is available under calendar
    folder permission, not calendar sharing permission.
    When we
    share calendar via Outlook, it should be like this.
    No Author permission, just like
    what you experienced in OWA. By default, these three permissions are available and we cannot add permission to this drop down menu based on my knowledge.
    Author permission is available under permission tab when you right-click calendar folder to properties in Outlook. And we can’t set calendar folder permission from OWA until now.
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Exchange 2013 OWA is not auto formatting hyperlinks when forwarding a message

    I have 2 sales managers in a company that receive sales leads via email from our website. The email is formatted in HTML with a table containing the name and email address of the customer and the url of the product they're interested in from our website.
    The managers then forward this email to the next available sales associate to contact the potential customer.
    The first sales manager uses Outlook and receives the sales lead email with active hyperlinks intact for the email address of the customer and url of the product. When you inspect the email, there is no href code in the source, so outlook is recognizing
    the types 'email address' and 'url' to make the text active. He then forwards the email to sales with active hyperlinks in the source. (they prefer this)
    The second sales manager uses OWA. when he receives the email, the email address and url are plain text (which is how its coded) so when he forwards the email to sales there are no hyperlinks.
    Is it possible to set OWA (for exchange 2013) to auto format (recognize then format) email addresses and url's from an email when forwarding it that didn't have the href code in the source to begin with? ...like Outlook does?

    Hi,
    Does this issue happen on all the OWA users or on specific user?
    Does this issue happen when sending emails by HTML format?
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange 2013 Public Folder Calendars in OWA

    Hello,
    I have a Public Folder calendar that I need to publish via OWA in Exchange 2013.  I understand that you cannot view any public folder that is not mail enabled in OWA.  If I make this specific calendar mail enabled will I be able to view the calendar
    in OWA?  I think I still have to convert this to a shared mailbox.  If that is the case, what are the best steps to perform that?

    Hi,
    Yes I agree with Ed Crowley. In Exchange 2013 Cumulative Update 1, Microsoft have allowed to display public folders. However, two major restrictions exist. First, OWA can only display modern public folders. In other words, you have to complete your
    migration to Exchange 2013 and then execute a public folder migration before OWA can be used. No access is possible to legacy public folders. Second, OWA can only display “mail public folders”, or public folders that contain “mail and post items” (as they
    are referred to by Outlook). Other folders (calendars, contacts, tasks, notes, InfoPath, and journal items) are unsupported.
    Regards,
    Santhosh,
    www.jijitechnologies.com

  • Exchange 2013 migration and Lync server

    hi guys,
    i wanna upgrade my exchange 2010 to 2013 in our company.
    but i faced with a question
    will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
    plz help me 
    thanks guys

    Hi,
    you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
    Here is a guide for enabling IM in OWA:
    http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
    Just remember to point DNS to the New Exchange 2013 server and it should be fine.
    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. Thank you! Off2work

  • Exchange 2013 ECP redirects to 2010 OWA still

    I have a new Exchange 2013 SP1 server on a 2012 R2 OS where I've installed both Mailbox and Client Access roles in an existing Exchange 2010 environment.  Initially ran into some DNS issues that caused errors installing the Client Access server, but
    I fixed those, removed Exchange 2013 and reinstalled with no errors.  In every scenario so far, trying to access the ECP redirects you to the 2010 OWA.  I have been scouring threads for hours and tried everything I've seen, but to no avail.  I
    have tried:
    1) Using the https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15 URL, which still
    redirects to the 2010 OWA
    2) Creating a new user account with all of the same rights as the domain admin but has no mailbox, which redirects to the 2010 OWA and throws an error that there is no mailbox.
    3) Setting the domain in IIS authentication settings for the ECP on both the 2013 and 2010 server.
    Does anyone have any ideas here on what to try next?

    Try creating a mailbox for the administrative account on the Exchange 2013 server or moving the existing mailbox.
    I've seen issues like you're experiencing in various forms before myself, though not exactly as you've reported.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 cros site blank page OWA/ECP

    Hello,
    I have an issue with a fresh installation of Exchange 2013 SP1.
    The are two AD site in different cities, connected by WAN link (site-to site VPN organized by Cisco ASA).
    I installed two Exchange servers in Site A (MBX1 and MBX2, both with MBX+CAS roles), and one Exchange server MBX3 in Site B (also both with MBX+CAS roles).
    Each Exchange hosts its own mailbox database (DB1, DB2, DB3 respectively), there are no DAG.
    Users spread over all databases. For example, user1 has mailbox in DB1, user2 - in DB2, user3 in DB3.
    When user1 opens OWA/ECP on CAS server MBX1 or MBX2, he successfully get into his mailbox.
    But, if user1 opens OWA/ECP on CAS server MBX3, he get blank page (no error at all).
    And vise versa:
    When user3 opens OWA/ECP on CAS server MBX3, he successfully get into his mailbox.
    But, if user3 opens OWA/ECP on CAS server MBX1 or MBX2, he get blank page (no error at all).
    I know, that Exchange 2013 is able to proxy request cross site.
    Where are no custom redirects set on IIS.
    Also I check IIS (Back End Site) for right certificate.
    There are no error in Windows Event log and IIS event Log.
    All ports are allowed between sites.
    Everything looks good.
    What I did wrong? May be I need to enable cross-site OWA proxy in Exchange somewhere?
    Or it is a CISCO ASA misconfiguration?
    Any help would be appreciated!
    Thank You!
    Pavel

    Hi,
    Firstly, I’d like to confirm if all your Exchange server are internet facing servers.
    We can try to clear the Forms based authentication on the non-internet facing server.
    And here is a similar thread you can refer to:
    http://social.technet.microsoft.com/Forums/exchange/en-US/85983a21-3922-46f4-b64a-d53c0a2271a7/issues-with-crosssite-cas-redirect-of-owa-users?forum=exchange2010
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

Maybe you are looking for