Yes. It is indeed corrupted. You could do an emergency boot (if the machine has finished encryption) - that will fix it, or you can remove it. Both require the 3.5 version of SafeTech, and the machine's object from your "Corporate Database"
wow - such an old version! I didn't think anyone was still using it. It must be from 2000 or so?
I tried to install SB 3.5 onto a Win NT 4 workstation. The only problem, is that during the install, there is no option to create a Safetech disk. Do you know how to create a Safetech disk on SB 3.5? Or how do you recover a machine with a corrupted SB 3.5?
If I remember there's a "recovery" directory within the management center directory which you need to copy to a bootable floppy. You only really need a few files on the disk if I remember right - safetech.exe, sbalg.dlm, recovery.dlm I think, but they are usually all in one directory under the management console.
absolutely there's a server - that's where 3x sends its recovery information to. There's a database as well.
There's no menu option to create the disk though - just the files are included with the "Corporate Database" side of the solution. Looking at the archive you just need the SafeTech.exe and sbalg.dlm files from the original media on a bootable disk. You should also copy sbrepair.cod there as well in case you need an emergency boot.
All are in the "SafeBoot" folder of the original media.