Question : SCCM OSD deployment to Hyper-v R2

I am attempting to use SCCM 2007 R2 Operating System deploment to create my base Windows 7 image.  I would like to create my base image on a hyper-v R2 VM, but my task sequence fails during or right after the "Installing Windows" because the VM loses its IP for some reason.  It then gets a 169.... IP address and the task sequence fails.

I found this article which could explain what is happening, but I have disabled "apply device drivers" and "apply driver packages" so no drivers are added and it still fails the task sequence because it is losing its IP during the "Installing Windows" phase.

http://social.technet.microsoft.com/wiki/contents/articles/nic-devices-that-require-a-special-driver-for-winpe-may-cause-a-configmgr-task-sequence-to-fail-if-a-vista-or-newer-os-is-being-deployed-via-an-operating-system-install-package.aspx

The only issue with this is that I am running SCCM 2007 R2 (WinPE 3.0) and I am not injecting any drivers.


The task sequence works fine under a vmware VM and on a physical machine, but will always fail in a Hyper-V vm.

I have F8 enabled on the boot image so I can clearly see the machine just loses its ip during the "expanding Windows files" phase of "Installing Windows"

Please let me know if you have any ideas what may be causing this.  I have tried to do this on two completely different physical Hyper-V VM servers with different VM's and it always loses its ip during this phase.

Answer : SCCM OSD deployment to Hyper-v R2

I hope that u used Legacy network adapter to be able to boot from Hyper-v Virtual machine.

did you add network driver to boot image?
did you configure DHCP server correctly?
What error or message you received when connection stop?
did u advertise Task sequence to Unknown collection or to different collection, if to unknown collection please make sure that this machine is not member on other collection.