Vaatate praegu abisisu järgmise versiooni jaoks::

This section describes about configuring AEM Screens Windows 10 player. It provides information of the configuration file and the options available and recommendations as to which settings to use for development and testing.

Registering multiple Windows 10 Players with one Configuration


When implementing the windows player you need not manually configure every single player. Instead, you can update the configuration JSON file after it is tested and is ready for deployment.

The configuration will make sure that all players ping the same server provided in the configuration file. You still must manually register each player.

Follow the steps below to configure the Windows 10 Player:

  1. Extract the zip file containing the windows player.

  2. Find the configuration file player-config.default.json under resources/app/www.

  3. Update the configuration JSON using the information below and then copy the same folder to all the systems where the player resides.

Policy Attributes

The following table summarizes the policy attributes with an example policy JSON for reference:

Policy Name Purpose
server The URL to the Adobe Experience Manager (AEM) server.
resolution The resolution of the device.
rebootSchedule The schedule to reboot the player.
enableAdminUI Enable the Admin UI to configure the device on site. Set to false once it is fully configured and in production.
enableOSD Enable the channel switcher UI for users to switch channels on device. Consider setting to false once it is fully configured and in production.
enableActivityUI Enable to show progress of activities such as download and sync. Enable for troubleshooting and disable once it is fully configured and in production.

Example policy JSON file

  "server": {
    "Value": "http://localhost:4502"
  "resolution": {
    "Value": "auto"
  "rebootSchedule": {
    "Value": "at 4:00am"
  "enableAdminUI": {
    "Value": false
  "enableOSD": {
    "Value": false
  "enableActivityUI": {
    "Value": false