Re: Using EWF and cloning

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



KM

I did as follows .. and another question came up:
- let FBA run and let it reboot
- make changes / install software
- clear everything -> reboot
- enable EWF (ewfmgr c: -enable)
- reseal, and let it reboot (shutdown)
- used this as the master to multiply

I assume every clone will be protected upon its first boot.
However, booting the clones takes longer than the master before resealing.

Do I have to commit changes to EWF on every clone after its first boot?

Thanks and bye
Franz

"KM" <konstmor@xxxxxxxxxxxxxxxx> schrieb im Newsbeitrag news:%23g7woJMrFHA.1788@xxxxxxxxxxxxxxxxxxxxxxx
Franz,

Since you are using EWF Ram Reg mode you showed the correct procedure for cloning the image with EWF.
There will definitely be some device reboots during FBA and at the end of the manual reseal (right after you enable EWF). After that you can safely reboot your master image many times since it is going to be EWF protected anyway. (I assumed the system protected partition)


Only one thing you may add to the procedure that will help you avoiding some potential issues with the system running on target devices after cloning: delete the content of [HKLM\System\MountedDevices] key just before enable the EWF.

You may find this article useful to you now: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xecondesignconsiderationsforusingewfwithcloning.asp

--
Regards,
KM

PS. It is advised to run FBA on HDD rather than on CF directly.


Hello

I am somewhat confused about the correct procedure:
I am preparing an image for a CF using EWF Ram reg mode. After FBA has run and the system reboots I have to make some changes to the system and enabling EWF after all the changes have been made. So far so good .. everything works perfect .. that was during development/setup of the basic image in TD.


No I have to add the cloning component to create the Master for cloning.
Now, what goes when? What's the correct order?
- FBA
- make changes
- reseal (manually)
- enable EWF

Is that correct? Are there some boot's in between.

I am looking forward to any hint.
Thanks and best regards.
Franz



.



Relevant Pages

  • Re: Using EWF and cloning
    ... If you don't commit the changes to EWF on every cloned image you will repeat the cloning every time you reboot it. ... booting the clones takes longer than the master before resealing. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Using EWF and cloning
    ... If you don't commit the changes to EWF on every cloned image you will repeat the cloning every time you reboot it. ... booting the clones takes longer than the master before resealing. ...
    (microsoft.public.windowsxp.embedded)
  • Re: ewf + fba reseal
    ... Then you can copy the image to other drives and each ... do i reseal and then boot back up and enable EWF? ... resealing wont have a chance to generate a unique SID for each machine: ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF Ram-Reg and cloning
    ... Reg RAM EWF will not be active only in case that PnP detected new volume, only in this case you need to do one extra reboot. ... First FBA. ... Only after reboot EWF driver will become aware of that change and start enabled. ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF/DUA help needed
    ... >> Your script does not reboot the device because it likely fails on the EXECUTE command. ... I suppose it is> mute though if there is a better way to update using ewf. ... >> With EWF command you just commit a registry change to move/replace the JP.exe file on next reboot. ... The file will be replaced each>> reboot until you commit EWF again. ...
    (microsoft.public.windowsxp.embedded)