Configuring WinCC 6.0 SP2 Server-Client Project with Standard

Overview of WinCC 6.0 SP2 Distributed Architecture

WinCC 6.0 SP2 supports a distributed server-client topology in which one or more WinCC Servers host the project database, graphics, archives, alarms, and tag data, while WinCC Clients open the runtime (RT) against the server packages exported to the client workstation. The client machine never edits server-resident data; it only renders pictures, subscribes to tag subscriptions, and reads archived values from the assigned Standard Server.

Two configuration objects control the distributed runtime:

• Server Data / Package - a binary export (\*.pck) of the server-side configuration (graphics, tag list, alarms, archives, user archives, text library, time synchronization, redundant partner settings). The client imports the package before activating runtime.
• Standard Server - the per-component server assignment on the client (Graphics, Archives, Alarms, Tags, User Archives, Text Library, Time Synchronization). The Standard Server dialog appears on the client under Server Data -> Standard Server...

Because both the start picture and the Standard Server assignment are client-side properties, the most common deployment failures are caused by editing them in the wrong project (the server project), missing package updates after a server change, or network/symbol-name resolution failures.

Prerequisites and Licensing

Server-Side Configuration

On the WinCC Server, confirm the project is configured for client distribution before exporting a package:

1. Open the WinCC Explorer of the server project.
2. Right-click Server Data and verify the option Server is checked. This flag is what differentiates a Server project from a single-user project.
3. Right-click Computer -> Properties -> Startup. Confirm the server's own start picture is set; this is independent of any client start picture.
4. Open User Administrator and create or activate the runtime user(s) that will be used by the clients for logon. WinCC Clients can use server-side user administration when SIMATIC Logon is configured, otherwise each client maintains a local user list mirrored from the package.
5. Right-click Server Data -> Export... (or the entry Server Data -> Server1 -> Export in WinCC 6.0 SP2). Choose a path the client can reach over SMB, e.g. \\<SERVER>\WinCCProjects\<PROJECT>\Packages\.

The exported file has the form <ServerName>_<ProjectName>_<Timestamp>.pck. Regenerate and re-export the package every time the server's picture tree, tag list, archive configuration, or alarm logging changes; clients importing a stale package will display deleted pictures or hold retired tags in subscription.

Client-Side Project Setup

1. Install WinCC 6.0 SP2 with the WinCC Client license on the target workstation.
2. Create a new client project on the client PC using WinCC Explorer -> File -> New. The client project name does not need to match the server project name; the link is established through the imported package, not the project identifier.
3. Stop the WinCC CCAgent (Control Center Agent) service before importing the package: net stop "CCAgent" or via Start -> Programs -> SIMATIC -> WinCC -> Tools -> CCAgentAdmin. This avoids a file lock on <Project>.mcp.
4. Copy the .pck file to the client project's Packages folder, typically C:\Program Files\Siemens\WinCC\WinCCProjects\<ClientProject>\Packages\.
5. In the WinCC Explorer on the client, right-click Server Data -> Import... and select the package. The server appears as a child entry under Server Data with the symbolic computer name from the export.

Configuring the Standard Server Dialog

The Standard Server dialog controls which server (out of one or more imported packages) supplies each runtime component to the client. This is the answer to the user's question 2 (access all pictures from server only).

1. In the client WinCC Explorer, right-click Server Data.
2. Select Standard Server... from the context menu. The Configure standard server dialog opens.
3. The list shows every symbolic computer name for which a package has been loaded on the client. Map each row to one of the listed servers:

If the list is empty, no package has been imported yet, or the package import failed silently. Re-check the Packages folder for the .pck file and confirm the import action completed without error.

Setting the Client Start Picture

Unlike Standard Server, the start picture is a property of the client computer, not the server. This answers question 1 in the source thread.

1. In the client project, right-click the local Computer node and select Properties.
2. Switch to the Graphics Runtime tab.
3. Under Start Picture, click Browse and select the desired .pdl from the picture tree. Any picture present in the imported package can be selected; it does not have to exist as a local file on the client.
4. Set Window to Full for production HMI panels; Process window mode is for embedded deployments.
5. Apply, then restart the WinCC Runtime or the CCAgent service.

If a single project contains multiple clients, each client maintains its own start picture; setting it on the server computer has no effect on remote clients. This is the architectural reason the source thread raised the question.

Resolving the "Assign Start Picture in Control Centre" Prompt

When the client runtime is started manually with WinCC Runtime Start from the desktop shortcut, WinCC 6.0 SP2 verifies that a start picture is defined for the local computer. If the field is empty (or contains a reference to a server-side computer object), the runtime prompts:

"Please assign start picture in the Control Centre."

This message means the CCAgent (the WinCC Control Center service) was unable to resolve a start picture for the local computer because one of the following is true:

