Virtualizing Windows NT BDC

[hdoan53]

We have vSphere 5 in place and try to upgrade Windows NT 4 domain to Windows Server 2003 AD.  I am running into a road block creating a  Windows NT 4 BDC virtual machine and join the NT 4 domain.

VMware suggests that do not convert physical NT 4 domain controller but to create a VM as a BDC and join the NT domain then promote it to the PDC then upgrade the PDC to Windows 2003.

When I create the VM as Windows NT BDC, I have to join the NT domain.  However, I can't join the NT domain since the network card does not work without SP6 install.  I have tried AMD and E1000 network card under the VM but none works without SP6.

Opened a ticket with VMware tech support and was told VMware does not support NT without SP6.  He suggested me to slipstream SP6 to NT installation disk but I haven't found a way to do it since slipstream service pack is not an option for Windows NT.

If you have figured out how to create the VM as Windows NT 4 BDC and join the existing domain without SP6, please let me know.  Otherwise, if you know how to slipstream SP6 into Windows NT 4 installation that should work too.

Thanks,

Hien Doan

[MartinAmaro]

As yuo already know split stream is not an option for NT 4.0, the only option will be for you to build the NT 4.0 with sp6 server using physical hardware then P2V it.

or I think you can install it on VMware workstation or Server then migrate it to ESX. (see this article)

http://partnerweb.vmware.com/GOSIG/Windows_NT_4.html

[hdoan53]

Hi Martin,

I have seen many issues (BSOD) with converting a physical NT domain controller and VMware does not recommend it.

The link you sent is good for installing a workstation or server but not a BDC.  With a workstation or server I can ignore the network and move on but I can't with a BDC, the network adapter must have an IP address to join the domain before finishing the installation, I can't pass this point since without SP6 I can assign the IP address or use DHCP but the IP address for the BDC VM is not pingable.

Hien Doan

[rickardnobel]

Good old Windows NT, I have almost forgotten the part that the BDC must join the domain at installation time..

However, perhaps you could install NT4 on some physical server or PC as a BDC, then promote it to PDC, then upgrade it to Windows 2000 or 2003 (and by such Active Directory). Then you could use a VM with Win 2003 and run dcpromo and transfer the domain database into that. After this you could remove the two physical machines.

[MartinAmaro]

You are correct VMware does not recommend it but it provides specific instructions if you dont have a choise but to P2V it (see below) . I have done it several times without a problems for different clients and as you already know trying to P2V does not introduce a risk. However; the instructions from rickardnobel sound like the will do the job.

Windows NT

Converting  a Windows NT domain controller is a very involved process that may be  trouble prone. VMware does not recommend converting a Windows NT domain  controller if at all possible.

(see link for step by step instructions)

http://communities.vmware.com/message/1054290

[hdoan53]

Hi Martin,

I got another advice using virtual hardware version 4 so I downloaded ESX 3.5 and created the BDC under ESX 3.5 host.  The BDC can join NT domain during the installation without SP6.  I then upgrade the BDC to SP6 and use vConverter to convert the BDC to ESXi v5 host.  Works like a charm.

Thanks for your suggestions but finding an old desktop or dealing with SCSI drivers under NT is no fund.

Hien Doan

[MartinAmaro]

Great!