Asked by:
OWA 2013 publish through TMG 2010 logoff URL problem

Question
-
Hi all,
The problem is the OWA publishing over the Internet via TMG. TMG is not able to Catch the OWA LogOff URL page. So it will instead receive the "Close all your Browser Settings.." and no log out from OWA.
Does anyone get that "Real LogOut" fixed via TMG.
Wednesday, October 1, 2014 1:10 PM
All replies
-
Hi,
Have you tried to change the default value of Published server logoff URL from ?Cmd=logoff to /owa/logoff.owa?
For more information, please check the following blog.
Publishing Exchange Server 2013 using TMG
Best Regards,
Joyce
Thursday, October 2, 2014 12:37 AMModerator -
Dear Joyce,
Yes. I already follow that but still can't log out successfully. You can refer to the following thread that posted by others and it still remain unresolved.
Wednesday, October 8, 2014 4:17 AM -
Hi there,
Can you please confirm the build version of Exchange 2013 you are using?
Based on your answers to Joyce, I assume you have Exchange 2013 RTM CU1 or above ?
If thats the case, modifying the log off URL in application tab might not help and I am afraid that, currently we DO NOT have a way to catch the log off URL from TMG.
Note: 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).
For full reading you can refer this blog from a senior MSFT guy
Saturday, October 11, 2014 4:15 AM -
Hello folks, i have been experiencing this same problem. My exchange server 2013 is patched to current releases as of Sept 2015. This has been driving me crazy! ANY solutions out there?Friday, September 18, 2015 7:12 PM
-
This worked for me:
On any TMG publishing rules, on the Application Settings tab, modify the "Published server logoff URL" to be "owa/auth/signout.aspx".
Then, on any CAS servers, navigate to and open
%ExchangeInstallPath%\Frontend\HttpProxy\OWA\web.config
and delete this line:
<add key="LogonSettings.SignOutKind" value="LegacyLogOff" />
Thirdly, on any mailbox servers, navigate to these files
%ExchangeInstallPath%\ClientAccess\OWA\web.config
%ExchangeInstallPath%\ClientAccess\ECP\web.config
and delete the same line from both files.
Lastly, do an IISreset on each affected server.
Viola.
Wednesday, April 20, 2016 3:54 PM