Exchange 2013 and OWA and Out of Office

I can't do shit... can't even fucking log in to ECP now ffs.....
done with this shit.....
Off to be a fishing guide...... I'm not the Exchange admin yet they change something and I'm forced to figure it out. PFFT

I've had several reports and it seems to be universal now. If anyone logs in to Outlook Web Access to set their Out of Office (via the gear icon in the top right) it boots them out to the login screen. This was confirmed to be working normally as recently as 2-3 weeks ago.
- It is Exchange 2013
- It doesn't matter if it's Chrome or IE
- It doesn't matter if it's their own email account, or a secondary one they may be responsible for.
Any ideas?
This topic first appeared in the Spiceworks Community

Similar Messages

Exchange 2013 SP1 -OWA and ECP login authentication

Coexisting with Exchange 2007 in the same Org.
Just been through a nightmare where I changed the authentication type from Basic and Forms to Windows Integrated Authentication through the EAC for OWA and ECP. It broke them completely. Three hours later after rebuilding the two virtual directories I have
it working.
So I learnt about the backend process for both ECP and OWA and realised I have to have the authentication types the same in front and back end.
1. Is there a way to set authentication for both components at the same time? (that's a stoopid design)
2. So now I have integrated authentication- but I cannot login as someone else unless of course I login to windows as that other person. Which authentication do I need to add to allow prompting ifor other credentials (or is this not possible)?
3. Set-ECPvirtualdirectory can set the backend but get-ecpvirtualdirectory can not. It was really difficult to see the two sections had different authentication settings. Is there a way to see them?

I would recommend Basic Authentication and set Group Policy to add Exchange URLs to Trusted sites and modify IE settings to "Automatic login using current username/password" option for trusted settings.
This way Single-Signon would work for domain joined systems and Basic authentication would prompt for any unsuccessful logins
However, from the best practices perspective, I would recommend Form based authentication, unless there are business reasons for not doing it this way.
- Sarvesh Goel - Enterprise Messaging Administrator

Exchange 2013 issue / OWA time-out and WiFi/Cell problem.

Hi everybody,
I'm having some issues with an Exchange 2013 server.
When some users try to logon to the OWA page it keeps loading the page and ends with a time-out.
This only applies to 6 or 7 users, other users can login and open the page.
I tried to replace the signed certificate to solve this problem, and did a online analyzer check, most tests come out good.
I can't seem to find the source of this problem.
There are also multiple users that are having trouble to receive e-mail through the wifi on phones and tablets at home but when they switch to 3g it works fine.
You might need more information, just ask.. i don't know where to search anymore.
I tried inheritance on the AD, disabled SSL in the IIS, restarted the server, replaced the signed cert. etc.
Update:
I set the selfsigned cert in the IIS default web page,, to check if it responds to the certificate and it does, so the issue doesn't come from the certificate.
This issue probably came up after CU1, and i've read something about healthboxes..
I'm going to install CU6 and hope for good result.
Kind regards,
Tim

I've installed CU6, only one of the six users have gained access to OWA or ECP.
Al the other users won't get a logon screen, just a blank page.
So there is no option to insert a username or password to login, the page keeps loading and ends with "the page cannot be displayed"
But on my working spot i can open owa or ecp without any issues.
I've recreated the virtual directory for ECP and OWA with powershell, and checked the certificate.
I checked if the same certificate was connected to the back-end port 444, and this is set correct.
I even reconnected the cert on 444 with the following.
Open the Command Prompt
Run-
netsh http show sslcert
This will show the certs, copy and paste this information into notepad. Under IP:port : 127.0.0.1:443, note the certificate hash and application ID.
Run this command- (Yes, I know there is no :444 listed in the output from the earlier command.)
netsh http delete sslcert ipport=0.0.0.0:444
Run this command. Replace certhas with the certificate hash and appid with the application ID you saved in notepad.
netsh http add sslcert ipport=0.0.0.0:444 certhash=123123123123123 appid="{123123123123-1231231235}"
I used powershell to set the login authentication,
et-Owavirtualdirectory -identity "YourMailBoxServerName\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
set-Owavirtualdirectory -identity "YourCASserverName\owa (Default Web Site)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
and iisreset /noforce
I unchecked the "require SSL" on the default website and left it enabled on the owa and ecp etc.
Checked if HTTP over Proxy is installed, but this one is need to install exchange 2013.
I've checked all ECP/OWA directories in in the IIS, the directories point to the Exchange V15 folders, this should be correct.
Something is really broken, i really can use the help..
I'm going to try to install Exchange 2013 SP1, but i don't know if this one is needed when CU6 has been installed.
The strange thing is, it seem to be location based, not user based.
I can login perfectly, but when i try this at one of the employees, it ends up blank.
When i try to connect on a location dat does not work, at the exact time i press the enter-key to open the page, the eventviewer logs the following:
Event 4634 - An account was logged off.
For the issue on the smartphones and tablets, everything worked fine a few months ago, and happens to users on different ISP connections.
I already checked the inheritance settings on the users in the AD.
Kind regards,
Tim

Users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply

Hi All,
Please help me.
I have an issue where users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply. But they are can set Out Of Office automatic reply from OWA. My exchange server is Ms Exchange 2010.
The test E-mail AutoConfiguration failed with this error:
Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml starting
GetLastError=12175; httpStatus=0.
Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
GetLastError=12007; httpStatus=0.
Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
Local autodiscover for mydomain.com starting
Local autodiscover for mydomain.com Failed (0x8004010F)
Redirect check to http://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
Srv Record lookup for http://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x80072EE7)
Srv Record lookup for mydomain.com starting
Srv Record lookup for mydomain.com Failed (0x8004010F)
Any idea?
Thanks,
Pieter

OK.
Please follow this step.
1. As you said you are in coexistence step , so for now all endpoint already point to Exchange 2010 right?
2. Check legacy owa redirect that you already configure
3. In Exchange 2010 , Make sure that you already configure "Autodiscoverinternaluri" by this command set-clientaccessserver -identity "servername" -autodiscoverinternaluri
https://autodiscover.domain.com/autodiscover/autodiscover.xml. and don't forget to create autodiscover record in DNS
4. in Exchange 2010 , Make sure that you already configure "EWS" path by this command set-webservicesvertualdirectory -identity "XXX\Default web site name" -internalurl
https://yourinternalurl/EWS/Exchange.asmx -externalurl https://yourexternalurl/EWS/Exchange.asmx
5. don't forget to replicate freebusy from Exchange 2003 to Excahnge 2010 via public folder.
You error look like client cannot get autodiscover process please check it again.

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 2010 and 2013, Coexisting "OWA" and "ActiveSync" 1 Public IP.

Hello Everyone.
I find myself in a bit of a dilemma and in a desperate need for some well educated help.
Scenario: Server 1 (Small Business Server 2011 Standard) with Exchange 2010
Server 2 (Server 2012 Standard) with Exchange 2013
1 Static Public IP Address
This used to be one domain that split into two separate entities that are still occupying the same office space.
All port forwarding is currently pointing to the SBS and everything there is working properly. I setup a new receive connector on the SBS that is forwarding the mail for domain 2 to the "Exchange 2013" server and mail flow in and out is working
100%.
The problem lies with OWA and ActiveSync.
I tried changing the SSL port in IIS on Server 2 from 443 to 1443 and forwarded those ports to server 2 from the router, then OWA works externally, but for some reason the clients on the local network can't connect anymore, so I had to drop that idea after
being unable to find the cause.
The only other thing I can think to try, is to setup HTTP redirection on the SBS IIS or adding the mail.domain2.com in the SBS DNS or something.
I have searched for hours but can't find anything specific to my scenario. Any and all help will be greatly appreciated.
Any and all help will be greatly appreciated.
Thank you in advance.
Hentie Loots

You need to use ARR.
http://www.iis.net/downloads/microsoft/application-request-routing
It is essentially like a basic proxy service. So the SBS would receive an SSL connection for mail.domain2.com and instead of it failing it would be redirected internally to the second server.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Exchange Server 2013 CU3 OWA and TMG logoff process.

Hi folks,
I just wanted to quickly check if the intent behind Greg Taylor's deliberate choice of words in
this article are still current, or if we can expect to have a resolution in the SP1 timeframe?
Specifically, I'm referring to Greg's CU1 update early-ish in the article where he states:
"The release of Exchange 2013 RTM CU1 changed the way OWA logoff works, such that the TMG change recommended in this post no longer applies. At the current time there is no way to catch and force logoff at TMG when TMG is generating the form,
instead users should be educated to close their browser window (as the pop-up tells them when they click Sign Out from within OWA).".
Given the "current time" of his update was CU1, is there any update as to whether something more meaningful than the pop-up is going to be put in place? While it's more symbolic than anything else, it's off-putting to
the users to still see their e-mail panel after having chosen to "log off".
Cheers,
Lain

Hi,
Thanks for your update.
Generally, the official clarification can be released after the SP update’s release. We can keep an eye on the Exchange Teamblog to see if there are any new updates for your question.
Regards,
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

Winmail.dat attachments from Exchange 2013 on premi and Hosted Office 365 set up.

Hello TechNet,
I have an on going situation with winmail.dat attachments. I currently have a ticket open with Microsoft, but I want to see if anyone has personal experience with this. Here is the rundown.
We have migrated from an Exchange 2007 server to Exchange 2013 for the migration to Office 365. We also have a hosted Office 365 server with half of our mailboxes in the cloud and half of them on the Exchange 2013 on premise server.
The current settings for TNEFEnabled:
On Premise: False
Hosted: False
Whenever a internal email with a calendar invite(exchange calendar, go to meeting) goes out to any external domain the recipients receive winmail.dat.
When settings for TNEFEnabled On Premise and Hosted are set to true both calendar invites and PDF, Excel attachments etc the recipients receive winmail.dat.
When speaking with Microsoft about this issue. The representative was watching me through a LogMeIn session as I set both TNEFEnabled false on both on Premise and Hosted.
This is really frustrating as many employees depend on this to be fully functional, and to be honest am tired of dealing with this.
I need help.
-Ben

I am having the same issue.
Luckily I have only migrated my own mailbox to office365.
Tried both true and false TNEFEnabled on both onpremise and office365 via powershell and confirmed that both have been applied.
If I send the email as a plain text then the attachment works ok. If I send it as HTML then I get winmail.dat.
The above KB doesnt really help me, sending plain text emails is like going back to the dark ages!
I am sending from outlook to outlook (I send from my external email address, to my work email address and visa-versa)
If someone with an onpremise mailbox sends me an email, the attachment works ok.
If someone sends me an attachment via hotmail, the attachment works ok.
It seems to only effect emails I send to myself through outlook, i am sending it through a POP3 account to our onpremise exchange 2010 which forwards the email to office365

Exchange 2013 Malware Filter and ScanningProcess.exe

Hi all...
We have an Exchange 2013 environment with an external Mail Security Appliance (FortiMail), because of this our Malware Filter was disabled, but the process ScanningProcess.exe (Microsoft Filtering Server Scanning Process) are still running and
sometimes hangs the CPU for several minutes scanning attachments.
Is there a method to disable the process and avoid the CPU high use?
(all servers have Exchange 2013 CU7)

Hi Nico,
According to the description, I know it doesn't send to Mailbox-B a Alert Text as expected, just like following problem:
After the appaling result, i made an additional test. I tested to send internal Malware mails from Mailbox-A to Mailbox-B. The Mail was send from Mailbox-A with no interruption and only on the receive Mailbox-B the attachment was deleted.
I suggest double check this issue on OWA to verify whether Mailbox-B have received the Alert Text.
If in OWA everything is OK, it seems an issue on the Outlook client side.
If this issue exists in OWA, I suggest get the Malware Policy in details to check whethe it specifies some limitation.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 with CAS and HLB in different sites

Hello...
Coming son, we'll deploy Exchange 2013 with high availability in all roles. The CAS and Hub Transport roles, are with a HLB; and the Mailbox with DAG. The infrastructure is formed by:
Citi1:
- AD Site 1
- 1 Hardware Load Balance: HLB01 to load balance the CAS and Hub Transport of Exc01 and Exc02
- 2 Exchange: Exc01 and Exc02 multiroles Exchange Server 2013
- 1 DAG for Citi1 databases: conformed by the Exc01 and Exc02
Citi2:
- AD Site 2
- 1 Hardware Load Balance: HLB02 to load balance the CAS and Hub Transport of Exc03 and Exc04
- 2 Exchange: Exc03 and Exc04 multiroles Exchange Server 2013
- 1 DAG for Citi2 databases: conformed by the Exc03 and Exc04
The Active Directory is one forest with one domain. The Domain Controllers are Windows Server 2012. The Site1 and Site 2 are connected by a WAN link. The accepted domain is domain.com. The smtp address is @domain.com
How to make that users of Citi1 always connect throught the HLB01 to their mailboxes; and the users of Citi2 always connect throught the HLB02 to their mailboxes if the autodiscover.domain.com is the same for all users?
I have not found documentation about
this architecture. Please help me.
Thank you very much.
Best regards, Javier Uribe

Hi javier,
In this issue, I guess you can try to use site affinity for the Autodiscover service for intranet-based traffic.
To use site affinity, you specify which Active Directory sites are preferred for clients to connect to a particular Autodiscover service
instance.
You configure site affinity by using the
Set-ClientAccessServer cmdlet. This cmdlet lets you specify the preferred Active Directory sites for connecting to the Autodiscover service on a specific Client Access server. After you configure site affinity for the Autodiscover service,
the client will connect to the Autodiscover service as you specified.
According to your needs, you might want to allow users in the site1 to use site1, users in site2 to use site2 to access the Autodiscover Service.
You can configure site scope for Client Access servers in the Site1 by following command.
Set-ClientAccessServer -Identity "site1-cas" -AutodiscoverServiceInternalURI "https://internal.domain.com/autodiscover/autodiscover.xml" –AutodiscoverServiceSiteScope “site1”
The Command for Site2.
Set-ClientAccessServer -Identity "site2-cas" -AutodiscoverServiceInternalURI "https://internal.domain.com/autodiscover/autodiscover.xml" –AutodiscoverServiceSiteScope “site2”
Hope it helps
Best regards

Exchange 2013 CU1 UM and Avaya SM R6

Hello! I have a problem integrating Avaya and Exchange 2013 CU1 UM.
In 2010 environment it works perfectly fine, however with Exchange 2013 I was unable to make it work.
I was looking into the packets sent by 2010 and 2013, the only difference is in 302 reply. Exchange 2010 sends
extension@ip:port as the Contact URI while Exchange 2013 sends
extension@fqdn:port
Avaya doesn't seem to recognize the format and instead of connecting to the specified within the contact field service just keeps querying TCP 5060 (Call Router Service).
Is there any way to force Exchange to use IP within the contact field instead of FQDN?
Pointing SIP Entity to 5065/5067 directly is not an option for obvious reasons well covered here on the forums.

To get this functioning u must do the following! The CM will handle the "302 moved" FQDN request with this setup. CM 5.2.1 with 6.2 SM.
1. Lockdown the CAS server worker port to 5065. A restart of the UM service every couple of days will take care of this because it defaults to 5065.
2. CM hunt group set "voice mail handle" to a name. EX: sipms
3. SM create SIP entity for CAS server with entity link SM TCP 5060 -> CAS TCP 5060
4. SM Create SIP entity for each MBX server and port needed.
EX: Entity MBX-1-5062 IP 10.10.10.1 with entity link SM TCP 5062 -> MBX-1-5062 TCP 5062
Entity MBX-1-5065 IP 10.10.10.1 with entity link SM TCP 5060 -> MBX-1-5065 TCP 5065
Note: IF the SM is not listening on 5060 for the 5065 link MWI and "play on phone" will fail. This is why you need to lockdown the worker port to 5065.
5. SM Create routing policies for each entity.
6. SM create regular expressions for the CAS server and each of the MBX server entities and assign to the appropriate routing policy. The examples below are for one CAS server and one MBX server. There are one CAS and six MBX servers in my environment,
so I have 13 routing policies and 13 reg expressions.
EX: "sip:sipms@example\.org" asign to CAS policy.
"sip:sipms@mbx1@example\.org:5062.*" assign to MBX-1-5062 policy.
"sip:sipms@mbx1@example\.org:5065.*" assign to MBX-1-5065 policy.
Hopefully this is enough to get you going. I would have killed to have this information when I started on my quest!

Exchange 2013 Health mailbox and Journaling

Hi All,
We have recently build green field Exchange 2013 environment with standard journaling. Now we are seen that as per journal capture process it captures health mailboxes emails as well.
As we all know we will use options ignore/disable health mailboxes emails
Method 1 : Dynamic DL
Method 2 : Use global override
http://support.microsoft.com/kb/2823959/en-us
My questions
if go for Method 2
1. What will be the challenge will face in environment
2. Is Microsoft recommendation is go with Method 2 ( I am still looking for clarification even though I mentioned in MS KB)
Thanks
Vishal Saxena

Hi Vishal,
1. As it says in KB some server monitoring applications may not correctly monitor transport server components if you have any. Basically you will lose the ability to detect any condition when server stop accepting mails automatically.
2. You can definitely go with method 2 considering you have another way to monitor transport components and this failure detection.
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 Licencing Terms and Agreements

When you install Exchange 2013 you have to agree to the terms and conditions with the /IAcceptExchangeServerLicenceTerms
If you dont setup.exe points you to a URL
The the URL is http://go.microsoft.com/fwlink/p/?LinkId=150127
However when you go to the link there is only an option for Exchange 2007 and 2010 ? Where’s the version selection for Exchange 2013?
And How has the rest of the world been accepting these license terms for Exchange 2013?
I need our legal department to give me (the technical guy) approval that I can accept these terms on behalf of the organization and without the terms I technically cannot go ahead..

Hi Riccardo,
For licensing related question, it's recommended to consult the local supplier for more accurate information,
you may
get effective solution timely:
http://support.microsoft.com/gp/customer-service-phone-numbers/en-us
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

2 exchange 2013 multirole server and 1 addess for Outlook Anywhere. How to?

Hello everybody.
I'm coming to you with a question about my new Exchange 2013 infrastructure.
I have 2 Exchange 2013 SP1 servers. Both are multirole (CAS + MBX). My servers are Server12 and Server13.
I created a DAG which IP adderss is 192.168.3.30 (Servers IP are 3.31 and 3.32). Everything's working fine.
For CAS High Availability, I followed this thread : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
On my firewall, I use NAT to send https flow from my public IP address (mail.domain.fr, external domain
published on internet) to point to mail.domain.org (internal domain, non published on Internet). The mail.domain.org alias is my record defined in my internal DNS to
point to my 2 multirole server, as shown in the tutorial above.
I encounter a problem with external outlook anywhere. My problem comes with Outlook Anywhere which is not working fine when I redirect https flow to my cluster IP address (192.168.3.30) (DAG's address, corresponding to my servers). If I do the same redirection,
but pointing to only one of my servers, it's working fine. In Exchange, external outlook Anywhere directory points to mail.domain.fr
But anyway, if this servers goes down, I have to change manually the NAT on my firewall. And I don't want to :).
How can I do ? Can I do something without a physical load-balancer?
Thanks

You cannot point Outlook Anywhere to your DAG cluster IP address. It must be pointed to the actual IP address of either server.
For no extra cost DNS round robin is the best you will get, but it does have some drawbacks as it may give the IP address of a server you have taken down for maintenance or the server has an issue.
You could look to implement a load balancer but again if you are doing this for high availability then you want more than one load balancer in the cluster - otherwise you've just moved your single point of failure.
Having your existing NAT and just remembering to update it to point to the other server during maintenance may suit your needs for now.
If you can go into more detail about what the high availability your business is looking to achieve and the budget we can suggest the best method to meet those needs for the price point.
Have a great day
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Exchange 2013 Transport Rules and Exchange 2007 Decommissioning

Hello,
I recently migrated from Exchange 2010 to Exchange 2013, I do have a few traces of Exchange 2007 in the Active Directory that I would like to completely remove. The Exchange 2007 server failed earlier and wasn't decommissioned properly. I read a few articles
on how to completely remove it from AD, I am still concerned to make the changes in "ADSI Edit".
Here is the error message I receive when creating transport rules in Exchange 2013:
"You are about to create a rule in an organization where Hub Transport servers running Exchange Server 2007
exist. To ensure the rule is applied consistently across all Hub Transport servers in the organization, you must create an equivalent rule from the Exchange Management Console on an Exchange 2007 server."
I also noticed that the version of the rules remain Version: 14.0.0.0 for any new rules that I am creating in Exchange 2013.
I would really appreciate if someone can provide their views and the best practices to remove the traces of Exchange 2007 in AD.

Hi Sathish,
How about the result after using ADSI Edit ?
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 and OWA and Out of Office

Similar Messages

Maybe you are looking for