IMDTouchKnowledge BaseShop main store

How-to

Getting RDP from a Comfort Panel to a Cabinet PC

HMI and touchscreens Published 6 min read

Short answer

A TP900 or TP2200 cannot remote into a cabinet PC as delivered, because the Siemens Windows CE image carries no RDP client. Add a third-party CE client — 2XClientCE.CAB is the one reported working on these panels — enable the remote desktop host on the PC, and prove touch input before removing the local monitor. Sm@rtServer serves the opposite direction and replaces none of it.

On this page
  1. Confirm the direction of the session
  2. Check the image, not the operating system
  3. Choose a CE client and get it from its vendor
  4. Prepare the PC as the host
  5. Install the client and open the first session
  6. Worked example: TP2200 on Windows CE 6.0 into a Windows Server 2008 R2 host
  7. Prove touch and persistence before dropping the monitor
  8. Questions asked

A Comfort Panel can run a cabinet PC over RDP, but not as it ships: the Siemens Windows CE image on the TP900 and TP2200 contains no RDP client, so the panel cannot start the session until you add one. The working path is a third-party Windows CE client — 2XClientCE.CAB is the package reported working on these exact panels — pointed at an industrial PC with its remote desktop host enabled and its account allowed to sign in. Sm@rtServer does not fill this gap, because it serves the opposite direction. Confirm the direction first, match the client to the image, prove the host and the touch input, and only then drop the local monitor from the station.

Confirm the direction of the session #

Half the confusion around remote desktop on these panels is direction. An RDP session has two ends: the client initiates the session and draws the remote screen; the host accepts it and runs the desktop. The operator must see and control the cabinet PC from the panel, so the panel is the client and the PC is the host.

Sm@rtServer runs the other way around. It is a licensed Comfort Panel option that turns the panel into the server, so a remote computer can view and operate the HMI runtime. Buying it adds no client to the panel and no host to the PC. The same direction rule is why Sm@rtServer rejects Sm@rtClient on a WinCC runtime PC when both halves land on one machine. If the real requirement is operating the HMI from an office computer, Sm@rtServer is the right purchase, and the TP2200 Comfort Sm@rtServer remote tab missing fix covers its common configuration fault.

Check the image, not the operating system #

Windows CE supports RDP as an operating system family. That says nothing about the image on the panel in front of you: the TP2200 runs Windows CE 6.0, and that factory image does not include a Microsoft remote desktop client. The installed image is the deciding evidence, so open the panel's control interface — the steps for entering configuration mode on a touch HMI get you there when the runtime is in the way — and list what is installed.

  • A client is already there: record its name and version, then test it against the PC before evaluating anything else.
  • No client: that is the factory condition on these panels, so the path forward is a third-party client matched to the image.

Choose a CE client and get it from its vendor #

The field-reported package is 2XClientCE.CAB, which fully operated a Windows machine from TP900 and TP2200 panels in one installation. Treat that as an existence proof, not a compatibility guarantee: a CAB built for a different CE version or processor architecture either will not install or will not run correctly. Before any install, match three things — the CE version on the panel (6.0 on the TP2200), the panel's processor architecture, and an installation route the image supports.

Get the package from the software vendor's own distribution channel and read its license terms before it touches a production HMI; a CAB found through a search engine carries no provenance you can defend. Also confirm the panel retains the installation across a restart, because a client that vanishes on power-up is not a station solution.

Prepare the PC as the host #

Enable the remote desktop host on the cabinet PC and allow the intended account to sign in remotely; an unconfigured host produces exactly the same blank screen as a missing client. Read the PC's name or address off the machine itself, not from memory.

Then prove the path with a control test: from a known-good RDP client on the same network, connect to the PC. If that client also fails, the fault is the host, the account, or the routing — fix it there before touching the HMI. Keep the host reachable only inside the control network and only for the accounts the station needs; an RDP service opened wider than that is a standing risk on a plant floor.

Install the client and open the first session #

Once the client matches the image and a test client reaches the PC, work in this order:

  1. Back up the HMI project and record the current image version and panel settings so the station can be restored.
  2. Install the client through the panel's supported deployment method, restarting only if the documentation calls for it.
  3. Enter the PC's address or name and the sign-in details in the client, storing credentials per site policy rather than embedding them in a shared screen.
  4. Launch the session and confirm the desktop shown belongs to the intended PC and account, not another machine.
  5. Exit the session the way an operator would and confirm the HMI runtime is still reachable.
  6. Power-cycle the panel once, then reopen the session to prove the installation and its configuration survived.

Worked example: TP2200 on Windows CE 6.0 into a Windows Server 2008 R2 host #

