Instead, you are using a standalone Windows Deployment Services (WDS) server to handle/manage the PXE-boot process. So, to sum up: SCCM Distribution Points without PXE enabled, using the MDT Boot Image, and using WDS standalone. IF you take the MDT Boot Image from SCCM, and upload it into WDS as a Boot Image, you encounter an issue.
When you system PXE Boots, everything seems to be OK, and the boot image starts to load.
The problem is that names on those ISO images is slightly “technical” and not so user-friendly. The bare metal OS deployment function in SCVMM has the ability to be customized by adding custom scripts (also know as GCE).
Basically there is two ways to do this, you either make sure the script is in the Win PE image or you add it using recourses in the SCVMM Library. It will give you a very informative message in the job log like this: Error (2941) VMM is unable to complete the request.
We will look at how you can use PXE to boot Hyper-V virtual machines off of the network in this post.
As I said in the introduction, in a medium to large environment we will normally use SCVMM to deploy virtual machines; not only will SCVMM deploy the virtual machine, but it will configure the guest OS (including the post-Syprep specialization), name the computer, join a workgroup/domain, and possibly even do other work for us if we configure it.
Let’s say you have SCCM installed, including a CAS, multiple Primary Sites and Secondary Sites, and many Distribution / Management Points.
I ran into this scenario recently while at a client’s site, working with SCCM to create a server build task sequence.
Doing an OS installation with just 512 MB RAM can cause all sorts of funny symptoms, including network driver failure in a boot image, failures of SCCM task sequences, and OS installation failures because (allegedly) the text of the EULA cannot be found on the media!
It contains fixes that was caused by Update Rollup 2.0.
But there are situations were using PXE can be useful, including: Remember that since Windows Server 2012 R2 (WS2012 R2) Hyper-V and Windows 8.1 Client Hyper-V, there are two generations of virtual machine hardware specification.
Generation 1 virtual machines (the only generation on legacy versions of Hyper-V) make things a little tricky when it comes to PXE booting.