Hello all, and I’m back. If only I were better than ever.
I guess this post could also be titled “making software do things the manufacturer didn’t intend”, but here goes:
The thawspace of Deep Freeze can be accessed (offline) with ImDisk (free, available here) and WinImage. And of course with Linux (loopback device, lookup the man page for losetup). We recently had a situation at my employer where the existing thaw space was no longer big enough, and critical system files (user profiles) were stored on it, so I researched how to create a new one – and it is fairly easy with those above tools. Turns out the driver for the thawspace, named ThwSpace.sys, has some parameters in the registry at:
In this path, you’ll see a key for the drive where the image file is located (ususally C:), and a sub-key for the drive letter the thawspace is mounted on. Under the sub-key, the default value will indicate how big the image/thawspace is supposed to be in megabytes, and there will be another binary value that I honestly don’t have a clue what the data in represents. The name of the binary value will be the name of the actual image file used for the thawspace.
What’s cool is you can thaw deep freeze out, setup a disk image with ImDisk, and change the registry values for the ThwSpace service to point to your disk image, and voila you have a custom thawspace. I highly recommend that you follow their naming convention for the thawspace image, though – usually it’s at C:\$Persis0.dsk or C:\Persis0.dsk depending on what version of Deep Freeze installed the thawspace to begin with. I just added a new image, and ended the file name with a 1 instead of a 0.
What I did to solve our little situation was to create a new, bigger image with ImDisk, use xcopy to copy all the files with permissions intact, and change the registry to reflect the size and file location of the bigger disk image. On the next reboot, the Thawspace driver mounts the new disk image instead of the old, and you can erase the old one.