I'm using a Hyper-V enviroment to build and capture my reference images. I'm not able to create a search folder with only the specific Hyper-V Server updates, because there is no seperate update classification for Hyper-V Server 2008 R2. So the only option is to create a deployment mangement job with all the Windows Server 2008 R2 updates. I did not yet installed the hotfix because this will only solve a problem when installing a large amount of updates.

Hi All, Currently I'm on a project where we need to deploy a lot of Hyper-V hosts. We will be using Hyper-V Server 2008 R2 SP1 instead of the full Windows version with the Hyper-V role installed. SCCM with MDT 2010 SP1 integration is the main software and OS distribution tool. I created a "Build & Capture" task sequence to build an image with the latest software update. Unfortunally this task sequence did not work well for Hyper-V Server. When I look in to the log file smsts.log I see that updates have been installed and it initiated a reboot. After the reboot it did not continue with the task sequence, it simply showed the Windows login screen and did not prepare (sysprep) and captured an image. I did the same thing for a normal Windows 2008 Server edition. This task sequence did not have any problem with the software updates, it rebooted Windows and continued with the TS and ended with a captured image. I’m curious if someone did successfully created an Hyper-V Server image including the latest software updates. When I disable software updates in the TS it will create an image without any problems. It looks like a specific OS related problem. Greetings, Coen

First, I recommend creating the Image on a Hyper-V machine. Create a Update Management job with only the Updates containing that OS. Assign it to the Build and Capture collection where the Referance machine is. Apply All Updates check in the Task Sequence. Use the hotfix: http://support.microsoft.com/kb/2509007Nicolai

Did you ever find a solution to this? I'm facing the same problem. The only solutions I've been able to find so far is if you're deploying a machine from a pre-captured WIM, you can use dism.exe to deploy it before you boot the host OS, but that doesn't seem to work if you're working off an OS installation package.