OWA Timeout 2007
Hello, I am trying to adjust the public and private timeout values of OWA. There are many docs out on the web to do this but none of them consistant with the registry change that needs to be done. Could anyone point me to the correct registry value that needs to be changed? I am running Exchange 2007 sp1.Thank you.
April 8th, 2008 11:20pm

Since you are running Ex2007, you can do it through powershell also (except regedit) Private: set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\MSExchangeOWA -name TrustedClientTimeout -value <amount of time> -type dword Reference : http://technet.microsoft.com/en-us/magazine/cc162367.aspx Public: set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -name PublicTimeout -value <amount of time> -type dword Reference : http://technet.microsoft.com/en-us/library/bb124787(EXCHG.80).aspx
Free Windows Admin Tool Kit Click here and download it now
April 9th, 2008 2:10am

Thanx for the response.I have tried that and it failed because "HKLM:\SYSTEM\CurrentControlSet\Services\MSExchangeOWA" didn't exist.But even in your example there are differences in Private vs public as one has a space between "MSExchangeOWA" and MSExchange OWA"Is this correct?
April 9th, 2008 4:51pm

Looks like typo mistake in magazine. Technet articlehas a space in reg key. http://technet.microsoft.com/en-us/library/bb124819(EXCHG.80).aspx Code Snippet set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -name PrivateTimeout -value <amount of time> -type dword
Free Windows Admin Tool Kit Click here and download it now
April 9th, 2008 4:57pm

I have the same issue and found an article mentioned above, I did follow all the steps to immpliment the registry key for both PublicTimeout and PrivateTimeout, but still get the timeout issue, I did run the iisreset /noforce, that did not work, I even reboot the CAS server, still no luck. Is there any other suggestion? Please help. My Exchange Server 2007 installed on Windows Server 2008 with 2 CAS nodes (LNB), the LNB worked just fine, Outlook Anywhere worked internal/external. I use the Exchange Management Shell to add those 2 key as follows. set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -name PrivateTimeout -value <amount of time> -type dword and set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -name PublicTimeout -value <amount of time> -type dword Any other suggestion will appreciate. Thanks, DTV.
November 27th, 2008 2:38pm

I think I narrowed down the root cause of this timeout issue, we had 2 CAS server with MS LNB, if I turn off 1 of the LNB node, everything started to work just fine, but when I had both LNB nodes enabled for LNB, the timeout issue started. Is there a way to fix this problem?
Free Windows Admin Tool Kit Click here and download it now
December 3rd, 2008 5:28am

What's the correct registry key, anyway... In some places the key names are PublicClientTimeout and PrivateClientTimeout, here the names are PublicTimeout and PrivateTimeout. wich ones are the correct ones? Thanks
April 6th, 2009 1:21pm

It appears to be:PrivateTimeout http://technet.microsoft.com/en-us/library/bb124819.aspxandPublicTimeout http://technet.microsoft.com/en-us/library/bb124787.aspxHowever, neither article discusses what the default settings are, and as many people in this thread found (and others I found while googling) nowhere can I find mention what the DEFAULT values are. Some people may be fine picking a set amount of hours, but I would like to know what the defaults are so that I know if I am adjusting upward or downward from MS recommendations.Anyone?
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2009 9:45pm

looks like the defaults arePrivateTimeout = 8 hoursPublicTimeout = 15http://technet.microsoft.com/en-us/library/bb123719.aspx
October 21st, 2009 6:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics