By default IE has a built-in “feature” that checks for newer versions of stored web pages automatically (such as the PVE login page). Rather than honoring the content expiration specified by the web server, it uses its own logic algorithm to determine whether or not IE should download a new version of the page or use a cached version previously stored on the computer. If IE determines that the page doesn’t change very often, then IE will not always check for new versions of the page. Unfortunately, there is no configuration change or code change that can be made on the server-side to resolve this as Microsoft has eliminated the standard expiration checks that should be taking place in the client.

Users can resolve this issue in one of two ways:

• Clear the Temporary Internet files
• Change the setting so that the browser uses the server-specified expiration for the files

To clear the Temporary Internet Files:

1. Launch IE and from the toolbar, select “Tools”, then “Internet options”.
2. From the “General” tab click the “Delete” button under the Browsing history section.
3. Ensure that ONLY Temporary Internet Files is selected/checked.
4. Click the “Delete” button.
5. Click the OK button to close the Internet options window.
6. Refresh the PVE login page, or close IE and re-launch it.

To change the settings so that IE always checks for and uses the most current version of the page, properly honoring the server’s content expiration:

1. Launch IE and from the toolbar, select “Tools”, then “Internet options”.
2. From the “General” tab click the “Settings” button under the Browsing history section.
3. In the Temporary Internet Files section, change the Check for newer versions of stored pages option from “Automatically” to “Every time I visit the webpage”. This will force IE to check for a newer version of the page each time you view that page.
4. Click the OK button to save the change and close the window.
5. Click the OK button to close the Internet options window.
6. Refresh the PVE login page, or close IE and re-launch it.

For more information, view Microsoft’s Knowledge Base article: http://support.microsoft.com/kb/263070