Dear all,I haveaserver. Roughly once a week, at different times,will not let me login.the Hyper-v servers are still running and working fine.Basically the symptoms are thatI can connect RDC and logon, its just stuck on the 'Welcome' screen.the same happens when i try to logon locally tooThe only way to "fix" the problem is to power off the server.Checking the event logs hasn't been helpful as there aren't any nasty errors in there.I am running Windows Server 2008ENTERPRISE x64 Edition. DL380 G5.HP Server are fully patched.I am running symantec endpoint management and backupon this server the remote consolefor the symantec tools still workThis problem now has me seriously worried. as i don't want to redo all the virtual servers

Hi, Please understand that to troubleshoot this logon hanging issues, we usually need to perform debugging. However, in this forum, we do not provide debugging support. If you would like to perform debugging, please contact Microsoft Customer Support Service (CSS). To obtain the phone numbers for specific technology request, please refer to the website listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US, please refer to http://support.microsoft.com for regional support phone numbers. Having said that, I'd still like to provide the following general troubleshooting steps to see if we can eliminate this problem: Note: Please perform a complete system backup first. If any unexpected issue occurs, we can quickly restore the system to the current status. 1. Update the drivers for the motherboard and video card. 2. Scan your system to make sure that the system is virus free. If you have recently installed any software, hardware or drivers, please remove them. 3. Ensure all the hardware devices, installed device drivers, and installed applications are all compatible with Windows Server 2008. 4. Disable all the third party startup programs and services by using the MSConfig.exe utility shipped with Windows Server 2008. To use this tool, you can refer to the following Microsoft Knowledge Base article. Although this article is written for Windows Vista, it also applies to Windows Server 2008. (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135 If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit. However, if the issue still persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon. Thanks! Tim Quan - MSFT

Hi Markod21uk I am experiencing the same problem with 2008 x64 on the exact same hardware. Did you ever figure this on out? Many thanks, Paul.

I have 3 x DL380 Windows Server 2008 Enterprise x64 servers on a single site, and am also experiencing this issue with one of them.Did anyone get anywhere ?What else do you have running on the system Markod21uk / Paultown?I can access the server via Computer Management, and i have been able to kill processes (via terminal services manager) to try and free the box box up, but at the moment havent found the exact cause.Could you tell me if you have a anti virus product on the machine and which one it is, also does you box have exchange or exchange management tools on there ?Cheers

Sorry for the late response. We have nothing else running on ours, it's a dedicated SCCM server, nothing else apart from SEP11 AV client (no proactive or network threat protection).

I am seeing this same problem too on HP BL460c blades and a HP DL585G2 server. This happens at logon only after a reboot. If I wait somewhere between 20 and 40 minutes, it will sometimes let me in. Once I am back in I can logon and logoff without any issue. It only happens the first logon after a reboot. If I do not logon to the server and treat it like a headless server, it functions as expected and never freezes. Here are some specifics about my hardware: HP BL460c and HP DL585G2 servers Windows Datacenter x64 All are or have been Hyper-V hosts (Other W2K8 x64 servers are not seeing this issue) Intel and AMD processors (Quad and Dual cores) 32GB or 64GB of RAM Fiber Channel SAN connected (QLogic) Using HP Multipath Software. No Antivirus I currently have a case with Microsoft open on this to see what is happening, but that is moving very very slow. Glad to know others are having the problem. Would be better if there was a solution. I am getting the Yips when I need to logon to server. If you guys want to get on a call and compare notes, maybe we can escalate the case if it turns out we all have the same problem. Rob McShinsky http://www.virtuallyaware.comRob http://www.virtuallyaware.com

I currently have a HP DL380 G5 32 bit Server 2008 that is stuck at the Welcome screen also. This has to be something with HP and Server 2008. Maybe a recent update broke something?

I have the same problem too but my hardware is a Dell PowerEdge R710 with an EqualLogic attached. I also have Windows Server 2008 64 bit with Sumantec Endpoint 11. I am eager for a solution. Is it the anti-virus software since that is a common factor among all of us, in addition to the OS version.

Win2k8 issue, this has impacted anything running Windows 2008 -virtualized or not: http://support.microsoft.com/kb/952664

So I am guessing this is a problem that microsoft cant even fix. we have a 2008 server thats deadlocked right now. copmpletely up to date. when it does this you cant log in to the server, and cant remote in to it, cant even remotely access the registry.

I've experienced this on Dell Hardware, running Windows Server 2008 and Hyper-V. If was one of the virtual machines that was hanging, so I couldn't log into it, but it was still doing its job(sending/receiving the correct data). So this isn't HP specific, it looks like Server 2008 or maybe a hyper-v issue

Win2k8 issue, this has impacted anything running Windows 2008 -virtualized or not: http://support.microsoft.com/kb/952664 I'm not sure that this KB has any baring on the issue we are facing. The problem for us is pretty infrequent but still a major annoyance as a hard shutdown/restart is needed to bring the server back up. It also seems like it's not particularly related to hardware/software as most of have completely different setups. Is there someone from Microsoft who has seen this? The only information that stands out in the event viewer just before it freezes is a HP Wbem Dump is ours. I'm also not entirely convinced that this is even the problem as it could have frozen well before we attempt to RDP. Has this problem been flagged with Microsoft yet? I'm asking because as I said this is a pretty rare occurrence for us but still a major problem and would be nice to get a little more feed back from Microsoft on this.

I have reposted this thread as it is marked as answered when it clearly isn't. Please see:- http://social.technet.microsoft.com/Forums/en-CA/winservergen/thread/29a6a753-0187-42b8-a01b-1a023043727b