Here's what I did for just a plain IIS 4.0 server and FPSE 2K
1) installed NT service pack 5 (yes it says not to but I have more luck this
2) installed IE 5 (again M$ says you should only use 4.01 sp2 but I still
have more luck this way)
3) installed Option Pack
4) installed FPSE 2k from the Office 2000 disk
5) setup the FPSE extensions in the FP MMC (just the email support stuff and
6) created the virtual client in a directory (D:\inetpub\virtual
7) Set the web site up in IIS MMC with HTTP 1.1 header settings
8) Installed FPSE on the new web using the task menu under IIS MMC
9) Went to my computer and started FP 2000 (only a 166 some I had time to do
the other steps ;-))
10) Added a user to either the Main NT domain or (if the computer is not a
BDC) added a user to the local NT SAM.
11) set the new users main NT group to my FP Authors group
12) Went back to my computer and load new Virtual web site
13) In FP I go to security and give author and browser to new NT user and
remove (or reset) all other permissions the only person with Admin
permissions is the Administrators Group
14) Called customer and told him to user the new NT user name to edit his
As far as FP98 is concerned most of my customers have not reported any
conflicts with the new FPSE 2K.
and if they did I would tell them to go out and buy office 2000 just because
FP 2000 is soooooooooo much better then fp98.
I hope this helps.
P.S. I noticed someone on this thread said their customer had a good ecom
plugin for FP 2K. I don't suppose you could email me with which one that
Will ,,,=^. .^=,,,
"Link Locally ~ Surf Globally©" http://www.greennet.net
Come Play On The Best Quake Server in the Northeast
Serving Eastern Massachusetts and Southern New Hampshire
TEL: 978-363-8898 FAX: 978-363-1225 email:email@example.com
----- Original Message -----
From: Jeff Woods <firstname.lastname@example.org>
Sent: Wednesday, September 22, 1999 3:17 PM
Subject: Re: [NTISP] frontpage 2000 server Extensions
> I did the upgrade at the behest of a client who wanted to install a
> shopping cart / E-Commerce package that claimed to require FPSE 2K. This
> client brings me a LOT of hosting business, so I obliged. It BROKE the
> existing FPSE 98 in the process, and I couldn't get FPSE 2K to allow an
> install, for the reason I quoted below. I *did* manage to get it going
> since, in desperation, and here's what I wrote to that client about the
> solution. Perhaps it will help some here:
> I have SOLVED the problem for FPSE 2K by the brute force method....
> "Unable to create a web for the URL "/" because its root directory,
> "d:\docs\aeicomp\" falls below the root of another web int he directory,
> There *is* no web at d:\docs. I've spent hours trying to solve this one,
> and cannot.
> Well, turns out that the initial installation of IIS asks for the home
> directory, where all future sites will be located. This defaults to:
> c:\iis\wwwroot (or some such tree, wwwroot being the end, on C:)
> Ick. C: sucks. 2 GB limit on the boot drive under NT, and for safety
> and recovery, I make it a FAT drive, not NTFS (thus you can access the
> drive by botting with a DOS floppy if you just MUST). But a FAT drive
> cannot have any security, hence no FPSE. (No, don't think that far
> of me, I didn't do THAT).
> Since I couldn't abide by having the web docs stored on a non-secure FAT
> partition, I typed in a new location where permitted, during the Option
> Pack installation:
> D:\DOCS (A many-gigabyte NTFS partition)
> IIS then creates a DEFAULT WEB SITE in that directory! I always KILL
> site, since that's NOT what I want. I then install all directories
> Since they are all "on par" with each other, no site in a subdirectory of
> another site (by definition, no "sub-webs" exist), there should be no
> problem, right?
> Remember that default web site it creates in the first directory you give
> it? That was d:\docs, right? Well, I removed the site from the IIS
> pages using the MMC console, so there shouldn't be a front page web
> there. But THERE WAS.
> Deep inspection found _vti_cnf and other _vti* directories in d:\docs, the
> usual hidden directories. I didn't think to look there for them, because
> did not remember there ever being a web installed at that "top level".
> I stopped the web server, and removed these directories. I then re-BOOTED
> the web server, and again tried to apply FPSE 2K to the site.
> I did *not* get the error from before, and I do seem to have the ability
> now use the FPSE 2K tab in the MMC console, which I never could do before.
> I have also been able to open the web (as Administrator) using FP98, and
> have confirmed that the NT SAM account has proper permissions even now.
> At 12:28 PM 9/22/99 -0600, you wrote:
> >I am sure FP98SE do not support all 2000 functions, but FP2000 on the
> >end will interface fine with the FP98SE. I have used it plenty lately.
> >So, what am I missing, and why should we install the FP2000SE then?
> >----- Original Message -----
> >From: Jeff Woods <email@example.com>
> >To: <firstname.lastname@example.org>
> >Sent: Wednesday, September 22, 1999 8:34 AM
> >Subject: Re: [NTISP] frontpage 2000 server Extensions
> > > INSTALLING isn't the problem. RUNNING is. <sigh>
> > >
> > > If you locate a clue, could I borrow it? Here's what I ran into:
> > >
> > > Install went OK, but when I try to set up FPSE2K on a site, I am told:
> > >
> > > "Unable to create a web for the URL "/" because its root directory,
> > > "d:\docs\aeicomp\" falls below the root of another web int he
> > > "d:\docs".
> > >
> > > There *is* no web at d:\docs. I've spent hours trying to solve this
> > > and cannot.
> > >
> > > At this point, I'm unable to even go back to FPSE98 without nuking the
> > > site, either. Right now, I'm without FPSE at all, and will likely
> > >
> > > At 09:02 AM 9/22/99 -0500, you wrote:
> > > >HI
> > > >
> > > >Can anyone lead to some good doc. on how to install FrontPage 2000
> > > >Extensions on to iis 4.0 server.
> > > >
> > > >Thanks
> > > >Thomas
> > > >
> > > >
> > >
> > >
> > > For more information about this list (including removal) go to:
> > > http://www.iea-software.com/support/maillists/liststart
> >For more information about this list (including removal) go to:
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: