Re: Move WSS 2.0 to a new server

The problem is I want to move the WSS 2.0 to tthe new server before I
upgrade. How could I accomplish that?

"Mike Walsh" wrote:

I'd upgrade the old server to WSS 3.0 and then move it.

That way you have more options including only transferring some content
rather than the whole site.

Mike Walsh
WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
no questions by e-mail please



George Schneider wrote:
I have our current WSS 2.0 server on a sever name server1. Thes ite is
called server1:1080. I want to move this to a new server I just bought since
the old server is about t be taken offline and retired. How cna I best
accomplish this? The curren ws 2.0 runs on a sql 2000 server. The new
server I want to use the internalsql database since the plan is to after the
move to the newe server to upgrade to wss 3.0.

.

Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: upgrade wizard 6.5 to 2000
    ... I finally figured out a way to accomplish the upgrade... ... why the heck couldn't the darn Wizard figure out ... > But my import server IS sql server 2000! ...
    (microsoft.public.sqlserver.setup)
Loading