A warning for those using the Novell Image Explorer
October 20, 2013 3 Comments
I know this won’t apply to many people reading posts here but for those who do this could save your hours of frustration!
If you’re following the ZCM Imaging Megapost and creating driver packs with Image Explorer as per the instructions here there’s a glaring bug you need to watch out for :
- you’ve created a ZMG file with some add-on content e.g. drivers, let’s call it DRIVERS.ZMG
- you decide that you want to make some major changes to the package so you create a new file in Image Explorer and import your new content
- you click File > Save As and click on the existing DRIVERS.ZMG file with the aim of overwriting it
- Image Explorer asks if you want to Overwrite the existing file and you say Yes
You’d think this would be fairly simple and work OK… you’d be wrong!
I found the bug while testing a custom imaging process that kept failing with random behaviours that didn’t match the scripts I was working on. In desperation I opened up a file browser window in the middle of the sysprep process to check what was actually on the hard drive and was amazed to find (very) old versions of the scripts running instead of the new ones I believed had been saved using the process above! At least finding out the source of the problem stopped me from wanting to punch a hole in the case of the PC I was working on…
Seems like Image Explorer doesn’t actually complete the save process despite showing up as if it has. The workaround is to always delete the old .ZMG file before saving a new version with the same name. Basically never do this…