Creating a Windows NT VM- P2V

[guest]

Q: I am trying to migrate a Windows NT SP4 server into a VM on VS 2005. Client
(obviously) is running on old hardware but can't upgrade the manufacturing
application, can't even go to SP6.

I tried using the process of converting to a VMWare VM then using the
vmdk2vhd utility and running a tape restore. Each time I get the stop 7B
inaccessible oot device B.S.O.D.

It's coming from an HP Netserver with a RAID controller.
With NT4 not ale to detect hardware, is there any way I am going to be able
to get this to work? I went though the registry and set all the oddball SCSI
and RAID drivers to disabled.

I've read the MS convert utility is a pain in the ass and not worth it if
you're only doing 1 machine, but if I could be told it would work, I'd go
through the process.

Are their VM specific drivers I can load before the tape backup (or whatever
process I use) that would work when it loads on the VM?

A: Firstly, I would like to say that based on my Microsoft solutions, they all
need the Windows NT 4.0 Sp6. However, the current Windows NT 4.0 server is
Sp4. I am sorry to say that you must upgrade the current Windows NT 4.0
server to at least SP6.

After you update the Windows NT 4.0 server to Sp6, you could use the
following tool to migrate the Windows NT 4.0 sp6 server to a Virtual
Machine on Virtual Server:

Virtual Server 2005 Migration Toolkit
http://technet.microsoft.com/en-us/virt ... 76674.aspx

Also please note that Windows NT 4.0 support is no longer available for
this product. As of December 31, 2004, support for Windows NT 4.0 Server
and Terminal Server have been discontinued. Windows NT workstation Support
was ended earlier on June 30, 2004 (See
http://support.microsoft.com/?scid=gp%2flifean5)

The partner managed newsgroup support policy is based on the product
lifecycle used by Product Support Services:

http://support.microsoft.com/lifecycle/