Command Line Security Changes Require Restart of IIS

ID: Q190521

The information in this article applies to:

Microsoft FrontPage 98 for Windows
Microsoft FrontPage 97 for Windows with Bonus Pack

SYMPTOMS

When you update security on an existing FrontPage Web using the command line, Internet Information Server (IIS) must be restarted in order for the changes to take effect.

CAUSE

This only occurs when the security is edited with the Fpsrvadm.exe or Fpremadm.exe command-line utilities. User tokens are not refreshed until the server is restarted.

RESOLUTION

Method 1

Apply security changes to a newly created Web using the command-line Server Administrator before you open the Web for the first time.

An example command-line change:

fpsrvadm.exe -o security -p 80 -w webname -a authors -u <author name>

For more information about the Fpsrvadm.exe utility, refer to the administration section of the FrontPage Server Extensions Resource Kit(SERK), which is available online at:

http://www.microsoft.c om/frontpage/wpp/serk

Method 2

Restart IIS after you apply security changes using the command-line Server Administrator. For information about restarting IIS, see the IIS documentation.

Method 3

In FrontPage Explorer, go to the Tools menu and click Permissions to set permissions. No restart is required.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Permissions changes made through FrontPage Explorer do not require a server restart, because FrontPage Explorer forces a refresh of the cache.

Example

Using the following command on an existing Web requires a server restart in order to take effect, because the existing Web has already been cached by IIS:

fpsrvadm.exe -o security -p 80 -w webname -a authors -u <author name>

If a new Web is created by using the following command and further security changes are applied before the new Web is opened using the preceding command:

fpsrvadm.exe -o install -p 80 -w webname -u <username>

then a server restart is not required for the changes to take effect, because the new Web has not yet been cached by IIS.

Keywords : fpiis fp97 fp98
Version : WINDOWS:98,97
Platform : WINDOWS
Issue type : kbbug