We currently have a ftp server at work(which is also a DMZ) that we want to upgrade to Windows 2003. Is there a guide out there that can walk me through how to perform this upgrade to where the user accounts get migrated and
how setting up FTP would be done on the new server?
Firstly, don't "upgrade" to Windows Server 2003. Extended support ends in three years so you should seriously think about upgrading instead to Windows Server 2008 R2. It has a raft of benefits (especially for FTP!) over and above IIS6 in Windows Server 2003.
Secondly, don't think of it as a migration. Build your new solution in a lab/test environment. Get yourself a trial version of VMWare Workstation, build a server (use an evaluation copy of Windows Server 2008 R2 if you have to) and FAMILIARISE yourself with
the product. How you migrate from the old to the new will come after you know about the technology.
People tend not to want to lead others by their hand and instead seek to encourage them to choose to learn by reading and learning as you go. You'll get more answers if you cover off the bulk of the work yourself and come here asking for help on specific
things you're struggling with.
Good luck.
Marked as answer by Lloydz on Apr 02, 2012 01:30 AM
l3c03
2 Posts
migrating ftp server on Windows 2000 to Windows 2003 process
Mar 26, 2012 03:20 PM|LINK
Hi,
<div class="body">We currently have a ftp server at work(which is also a DMZ) that we want to upgrade to Windows 2003. Is there a guide out there that can walk me through how to perform this upgrade to where the user accounts get migrated and how setting up FTP would be done on the new server?
Thanks for any help anyone can provide.
</div>lwsrbrts
15 Posts
Re: migrating ftp server on Windows 2000 to Windows 2003 process
Mar 27, 2012 06:44 PM|LINK
Firstly, don't "upgrade" to Windows Server 2003. Extended support ends in three years so you should seriously think about upgrading instead to Windows Server 2008 R2. It has a raft of benefits (especially for FTP!) over and above IIS6 in Windows Server 2003.
Secondly, don't think of it as a migration. Build your new solution in a lab/test environment. Get yourself a trial version of VMWare Workstation, build a server (use an evaluation copy of Windows Server 2008 R2 if you have to) and FAMILIARISE yourself with the product. How you migrate from the old to the new will come after you know about the technology.
People tend not to want to lead others by their hand and instead seek to encourage them to choose to learn by reading and learning as you go. You'll get more answers if you cover off the bulk of the work yourself and come here asking for help on specific things you're struggling with.
Good luck.