So, I finally decided to try out SP1 for Windows 2008 R2 on one of my domain controllers. It's been fine on my Windows 7 workstations and most member servers.
Anyways, I copied the SP1 executable (didn't want to wait for the download) to the server and waited. Then waited some more. It took about 2 and a half hours for it to complete. When it finally got back to the logon screen, the mouse and keyboard were frozen. Ugh. Tried to connect remotely but had no luck.
Power it off and back on again and all seemed okay. Got the message that SP1 is installed and seems to be working okay (this is just a domain controller/DNS server...nothing else).
A few days later and I'm trying to connect to the server remotely and I find that I can't. The server was fine before SP1. When I attempt to connect with mstsc, I'm prompted with the certificate dialog, I say "okay" (nothing unusual to me yet) and then the box disappears for half a second before the logon box reappears. Subsequent attempts don't have the certificate dialog, it just comes back to the logon prompt. No errors.
I can logon directly to the server console. When I check the logs, I see the "Windows logon service terminated unexpectedly" message at exactly the same time I attempted to remotely logon. Rebooted the server but the problem persists.
Port 3389 is active on the server(I can telnet to it) and I'm actually seeing success entries in the security log for my logon attempt followed by an immediate logoff success. The accounts I'm using have remote access rights and remote access is enabled (all terminal service clients). Using an account without proper rights will generate a "this account doesn't have rights" message as expected.
I'm tempted to rollback the service pack, but I really don't want to wait another 2 hours for it to be remove and I really don't want any more surprises. Has anyone run into this and is there a fix?