Migrating Siemens PCS 7 to Windows 10: Software and Licensing Guide

Migrating a Siemens SIMATIC PCS 7 Distributed Control System (DCS) from a Windows XP workstation to a Windows 10 platform is not a simple operating-system swap. PCS 7 is a tightly integrated bundle of engineering, visualization, and automation tools, and each subsystem (ES, OS, OS client, AS firmware, licenses) has its own compatibility and upgrade matrix. This guide walks through the software inventory, licensing transfer, version selection, and field-proven migration path so that a working XP-era system can be re-deployed on a modern Windows 10 platform without losing data, project files, or operator screens.

1. PCS 7 Software Stack Architecture

PCS 7 is delivered as a single installation package, but internally it bundles multiple Siemens products. Understanding the stack is essential before deciding what to keep, replace, or retire.

WinCC flexible is not part of PCS 7. WinCC flexible is the legacy HMI configuration tool for SIMATIC Panels (e.g., OP 77B, TP 177B, MP 277). It has been superseded by WinCC (TIA Portal) for panel and runtime configuration. If a site is still using WinCC flexible, it runs on its own licensing and is not bundled with PCS 7. Retiring it has no impact on a PCS 7 migration.

2. Prerequisites

Before the migration, confirm the following are in place:

• Full installed software inventory from the source PC: open SIMATIC Manager → Help → Installed Software. Save the screenshot or text output. This is the single most important document for the migration.
• Access to the Automation License Manager (ALM) on the current license server. Record all license keys (single, floating, trial, upgrade) and their assigned seats.
• Confirmed SIMATIC PCS 7 Contract (Software Update Service / SUS) status. An active SUS contract entitles the customer to receive the next major version at no additional license cost, and is the typical path for in-place upgrades.
• Hardware specification sheet of the existing AS (CPU type, firmware version, IM/CP modules, redundancy configuration). The AS firmware is upgraded separately from the PC software.
• Local Siemens sales contact or Solution Partner with PCS 7 certification. Migration of a live DCS is not a self-service install.

3. Inventory the Existing Installation

The inventory step is mandatory. Do not rely on memory or installer logs older than the project.

1. On the existing XP workstation, launch SIMATIC Manager.
2. Navigate to Help → Installed Software. This lists every installed component, build number, and Hotfix level.
3. Capture the PCS 7 DVD revision label (e.g., PCS 7 V8.2 + SP1 + HF3). This identifies the source installation precisely.
4. Open Automation License Manager on the license server. Export the license inventory to a text file: Edit → License Inventory → Export.
5. Document the number of OS servers, OS clients, BATCH stations, and Web clients. Each seat carries its own license.
6. Note the AS CPU type and firmware: in HW Config, right-click the CPU → PLC → Operating System Version. Record the firmware and order number (MLFB), e.g., 6ES7416-3ES06-0AB0, firmware V6.0.7.
7. Save the project archive: in SIMATIC Manager, File → Archive, and store the .zip/.arc file in at least two physical locations.

4. Licensing: Automation License Manager (ALM)

Siemens software licensing is handled by ALM. There are three license types:

For a major version upgrade, the standard path is:

1. Verify the existing Certificate of License (CoL) identifies the software as PCS 7 Vx.x.
2. Order a License Key Upgrade via the local Siemens sales office. Each original V8.x license typically requires one 6ES7 658-… upgrade license per seat.
3. After ordering, the new license is delivered through the Web License Manager portal and downloaded as a .zip.
4. On the new license server (Windows 10), install ALM V6.0 (or matching the target PCS 7 version), then import the new keys via ALM → License Key → Install.
5. Deactivate (return) the old V8.x license keys only after the new V9.0 installation is verified. ALM → License Key → Return. This frees the old key for use on another machine or for disposal.

5. PCS 7 Version Selection and Windows 10 Compatibility

Windows XP is end-of-life and not supported by any current PCS 7 version. The supported operating-system matrix is the second most important decision after the license inventory.

For an XP-to-Win 10 migration, the realistic target is PCS 7 V9.0 SP3 or V9.1. Staying on the original V8.0 to extend the life of older hardware is generally not worth the effort, because V8.0 was the last version that supported Windows 7, not Windows 10, and lacks the security patches built into V9.0.

6. AS Hardware and Firmware Considerations

The Automation Station (AS) is the SIMATIC S7-400 (or the newer S7-410H) controller. The PC-side migration does not change the AS, but several firmware-level updates are typically performed in the same project to avoid double downtime.

Firmware update procedure:

1. Connect the engineering PC to the AS MPI/PROFIBUS or PROFINET interface.
2. Open SIMATIC Manager → HW Config, right-click the CPU → PLC → Update Firmware.
3. Select the new firmware file (.upd) from the PCS 7 installation DVD under \Driver\Firmware\S7-400.
4. The CPU performs a restart; verify the new firmware in PLC → Operating System Version.
5. For redundant H-systems, repeat for the standby CPU, then perform a fail-over test.

