Quick dumb question about Remote Boot Service

[Guest]

After it first executes off the RAM does it revert to running on the hardrive
after a reboot? Or does it always run off the ram?
Is this the best way to remotely deploy xpe on a system w/ No removable
storage, network connection, and w2k as the primary os? thanks.

 

[KM]

walnut,

Remote Boot is implemented through RAM Boot (where your image is just downloaded from network).
So, to answer your question, it always run off the RAM and there is no built-in functionality to flush the image on a persistent
storage on target.

However, you can always do that manually. Moreover, this is how many of us here have implemented their deployment scenarios.
Basically, you create an image to be boot remotely. When the image is running on the device you do:
- prepare the storage media (use tools like diskpart, format, etc.)
- download a full XPe image from network or any local removable media you have on the device (CD-ROM, USB, etc.)
- burn the image on to the persistent storage (xcopy, SDI extract, etc.)
- reboot (make sure to abort Remote Boot here)

You can definitely automate the procedure by using various scripts.