One of our escalation folks just happened to be visiting my desk so I asked him about this.  Apparently we have an issue where wrse.exe will hang sessions, which is why you used to see an instance for each user.  Either due to a recent reboot of the server, or a recent update from us that restarted the process, those are all cleared out and you're only seeing the user session for whoever is logged in now.  It's possible that the recent update has changed the hanging behavior, although we're not sure what would have done that, so we're still investigating.  If you could keep an eye on it and let me know if the multiple sessions start showing up when more people have logged in, then I can pass that along to the engineering teams.

---

I've seen it stated elsewhere that you guys use Terminal Services.  If one of your admin folks logs in and opens task manager, do they see a wrsa.exe process running for each *logged in* user?  Should they?  That's what we've always seen and when the user logs off, the process would go away.  I don't recall having it hang more than once or twice since June.  I just want to know what the expected behaviour should be so I can tell my clients with **bleep** admins the correct answer.

---

So there should be an active process for every currently logged in user; if that isn't the case then go ahead and contact our support so we can delve into it.

---

Excellent!  Thank you very much.  Sorry that I made this difficult.  

---

No worries, glad you brought up the issue, as I get to learn something new 🙂  Let me know what support says.

---