Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 7 subscribers
  • Views 9691 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dell Latitude E7450 No Init SafeGuard 7.00.0.97

DC_IT_Manager

Been using SafeGuard 7.0 with the Latitude E7440 successfully for about a year.  One of the 7440s died, so Dell sent an E7450 as a replacement.  Had to build a new image.  Finally add SafeGuard AT THE END and get this No Init thing that I had never seen before, but which is all over these boards.

I changed the SATA settings to no avail.

I've tried every left / right /shift / F6 / FN key combo I can think of to no avail.  The left shift key does work, but no hot key is accepted.

This ticket https://community.sophos.com/products/safeguard-encryption/f/6/p/5835/17779#17779 says I need to create a bootable WinPE disk and copy a file, which seems a bit much.

How did this product go from being workable to being untenable?

Suggestions?



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to SimonUOL
    Thanks for your suggestion. When support finally got back to me, they suggested the same thing. I tried two different external usb keyboards. Neither one worked. I didn't think that was going to work because the left shift key built in to the laptop was recognized. The problem was non of the function keys were recognized after the shift key was recognized. Then I was told to disable USB 3.0 because that was part of the problem with the external keyboard. I did that - and there was no change. Then I was told that I couldn't use the BeSetFlags tool because that was for an earlier version of SafeGuard - not 7.0. Finally, Sophos Support told me to wipe the machine and start over, but not to use the script to install Safeguard - and to install it one exe at a time manually.

    Adam in DC

  • 0 in reply to DC_IT_Manager
    So, in the end, the solution was to download the newest version of the client 7.00.2.23 and install the 2 files from it (the client pre-install and the client x64) - and then install the configuration file from my own server as the third and final file. The version numbers of the new client were so close to the old client that I didn't realize there was a new client. Wish that had been pointed out to me when I started this!

    Adam in DC

Unfiltered HTML