Change default Ghost32 settings for all users?
Is it possible to change the default settings in Ghost32 for all users, including the settings stored in the WinPE & WinPE-512 virtual partitions?
The reason why I ask is because two days ago an image spanned across a few .ghs files became corrupt, for seemingly no reason. The only logical conclusion I came to is that the image either wasn't written to disk properly, or something interrupted the flow of network data from the client being captured to the server w/o making the task fail. The biggest pain is that the image was my small, base Windows 7 build from which we base all other builds!
I made a backup of the image about a week ago and by looking through my change log I was able to get it completely patched up to how it should be. As a precaution I changed the tasks that capture images for Windows 7 to include the 'split' switch for Ghost32, specifically:
-split=1536
The images are stored on a server running Windows Server 2003, with all drives formatted as NTFS. My theory is that because Ghost32 was spanning the image across multiple files up to the max. 2GB limit, perhaps I'm risking the stability of the image by pushing each file to the max size. Thus I threw in that split switch.
So with all that background info, is there a way to change the default options for Ghost32 for all users? I'd like to include the -split=1536 switch if I could.
Beyond that, is there any stability gained or lost by spanning images across files? Given that these images are on NTFS volumes, and being backed up to NTFS volumes, should I even span the images at all? If I don't span the images, is there a way to change Ghost32, again for all users etc. so that it doesn't span, even in tasks?
Whatever change I make, I'd rather make it as part of a default setting rather than a task-by-task setting (task->advanced button, insert switch there) so I can set it and forget it. Any takers? Thanks in advance.
Comments
Turns out, after a bit of
Turns out, after a bit of reading, it looks like if an image is being created via task over a network spans must be created because Ghost32 on the client side doesn't know if the target destination is capable of files larger than 2GB. So, looks like I'll have to stick with spanning images. I've set -split=1536 for the tasks I've got, also running Image verifications on each of them as I create them before backing up the updated images, but it's working.
If I could set the -split=1536 for all users / clients / tasks etc. that'd be great, but if not I'll deal.
Would you like to reply?
Login or Register to post your comment.