Status not compliant
Status NOT COMPLIANT overwrites Status OK in DCC this is not good because a NOT Compliant Drivelock Agent is stil OK. There should be a separate sub status displayed, many customers turn off the compliant feature so it doesn't happen
Jan Reinders
shared this idea
Please use DOC options
-
AdminUdo Riedel
(CTO, DriveLock SE)
commented
PM-1134
-
AdminUdo Riedel
(CTO, DriveLock SE)
commented
Many thanks for your input. The DriveLock Operations Center (DOC) will replace the DCC. In the DOC, we will soon be working on a separation of risk score, agent status and compliance status. This will probably solve the problem you mentioned. However, the compliance status will be the last issue to be addressed. Compliance in the true sense of the word means that an actual status corresponds to a desired target status. This is not quite the reality in current implementation.
-
dluv 40542190
commented
good idea - And I woulkd prefer to have the List of possible DCC status information messages "configureable", so I can decide which status I would accept prior another status - as the main status.
A "right mouse click" at the "main status" within the single DCC helpdesk row, may also offer a popup, to see "all multiple status entries" a client PC may have at the current time.