Make your own free website on Tripod.com
Microsoft Home Microsoft Home
Microsoft FrontPage 2000 Server Extensions Resource Kit

HTML Administration Forms


 

 

TOP  

 

Installing the FrontPage Server Extensions on a Virtual Server

Use this form to install or upgrade the FrontPage Server Extensions on the specified port of a virtual server. It requires an administrator name and password.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click New Virtual Server.
  3. In the Virtual Host Name field, type the name of the virtual host on which you want to install the FrontPage Server Extensions.
  4. In the Port Number field, type the port number.
  5. In the Administrator Account Username field, type a user name.

    On IIS, this value can be either a Microsoft® Windows NT® user account name or a Windows NT group name, and it can be qualified with a domain name, for example Domain\Username

  6. For all server types except IIS, in the Administrator Account Password field, type the administrator account's password.
  7. If the server has a server configuration file, type its full path name in the Server Configuration File Path field. For example, on Apache servers, type /usr/local/apache/conf/httpd.conf
  8. In the Server Type list, click the Web server type.
  9. To specify that the web content and the FrontPage Server Extensions stub programs should be chowned to a UNIX user account, type the account name in the UNIX User Account Username field.
  10. To specify that the web content and the FrontPage Server Extensions stub programs should be chowned to a UNIX group account, type the account name in the UNIX Group Account Name field. Note that even if you specify a UNIX user account name, you do not have to specify a UNIX group account name.

    If either a UNIX user or group account name is specified, then the server extensions stub programs are set to read/execute access with the set user ID bit set to the given user name and group name. Note that only the server extensions stub programs are chmoded, not the web content files.

  11. Click Create Server.

 

The FrontPage Server Extensions are installed and a root web is created.

TOP  

 

Creating or Merging a Subweb

Use this form to do one of two things:

  • Create a FrontPage-extended subweb at the specified directory in an existing FrontPage-extended web.
  • Uninstall the server extensions on the specified subweb. This converts the subweb into a folder of its parent FrontPage-extended web.
  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Create/Merge Subweb.
  3. In the Create or Merge field, select Create or Merge.
  4. In the Virtual Host Name field, type the name of the virtual host in which the subweb will be created or removed.
  5. In the Port Number field, type the port number of the virtual server in which you are creating or removing the subweb.
  6. In the Web Name field, type the name of the subweb.

    This should be the path of a directory, relative to the server's top-level directory.

  7. If you are creating a new subweb and you want the subweb to have permissions that are different from its parent web, type a user name in the Administrator Account Username field.

    If this field is blank, new subwebs will inherit their permissions from the parent web. If this field is not blank, the new subweb will have unique permissions with an initial administrator account based on the contents of this field.

    On IIS, this value can be either a Windows NT user account name or a Windows NT group name, and it can be qualified with a domain name, for example Domain\Username.

  8. For all server types except IIS, in the Administrator Account Password field, type the administrator accountís password.

    If this field is blank, new subwebs will inherit their permissions from the parent web. If this field is not blank, the new subweb will have unique permissions with an initial password based on the contents of this field.

  9. To specify that the web content and the FrontPage Server Extensions stub programs should be chowned to a UNIX user account, type the account name in the UNIX User Account Username field.
  10. To specify that the web content and the FrontPage Server Extensions stub programs should be chowned to a UNIX group account, type the account name in the UNIX Group Account Name field. Note that even if you specify a UNIX user account name, you do not have to specify a UNIX group account name.

    If either a UNIX user or group account name is specified, then the server extensions stub programs are set to read/execute access with the set user ID bit set to the given user name and group name. Note that only the server extensions stub programs are chmoded, not the web content files.

  11. Click Create/Merge Subweb.

 

TOP  

 

Removing the FrontPage Server Extensions from a Virtual Server

Use this form to uninstall the FrontPage Server Extensions on the specified port of a virtual server. This operation also uninstalls the Server Extensions from any subwebs below the root web.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Uninstall.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Full Uninstall list, click Yes to uninstall the FrontPage Server Extensions without leaving any FrontPage meta-information in the web. Click No to leave some FrontPage meta-information in the web. If you select Yes and then reinstall the FrontPage Server Extensions on the virtual server, FrontPage subwebs will not be automatically recreated. If you select No, any subwebs on the server will be recreated when the FrontPage Server Extensions are reinstalled.
  6. Click Uninstall.

 

TOP  

 

Checking and Fixing the FrontPage Server Extensions on a Virtual Server

Checking the FrontPage Server Extensions includes:

  • Checking permissions on the FrontPage DLLs or executables.
  • Verifying the existence and correctness of _vti_bin , _vti_pvt, _vti_log, and other FrontPage-created directories.
  • Verifying that server virtual roots and meta-base settings are correct and up to date.
  • If the web you are checking has subwebs, those are checked also.

 

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Check and Fix Extensions.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. Click Check.

 

