I have a Server 2008 R2 x64 box that is being used as an NComputing vSpace server. We create users on the server dynamically via a DLU policy from ZCM 11.2. Semi-frequently, I have been seeing users' sessions stuck at a black screen immediately after login (sometimes a blank screen with just wallpaper, but no icons).
After spending a week or two thinking it was a ZCM policy issue, I found document ID 7006892, "Session "hangs" when attempting remote login to Windows 2008 R2 Terminal Server." The document seemed to describe my issue exactly. "When a user attempts a remote login to the Windows 2008 R2 server running the Novell Client 2 SP2 for Windows 2008 R2 (IR2a), they are presented with the Novell login GUI as expected. They enter their credentials and then they are taken to a pre-desktop screen but the desktop never appears. If the user starts Task Manager and runs Windows Explorer, the desktop will appear."
We were indeed running Client 2 SP2 IR2a at the time, so at the end of the day, we updated to IR4a, hoping this would resolve things. Well, things were good for the first few hours the next day, but then we started to see the problem again. I see the issue both with users created dynamically via the DLU policy, as well as when logging in with a local administrator account via "Computer Only Logon." Is it possible things re-broke in IR4a, or do we have a different issue going on altogether?
After spending a week or two thinking it was a ZCM policy issue, I found document ID 7006892, "Session "hangs" when attempting remote login to Windows 2008 R2 Terminal Server." The document seemed to describe my issue exactly. "When a user attempts a remote login to the Windows 2008 R2 server running the Novell Client 2 SP2 for Windows 2008 R2 (IR2a), they are presented with the Novell login GUI as expected. They enter their credentials and then they are taken to a pre-desktop screen but the desktop never appears. If the user starts Task Manager and runs Windows Explorer, the desktop will appear."
We were indeed running Client 2 SP2 IR2a at the time, so at the end of the day, we updated to IR4a, hoping this would resolve things. Well, things were good for the first few hours the next day, but then we started to see the problem again. I see the issue both with users created dynamically via the DLU policy, as well as when logging in with a local administrator account via "Computer Only Logon." Is it possible things re-broke in IR4a, or do we have a different issue going on altogether?