webcast schedule todays event will run one-hour long. here are the expected times for each segment...
TRANSCRIPT
WEBCAST SCHEDULE
Today’s event will run one-hour long. Here are the expected times for each segment of the webcast:
:00 – :05: Moderator introduces the speaker and discusses the
details of the webcast.
:05- :35: Speaker delivers a PowerPoint presentation on the webcast topic.
:35- :60: Moderator and speaker engage in a Q&A on the topic.
TECHNICAL FAQsHere are answers to the most common technical problems users encounter during a webcast:
Q: Why can’t I hear the audio part of the webcast?A: Try increasing the volume on your computer.
Q: I just entered the webcast and do not see the slide that the speaker is referring to. What should I do?A: The slides are constantly being pushed to your screen. You should refresh (hit F5) to view the latest slide.
Q. I can’t view some of the detail on the slides. How do I enlarge the slides for a better view? A: Click the “Enlarge slide” link in the upper right corner of your presentation. This will open a new browser with a full view of the current slide.
You can also visit the Broadcast Help page for more information or to test your browser compatibility. Click here: http://help.yahoo.com/help/bcst/
If you still have technical questions or problems, send an e-mail to [email protected]. A technical support person will respond to you within 24 hours.
Copyright 2003 Christa Anderson
The Terminal Services Report Card
Where Terminal Services has been, where it’s going and how the changes affect the need for
third-party software
Agenda
What do you need a terminal server to do? Evolution of Terminal Services What’s new in Windows Server 2003? What’s still missing?
Click the “Ask a question” button in the lower left section of your screen to submit a question.
What do you need a terminal server to do?
Provide a rich client experience to users Map local resources to terminal sessions if
needed Provide users secure access to the server Simplify printer driver management Get applications to the terminal servers and
configure them appropriately Distribute client sessions across servers Distribute licenses to qualified users
Evolution of Terminal Services
Windows NT, Terminal Server Edition
Windows 2000 Server
TSE
Remote RDP sessions 256 color, no session-client interaction Difficult to manage per-user settings Almost required MetaFrame
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Windows 2000 Server
Session encryption and compression Improvements in bandwidth usage and resource
usage Client printer mapping Shared clipboard Remote control (session shadowing) Integration with core OS New license management utility Network load balancing (Advanced Server and
DataCenter only)
What’s new in WindowsServer 2003?
Client changes Server changes
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Client changes: B
Automatic client reconnect Concurrent connection limiting True color support Mapped drives Sound Improved full-screen mode More responsive sessions
Server changes: B-
Group policies managing server and user settings
New licensing scheme Control over license issue Server farms (Enterprise Server only)
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Server and user group policies
You can now configure Terminal Services using group policies
Per-computer settings control Configured policies control — otherwise,
normal configuration priorities are in effect Use loopback policies to make sure that
appropriate policies control when users log onto the terminal server
Licensing in WindowsServer 2003
Both per-seat and per-user TSCALs Unlimited External Connector license
replaces Internet Connector license Unlimited pool disabled
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Server farms
Not equivalent to MetaFrame server farms Allows users to connect to a single virtual
server Uses NLB or other load balancing to
ensure that user requests are spread out Reconnected sessions restored on
previous server
What’s still missing?
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Server-side wish list
Printer driver management Stress-based or application-based load
balancing Server zones
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Client-side wish list
Application publishing Seamless windows Automatic printer mapping for CE devices Bandwidth management for print jobs Built-in support for non-Win32 clients SSL support
What’s in MetaFrame XP?
3 versions of MetaFrame XP, all with different capabilities
Many features also included in feature releases
Remember that some MetaFrame features are available in the OS or in Microsoft add-ons
Are other options available?
Terminal Services has become so capable that it’s worth investigating other options for a la carte additions such as: Print driver management or elimination Non-Windows client support Application metering Etc., etc.
Summary
Windows Server 2003 doesn’t get an A yet — but neither does MetaFrame
Most of the important features of MetaFrame are for very large networks
You can use the core OS to duplicate some features in MetaFrame
Investigate single-function utilities to supplement native Terminal Services
Any questions?
Free newsletter signup at www.isinglassconsulting.com
Terminal Services forums at www.minasi.com
Click the “Ask a question” button in the lower left section of your screen to submit a question.
Feedback
Thank you for your participation.
Did you like this webcast topic? Would you like us to host other events similar to this one? Send us your feedback on this event and ideas for other topics at [email protected].