Microsoft KB Archive/190521

= Command line security changes require restart of IIS =

Article ID: 190521

Article Last Modified on 7/10/2006

-

APPLIES TO


 * Microsoft FrontPage 98 Standard Edition
 * Microsoft FrontPage 97 Standard Edition

-



This article was previously published under Q190521



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.



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

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.com/technet/archive/office/office97/reskit/fp98serk/ADMIN.mspx

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

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

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: kbbug kbpending KB190521

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.