Show Menu

Implementing Windows 10 Player

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.

Installing Windows Player

To implement Windows Player for AEM Screens, please install Windows Player for AEM Screens.

Ad-Hoc method

The Ad-Hoc method to install the latest Windows Player ( .exe ), visit AEM 6.4 Player Downloads page.
Once you download the application, follow the steps on the player to complete the ad-hoc installation:
  1. Long-press on the top left corner to open the admin panel.
  2. Navigate to Configuration from the left action menu and enter the location (address) of the AEM instance you wish to connect to and click Save .
  3. Click on the Registration link from the left action menu to complete the device registation process.

Registering multiple Windows 10 Players with one Configuration

Once you have installed the Windows player, you can register multiple players with one configuration.
Bulk Registration of Windows Player
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. Install Windows Player.
  2. Find the configuration file under %appdata%\com.adobe.aem.screens.player\config.json .
  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
The URL to the Adobe Experience Manager (AEM) server.
The resolution of the device.
The schedule to reboot the player.
Enable the Admin UI to configure the device on site. Set to false once it is fully configured and in production.
Enable the channel switcher UI for users to switch channels on device. Consider setting to false once it is fully configured and in production.
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": "http://localhost:4502",
    "resolution": "auto",
    "rebootSchedule": "at 4:00 am",
    "enableAdminUI": false,
    "enableOSD": false,
    "enableActivityUI": false