Project

General

Profile

Actions

Bug #22820

open

PXE Boot / Deployment of Windows via WDS and multiple reboots

Added by Alexander Ray over 6 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When I deploy a new Windows server by chaining PXE to a WDS server, the VM is created fine - however, the WDS installation process involves several reboots. The problem is that until I call the 'built' URL, it will continue attempting to boot from WDS and never finish the install; I got around this by having it call 'built' before the first reboot, so the rest of the deployment works, except that as a result of calling 'built' the Puppet CA will not autosign the server's certificate when puppet is installed.

The VM seems to be provisioned with netboot as the highest priority, over local hard disk, whereas the reverse should work just fine since it will only boot off the network when the first stage of WDS deployment has not completed. However, there doesn't appear to be a configuration option to alter this behavior.

Actions

Also available in: Atom PDF