The next scenario we'll look at illustrates what happens when a user doesn't perform any operation within a specified window of time. The next operation the user tries to perform will present the logon page. Before I explain how this process occurs, it's important to note that the front-end server maintains knowledge of three symmetric keys—the current key and the previous two keys. In fact, there are two sets of these three keys—one set for Public access and one set for Trusted access. The reason for having two sets is to provide different timeouts for accessing OWA through a public computer (e.g., a kiosk) and from a private location such as a home office.
You can control the desired timeout values by modifying the REG_DWord values PublicClientTimeOut and TrustedClientTimeOut in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeWeb\OWA registry subkey on the front-end server. These values are expressed in minutes, with a default timeout of 15 minutes for a public client and 1440 minutes (24 hours) for a private client. . . .
Register
Microsoft recommends to delete cookies from the browser, 'usually' by closing the browser. However that doesn't work.
You must delete the cookies, and 2 copies of Index.dat
After deleting cookies navigate to:
C:\Documents and
Settings\%username%\Cookies\Index.dat
And,
C:\Documents and Settings\%username%\Userdata\Index.dat
Make sure all instances of Internet explorer are closed.
and delete both index.dat files. These are recreated the next time the browser is opened.
So, for a user named 'me', it would be:
C:\Documents and Settings\ME\Cookies\Index.dat
And,
C:\Documents and Settings\ME\Userdata\Index.dat
If this process gives any errors, then make sure that all instances of the 'iexplore.exe' process are closed.
Task Manager > Processes 'Tab'
redwraith94 February 24, 2007 (Article Rating: