RDP anomalies with Windows 2003

I am having some anomalies with TS/RDP on Windows 2003
that I have not seen with Win2K Server.

1. Screen refreshes seem to fail. Closing a program may
leave residual images on a Windows underneath, and have to
minimize and restore screens when the screen content
changes.

2. Here is the big one. I regularly run patches to my DB2
system via a TS/RDP session to my Windows 2003 DB2 server.
Everything will appear to run correctly, and the tools
will report no errors, yet portions of the patch will be
incomplete. In the most recent example, all the drop
procedure statements ran just fine. The system reported
success for all statements, but the replacement procedures
were not created. Running the patches locally on the
server has never yet caused an error of this type.

My software vendor insists that because I am the only one
using Windows 2003 and RDP to run these updates, the
problem must be here. Are there any known issues with RDP
interfering with DB2/SQL statements or other processes?
(If not, maybe I need to post this in a DB2 forum.)

Hi Brian,

when applying patches try to connect to Windows 2003 console. Procedure
would be something like this

Start -> Run -> mstsc /console -> click OK.

Once the mstsc loads enter IP or name of server. Run the updates.

This procedure will actually log you on to server console.

If you e.g. log on at console in server room, do some work and leave
appliction running and go out of server room to your desk then from your
desk run mstsc /console you will see your running application and you will
be able to continue your work. Screen in server room will be locked at the
time.

I don't have any other answers for you, but I hope this helps,

Mike

"Brian" <(E-Mail Removed)> wrote in message
news:15ac01c48550$9f902b40$(E-Mail Removed)...
> I am having some anomalies with TS/RDP on Windows 2003
> that I have not seen with Win2K Server.
>
> 1. Screen refreshes seem to fail. Closing a program may
> leave residual images on a Windows underneath, and have to
> minimize and restore screens when the screen content
> changes.
>
> 2. Here is the big one. I regularly run patches to my DB2
> system via a TS/RDP session to my Windows 2003 DB2 server.
> Everything will appear to run correctly, and the tools
> will report no errors, yet portions of the patch will be
> incomplete. In the most recent example, all the drop
> procedure statements ran just fine. The system reported
> success for all statements, but the replacement procedures
> were not created. Running the patches locally on the
> server has never yet caused an error of this type.
>
> My software vendor insists that because I am the only one
> using Windows 2003 and RDP to run these updates, the
> problem must be here. Are there any known issues with RDP
> interfering with DB2/SQL statements or other processes?
> (If not, maybe I need to post this in a DB2 forum.)