http://mattlog.net/2009/10/16/vmware-stop-0x0000005d/ All things IT Pro Wed, 14 Dec 2011 12:06:12 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://mattlog.net/2009/10/16/vmware-stop-0x0000005d/comment-page-1/#comment-26409 Jay Tue, 02 Aug 2011 15:51:11 +0000 http://mattlog.net/?p=246#comment-26409 Add to that: when I choose the 32bit 2k3 image during the deployment, it then pulls down the proper 32bit winpe image and reboots. I was able to set it back to 32bit by powering off before it booted the 1st time and everything seems fine. Add to that: when I choose the 32bit 2k3 image during the deployment, it then pulls down the proper 32bit winpe image and reboots. I was able to set it back to 32bit by powering off before it booted the 1st time and everything seems fine.

]]> http://mattlog.net/2009/10/16/vmware-stop-0x0000005d/comment-page-1/#comment-26408 Jay Tue, 02 Aug 2011 15:47:55 +0000 http://mattlog.net/?p=246#comment-26408 Running into this deploying a 2k3 32bit server under vSphere 4.1. If I set the VM to be 32bit, it still pulls down the 64bit winpe image. Strange. My SCCM guy is going to look at it in a bit. If I choose to set it to a 64bit 2k3, it starts the deployment fine. Running into this deploying a 2k3 32bit server under vSphere 4.1. If I set the VM to be 32bit, it still pulls down the 64bit winpe image. Strange. My SCCM guy is going to look at it in a bit. If I choose to set it to a 64bit 2k3, it starts the deployment fine.

]]> http://mattlog.net/2009/10/16/vmware-stop-0x0000005d/comment-page-1/#comment-19115 Anonymous Wed, 11 May 2011 06:40:54 +0000 http://mattlog.net/?p=246#comment-19115 Thanks for the tip Matt. What a noob mistake for me to make. :P Thanks for the tip Matt. What a noob mistake for me to make.

]]>