The odd relay I’ve seen this happen on I just usually uninstall, delete the relay folder and its contents and reinstall. Probably not the best approach but it works in a pinch.
I haven’t had a chance to do any reading on the subject but would you happen to know what some of the possible causes are of that particular relay behaviour.
BES Relay / BES Server Setting: Download Cache Size
I tried it but the affected relay pc is only showing as not reported but it is working on other relays. Pls tell some way other than manually deleting the folders as I cannot manually delete the folders on more than 2500 relay pcs.
This came up in my searching as we have run into this issue as well… Seems that the only solution is deleting the relay cache directories …
I created a “policy” action that checks for relay folders over a specific size, and then stops the relay service, deletes the cache directory, and then starts the service again…