I just went through 27 players via the WebUI and changed the "Content Check Frequency" on each one. This is going to become an issue when the network soon expands to over 200 units split between different groups.
Am I missing something or is there a way to change properties on multiple players en masse? Thanks.
I'd like to join you, by requesting BSN features such as:
Changing players' settings from the BSN group object.
Settings applied directly on a player, would over-ride settings inherited from the group.
Ditto
Assuming you are running your own BSNEE, you could edit the DB server directly and change the values. Next time the players check in they would pull that config. I admit I have not tried that yet. But anything you can change via the WebUI should be changeable by editing files and/or DB within the BSNEE.
Hi Allen,
I was also going to suggest adding groups nesting.
What is your take on that idea?
UD|_Sheme5h,
I am not sure what you mean. What functionality are you thinking about? Isn't that potentially covered by tagging?
That's an idea. Being able to select by player tags and properties, then change their properties based on that selection.
Louis,
So far I have not found a big need to change properties. I don't mean to snoop, but what would you change often?
We prefer to run DHCP. And we generally have no access to the customer networks where all of the players sit (although sometimes we have a tunnel in). So we don't need to mess with IPs. We generally set things and leave the players be after that.
The thought is to have a main group for the entire organization, with child group for branches.
Kind of like the way we use Stratacache for regional/geographic content. I am not a content management guy but I had thought tagging and Dynamic playlist would cover this.
Content-wise it may, but what if you want to limit the download data throughput on dozens or hundreds of players?
>So far I have not found a big need to change properties. I don't mean to snoop, but what would you change often?
Often? Would you want to be the one who has to change one property on 723 players just once? Not I. At 20 seconds per unit, that's 4 hours, not counting if you decide to make a checking pass.
"Content-wise it may, but what if you want to limit the download data throughput on dozens or hundreds of players?"
You are 100% correct and that is a perfect example that we just had an internal discussion about so I should have thought of it.
Good information. Thanks to both of you.
Seeing as how this has become a thread on feature wish-list...
The ability to see a graphed history of a players connectivity...again something that can be farmed from the DB and logs but that requires developement.
I send the uptime value as hearbeat to loggly.com in some projects. Their graphing feature makes it easy to spot irregularities.
It does require some coding, but it allows more control, and reduces the frustration from "shooting in the dark" type of experience :)