Page 1
remote booting remote booting for the hp e-pc and whitepaper whitepaper for the hp e-pc e-vectra www.hp.com/go/desktops...
Page 2
The processes contained in this document are also Current remote boot state-of-the-art technology requires applicable to the HP e-Vectra. a local server to be present on the LAN or IP subnet. WAN remote boot is allowed by some protocols but HP does not endorse any particular software.
Page 3
PXE application maintenance is optimized. PXE The boot method should be chosen in accordance with • applications rely on the Universal Network Driver the boot protocol that is installed on the server. Interface (UNDI) which is hardware embedded. PXE applications are independent of network Booting over a network •...
Page 4
The most suitable remote boot scenario depends on the remote boot server application and the particular needs of the company’s MIS. Configure network remote boot scenario Again, there are two possibilities: User-initiated network remote boot: The e-pc is configured by default for this scenario. Restart your e-pc.
Appendix A: Re-installing the operating system using a remote server boot Re-installation of the operating system after a remote server boot must be done in several steps. Create a software image from a known working PC. Different applications - such as Norton Ghost (Symantec) or Drive Image Pro (Powerquest) - can be used for this purpose.
Appendix C: Boot methods and protocols Boot method Protocols and Typical networking operating Boot mode technologies system booted Appendix D: PXE optimizing PXE application maintenance PXE applications may be built on UNDI network drivers. UNDI is hardware embedded. Accordingly, PXE network applications are independent of networking hardware.