bjornpreus

Indeed App-V is quite a good reason to capture Secure boot is a option for UEFI boot. Since uefi is a direct file boot, you might wanna put a layer for security over it so it can't be tempered with

The install should go without any problems on a physical UEFI machine. Tho if you install the hotfix and check your WDS service, you can go ahead and build gen2 VM's in Hyper-V without any problem, as matter of fact that is what currently is happening on my machine as I'm typing up this post. Testing the tasksequences on a hyper-v gen 2 machine to catch the problems, then deploy it for the physical machines. But why would you actually go ahead trough the trouble of capturing and sysprepping when your using SCCM?

Hi Norphy, In case your issue isn't solved yet: 1. check that you have installed the hotfix: http:///support.microsoft.com/kb/2905002 2. restart your WDS service if you have the hotfix installed, sometimes it hangs without giving a error. If you have your SCCM DP in the same subnet all should be fine after this. If your DP is in a different subnet, make sure you have all the IP-Helpers in place.