PRB: Changes to Personal Web Pages (PWP) Objects in LDAP Server Not Reflected on Front-End PWP Server (276373)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

In an MCIS version 2.5 environment, with a Personal Web Pages (PWP) server/Active User Object (AUO) instance, and an LDAP instance that is located on another server, changes that you make under ou=PersonalWebPages in the LDAP server may not be reflected in the local PWP server.

The PWP server cache may not appear to be renewing the information from the LDAP server. The changes are not reflected on the PWP server until you change the schema, modify the directory information tree (DIT), or restart IISADMIN. This means that when you delete a user in ou=PersonalWebPages, that change may not be reflected, and a deleted user could potentially access the PWP site.

CAUSE

The local PWP server caches the PersonalWebPages objects. Because this information is not cached within the AUO cache, restarting the Internet Authentication Service (Broksvc), or flushing the AUO cache, has no effect on these objects.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You can configure the amount of time that the objects are kept in the PWP cache (the default is 3600 seconds); to do this, change the value in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MCIS25\PWP\CacheTimeout