[mdt] MDT 2010 Update 1 woes

[jamesmay]

I had a rather lovely setup with WDS and MDT 2010 deploying out all my custom images, server went pop and lost the setup. Resetting it up now to try and get back to where i was before, I've spent days playing with SCCM and then went back to the old MDT 2010 method, but now with the update 1 version. The machines I'm installing this onto get as far as the solutions accelerations screen, then reset themselves. Before I didnt have to work about putting any drivers into the image and made sure I build my new reference machine on a virtual machine, Has anyone any ideas why its gone all wrong?

[SYNACK]

This could be because the previous imaging tasks did not clean up after themselves properly, I had this with the first MDT. On a client that is misbehaving delete the MININT and _SMSTaskSequence from the c: if present and also the c:\program files\Panther folder along with the contents of c:\windows\system32\sysprep

 

or just wipe the drive first then try imaging with MDT again.

 

This falt happened to me as the boot image tries to look for any previous setup instructions, finds them in an old/wrong format then kills itself rather than dealing with it gracefully.

[jamesmay]

thanks for that, just trying to work out how i can wipe the drive. Just deployed lovely to my virtual machine but nothing else

[jamesmay]

and seems to be ok on other machines, seems my tryigng to get sccm to work screwed up the test machines

[SYNACK]

thanks for that, just trying to work out how i can wipe the drive. Just deployed lovely to my virtual machine but nothing else

 

Boot the system into a stripped down WinPE environment, there is an option to build one of these aswell in the Deploy point properties of MDT. Once you have a command prompt you can use:

 

diskpart
select disk 0
clean

 

which will wipe the drive for you.

 

Alternativly you can use something like Darik's Boot And Nuke | Hard Drive Disk Wipe and Data Clearing to just boot up the pc and wipe it, you don't need to let it run the whole way through, just let it trash the first 1-2% where the boot sector and partition tables are and you should be good.