Updated: October 4, 2007
Applies To: Windows Server 2008, Windows Server 2008 R2
There are many scenarios in which you can distribute content by using Windows Media Services. Some examples to consider are: live product demonstrations, interactive television shows and movies, real-time customer conferences, breaking news stories, broadband video stores, and interactive training presentations. After a piece of content is available over the Internet, the number of clients who can discover and request it is tremendous. When planning your deployment, you need to be aware of how your server will react in situations in which it is being inundated with requests for content. Keep the following in mind when assessing your deployment:
Scalability. Windows Media Services is scalable by design to support a range of deployments, from small Internet radio stations that have hundreds of connection requests to large–scale streaming media Web sites that generate millions of requests. You can administer both groups of servers and publishing points and single servers and publishing points.
Security. You may want to secure certain content on your Windows Media server to allow only specific clients to connect. Windows Media Services supports several authentication and authorization methods that allow you to control access to your content.
Stream quality. As more clients connect to your server, its available bandwidth can decrease. Additionally, the load on your server can overwhelm the processor's ability to serve the content. If you are streaming video content, investigate encoding using multiple-bit-rate (MBR) video so that the bandwidth can gracefully scale down and up as necessary.
This section provides an overview of common scenarios for streaming audio and video content from a server running Windows Media Services.