12-05-05 10:55 PM
Just open the site in FP and publish to the new location/server.
You will have to recreate any permissions/groups, etc. on the new server.
Also Windows 2003 Server by default has many features/option disable by defa
ult, that where enabled
by default under prior versions of Window Server
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
========================================
======
"KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message
news:AD07B428-6768-423A-89F0-FD48787C1DD6@microsoft.com...
> Hello folks...
>
> looking for some general points, suggestions, recommendations, etc on the
> process of migrating a FPSE 2002 (5.0.2.4330) enabled site currently runni
ng
> on an IIS5 Win2K Adv Server box to one running IIS 6 Win2003 Web Edition (
32
> bit).
>
> Looks like IIS 6 includes FPSE 2002 within their Application server
> configurations (not sure of exact version).
>
> SSL Certificate will be "moved" in accordance with Verisign's procedures.
> Content should be straightforward... re-publish entire site to new box.
>
> What about administratively?
>
> FrontPage Publishing groups?
> Users & Roles?
> Windows Accounts (non-domain users)?
>
> Another *assumption* is that any applications (PDF Writer, etc) will need
to
> be re-installed from original media nad patched appropriately...
>
> any other GOTCHAS I need to be on the lookout for?
>
> any nice whitepapers out there for procedures like this?
>
> Thanks Much.
[ Post a follow-up to this message ]
|