Site deployment

This is the overall order for setting up TreeT at a site. (The installers and detailed procedures are provided together with the deployment package supplied when you adopt TreeT.)

What to prepare (by role)

Prepare the following before installation. The default is to use a separate machine for each role, but depending on the size of the site you can combine them.

Role	Count	What to prepare
CMS server	1 per site (one CMS can run several sites)	Ubuntu 26.04 LTS. The installer installs Docker itself → Installing the CMS server
Kiosk	N per site (usually 10–30)	One of Windows, Linux, or Android. A display and a wired network connection. Minimum: Windows 10 or later (64-bit) · 64-bit Linux (x86-64 · Raspberry Pi confirmed on Pi 5 with a 64-bit OS) · Android 7.0 or later
Sync server	1 when using multi-screen	Windows 10 or later (64-bit) or 64-bit Linux (x86-64 · arm64). No separate runtime to install (a single executable)
Edge relay	1, closed-network sites only	Windows 11 22H2 or later, a machine connected to both the internal and external networks

Closed-network sites

At sites where the kiosks cannot connect directly to the external network (the CMS), you place one edge relay. Only this machine, connected to both the internal and external networks, talks to the outside, and the kiosks connect only to it. The edge uses only outbound connections, so you don’t need to open any inbound holes in the firewall.

Regular sites (where the kiosks can reach the CMS directly) do not need this machine.

Where to install the CMS server

Do not install the CMS in a cloud sync folder such as OneDrive, Dropbox, or Google Drive. The configuration files and database would be synchronized, which can cause conflicts or file locks. Use a fixed local path — gather the package you received in C:\treet, and install the CMS itself by moving the installation package inside it into a Hyper-V virtual machine (Ubuntu) (see Installing the CMS server).

Ports to open

This is the table to use when configuring firewalls and routers. Note first that there are two directions — most traffic goes from the kiosk out to the server, but remote control is the one exception that comes in the other way.

Kiosk → server (outbound)

Port	What it’s for	Connects to	If blocked
8443	CMS secure connection — registration · settings · scheduling · content download	CMS (or MqttEdge)	The screen won’t switch to a new schedule
8080	CMS plaintext connection — sites not using https	CMS	Same as above
8883	MQTT (TLS) — remote commands · status reporting	CMS broker (or MqttEdge)	Remote control and immediate updates won’t work. Playback itself continues
53000 and up	Sync playback — one port per sync pool	SyncServer	Playback across multiple screens goes out of sync

⚠️ Sites running on https (8443) don’t open 8080 to the outside — because it’s a plaintext entrance. So kiosks outside the site (on a different network) should set both the CMS address and the content address to https://…:8443. If you change only the CMS address in the device settings, the content address follows along automatically — if the two used to share the same entrance, it changes even the port, becoming something like https://…:8443/data.

⚠️ Android 7.0 and below need TreeTview Android 2026.9.135 or later — this applies at sites where the CMS uses a Let’s Encrypt certificate (https 8443). Those devices don’t recognize Let’s Encrypt’s root certificate (ISRG Root X1), so they can’t trust the CMS and can’t connect (measured on a Galaxy Note4 · Android 6, 2026-09-22). From 2026.9.135 on, the app carries that root certificate itself, so it connects. Devices with an older version installed can’t reach the CMS, so they can’t be updated through the CMS — you must install the new version directly.

⚠️ The 53000 range only travels within the site — it never goes out to the internet, so there’s no need to open anything on the router. Adding a pool increases the number by one each time (53001, 53002, …) — the CMS finds an open number for you.

Server → kiosk (inbound)

Port	What it’s for	If blocked
5900	VNC remote control — view and operate that screen directly	The remote control button won’t open

🔴 This is the only one that goes the other way. If you open every other port but miss this one, only remote control fails — and since everything else works fine, it’s hard to find the cause. If different devices use different ports, enter address[:port] in the Remote access field via Devices → Edit basic information at the top of the device page (Admin and above).

Ports used only on the admin side (unrelated to the kiosk)

Port	What
4822 · 8080	Guacamole internal communication
5500 · 5901	VNC repeater (server side / viewer side, in a closed-network setup)

