KB957097 update breaks TS

Windows Server 2003.

Unable to connect to the server using Terminal Services after installation
of the KB957097 update. After the update, TS allowed a connection and the
restart message(part of the update) was confirmed. After the restart the RDP
client responded as if TS was shut off. The server was found but the login
screen would not appear as it does normally.

Ths was done twice to confirm that the update was really the problem.

Had to uninstall the KB957097 update from the Console.

Should I Reinstall it and if so how should I get TS to function normally
again?

See the section "How to obtain help and support for this security update"
here: http://support.microsoft.com/kb/957097

I am only replying, as I have a terminal server, but I have also had a harrowing experience with the dreaded KB957097 update.

I am running a native server 2003 Forest, with Native Exchange 2003 servers. The issue i have had with this update is due to 1 server not getting it, as I manage the patches on that server manually (due to past issues). The server is an Exchange front end server, but that is not relevant.

The issue i have had is with the Domain controller (on both the local and root domains) had this patch. Any server/workstation without the patch, if rebooted would hang at "applying security settings". It took quite a while to realize that the lack of the patch was the issue, and that once applied in safe mode (yes, i installed a patch in safe mode, i know), the server successfully booted in normal mode.

There is currently no information that relates to this patch and the problems i have had, so i wanted to make sure that i get it out there somewhere and this was one of the only forums referencing server 2003 and KB957097 issues.

I will be attempting to update my terminal server (which i also do manual patch management on) this weekend, if it reboots and does not have the patch, I am willing to bet that would be a bad thing.

Have you had any developments since your last post????

In my case, the problem turned out to be the graphics driver on the CLIENT side

NVIDIA (QUATRO NVS in my case) pointed me to Dell, who sent me a BIOS flash. Problem sorted...
phx