Post the new smsts log and we'll take a look.
Now you actually have an error I should give you enough info in smsts to find the cause.
What are the benefits of doing a B&C over installing from install.wim from the Windows 7 DVD?
I tried a few times to get B&C working but always seemed to mess up installing the Config Client so I went with installing from the install.wim and it worked fine first time so I never bothered to go back and look at getting B&C working when the current way we do it worked fine. Most workstations image in < 60 minutes.
But the amount of updates must be huge.
Most of our updates just get installed once the laptops are out and about in use.
I never managed to get updates deploying at build time. Is it easy enough to get sorted? I might have to look into it the next time we refresh all our workstations.
Well you can just use ztiwindowsupdate.wsf from mdt. I do a build and capture using mdt and then import the image into sccm. But its a pretty thin image. I like the image to be fairly up to date otherwise its a pretty poor experience for the user if it takes weeks for the laptop to be up to date. Not to mention bits chugging away in the background.
Must admit I've never used MDT before. Not entirely sure what it can do to be honest. I went straight from WDS to SCCM. I do agree with you by the way. Having updates already in the base image would be preferable. I'm not justifying the way it's currently set up when there are things I can implement to improve the current system (although it works well at the moment luckily).
Is there a way to take the standard install.wim from the Windows 7 and slip stream the updates in or is B&C the way to go?
If you have the software update point set up you can just update the install.wim offline. I've not done it myself.
I just build a Win7 virtual machine any old way and then capture it as and when required. I use the SCCM capture media to capture it.
I update the OS via the web through this machine then use the SUP to manage it when deployed.
Just keeps things simple :)
snagrat please find attached my smstslogs file thank you for taking a look.
Right click the TS in SCCM and go to the Advanced tab.
Under "Use a boot image" is it set to the correct Boot Image?
You could try removing all the relevant packages and distributing them again.
I'll look at the log when I have cmtrace to hand next