7. Migration Strategy

There are two accepted strategies. The choice depends on the site's tolerance for downtime.

7.1 Side-by-Side Migration (Recommended)

1. Build the new ES, OS, and OS-client PCs on Windows 10 with the target PCS 7 version.
2. Install and bind the new license keys on the new license server.
3. Migrate the project archive from the old system. In SIMATIC Manager, open the project on the new ES, perform a project migration (File → Migrate Project) to bring the project forward to the new PCS 7 version.
4. Compile the OS, perform a delta download to the AS, and verify the new system in a lab/staging environment.
5. Schedule a cutover: switch operators to the new OS, switch AS connections, and leave the old XP system as a cold backup for at least one week.

7.2 In-Place Migration

1. Back up the existing XP PC's hard disk image (e.g., with a Windows PE bootable tool).
2. Re-image the PC with Windows 10.
3. Install the target PCS 7 version on the new OS.
4. Restore the project archive, not the application state, and migrate.
5. Re-bind the license keys to the new machine.

Side-by-side is the lower-risk path because the original system remains intact until the new system is fully validated. In-place is faster but leaves no fallback if the migration fails.

8. Step-by-Step Migration Procedure

The following procedure assumes a side-by-side migration to PCS 7 V9.0 SP3 on Windows 10 LTSC 2019.

8.1 Pre-Migration Tasks

1. Confirm all prerequisites from Section 2.
2. Order the necessary License Key Upgrade (LK UPG) keys.
3. Build the new Windows 10 PCs. Apply all Windows updates up to and including the .NET 4.7.2 / 4.8 prerequisite. Install the OS in the locale matching the PCS 7 installation (English, German, etc.).
4. Disable Windows Defender real-time scanning for the duration of the installation only. Re-enable after the project is loaded.
5. Set the Windows region and language to match the engineering language. Mixing language packages in PCS 7 is not supported.

8.2 Install the License Server

1. Install Automation License Manager V6.0 SPx on the dedicated license server. This PC must be reachable on TCP/4410 from all ES, OS, and OS-client PCs.
2. Import the new PCS 7 V9.0 license keys.
3. Open ALM → Help → About and confirm the server's hostname and IP. Document this — every client points to this hostname.

8.3 Install PCS 7 on the ES

1. Insert the PCS 7 V9.0 SP3 DVD. The setup launcher starts automatically.
2. Select the Engineering System (ES) installation type. The setup installs SIMATIC Manager, CFC, SFC, SCL, HW Config, NetPro, PDM, and the WinCC Configuration Studio.
3. Accept the default installation directory C:\Program Files\Siemens\Automation.
4. Restart when prompted.

8.4 Install PCS 7 on the OS Server

1. Repeat the installation on the operator station, selecting Operator System (OS) Server.
2. Confirm that the WinCC Runtime is installed and starts as a service.

8.5 Install PCS 7 on the OS Client

1. Select OS Client on each operator-client PC.
2. Configure the OS client to point to the OS server's project name in WinCC Explorer (Computer → Properties → Startup).

8.6 Migrate the Project

1. Copy the project archive from the old XP system to the new ES.
2. Open the project in SIMATIC Manager on the new ES. The system will detect the older project version and prompt to migrate.
3. Follow the migration wizard. For multi-project setups, migrate in this order: Master data library → S7 programs → OS projects → Batch projects.
4. After migration, run File → Save As to write the project in the new format. Do not overwrite the original archive until the migrated project is validated.

8.7 Compile and Download

1. In SIMATIC Manager, right-click the OS → Compile OS. Resolve any compilation warnings; warnings about server prefixes or redundant tags are common during migration and usually safe to ignore on first compile.
2. Right-click the AS program → Compile and Download Objects. Choose Download to Target System for the entire program.
3. Verify the AS goes to RUN after the download. If the AS stays in STOP, check PLC → Diagnostic Buffer.

8.8 Update AS Firmware (Optional but Common)

1. Follow the procedure in Section 6 to update the AS firmware.
2. For redundant H-systems, update the standby CPU first, then fail over, then update the primary.

9. Verification

Verification is not a single step; it is a structured checklist. Each item below is a discrete test.

10. Troubleshooting Common Migration Issues

11. Decommissioning the Old Windows XP System

After the new system has been in production for at least one full operating cycle, decommission the old XP system. Do not decommission immediately after cutover.

1. Return the old license keys via ALM: License Key → Return. This writes the old keys back to the CoL pool and frees them.
2. Export the final project archive from the old XP system and store it offline with a date stamp.
3. Wipe the old hard disk with a DoD 5220.22-M compliant tool, or physically destroy the drive if it contained sensitive process data.
4. Document the decommissioning date in the plant's asset register.

12. Key Specifications Reference

FAQ