Physical servers were being used as PVS target devices.

One of these physical servers was configured as the master target device.

Windows and all required software had been fully installed and configured, and a PVS vdisk was created from it.

The vdisk created from this would never successfully PVS boot, booting would stop and hang at a black screen, or sometimes proceed further and then BSOD after PVS boot message “Attempting to set IP Address on boot NIC”.

Windows had been installed on the physical server using the hardware vendor supplied windows installation images.

PVS booting and streaming is dependent on uniform network adaptor and stable network connection between the PVS target and PVS server.

Hardware vendor supplied windows installation images for physical devices, can often have many driver packages preinstalled to accommodate diverse and different physical hardware configurations.

These additional driver packages can sometimes create unexpected behavior or delays around networking which impact PVS operation.

Create a simple minimal windows installation using unmodified Microsoft installation media, and validate this windows install operation with PVS

1. Install windows using an unmodified Microsoft installation media.
2. Install minimal chipset drivers and minimal network adaptor drivers
3. Do not domain join (to eliminate any contribution from domain policies or similar)
4. Install PVS target device software.
5. Capture a vdisk and confirm if it can be streamed successfully.
6. Once having successfully created a working PVS vdisk, continue to install and configure windows as required.

Physical servers installed using vendor installation images may contain unnecessary drivers and impact on PVS operations.