anyweb

i think you have the wrong logs, after setup windows and configmgr it reboots your system, i need the logs from THAT point onwards at the root of c:\ try dir /s smsts*.log and attach all those logs here

what version of mdt are you using and please describe what extrafiles and prestart files you are including in your mdt boot image

have you verified if the 35th version of this package is on the dp ? have you checked that the network access account is all ok ? have you looked at the distmgr.log file for any clues as to your problem

just follow my guide above and see does that resolve (after confirming the error messages) if not, post your errors here.

have a read of this

if you are deploying to a UEFI only system then you need to partition it for GPT disks, you cannot install Windows in UEFI mode on MBR discs, i've created a guide to show you exactly how to do this for the Microsoft Surface Pro, the only thing you'd need to change is the boot image if the architecture is x86, you can read the guide here.

check that package, is the second version of it really on the dp?

verify that you've configured the network access account with the correct password, that you can ping the FQDN of the managent point and that the content it's referring to has actually been distributed to your dp's

sorry for the delay, does it appear now ?

I guess you could use a prestart command like this one which uses SMSTSPreferredAdvertID

are you using Configuration Manager 2012 SP1 or RTM ?

hi you really should raise NEW posts when you have questions like this instead of tacking on your questions onto the end of a 'related' thread but to your question, those 'missing' updates are missing because the client needs them, therefore is the client computer in a collection that is targetted with those missing updates ? if not, then create a SUG with those updates and deploy it to a collection that contains these computers.

can you attach the smsts.log file please from a failing client computer

thanks

how wrong was the bios date ? and what gave you that clue ?

Here's an interview I did with Peter from WMUG (UK) at Tech Ed Europe 2013 in Madrid, Spain. http://wmug.co.uk/videos/b/wmug_interviews/archive/2013/07/07/niall-brady.aspx … @ncbrady ‪#‎WMUG‬cheers niall

you are probably including prestart commands in your boot image and it contains files/folders = 3gb in size,

in addition, have you verified in the SMSPXE.log that this mac address is showing up ?

have you seen this http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/ follow the guides in Setup SCCM section and use the SP2 media instead of SP1 as per the guides, finally when all is done install R3.

can you clarify this statement please are you using Configuration Manager to download and deploy updates or WSUS ?

yes using a script of via web services like Maik Kosters

i don't think so, where did you hear that ?

do you have an MSDN subscription ? it's not free

you shouldn't be installing drivers in a build and capture task sequence as you should be using virtual hardware (driver agnostic) for the build and capture process, save the driver installation for the Deploy task sequence, and that is covered here many times. The log to look at when troubleshooting anything OSD related is smsts.log or smsts*.log cheers niall

hi ben, have you tried deleting everything in the system management container in AD and see what get's re-populated ? (it should auto populate within an hour, or if you reboot the servers even quicker) try that and see what happens