Microsoft Knowledge Base Email Alertz

KBAlertz.com: (838684) - Explains how to set the permissions for the check server health utility to fix using the Owsadm.exe command in the command prompt.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 838684 - Last Review: May 5, 2004 - Revision: 1.2

How to set permissions for the check server health utility so that you can use the Owsadm.exe command in FrontPage 2002 server extensions

INTRODUCTION

This article describes how to set the permissions for the check server health utility so that you can use the Owsadm.exe command. This utility helps you to repair or to tighten security settings in Microsoft FrontPage 2002 server extensions.

MORE INFORMATION

The check server health utility helps you to maintain the supporting files of your Microsoft FrontPage extended Web site. This utility performs a set of tests that you can use to make sure of the integrity of your Web site system files and security settings.

You can set the permissions of the check server health utility to fix using the Owsadm.exe command at the command prompt. To do so, follow these steps:
  1. Click Start, and then click Run.
  2. In the Run dialog box, type cmd, and then click OK.
  3. At the command prompt, type the following commands, and then press ENTER after each command:
    • C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\50\bin
      This path assumes that the FrontPage 2002 Server Extensions are installed in the default folder. Change the path according to your particular installation.
    • owsadm.exe -o setproperty -pn checkrolesconfig -pv fix
    • owsadm.exe -o setproperty -pn checkuseraccess -pv fix
    • owsadm.exe -o check -p lm/w3svc/1
    • Type exit, and then press ENTER to quit the command prompt.
Note By default, your Web server's Default Web site uses port 80. If you have changed that setting or you are installing the server extensions on a different virtual server, substitute the appropriate port number for 80, or use an instance number, such as /LM/W3SVC/1 or /LM/W3SVC/3.

By default, when you run the owsadm.exe -o setproperty -pn checkrolesconfig -pv fix command or the owsadm.exe -o setproperty -pn checkuseraccess -pv fix command, the values of the following registry subkeys will be set to “Fix” in Registry Editor:
HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\All Ports\checkrolesconfig
HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\All Ports\checkuseraccess

REFERENCES

For additional information about how to use the SharePoint Team Service command-line utility, click the following article number to view the article in the Microsoft Knowledge Base:
272945  (http://kbalertz.com/Feedback.aspx?kbNumber=272945/ ) STS: Using the SharePoint Team Services command-line utility (Owsadm.exe)
For additional information about how to use the command-Line tools to install and configure FrontPage 2002, click the following article number to view the article in the Microsoft Knowledge Base:
825489  (http://kbalertz.com/Feedback.aspx?kbNumber=825489/ ) HOW TO: Use the command-line tools to install and configure FrontPage 2002

APPLIES TO
  • Microsoft FrontPage 2002 Server Extensions
Keywords: 
kbhowto KB838684
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

ADSI4NT - www.adsi4nt.com Report As Irrelevant  
Written: 4/22/2004 9:04 AM
OK, so I am wondering.. it doesn't say here what these commands actually do or why we might want to run them. So I search a bit more and find: http://www.microsoft.com/resources/documentation/sts/2001/all/proddocs/en-us/admindoc/owsl03.mspx CheckRolesConfig Specifies that the check operation will verify that user role settings are enforceable. This check detects and repairs possible problems with roles, including the following: a user record has an invalid format, the user has a record in the list of users, but no matching user account, the user record refers to a non-existent role, there is no role for the anonymous user, and so on. Set to check or fix. Default value is null, which means the action is ignored when the check operation is run. CheckUserAccess Specifies that the security settings from the roles.ini file are applied to the file system when the check operation is run. There is no check value for this property, only a fix value. Default value is null, which means the action is ignored when the check operation is run. Great... it looks like we have to go through and set this for each and every web site... No wonder Front Page permissions are such a PITA and 1/2 the time I have to set them manually...

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please