EWF Commit or Disable/Enable?

[Tim Houle]

If I send a field service rep out in the field to do an
update to an EWF RAM XPE box, should he/she execute a
commit after the installation or should he/she run the -
disable command, perform install, reboot, then run
disable command? Is there any difference or advantages of
running one over another? How are people performing
upgrades in the field to an EWF XPE box?

Thanks,
Tim

 

[Guest]

Thanks Tony.

-----Original Message-----
Here's the recipe I would use:

1. Reboot the system (this will clean-out anything in the RAM-based overlay)
2. Perform install
3. Commit ewf
4. Reboot

EWF

commands 'enable', 'disable', 'commit', 'commitanddisable'
don't actually get processed until you shutdown/reboot
the system. If you disable ewf, install software, then
reboot without commiting, the net effect is simply that
EWF is now disabled - the installation will not be
persisted since EWF was still enabled when the service
rep preformed the install.