Question Locked

Migrating to new server (Win 2k3)

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

I've started in a business where there is one server & DC (IBM xseries 226) running AD, DNS, DHCP, WINS, File & Print Services.

I discovered that it was bought second hand a few years ago, and has only 1GB ram! Also only 500MB free on primary partition. The network in our place is going down multiple times per week, group policies are being bypassed and there are multiple intermittent DNS/DHCP issues.

I got the go-ahead to purchase a new server, which is arriving later today. Luckily, I work in a college which is taking halloween holidays, so there is nobody accessing the network til next monday, so i have a bit of time to play with..

I'm just looking for information as to the best route to take with this new server.. IE: Should I migrate all services, or use old server as, lets say, a file and print server? The new server is brand new, very high spec, and our college is relatively small (90-100 nodes, 120+ users)

Some advice as to the best way to do this migration would be very helpful, as I said, I just started in this job 2 weeks ago, it's my first job since graduating, and it's my first time to install a new server.

3 replies

by forthman

I have 6 servers to upgrade.
Decided to go the VMware route.
My thinking is that this will allow me to grow the system without lots of new hardware.
Is a military support system.
VMware will let you down load a converter and ESXi for free.
Just finished the first server. Used the VMware converter on the "old" server. Was able to do the conversion while it was running. Loaded "new" system with ESXi.
The whole process took me about 2 hrs.
Take a look at VNware might be a way for you to go.

This discussion is closed to new replies.