Presentation is loading. Please wait.

Presentation is loading. Please wait.

INF403 - Windows Server Code Named "Longhorn" Terminal Services: Introduction Alex Balcanquall Product Manager.

Similar presentations


Presentation on theme: "INF403 - Windows Server Code Named "Longhorn" Terminal Services: Introduction Alex Balcanquall Product Manager."— Presentation transcript:

1 INF403 - Windows Server Code Named "Longhorn" Terminal Services: Introduction Alex Balcanquall Product Manager

2 Agenda Why use Terminal Services What’s new in Longhorn Terminal Services TS Remote Programs TS Gateway TS Web Access The importance of x64 bit SoftGrid and Terminal Services ?

3 Advantages of Anywhere Application Access TS solution secures applications and data in the data center Data Security & Compliance TS solution reduces instances of server and application instances High IT Management Costs TS solution improves branch and WAN application access with less BW Reduce BW in branch & WAN TS solution provides simple and secure access for sharing apps and data with partners and remote users App & Data sharing TS solutions enables network access to legacy apps Connectivity to legacy apps Mobile Worker In Airport Branch Office Home Office Central Location

4 Terminal Services in Windows Server “Longhorn” Design Goals Improve basic out-of-box solution Provide improved platform for customers and partners Tighter integration with client OS to provide seamless experience Leverage and integrate with Microsoft management technology Solution Features TS Remote Programs (demo) TS Gateway (demo) TS Web Access (demo) Single Sign-on for managed clients Improved experience, security and manageability

5 Terminal Services Remote Programs Alex Balcanquall Product Manager Security Product Management

6 TS Remote Programs Deployment Best Practices Put common application on same server Office Family Consider putting individual applications on separate servers when: Application has compatibility issues A single application and associated users may fill server capacity Create load-balanced ‘farm’ for single applications that exceed 1 server

7 TS Web Access Alex Balcanquall Product Manager Security Product Management

8 TS Web Access Deployment Best Practices TS Web Access default is good for single server deployments Use Active Directory mode for multi-server deployments when customers are experienced in AD based software deployment When customer has no AD MSI experience use custom ASP scripting solutions or 3rd party solutions

9 Terminal Services Gateway Remote Access to internal applications resources DMZ HTTPS / 443 Internet Corp LAN Terminal Server Hotel External Firewall Internal Firewall Home Business Partner/ Client Site Other RDP Hosts Terminal Server Internet Terminal Services Gateway Server Tunnels RDP over RPC/HTTPS Passes RDP/SSL traffic to TS Strips off RPC/HTTPS Network Policy Server Active Directory DC

10 Terminal Services Gateway Alex Balcanquall Product Manager Security Product Management

11 TS Gateway Best Practices Use root-signed SSL certificate Don’t rely on TS Gateway to block devices Use a dedicated TS Gateway Server Consider placing behind ISA Use SSL terminator in DMZ and put TS Gateway in main network When should TS Gateway be used in place of VPN? When no local copy of data is required \When bandwidth or application data size makes VPN experiences suck

12 What else is new in LH TS? Resolution up to 4096x2048 & span multiple monitors PnP Device Redirection Framework Windows Presentation Foundation (WPF) 32-bit Color & new RDP compression Display Data Prioritization Experience NAP Integration Network Authentication Single Sign-on for domain joined clients Ability to block pre RDP6 client Per session & direct attached device isolation Security Display Data Prioritization Spooler scalability improvements Debug Logging available in all builds Full IPv6 Support Single Unified Win32 & Active X Client – serviced via Windows Update Manageability Investments in Windows and TS to eliminate potential attack vectors Faster Login & Logoff Profile corruption scenarios addressed Leverage UAP (LUA) for improved application compatibility Platform

13 Preparing for Windows Server “Longhorn” Terminal Services Understand you applications and current scalability limitations Re-evaluate hardware purchasing choices 4 to 8 cores are compelling price / performance for TS Ensure hardware has potential for memory and CPU upgrades you might need Can use 32-bit Windows until moving to x64 is possible Start deprecating 16-bit applications Test application compatibility on Beta 2 release

14 Citrix and Microsoft Citrix is a 2 time Gold Certified ISV Partner ( 2003 & 2005) Winner of Office Systems Desktop Deployment Technology of the Year (2006) Citrix Presentation Server Value-Add to TS & Microsoft Extends TS functionality Citrix MoM pack available Signed 5 year Joint Technology Agreement in 2004 “Constellation Technologies” will add new value in the Windows Server “Longhorn” timeframe

15 Citrix Presentation Server on Longhorn Server End user acceptance through high performance systems with proactive performance alerting Preferential responsiveness for important users Secure systems with automatic failure avoidance Simpler system provisioning and control for quick time to market Providing Service Level Assurance through autonomic, reconfigurable and high performance system built for Longhorn

