Related:
- Stubborn Clients
- http://bigfix.me/relevance/details/2999087
- http://bigfix.me/relevance/details/2996925
- http://bigfix.me/fixlet/details/3798
- http://bigfix.me/analysis/details/2994765
- http://bigfix.me/analysis/details/2994616
I wonder if the laptop IP address changed through DHCP, which would then cause the relay to be sending the UDP notifications to the wrong IP until the client re-registered. I believe the client is supposed to handle IP changes and re-register, but I’m not sure how quickly that happens.
If possible, you should check what the client’s IP was at the time as well as what the relay thought the IP was for that client. If this happens again, you could also shut down the BES Client service and then start something to monitor for UDP on the BES Client port and see if the UDP packets are actually coming through or not.
This seems less likely, but perhaps a firewall is letting UDP in on the same port it is seeing TCP go out from the client for a time, but if it does not see TCP going out for long enough, then it starts to reject the UDP coming in for the client.
You might consider lowering the client registration interval, particularly for mobile clients.
It is still a good idea to investigate what is happening with the UDP notifications, but I would recommend the following regardless:
I would strongly recommend reducing the Download RetryMinutes to 1, which used to be the default, but was changed to 10.
I would recommend enabling command polling to be at least once every 24 hours for all clients, and more aggressive for mobile clients.