RDP sessions disconnected during install of SP4

[Sleurhutje]

Hi,

I tried this several times on different servers and every time the same.
When installing W2K SP4 by using a RDP session as administrator, the
connection is broken when an inventory is made by the service pack. I have
to wait about 30 secs and then I can logon to my previous session to
continue installation.

The WAN link is SDSL 2.3MBit up/down stream with aVPN tunnel (tunnel stays
up, ping doesn't show any problems). All servers are fairly new Compaq
ProLiant ML310/ML330/ML350 servers with PIII/Xeon CPU's.

Is this a normal behaviour???



Jeroen

 

[Apocs]

Do you have any other problems with this connection ?

Otherwise you might go onsite to the remote office, if it
is not to far away, to install SP4 localy.

Tip: SP4 is causing problems with TS server, better wait
with installing SP4. Try installing SP3. If you experience
slow logons/logoff, programs hanging ("end program now")
consider installing KB324446 fix. Further more you can
install all the latest security pacthes since SP3.

De groeten

 

[Sleurhutje]

Nope, all works fine. Even with SP4 there are no problems with any
applicatiosn or connections. Installing SP4 locally is possible but aren't
we all lazy people who want to manage their (customers) servers from their
desks???

It's only on SP4 from a remote session (either in admin or appl mode) when
the SP has done it's decompression and checks for necessary files to
install/replace. All of a sudden at about 35% the connection is broken (RDP
only). After this phase is completed, I can logon again. When pinging the
server, or even doing a copy during this inventory there are no
interruptions.


Jeroen (groeten terug)

 

[Vera Noest [MVP]]

Check:

215465 - Installing Service Packs from Terminal Server Client
Sessions
http://support.microsoft.com/?kbid=215465

which first states that installing SPs from within a TS session is
unsupported, but then continues to say that this is fixed in SP3.
But the wording is a bit strange, it almost reads as if it is
fixed for SP3 specifically, not for all subsequent SPs. I can't
say that I am surprised by the behaviour you see, regarding what
has to be done during installation of a servicepack.