Bumping this.

This problem is still on-going. Apple still hasn't provided us with ANYTHING, it's actually quite sad especially because we have their engineering teams involved.

We have since grown a bit adding an additional 18 conference rooms. When we did this, we decided that we would remove all of these machines from JAMF (66 Mac Minis) and redeploy them over a weekend. While this seemed to help the issue, we have now run into it again in multiple rooms. Same WindowServer process is crashing, same forced logout to the login window when this occurs. We are about to install Intel NUCs in place of our Mac Minis in all 66 conference rooms and I would really prefer not to. Does anyone have ANY idea(s) that may help resolve this issue/discover a root cause?

Couple of questions for you. Does this logout occur right in the middle of using the system, or is it happening when it's been sitting idle for a little while?
If it's only the latter, have you checked to make sure you don't have a Loginwindow Configuration Profile applied that has the "Log users out after: [x] minutes" option checked?

For reasons that I still don't comprehend, when a new Loginwindow Config Profile is created in Jamf Pro (even in the latest version of 10.10.1), that option is automatically checked. It should not be, in my opinion, but, it is. I'm wondering if that's part of what's going on here.

Even if that option isn't checked, I would start by taking an affected machine and removing all config profiles from it, except of course for the main MDM profile. See if the problem persists. You already discovered that only enrolled machines exhibit this problem, so something from Jamf is likely causing it, but start taking things away systematically on one affected machine, until the problem goes away. This would include any policy scopes. If the machine is in smart groups scoped to policies, add it to the Exclusion tab in each policy to make sure it's not going to run on that system. Once the problem stops, you'll at least you'll have something to focus on for further investigation.

@mm2270 Appreciate the suggestion, but we completely removed all of our Mac Minis from JAMF (see follow up post). They are literally running clean installs of Mojave with nothing other than Zoom installed and this is still occurring. :(

I believe for the most part they are sitting idle when this occurs, but I've also seen the issue happen while in use.

@aconte I have only anecdotal information at this time. We (Notre Dame) use Zoom heavily on desktops and in conference rooms and "enclaves" (multipurpose work areas) and have not seen this issue. I've passed it on to our help desk, though, just in case it crops up. If I find out anything, I'll post it.

@bcarter5876 Thank you! You're running Zoom Rooms on Late 2014 Mac Minis? If so, what OS are they on? I'm concerned it's in-line hardware at this point, but what we use is pretty basic and changes depending on the room.

It must be something in the environment that is causing this issue. My quick research on Google shows that this is an issue to do with the video card/drivers. I am assuming the machines having this issue are plugged into a screen? How about the MacBook Pros experiencing this? Are these users working off an external monitor?

In addition, others are saying it may be related to the Safari browser. There has to be a commonality between all of these machines experiencing this issue. Any idea?

@aconte We have it on all kinds of Mac hardware, including Minis and all sorts of MacBooks. We're running mostly High Sierra on staff/faculty machines, with some early adopters or new equipment owners on Mojave.

The stand alone Macs don't have any additional hardware involved, but I will check on how the conference/enclave rooms are set up. We use Zoom a LOT for dispersed meetings.

@bcarter5876 I'm experiencing exactly the same WindowServer crash on two different computers (Mac Mini and Mac Pro both running Mojave). No JAMF installed on either though! Have you made any progress with this?