I just stole this from a well known forum of experts, it might help or partly answer the questions you posed:
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
2.Ref this article to change the OWA session timeout settings,
http://www.tech-archive.net/Archive...blic.windows.server.sbs/2006-06/msg00061.html
3.KB 173497: XADM: Session Timeout Settings for Outlook Web Access -
http://support.microsoft.com/default.aspx?scid=kb;en-us;173497 (Microsoft Exchange Server 5.5 Standard Edition)
KB 294752: XCCC: Session Time-Out Settings for Outlook Web Access on Exchange 2000 Server -
http://support.microsoft.com/default.aspx?scid=kb;en-us;294752 (Microsoft Exchange 2000 Server)
http://www.microsoft.com/downloads/...65-A04E-43CA-8220-859212411E10&displaylang=en
There is also an article here:
http://social.technet.microsoft.com...n/thread/d5c5e8b7-edee-4ab7-9da8-b173ba5d5a92
Which helps with the particular registry entry you are talking about (i think).