Tuesday, August 24, 2010

Set OWA Private Computer Cookie Time-Out Value Exchange 2010.

If you ever wondered how long it takes for your browser to close after opening OWA ( outlook web App) if there is no activity?  here are the measurements.

  • Public 15 minutes
  • Private 8 days


For whatever reason you may have if you decide to change these default values here is the link how to get the work done. The simplest way to achieve desired goal is using PS. Let’s say we will increase the Public cookie time out settings from 15 minutes to 25 minutes.

set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\MSExchange OWA' -name PrivateTimeout –value 25 -type dword

copy and paste above PS code into  EMS ( management Shell) , adjust the time as you wish , in this case we are going to set it to “25” minutes….



Cookies to control access

The first time that the user name and password are sent to the Client Access server to authenticate an Outlook Web App session, an encrypted cookie is created that's used to track user activity. When the user closes the Internet browser or clicks Sign Out to sign out of their Outlook Web App session, the cookie is cleared. The user name and password are sent to the Client Access server only for the initial user sign-in. After the initial sign-in is complete, only the cookie is used for authentication between the client computer and the Client Access server.

Read more click here…………..

Oz Casey, Dedeal
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog
http://telnet25.spaces.live.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)


Wildcard SSL said...

Im using exchange 2007 OWA with ISA 2006 Publishing and Alladin OTP Tokens.
Everything is working good except that the users complain that the OWA logoff them after a few minutes (something like 5 minutes).
I tried to run this command from the powershell: "set-ItemProperty ‘HKLM:\SYSTEM\CurrentControlSet\Services\
MSExchange OWA’ -name TrustedClientTimeout
-value 1440 -type dword"
and after this restart the iis service but it doesnt help.
what else should i do ?

Anonymous said...

Private: 8 days - although you probably mean 8 hours? Luckily the capture below corrects this.