🔵 The database port (3306) is never opened to the outside. It’s only used within the stack.

Sites using MqttEdge

When there’s an edge relay, kiosks connect only to the edge, not directly to the CMS. The edge opens 8883 (MQTT) and 8443 (content proxy) toward the site, and outward it has only one connection from the edge to the central server.

⭐ So even on a closed network, there’s no need to open an inbound hole in the router — because the edge only makes outbound connections.

Order of work

🔵 Follow this order. In particular, do not swap steps 2 and 3 — the CMS address is entered on the player screen, so the player must be installed first.

1. Install the CMS — set up the server on the CMS host and settle its access address (IP/domain + port). → Installing the CMS server
2. Install programs on the kiosks — install the player (+ the watchdog, and the sync server if needed). → “Installing on the kiosk PCs” below
3. Enter the CMS address — press F8 on the player screen. For the watchdog and sync server, enter it during installation (from the versions noted below), or later with a command or in a file. → “Entering the CMS address” · “Other programs need the CMS address too” below
4. 🔴 Check that it took effect — look with your own eyes at the [사이트설정] 확인 line in the player log. → “How to check that it took effect” below. If you skip this step, you won’t be able to find the cause later.
5. (HTTPS + IP address sites only) Register the server certificate as trusted — “Sites that use an IP address” below.
6. Register devices + schedule — once the address is correct, the player registers itself with the CMS (it also gets its device certificate automatically). In the CMS admin console, set up content and schedules. New program versions are received by every device together, according to the CMS’s update mode (automatic · manual) (admin console).

Installation and updates

Each program needs different permissions. You should know this in advance when planning the installation order.

Program	Installation permission	Installed to
TreeTview (player)	Regular user	That user’s personal folder
🔴 SyncServer (sync)	Administrator	Program folder (shared)
🔴 Watchdog (monitoring)	Administrator	Program folder (shared)
🔴 MqttEdge (closed-network relay)	Administrator	Shared folder

Why Watchdog needs administrator rights

It has to change machine-wide settings such as the screensaver and power saving. So during installation an administrator approval prompt appears — this is normal.

🔵 Only its configuration file is placed where operators can edit it (C:\ProgramData\TreeT\Watchdog). If it were in the administrator folder, every change to a value would need approval. ⚠️ C:\ProgramData is a hidden folder and does not show in File Explorer — type C:\ProgramData\TreeT\Watchdog into the address bar to open it.

🔵 SyncServer is also installed as administrator — it has to be running even before anyone logs in, so it starts under the system account at boot. Its configuration file is C:\Program Files\TreeT\SyncServer\SyncServer.json, so open Notepad as administrator to edit it.

The player is the only program installed as a regular user, and it is installed separately for each account — if several people use the same PC, you must log in with the relevant person’s account to install.

Updating = running the same installer again

There is no separate update file. Just run the new version’s installer and it overwrites the existing installation.

Settings and certificates are kept when you do this. You don’t need to re-enter the site settings because of a reinstall.

Updating from the viewer screen

Instead of running the installer directly, you can also check and install from the viewer screen. When the CMS has a new version to hand out to that device (program versions), do the following on site:

1. On the viewer, press F8 to open the settings screen.
2. Under 프로그램 업데이트 (Program update), press [확인] (Check) — the current version and status are shown.
3. If there is something to install, [지금 설치] (Install now) becomes available.

New versions install outside operating hours — to install now, press [지금 설치] (Install now)

Even when the CMS has a version to receive, the device does not install it right away. This keeps a playing screen from stopping without warning. It installs it by itself when the operating hours of that device’s screen group end; for a group with no time outside operating hours (24-hour operation, etc.), it installs within 60 minutes from the update time (default 03:00) in the CMS’s Settings › App updates.

To install now without waiting, press [지금 설치] (Install now). There are two places to press it:

Where	How
In the CMS (many devices at once)	Devices (기기관리) → select the devices → Commands for selected → Install now
On the device (one device)	F8 → 프로그램 업데이트 (Program update) → [확인] (Check) → [지금 설치] (Install now)

When installation starts, the viewer closes briefly and comes back up with the new version.

