I installed the 9/23 updates for WHS a little while ago... (Everything has been functioning just fine for several months up to this point. Upgrades to PP1, etc. all fine. Did NOT install either of the HP-provided Add-Ins though.)

Following the update I found that the MSS had not been "discovered" and the server icon was grey. The connector failed and executing "Discovery.exe" did not find it. I checked that all cables were connected and that the appropriate switch/router indicators were lit to indicate proper connections. I powered the MSS off (quick push of the power button on the rear followed by a wait for a shut down) and on again and observed the following in this order:

1. The MSS did not connect to either my Vista or my WinXP clients
2. The MSS was not visible on the network
3. The Connector Troubleshooter could not find the server
4. I could not connect to the server via RDP using the server name ("ServName")
5. I could not connect to the server via RDP using the IP address (192.168.xxx.yyy)
6. I could ping the IP address (192.168.x.y) successfully
7. I could ping the server by name ("ServName") successfully
8. Above was the case through three power cycles of the MSS

I went through this three times. The delay between first and second attempts was over an hour (dinner break); the delay to a third attempt was about 30 minutes. Before trying another round I did check that the icon had not changed to green! (Prayers did not seem to help.)

Following the last (3rd) cycle of this I tried the RDP (by name) again (icon still grey) more out of frustration than anything else. (I had been interrupted with a phone call).

It worked! As it connect logged on the icon turned green. (And looking at the time of "balancing" it obviously did that right after being turned on.)

I have restarted the MSS successfully since this experience (from the console) and even shut it down again. All is behaving normally at this point. The only indications of any anomalies are (a) a string of warnings in the Application Event Log reading "TZO Key Check Failed Success", and (b) an abnormal number of informational MSSQL$SQLEXPRESS messages indicating that the SQL Server was having start-up difficulties and certificate issues. Other logs and messages appear to be consistent with past behavior. The SQL messages continued in the restarts and power cycles after the problem cleared up so I doubt those are related.

I mention this not just to start a discussion, but to warn folks that when this automatically updates tonight there may be some problems. (And there may some foul language to be overheard by family members in the morning). But persistance seems to help here. Maybe someone can find a way to boil this down to 2-3 steps! BUT THERE IS HOPE!

PS: I did manage to contain MOST of my more "colorful" language during this, knowing that there was an excellent community out here to help me should things go "south".