Whats best practice for optimising IE??
A 50mb profile on a 56K link, sounds like a bad move to me. Is there a reason why you need to store so many temporary Internet files? Hope this helps. Jeff Jesus Loves You
-----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Rosemary Sarkis Sent: Thursday, August 05, 2004 8:23 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Windows 2003 Terminal Server performance tips for IE?
Speed is OK on LAN via WTS. Extremely slow on 56k modem (I know its a ridiculously slow link) but I was expecting the speed to be much better.
Also slow on 256k link.
The IE cache goes to the default location - profile I believe. I have reduced the temporary internet files to 50Mb via GPO - no other changes were made. There are no files in the cache. Its just sluggish and slow in IE via WTS - IE is much faster if running via the local workstation browser
I just wanted to see if there were any tweaks that would increase the speed and make the experience more responsive. Im trying to migrate a small office off local apps to a Windows Terminal Server. Users won't be happy running on a browser which is 2-3 times slower than their current setup..
What bandwidth are you using? Are you on a Lan or remote? If you're remote then it don't surprise me that a 2MB graphic takes a while - Terminal Services is not a great solution for graphics-type tasks. With IE6, you might check where you've directed the Cache - if you've just pointed Local Settings to a netwrok share, that might cause problems. Again, though, if you're downloading big graphics it will be slow.
I have had one user complain about internet access speeds. While investigating I looked in his cache and discovered some very large graphics files of not entirely clothed females. I merely mentioned that "Large graphics files may not work as well over TS as on a local machine".:)
-----Original Message----- From: Rosemary Sarkis [mailto:rosemary_sarkis@xxxxxxxxxxx] Sent: 04 August 2004 11:52 To: thin@xxxxxxxxxxxxx Subject: [THIN] Windows 2003 Terminal Server performance tips for IE?
I have a 2003 WTS I need to fine tune. Server runs std office apps - Office 2000, Project 2000, Visio 2000, Access 2000 etc. All these apps seem to run at respectable speeds. I have disabled all animation, removed actors etc and also looked at some of the documentation on Brian Maddens site and implemented accordingly.
My issue is mainly with IE6 performance. It runs really slow via Terminal Server (runs fine on the LAN outside of TS). Also have speed issues when viewing JPG files. Takes quite a while to load a 2Mb Jpg in Photo Editor or the Picture Viewer. I am the only person using the server at this stage and the server is specced as follows:
CPU 3Ghz x 2 RAM 2Gb Raid 1 disk config
The images load but very slowly - u can see the bar slowly scroll across the screen (I was expecting much better performance). Im running the latest MSTC client.
IS there anything obvious I can do to improve IE and JPG loading performance? Any GPO I can set?