Solved

Exchange 2007 Outlook Web Access Light timeout

Posted on 2009-07-12
14
768 Views
Last Modified: 2012-08-13
I need to adjust the timeout on my outlook web access for the light mode.  It is timing out at 5-10 minutes.
I have created 2 registry key's in HKLM\System\CurrentControlSet\Services\MSEchange OWA

They are PublicClientTimeout (set at 60), and TrustedClientTimeout (Set at 240).  I have restarted IIS and W3SVC, and there's been no change.

Is there a regedit I am missing?

Is there anything else
0
Comment
Question by:ksuchewie
  • 6
  • 5
  • 2
14 Comments
 
LVL 23

Expert Comment

by:debuggerau
Comment Utility
not sure about regedit yet, I goto IIS management and change the timeout on the web server firstly..

untitled.JPG
0
 

Author Comment

by:ksuchewie
Comment Utility
That does not seem to make a difference for the Light version.  I still get the message, "Message automatically saved
Click here to recover the last item you were working on  
 The item you were working on was automatically saved to the Drafts folder because no action occurred for an extended period of time. You may be required to log on again. "

I set it for 60 minutes.  I did reset IIS.  It timed out after 5 minutes.
 

sessionstate.JPG
0
 
LVL 23

Expert Comment

by:debuggerau
Comment Utility
Found these links:
http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1231470_mem1,00.html

And this description, hope it helps..

A. By default, when OWA has forms-based authentication enabled, sessions have a 15-minute inactivity timeout for public or shared computers and 24 hours for a private computer. If you're using a public computer to compose a long email message that takes more than 15 minutes to write, the session will time out and you won't be able to send the message. You can change this timeout value (which is the cookie lifetime) by using this procedure:
1. Log on to the Exchange server as an Administrator.
2. Start the registry editor (regedit.exe).
3. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA subkey.
4. From the Edit menu, select New - DWORD value.
5. Enter a name of PublicClientTimeout and press Enter.
6. Double-click the new value and set it to the desired number of minutes before a timeout (1 to 4320), set the type to decimal, and click OK.
7. To set the timeout period for a private client, repeat the process of creating a DWORD value, but this time enter a name of TrustedClientTimeout and again set the value to the number of minutes before a timeout (The value for private computers should be significantly higher than for public computers.)
8. Stop and restart the World Wide Web (WWW) Publishing service by using these commands at the command line.

net stop w3svc net start w3svc
0
 

Author Comment

by:ksuchewie
Comment Utility
That is what I've already tried...and it doesn't make a difference for the LIGHT version.

The light version times out after 5 minutes.
0
 
LVL 23

Expert Comment

by:debuggerau
Comment Utility
I see you reset IIS, but did you reset the exchange services though?


0
 

Author Comment

by:ksuchewie
Comment Utility
I reset IIS and W3SVC.  That's all I've found to reset.  What else needs to be reset?
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 23

Expert Comment

by:debuggerau
Comment Utility
I'd be giving exchange a cycle too..

Are you using form based authentication?

Was this the guide your using?
http://anewmessagehasarrived.blogspot.com/2009/01/owa-authentication-and-its-affect-on.html
0
 
LVL 1

Expert Comment

by:serafira
Comment Utility
Ksuchewie,
 We are having the same problem... did you ever get a resolution?
Serafira
0
 

Author Comment

by:ksuchewie
Comment Utility
no resolution yet on my side
0
 
LVL 23

Expert Comment

by:debuggerau
Comment Utility
0
 

Author Comment

by:ksuchewie
Comment Utility
debuggerau:
I have already tried that setup.  That does not seem to affect the light version timeout.  
0
 
LVL 23

Expert Comment

by:debuggerau
Comment Utility
ok, let do some test, I've just checked that the timeout is above 10mins, but less than 19Mins.
Will narrow the time down a little more before registry change to shorten the period.
It is a cookie timeout, so it will be that time period after last use; each time you change the page, it will reset the timer (from the server, not locally).

10:52 last change
11:07 still working
11:27 returns to login
11:28 modify reg key for 5 Minutes.
11:31 reset IIS
11:34 start test again
11:44 try and test, logged off as expected.

So the registry setting do have an effect, each time I verified that the 'light' version was selected, are you certain that was the 'mode' you were in?

Also, it talks about having form based authentication, is that the case in your situation?
Maybe it is using one of the other methods of authentication?
0
 
LVL 1

Accepted Solution

by:
serafira earned 500 total points
Comment Utility
The response we got from Dell Gold support who theoretically contacted Microsoft was that it's a feature not a bug, they won't fix anything that is Exchange 2003 backend mailboxes and Exchange 2007 OWA.  We confirmed that users we migrate to Exchange 2007 mailboxes work correctly.  Problem is we are not ready to migrate all 10,000 users to Exchange 2007 mailboxes.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now