Publishing point name: PubPoint
If the publishing point path uses the HTTP or MSBD protocol to
point to an existing local station service and programs, the
upgrade process results in the following:
A new playlist file is created, using the name of the program,
and the playlist file is saved to a new directory
Each stream within the program becomes a media element
within the playlist, and all properties associated with the stream
become attributes of the media element.
References to MSBD in the source URL are replaced by HTTP.
If two programs exist for a single station:
A new playlist file is created for each program, using the name
of the program, and the playlist file is saved to a new directory
A broadcast publishing point is created for the station and the
path points to the playlist file that was created for the first
Two broadcast publishing points are created:
The version 4.1 station name becomes the name of the first
broadcast publishing point, which points to the playlist path. The
station properties are migrated to the publishing point.
The version 4.1 publishing point name becomes the name of the
second broadcast publishing point, which points to the first
The upgrade process only covers the migration of
Windows Media Services. Any remote servers and encoders must be
reconfigured manually to use the HTTP protocol.
If you were using a port other than 80 to stream
content from another server or an encoder, you will need to update
the URLs in the playlist to reference the appropriate port number.
For example if you streamed welcome.asf over port 8008 on your 4.1
server and your original URL was msbd://server1/welcome.asf the
upgrade process will result in the URL http://server1/welcome.asf.
However, that will not work if the content is not available on the
default HTTP port, so you must modify the reference to