NT migration via Hyper V
Is it possible to install NT4 on a Hyper-V vhd and upgrade it to W2003 then transfer the roles to a 2 year old W2003 server or is it just best to bring in an old box and do the same.
They are adding a W2008R2 SQL server that could be used for the VHD?
I am concerned that there might be hardware issues on the NT install (I know it is not supported but it will be temp only).
They are adding a W2008R2 SQL server that could be used for the VHD?
I am concerned that there might be hardware issues on the NT install (I know it is not supported but it will be temp only).
ASKER
I am migrating from NT 4 to AD.
There is an existing PDC NT on the network that needs to retire.
I was going to install new install as BDC ~ promote to PDC and upgrade to W2003.
Then transfer roles to existing W2003 svr after DCPROMO.
Retire both old NT4 box and the VHD.
I don't think the old box will take an upgrade and it is SOP to have a BDC if the upgrade fails or kills the PDC via upgrade.
There is an existing PDC NT on the network that needs to retire.
I was going to install new install as BDC ~ promote to PDC and upgrade to W2003.
Then transfer roles to existing W2003 svr after DCPROMO.
Retire both old NT4 box and the VHD.
I don't think the old box will take an upgrade and it is SOP to have a BDC if the upgrade fails or kills the PDC via upgrade.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Anyone esle with experience migrating an NT4 domain using HyperV?
I am not sure that you are going to find somebody that has had an experience with NT4 under Hyper-V. I think, kevinhsieh’s suggestion is the only valid one.
I have a question: are planning to run Hyper-V on the same server as SQL Server? Not a good idea. SQL Server tends to take all available memory if you do not limit it and at some point you won’t be able to start your virtual machine.
If it is just temporary, just for the migration, you could use the trail version of Windows Server 2008 on any 64-bit computer with 4GB of RAM that supports hardware virtualization as a Hyper-V host and perform the migration there.
Or, under Windows Server 2003 you can install the old Microsoft Virtual Server 2005 R2 and perform the migration there.
I have a question: are planning to run Hyper-V on the same server as SQL Server? Not a good idea. SQL Server tends to take all available memory if you do not limit it and at some point you won’t be able to start your virtual machine.
If it is just temporary, just for the migration, you could use the trail version of Windows Server 2008 on any 64-bit computer with 4GB of RAM that supports hardware virtualization as a Hyper-V host and perform the migration there.
Or, under Windows Server 2003 you can install the old Microsoft Virtual Server 2005 R2 and perform the migration there.
ASKER
Just to update everyone.
I did successfully install NT4 on Hyper V then upgrade to W2003.
Note: it installed fine but had to do some partition resizing to allow for the SP2 on W2003.
I could not get any resize tools to work on NT (even after SP6a) but did work on W2003.
No other real issues but for NT must use the legacy NIC, IDE and note that you must use an ISO for loading the OS and check NT box in the CPU. The upgrade went fine and was able to load Integration Services on W2003.
That was in test environment so now the real thing.
I did successfully install NT4 on Hyper V then upgrade to W2003.
Note: it installed fine but had to do some partition resizing to allow for the SP2 on W2003.
I could not get any resize tools to work on NT (even after SP6a) but did work on W2003.
No other real issues but for NT must use the legacy NIC, IDE and note that you must use an ISO for loading the OS and check NT box in the CPU. The upgrade went fine and was able to load Integration Services on W2003.
That was in test environment so now the real thing.
ASKER
Not exactly the total solution but still pretty good.
So, I think you can get NT 4 to run, but I am questioning the reason for doing so. Are you taking an existing Windows NT 4 server and trying to move the data/services overto Windows 2003? Are you thinking about doing a physical to virtual conversion?