Exchange 2007 Outlook Web Access Light timeout

Posted on 2009-07-12
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
Question by:ksuchewie
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
  • 2
LVL 23

Expert Comment

ID: 24837169
not sure about regedit yet, I goto IIS management and change the timeout on the web server firstly..


Author Comment

ID: 24839114
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.

LVL 23

Expert Comment

ID: 24845195
Found these links:,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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 24848731
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.
LVL 23

Expert Comment

ID: 24854988
I see you reset IIS, but did you reset the exchange services though?


Author Comment

ID: 24859254
I reset IIS and W3SVC.  That's all I've found to reset.  What else needs to be reset?
LVL 23

Expert Comment

ID: 24865518
I'd be giving exchange a cycle too..

Are you using form based authentication?

Was this the guide your using?

Expert Comment

ID: 24988548
 We are having the same problem... did you ever get a resolution?

Author Comment

ID: 24988635
no resolution yet on my side
LVL 23

Expert Comment

ID: 25002132

Author Comment

ID: 25003792
I have already tried that setup.  That does not seem to affect the light version timeout.  
LVL 23

Expert Comment

ID: 25009955
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?

Accepted Solution

serafira earned 500 total points
ID: 25060388
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.

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Active Directory Account getting mysteriously locked 13 81
exchange, OWA, scripts 5 44
Exchange server licensing 2 40
Round robin for Exchange 2013 4 27
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create a Contact 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 >> Contact ta…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

696 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