🔵 If you can wait, you don’t need to press it. When the time above comes, the device installs it on its own. In our measurements this takes about 90 seconds. ⚠️ If the CMS is set to manual updates, the new version must first be approved ([지금 업데이트] (Update now) in the CMS) — until then, pressing [지금 설치] (Install now) finds nothing to install.

⚠️ Don’t press it again after pressing it once. Once is enough — when installation finishes, the device comes back up by itself and reports the new version. Pressing again during installation does not make it faster.

The watchdog and sync server download and install updates by themselves

Unlike the player, for these two the watchdog asks the CMS and installs on their behalf. When you press [지금 설치] (Install now), it starts within 1 minute.

⚠️ PCs with a version lower than Watchdog 2026.9.43 are different — before that version it could not pick up the button press, so it waits up to 6 hours (the watchdog’s check interval). If it’s urgent, restart the watchdog on that PC (Task Scheduler → Watchdog → End, then Run, as administrator). It checks immediately on startup.

⚠️ If you just ran the installer by hand, that restart won’t work. The watchdog running at that point was launched directly by the installer, so Task Scheduler doesn’t manage it — even if End reports “success”, it keeps running. Restarting the PC clears this up.

Files from a different source are rejected

Downloaded installers are installed only after their signature and checksum are verified. If verification fails, the file is discarded and not installed — if an installation is rejected, first check where the file came from.

A blue warning screen appears during installation — this is normal

When you run the installer, Windows may show a blue screen titled “Windows의 PC 보호” (Windows protected your PC), or antivirus software may quarantine the file. The file is not damaged.

Windows trusts files that many people have installed, but this program is software installed only at specific sites, so that count never builds up. It may therefore appear again every time a new version is released.

To install: on the blue screen, click 추가 정보 (More info) → 실행 (Run anyway).

🔴 But check the following first — so that skipping past warnings doesn’t become a dangerous habit:

• That you got the file from the location we told you
• That file Properties → Digital Signatures tab shows Jiseoan TreeT

⚠️ If antivirus software deleted the file, tell your support contact — we will report the false positive to the antivirus vendor. Until then, it is safer to wait for the result of that report than to add an exception.

Updating Linux devices — there is no installer

Linux has no installer file like Windows’ .exe. The installation package is a single archive (.tar.gz), which also contains a list of checksums for every file, and a signature for that list. Receiving new versions from the CMS (outside operating hours · [지금 설치] (Install now)) works the same way as on Windows.

	Windows	Linux
What you get	Installer file (.exe)	Archive (.tar.gz) + a signed file list
How it installs	Runs the installer silently	Extracts to a new folder and swaps the folder in
What is verified	The file’s signature	The list’s signature + a checksum for every file
If it doesn’t come up	A person has to look at it	It rolls back to the old folder by itself

If the new version doesn’t come up, it rolls back by itself

After swapping in the new folder, the player checks whether the new version actually came up. While the screen is alive, the player updates a marker every 10 seconds — if that marker isn’t updated within 3 minutes, it rolls back to the old folder and brings the old version back up. The failed folder is kept with .failed appended to its name, so the cause can be checked later.

If even the rollback fails, it then logs “사람이 봐야 합니다” (a person needs to look at this) — if you see that line, someone on site has to start it by hand.

A power cut during an update is recovered automatically

If the power is cut at the very moment the folders are being swapped, the install folder can end up empty with only the previous version left. The watchdog detects this, moves the previous version back into place and starts the player again. The CMS then receives an error: “바꿔 끼우는 도중 끊긴 뷰어 설치를 직전 판으로 되살렸습니다” (an interrupted viewer install was restored to the previous version). A half-written folder is kept with a .failed suffix.

If neither the install folder nor the previous version exists, the watchdog posts “사람이 봐야 합니다” (a person needs to look) to the CMS once — in that case reinstall on site.

The Raspberry Pi (arm64) has its own separate file

Even though both run Linux, a regular PC (x86-64) and a Raspberry Pi (arm64) use different executables. They’re distinguished by file name — the one with -arm64 in its name is for the Raspberry Pi.

