Hi, just thought I’d share.
I’ve been looking at changing host name on XP just after imaging.
It works, but init.gz in /usr/share/fog/funcs.sh, you must change
REG_LOCAL_MACHINE_XP=“/ntfs/WINDOWS/system32/config/system”
to
REG_LOCAL_MACHINE_XP=“/ntfs/WINDOWS/system32/config/SYSTEM”
Note that also with ‘changeHostname’ in it’s current position in /bin/fog, it will only attempt to change the name in the LAST partition - i copied it to after every partition restore.
Note again also, it’s reliant on the partition being ntfs :(. Since ntfs does not play nice with XP embedded EWF, I’ll need to implement FAT32 in all the functionality which currently only works with ntfs.

hi andrew, not not done it, but would also be interested in anyone who has considered mechanisms during the image writing to tell the SSD that it is empty again… i.e. knowing/ensuring that FOG sends the required TRIM commands so that the SSD starts wil a full set of erased cells…

hi all, new here.

Just been trying FOG, and it’s great. Does what it says on the tin…

Question:
before I start digging much deeper, has anyone done specific work with XP embedded clients where the system volume is EWF protected?
Basically, EWF is a filter layer on top of the disk which means all modifications are not written, but kept in RAM unless specifically ‘committed’. So i’d be looking for hints on how if FOG needs to change something (e.g. computer name/sid), before the required reboot, a script could be run to commit the volume.

to be VERY specific, I’d like to run a batch script before any automatic or forced reboot being done because the OS volume has been changed.

example script:
ewfmgr -commitanddisable -live
call dosomethingelse.bat
ewfmgr -enable

thanks, simon