This is not equivalent to command polling. I’m not even sure that issuing it to a client would actually cause it to poll for commands. It tells the client to send a full report with all property and applicability results.
You can address this by opening up UDP on port 52311 on all of you clients and firewalls to your relays. It won’t solve all cases, but it will help with many of them. In some cases you might want to put some relays behind WAN connections to help with both bandwidth but also with UDP notifications. You mention this happens with your clients connected over the internet, and in most cases there isn’t much you can do about that.
As far as I know there isn’t an API that can be easily triggered to tell the client that it should do command polling right now. There also isn’t an actionscript command. I have been asking for both of these things for various reasons for a long time now. CC: @AlanM
One option that I have been thinking about is to have an offer that would set the command polling interval to 10 minutes, then have a policy action automatically set it back to a less aggressive value after the next successful poll for commands. I would generally recommend something in the once every 3 hour range for all clients and once an hour for those that commonly communicate over the internet. (generally WiFi devices)
This is the best option I can think of as a way to trigger command polling.
Related:
- https://developer.bigfix.com/relevance/reference/client.html#last-command-time-of-client-time
- https://bigfix.me/fixlet/details/3798
- https://www.bigfix.me/fixlet/details/3801
- https://bigfix.me/fixlet/details/21066
- https://bigfix.me/fixlet/details/3799 ( I would be more aggressive than every 12 hrs )
- https://bigfix.me/fixlet/details/6117
- Forcing Computer Refresh Through API - #11 by jgstew
- Odd BESClient behavior on laptops - #8 by jgstew
- Clients failing to refresh unless service is restarted
- Command polling - #6 by jgstew