Device	File to get
Linux PC	TreeTview-linux-<version>.tar.gz · SyncServer-linux-<version>.tar.gz
Raspberry Pi	TreeTview-linux-arm64-<version>.tar.gz · SyncServer-linux-arm64-<version>.tar.gz

⚠️ Uploading the wrong file means it won’t come up on the device. Linux just says “not an executable format” (Exec format error) and stops there, so it’s hard to tell the cause just by looking at the screen. Double-check the file name when uploading it under Settings → App updates.

The sync server and watchdog update as administrator (root)

On Linux, these two are installed as systemd services, so the watchdog updates them with administrator rights too. It writes the new files alongside the old ones, then swaps them in all at once and restarts the service.

• On-site configuration files are not overwritten — values like the address stay as they are.
• When the watchdog updates itself, it exits on its own, and systemd brings it back up with the new files.

Installing on the kiosk PCs

Once the CMS is up, do this on every kiosk PC that will show a screen.

The installers are in the package’s 설치파일\ (installers) folder (C:\treet\설치파일\) — see “Before you start” in the CMS installation manual. 🔴 Move that whole folder to the kiosk PC and run it on that PC — the installers work relative to the folder they are in.

⚠️ Also take the package’s TreeT_코드서명_공개인증서.cer (TreeT code-signing public certificate) with you. If you don’t register it first, automatic updates will quietly fail (see “Installation and updates” above).

What to install

Order	Program	Required?
1	TreeTview — the player that shows the screen	✅ Required
2	Watchdog — restarts the player if it stops, and installs new versions on its behalf	✅ Recommended (effectively required for unattended sites)
3	SyncServer — only when several screens must change in step	Only sites that need it
4	🔴 UltraVNC — to view this device’s screen from the CMS	✅ Recommended

SyncServer only accepts screens once the CMS hands it a quota

Installing it isn’t enough on its own. How many screens can be kept in step together (the sync license) is decided by the CMS — within the license total it hands each sync server a quota, and the sync server accepts only that many screens.

Order — each step has to finish before the next one works:

1. That PC’s Watchdog must be paired with the CMS (approved once per PC — the sync server doesn’t make its own request; it shares that certificate).
2. In the CMS, on that PC’s device page → SyncServer tab, give this sync server a quota (number of concurrent screens) ([싱크 라이선스 몫 바꾸기] (Change sync license quota) — master account. Ask your support contact).
3. Once the sync server receives its quota, its log records 싱크 라이선스: 동시 클라이언트 N대 (sync license: N concurrent clients), and from then on it accepts screens (usually within about 10 seconds).

If you see this line	Meaning	What to do
[싱크 라이선스] CMS 에서 이 싱크서버에 배분된 싱크 라이선스가 0 입니다 — 기기관리에서 몫을 나눠 주세요 (the sync license allocated to this sync server in the CMS is 0 — hand out a quota in Devices)	It hasn’t received a quota yet — it accepts no screens at all	Do step 2
클라이언트 접속차단! (싱크 라이선스 N대 초과 — CMS 에서 몫을 늘리세요) (client blocked — over the N-screen sync license; raise the quota in the CMS)	More screens connected than the quota — only the screens over it are blocked	Raise the quota or reduce the number of screens
[싱크 라이선스] … 사이트 CA 가 없어 몫을 검증할 수 없습니다 (cannot verify the quota — no site CA)	It couldn’t find the certificate to check that the quota really came from the CMS — it accepts no screens	Update SyncServer to 2026.9.52 or later, and check that the PC’s Watchdog pairing (step 1) is done

🔵 The quota it receives is stored on that PC, so it keeps running for 7 days even if the CMS is briefly out of reach. 🔴 The unit is devices — a device with several screens (a 2-split layout, for example) counts as 1. 🔵 Sites that don’t use sync don’t need this at all — that’s why the table above says “only sites that need it.”

UltraVNC is not one of our programs

You must download and install it separately. Remote control on the CMS side is on as soon as it is installed, but the part that sends out the screen lives on this device — without it, pressing [Remote view] shows no screen.

