Discussion Locked

Need to Move from NT4/IIS4 to W2K/IIS5

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have recently been assigned the task of maintaining the servers in a small NT hosting centre. These servers were never set up properly and have not been maintained or even backed up for almost a year! I have some experience with installing/maintaining NT4/IIS4/SQL Server 7.0 servers, but most of my experience has been in the development arena, where I was more concerned with VSS configurations than performance/security.

Let me note from the beginning that there is absolutely NO DOCUMENTATION, and the staff who knew anything about these servers are gone.

Currently, the setup is as follows (I don't have the hardware specs yet):

- SERVER A: NT4/IIS4 webserver hosting approximately 200 personal/small business sites
- SERVER B: NT4/IIS4 webserver hosting 1 corporate site and all client ftp sites
- SERVER C: NT4/SQL Server 7.0 server that has 2 databases (more in the future)

I need to reinstall A (not upgrade), and put W2K/IIS5 on it, as well as SQL7, because B is to be removed from the system. I would like to remove C as well, but right now I am not sure why these FTP sites even exist - I know I can move the corporate site to A.

I have been trying to find out if it is possible to export the IIS4 settings for import into IIS5, once A is reinstalled. If not, do I have to manually document each of the 200 sites before reinstalling, then manually configure each site on IIS5? I also need to know what a good security model for this setup would be. I don't believe I will want to migrate the existing model because I think it is not very secure.

Also, I need recommendations for a proper backup solution. I plan to use GFS, but need to know which software works best for W2K.

1 more thing, since I am on a different site than the servers, I would like to use pcANYWHERE to manage them, but I am concerned that this would cause security issues - any comments on this?

thanks

8 replies

by gpwruck

I can help with the pcANYWHERE part of your question. I have been using pcANYWHERE for three years to manage computers remotely and if you are going to dial into pcANYWHERE you just need to set in to call you back. If you are going to use TCP/IP to get in, you can set pcANYWHERE to Windows NT security and allow only your login to be active. It can be set to allow logins at specific times and/or days. After you login to pcANYWHERE, you will have to login to the Windows 2000. If you use all of these security setting it would be hard for anyone to get in. Not impossible, but no remote management system is foolproof.

gpwruck

by russ werner

I upgraded a NT server to a Win2000 server and was able, once installed, copy all the files and folders under the NT wwwroot to the 2000 wwwroot. But I saw no provisions for exporting or importing all the settings of IIS itself. I am afraid that is going to be a manual job on your end.
As far as the PCAnywhere, I use it, and it works well. The answer number 1 above explained the provisions well.
I backup the wwwroot folders and files to another hard drive as backup, and then use the Win 2000 backup program separetly, to back everything again to the other hard drive. Make sure you enable the backing up of the registery. Hope it helped?

by kt100

I plan to backup the websites & registry before I do anything to the server. (I'm terrified this thing is going to totally blow up on me) I guess my real question is, how do I minimize downtime while reinstalling the server? I'm thinking my only option may be to install another temporary box, move the sites over to that, then reinstall Server A from scratch, implement a real security model, then move all the sites back over again.

Also, I have been researching this issue and have found somemention of an IIS "metabase" that contains the IIS config, which apparently is similar to the registry, that can apparently be imported/exported. Does anyone know anything about this? (I know I am probably grasping at straws here, but I am really trying to avoid manually setting up 200 sites!)

As for pcANYWHERE, since I have two expert votes for it being secure, I will try not to fear using it!

thanks

by carydahl

I have used PCanywhere in the past and if you are going to be running Windows 2000 you should use terminal server that is included. The transmission are encrypted, uses NT authentication, and the RDP protocol is much faster than PCanywhere. You can configure VPN, RAS, or some other remote access solution. RDP uses port 3389

This discussion is closed to new replies.