Your network contains a server named Server1 that has the Streaming Media Services server role
installed. Server1 has the WMS Http Server Control Protocol plug-in and the WMS Server RTSP
Control Protocol plug-in enabled. All client computers run Windows 7. The corporate website
contains links to on-demand media content that is hosted on Server1. You install the Web Server
(IIS) server role on Server1 by using the default settings. You change the port of the WMS HTTP
Server Control Protocol plug-in to 1450. Users report that the links on the corporate website no
longer work. You need to ensure that the users can access the on-demand media content by clicking
the links on the corporate website. What should you do? (Each correct answer presents a complete
solution. Choose three.)

A.
On Server1, bind the HTTP protocol of the Default Web Site to port 1450.

B.
On Server1, disable the Default Web Site

C.
On the corporate website, change the URLs of the links to use rtsp://server1.

D.
On the corporate website, change the URLs of the links to use mms://server1.

E.
On Server1, disable the WMS Server RTSP Control Protocol plug-in.

F.
On the corporate website, change the URLs of the links to use http://server1:1450.

Explanation:

Windows Media Services tries to use port 80 by default, but Web servers frequently reserve that
port. To avoid port conflict, use a port other than 80 for HTTP streaming. If you do not use the
default port, the URL that a player uses to connect to the publishing point must include the new port
number. For example, if you change the HTTP port to port 1450, the connection URL would be
http://server:1450/publishing_point. http://technet.microsoft.com/en-us/library/cc754336.aspx
—–
About Protocol Rollover
If clients that support RTSP connect to a Windows Media server using an RTSP URL moniker (for
example, rtsp://) or an MMS URL moniker (for example, mms://), the server uses protocol rollover to
stream the content to the client to provide an optimal streaming experience. Automatic protocol
rollover from RTSP/MMS to RTSP with UDP-based or TCP-based transports (RTSPU or RTSPT), or
even HTTP (if the WMS HTTP Server Control Protocol plug-in is enabled) may occur as the server
tries to negotiate the best protocol and provide an optimal streaming experience for the client.
Earlier versions of Windows Media Player, such as Windows Media Player for Windows XP, do not
support the RTSP protocol. When these players attempt to connect to a Windows Media server
using an MMS URL moniker, automatic protocol rollover from MMS to HTTP occurs, if the WMS
HTTP Server Control Protocol plug-in is enabled on the server.
To make sure that your content is available to all clients that connect to your server, ports on your
firewall must be opened for all of the connection protocols that might be used during protocol
rollover. For more information, see Allocating Ports for Windows Media Services.
You can force your Windows Media server to use a specific protocol by identifying the protocol to be
used in the announcement file (for example, rtspu:// server/publishing_point/file). However, to
provide an optimal streaming experience for all client versions, we recommend that the URL use the
general MMS protocol. If clients connect to your stream using a URL with an MMS URL moniker, any
necessary protocol rollover occurs automatically. Be aware that users can disable streaming
protocols in the property settings of Windows Media Player. If a user disables a protocol, it is
skipped during rollover. For example, if HTTP is disabled, then URLs will not roll over to HTTP. For
more information, see Windows Media protocol reference.
http://technet.microsoft.com/en-US/library/ee126137(v=ws.10).aspx