Configure PCS 7 V9.1 SP1 OS Clients and Assign Server Packages

In PCS 7 V9.1 SP1, an OS client is represented as a WinCC application client and receives the OS server data it needs through assigned server packages; it is not configured as another OS server. Assign the required OS server data to the client project in SIMATIC Manager and verify the assignment in the client's Server data list. If the correct assignment or download still reports an inaccessible target, investigate computer-name resolution and the documented ES-OS network prerequisites as a separate issue.

Why the OS clients do not appear as server targets

In a PCS 7 OS client/server project, an OS client is configured as a WinCC application client and receives server data from the OS server projects it must display. The PCS 7 V9.1 SP1 Operator Station Configuration Manual distinguishes the OS client from OS servers in SIMATIC Manager. The client does not become an OS server merely because it has an IP/MAC entry in HW Config.

For the reported system, the useful configuration path is to create/configure the OS client project in the PCS 7 project and assign the required OS server data to that client. PCS 7 documentation describes the “Assign OS Server…” action for the OS client project. The server packages are generated or updated through OS compilation/download, then assigned to the client. If the target-computer error occurs while performing the correct assignment/download, investigate connectivity and Windows name resolution separately; the forum replies report that IP-based access without working computer-name resolution can indicate a network configuration issue.

Configure the client and assign its server data

Confirm that each client has an OS client project represented as a WinCC application client in SIMATIC Manager, and that the server projects are configured and compiled. The operator-station manual shows the OS client as a separate station type from the OS server.
For the client project, use the PCS 7 OS-server assignment function and select the OS server data that the client must display. For a multi-client, assign the packages from each required OS server.
Compile/download the relevant OS server project so its server data are current, then complete the client assignment/download following the procedure in the PCS 7 V9.1 SP1 manual. The V9.1 Compendium states that server data are generated or updated during OS compilation and download, and that the client is provided with updated data when the OS server is downloaded or when client Runtime starts.
Verify the assignment in the client project's WinCC Explorer under Server data, and check the client Runtime's connection to each intended server.
If the client still cannot be reached during a download or package assignment, test access using the configured computer names from the ES and confirm name resolution, network profile, Windows firewall rules, and required shared-folder access. Use the Siemens ES-OS download FAQ for the exact network prerequisites and matching PCS 7 release; do not substitute IP/MAC assignment for verified host-name reachability.

Distinguish a configuration-list issue from a network issue

If the clients are absent from a dialog intended to configure or download OS server targets, first check that the operation is aimed at the correct object type. The client should be configured through its OS client project and server-data assignment; it is not a redundant OS server.

If the correct client assignment or OS download itself reports “The target computer is not accessible,” collect the exact operation, selected target, computer name, and load log. The ticket has two different suggestions: one reply says the client receives its configuration through server packages; another attributes the incomplete list to network browsing/name resolution because the stations were reachable only by IP address. The source does not show which operation produced the error or contain a screenshot, so a project-specific network fault cannot be confirmed.

Verification

Confirm that the client project has the intended server packages assigned and that the package list is visible under Server data. In Runtime, verify connection to both members of the redundant OS pair as applicable, the expected process pictures and tags, and alarm display from the assigned standard server. If it is a multi-client, verify data from every assigned server rather than relying only on a successful package transfer. Review the OS load log for the actual target and transfer result.

Limitations and Operational Precautions

The ticket does not provide the screenshot, full PCS 7/WinCC version and update levels, exact SIMATIC Manager operation, PC names, or load log. It therefore cannot establish whether the reported message is expected from an inappropriate configuration dialog or indicates name-resolution, share, firewall, or other connectivity trouble. PCS 7 V9.1 SP1 documentation supports the client/server package model; follow the matching manual for the installed update level.

Do not change station names, IP addressing, workgroup/domain membership, firewall rules, or server assignments on an operating system without the site's controls. Back up the project and coordinate OS downloads with operations. A wrong or missing package assignment can leave client displays without the intended server data.

Engineer FAQ

Should an OS client be configured as an OS server in Component View? No. The PCS 7 Operator Station manual represents an OS client as a WinCC application client, distinct from an OS server application.

How does a client receive OS server data? The OS server project generates server data packages. The OS client project is assigned the required server data, and PCS 7 updates the client package data during server downloads or client Runtime startup as documented for the applicable release.

What does a multi-client need? It needs server data from each OS server whose process information it is intended to display. Assign the appropriate packages to the client project.

Does an IP/MAC entry prove the client is reachable by name? No. It establishes configured addressing information but does not prove that Windows computer-name resolution or the PCS 7 download path works.

What if the correct assignment operation still reports the target computer as inaccessible? Capture the full load log and exact target name, then verify reachability by computer name and the network/share prerequisites in the matching Siemens ES-OS download documentation.

Technical References

Siemens, SIMATIC PCS 7 Operator Station (V9.1 SP1) Configuration Manual, 11/2021, section 6.1.4. It maps an OS client to a WinCC application client and identifies the OS client project type: PDF.
Siemens, PCS 7 Compendium Part A – Configuration Guidelines (V9.1), 03/2022, section 10.1.1, pp. 210–213. The section describes assigning OS server data/packages to client projects and updating them during server download or client Runtime startup: PDF.
Siemens, PCS 7 Minimal Configuration, Entry ID 24023824, V6.0, 06/2016, section 4.3. It shows selecting an OS client application and using “Assign OS server…”: PDF.

Configure PCS 7 V9.1 SP1 OS Clients and Assign Server Packages