Robert McMurray See Profile View Website Forum Posts: 228 End-of-life As of December 18, 2010, Microsoft FrontPage Server Extensions (FPSE) 2002 is simply not supported on Windows Vista and Windows Server 2008 RTM and it is no lengthier to choose from for download. Instead, use an choice IIS technology, which include Web Deploy, FTP publishing services, or WebDAV extension.Introduction As a lot of people which have installed IIS 7.0 on Windows Vista and Windows Server(c) 2008 have realized, there are no choices to put in the FrontPage Server Extensions, leaving only two means to edit your Web site blog if its hosted on the Windows Vista or Windows Server 2008 computer:Edit the internet blog locally by using the file system. Use FTP to upload your files to a remote Windows Vista or Windows Server 2008 personal computer. Microsoft realizes that the FrontPage Server Extensions are essential to many Net hosting companies and developers,
Microsoft Office 2010 Pro Product Key, and has worked with Ready-to-Run Software to release a version of the FrontPage 2002 Server Extensions (FPSE 2002) for Windows Vista and Windows Server 2008. This version of FPSE 2002 is on hand for x86 (32-bit) and x64 (64-bit) Windows Vista and Windows Server 2008 as a separate download for IIS 7.0, and you can download this version by clicking the following URL:FrontPage 2002 Server Extensions for IIS seven.0 In This Walkthrough FPSE Prerequisites FPSE Installation on Windows Vista or Windows Server 2008 Extending Website Sites with FPSE Removing FPSE from Website Sites Notes: The FrontPage 2002 Server Extensions (FPSE 2002) are not supported for IIS 7.5 on Windows seven or Windows Server 2008 R2. If you attempt to put in FPSE 2002 on Windows seven or Windows Server 2008 R2, you should receive several installation errors, following which the server extensions will fail to work. This release of the FrontPage 2002 Server Extensions (FPSE 2002) is supported Ready-to-Run Software. More information about Ready-to-Run Software is to choose from at the following URL: This version of FPSE 2002 introduces no new functionality; it truly is essentially the same version of FPSE 2002 that was created for Windows Server 2003, but it has been updated to work on Windows Vista or Windows Server 2008. By way of additional explanation, FPSE 2002 is part of the Office XP system of products. The Office XP system, including FPSE 2002, left mainstream support on July 11th, 2006, according to the Office lifecycle policy. Because Microsoft's support policy is to remove software from the Download Center that is no longer supported, FPSE 2002 was removed from the Microsoft Download Center at that time as a separate product. FPSE 2002 continues to be offered and supported on Windows Server 2003 through the Add Windows Components section of the Add/Remove Programs control panel.FPSE Prerequisites Supported Platforms This version of the FrontPage Server Extensions is only supported on the following platforms:Windows Server 2008: All SKUs Windows Vista: Business Enterprise Ultimate Home Premium Note: FPSE 2002 isn't really supported for IIS 7.5 on Windows seven or Windows Server 2008 R2Required Role Services and Features The following role services and features are required to put in the FrontPage 2002 Server Extensions (FPSE 2002) on Windows Vista or Windows Server 2008. If they are not already put in on your personal pc when you set up FPSE 2002, they will be installed for you automatically. If you do not want these role services and features put in on your pc, you cannot set up FPSE 2002.Net Server (IIS) Role Services: Website Server Common HTTP Features Static Content Default Document Directory Browsing (See note 1) HTTP Errors (See note 1) Application Development ISAPI Extensions ISAPI Filters Health and Diagnostics HTTP Logging (See note 1) Request Monitor (See note 1) Security Windows Authentication or Basic Authentication (See note 2) Request Filtering Performance Static Content Compression (See note 1) Management Tools IIS Management Console (See note 1) IIS 6 Management Compatibility IIS 6 Metabase Compatibility Features: Windows Process Activation Services Process Model Notes:These role services are required to put in 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: Windows Authentication is required for all versions of Windows Server 2008 and all versions of Windows Vista except Windows Vista Home Premium. Basic Authentication is required for Windows Vista Home Premium. FPSE Installation on Windows Vista or Windows Server 2008 Downloading FPSE To put in the FrontPage 2002 Server Extensions (FPSE 2002) on Windows Vista or Windows Server 2008, begin by downloading the installation package from the following URL: FrontPage 2002 Server Extensions for IIS seven.0 After you have downloaded the FPSE 2002 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 just not the local "administrator" account,
Office Home And Student 2010 Key, open a command prompt using the "Run as Administrator" option, then use the following command to start the installation process:msiexec /i <path to FPSE package><name of FPSE package>.msi Note: The above steps are required because the User Account Control (UAC) security component in the Windows Vista and Windows Server 2008 operating systems will prevent the FPSE 2002 installation package from installing correctly. For more information about UAC, please see the following documentation: Installing FPSE 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 put in then the installation package will present you with a list of the role services and features that are required to put in FPSE 2002. If you do not want these role services and features put in on your laptop 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 2002, and their descriptions will list which FrontPage features use each role service. After choosing any additional role services, you can click Next and then Set up to being the actual installation process.Note: Unlike previous versions of the FrontPage Server Extensions, the installation process will only create the "MSSharePointAppPool" application pool and the FrontPage Server Administration Internet internet site (also called the Microsoft SharePoint Administration World wide web web-site). Therefore no Web sites will have the FrontPage Server Extensions installed after you have completed the installation process.Extending Internet Sites with FPSE After you set up FrontPage 2002 Server Extensions (FPSE 2002) on your server, you must extend a Web site website or virtual server with FPSE 2002 before you can open the world wide web blog using an authoring tool.You can extend the server one of two means:By using HTML Administration pages. By using the install operation with the command-line tools. Note: Extending a Web blog does not configure any authentication methods. After installing FPSE 2002 on the Web site page, you will need to configure an authentication method, which includes Windows or Basic Authentication,
Office Pro 2010 Activation Key, before your users will be able to open or publish to the internet webpage.Using HTML Administration Pages to Extend a Internet Web page To extend a Web site website using HTML Administration pages on Windows, use the following steps:Click Start, point to Programs, point to Administrative Tools, and then click Microsoft SharePoint Administrator to open the Server Administration page. In the list of virtual servers, click Extend next to the virtual server you want to extend. In the Administrator box, type the user name for the administrator of the virtual server. Click Submit. Note: Using the HTML Administration pages gives you the most flexibility in choosing which selections you want enabled after you extend your server.Using the Command Line to Extend a Net Online site You can extend a Internet webpage by using the command-line tools, owsadm or owsrmadm. These tools are located in the "%ProgramFiles%Common FilesMicrosoft SharedWeb Server Extensions50bin" folder. To extend a Web site, use the set up operation, which takes the following parameters.Note: To determine which web-site instance number to use, open the IIS manager and select the "Sites" node in the tree. The ID column in the internet page list contains the unique identifier for each blog,
Office Pro 2010 Serial, which you would use in the online site instance number. For example, if a web page has an ID of 3, the webpage instance number would be LM/W3SVC/3.The following example shows the syntax for the set up operation on Windows:owsadm.exe –o set up –p <port> -u <username> Note: For a complete list of the parameters required for the install operation and their descriptions,
Windows 7 Activation Key, see Command-line Operations.Removing FPSE from World wide web Sites You can temporarily or permanently remove FrontPage 2002 Server Extensions on a particular server. To temporarily remove the extensions so you can clean or restore your website, use the Uninstall command. In this mode, much of the data about your website is preserved, so you can extend the virtual server again and return to your original configuration.To permanently remove FrontPage 2002 Server Extensions, use the Full Uninstall option. Doing so also removes any other files and folders that FrontPage 2002 Server Extensions put in. All of the data about your webpage (excluding actual web page content) is deleted when you perform a full uninstall, so be sure that is what you want before you use the Full Uninstall option.Using HTML Administration Pages to Remove You can use HTML Administration pages to uninstall FrontPage 2002 Server Extensions. To remove FrontPage 2002 Server Extensions from a website page:Open the Server Administration page. In the list of virtual servers, next to the virtual server you want to uninstall, click Administration. Under Administration, click Uninstall FrontPage 2002 Server Extensions. If you want to uninstall FrontPage 2002 Server Extensions completely, including the metadata about your Website internet site, next to Full Uninstall, click Yes. Click Uninstall. Using the Command Line to Remove You can remove the FrontPage 2002 Server Extensions from a World wide web website using the command-line tools, owsadm or owsrmadm. These tools are located in the "%CommonProgramFiles%Microsoft SharedWeb Server Extensions50bin" folder. To remove FPSE 2002 from a Internet internet site, you use the uninstall or fulluninstall operations. The uninstall operation removes FrontPage 2002 Server Extensions from your server. The full uninstall operation also removes the data about your website (excluding actual webpage content) from your virtual server.The uninstall and fulluninstall operations take the port parameter. The following example shows the syntax for removing FPSE from a website website:owsadm.exe –o uninstall –p <port> Related Content Articles FrontPage Server Extensions (FPSE) for IIS 7.0How to Migrate FPSE Sites to WebDAVPublishing Components: FTP 7.0, WebDAV, and FPSEUsing Visual Studio 2008 with IIS 7