Your customer boots to the HPE Smart Scripting toolkit via PXE to automatically configure their new systems. They are moving to a new data center which has a policy that PXE boot will not be allowed…

Question

Options

• AiLO Federation running the Smart Scripting Toolkit scripts
• BiLO RESTfull API running the Smart Scripting Toolkit scripts
• CInsight Control server provisioning running the Smart Scripting Toolkit scripts in a build plan
• DHTTP/HTTPS Boot to the Smart Scripting Toolkit

• A
  17% (4)
• B
  4% (1)
• C
  8% (2)
• D
  71% (17)

Explanation

HTTP/HTTPS Boot is the closest functional replacement for PXE because both are network-based boot mechanisms - HTTP/HTTPS Boot is a UEFI-native standard that lets Gen10 servers fetch the Smart Scripting Toolkit over standard web protocols, bypassing the TFTP/DHCP-dependent PXE stack that the new data center prohibits. The key word in the question is "closest alternative" - HTTP/HTTPS Boot preserves the same automated, network-driven deployment workflow with minimal process change.

Why the distractors fail:

• A (iLO Federation): Federation is for bulk management and monitoring of iLO devices across a fleet, not a boot/provisioning mechanism.
• B (iLO RESTful API): The RESTful API enables programmatic configuration of individual servers but doesn't replace the booting step - you'd still need another mechanism to initiate deployment.
• C (Insight Control server provisioning / ICsp): ICsp with build plans is a valid provisioning tool, but it traditionally relies on PXE under the hood to boot target servers, so it doesn't solve the PXE-banned constraint.

Memory tip: Think of HTTP/HTTPS Boot as "PXE for the modern UEFI era" - same idea (boot from the network to a deployment environment), just using ports 80/443 instead of TFTP/67/68. When a data center blocks PXE, it's almost always allowing HTTP/HTTPS, making D the natural drop-in.

No community discussion yet for this question.