• Port 5900 (leave the default)
• Set it to start automatically (install it as a service)
• No need to set a password — each time a button is pressed in the CMS, this device’s Watchdog sets a one-time password (from Watchdog 2026.9.153 · a Watchdog older than that version uses the site-wide password, so update Watchdog to a new version)
• Enter it in the CMS only when the address or port differs (Devices → device page → Edit basic information → the Remote access field: address[:port] — Admin and above)

Watchdog shows an administrator approval prompt

An approval prompt during installation is normal (see the table above). The other two don’t show one.

Do not clone a PC that has TreeT installed from a disk image

To prepare many PCs at once, do not take a disk image of a PC with TreeT already installed and write it onto other PCs. The device identity record and CMS registration are copied as well, and the moment it is switched on it can take over the original PC’s registration.

• Take the image before installing TreeT (Windows, drivers, up to UltraVNC), and install TreeT on each PC separately.
• If you have already cloned one, do not leave that PC running — remove TreeT and install it again. If the device page shows [신원] 같은 PC 의 Watchdog 정본 신원과 다릅니다 (differs from the Watchdog identity on the same PC), this may be the case.

Watchdog and SyncServer ask for the CMS address during installation

The setup wizard shows a CMS address field. Enter the CMS IP or name (e.g. 192.168.0.10).

• If you leave out the port, it becomes https://<address>:8443. At sites that run the CMS over http only, leave this field empty and, after installing, add --scheme=http to the command in “Other programs need the CMS address too” below.
• If you leave it empty, the default (127.0.0.1 — this PC itself) stays. That won’t reach the CMS, so fix it after installing.
• Reinstalling (updating) does not ask — this protects the address that is already set.
• 🔴 This address cannot be changed from the CMS screen. If it is wrong, the link to the CMS is lost — and with it the only way to fix it.

For unattended installs, pass it with /CMSURL=:

.\Watchdog_Setup_<version>.exe /VERYSILENT /CMSURL=192.168.0.10
.\SyncServer_Setup_<version>.exe /VERYSILENT /CMSURL=192.168.0.10

Only when you deliberately pass /CMSURL= does an update change the address.

Keeping the taskbar and notifications from coming up over the screen

When the player is full screen (kiosk), it sits above the taskbar. Even if a notification or another window briefly takes focus, the taskbar does not come up over the player. If you leave full screen with the shortcut (windowed mode), it goes back down like an ordinary window.

	Windows	Linux (Raspberry Pi)
While the player is full screen	The player covers the taskbar	The window manager (labwc) hides the taskbar by itself — the player does not turn the taskbar off
Notifications	The Watchdog keeps notifications off and turns them back off if they come on	—
Swiping in from a touch-screen edge	The kiosk setup (Settings_All.cmd) turns it off — it is a machine-wide setting, so the Watchdog only reports a mismatch	—
Right after power-on	—	The hardening run at install time removes the taskbar from autostart
In windowed mode	—	If cursor hiding is on, the player turns the taskbar off (fallback)

⚠️ The cursor is hidden only over the player window — it stays visible on screens the player does not cover (a second monitor, etc.) (same on Windows and Linux).

🔵 When the player is not on screen, the taskbar and cursor are visible — close the player (F4) or move it out of the way (F11) and the taskbar and cursor come back so you can use that PC right away; when the player returns, they go back to what the user chose (with F9 · F10 — if nothing was chosen, both hidden). Even if the player stops unexpectedly, the Watchdog restores the taskbar and cursor.

What to check after installing

When the player starts for the first time, it finds the CMS and registers itself. Nobody needs to register it by hand.

It has worked if the device appears in the Devices (기기관리) list in the CMS admin console.

If it doesn’t appear — it’s almost always “the address”

The setting for which CMS the player looks at is wrong. Do “Entering the CMS address” right below.

⚠️ The device is on and the screen is showing. Only the connection to the CMS fails, so from the outside it looks normal.

Running the installation check — check-install.ps1

The package (C:\treet) also includes a script that checks whether installation went correctly. It looks at things you can’t tell just from a picture appearing on the screen.

An installation can finish with “success” and still be wrong

Don’t stop when you see the “installation complete” window.

On the kiosk PC, open PowerShell and run these one line at a time.

Before installation — record the current values as a baseline (you need this to say “were the settings preserved?”):

