Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
  1. I log in to my Hyper-v host server
  2. I open the Hyper-V manager, select my server S1 and click Connect
  3. When I want to shut down server S1 or reboot server S1, I just click the start button and select shut down or restart (it's a server 2008 r2).

Now this is my problem. The Connect window turns blue (like the default background of the server) and doesn't do a thing (not even after 10minutes, I also don't see any cpu activity in the hyper-v manager).

Only when I select "Shut down" in my Hyper-v manager the server starts shutting down.

I only have this with this one server (it runs Exchange 2010 if that helps...)

In the Administrative Events from S1 I also see these warnings, but i'm not sure if they have anything to do with this problem:

Winlogon Event 6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (EndShell).

Winlogon Event 6006: The winlogon notification subscriber <GPClient> took 241 second(s) to handle the notification event (EndShell).

Update: at logon/logoff I have 1 powershell script running that logs the user (but other server have this also..) Update 2: I logged in via RDC to the server. I logged of and the RDC screen was blue and doesn't do a thing. When I went to the hyper-v host server and when I clicked 'Connect' I see the Ctrl+Alt+Del screen of the server. But when I login from the hyper-v host server and I log off I see the blue background there. It's like that the window is not getting a refresh or hangs.

I hope anyone could help me with this.

share|improve this question

closed as too localized by Dan, mdpc, Dave M, Ward, Khaled Mar 26 '13 at 12:35

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Actually, I think that you've titled your question wrong. Hyper-V does shut down your VM, as evidenced by pushing the "shut down" button in the Hyper-V manager. What doesn't work is telling the guest OS to shut itself down, which has little to do with Hyper-V. – Jake Oshins Feb 14 '13 at 0:13
I don't know if it has something to do with Hyper-v or not, I thought that it had something to do with it. – juFo Feb 14 '13 at 8:07
up vote 0 down vote accepted

I found the problem. First make sure you do gpupdate Next use the command: gpresult /z>policy.txt

If you have scripts running at logon or logoff check the policies via gpedit.msc.

My problem was a policy which was not set correctly and I changed an old script to a powershell script and that runs much better now!

Update: also make sure you didn't add any powershell scripts as regular scripts or the other way around, that would also result in a 'hang'.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.