Extension frontpage install server

If you are using IIS 4. The IIS 4. However the Server Extensions are added to virtual servers based on the following rules: If the machine already has a previous version of the FrontPage Server Extensions active on one or more virtual servers, then those virtual servers are automatically upgraded to the FrontPage 98 Server Extensions. If any virtual servers did not already have a previous version of the FrontPage Server Extensions installed, then the FrontPage 98 Server Extensions are not automatically installed to those virtual servers.

Use the IIS 4. The tar file is named fp The files fp Unlike previous releases of the Server Extensions that offered the Web Presence Provider's Kit, there are no additional utility or configuration script downloads required for the FrontPage 98 Server Extensions. The contents of the former Web Presence Provider's Kit are included. If you do not have this directory, the installation script will create it.

Note : The install directory must be on a local partition. Stub executables that link to the FrontPage Server Extensions are installed in directories below the top-level folder of each FrontPage web. The Apache server patch. FrontPage 98 offers a new patched Apache server that makes it possible to install a single version of the FrontPage Server Extensions, without stub versions of the Server Extensions in each FrontPage web. You will also have the options to install sub-webs on each virtual server.

Each content area is stored on a separate Web server. You must be logged on as root to run this script. You are prompted to back up the FrontPage installation directory, the server configuration file directory, and any content before installing the FrontPage 98 Server Extensions, and you are prompted for a Server Extensions directory. You can accept the default or specify another location. You are prompted to untar the FrontPage Server Extensions tar file, fp If the tar file is not in the default directory, you are prompted for its location.

The stub Server Extensions are installed on the root web and each sub-web. In order for this to work correctly, the ID of the Server Extensions on each FrontPage web must be set to the ID of the user who owns the web, and the content needs to have write-permissions by that user.

To make this model secure, the content must only be owned and writeable by that user. These role services are required to install the FrontPage Server Extensions, but they are optional once installation has completed.

After installation is complete, you can use Server Manager to remove one or more of the optional role services if you do not require the functionality that they provide. However, most of these optional role services are useful for configuring and monitoring your Web server. The following authentication method is required by the FrontPage Server Extensions depending on your version of Windows:. After you have downloaded the correct FPSE installation package, you need to make sure that you install the FrontPage Server Extensions using full administrative permissions.

This is best accomplished using one of two methods:. Log in to your computer using the local "administrator" account, then double-click the installation package to being the installation process.

If you are logged in using an account with administrative permissions that is not the local "administrator" account, open a command prompt using the "Run as Administrator" option, then use the following command to start the installation process:.

For more information about UAC, please see the following documentation:. The installation process will first present you with an End-User License Agreement, which you may choose to accept or cancel, but acceptance is required to continue installation.

If you accept the terms of the license agreement and click Next , if any of the prerequisites are not installed then the installation package will present you with a list of the role services and features that are required to install FPSE If you do not want these role services and features installed on your computer, click Cancel to cancel the installation.

If you click Next , the installation package will present you with a list of optional role services that are used by some additional FrontPage features. These role services are not required by FPSE , and their descriptions will list which FrontPage features use each role service. Locate the fpadmin. You can use this to configure your FrontPage web.

Users can edit the local web that is displayed when FrontPage is started, but they must have a valid user ID and password to modify it. The extensions require a specific directory structure, which is discussed later in this section.

After installation, you must perform some additional administrative tasks for setting permissions and accessing specific webs. Untar the downloaded file. For example, for the FrontPage 97 extensions on a Solaris platform, you untar the vt For Solaris, use this code:.

Move the file fpsrvadm. When you are prompted for the name of the server configuration file, enter the pathname of your server's magnus. Modifies magnus. Once you have completed the installation process, you must perform the following administrative tasks:.

Execute the fpsrvwin. A remote machine must have the FrontPage 97, 98, or program installed Macintosh or Windows only. If the user wants to edit a web on a different machine, click on "MoreWebs" on the line to select a web server or disk location type in the servername : portnumber of the web to edit. Choose OK. Select the proper web from the list of webs on the host machine to edit.

Log in as the root user so you can install the FrontPage Server Extensions from the tar file. For example: When a user moves a page between folders in a FrontPage web, the extensions automatically update all links to that page from every other page in the web.

Once you have installed the extensions on your server, FrontPage web publishing, administering, and discussion group functionality is available from any computer that is on the Internet or a local Intranet, although you need the FrontPage client program for authoring and administrative functions. A single root web can support a number of sub-webs. A sub-web is a complete FrontPage web that is a subdirectory of the root web. Sub-webs can only exist one level below the root web.

Each sub-web can have many levels of subdirectories, making up its content. Even though sub-webs appear below the root web in the Web server's filesystem and URL space, the root web does not include the content in its sub-webs.

This separation of content is done by the FrontPage Server Extensions. The root web and all sub-webs on a server must have separate copies of the extensions installed or have stub executables of the extensions programs. This page and associated content may be updated frequently. We recommend you subscribe to the RSS feed to receive update notifications. From time to time, Microsoft may publish a preview, or pre-release, version of an Open Specifications technical document for community review and feedback.

To submit feedback for a preview version of a technical document, please follow any instructions specified for that document. If no instructions are indicated for the document, please provide feedback by using the Open Specification Forums. The preview period for a technical document varies. Additionally, not every technical document will be published for preview. After the preview period, the most current version of the document is available on this page.

Find resources for creating interoperable solutions for Microsoft software, services, hardware, and non-Microsoft products:. Technical Documentation. Additionally, overview documents cover inter-protocol relationships and interactions.