jdoldridge Posted July 29, 2013 Posted July 29, 2013 Hi Guys, I have just built myself a new image for our network, I have sysprepped and uploaded to WDS no issues at all. But we are starting to slowly implement SCCM 2012. If I try to capture the image using capture boot media I get q HAL_INITIALIZATION_FAILED. Error when it boots to network up upload the image. I have build the image on a VM on VMWare workstation 9 and just wondered if anybody else has had this problem and how you got around it. Thanks in advance Josh
FN-GM Posted July 29, 2013 Posted July 29, 2013 I think its because SCCM wants to run sysprep itself and not for you. You can run in capture media inside windows. I would give that a try. Could you not just import your existing WDS WIM file to sccm?
jdoldridge Posted July 29, 2013 Author Posted July 29, 2013 I ran the capture media once and it ran through some stuff and went for a reboot and I got the HAL message. We are using WDS on server 2008 But sccm seems to use 2012 boot.wim. I get a big windows 8 sad face appear when it doesn't work everytime. Is it possible to use 2008/win7 boot.wim and how can I import it? I get failed messages when I try to import ours that works with WDS
FN-GM Posted July 29, 2013 Posted July 29, 2013 I wouldn't import the old boot images. I had similar issues with Vmware ESXi intel network card, do you have any other network card options in Vmware?
free780 Posted July 30, 2013 Posted July 30, 2013 Sccm 2012 sp1 uses the adk where as 2012 uses waik. Adk is based on win 8. This means older processors like p4 are no longer supported. There is limited support for waik in 2012 sp1 cu2. Sccm seems to work best with capture if you configure it all in the TS. If you need to do a manual process intergrate mdt 2012 u1. Use the ltisuspend script.
jdoldridge Posted July 30, 2013 Author Posted July 30, 2013 I had similar issues with Vmware ESXi intel network card, do you have any other network card options in Vmware? No, Not that I can find anyway? Its really rattling my cage now :/
Arthur Posted July 31, 2013 Posted July 31, 2013 Not that I can find anyway? Open your VM's VMX file in Notepad and change ethernet0.virtualDev="e1000" to ethernet0.virtualDev="vmxnet3".
jdoldridge Posted July 31, 2013 Author Posted July 31, 2013 Open your VM's VMX file in Notepad and change ethernet0.virtualDev="e1000" to ethernet0.virtualDev="vmxnet3". As easy as that... Well I can give it a go tomorrow when I'm back at work. Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now