Using SWA with WIndows Remote Desktop - slow response?

[deyjvu]

Our customer has setup Windows Remote Desktop support for the SWA and is experiencing slow response/connectivity.

He has now upgraded to Windows 2003 and the latest Remote Desktop and has found the following:

- at 8bit colour the performance is not noticeably different to W2K @ 8bit
- at 15/16bit colour the performance is noticeably improved.

Does anyone else use this setup and do they have any other suggestions for improving performance in this environment?

The reference to colour is related to the SWA using colour in painting this client to the screen. It was hoped that the colour could be manipulated on the SWA but this isn't possible.

[ScalixSupport]

Is there a reason why your customer needs to use Remote Desktop rather than providing direct access to the web application ?

Cheers

Dave

[deyjvu]

The subject says it all Dave, I really don't know why they have set it up this way but this is what they want to use.

Are you suggesting that they should re-think why they are using the remote desktop?

[ScalixSupport]

It's just that none of our design is based on using this through Remote Desktop. It seems a strange thing to do given that SWA is a web app. Understanding their requirements may help us a bit but it's like asking why the screen refresh rate when playing Quake through VNC is so slow :-)

Cheers

Dave

[abnormaliti]

In our case Scalix is being used in a thin client environment. i.e. A user accesses their desktop via an RDP session on a cluster on Windows Terminal Servers.

Therefore the users have no choice but to use an RDP session to access SWA. Other clients are over kill, i.e. Outlook or Thunderbird, or inappropriate.

For example, a user doesn't require the advanced features, and cost, that an Enterprise user has but access to a personal calendar and contacts would be beneficial. The only option is SWA. When iCal support comes this may change but will that only work with Enterprise user accounts?