 Richard,  I have felt your pain for so long with this issue and eventually support seemed to just give up.  Ian the support rep was a great guy but he never found a resolution.  I like you have been through everything and ripped the container down to nothing.  I tweaked the auto-log offs.  Ran through debugs to catch what was not closing on log off and nothing worked.  People would call me non-stop every day with the blue screen hang.  I spent most of my day in the management software logging people off.  Those that I could teach to go to the systray and get session properties from the vworkspace icon and click log off could fix themselves.  This cut down some support calls but I was still flooded.  I even built a new broker, new parallels server, new container all from scratch and minimal updates tracking everything I installed and it made no difference what so ever.   I have since upgraded my enviroment to 7.2 MR1 and things are working correctly now.  I had to go through and updat the broker, gateway, and ALL the clients on every workstation.  Plus update the PN Tools to .461 on all the containers.  This seems to fix the blue - gray screen hang on log out.  It also fixed my usb connectivity issues that we have with USB signature pads. As Ian and I expected it had to do with the USB hooks that PN Tools installs.  Let me know if you get a chance to upgrade to 7.2 MR1 and see if it helps you out also.    Jeff
Hello everyone,  I need help.  Bad.   This is my enviroment.  3 Dell Poweredge 2900 servers running Windows 2003 SP2 Datacenter.  Installed is Parallels Virtuozzo Containers 4.6 and for Quest we have 1 SSL GW, 1 CB, and the version installed is 7.2.  The issue I have is that when users go to log off everything starts to log off but then windows box that says "Logging off" never shows and it just sits at the background with no icons and Quest vWorkspace still shows the user logged in, not disconnected.  If you try to log back into the computer it just sits at the same background with no icons.   What I have done to troubleshoot is to install the old PNTools back to 7.1.0.356 and try it.  Still no change.  Looked at the running processes when it logs off and the only things running for that container are winlogon.exe and csrss.exe.  If you use procmon and kill the winlogon process for that container it logs the session off, or actually just kills the session all together and the user can log back in and runs fine.   I can also log the computer off through vWorkspace mgmt console.  The third way that I have had to train users on is to use the vWorkspace icon on the laptop and go to OPEN SESSIONS then click the log off button and it properly logs the computer off.  I have tried to debug the winlogon process on the computer but if you set the winlogon for debugging you will no longer be able to access the computer because of the way parallels works.  If I RDP straight to the computer and log off it works fine everytime, so this leads me to believe it is a quest vWorkspace issue for sure and not a parallels issue. I have been trying to get this fixed ever since we upgraded to 7.2 about 2 months ago.  Nothing shows in the event log for the computers or the server nodes.  I've opened a ticket with quest and have gotten no where so far with them and I also have a ticket opened with Parallels and verified it works fine there.  We made a plain jane container in parallels and tested log offs and it works fine with RDP then installed PN Tools 7.2 and then could no longer log off with the vWorkspace client but RDP still worked.  I've taken all the antivirus off the server and ripped that down as far as I could and still make it useable to users.  I have disabled all extra resource mappings in quest on the server and the client itself including the EOP and it has not made a difference.  If anyone can lead me down a new path for help that would be awesome.  Thank you.   - Jeff
Gray \ Blue Screen on Log off