Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 5526 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 Messenger won't take 'Do not show this message again' for an answer

WillWatts

Sophos Messenger pops up every time I remote desktop into the server. It shows a sequence of four 'Important Notifications', the earliest from 19/04/2016, with a 'Do not show this message again' checkbox at the bottom of each message.

Every time, I check the checkbox on each message, and every time they come back.

How do I make them go away, please? I have read the FAQ, which implies that they should clear. But evidently this is not happening.

Windows 2008R2, Enterprise Console 5.1.0.1839, Endpoint Security 10.6



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

    Hello Will Watts,

    the check is stored in the user's registry,  HKU\Software\Sophos\Sophos Messenger\MessageHistory, the values correspond to the ids in C:\Program Files (x86)\Sophos\SophosMessenger\Sophos.Messenger.xml. (there can be more values - for expired messages - than ids). I'm on SEC 5.4.0, the Sophos.Messenger.exe version is 1.2.0.32 and it works as it should.

    Christian

  • 0 in reply to QC

    Thanks for that.

    I've had a look, and it is as you describe. The XML file contains the four messages I am seeing, available in a selection of languages. The registry contains a MessageHistory branch, with 11 id keys, all set to integer 1 (which I suppose corresponds to 'checked').


    However, I am still shown the four messages.


    A detail, which may be telling: it is not *every* time I log in - just once per day (I think). I get the impression that using the checkbox prevents a message from being shown again that day, but thereafter acts as though reset.

    Will

    PS Later: on more careful inspection' one message's GUID is absent from the registry, if that has any significance. The other three are present as described. I may have omitted to check one of the four this morning, so that may be the explanation for that.

Reply
  • 0 in reply to QC

    Thanks for that.

    I've had a look, and it is as you describe. The XML file contains the four messages I am seeing, available in a selection of languages. The registry contains a MessageHistory branch, with 11 id keys, all set to integer 1 (which I suppose corresponds to 'checked').


    However, I am still shown the four messages.


    A detail, which may be telling: it is not *every* time I log in - just once per day (I think). I get the impression that using the checkbox prevents a message from being shown again that day, but thereafter acts as though reset.

    Will

    PS Later: on more careful inspection' one message's GUID is absent from the registry, if that has any significance. The other three are present as described. I may have omitted to check one of the four this morning, so that may be the explanation for that.

Children
  • 0 in reply to WillWatts

    Hello Will,

    can't see where it should store the day (it does store a last run date but not pre user and this does not have an effect on the display, I assume it's for clearing expired entries). I assume the Messenger is, like SUM, updated regardless of the SEC version so yours should be current. BTW - do you log in with a local user/profile or perhaps a domain user with a roaming profile?

    Christian

  • 0 in reply to QC

    Hi Christian,

    Sorry, missed from my previous reply: I am also on Messenger 1.2.0.32 (Product Name 'test' according to the EXE's resources!), so that isn't the issue.

    I am logging in with a domain account but with no roaming; the machine is a domain controller.

    Setting the checkbox my missed message deffo adds an appropriate new registry entry, so that part is working.

    I wonder if some registry sweep utility (some part of the suite of nocturnal backup-related and updating things) is helpfully deleting this setting overnight. A new angle for me to investigate. Perhaps change permissions on the key and see what whinges...

    Thanks once more for your tips.


    Will

Unfiltered HTML