WMC Controller
Posted: Tue Nov 05, 2013 1:45 pm
This is a modified version of Vista Media Controller plugin viewtopic.php?f=9&t=911&hilit=vmccontroller. It adds some better reconnecting measures, as well as monitoring multiple extenders (MCX#) at once from the same host.
Basic running:
Hostname/IP Address of the computer with vmccontroller running.
List MCX# 0 for pc and 1,2,3,4,5,6,7,8,9 for the accounts of the extenders.
EventPrefix is what you want for the naming of each account being monitored.
Note: in List Mcx# and Event prefix list then with spaces between.
Ex. 0 1 2 4
WMC-PC DMALivingRoom EchoBedroom BasementTV
The Connect action is not needed if this plugin is running on the pc with the extenders setup with. This is all automated in this situation.
To use the Connect action for remote WMC status on extenders. You will need eventghost running on machine with the extenders attached. You need to setup the Network Event Sender plugin on this machine. Likewise you will then need the Network Event Receiver on the monitoring eventghost. Map whatever you like with the events related to SessionLogon MCX#
You will have to use eg.event.payload to know what mcx# just logged on.
Basic running:
Hostname/IP Address of the computer with vmccontroller running.
List MCX# 0 for pc and 1,2,3,4,5,6,7,8,9 for the accounts of the extenders.
EventPrefix is what you want for the naming of each account being monitored.
Note: in List Mcx# and Event prefix list then with spaces between.
Ex. 0 1 2 4
WMC-PC DMALivingRoom EchoBedroom BasementTV
The Connect action is not needed if this plugin is running on the pc with the extenders setup with. This is all automated in this situation.
To use the Connect action for remote WMC status on extenders. You will need eventghost running on machine with the extenders attached. You need to setup the Network Event Sender plugin on this machine. Likewise you will then need the Network Event Receiver on the monitoring eventghost. Map whatever you like with the events related to SessionLogon MCX#
You will have to use eg.event.payload to know what mcx# just logged on.