1. The start picture is set on the server's Computer properties instead of the client's Computer properties.
2. The selected picture file is missing from the imported package (picture deleted on server after export; package not refreshed).
3. The picture path stored in the project database points to a relative path that no longer exists on the client after a project folder rename.
4. The local Computer node has No set under Server flag (single-user computer instead of client computer).

Fix procedure:

1. On the client, open Computer -> Properties -> Graphics Runtime and re-select a picture that you can verify exists by clicking Browse and locating it in the dialog.
2. If Browse shows no graphics, the package import has not placed the picture files into the client's GraCS folder. Re-export the package from the server and re-import.
3. Confirm the local computer type: right-click Computer on the client and verify it is set to Client, not Standalone. WinCC 6.0 SP2 changes the visible tabs based on this flag.
4. Restart CCAgent from Start -> Programs -> SIMATIC -> WinCC -> Tools -> CCAgentAdmin by selecting Stop and then Start. Equivalent command line: net stop "CCAgent" && net start "CCAgent".
5. Re-launch runtime with the desktop shortcut WinCC Runtime. The start picture should now load without prompting.

Network and Permission Verification

When the client cannot see the server in the Standard Server list, or runtime activates but no data appears, validate the underlying TCP/IP and Windows security layer in this exact order:

1. IP ping both directions. From the client: ping <SERVER_IP> and ping <SERVER_NAME>. Both must succeed. Failures on hostname only indicate a NetBIOS/LLMNR or DNS issue, not a routing issue.
2. SMB share access. From Windows Explorer on the client, type \\<SERVER>\WinCCProjects\<PROJECT>\ and confirm the project folder opens. The user running the WinCC client must have read permission on this share.
3. SQL Server connection. Verify the SQL service on the server is listening on TCP 1433: telnet <SERVER> 1433. The screen should clear to a blank cursor on success. The client uses the SQL Native Client to reach WINCC and the runtime databases <Project>_R, <Project>_ALG, <Project>_TLG.
4. DCOM and SIMATIC HMI group. The runtime user on both machines must be a member of SIMATIC HMI (added by the WinCC installer). Missing membership produces silent authentication failures when DCOM launches the WinCC server process on the host.
5. Firewall. Windows Firewall on Windows XP SP2 and Server 2003 SP1 is on by default after SP2. Create inbound exceptions for: CCAgent.exe, WinCC.exe, SQLServer.exe, and TCP ports 80, 1433, 139, 445.
6. Symbolic computer name match. Open Computer -> Properties -> General on the server. The Computer Name field must match the symbolic name embedded in the package file. If the server was renamed after the project was created, update the name in WinCC and re-export the package.

Troubleshooting Matrix

Verification Checklist

Before declaring the deployment complete, walk through this list with both machines logged in:

1. On the client, ping -a <SERVER_IP> resolves the server's NetBIOS name without timeout.
2. From Windows Explorer on the client, the share \\<SERVER>\WinCCProjects\<PROJECT>\GraCS\ opens and shows the .pdl files.
3. On the client, Server Data in WinCC Explorer lists the imported server with the symbolic name.
4. Standard Server dialog shows the assigned server highlighted for every component row.
5. Local Computer -> Properties -> Graphics Runtime shows a populated Start Picture path.
6. Start WinCC Runtime on the client; the start picture opens within 5–10 seconds with no control-center prompt.
7. Click a button on the start picture that has a C-action with SetTag; tag value updates on the server (verify with WinCC Tag Simulator or server-side Tag Management).
8. Open an AlarmControl on the client; live alarms from the server appear with correct state colors.
9. Open a TrendControl pointed at an archived tag; historic values render.
10. Close the client runtime cleanly and re-open; CCAgent does not re-prompt for start picture.

Field-Proven Caveats

• WinCC 6.0 SP2 has a known issue where the Standard Server dialog accepts an assignment but does not persist it if the project is closed before the dialog's Apply button is acknowledged. Always click Apply then OK and only then close the dialog.
• If the server was renamed (e.g. promotion from workstation to server hardware), regenerate the project on the server using Project Duplicator with the new computer name before exporting a fresh package. Importing an old package referencing the previous computer name creates a ghost Standard Server entry that cannot be deleted from the GUI; it must be removed by editing <Project>.DBF in the library directory while WinCC is stopped.
• Hotfix roll-ups for WinCC 6.0 SP2 are cumulative; install HF14 or later on both server and client to avoid a mismatch that triggers event ID 0x80040154 "Class not registered" in CCAgent logs.
• Multi-monitor clients in WinCC 6.0 SP2 must set Start Picture and Start Monitor in tandem; setting Start Monitor only without a matching Start Picture reverts to windowed mode on Monitor 1.
• When using the Web Navigator client option (not the standard Client), the start picture is configured separately in the Web Configurator and overrides the WinCC Client start picture for browser sessions.

FAQ