Web Browser fo choice for a Terminal Server environment
I just looked at it a bit and it seems that modern brwosers are real memory menace.
IE8, FF and Chrome all have about the same memory utilization, while Opera 9 uses about half of what they use.
Regarding that I need to run TS environment for a significan nuber of users on a powerful server which runs 32bit Windows, and therefore can use only 4GB of ram, -> which one is browser of choice?
IE8, FF and Chrome all have about the same memory utilization, while Opera 9 uses about half of what they use.
Regarding that I need to run TS environment for a significan nuber of users on a powerful server which runs 32bit Windows, and therefore can use only 4GB of ram, -> which one is browser of choice?
FireFox beats out Opera, to me, because of the available extensions. I sounds to me like you won't be allowing those extensions, so I would use Opera or chrome, both of which are smaller than firefox.
ASKER
Yes, that is what I am thinking also, but there is a problem - while Chrome is the fastest browser, it also soaks up tremendous amount of memory.
Any way to get around that?
Any way to get around that?
Not that I am aware of. The other problem with Chrome is that it is in beta, which isn't always a good idea in a production environment.I'd probably stick with Opera, as the speed difference isn't that great, it is a more mature product, and has a smaller memory footprint.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah, I get your point.
I don't want to enable people use internet on the TS, but I need to, as some will only have a Thin Client in front of them.
Is there a specific GPO I could use to allow only specific sites?
I don't want to enable people use internet on the TS, but I need to, as some will only have a Thin Client in front of them.
Is there a specific GPO I could use to allow only specific sites?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow, great idea!
So, I do next:
let the people in the network with think clients use regular NAT internet, and set up a Reverse Terminal Server Machine based policy that will configure Thin Clients users' Explorer browser to point to this proxy server, where I define what can be accessed?
So, I do next:
let the people in the network with think clients use regular NAT internet, and set up a Reverse Terminal Server Machine based policy that will configure Thin Clients users' Explorer browser to point to this proxy server, where I define what can be accessed?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.