Page 2 of 2
Posted: Fri Sep 06, 2013 1:44 pm
by bo.elam
lwc wrote:The problem with hiding is that it'll hide it for legitimate occurrences as well.
If it's a third party software, how come it still (thankfully!) saves the files anyway?
lwc, like you, I prefer not to hide messages but I think in this particular case is OK to do it since it is a extremely rare message, you are still able to do what you want and you would only be hiding the message in "one" sandbox. I think, I would hide it if I was experiencing the same situation.
Bo
Posted: Fri Sep 06, 2013 1:59 pm
by lwc
I doubt it'll hide it just for "one" sandbox. Besides, there's no easy way to "unhide" it later.
There's only a global and general "unhide" command.
Posted: Fri Sep 06, 2013 2:13 pm
by bo.elam
Is easy to test to see that if you hide a message, its only hidden in the particular sandbox that you are using when you clicked Hide.
For testing, hide SBIE message 1308 in one sandbox and you ll see that you still get the message in other sandboxes when a program that's not allowed to run attempts to Start and Run.
Bo
Posted: Sun Sep 08, 2013 4:01 am
by tzuk
lwc wrote:I doubt it'll hide it just for "one" sandbox. Besides, there's no easy way to "unhide" it later.
There's only a global and general "unhide" command.
It should hide the message for the specific detail shown in the message, i.e. *GUIPROXY_00000000 - MSOSYNC.EXE [FF000005].
bo.elam wrote:Is easy to test to see that if you hide a message, its only hidden in the particular sandbox that you are using when you clicked Hide.
Some messages have the sandbox name in the detail, so that effectively hides the message for a particular sandbox.
Posted: Thu Sep 12, 2013 11:27 am
by Tomwa
Just an FYI the problem occurs after restoring my group policy settings from a backup, evidently they were the cause. Simply resetting to defaults is enough to fix the problem and it is easily reproduced.
Posted: Fri Sep 13, 2013 4:30 am
by tzuk
I am not sure this can explain it.
I haven't made any changes to group policy settings on my test systems,
so I should have the default group policy.
Why don't I see this problem?
Posted: Thu Sep 26, 2013 11:18 pm
by Blackbeat
I think he means that he had none-default settings and that was the cause, not default settings as you do (which is why you wouldn't have the error).