OWA/ECP Custom Theme Exchange 2013

Hello,
I've read numerous posts on customizing OWA themes and currently have them in place in my 2010 Exchange environment. I've also used them in 2007 Exchange infrastructures. I've been trying to roll out a similar design in my lab before we go live
with our 2013 migration but I have a few questions. I've read the tech net article (http://technet.microsoft.com/en-us/library/bb201700%28v=exchg.150%29.aspx)
and found no issues with it. Everything works as it should. However, in my current 2010 environment, the paths to the image files are slightly different than they are in 2013.
The biggest problem is that I have to place the headerbgmain.png and headerbgright.png in the ECP folder (Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\version\Themes\Default) in addition to the OWA folder (Program Files\Microsoft\Exchange
Server\V14\ClientAccess\Owa\version\themes\default). If I don't do this, the header and the OWA logo won't match when switching between OWA and ECP. So this has worked since the 2010 release of Exchange. Not certain if this is supported or
not.
Moving forward, how do I ensure that the two image files get propogated between OWA and ECP without a disconnect as the file path no longer exists for ECP and there is no documentation on how to go about doing this? I've got the OWA part working
without any issues in 2010. Just not certain how to go about it in my 2013 lab and would like to know before I can go ahead with the migration. Thanks for any help!

Hi,
Please refer to the following article :
How to Customize the Outlook Web App (OWA)Sign-In page in Exchange 2013
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled
by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Niko Cheng
TechNet Community Support

Similar Messages

OWA :( something went wromg -exchange 2013

hi
I have another fresh exchange 2013
i cant login to owa with error : :) something went wrong
It seems authentication issue
Ecp is working with no issues .
Identity : EXCHCASSRV1\owa (Default Web Site)
Name : owa (Default Web Site)
InternalUrl : https://exchcassrv1.corp.net/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHCASSRV2\owa (Default Web Site)
Name : owa (Default Web Site)
InternalUrl : https://exchcassrv2.corp.net/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHMBXSRV1\owa (Exchange Back End)
Name : owa (Exchange Back End)
InternalUrl :
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication : False
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHMBXSRV2\owa (Exchange Back End)
Name : owa (Exchange Back End)
InternalUrl :
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication : False
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
[PS] C:\Windows\system32>^A
need help
MCP MCSA MCSE MCT MCTS CCNA

