Installing WinCC V12 WebNavigator: Thin Client Trial Setup
SIMATIC WinCC V12 (TIA Portal) bundles the WebNavigator option inside the WinCC Runtime Professional installer. To evaluate thin-client operator access, you do not need a separate media purchase: the WebNavigator components ship on the same product DVD and are activated through the user-defined installation dialog. A 30-day demo license is generated automatically on first launch, which is sufficient for engineering acceptance tests, customer demos, and SCADA evaluation projects.
This guide covers the full trial workflow: preparing the engineering PC, selecting the correct installation options, deploying the WebNavigator Client, configuring a Microsoft Terminal Server for thin-client access, sizing Client Access Licenses (CALs), and verifying the runtime end-to-end.
1. Product Overview and Component Map
WinCC V12 (TIA Portal) is the HMI/SCADA component of the SIMATIC TIA Portal V12 release. The visualization software covers the full range of panels through to PC-based SCADA. The relevant product line for thin-client work is WinCC Runtime Professional, which includes the WebNavigator server and client as installable options.
| Component | Media | Default install | User-defined install | Purpose |
|---|---|---|---|---|
| WinCC Runtime Professional (RT) | WinCC Product DVD | Yes (core) | Yes | PC-based SCADA runtime, tag server, alarms, logs |
| WebNavigator Server | WinCC Product DVD | No | Yes (optional) | Publishes RT graphics to web clients |
| WebNavigator Client | WinCC Product DVD | No | Yes (optional) | Browser-based / RDP-hosted client for operators |
| WinCC Engineering (TIA Portal) | WinCC DVD / TIA DVD | No | Yes | Configures the HMI project, alarm classes, tags |
| SQL Server (WinCC instance) | WinCC DVD | Yes | Yes | Archiving, logging, user administration |
For the official release notes, refer to the Delivery Release for SIMATIC WinCC V12 (ID 67797516) on the Siemens Industry Online Support portal. The document lists supported operating systems, prerequisites, and the approved PC hardware matrix.
2. Prerequisites
Before running the installer, confirm the following:
- Operating system: Windows 7 SP1 (64-bit) or Windows Server 2008 R2 SP1 / 2012 R2 are the supported WinCC V12 targets. The TIA Portal V12 setup blocks installation on unsupported builds; consult the delivery release document for the complete list.
- Microsoft .NET Framework 4.5 and the matching language pack installed.
- Microsoft Message Queuing (MSMQ) service installed and running — required by WinCC Runtime Professional for internal message distribution.
- SQL Server 2008 R2 SP2 or SQL Server 2012 (the WinCC setup installs a private instance by default; do not point WinCC to an existing production SQL instance during evaluation).
- Administrator account on the target machine (local administrator or equivalent for domain-joined servers).
- DVD or ISO image of the SIMATIC WinCC V12 / TIA Portal V12 product set. Siemens ships these as dual-layer DVDs; the WebNavigator files are part of the standard media set.
- Internet Explorer 9 / 10 / 11 (32-bit) on client stations; the ActiveX-based WebNavigator Client is a 32-bit component.
- A Windows Server 2008 R2 / 2012 R2 machine if you intend to test thin clients (RDP). The thin client hardware itself can be any RDP-capable device (IGEL, HP t520, Wyse, etc.).
3. Step-by-Step Installation
3.1 Launch the user-defined setup
- Insert the WinCC V12 / TIA Portal V12 product DVD. The setup launcher starts automatically; if autorun is disabled, run
Start.exefrom the root of the DVD. - Select the language and accept the license terms.
- On the product-selection screen, choose WinCC Runtime Professional. The product is what unlocks the WebNavigator options in the user-defined tree.
- When prompted to choose between typical and user-defined installation, select User-defined installation. The typical install path skips optional components such as WebNavigator.
3.2 Select WebNavigator packages
Expand the WinCC Runtime Professional node in the package tree. The dialog mirrors the structure documented in the Siemens application example (ID 28309119), Chapter 5.2.1, Table 5-3. Tick the following entries:
| Package | Path in setup tree | Required for |
|---|---|---|
| WebNavigator Server | WinCC Runtime Professional → Options → WebNavigator | Publishing HMI graphics to web clients |
| WebNavigator Client | WinCC Runtime Professional → Options → WebNavigator | Operator stations (also for RDP sessions on the Terminal Server) |
| WebNavigator Configuration | WinCC Runtime Professional → Options → WebNavigator | Managing user permissions on the WinCC project |
3.3 Complete the installation
- Click Next and review the disk-space summary. A full WinCC Runtime Professional install with WebNavigator typically requires 8–12 GB.
- Click Install and wait for the wizard to copy files, register services, and configure the WinCC SQL instance.
- When the installation finishes, leave Restart computer selected and reboot.
3.4 Activate the demo license
On first start of the WebNavigator configuration tool, WinCC displays the license manager. Choose Activate trial license (30 days). The license is bound to the host's SID and is valid for 30 calendar days, after which the runtime switches to a one-hour grace period before logging the project out.
4. Deploying the WebNavigator Client
The WebNavigator Client can be installed two ways: as part of the Runtime Professional DVD setup (Section 3), or distributed via group policy to operator stations. For trial deployments, the in-place install is sufficient.
4.1 Installing on a Windows operator station
- Run the WinCC V12 setup on the operator PC.
- Choose User-defined installation.
- Select only WebNavigator Client; you do not need the Runtime Server components on operator stations.
- Complete the wizard and reboot.
4.2 Installing on a Terminal Server (RDP host)
For thin-client testing, install the WebNavigator Client on the Windows Server that hosts the RDP sessions. Each RDP session can then run a separate WebNavigator operator console.
- On the Terminal Server, open Server Manager → Add Roles and Features and confirm the Remote Desktop Services role is installed with the Remote Desktop Session Host service.
- Run the WinCC V12 setup with WebNavigator Client selected.
- Publish the WebNavigator Client icon as a RemoteApp so the thin client sees it as a native application. Use the
tsconfig.mscsnap-in orRemoteApp Managerdepending on the Server version. - Confirm the RD Licensing Diagnoser reports sufficient TS-CALs (the WebNavigator itself does not consume TS-CALs, but every RDP session does).
Reference the Installing the WebNavigator Client (RT Professional) documentation for the step-by-step install procedure, supported Windows builds, and post-install verification checks.
5. Thin-Client Architecture
The thin-client topology is a three-tier architecture: the WinCC Runtime Server (process data and graphics), the Terminal Server (WebNavigator Client sessions), and the thin-client device (RDP endpoint). The thin client is a presentation device; no WinCC, no SQL, no ActiveX runs on it.
Latency budget for a comfortable operator experience:
| Path | Target RTT | Max acceptable RTT |
|---|---|---|
| Thin client ↔ Terminal Server (RDP) | < 30 ms | 80 ms |
| Terminal Server ↔ WinCC RT Server (WebNAV) | < 10 ms | 50 ms |
| WinCC RT Server ↔ PLC (S7 / OPC) | < 50 ms | 200 ms |
6. Configuration in the TIA Portal
- Open the HMI project in TIA Portal V12 and select the HMI device (e.g.,
RT_PC_1). - In the device properties, expand Web settings → WebNavigator.
- Set Operator stations → Number of WebNavigator clients to the planned number of concurrent operators. This value controls the licensing as well as the session pool.
- Define the start screen (typically the process overview) and the language list.
- Open Runtime settings → User administration and grant the WebNavigator user group the required operator authorizations.
- Compile the HMI project and download it to the WinCC RT Server.
6.1 User management (WebNavigator Configuration)
On the WinCC RT Server, open WinCC WebNavigator Configuration from the start menu. The tool exposes the following tabs:
- WebNavigator users — local or domain users authorized to log in via the web client.
- Groups — assign operators to groups with the rights configured in TIA Portal.
- WebNavigator settings — port (default 80 / 443), session timeout, encryption, and certificate selection.
- Server — start/stop the WebNavigator service, view active sessions.
7. Licensing and CAL Sizing
WebNavigator licensing has three independent layers. Mis-sizing the top layer is the most common reason for license audit flags.
| License | Scope | Type | Counted by |
|---|---|---|---|
| WebNavigator Server | One per WinCC RT Server | Countable | Server |
| WebNavigator Client (V12) | Concurrent operator sessions | Countable | Concurrent session |
| Microsoft RDS CAL (User or Device) | RDP sessions to the Terminal Server | Countable | Per named user or per device |
| Microsoft TS-CAL (per user / per device) | Remote Desktop Services access | Countable | Per session |
| SQL Server CAL | Devices connecting to the WinCC SQL instance | Countable | Per device or per user |
7.1 Worked sizing example
A production cell with the following target: 4 thin clients in the control room, 1 supervisor station in the engineering office, 1 maintenance laptop via VPN.
- WebNavigator Client licenses: 6 concurrent sessions. Add a 10 % headroom for shift overlap and training → round up to 8. (WebNavigator license packages commonly ship in 1, 3, 5, 10, 25, 50, 100.)
- WebNavigator Server: 1 license.
- Microsoft RDS CALs: 6 user CALs (or 6 device CALs if the thin clients are dedicated).
- SQL Server CALs: 1 per Terminal Server (the SQL instance receives connections only from the WebNavigator server side, not from each client). Use the Core license if the WinCC RT Server is dedicated to the WinCC workload.
8. Verification and Acceptance Test
- On the WinCC RT Server, start the project from the TIA Portal download or via
WinCC RT Start. Confirm the project is in Running state in the WinCC Explorer. - On a Windows operator station, open Internet Explorer 9 / 10 / 11 (32-bit) and navigate to
http://<wincc-server>/WebNavigator/. The portal page should display the project thumbnail. - Log in with a user defined in the WebNavigator Configuration. The process screen should render within 2–4 s on a Gigabit LAN.
- On the thin client, open the RDP connection to the Terminal Server and launch the published WebNavigator RemoteApp. Validate the same screens load and respond to input.
- Verify tag updates by toggling a bit in the PLC and confirming the screen updates within one polling cycle (default 1 s for WebNavigator).
- Trigger an alarm and confirm both the alarm line and the alarm log render.
- Test operator logout, session timeout, and reconnection.
9. Troubleshooting Matrix
| Symptom | Likely root cause | Resolution |
|---|---|---|
| WebNavigator option not visible in the setup tree | The user-defined install was not selected, or the wrong product was chosen (RT Basic instead of RT Professional) | Re-run the setup, choose User-defined, ensure WinCC Runtime Professional is selected; WebNavigator is not available under RT Basic |
| Browser prompts to install the ActiveX control and fails | 32-bit IE not used, or ActiveX filtering / Enhanced Security Configuration (ESC) blocks the install | Use the 32-bit version of Internet Explorer; disable ESC on the server, or add the WebNavigator site to the Trusted Sites zone |
| Login fails with "WebNavigator license not available" | Demo license expired, or the concurrent-client count was reached | Re-arm the trial on a fresh image, or purchase additional WebNavigator Client licenses; check WinCC WebNavigator Configuration → Server for current sessions |
| Thin client shows black screen after RDP login | WebNavigator Client not installed on the Terminal Server, or RemoteApp not configured correctly | Install WebNavigator Client on the Terminal Server, publish the .exe via RemoteApp Manager, verify the user has logon rights to the server |
| Tags update very slowly or not at all | WebNavigator Server on a different subnet; firewall blocks port 80/443; S7 connection configured only on the local PC station | Open the required ports; check the TIA Portal connection list and confirm the S7 connection is configured on the WinCC RT Server, not on a client |
| Alarms appear on the engineering station but not on the WebNavigator client | Alarm class not assigned to the WebNavigator user group; language not enabled for the client | In TIA Portal → Runtime settings → User administration, grant the group alarm-acknowledge rights; in WebNavigator Configuration enable the runtime languages |
| Browser shows "Page cannot be displayed" | WebNavigator service is stopped, or port conflict (IIS shares port 80) | Start the SIMATIC WinCC WebNavigator service; if IIS is in use, change the WebNavigator port under WebNavigator settings |
| Operator sees another operator's screen | Session caching in IE; wrong user logged in at the OS level on the Terminal Server | Clear IE cache, force unique session per user via RDP Group Policy: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections → Restrict each user to a single session = Disabled
|
10. Migration Path Beyond V12
V12 was the first TIA Portal release to integrate the WebNavigator install path. If the trial is successful and a production rollout is planned, consider these forward moves:
- WinCC V13 / V14 / V15 and later: The product DVD structure changes between releases; the current Installing the WebNavigator Client (RT Professional) documentation reflects the V20 procedure. Always consult the release-specific document before redeploying.
- WinCC Unified (V17+): The Unified line replaces the ActiveX WebNavigator with a HTML5-based web client. The thin-client architecture is the same (Terminal Server hosting the client), but the browser is decoupled from Internet Explorer.
- WinCC OA: For larger SCADA rollouts, consider WinCC OA (Object Arithmetic) which has its own thin-client model and a different license structure.
11. Field-Engineer Checklist
Before signing off the trial, validate the following on a clean machine:
- WebNavigator packages present in the WinCC V12 product DVD (Server + Client + Configuration).
- User-defined install completed, default install rejected.
- 30-day demo license activated and the expiry date noted.
- WinCC project compiled and downloaded to the RT server.
- IE 32-bit on the operator station loads the WebNavigator portal.
- Terminal Server hosts the WebNavigator Client and the thin client launches the RemoteApp via RDP.
- Tag updates, alarms, language switching, and operator logon / logoff work end-to-end.
- License stack sized for the production target (Section 7.1).
- Image of the trial machine captured for clock reset if a second 30-day cycle is required.
Frequently Asked Questions
Where is the WebNavigator installation option in WinCC V12?
It appears only under the WinCC Runtime Professional package in the user-defined installation tree. Launch the DVD setup, choose User-defined installation, select WinCC Runtime Professional, and tick WebNavigator Server, WebNavigator Client, and WebNavigator Configuration. The option is not present in a typical/default install and is not available under WinCC RT Basic.
Can I run WebNavigator on a thin client without a Terminal Server?
No. A thin client is an RDP endpoint and cannot host the WebNavigator ActiveX client. You must deploy the WebNavigator Client on a Windows Server 2008 R2 / 2012 R2 (or later, per the compatibility matrix) Terminal Server and have the thin client open an RDP session to it. Publish the WebNavigator Client as a RemoteApp for the cleanest user experience.
How long is the WebNavigator trial license valid in V12?
WinCC V12 grants a 30-day license-free trial the first time the WebNavigator is launched. The countdown is anchored to the host SID and continues even if the project is recompiled. To extend the trial, restore a clean machine image to reset the host SID; reinstalling the application alone does not reset the counter.
What licenses are required to run WebNavigator in production?
You need one WebNavigator Server license, N WebNavigator Client licenses for N concurrent operator sessions, and Microsoft RDS CALs (User or Device) for each RDP connection to the Terminal Server. Add SQL Server CALs only if the SQL instance is licensed in CAL mode; a Core license on a dedicated WinCC host is usually cheaper for small deployments.
Which browser does the WebNavigator Client require?
WebNavigator V12 is ActiveX-based and requires the 32-bit build of Internet Explorer 9, 10, or 11 on the operator station or Terminal Server. Enhanced Security Configuration must be disabled on Windows Server, and the WebNavigator site should be added to the Trusted Sites zone to allow the ActiveX control to install.