How to move FrontPage Webs to a new computer?

  • Thread starter Thread starter BenC
  • Start date Start date
B

BenC

Does anybody have any suggestions for how to move a
FrontPage Web to a new computer without having to import
the web from the server. My problem is that I have over
200 FrontPage Webs on my computer and I need to upgrade to
a new computer. Importing each web from the server would
be very time consuming. I am looking for a shortcut. Any
advice would be appreciated!
 
If the remote (hosting service) server has the FP extensions, then you have
to open each site and publish it to the new computer.

For other possible solution, please provide info about your Windows versions
--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
-----Original Message-----
Does anybody have any suggestions for how to move a
FrontPage Web to a new computer without having to import
the web from the server. My problem is that I have over
200 FrontPage Webs on my computer and I need to upgrade
to a new computer. Importing each web from the server
would be very time consuming. I am looking for a
shortcut. Any advice would be appreciated!
Click to expand...

If the Webs are in a hierarchy (i.e. one root Web and 199
subwebs) just publish the Root Web, taking care to select
Include Subwebs in the Publish Web Dialog box.

Otherwise, I would get IIS and the FPSE working on the new
computer, then drag the whole InetPub folder from the old
box to the new one, excluding folders installed by IIS
itself. This will *probably* start working immediately but
after a quick test, I'd run Server Health and Recalculate
Hyperlinks, then test again.

Needless to say, don't format the old box until you're
sure everything survived the transition.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
Hi Jim,
A follow up question to your last answer. Using FP 2002 or 2003 would it be
considered "good practice" when publishing, to publish all changed pages
only for subwebs from the root web? Is there anything tricky to this as long
as all subwebs are arranged properly under the root?
 
-----Original Message-----
Hi Jim,
A follow up question to your last answer. Using FP 2002
or 2003 would it be considered "good practice" when
publishing, to publish all changed pages only for subwebs
from the root web?
Click to expand...

Yes, unless you suspect the target Web is damaged, or if
the Target Web doesn't exist yet. In those situations,
publishing "All Pages, Overwriting Pages Already On
Destination" is more reliable (in the first case) or
faster (in the second).
Is there anything tricky to this as long
as all subwebs are arranged properly under the root?
Click to expand...

No.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
 
Thanks a bunch.
Jim Buyens said:
Yes, unless you suspect the target Web is damaged, or if
the Target Web doesn't exist yet. In those situations,
publishing "All Pages, Overwriting Pages Already On
Destination" is more reliable (in the first case) or
faster (in the second).


No.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*
Click to expand...
 
PS
Just be aware that if any of the subwebs have unique permissions set, those will not publish and must be recreated on the new server

--




| Thanks a bunch.
| | > >-----Original Message-----
| > >Hi Jim,
| > >A follow up question to your last answer. Using FP 2002
| > >or 2003 would it be considered "good practice" when
| > >publishing, to publish all changed pages only for subwebs
| > >from the root web?
| >
| > Yes, unless you suspect the target Web is damaged, or if
| > the Target Web doesn't exist yet. In those situations,
| > publishing "All Pages, Overwriting Pages Already On
| > Destination" is more reliable (in the first case) or
| > faster (in the second).
| >
| > >Is there anything tricky to this as long
| > >as all subwebs are arranged properly under the root?
| >
| > No.
| >
| > Jim Buyens
| > Microsoft FrontPage MVP
| > http://www.interlacken.com
| > Author of:
| > *------------------------------------------------------*
| > |\----------------------------------------------------/|
| > || Microsoft Office FrontPage 2003 Inside Out ||
| > || Microsoft FrontPage Version 2002 Inside Out ||
| > || Web Database Development Step by Step .NET Edition ||
| > || Troubleshooting Microsoft FrontPage 2002 ||
| > || Faster Smarter Beginning Programming ||
| > || (All from Microsoft Press) ||
| > |/----------------------------------------------------\|
| > *------------------------------------------------------*
| >
| >
| > in message
| > >| > >> >-----Original Message-----
| > >> >Does anybody have any suggestions for how to move a
| > >> >FrontPage Web to a new computer without having to
| > import
| > >> >the web from the server. My problem is that I have over
| > >> >200 FrontPage Webs on my computer and I need to upgrade
| > >> >to a new computer. Importing each web from the server
| > >> >would be very time consuming. I am looking for a
| > >> >shortcut. Any advice would be appreciated!
| > >>
| > >> If the Webs are in a hierarchy (i.e. one root Web and
| > 199
| > >> subwebs) just publish the Root Web, taking care to
| > select
| > >> Include Subwebs in the Publish Web Dialog box.
| > >>
| > >> Otherwise, I would get IIS and the FPSE working on the
| > new
| > >> computer, then drag the whole InetPub folder from the
| > old
| > >> box to the new one, excluding folders installed by IIS
| > >> itself. This will *probably* start working immediately
| > but
| > >> after a quick test, I'd run Server Health and
| > Recalculate
| > >> Hyperlinks, then test again.
| > >>
| > >> Needless to say, don't format the old box until you're
| > >> sure everything survived the transition.
| > >>
| > >> Jim Buyens
| > >> Microsoft FrontPage MVP
| > >> http://www.interlacken.com
| > >> Author of:
| > >> *------------------------------------------------------*
| > >> |\----------------------------------------------------/|
| > >> || Microsoft Office FrontPage 2003 Inside Out ||
| > >> || Microsoft FrontPage Version 2002 Inside Out ||
| > >> || Web Database Development Step by Step .NET Edition ||
| > >> || Troubleshooting Microsoft FrontPage 2002 ||
| > >> || Faster Smarter Beginning Programming ||
| > >> || (All from Microsoft Press) ||
| > >> |/----------------------------------------------------\|
| > >> *------------------------------------------------------*
| > >>
| > >>
| > >>
| > >
| > >
| > >.
| > >
|
|
 
Back
Top