Inputs, each with its source: the panel is a TP2200 whose documented environment is Windows CE 6.0; the factory client count on that image is 0, because the Siemens CE image ships without an RDP client; the target is an industrial PC running Windows Server 2008 R2; the candidate package is 2XClientCE.CAB, reported working on TP900 and TP2200; the PC's remote desktop host is off until configured.

Rule in words: one usable RDP session needs exactly two halves pointing in the operator's direction — a client on the controlling screen and an enabled host on the controlled screen.

Arithmetic: required halves = 1 client + 1 host = 2. Present on delivery: panel client = 0, PC host = 1 once enabled, so 1. Missing = 2 - 1 = 1. Direction check: sessions needed = 1, panel to PC; directions Sm@rtServer can supply = PC to panel, so matches = 0 of 1.

Result: exactly one component to add — the CE client — plus host enablement on the PC, and zero help from Sm@rtServer.

Decision: a missing count above zero blocks the build, so at 1 missing, buy nothing from the HMI options list; source the client from its vendor, enable the host, and re-count to zero. At zero, run the touch test: pass, and the monitor comes off the station; fail, and the monitor stays until input mapping is fixed.

Prove touch and persistence before dropping the monitor #

The session must be operable, not merely visible, before the local monitor leaves the cabinet.

  • Touch: every tap lands on the intended control — test a dialog, a menu, and a text field, because a desktop that draws but mis-maps input is not a display replacement.
  • Keyboard: every entry the operator needs works through the panel's input method.
  • Reconnect: closing and reopening along the operating sequence leaves a working session or a clear sign-in path, and the PC still accepts the next one.
  • Persistence: after a restart, the client and its saved configuration are still on the panel.

Failures localize cleanly. The package will not install: image or architecture mismatch, so re-check the match. The client launches but never connects: host, address, or network path — rerun the control test. It connects but input fails: fix the client's input behavior while the monitor is still fitted.

Questions asked

Does Sm@rtServer let a Comfort Panel control a PC?

No. Sm@rtServer is a licensed option that runs on the panel and lets a remote computer view and operate the HMI runtime, so the session travels from the PC to the panel. The station needs the opposite direction: an RDP client on the panel and an enabled host on the PC. Sm@rtServer supplies neither half, so it cannot replace the client.

Do Unified Comfort Panels have the same gap?

No. HMI Unified Comfort Panels include remote access of their own: one Client Operate and one Client Monitor ship with the panel and can be extended by license, and a Smart Client app supports the Smart Server with supported versions tied to the main TIA version. The classic Comfort Panels on Windows CE are the line that ships without an RDP client.

Which port does the panel's RDP session use?

RDP reaches the host over TCP port 3389. When the panel and the cabinet PC sit on different subnets, that port must be permitted along the whole route. If a test client on the same network connects but the panel does not, recheck the address entered in the client before suspecting filtering.

Can the HMI runtime and the RDP session share the panel screen?

Plan on switching, not side by side. While the session is open the client takes the panel's screen, so the station design must give the operator a clear exit from the session back into the HMI runtime, normally through the client's own disconnect control. Commission that exit path before the local monitor leaves the cabinet.

What if the CAB installs but disappears after a restart?

That is an installation-persistence problem, not a network fault. Reinstall through the deployment method the panel's documentation supports, so the package lands where the image keeps applications across power cycles, then repeat the restart test. A client that cannot survive one restart has no place on a production station.

Keep reading

  • Selection guide

    Where WinCC Unified Runtime Can Run and Remote HMI Options

    The Unified runtime executes only on a PC, a Panel IPC, a Unified Comfort Panel or the MD-34 tablet; a browser or Sm@rtServer VNC client displays it and never replaces the host. With no PC in the cabinet, a Unified Comfort Panel is the host and the tablet browser is the client. If a safety function must travel with the operator, no Unified mobile panel exists and the design stays Comfort-based.

    HMI and touchscreens

  • Troubleshooting

    Why Sm@rtServer Rejects Sm@rtClient on a WinCC Runtime PC

    Sm@rtServer is a VNC server that listens on TCP 5900, so a refused Sm@rtClient session has one of three causes: no VNC password is set, loopback connections from 127.0.0.1 are filtered, or another VNC server such as TightVNC owns port 5900. Identify the listener with netstat -ano | findstr :5900 first, then set the password in Runtime settings and restart the runtime.

    HMI and touchscreens

  • How-to

    How to Fix Overlapping Graphics Hiding HMI Symbols

    Put the static background picture inside a frame container so it sits behind the process symbols, bring each symbol forward through the editor's object list, and leave the generated source alone. Assign z-values ten apart by role so new layers insert without renumbering. Stacking fixes visibility only; click handling and state-driven colors need their own runtime checks.

    HMI and touchscreens