Home > Windows 2000 > Windows 2000 Blue Screen After P2v

Windows 2000 Blue Screen After P2v

I find these issues occur much more often on Windows 2000 due to its age. Power on the source for the conversion. Use vConverter to convert image to the ESX server, it knows about it natively and is usually seemless 0 LVL 21 Overall: Level 21 VMware 19 Virtualization 8 Message Assisted but my memory is sometimes poor! 0 Top 6 Sources for Identifying Threat Actor TTPs Promoted by Recorded Future Understanding your enemy is essential. his comment is here

Back in the day the very best conversion utilty was PlateSpin PowerConvert. After that, the P2v works and your Windows 2000 machine will not blue screen. All is well until you boot the new VM… FAILURE. share|improve this answer answered Jun 1 '09 at 16:22 Sage 1112 This worked for me, as well.

Write contents of the image onto a floppy diskette and insert the diskette into the physical source. Didn't help. 4. I copied the known working copy of SCSIPORT.SYS from C:\WINNT\System32\Drivers to my second drive (E:\WINNT\System32\Drivers\SCSIPORT.SYS). Tagsactive directory adam android autoview backup cert citrix composer equallogic error firewall firmware flipfactory gpo hiding ipad iscsi mks p2v pcoip powercli powershell reboot recompose replication reset san sanhq security ssl

Why? Is there anything I can do to get the vm to boot? The PC is a standard Pentium with IDE disk from circa 2001. Since I’m using virtual machines and already had a Windows 2000 VM template, I deployed a copy of my Windows 2000 template and attached my P2Ved C: drive as a second

It was spendy but well worth the cost for P2V-ing old operating systems. Bookmark the permalink. We’ll assume you are using Windows 2003 media. http://www.bonusbits.com/main/HowTo:Fix_Windows_2000_Vmware_P2V_BSOD_with_KMODE_EXCEPTION_NOT_HANDLED I am lost for ideas, normally p2v of a basic IDE pc works flawlessly.

Click the operating system that you want to repair, and then click Next. When we experienced it, I seemed to recall that the issue was due to the driver in a post Rollup hotfix causing the issue, hence reverting back to the rollup version Injecting SCSI controller device drivers into Windows (VMware KB 1005208). Repeat server prepare steps and start P2V wizard from VMware Converter. 4.

One Comment Tweets that mention Windows 2000 P2V in vCenter Converter 4: No more BSoD « Virtual Andy -- Topsy.com 2011-02-17 at 9:06 pm […] This post was mentioned on Twitter http://enterpriseadmins.org/blog/virtualization/windows-2000-p2v-blue-screens/ Extract the disk image into files and copy them to the source. Go find an ISO or DVD of any of the operating systems just listed in the title. However - the only thing that I did to fix it was downloaded the SP4 rollup, installed in on the Windows 2000 server and reran the VConvertor to do a P2V

Prepare to boot your VM from this media. this content I started searching and found it on some other W2k server. The latest version back then was VMware vCenter Converter Standalone 4.3.ReplyDeleteAdd commentLoad more... I downloaded and extracted Hotfix from KB904374 and copied files to virtualized server.

We’re going to use the recovery console. Why would the physical disk geometry change in the VM? Start "Add new hardware" from Control panel. weblink It simply means the path to load Windows cannot be found by the boot loader.

It is painful. The OS lacks many of the hardware compatibility features that make Server 2008 really easy, and Server 2003 relatively easy to move between hardware. If an operating system is not found simply continue anyway Type the following command in this order to set your system straight: bootrec /fixmbr (Fixes MBR) bootrec /fixboot (Fixes Boot Sector)

It says STOP: 0x0000001E (0xC0000005,0x804a6467,0x00000000,0x000000B0).

This was also my suggestion for the customer. I tried to re-run the P2V several times and even tried including the diagnostic partition in my VM. Go find an ISO or DVD of any of the operating systems just listed in the title. I had the same issue with another similiar server, but i fixed it by changing the SCSI host adapter type from Bus Logic to LSI.

Thanks a bunch. 0 Featured Post Why You Should Analyze Threat Actor TTPs Promoted by Recorded Future After years of analyzing threat actor behavior, it’s become clear that at any given I tried it and it didn't help. 2. What fixed the issue was the info initially provided by za_mkh. check over here If you didn't get my point - Server 2000 is not a simplt point and click convert.