Jump to content


Strange problem when capturing to HyperV

Recommended Posts


I have this strange issue:

When the capturing step begins - it creates a 1 kb. wim file on the share and then quits without any error. (when using hyperV)

When I use Vmware - it just works... the exact same task sequence.

Any Ideas? (Using Windows 2012 R2 HyperV + SCCM 2012 R2)


Share this post

Link to post
Share on other sites

I am having the EXACT same problem. Windows 2012 R2 Hyper-V + SCCM 2012 R2 (all hotfixes installed). It's driving me nuts. I'm about to pay Microsoft for a tech support call because I am dead in the water. I have Googled to infinity and beyond, and it seems no one else seems to have this problem. I'm trying to develop an image for a remote client using VPN to access their server. I don't have access to physical machines to try to capture from, hence why I'm using Hyper-V machines.

When using an image capture media (ISO mounted in Hyper-V), it seems to start scanning the volumes, but when it moves to capturing the volumes, the machine just reboots without warning or any messages. I'm left with a very small WIM file on the network share (ensuring network permissions are correct) and the machine boots into OOBE mode.

Anyweb - I have triple checked the network account and file share permissions. I have tried different network accounts on different file shares. I have tried Fixed and Dynamically expanding virtual hard disks, fixed and dynamic RAM.

The SMSTS.log file on the drive shows nothing useful. I can see entries when it was performing sysprep, but the last entry in the log does not show anything related to the image capture. The last entry in the log has a timestamp that is 4-5 minutes before the image capture fails and reboots, so I don't think the actual image capture process logs anything. Unless it's in another log file that I'm not aware of.


This problem is making me very sad :(

Share this post

Link to post
Share on other sites



Are you by chance using a Hyper-V High Availability Windows Cluster? If so, that seems to be the issue. I stumbled upon this link while searching today: http://scug.be/sccm/2014/01/29/osd-capture-fails-on-a-hp-gen8-hyper-v-cluster/


They were having the same exact issue as us. I tried the hotfix mentioned in the article, but that did not seem to help. However, I did get my image to capture by creating the virtual machines on the Hyper-V cluster nodes directly (not highly available through Failover Cluster Manager) using Hyper-V manager.


Why capturing a highly available virtual machine causes such a strange issue, I have no idea ... but this workaround has me up and running again. I hope this is useful for you as well.

  • Like 1

Share this post

Link to post
Share on other sites

To thesauce98 - I found your comments helpful. I had the exact same issue where the BDE drive content would get copied (~7MB) and when processing the 2nd volume, no content was copied and the VM just rebooted without warning. The reference VM was indeed clustered on Hyper-v 2012 R2 running on Dell hosts instead. Once removed from the cluster, the Capture step worked!



Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.