Microsoft and Quest are jointly promoting a solution which uses RDSH / Terminal Server + Quest vWorkspace to deliver IE6 as an application in a way which is compliant with Microsoft’s licencing regulation.
How significant an issue do you believe IE6 application compatibility is for Windows 7 deployments? I am getting varied feedback: some customers feel it’s not an issue as they understand the problem and have plans to correct the applications or migrate, while others feel that customers may not have realised how significant an issue it is for them and the fact that some of the solutions in the market are not supported by Msft.
Microsoft and Quest team up
Microsoft and Quest are jointly promoting a solution which uses RDSH / Terminal Server + Quest vWorkspace to deliver IE6 as an application in a way which is compliant with Microsoft’s licencing regulations – as for example VMware’s solution using ThinApp is not.
[For those in the UK there is a joint Microsoft/Quest breakfast briefing in London on 5th July.]
This joint solution
• Presents Internet Explorer 6 onto Windows 7 (or other devices that do not support Internet Explorer 6)
• Extends native Remote Desktop Services functionality in the areas of Connection Brokering, Load Balancing, Web Access, Single Sign-on
• Adds Application, Desktop or Content Presentation to Windows Server 2003 Terminal Services
• Enhances Microsoft RDP to deliver a rich end user experience to users over low bandwidth and high latency connections.
• Integrates with Active Directory, System Center Virtual Machine Manager and App-V
• Provides an easy to use management console for Remote Desktop Session Host, Terminal Server & Microsoft VDI
There is a reference architecture and deployment guide available.
- Download the Msft “Solutions for Virtualizing IE” whitepaper.
- General info on TS in Windows Server 2003
- Terminal Services Overview on TechNet.
- Quest AppCompat Datasheet
- Quest solution Deployment Guide