Enable Windows Media Service HTTP Server Control Protocol From Batch File
I have a server that keeps disabling the Windows Media Service HTTP Server Control Protocol when it reboots. I would like to make a batch file to check/enable this after reboot. But I cannot seem to find the correct command to do this from command line.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
simply a link to microsoft, not an answer
Fair enough. Out of curiosity, did you go to the Windows Media community forum and ask the question? (The team that staffs it are long-time Windows Media experts at Microsoft.) More importantly, did you find an answer to your question?
-Chris
-Chris
ASKER
currently have not found a viable answer for this. I have basically written a small windows service that can check and alert me if it is not up. but as for accessing it directly and enabling no.
You seemed reluctant to ask the Microsoft team, so I went ahead and asked them. Here is their reply:
"If something is turning off port 80 for Windows Media Services (WMS), then that same something should prevent a script from turning the port back on for WMS. I’m assuming from this description that this is a classic port conflict issue with something like IIS or another port 80 consumer." [Note that if a port conflict seems possible, this article on WMS port conflicts might be helpful: http://www.iis.net/learn/media/windows-media-services/using-http-for-streaming-and-downloading-from-the-same-computer.]
"Finding the underlying cause of this issue makes more sense than writing a script to fix this. But, if they’re dead set on writing a script, then here are the starting APIs: http://msdn.microsoft.com/en-us/library/windows/desktop/dd893168(v=vs.85).aspx."
I hope this helps...
-Chris
"If something is turning off port 80 for Windows Media Services (WMS), then that same something should prevent a script from turning the port back on for WMS. I’m assuming from this description that this is a classic port conflict issue with something like IIS or another port 80 consumer." [Note that if a port conflict seems possible, this article on WMS port conflicts might be helpful: http://www.iis.net/learn/media/windows-media-services/using-http-for-streaming-and-downloading-from-the-same-computer.]
"Finding the underlying cause of this issue makes more sense than writing a script to fix this. But, if they’re dead set on writing a script, then here are the starting APIs: http://msdn.microsoft.com/en-us/library/windows/desktop/dd893168(v=vs.85).aspx."
I hope this helps...
-Chris
ASKER
No answer given the only response was to go to microsoft