Mark
My feedback
-
27 votes
Mark supported this idea ·
-
4 votes
Mark supported this idea ·
-
17 votes
Mark supported this idea ·
-
12 votes
Mark supported this idea ·
-
11 votes
Mark supported this idea ·
-
3 votes
Mark supported this idea ·
-
6 votes
Mark supported this idea ·
-
21 votesUnder Review · 5 comments · Endpoint Protection » Device Control · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
28 votes
Mark supported this idea ·
-
22 votes
An error occurred while saving the comment Mark commented
Seconded.
Mark supported this idea ·
-
2 votes
Mark supported this idea ·
-
322 votes
Mark supported this idea ·
-
7 votes
Mark supported this idea ·
-
7 votes
Mark shared this idea ·
-
28 votes
Mark supported this idea ·
-
15 votes
Mark supported this idea ·
-
35 votes
Looking into possible solutions as part of the current roadmap
Mark supported this idea ·
-
252 votes
We are looking at changes to help avoid large numbers of reboot related alerts. This work is not yet planned, so I can’t provide a date, but the proposed implementation would be as below.
For urgent reboots, e.g. to complete removal of a competitor product being replaced, users will see a notification immediately.
For non-urgent reboots (i.e. where protection is maintained), users will not see a reboot for the first 2 weeks (typically they will reboot in this time anyway, e.g. for windows updates).
If not rebooted for 2 weeks they will see a notification they can dismiss.
The reboot notification be persistent on an endpoint; it will require acknowledgement by the user to clear it. We would expect to have a registry key to be able to prevent this behaviour for systems like shop tills, advertising displays and so on.
If a further week goes by without a reboot…
Mark supported this idea ·
Agreed, can see no reason why we shouldn't be able to expand any column on any screen.