Tuesday, June 12, 2007 12:10 PM
How is this product positioned in Microsoft's remote/application sharing software stack?
I saw this asked before, but it is still not clear.
MS has several products, and I will give a bit of what I understood, please correct me:
1. Microsoft Netmeeting - is dead it will be replaced by Vista's Meeting Space. This is the enterprise application sharing platform.
2. Remote assistance - will continue to be a part of the Windows OS stack as a remote help/control platform
3. Terminal Services remote control - will continue to be the way to control an RDP session in Terminal Services.
4. SharedView - intended for internet audience. Will be a part of the Windows Live software stack. Not for enterprises.
Tuesday, June 12, 2007 6:17 PM
You are correct that NetMeeting is no longer shipping (but still supported in XP through the XP life cycle). In Vista, Meeting Space can be used as a replacement for app sharing, file transfer, and simple messaging, and it has similar "inside the firewall" limitations, requiring IT department involvement to enable internet scenarios (Teredo/IPv6 enabling).
Remote Assistance and Term Svcs Remote Control are similar (same protocol is used), although the user experience is different. Firewalls can be configured to allow port 3389 traffic for internet use, but IT departments are often reluctant to do this. Remote assistance is really a different scenario than collaboration, and the clients are designed as such.
SharedView works both inside the firewall and across the internet, and is also a good solution for enterprises for ad hoc collaboration, as it will get through firewalls using HTTP if necessary. SharedView actually requires internet access as all traffic goes through the SharedView service. SharedView is not a Windows Live application from a branding perspective though - it's available for download at ideas.live.com as that site is Microsoft's central beta location.
Hope this helps - let me know if you have further questions.