This content has been marked as final. Show 9 replies
You can use wintech on a machine as long as it does not have eepc active if you want to slave a drive to it
Ok can Wintech only be run from a PE disk? Or is there a windows executable of some kind that will work as long as eepc isn't installed?
If it has to be PE then I'd imagine it'd be just as easy to boot to the PE disk on the affected system rather than slave it to another and then have to boot from PE.
You can run wintech under any version of windows from 2000 up. Makes no difference if it's pe or not.
Thanks! I will give this a try.
I can run the program from the directory in the BartPE disk, and I can authorize and set the appropriate algorithm.
However, when I try to authenticate (using database file or SBFS) I get an error that the SafeBoot disk driver is not present.
What is the proper method of running WinTech from within Windows?
you need to run it from the proper environment, install all the drivers etc.
the easiest way I guess is to run it from an inactive client - ie install a proper EEPC client on the machine so the drivers get put in place, but DONT let it communicate back to the server or activate (rename sdmcfg.ini will do that for you).
if the client activates, then you won't be able to mount a drive from another machine.
Thanks... I'm sorry - this is the first time I've messed around with the installation files (other than creating a file set). Would these steps work?
1. Install the package but before the reboot, rename sdmcfg.ini
3. Run .exe from PE disc
4. Once WinTech is properly authorized and authenticated, mount SBFS as volume
5. Run a scan (or whatever is needed) against that mounted volume
yes, that would work fine.
just put wintech.exe in the client directory and it will play nicely.
actually renaming scm.ini might be better, as if sdmcfg.ini is still good, you can use the api command line to do helpful things like exporting a machine from the database etc.
Worked like a charm!
I didn't have to map the drive either... Windows recognized it right away but couldn't read it... Once WinTech was Authorized and Authenticated, the drive became readable and remained that way even when WinTech was closed.