Hi,
Since your ECP can work fine, please run the following command and post the results here:
Get-EcpVirtualDirectory | FL Identity,*Authentication*,*URL*
Please note to set the Authentication method by using EMS or EAC instead of IIS manager. Just restart IIS service after changing any authentication settings in Exchange.
Regards,
Winnie Liang
TechNet Community Support
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL Identity,*Authenticat
Identity                      : EXCHCASSRV1\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication        : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv1/ecp
ExternalUrl                   :
https://exchcassrv1/ecp
Identity                      : EXCHCASSRV2\ecp (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv2.corp.net/ecp
ExternalUrl                   :
[PS] C:\Windows\system32>
Also find the same from EXCHCASSRV2:
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL Identity,*Authentication*,*URL*
Identity                      : EXCHCASSRV1\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv1/ecp
ExternalUrl                   :
https://exchcassrv1/ecp
Identity                      : EXCHCASSRV2\ecp (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv2.corp.net/ecp
ExternalUrl                   :
[PS] C:\Windows\system32>
MCP MCSA MCSE MCT MCTS CCNA

Missing ECP directory in Exchange 2013/2010

Hi Folks,
I have an exchange 2013 and 2010 server running in a domain.
I was trying to log into the Exchange Admin Centre on Exchange 2013. After typing the credentials the page just refreshed and set the prompt back in the password field.
Doing a Get-ECPVirtualDirectory results in the message "An IIS directory entry couldn't be created. The error message is Access is denied", Category Info: Not Installed (myserver\ecp (Default Web Site):ADObjectId). FSComputername:(name of exchange
2010 server).
I am unable to either create or remove the ECP directory (although it claims one exists). Opening the exchange management console on my 2010 server shows OWA is set up, but the ECP entry is blank.
If I try and login to OWA I get the login screen, but after entering credentials I just get HTTP 400 bad request.
In IIS on my 2013 server, there is an ecp directory with just a web.config and auth directory under the default website, there is also an ecp directory (containing contents) under the 'Exchange Back End' site.
Does anyone know how to go about re-creating the ECP directory etc.
Regards
Andy

Hi Andy
Ensure that Microsoft Exchange Security Groups and Exchange Trusted Subsystem group should be a member of the local admins and restart the server
Steps:
Launch IIS Manager Navigate to -> Web Sites -> Default Web Site Right Click on Default Web Site and choose Permissions Add Exchange Trusted Subsystem and grant Full Control Restart IIS Restart the server
If none of the above works then try the following
First remove the affected one
Get-ECPVirtualDirectory | Remove-ECpvirtualDirectory
Then create a new one by following below
http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
Remember to 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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

OWA SSO issues in Exchange 2013 - 2007 co-existence

This may not be possible. For a multitude of reasons the client needs OWA authentication of Windows Integrated and Basic. As a result I''ve got a double prompt for users still on 2007 for OWA externally.
Do you have to use Forms Based Authentication to get SSO to work? Is it possible to enable FBA as well as basic and Windows auth?

FBA is required on the source and destination, yes. You would need to enable that and not use Basic or Windows Auth.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox is located within the local AD site on an Exchange 2007 Mailbox server.
CAS2013 will initiate a single sign-on silent redirect (assumes FBA is enabled on source and target) to
legacy.contoso.com. CAS2007 will then facilitate the request and retrieve the necessary data from the Exchange 2007 Mailbox server.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Use Exchange 2010 OWA Login Page with Exchange 2013

We are planning on upgrading our exchange server from 2010 to 2013. We want to keep 2010 OWA login page with this upgrade. Partly due to educating users to new OWA interface and no plan to upgrade to office 2013 anytime soon.
Questions:
1. Do you or do you not recommend?
2. Is it possible?
3. How to keep 2010 OWA login page during and after migration to 2013 (instructions)?
Thank you!

Hi, EthenLEC
I agree with Andy David.
For additional information, we can change OWA 2013 back to OWA 2010 interface to use light version by the following steps.
Log in to OWA 2013.
Once logged in, click on the settings gear in the upper right corner, choose
Display Settings.
From the Display settings menu, choose Outlook Web App version, then check the box to use the light version.
Sign out of OWA and sign back in. Now it has the OWA 2013 light version.
Best Regards.

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 |

Exchange 2013 Public Folder Migration Problem

Hi All,
Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
I have followed the guide for public folder migration here
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders. Administrators can create them
fine from the ECP - just not from outlook.
It also appears some users cannot see some folders that they have permissions to.
Can anyone assist with some ideas to resolve ?
Thanks.

Question?
Are you able to create the Folder in OWA?
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
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.
it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
My Bad, that's what I was trying to say.
Testing the same thing in the LAB, should have some update tomorrow morning.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
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.

SBS 2008 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

Migrating a customer to Exchange 2013 from SBS 2008.
Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
The customer only has a single external IP address...
So what do I do for this external DNS of legacy.customer.com?

Hi Allister -
You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
is inside AD, Ex2013 will find it.
These are the URLs you need to change in 2007/2010
ClientAccessServer
webservicesvirtualdirectory
oabvirtualdirectory
owavirtualdirectory
ecpvirtualdirectory
ActiveSyncVirtualDirectory
AutodiscoverVirtualDirectory You can read more on how to set these here:
http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
A wise man is a fool, with a good memory.

Exchange 2013 CU1 Outlook Web App LogOff with Basic or Windows Integrated Authentication

Hi all,
Exchange 2013 CU1 has a new OWA LogOff behaviour when Basic or Windows Integrated Authentication is configured. When clicking the LogOff Button you receive the message "Close All your Browser Windows.." but OWA does not sign out. This is not the
case when using Formbased Authentication...
The problem in our case is the OWA publishing over the Internet via TMG. When publishing via TMG, only Basic and NTLM authentication is supported. This means you have to change the Authentication for the OWA Virtual Directory to basic or Windows Integrated.
OK so far, now we can use the TMG Authentication Form. but... TMG is not able to Catch the OWA LogOff. So we will still receive "Close all your Browser Settings.." and no log out from OWA.
It is a known issue that TMG cannot catch the OWA Logoff with the Exchange 2013 CU1 Release..So my Question:
Does anyone get that "Real LogOut" fixed via TMG or directly on the CAS Server for Exchange 2013 CU1?
I know another possibility is to activate Form Based Authentication on the CAS Servers and external users directly authenticate against the CAS Server without pre-authentication at TMG Level, but this of course does not provide the highest security
we can have.

Hi SLShare,
As far as I know, if there is no TMG involved, with Exchange 2013 when the user signs out of mail, the authentication tokens are cleared and the user will be presented with the
Login Screen. There will not be a need to click on "Close Window" or any other pop ups that may appear.
Therefore, you may ask the TMG forum about this question and see whether there are still some other workaround we can temporary bypass this issue. For your convenience:
Forefront TMG and ISA Server Forum - TechNet - Microsoft
http://social.technet.microsoft.com/Forums/forefront/en-US/home?forum=Forefrontedgegeneral
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 SP1 & Custom OWA Theme

On Friday of last week we updated from Exchange 2013 CU2 to Exchange 2013 SP1. Since updating our custom OWA theme no longer works. We configured it according to the following guide:
http://technet.microsoft.com/en-us/library/bb201700(v=exchg.150).aspx
The theme we customized was stored in the following location:
\Client Access\OWA\version\Owa2\resources\themes\"title of our theme"
Themes no longer appear to be stored in this location and I am uncertain as to where they have moved and how to apply them. Has anyone else run into this issue?

Hi,
Can we try to re-importing the theme again?
Thanks
Mavis
Mavis Huang
TechNet Community Support

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

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

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 ECP Login fails HTTP 404 Requested URL: /owa/auth/logon.aspx

Hi,
One of our Exchange servers stopped allowing access to OWA and ECP. I have now managed to get OWA working but ECP is still failing. When connecting to ECP using https://servername/ecp/ it asks me for my username and password. After hitting enter it shows
me an error page:
Server Error in '/owa' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /owa/auth/logon.aspx
URL in the address bar while on this screen: https://exchangeserver:444/owa/auth/logon.aspx?url=https://exchangeservera:444/ecp/&reason=0
Question: When the URL points to servername:444/owa/auth/logon.aspx - Is it trying to find the logon.aspx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth? There is no such file in that directory?
I have removed and recreated the ECP and OWA virtual directories several times.
I am trying to login using a domain administrator account.
Thanks,

Hi,
Is there any Exchange server 2010 coexistence with your Exchange 2013 server? If it is, please try the URL
https://CAS15-NA/ecp?ExchClientVer=15 to access ECP.
Also run the following to check your OWA and ECP virtual directories:
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
And make sure the Basic and Forms authentications are enabled in
Default Web Site and Ntlm, WindowsIntegrated
authentication methods are enabled in
Exchange Back End. Then restart IIS service by running
iisreset /noforce from a command prompt window.
If the issue persists, please collect any event logs or IIS logs for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 OWA/ECP HTTP 500 Internal Server Error

So I know there are a lot of these threads, so I'll list what I've done and what I've tried so far.
The setup is a pair of multirole servers with a DAG. We have a root domain and sub domain.
I've created 4 databases associated with the DAG, I successfully removed the default database on the 2nd mail server, then migrated the arbitration/system/discovery etc... mailboxes to one of the DAG databases. I then removed the 1st mail server's default
database after killing it's healthmailbox. Rebooted the pair of servers and after that the ECP/OWA were inaccessible.
To run tests I installed .NET 3.5 SP1 so I could run the ExBPA which really didn't get me anywhere.
I can access the logon screen for both, but when I enter my username and password, I get the http 500 internal server error.
I have used: Get-OwaVirtualDirectory -Server <server name> | fl *auth*
To verify that basic and forms based auth are enabled, and they are.
I've verified all services have started.
I've tried to remove and re-add the app pools and the ecp virtual directories.
http://social.technet.microsoft.com/Forums/ie/en-US/bb148ccb-a75e-4571-bfc7-76950f8e638e/exchange-2013-cu2-cant-access-ecp-unexpected-error-500?forum=exchangesvrgeneral
I've tried to use ADSI Edit to purge the Canary Data.
http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclients
I've tried to run test-ecpconnectivity but stated that the test user wasn't available.
So I tried to use the powershell script to create a new test user, but it doesn't seem to work either I think it's related to the exchange machine not being a member of the root domain, but not sure on that one.
I seem to be able to manage everything with command-line still. Create and remove mailboxes etc.
As far as errors/warnings go exchange wise I get an ASP.NET 4.0 warning Event ID 1309 stating that an unhandled exception occurred, which seems to coincide with the logon attempt. I'm sure this has something to do with it, but not real sure what yet.
Nothing I can see within the logon attempt from IIS or anything else really.
I think that's about all I have.

Hi,
Please check on the Application Pools to view whether OWA and ECP Application Pool is running on .NET Framework v4.0. It maybe the incompletely installation of Framework that causes this error.
If so, We can try to run the following command as Administrator:
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
Or change the MSExchangeECPAppPool from .NET Framework from v4.0 to v2.0. Then restart IIS to have a try.
Regards,
Winnie Liang
TechNet Community Support

OWA/ECP Custom Theme Exchange 2013

Similar Messages

Maybe you are looking for