Skip to main content

About our Windows Client

Supported device line-up​

Select the perfect device to make your content stand out!
Here's a quick overview of the device models we typically recommend and are well-acquainted with:

Manufacturer / Model seriesPlatform / FWChromium version
Giada (Windows devices)Windows 10, or 11 Enterprise OS installed with English language110

Currently supported device line-up​

Here's a quick overview of the device models we typically support and are acquainted with:

Manufacturer / Model seriesPlatform / FWChromium version
AOPEN DEX5750Windows 10 / 11 Enterprise or Professional OS installed with English language110
AOPEN DE3650-CWindows 10 / 11 Enterprise or Professional OS installed with English language110
SenecaWindows 10 Enterprise or Professional OS installed with English language110

System Requirements​

OS License Requirements​

According to the table above, we recommend Windows 10, or 11 Enterprise OS since KIOSK mode lock requires an Enterprise license.

We support devices with Professional OS license as well.

Please note

Windows Home licenses are not supported for our devices

Minimum System Requirements​

Wallboard Windows signage player application can run either on Windows mini box or desktop PCs.

  • Dual core CPU with iGPU
  • 2 GB RAM
  • 20 GB free disk space
  • 10/100 Mbit network connection
  • Windows 10, or 11 OS (Enterprise for Kiosk mode)
  • .NET Framework 4.6.2
  • Administrator rights to run the application

These players are usually good enough for displaying basic contents on single/dual screen (FHD) setups.

Please note

A desktop PC is much more customizable for your needs, and are recommended for multiscreen setups and 4K contents.

  • Mobile (undervolted) dual or quad core CPU
  • 4 GB of RAM
  • eMMC or SSD storage
  • Quad core standard voltage CPU
  • Integrated or dedicated GPU
  • 8 GB of DDR4 RAM
  • HDD or SSD storage
Please note

SSD storage is always recommended to achieve faster boot time and better playback performance.

How does Our Windows Client work?​

Our Windows client displays content on Windows 10 and 11 OS devices. Older versions of Windows will not be compatible with our client due to compatibility and security issues.
The Windows client is compatible with any device that is operating on Windows 10, or 11.
In our Windows application, we provide and update the browser version. The current latest version of the browser is Chromium version 110.

We recommend using Windows 10, or 11 Enterprise if the device will only run Wallboard and will never be closed. On Windows 10 and 11 Enterprise, the device can run in Kiosk mode which is the most optimized way to use our application.

info

For more information about Kiosk mode visit the following article: Kiosk mode

The application is a full screen HTML browser that also allows other functionalities:

  • Controls the device and the performance of the client application
  • Communicates with content inside the Wallboard CMS
  • Maintains the system

Window modes​

windowed.png

You can display our windows client in windowed mode which will display the application in a section of your screen.

You can make it Movable.

Content Caching On Windows​

Our client application stores all components of a piece of content on the device storage and supplies the embedded browser locally. This allows the device to load in the content without an internet connection.

The cache also reduces the network traffic significantly because media files are downloaded to the device only once, and when you display content that includes these media, the device will initially load them in from the local storage.

FAQ​

Why do I need English language OS specifically?​

We specifically recommend setting up Windows in English because the system logs are recorded in the OS language.
This means that if we receive logs from a device set to other languages, any error messages will appear in that language.

Why does Windows client require Administrator rights?​

The application needs Administrator privileges for the following reasons to ensure all features work correctly:

Time management

  • Changing time zone
  • Changing system time
  • Start/stop windows time service based on configuration

Lock default mode

  • Eliminating explorer.exe process
  • Disabling tablet mode if applicable

Lock KIOSK mode

  • Create a dedicated local admin user
  • Setting up Shell Launcher v1

Auto updater

  • Creating a scheduled task with highest privileges
  • Running the installer with administrator rights

Working hours

  • Running powershell script to check whether Wake Timers are supported and enabled
  • Creating a scheduled task with highest privileges
  • Running powershell scripts to execute power state change (sleep/wake up)

Other

  • Increasing Wallboard process priority

Windows client got flagged as a malicious software, what to do?​

Before delving into the details, it is worth emphasizing that **Wallboard's actions are never intended to be malicious **.

Here's a short list what may have triggered the monitoring tool:

  • Wallboard.exe created the scheduled task Wallboard Update: This task is solely for updating our application. We also utilize scheduled tasks for functions like Working Hours, which helps manage device sleep and wake-up times.
  • Wallboard.exe performed discovery indicative of virtualization/sandbox evasion: These "discoveries" are intended to gather device information, such as BIOS version and unique hardware IDs, for metrics purposes.
  • TabletMode-disable.exe file is an essential part of our system. It's required for the device's lock function, which disables the tablet's UI to prevent any tampering.
  • A powershell command executed by Wallboard.exe "powershell.exe" -WindowStyle hidden Remove-Item C:\Users\User\AppData\Local\Temp\WallboardUpdate.exe that is part of our update process. Its purpose is to manage the update files by downloading them and then clearing them once the update is complete or if a newer update becomes available.
caution

Additionally, please note that kflash.exe is not essential for the client app; and after version 4.0.356 it is no longer bundled with the application.

If you installed the application before version 4.0.356 the exe is still there, but you may remove it freely.

Last updated on