Have a SUS Blog that is staffed or updated during the monthly Patch release so we can quickly and efficiently locate any problematic updates.

For example we had various issues last year with different monthly .NET updates and this past week with the March updates, a known PXE issue impacting SCCM due to an update. I also had to open a CritSit case Sunday evening because our SUS server could not synchronize with Microsoft internal servers and was told it was an internal Microsoft server issue but it was not posted/blogged or communicate anywhere for customers. We should NOT have to open Premier or CritSit cases if Microsoft is AWARE of a known SUS issue.