cyr0nk0r

I deploy this TS to a custom collection called "Capture" which contains a single computer that is added manually via the MAC address per the guide. I am attempting to boot into WinPE using the Capture TS via the same VM that is added manually via the MAC address over and over again. I don't understand why this isn't doable. EDIT: and for that matter what happens when I have clients that I want to re-image over and over again? Lets say I image them and then need to image it again 3 months later. I want to replicate WDS in that whatever machine that boots into PXE will get imaged. Regardless of how many times it has been imaged before or what. I need a set and forget solution that our technicians can just blast computers when they need to without having to worry about if the computer is "known" to sccm or if it has deployed an image to that machine in the past.

I followed the guides to create a "build and capture" sequence. I then deployed it. I set the target to be a single computer VM that I am using for testing. I have found that once I create the deployment and try and PXE boot my VM it will download the right boot image and go into WinPE. (I then turn the VM off because I'm just testing everything right now) However if I try and PXE boot a second time I get the following error. If I delete the "capture" deployment that I have created and re-create it, I can then boot into WinPE again but only once. How do I setup the deployment to work every time? (I am doing it this way because when I don't need the capture anymore I will just disable the task sequence or deployment rather than deleting them and re-creating them every time I need to do a capture)

Ok, so there seems to be some changes in terms when moving from wsus to sccm2012. Previously, I maintained a wsus server on 2008 r2. I created 2 collections, workstations and servers. Workstations were all XP systems Servers were any 2003 or 2008 r2 machine. I then set an auto-approve rule to automatically approve any critical updates to XP and apply it to the workstations collection. I then point each machine to WSUS in group policy and everything just worked. I am looking to replicate the exact same behavior with SCCM. Every guide I can find (especially ones in this forum) only show you how to setup this insanely complex series of creating ADR's for 1 month updates, patch tuesday updates, then creating new software update groups for every week after patch tuesday and all this nonsense. All I want is critical updates to automatically download from Microsoft, auto-approve, then auto-deploy to a collection. I don't want to ever touch it again. I don't need or care about reporting after every patch tuesday and all that. I just want a set and forget solution. Nothing I can find mentions how to set something like this up. Can someone explain the series of steps needed to get updates automatically downloaded and deployed to a collection without me having to do anything after its initially configured?

this guide does not work with SCCM SP1 and Server 2012. Several key steps are not included such as during the update role installation do you select WID or Database. this guide also doesn't address the KB articles that several other guides say are pre-reqs before adding the SUP role on SCCM. The IIS configuration is severely lacking for the post installation of WSUS.