16 Connectivity  Access Policies  Integration with Citrix Access Gateway (Advanced Access Control option)  System Monitoring and Reporting  Advanced Print Management  Enhanced Management Experience  Extended Shadowing Support  Application Availability Control  Automatic Client Updates  Unified Licensing  Simplified Application Installation  Integration with Network Management Consoles  More…. Citrix Presentation Server 4.0 Value-Add to Windows Server 2003 Scalability End-User Experience ManageabilityApplication Support  Application Isolation Environment  Virtual IP Address Support  Support for local TWAIN devices  Support for ActiveSync\  more…… Security  SpeedScreen TM 3  Application Publishing  Content Publishing  Content Redirection  Seamless Windows  Desktop Integration  SmoothRoaming TM  Simplified Printing  Built-in Group Conferencing  Pass-through authentication  Integration with Citrix Password Manager (single sign-on)  More……  Enterprise Load Balancing  CPU Utilization Management  Virtual Memory Optimization  Multiple Farm Support  Supported and tested on 1000+ server farms  More……  Two-Factor Authentication Support  Enhanced SmartCard Support  Secure Gateway  Access Policies  Integration with Citrix Access Gateway (SSL VPN)  More…..  Web Interface for Remote Access  Universal Device Access  DOS and Windows  Windows CE / PocketPC  Macintosh  Java  IBM OS/2 Warp  EPOC / Symbian OS  UNIX platforms  Support for Unix Applications  Support for Direct Dial-Up  Extended Network Support  More…

17 Benefits of x64 Architecture Can act like an x86 processor when an x64 system is booted into a 32-bit operating system and as such runs all 32-bit versions of Windows commercially available today Runs 32-bit software without being recompiled Runs 32-bit apps at high performance 4 GB User VA for Large Memory Aware Processes Eases Migration to 64-bit infrastructure X64 ideal for current deployments that are kernel VA limited x64 provides opportunities to increase user density with new multi-core processors 32-Bit Device Drivers Printer Drivers Software Kernel Driver Components Dongles Hardware Specific Drivers Subsystems NTVDM / Command.com (DOS) CMD processor still present 16-bit WOW Portable Operating System Interface for UNIX (POSIX) Legacy Transport Protocols Apple Talk, Services for Macintosh DLC LAN, NetBEUI IrDA, OSPF Features Not Supported in x64

18 Why is x64 so Important for TS? Up to 4x improvement in on comparable hardware Expected sweet spot for TS moves to 4 cores or more If driver compatibility is an issue consolidate onto Windows Server 2003 x86 SP1 with 2 to 4 cores x64 needs more resources for same workload set Performance is entirely dependent on scenario Whitepaper @ http://www.microsoft.com/ts http://www.microsoft.com/ts Knowledge Worker X86 & x64 TS User Capacity Scaling 2003 x64 4cores 2003 x64 8 cores Windows Server 2000 32 Bit Baseline 2003 x86 4 cores 2000 x86 4 cores ~ x2 ~ x4 ~ x6 Based on Initial Internal Testing x86 & x64 Performance Tip: Registry Setting to Reduce Microsoft® Outlook® 2003 Periodic Polling: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\RPC [dword] ConnManagerPoll = 0x600 [dword] ConnManagerPoll = 0x600

19 SoftGrid for Terminal Services Benefits Improve application compatibility Reduce application regression testing Eliminate silos – enable server consolidation Uses same infrastructure as SoftGrid for desktops. Requirements SoftGrid CAL for TS for every user / device connect to TS managed with SoftGrid Not part of Microsoft Desktop Optimization Pack. Availability Currently available from SoftGrid channel Available in MS channels from 01/01/07

20 Applications are virtualized per instance: Files (incl System Files) RegistryFonts.ini COM/DCOM objects Services Name Spaces Semafores, Mutexes Applications do not get installed or alter the operating system Yet tasks process locally on the terminal server. Microsoft SoftGrid Application Virtualization

21 Terminal Services Partners http://www.microsoft.com/windowsserver2003/partners/termsrvs.mspx

22 Summary Centralized application access using TS is about more than just remote access New Longhorn TS features enable new native TS scenarios TS Remote Programs and TS Gateway provide a complete solution for low complexity scenarios Expect 3rd party value to still be required for many scenarios in Windows Server “Longhorn” and beyond Consolidation using x64 on Windows Server 2003 gives significant current benefit Terminal Services is a Rich Client Technology Terminal Services can reduce application deployment and management overhead TS isn’t just about WAN links

23 Resources IT Forum: TS Longhorn Q&A – INFCT08, Room 130, 10:45am Today TS Longhorn HOL - INFHOL04 LH TS Information and Webcast : http://www.microsoft.com/windowsserver/longhorn/terminal-services/default.mspx TechNet online TS LAB: http://go.microsoft.com/?linkid=5496773 TS Blog: http://blogs.msdn.com/ts http://blogs.msdn.com/ts TS Main Page: http://ww.microsoft.com/ts http://ww.microsoft.com/ts TS LH Web Forum: http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=580&SiteID=17 http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=580&SiteID=17 TS x64 Scalability Whitepaper: http://www.microsoft.com/downloads/details.aspx?familyid=9B1A8518-D693-4BBB- 9AF8-B91BBC0D2D55&displaylang=en http://www.microsoft.com/downloads/details.aspx?familyid=9B1A8518-D693-4BBB- 9AF8-B91BBC0D2D55&displaylang=en Application Compatibility Toolkit: http://www.microsoft.com/technet/prodtechnol/windows/appcompatibility/default.mspx http://www.microsoft.com/technet/prodtechnol/windows/appcompatibility/default.mspx

24

25

26 ©2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.


Download ppt "INF403 - Windows Server Code Named "Longhorn" Terminal Services: Introduction Alex Balcanquall Product Manager."

Similar presentations


Ads by Google