Announcing the upcoming OpenMic event “Steps to Take in Troubleshooting Endpoint Manager Actions with a <not reported> Status” taking place on August 27th, 2015 at 11:00 AM EDT (15:00 UTC/GMT, UTC-4 hours) for 60 minutes. Presented by Adam McDonald from our IEM/BigFix L2 Support organization along with a panel of other product experts arrayed from our product management, development, and services teams.
For conference information and to add this event to your calendar see the announcement here.
Please post any questions you might have before and after the event in reply to this topic.
IBM Security Systems Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format.
To be on the mailing list that gets notified about Security Support’s Open Mic webcasts, send an e-mail to isssprt@us.ibm.com with the subject line: ste subscribe Endpoint And Mobility Management
We have agents that and firewall’d …they select a relay and connect. Custom properties and policies are applied and work. Then they become greyed out, unreachable. Relay_server1 and relay_server 2 in besclient.config are still correct for selected relay. the Log shows that it is trying to connect to the master server (firewall not open to the agent)… Why is the agent reverting to the master server. there was 2-way communication before.
Someone asked a question on the OpenMic today: Is there anyway to tell how long a client is taking to get through its evaluation cycle so I have a good idea of what I should set the command polling interval to so as not to disrupt the client’s evaluation cycle too much with gathering?
At the bottom of the article is an analysis that can be imported into your actionsite via the console and activated that will return data an array of performance counter properties.
The property “Average cycle seconds” will be useful to in making this decision. It returns the average amount of time (in seconds) the evaluation cycle has taken in the last 10 cycles.
To get useful results after activating the analysis it is advised to let the analysis evaluate on the endpoints for a good 48 hours before using the results to make decisions from the values returned.
I would advise to keep the command polling interval to at least 30 minutes or greater. And not to set the command polling interval to less than double the average the cycle in seconds. Opinions will probably vary on this based on deeper experience, so I invite others to comment to that affect.
I attended this meeting but missed a good portion of it due to other conflicts. It still hasn’t been published to the IBM YouTube channel. Any update on when the recording will be made available?
Please post any questions you might have before and after the event in reply to this topic.