Ouch, bummer. Thanks for the quick reply. Do you usually restart just the service, or the entire server?
I'll add some follow-up details for future googlers: We had POC'd Boxer within IT for about 4 months prior to rolling it out to genpop. Flawless with ~10 people. At 50 users we were restarting weekly. At 100+ users it's a few times per day. It's gotta be load-related. Oh well... easy to automate rebooting these days.
I wrote a Powershell script to restart the service every 6 hours and set it as a scheduled task.
I've been fighting with ENSv2 on premise for the past two days with no luck. It looks like I'm going to have to get completely new certificates setup for it. It doesn't like the one that was configured for ENSv1.
OP here
Our MSP helped us wade through this. ENS2 is actually part of the Airwatch cloud service now. We created a new assignment profile for Boxer with some keys provided by airwatch support, pushed it to some test groups, and notifications just worked. Going on a month now with no problems.
For anyone coming across this post, open a ticket with Airwatch and let them help you.