I'm restoring a bunch of websites from a dead Windows 2000 server onto a
windows 2003 server. This entails reinstallation of the FrontPage extensions
on each site. At the moment on a couple of test server I'm finding it takes
10-15 minutes to install the extensions on a new, empty website. When a site
has data it's taking even longer!

With several hundred sites to restore this is going to take a couple of
weeks!

The test servers are windows 2003 standard, all latest patches installed,
Athlon 2.2Ghz, 1Gb ram. Nothing else running, just installing FPSE on a
website with no files and no folders.

Anyone got an suggestions on how to improve the speed?

thanks,
david

[ Post a follow-up to this message ]

When you say install, do you mean install the extensions from scratch to the
server, or do you mean configure the extensions for the site with extensions
already installed on the server?
--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/of...etid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/fro...fo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/un...ding/frontpage/
===
"Asgard Hostmaster" <hostmaster_remove_@asgard.net> wrote in message
news:%23zbCvQTFFHA.2828@TK2MSFTNGP09.phx.gbl...
| I'm restoring a bunch of websites from a dead Windows 2000 server onto a
| windows 2003 server. This entails reinstallation of the FrontPage
extensions
| on each site. At the moment on a couple of test server I'm finding it
takes
| 10-15 minutes to install the extensions on a new, empty website. When a
site
| has data it's taking even longer!
|
| With several hundred sites to restore this is going to take a couple of
| weeks!
|
| The test servers are windows 2003 standard, all latest patches installed,
| Athlon 2.2Ghz, 1Gb ram. Nothing else running, just installing FPSE on a
| website with no files and no folders.
|
| Anyone got an suggestions on how to improve the speed?
|
| thanks,
| david
|
|

[ Post a follow-up to this message ]

I mean configuring to a site

"Tom Pepper Willett" <tompepper@mvps.org> wrote in message
news:eW7OZzTFFHA.2156@TK2MSFTNGP10.phx.gbl...
> When you say install, do you mean install the extensions from scratch to
> the
> server, or do you mean configure the extensions for the site with
> extensions
> already installed on the server?
> --
> ===
> Tom "Pepper" Willett
> Microsoft MVP - FrontPage
> ---
> About FrontPage 2003:
>  http://office.microsoft.com/home/of...etid=FX01085802
> FrontPage 2003 Product Information:
>  http://www.microsoft.com/office/fro...fo/default.mspx
> Understanding FrontPage:
>  http://msdn.microsoft.com/office/un...ding/frontpage/
> ===
> "Asgard Hostmaster" <hostmaster_remove_@asgard.net> wrote in message
> news:%23zbCvQTFFHA.2828@TK2MSFTNGP09.phx.gbl...
> | I'm restoring a bunch of websites from a dead Windows 2000 server onto a
> | windows 2003 server. This entails reinstallation of the FrontPage
> extensions
> | on each site. At the moment on a couple of test server I'm finding it
> takes
> | 10-15 minutes to install the extensions on a new, empty website. When a
> site
> | has data it's taking even longer!
> |
> | With several hundred sites to restore this is going to take a couple of
> | weeks!
> |
> | The test servers are windows 2003 standard, all latest patches
> installed,
> | Athlon 2.2Ghz, 1Gb ram. Nothing else running, just installing FPSE on a
> | website with no files and no folders.
> |
> | Anyone got an suggestions on how to improve the speed?
> |
> | thanks,
> | david
> |
> |
>
>

[ Post a follow-up to this message ]

Hmmm,
I've just tried running FileMon and RegMon from Sysinternals to see if I
could see what was going on ... very very  interesting ....

The site I am testing is pointed to c:\inetpub\test. There are no files or
subfolders.

When I run the extensions install, the w3wp.exe process starts to query
*every folder* in c:\inetpub with "QUERY SECURITY" and "QUERY INFORMATION"

All the websites are in that folder, so that's a LOT of folders and files.
Note that these folders are not and have never been configured as websites
on this machine.

So, for a test I moved all the folders out of c:\inetpub\clients and in to
c:\clients. I then reran the FP install on c:\inetpub\test .... and it
configured in seconds!!!

So, installing FP extensions on c:\inetpub\test causes IIS to for some
reason query all the files in c:\inetpub. That is odd .... I'll experiment
further .....


"Asgard Hostmaster" <hostmaster_remove_@asgard.net> wrote in message
news:%23RE2d5TFFHA.1836@tk2msftngp13.phx.gbl...
>I mean configuring to a site
>
> "Tom Pepper Willett" <tompepper@mvps.org> wrote in message
> news:eW7OZzTFFHA.2156@TK2MSFTNGP10.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Further findings ...

When configuring FPSE on a site with a root of c:\inetpub\test, it caused
the server (ie w3wp.exe) to enumerate every folder in c:\inetpub, including
the very large c:\inetpub\clients, causing installation to take a looonngg
time, up to half an hour. I moved other folders out of there to c:\clients
and configured FPSE on the site and they installed in seconds..

So, I just moved the test site to c:\clients\test to see what would happen
when I tried configuring FPSE on the site. Low and behold, w3wp.exe is
enumerating every folder in c:\clients.

Next test was to move the site to c:\clients\test\test. Installs in
seconds!!!!

So it looks like installation of FPSE cause enumeration of the parent
folder. To prevent this causing problems then each site needs to be down an
extra level.

very bloody annoying .....

[ Post a follow-up to this message ]