Hi Ed,
Thanks for replying, most appreciated. I can definitely say that at least one of the problematic machines was not shutdown as it was mine and I logged off at the end of the day yesterday. After discussing with my colleagues, I am sure their machines were not shutdown either but you are correct about users not accurately describing what they were doing (or not doing).
The pool power setting is interesting, we were set to the default "Take no action", so when we logoff, the client machine should not be suspended, but I have changed it to "Ensure desktops are always powered on" to be sure. I am using the High Performance power settings and have disabled all power saving settings there for display, HD, and NIC.
The strange thing is that we haven't changed the View environment in the last several months before the problem started happening a couple weeks ago. We had been on 5.0.1 for months without issues, then about 2 weeks ago this started happening every single night. I upgraded to 5.1.2 in the hope it would be resolved and because I am sure VMWare would have said to do that when we opened the case, but no change at all this morning when I came in.
The only other things we did was to install Windows patches, to both our physical and VDI clients, and that was in the same time frame, so it is entirely possible that this is not a VMWare issue at all but if that is the case I would expect Google to find more results for me and it isn't. Maybe if we are lucky the VMWare support folks may be able to find a clue in the logs to point us in the right direction.
Mike