WinCC Server Client Limits Configuring Multiple Clients

Problem Statement: 1 WinCC Server with 6 Clients on Windows XP SP3

Many legacy automation projects pose the question: "Is 1 WinCC server with 6 WinCC clients supported on Windows XP SP3?" The short answer is no. The official Siemens compatibility tool documents that Windows XP is only approved for a WinCC client/single-user operating system, or for a WinCC server project with a maximum of 3 clients. A 6-client server project on Windows XP SP3 falls outside the approved configuration envelope and must be treated as a non-supported scenario.

This article consolidates the version-specific WinCC client-server limits, explains the Windows XP SP3 constraint with its root cause, lays out a sizing matrix for legacy and current WinCC releases, and provides the verification steps an integrator should run before commissioning. The 6-client question is used as a worked example, but the limits and the upgrade path apply to any WinCC project being scaled beyond 3 client seats on a Windows XP host.

WinCC Client-Server Architecture Background

WinCC is a SCADA/HMI suite that follows the classical client-server model: the server holds the project, archives, alarms, and tags; clients connect to the server to visualize and operate the process. Each client requires a runtime license (WinCC RT Client or a WebNavigator/WebUX license), and the server holds the server license plus the project configuration. In a multi-server plant, one client can subscribe to up to 12 servers in runtime, allowing the operator to see data from many subsystems through a single client window.

The typical WinCC client-server topology places the server on the process LAN, with clients and optional WebClients in the operations LAN. For multi-server plants, redundant server pairs are bonded by the WinCC Redundancy option, which synchronizes archives and messages.

WinCC Server Maximum Client Counts by Version

Siemens has revised the supported client count several times as network bandwidth, PC RAM, and WinCC's internal connection pooling improved. The table below consolidates the published limits that apply when planning a 1+6 (1 server, 6 client) configuration.

Key takeaway: the WinCC engine has not raised the maximum parallel fat client count above 32 in any released version. The growth in concurrent connections has been delivered through WebNavigator and WebUX, which keep the heavy lifting on the server and stream the picture to thin-client browsers.

The Windows XP SP3 Constraint: Why Only 3 Clients

The "3 clients on XP" rule is documented in two Siemens sources that engineers must consult before quoting capacity:

1. WinCC Information System > Configuration > WinCC ServiceMode — defines that the ServiceMode runtime context is not available on Windows XP; the maximum number of client connections is reduced because the OS cannot host the same number of long-lived authenticated sessions as Windows Server 2003/2008/2012/2016/2019/2022.
2. WinCC Release Notes > Notes on Process Control Options > Server project on Windows XP with clients without own project — explicitly limits XP-hosted server projects to 3 simultaneous clients and prohibits the use of XP as a server when the client count is 4 or more.

Root cause analysis for the 3-client ceiling:

• Connection pool exhaustion: Windows XP Professional SP3 is built on the Windows NT 5.1 kernel, with a default limit of 10 simultaneous inbound SMB/NetBIOS sessions. WinCC uses Windows-authenticated DCOM/RPC sessions; even with optimizations, the kernel effectively caps usable connections at 3-4 active clients per server.
• Memory architecture: XP's 32-bit kernel with 4 GB address space (4 GB limited by PAE) leaves less contiguous virtual memory for WinCC's archive and alarm caches. Six clients synchronizing tag subscriptions against an XP server can drive the process into paging within hours.
• Service Mode absence: WinCC ServiceMode is required for unattended server operation (no interactive logon). XP cannot host services with the same reliability as a server-class Windows SKU, and Siemens withdraws support for this configuration in the ServiceMode chapter.
• Lack of extended security: XP SP3 reached end-of-support in 2014, and Siemens will not extend the compatibility matrix for new WinCC versions past the published cut-off date.

Verifying the Active Configuration

Before declaring the configuration unsupported, confirm the following from the live system. These steps are also the verification list to use after any upgrade.

1. Open the WinCC project on the server, right-click the project node in WinCC Explorer, and read the WinCC version + build number (e.g., "WinCC V7.5 SP1 Update 14").
2. From a command prompt on the server, run winver to capture the Windows version and Service Pack. Confirm whether the host is Windows XP SP3, Windows 7 SP1, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, or Windows Server 2022.
3. Count the number of WinCC RT Client licenses installed. In WinCC Explorer, navigate to Server Data > Licensing and read the count and type (RT Client, WebNavigator, WebUX).
4. Use the CCAlgLicLog log under the WinCC project directory to inspect active client sessions and their license IDs.
5. Run net session on the server to list the active inbound SMB sessions; this is a quick proxy for the kernel-level session count.
6. Check Redundancy > Server Pairs in the WinCC project to identify the number of redundant pairs. Each pair counts as 2 servers toward the 24-server ceiling.

Configuration Options to Reach 6 Client Seats

If the requirement is fixed at 6 clients and the host is Windows XP SP3, the engineer has four documented paths. Each path is rated for complexity, downtime, and risk.

Step-by-Step: Migration of a 1+6 Project from Windows XP SP3 to a Supported OS

This procedure assumes the existing project is WinCC V7.0 SP3 and the target is WinCC V7.4 SP1 on Windows Server 2012 R2. Adjust the build numbers for your specific situation.