powershell -ExecutionPolicy Bypass -File C:\treet\check-install.ps1 -Before

After installation — check the post-conditions:

powershell -ExecutionPolicy Bypass -File C:\treet\check-install.ps1 -After

-After runs even if you didn’t record -Before. However, it can only say “the values are like this now”; it can’t say what changed.

This tool doesn’t fix anything — it only reports

The goal is to keep a site record of what was checked. If it finds something, pass the message on to us exactly as shown.

Entering the CMS address — on the player screen (first time only)

Right after installation, the player holds the development default (127.0.0.1). You must enter the address once on that PC for it to find the CMS. This is the only time you do it by hand; after that, you change it from the CMS.

You do it with keyboard shortcuts — there’s no need to open a file.

Key	What it does
F8	Opens the settings screen ← enter the CMS address here
F11	Temporarily moves the screen out of the way (minimize)
F10	Full screen on/off — your choice is remembered (stays after a restart)
F9	Show/hide the mouse cursor and taskbar (on Linux including the Raspberry Pi taskbar) — your choice is remembered
F4	Quit the player

1. With the player running, press F8.
2. In the CMS 주소 (CMS address) field, enter the site’s CMS address — for example http://192.168.0.10:8080
3. 🔴 Also fill in the MQTT 사이트 (MQTT site) field — exactly the same as the site name you were asked for when installing the CMS (including upper/lower case). ⚠️ If you leave it empty, the screen shows but remote commands never arrive — the broker blocks them by topic permission, and no error appears at all.
4. In the MQTT 주소 (MQTT address) field, if the broker is on the same machine as the CMS, enter just the host part of the CMS address (e.g. 192.168.0.10).
5. When you save, the player finds the CMS at that address and registers itself.

Even when a Raspberry Pi or Linux machine has no Korean font, Korean · Japanese · Chinese on the settings screen and boot screen display correctly — the player ships its own fonts (the fonts add about 13 MB to the installer). Nothing is downloaded from the internet, so this works on closed networks too.

Shortcuts work even in full screen

Even when the kiosk is in full screen, F8 and F11 work. To move the screen out of the way briefly and do something else, press F11; to see it again, select the player window.

Editing the file directly is a last resort

Only if the settings screen (F8) won’t open, edit the single field path.baseUrl in that PC’s %APPDATA%\TreeTview\config\setting.json.

🔵 Leaving the other two empty is the correct answer — when path.dataUrl and mqtt.host are empty they follow path.baseUrl. Writing all three separately means that when the CMS address moves later you fix one and forget the rest; that actually happened, and the device never once connected to the broker.

When to fill it in	What
path.dataUrl	only when the file server is kept separate
mqtt.host	only for an edge broker on a closed network

🔴 You must edit it on that PC, as that user. When it was edited through a shared folder, another account, or a remote tool, there were real cases where the file changed but the player didn’t see it. So be sure to do the check below — the evidence is not that you edited it, but that the player read it that way.

How to check that it took effect (don’t skip this)

After restarting the player, open that PC’s

%APPDATA%\TreeTview\logs\main_<today's-date>.log

and look at the [사이트설정] (site settings) lines near the bottom.

