We've just started putting v5 in our community as an upgrade to our existing v4 estate. To start with, I've just provided our engineers with the SafeTech utility for v5 while I work through the WinTech possibilities to discover how powerful a tool this might be.
I'm finding it all a little unclear. So a few questions:
What exactly does "Mount SBFS as a Drive" do? I tried it, mounted it as F:, and the then used WinTech System Tools>A43 File Management Utility to look at the machines file structure. Sure enough, there is F: with a load of SB Files and folders there. Interesting I thought, not much use to a Desktop Engineer doing an Emergency Boot or Decrypt, so I came out of there, exited Wintech and found now the machine won't boot "Error, unable to mount SBFS". Oooops...... Did I do something wrong? And also, just after that I notice that any attempts to now authenticate using SBFS result in "Error 0050020 Unable to open the client data store".
And the re-write MBR thing looks interesting. In v4 I can remember on a few occasions that if we had an unencrypted SB install, we could do an FDISK /MBR and it would, sometimes, have the effect of removing the SB installation. Is this what this option is for in the Wintech recovery?
And finally, the most compelling reason to use Wintech is the ability for an engineer to boot up to the disc, authenticate using either SDB file or user's credentials (if known), and then pull off all the customer files in an unencrypted state. A lot quicker than a full removal when the OS is broken. But....how exactly is this done? That process doesn't seem too clear...
Ah...one last thing actually. The guide seems to talk in terms of booting Wintech from CD and then having the SDB file on a USB stick. Is it not possible to boot Wintech from the same USB? Our engineers carry sticks around and if they could do the full wintech recovery from a single USB stick they'd be most pleased.
Message was edited by: Odgeuk on 19/07/10 09:21:06 CDT