Prerequisites

• Original WinCC V7.0 SP3 project archive (.zip) with the most recent engineering backup.
• Target server hardware meeting the WinCC V7.4 SP1 minimums: Intel Core i5 / 8 GB RAM / 250 GB SSD. For 6 clients, Siemens recommends 16 GB RAM to accommodate tag buffering.
• Windows Server 2012 R2 Standard with the latest cumulative update installed.
• WinCC V7.4 SP1 installation media (DVD or Siemens Software Delivery Service).
• Sufficient WinCC RT Client licenses (x6) and one WinCC Server license.

Procedure

1. Install Windows Server 2012 R2 on the new server hardware or in a fresh partition. Apply all Windows updates and the .NET Framework prerequisites that WinCC V7.4 SP1 requires.
2. Install WinCC V7.4 SP1 in Custom mode. Choose WinCC Server as the package type. Do not start the WinCC service yet.
3. Copy the V7.0 SP3 project backup to C:\Program Files (x86)\Siemens\Automation\WinCC\WinCCProjects on the new server.
4. Open the project in WinCC Explorer. WinCC V7.4 SP1 will run the project migration wizard. Accept the license agreement and confirm the upgrade.
5. Re-link the process communication channels. For S7-1500 PLCs, use the "SIMATIC S7-1500 Channel" with TLS activated. For S7-300/400, keep the named connections.
6. From the WinCC Information System, run the Project Duplicator tool to create the client projects: Start > Siemens Automation > SIMATIC > WinCC > Project Duplicator. Generate six clients with their own computer names, each pointing back to the central server project.
7. On each client, install the WinCC V7.4 SP1 RT Client option only. Do not install the configuration tools unless operator-level changes are expected.
8. Activate the WinCC server project. Verify that all six clients can start Runtime and load the start picture.
9. Run a 24-hour soak test with full alarm and archive load. Watch the server's CCArchiveAdmin and CCAlgRt log for connection churn.

Redundant Server Pair Sizing Rules

When the project expands beyond one server, the redundant pair model becomes relevant. The 2009-era WinCC documentation and the current WinCC V7.x manual both cap the configuration at 12 redundant server pairs, for a total of 24 servers. Each redundant pair requires:

• Two WinCC Server licenses (one per physical/virtual host).
• One WinCC Redundancy option license for the project.
• Identical archive configuration. Siemens requires byte-for-byte identical archive sizes; the configuration tool will warn if not.
• A dedicated heartbeat connection (named connection or TCP) on a separate VLAN for determinism.

Redundancy is not a workaround for the 3-client XP limit. Adding a second server still leaves each server constrained to 3 clients on XP. The redundant pair rule applies only on supported Windows Server SKUs.

WebNavigator and WebUX Sizing

Web clients are a way to grow the operator seat count without driving up the fat-client connection count. The licensing and topology rules differ from RT Client:

On a Windows XP SP3 server, WebNavigator is only licensed up to 3 concurrent clients because the host is treated as a 3-client server project per the Release Notes. The 50-WebClient cap applies only to a supported Windows Server host.

Troubleshooting Matrix: 6-Client Configuration Problems

Long-Term Roadmap

Windows XP SP3 has been out of mainstream support since 2009 and out of extended support since 2014. Any plant still running an XP-based WinCC server faces compounding risk: no security patches, no driver updates, no new WinCC version compatibility, and no OEM support. A staged migration plan is the only sustainable answer.

1. Phase 1 — Inventory: capture all WinCC server/client installations, versions, license counts, and connected PLCs.
2. Phase 2 — Hardware refresh: replace XP-era servers with a current x86-64 platform certified for Windows Server 2019 or 2022.
3. Phase 3 — OS migration: move the WinCC project to a supported Windows Server SKU without changing the WinCC version.
4. Phase 4 — WinCC upgrade: once stable on the new OS, evaluate WinCC V7.4 SP1 (or V8.0 if TIA Portal is in use) for project modernization.
5. Phase 5 — Modernization: introduce WebUX for additional operator seats, evaluate WinCC Unified as the long-term SCADA platform.

Field-Proven Caveats

• Some plants have run a 1+6 XP server successfully for years. This is operationally possible but out of support. The first major event (Windows update, antivirus signature, PLC firmware) can break the configuration.
• The "3 clients" rule counts simultaneous Runtime clients. Configuration clients and WebDiagnostics are not counted toward the 3.
• If the customer is using WinCC/CAS (Central Archive Server) or WinCC/BPC (Basic Process Control) options, additional platform constraints apply on top of the 3-client rule.
• Always quote the active Siemens compatibility tool matrix in writing when delivering a WinCC client-server project; it is the contractual reference for support.

Quick Reference Cheat Sheet

• Windows XP SP3 + WinCC server project = 3 clients maximum, per the WinCC Release Notes.
• 1 server + 6 clients on Windows XP SP3 = unsupported. Plan a migration.
• WinCC V7.x = up to 32 fat clients + 50 WebNavigator clients per server, on a Windows Server OS.
• WinCC redundant server pairs = up to 12 pairs (24 servers) per project.
• One client, multiple servers = up to 12 servers in runtime per client.