Line you see	Meaning
[사이트설정] 확인 — CMS 주소·MQTT·CA 설정에 걸리는 것 없음.	✅ Passed (no problems with the CMS address, MQTT, or CA settings)
✗ CMS 주소가 아직 개발 기본값입니다 (http://127.0.0.1)	❌ path.baseUrl was not entered (the CMS address is still the development default)
✗ mqtt.host 가 아직 개발 기본값입니다 (127.0.0.1)	❌ A development default is still in mqtt.host. 🔵 The fix is not to enter a value but to empty it (then it follows baseUrl). Enter an address only for a closed-network edge broker
✗ mqtt.site 가 기본값 "site" 입니다	❌ The MQTT 사이트 (MQTT site) field is empty — remote commands won’t arrive
· 사이트 CA 가 아직 없습니다	Normal before the first registration (not an error; means there is no site CA yet)

🔴 A wrong address doesn’t look like “a failure”. The screen comes up fine in full screen, and Watchdog keeps restarting the player every few minutes. It looks like “it’s on, but the content just isn’t showing”. The log lines above are the only accurate signal.

Device certificates are not installed by hand

When the player first registers with the CMS, it creates its own key, gets a certificate issued, and stores it. There is nothing to prepare or copy — as long as the address is right, the rest happens automatically.

Don’t copy another PC’s certificate onto a device

The certificate’s private key is locked and tied to that machine. A copied one won’t open, and worse, it hides the real reason automatic issuance isn’t working — because the file is there, it looks normal on the surface, and nobody can find out why the device won’t connect to the CMS.

The only thing a person may need to install is the site CA at HTTPS sites (see “Sites that use an IP address” below).

Other programs need the CMS address too

Fixing the player alone is not enough. The programs installed alongside it each look at the CMS too.

Program	File to edit	Field to edit
Watchdog	C:\ProgramData\TreeT\Watchdog\watchdog.json	appCheck.cmsUrl
SyncServer (sites that use it only)	C:\Program Files\TreeT\SyncServer\SyncServer.json	cms.url
MqttEdge (closed-network sites only)	conf.d\site.conf in the installation folder	Central broker address

If the Watchdog address is wrong, updates stop “silently”

The player runs fine and the screen is normal. The only thing that fails is that new versions deployed from the CMS never get installed, so it’s discovered months later as “why is it still on the old version?”

How to fix it with a command — you can change just the address without opening the file. In an administrator PowerShell, one line at a time:

& "C:\Program Files\TreeT\Watchdog\Watchdog.exe" --configure 192.168.0.10
& "C:\Program Files\TreeT\SyncServer\SyncServer.exe" --configure 192.168.0.10

• An address alone becomes https://192.168.0.10:8443. At http sites add --scheme=http (http://192.168.0.10:8080).
• To only preview, add --dry-run — it says how many places would change and writes nothing.
• The original is kept next to it as .bak before changing.
• On older Watchdog versions this command stops with watchdog.json 을 못 찾았습니다 (file not found) — then fix it in Notepad as below.
• Either way, the program must be restarted to apply the change (table below). How to fix it in Notepad — open Notepad as administrator and change only the address in that file.

Right after installation, the Watchdog address points to this PC itself

The value the installer puts in is "cmsUrl": "https://127.0.0.1:8443". 127.0.0.1 is the kiosk itself, so there is no CMS there — change it to the site’s CMS address. 🔴 Do not add a path after the address (for example /treetweb) — the device won’t register.

The ports are already filled in in two fields — httpPort (plain entrance, default 8080) and httpsPort (secure entrance, default 8443). Change them only at sites where the CMS uses different ports. When connecting over https (for example https://192.168.0.10:8443), leave caFile empty — Watchdog fetches the site CA from the CMS once through httpPort, saves it, and writes its fingerprint to the log. Compare it once with the site CA fingerprint on the CMS settings screen.

watchdog.json is a list starting with [, and the address is in appCheck inside the very first { … } block. Change only that one line and leave the other values as they are — in particular, emptying signerThumbprints turns off automatic updates. Below is the entire file for a site whose CMS is at 192.168.0.10:8080.

[
  {
    "autoHide": true,
    "updateLock": {
      "file": "%APPDATA%\\TreeTview\\update.lock",
      "maxHoldMinutes": 10
    },
    "startupDelayMs": 30000,
    "appCheck": {
      "cmsUrl": "http://192.168.0.10:8080",
      "caFile": "",
      "httpPort": 8080,
      "httpsPort": 8443,
      "tokenFile": "%APPDATA%\\TreeTview\\data\\device-token.json",
      "intervalMs": 600000,
      "autoApply": true,
      "downloadDir": "%APPDATA%\\TreeTview\\data\\update",
      "signerThumbprints": [
        "1CAE827334F20023B720E10A3460FEA788F2DD8B"
      ],
      "nodeHeartbeatInterval": 60000
    }
  },
  {
    "processName": "TreeTview.exe",
    "execPath": "%LOCALAPPDATA%\\TreeT\\TreeTview\\TreeTview.exe",
    "execArgv": [],
    "heartbeatTimeout": 30000,
    "scheduledTask": "TreeTview"
  },
  {
    "processName": "SyncServer.exe",
    "execPath": "%ProgramFiles%\\TreeT\\SyncServer\\SyncServer.exe",
    "execArgv": [],
    "program": "SyncServer"
  },
  {
    "processName": "mosquitto.exe",
    "execPath": "C:\\ProgramData\\TreeT\\MqttEdge\\vendor\\win64\\mosquitto.exe",
    "execArgv": ["-c", "mosquitto.conf"],
    "workingDir": "C:\\ProgramData\\TreeT\\MqttEdge",
    "program": "MqttEdge",
    "logFile": "logs/mosquitto.log"
  }
]

• The \\ in paths is JSON syntax, so leave both backslashes as they are.
• On PCs without MqttEdge, Watchdog skips the mosquitto.exe block by itself — you don’t need to delete it.
• Save the file with UTF-8 encoding.

For SyncServer it’s one line in the cms block (there is no /treetweb here to begin with):

"cms": {
    "url": "http://192.168.0.10:8080",

After changing it, you must restart that program for the change to take effect.

Program	How to restart
Watchdog	Task Scheduler → the Watchdog task → End, then Run (as administrator)
SyncServer	Task Scheduler → the SyncServer task → same way. Or log off and log back on
TreeTview (viewer)	Task Scheduler → the TreeTview task → End, then Run. The watchdog also restarts it by itself within 10 seconds

Checking that it took effect — Watchdog writes the address to its own log when it starts:

C:\Program Files\TreeT\Watchdog\logs\server_<today's-date>.log

Line you see	Meaning
업데이트 확인 시작 (10분 주기, CMS http://192.168.0.10:8080)	✅ It is looking at that address (“update check started, every 10 minutes”; the interval depends on intervalMs)
업데이트 확인이 설정돼 있지 않습니다(watchdog.json 의 appCheck.cmsUrl)	❌ The field is empty (“update check is not configured”)

Checking in the CMS is more reliable — even if the address in the log is correct, the device won’t register if the path (/treetweb) is wrong. In Devices (기기관리), open a device on that PC: Watchdog · SyncServer should appear under Programs on this PC in its Device settings tab within 1–2 minutes, and if the last response is just now to 1 min ago, it worked (if they are not tied to the PC yet, they first appear in the PC 미확인 프로그램 line above the Devices list). If they don’t appear, check the address again first.

To restart with PowerShell (as administrator), one line at a time:

Stop-Process -Name Watchdog -Force

Start-ScheduledTask -TaskName Watchdog

Stop-Process -Name SyncServer -Force

Watchdog restarts SyncServer shortly — so it is normal for one line saying “SyncServer.exe 이(가) 죽어 있어 다시 띄웠습니다” (SyncServer.exe was down, so it was restarted) to appear on the dashboard right afterwards.

Register the player first

Watchdog borrows the device token the player received when it registered. If the player has not yet registered with the CMS, Watchdog’s log shows AUTH_TOKEN_REQUIRED — this doesn’t mean the address is wrong, it’s an ordering problem. Once the player is connected, it resolves itself.

Automatic startup

Installation registers the programs to start automatically when someone logs in to that PC. There’s nothing else you need to do.

For unattended sites, also check automatic login

The player starts after login. For it to recover by itself after a power outage, Windows automatic login must be turned on — this is an OS setting, so our installers don’t touch it.

Sites that use an IP address (HTTPS)

If the CMS address is a domain, you can use a public certificate and there’s no extra work. Sites that connect by IP address, on the other hand, use a certificate specific to that site, so the kiosks must be set up once to trust it.

Compare the fingerprint with your own eyes when registering

The channel the certificate is fetched through is not yet protected, so you must check for yourself that the fingerprint shown on screen matches the value on the CMS settings screen before accepting it. If you skip this comparison, the registration procedure loses its protection.

Registration is handled by a tool provided when you adopt TreeT; the on-site person only needs to compare the fingerprint.

Development defaults vs. site values

Note

Firewall/ports (the web access port, the real-time control and sync ports) and the license for multi-screen sync are checked additionally depending on the site setup. For detailed deployment consultation, contact TreeT staff.