Does anyone know if the following behavior is normal? I have a workaround,
but would like to know if it is how the Image-safe stuff is supposed to
work. I've not been able to determine from the DM administration
documentation or from the support site.

1. created base image on Dell GX620 (have tested on other hardware too).
2. Created both a Ghost image and a Zen image of the system after sysprep
3. Booted machine, tested - sysprep mini-setup runs fine, everything appears
in order. During sysprep mini-setup, prompts for a new PC name (or provides
a randomly generated one). I name it "testname". Test apps, etc,
everything is good.
4. I re-image system with the Zen image created in step 2 to make sure the
image is good. Boot system, sysprep mini-setup runs, this time I name the
computer "testname2". However, when mini-setup finishes and system reboots,
it is still named "testname" from step 3. I am able to manually rename the
system fine in Windows and it sticks after a reboot. Ran this re-imaging
process step several times to verify this was what was really happening (and
several other staff noticed same problem on other machines).
5. Re-image system with Zen image. Prior to booting into OS, use zisedit to
see what info is there. It contains the "testname" info from step3. Run
"zisedit -c" to clear all image safe data
6. Boot into OS, run sysprep mini setup, name it "testname3". System
retains this name after reboot.

7. I repeat step 4 with the Ghost image - several times, each time giving
sysprep mini-setup a different name for the system. Each time, the name
sticks. This step was to verify that behavior is related in some way to

All of our imaging process is scripted, so I've solved the problem of
systems retaining old image-safe name even after syspre by just adding the
"zisedit -c" command to the end of the imaging process. My question is -
even if there is image-safe data stored on the workstation, shouldn't it
overwritten by the sysprep mini-setup process?