Need help to upgrade to 2008
Posted 16 November 2011 - 01:27 PM
We're planning to upgrade our network from 2003 to 2008 and would like to have some information on the steps.
Right now we have a 2003 network with several 2000 servers but they are used as application servers only.
We have 8 x 2003 servers (32 bit) standard in different locations. Two in the main office that one used as DC and the other one used as file server. Others act as secondary DCs in different offices.
I want to know if there is any way to directly upgrade the 2003 servers to 2008 x64 or I need to upgrade one by one. If I need to upgrade one by one, what would be the steps???
Thank you in advance for all your help.
Posted 17 November 2011 - 08:46 AM
Posted 16 December 2011 - 12:36 PM
Thanks for your suggestion.
Is there any way I can find step-by-step information to the upgrade?? I did some search from MS but wasn't able to find it.
I also want some information on 2000AD upgrade to 2008.
I post here for a month but seems nobody can help!!!!!
Could you help me on this??
Posted 18 December 2011 - 11:09 AM
Posted 18 December 2011 - 06:27 PM
Posted 18 December 2011 - 10:11 PM
This. That's the only way I would do it personally. And with a virtualization platform too (vSphere or Hyper-V).
I sure wouldn't want to be running 2008 or 2008 R2 on Win 2000/2003 era hardware.
Posted 19 December 2011 - 09:53 AM
Considering 2008 R2 comes with Hyper-V, and if the OP uses an enterprise or datacenter license, the first 4 VMs (or all of them, in datacenter's case) would be freely licensed), that would be the obvious choice in this case, at least to me.
Posted 19 December 2011 - 02:31 PM
1) Win2000 AD with several DCs they need to be upgraded to 2k8 but can only use the existing hardware (all Xeons)
2) Win 2k3 AD with several DCs and all x32,
3) Win 2k3 AD running r2 (x64).
All of them needed to be upgrade and have different requirements but none of them want to buy new hardware. That's why make me so confuse on how to work on them.
I'm looking for something like step-by-step information to follow with!! Please provide some help!!!!
Posted 19 December 2011 - 04:08 PM
Again, if I were you, I would *strongly* recommend they migrage and pony up for new hardware (even temporarily). Otherwise, you need to make sure they're aware that there WILL be downtime during the transition, as you will need to take full backups (disk2vhd is a good method, assuming the Windows partitions are 127GB or smaller) of EVERY DC IN THE ENVIRONMENT AT THE SAME TIME, and then migrate, carefully, one DC at a time (waiting between upgrades to make sure replication, auth, etc. are all still working after each DC is physically upgraded to the next OS. Also, given you may be going from 2000 to 2003, and then from 2003 to 2008 or 2008 R2, you will need to do everything TWICE, including a full environment backup of the 2000 environment, upgrading each and every DC (one at a time) pausing between each upgrade to make sure everything is working on each DC post-OS upgrade, and then (once you're at 2003 across the board) doing everything a second time (including a full environment backup of each DC).
Posted 19 December 2011 - 04:18 PM
Different strokes for different folks I guess. We're probably addressing different needs with vSphere (me) and Hyper-V (you). We use it as a thin "shim" (ESXi that is) to have an OS that will run/restore on any hardware (we've had to do it too), and some server consolidation too, whereas you're most likely using it for server consolidation. Hyper-V as a "host" is heavier and takes longer to install, and around here all consultants only support/recommend vSphere (we even rented a temp server that was running it), and we already had significant experience & investment in VMWare's solutions, so it was really a no-brainer for us (I'm not suggesting that's the one and only universal solution for everybody though)
As for his setup, I'm guessing he probably wants to use a bunch of separate DCs across different sites and for redundancy, which running a Enterprise or Datacenter edition with Hyper-V wouldn't really help for. But I'm sure it's a nice option for Datacenters and the like.
That essentially means nothing at all, besides that they're Intel CPUs that have been produced somewhere in the last 14 years. Xeons span from the Pentium 2-based Xeon @ 400MHz from 1998, all the way to Sandy Bridge based ones (like the latest 2nd generation i7's). For all we know, it could be P3-era hardware (that's fairly likely given the OS) that barely runs Win2k adequately. Combine that with older SCSI disks, slow single core CPUs, not so much RAM and the like, and you get something I definitely wouldn't want to upgrade to 2008 (essentially "Vista Server", not quite the same overhead as Win2k!) or 2008 R2. I would check the minimum requirements first. If you do attempt to upgrade ancient hardware, be prepared to roll back the old installation when the inevitable happens
Posted 19 December 2011 - 06:32 PM
Good luck to you - please do let us know how it goes.
Posted 20 December 2011 - 08:58 AM
Posted 20 December 2011 - 10:04 AM
Posted 27 December 2011 - 01:07 PM
Just want to update the status.
I started the process from the simple one (Case 3 from post #12).
I cloned the 2k3 DC to a VM and created another 2k8r2 VM and did the following:
a) I joined the 2k8 to the domain,
used "DCPromo" to upgrade the 2k8 server to be a DC.
From this step, I stucked. What is next step??
How can I take out the old DC??
How to transfer the AD information to the new DC??
How to move the data and login scripts to the new server?? (I used the DC as file server and DNS too).
Posted 28 December 2011 - 09:09 AM
- ← Uninstalling internet explorer9 x64 bit
- Windows Server 2008 / 2008R2 / 2012
- Window server 2008 R2 →