Implementing Windows Player implementing-windows-player
This section describes configuring the Windows Player in AEM Screens. 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 installing-windows-player
To implement Windows Player for AEM Screens, install Windows Player for AEM Screens.
Visit the AEM 6.5 Player Downloads page.
Setting up Environment for AEM Screens 6.5.5 Service Pack fp-environment-setup
Set the SameSite attribute for the login-token cookies from Lax to None from Adobe Experience Manager Web Console
Configuration on all AEM author and publish instances.
Follow the steps below:
-
Navigate to Adobe Experience Manager Web Console
Configuration usinghttp://localhost:4502/system/console/configMgr. -
Search for Adobe Granite Token Authentication Handler.
-
Set the SameSite attribute for the login-token cookies from Lax to None.
-
Click Save.
Ad-Hoc method ad-hoc-method
The Ad-Hoc method lets you install the latest Windows Player (.exe). Visit the AEM 6.5 Player Downloads page.
After you download the application, follow the steps on the player to complete the ad-hoc installation:
- Long-press on the top-left corner to open the admin panel.
- Navigate to Configuration from the left action menu and enter the location (address) of the AEM instance you want to connect to and click Save.
- Navigate to the Device Registration link from the left action menu so you can check the status of the device registration process.
Naming Windows Player name-windows
You can assign a user-friendly device name to your Windows Player, thus sending the assigned device name to Adobe Experience Manager (AEM). This capability not only lets you name your Windows Player but also lets you easily assign appropriate content.
Follow the steps below to configure the name in Windows Player:
- Click start > run.
- Enter
system.cpl. - Use the computer name tab to set the computer’s hostname.
Changing the Default Options in Windows Installer changing-default-options
Follow this section so you can learn how to change the default options in Windows Installer and the list of available customizations.
Installation using CLI (PowerShell) install-powershell
- Create a custom location dedicated for Screens Player, for example:
C:\Users\User\screens-player - Install
aem-screens-player-electron-xxx-signed.exe /S /D=C:\Users\User\screens-player - Open
Start-Process C:\Users\User\screens-player\AEMScreensPlayer.exe
Example
C:\Users\User\Downloads> mkdir screens-player
C:\Users\User\Downloads> .\aem-screens-player-electron-xxx-signed.exe /S /D=C:\Users\User\Downloads\screens-player
C:\Users\User\Downloads> Start-Process C:\Users\User\Downloads\screens-player\AEMScreensPlayer.exe
Bulk Registration of Windows Player bulk-registration
When implementing the Windows Player, you need not manually configure every player. Instead, you can update the configuration JSON file after it is tested and is ready for deployment.
The configuration makes sure that all players ping the same server provided in the configuration file. Manually register each player.
Follow the steps below to configure the Windows 10 Player:
- Install Windows Player.
- Find the configuration file under %appdata%\com.adobe.aem.screens.player\config.json.
- Update the configuration JSON using the information below and then copy the same folder to all the systems where the player resides.
Policy Attributes policy-attributes
The following table summarizes the policy attributes with an example policy JSON for reference:
Example policy JSON file example-policy-json-file
{
"server": "https://localhost:4502",
"resolution": "auto",
"rebootSchedule": "at 4:00 am",
"enableAdminUI": false,
"enableOSD": false,
"enableActivityUI": false
}
Enabling Kiosk Mode enabling-kiosk-mode
When you are deploying the Windows Player, it is important to enable a Kiosk mode so that other applications or the taskbar do not appear on the Windows desktop.
Follow the steps below to enable Kiosk mode:
-
Enable Shell Launcher.
See Configure Shell Launcher in Shell Launcher page by Microsoft® Windows support for additional information.
-
Create a non-administrative user (if you already do not have one) to be used for Kiosk. It can be a local or domain user.
-
Install the Windows Player for that Kiosk user from the AEM Screens Player Downloads page.
-
See Use Shell Launcher to create a Windows 10 kiosk to modify your PowerShell script for more information.
Modify the PowerShell script so you can replace the username with the one you created. Ensure that the path to the application executable is correct. This sets the custom shell as the Windows Player application for the kiosk user and set the default as explorer.exe for other users.
-
Run the PowerShell script as an administrator.
-
Reboot and login as the Kiosk user and the player application should start right up.
Troubleshooting troubleshooting
If you get a black screen after you log in as the Kiosk user, it means that you may have incorrectly specified the path to the Windows Player executable. Log back in as the administrator and verify and rerun the script.
The default installation path for Windows Player is:
C:\Users<your user>\AppData\Local\Programs@aem-screensscreens-player-electron\AEM Screens Player.exe
The sample script in the links enables and disables the custom shell. Therefore, split the script into two and enable/disable the below applicable lines:
set-executionpolicy unrestricted - to remove restrictions temporarily.set-executionpolicy restricted - to re-enable restriction after running the script.# Remove the new custom shells.
$ShellLauncherClass.RemoveCustomShell($Admins_SID)
$ShellLauncherClass.RemoveCustomShell($Cashier_SID)
Using the Screens Remote Control using-remote-control
AEM Screens provides Remote Control functionality. Learn more about this feature here: Screens Remote Control