Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 4398 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

Can I, and if I can how can I, modify the time before end points appears as not connected in the enterprise console

Peter Vroegop

Right now I see red crosses of every endpoint whice is shutdown yesterday and today not used.

This behavior decreases the attention value  of the red crosses. After all every day one of more endpoints are not in use.

As a result, the computers with in 'not connected' state for a long time can be overlooked, also the a potential problem can be overlookes.

When the time before the not connected state is flexible the not connected status has more attention value

Best regard,


Peter Vroegop



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

    Hello Peter,

    red crosses of every endpoint whice is shutdown yesterday
    this is the intended behaviour. Connected indicates that the endpoint's Message Router has established a connection with the management server. On an orderly stop the endpoint's MR sends a logoff message and the status changes to Disconnected.

    The connected status (which sometimes incorrectly persists) is not designated as an indicator of the endpoint's "health": First of all, an endpoint might successfully establish a connection - but not send any message, or accept messages but not process them (e.g. due to an endpoint-internal communication error). I daresay that many, if not most, endpoints with problems (except - naturally - those with connectivity issues) will correctly connect/disconnect.
    In other words, only a small subset of endpoint problems results in a prolonged disconnected status - thus you shouldn't read too much into this state.

    Christian

Reply
  • 0

    Hello Peter,

    red crosses of every endpoint whice is shutdown yesterday
    this is the intended behaviour. Connected indicates that the endpoint's Message Router has established a connection with the management server. On an orderly stop the endpoint's MR sends a logoff message and the status changes to Disconnected.

    The connected status (which sometimes incorrectly persists) is not designated as an indicator of the endpoint's "health": First of all, an endpoint might successfully establish a connection - but not send any message, or accept messages but not process them (e.g. due to an endpoint-internal communication error). I daresay that many, if not most, endpoints with problems (except - naturally - those with connectivity issues) will correctly connect/disconnect.
    In other words, only a small subset of endpoint problems results in a prolonged disconnected status - thus you shouldn't read too much into this state.

    Christian

Children
No Data
Unfiltered HTML