-
Posted to
IIS7 - Media
by
prakashd
on
10-09-2009, 11:42 AM
Do you have to change wmpub? The actual content is under wmpub\wmroot and wmroot folder is accessible to administrators
-
Posted to
IIS7 - Media
by
prakashd
on
10-09-2009, 11:38 AM
An easy alternative would be to use Active Script plugin and write a small plugin to authorize based on the referer header. This should be easy to get it up and running fast but may not be very efficient for a high traffic site (since you are running a script for each user request)
-
Posted to
IIS7 - Media
by
prakashd
on
09-28-2009, 7:42 PM
Are you using a playlist to play the file?
-
Posted to
IIS7 - Media
by
prakashd
on
09-28-2009, 7:21 PM
No. The MediaElement in WPF doesn't have the support for a Custom MediaStreamSource. (Which is what the sliverlight client implementation uses). So unless there is built in support in Windows for smooth streaming (which currently isn't) you can't use WPF
-
Posted to
IIS7 - Media
by
prakashd
on
09-28-2009, 7:14 PM
Are you trying to open the .nsc file in the browser? Can you share the .nsc file? What is the error you are seeing?
-
Posted to
IIS7 - Media
by
prakashd
on
07-24-2009, 7:25 PM
Is this x86 or amd64 build? I belive we know of an issue on amd64 that we should have a patch soon
-
Posted to
IIS7 - Media
by
prakashd
on
07-24-2009, 7:13 PM
I guess a cleaner way to avoid the above problem is to
Do a clean install of WMS on a server 2008 box (delete any old servernamespace.xml)
Stop the service and copy over the old servernamespace.xml
Run WMSSErverConfig.exe /repair
and start the wMS service
This way you should not see any problem with the counters.
-
Posted to
IIS7 - Media
by
prakashd
on
07-24-2009, 7:10 PM
Could you not use silverlight and use with SSPL from WMS ?
-
Posted to
IIS7 - Media
by
prakashd
on
07-24-2009, 7:08 PM
In the mean time you could follow the steps on http://support.microsoft.com/kb/934518 to download and install the Windows media services for Windows Server 2008
-
Posted to
IIS7 - Media
by
prakashd
on
07-24-2009, 7:07 PM
Did you check for the number of connected clients from the Cache Proxy publishing points (The two cache proxy publishing points under the Cache/Prxoy Management node)?