Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 5 subscribers
  • Views 13838 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

Sophos SafeGuard 5.50.1.17 - Keyboard and Mouse Lock-Up - In Windows - NOT POA

dBeail

Hello Everyone,

I'm currently looking to deploy Sophos SafeGuard 5.50.1.17 (Without DE) to a few thousand systems however I am finding that a high percentage of installations leave the systems with an inoperable USB keyboard and mouse.

I have concocted a number of removal scripts for the product which successfullyremoves the products MSI's, removes all USB devices and initiates and hardware rescan however after everything comes back to life the devices still still inoperable.

We also experience this on newly built systems but its only in around 1 / 100 systems that fail - our current resolution of these is re-imaging the system and re-installing Sophos. (Basically repeating the build process again)

Is this is known issue in which someone can point me towards a resolution? Everything i seem to find relates to POA (which we don't have)

Many thanks

Daniel

:26803


This thread was automatically locked due to age.
Parents
  • 0

    Ahh sorry, Network Devices are blocked as well - makes it kind of hard to troubleshoot / collecting information from the machine.

    In this case the only option to access the logfiles would be booting the machine from a Live CD like WinPE and gathering the files or slavinging the drive into another machine and grabbing the logfiles from the seconday machine - if possible.

    Is it always the same make/model that is affected by this issue and if yes, is this the only affected make/model, or are the other 99% of machine from the same make/model?

    Cheers,

    Chris

    :26827
Reply
  • 0

    Ahh sorry, Network Devices are blocked as well - makes it kind of hard to troubleshoot / collecting information from the machine.

    In this case the only option to access the logfiles would be booting the machine from a Live CD like WinPE and gathering the files or slavinging the drive into another machine and grabbing the logfiles from the seconday machine - if possible.

    Is it always the same make/model that is affected by this issue and if yes, is this the only affected make/model, or are the other 99% of machine from the same make/model?

    Cheers,

    Chris

    :26827
Children
No Data
Unfiltered HTML