vCenter

 View Only
  • 1.  Problem converting windows 2000 with SP3

    Posted Nov 29, 2009 07:26 PM

    I am having numerous issue converting an old windows 2000 SP3 server (HP DL360 G something with 2 onboard NIC) to our esx 3.5i environment. I try to use the latest standalone converter 4.0.1, but it looks like it doesn't support w2k sp3 (sp4 minimum) and fair before it even begain. When I trying to use the Cold Boot CD that come with vCenter, I am running in another set of problem. I have try to set a static IP on both of the NIC, but for what ever reason, after I hit apply, I can't ping to the IP address I just set, nor can the converter problem seem to get to the network. This is a HP server, so I would think the driver would be part of the cold boot cd image. Any though on this?



  • 2.  RE: Problem converting windows 2000 with SP3

    Posted Nov 29, 2009 10:03 PM

    for Win 2000-sp3 use ghost/acronis + DriverInjectionGUI from your favorite PE-LiveCD

    Converter needs SP4




    ___________________________________

    VMX-parameters- VMware-liveCD - VM-Sickbay



  • 3.  RE: Problem converting windows 2000 with SP3

    Posted Nov 30, 2009 02:40 AM

    So the problem is with SP3 or the NIC? Is there any reason why the NIC is not working?



  • 4.  RE: Problem converting windows 2000 with SP3

    Posted Nov 30, 2009 03:12 AM

    both I guess - afaik converter 3.0.3 also assumes SP4 as minimum requirement for 2000.

    Have you checked if the network-driver is included ?

    I would not waste time with Converter on this case - this is something for the driverinjection-tool I already mentioned






    ___________________________________

    VMX-parameters- VMware-liveCD - VM-Sickbay