frontpage intranet migration website strategy with a twist

[Steve Stewart]

Hi all,

I'm hoping to get some assurance or advice on this. I posted a
previous post but didn't realize that there is a twist in my
environment.

Scenario:

Migrating from an old SBS 2000 server to a SBS 2003 Server. A user has
developed an internal website that is located on a shared drive on the
old server.

Twist:

The user does not publish the website from her local client machine
harddrive to the server share. She is working on the live share and
does not publish at all. Users browse to the share and locate the
index.htm file to use the intranet.

What I've done:

I'm halfway through the migration and am moving email and data. Before
I started the migration this evening, I opened her Frontpage 2002 that
defaults to the server share and published a copy of the website to
the local hard drive.

I also installed Frontpage 2003 and repeated the process to another
directory on the local hard drive in the event that the 2003 version
of the software has some magical features.

What I need to do:

After I have my new SBS 2003 server up and running, I'm curious how to
proceed. Do I just create a new empty web folder on the new server,
open a local copy of the website (that I created on the hard drive)
and publish to the server share? Is there anything else I need to do
to make this fully functional? Should I be concerned with any IIS or
Sharepoint service that come installed on the SBS 2003 box?

Thanks for your advice. I'm sure this is an easy one, but I'm not
familiar with how to get Frontpage to interact with in house servers
correctly.

Thanks!

Steve

 

[Jim Buyens]

Howdy.

Generally, you would open the root Web on the old box and
then publish it (including subwebs) to ten new box.

If you want to publish it to another share, fine, but for
more functionality you could create an IIS virtual
server, install the FrontPage Server Extensions, and then
publish to that location.

The extra functionality would involve things like
database access, sending mail, saving submitted form
results, and running ASP or ASP.NET pages.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Steve Stewart]

Let me start off by mentioning that I am a pretty decent network SBS
person, but am completely absent minded in the world of IIS. I do have
decent experience with Frontpage and publishing to third party WWW
sites. I have a newly integrated Small Business Server 2003 and I'm
trying to publish a website via FrontPage. the problem is occuring at
the client's office and in my test lab, which raises the administrator
error flag pretty high. Here are my thoughts and processes for
attempting to publish a frontpage website.


1. Creating a directory on the server.
2. Opening IIS and creating a new website using server ip address,
port 80, and a host header titled intranet
3. Specifying the path the the directory I created in step 1.
4. Setting access permissions..read, write, etc.
5. Right clicking on my new website in IIS and configuring FP 2002
frontpage extensions
6. Opening up Frontpage 2003 and attempting to publish website
7. Receive error that url cannot be found.


I know that I'm missing a step somewhere, but for the life of me I
can't determine what it is, and I'm running the risk of messing up the
default sharepoint websites that come with SBS by taking pot shots at
it.

Does anyone have any clues or suggestions?

Thanks in advance!

 

[Jim Buyens]

Actually, at step 2, I would

2. Go to Local Area Conenction Properties, open TCP/IP Properties, and
assign a second IP address. Then, go to DNS Manager and set up a CNAME
pointing to that new address. Then, openg IIS and create a new website
the new ip address, port 80, and no host header.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------