Just to let everyone know how this was solved in this environment: we use App-V and found that the App-V Management service on the streaming server was unstable. For some reason the service sometimes stopped, which we did not always notice in the pilot environment, as the App-V client then used the cached sequence. We do not use App-V to place application shortcuts on the desktop, but the App-V client does try to communicate with the streaming server, and that seemed to hang the logon process. We did several tests and the relationship between the "pnshell not responding" and the service is definitely there. So keep an eye on your App-V servers if you have some....  Patrick
Hi everyone,  In our pilot environment (v7.2) we regularly see pnshell.cmd hanging during the logon to the desktop. More precise: we see pnshell.cmd minimized and a white dialog "process not responding". It happens with various user accounts and on both pilot servers. We have tested with no resources assigned to the user, but this shows no difference. Eventually the message disappears and desktop is displayed, but it does slow things down and looks very ugly...  Is there a debugging option that can help us trace what is happening during the logon?  Regards, Patrick Warning  -- EDIT -- OK, I found the /Trace and /Log options with pnshell.exe. Interesting logs, but still not clear what's hapening.... About 10 seconds are spent on managing shortcuts (5 to delete, 5 to create). That seems a lot for about 10 shortcuts.
pnshell hangs - debugging?