Reboot Players Immediately and Weekly 11.00.06

1. Reboot Players Immediately

When players stop playbacks, try to restart the players remotely.

1. Open ContentManger and go to Network> Maintenance jobs> +New

1. Select Player type (Scala Player or Android Player), and give the job a name and brief description, then click Create.

1. Select the Player(s) you want to run this job (If you selected Scala Player in Step 2, it will be only PC Players), and then click Add & Close

1. Go to Tasks> Add> Reboot> Add

1. Go to Scheduling>Add. Select ASAP then click Add>Save & Close.

1. Go to Network>Players. Tick the players you would like to reboot. Click Generate Plan

1. Wait for a while, Go to Network>Maintenance Check the status (Success).

2. Reboot Players Weekly or Once a day.

Restart Scala Players at least once a week or once a day. Doing this is a good way to clear out their memory and ensure that any errant processes and services that started running get shut down. Restarting can fix mysterious performance problems when the exact cause is hard to pinpoint. The more things you have open and the longer you keep them running, the greater the chances Scala Players will become slow and eventually run low on memory.

Here is how to set your Player up to reboot on a weekly basis.

1. Open ContentManger and go to Network> Maintenance jobs> +New

1. Select Player type (Scala Player or Android Player), and give the job a name and brief description, then click Create.

1. Select the Player(s) you want to run this job (If you selected Scala Player in Step 2, it will be only PC Players), and then click Add & Close

1. Go to Tasks> Add> Reboot> Add

1. Go to Scheduling> Add. Select Weekly or Daily, a week day and appropriate time, then click Add.

1. Go to Network>Players. Tick the players. Click Generate Plan

1. Wait for a while, Go to Network>Maintenance Check the status (Success).