TOP  

 

Recalculating Hyperlinks in a Web

Recalculating hyperlinks synchronizes FrontPage-based content databases with the current state of the web. This also re-includes pages in Include Page components, recalculates other components (such as search forms and navigation bars), reapplies borders to any pages that use borders, resets permissions on form handler result pages, re-indexes categories, and recalculates text indexes.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Recalculate Links.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Web Name field, type the name of the web.

    This should be the path to the web's top-level directory, from the server's top-level directory. To specify the root web, type a forward slash (/).

  6. Click Recalculate.

 

TOP  

 

Enabling Authoring on a Virtual Server

Authoring is enabled by default in the FrontPage Server Extensions. However, if you have disabled authoring, you can use this form to enable it.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Enable Authoring.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. Click Enable Authoring.

 

This also enables remote administration of the FrontPage-extended web by using the FrontPage client.

TOP  

 

Disabling Authoring on a Virtual Server

Authoring is enabled by default in the FrontPage Server Extensions. Use this form to disable authoring.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Disable Authoring.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. Click Disable Authoring.

 

TOP  

 

Setting Permissions for a User

Use this form to set up FrontPage-extended web permissions on the specified web.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click User Permissions.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Web Name field, type the web name.

    This should be the path to the web's top-level directory, from the server's top-level directory. To specify the root web, type a forward slash (/).

  6. In the Username field, type the name of the user whose permissions you are adding, removing, or changing.
  7. For all server types except IIS, in the Password field, type the user's password.
  8. Select the level of access for the user: Browse Access, Browse and Author Access, or Browse, Author, and Administrate Access. To give the user no access, click Remove this User.
  9. Click Change Permissions.

 

TOP  

 

Setting Permissions for IP Addresses

You can change permissions for a computer or group of computers by setting permissions on IP address masks. An IP address mask is a range of IP addresses defined so only computers with IP addresses within the range are allowed access to an Internet service. To mask a portion of an IP address, replace it with the asterisk (*) wildcard character. For example, 192.44.*.* represents every computer on the Internet with an IP address that begins with 192.44.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click IP Address Permissions.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Web Name field, type the web name.

    This should be the path to the web's top-level directory, from the server's top-level directory. To specify the root web, type a forward slash (/).

  6. In the IP Address field, enter the IP address of the computer or set of computers whose permissions you are adding, removing, or changing. You can use the asterisk (*) as a wildcard character, as in 128.109.*.*
  7. Select the level of access for the computer or group of computers: Browse Access, Browse and Author Access, or Browse, Author, and Administrate Access. To remove all restrictions on the IP address or IP address mask, click Remove this mask.
  8. Click Change Permissions.

 

TOP  

 

Deleting a Subweb

Use this form to delete a specified FrontPage-extended subweb on the specified virtual server and port. You cannot delete the root web using this command; to delete the root web, use the Uninstall form.

This form deletes all content, including all subwebs of the web you are deleting.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Delete Subweb.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Subweb Name field, type the name of the subweb.

    This should be the path to the subweb's top-level directory, from the serverís top-level directory.

  6. Click Delete Subweb.

 

TOP  

 

Renaming a Subweb

Use this form to rename a subweb.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Rename Subweb.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Subweb Name field, type the current name of the subweb.

    This should be the path to the subweb's top-level directory, from the server's top-level directory.

  6. In the New Subweb Name field, type the new name of the subweb.
  7. Click Rename Subweb.

 

TOP  

 

Specifying That a Folder Can Contain Programs

Use this form to specify that a directory can contain executable scripts or programs. By default, directories cannot contain executable scripts or programs.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Set Directory Executable.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Web Name field, type the name of the web.

    This should be the path to the web's top-level directory, from the server's top-level directory. To specify the root web, type a forward slash (/).

  6. In the Directory URL field, type a URL relative to the top-level directory of the FrontPage-extended web.
  7. Click Set Directory Executable.

 

TOP  

 

Specifying That a Folder Cannot Contain Programs

Use this form to specify that a directory cannot contain executable scripts or programs. By default, directories cannot contain executable scripts or programs.

  1. From your browser, start the HTML Administration Forms by opening Fpadmin.htm.
  2. In the contents listing, click Set Directory Not Executable.
  3. In the Virtual Host Name field, type the name of the virtual host.
  4. In the Port Number field, type the port number.
  5. In the Web Name field, type the name of the web.

    This should be the path to the web's top-level directory, from the server's top-level directory. To specify the root web, type a forward slash (/).

  6. In the Directory URL field, type a URL relative to the top-level directory of the FrontPage-extended web.
  7. Click Set Directory Not Executable.

 

Administration

  BACK  TOP
 
  Last Updated June 1999
©1999 Microsoft Corporation. All rights reserved. Terms of Use. Disclaimer