Deploying Legacy PCS 7 V6.1 SP1 in a Virtualized Windows XP Environment

In modern industrial computing, running legacy SIMATIC PCS 7 V6.1 SP1 on a Windows 10 host requires configuring a virtual machine hosting Windows XP Professional SP2 (32-bit). Siemens officially released PCS 7 for virtualization starting only with PCS 7 V7.1 SP2; running PCS 7 V6.1 on a hypervisor is therefore technically unsupported by Siemens and operates under user responsibility. However, for maintenance and software troubleshooting, deploying V6.1 inside VMware Workstation or ESXi is achievable. The virtual machine requires a bridged virtual network adapter for ISO Industrial Ethernet protocols, dedicated CPU core reservations, and legacy authorization key handling via floppy disk images.

Virtualization Support Boundaries for Legacy PCS 7 Releases

Plants operating legacy infrastructure frequently face scenarios where original industrial PC hardware running Windows XP has failed, while the process control system cannot yet undergo a multi-month DCS migration. Engineers naturally seek to run the legacy engineering station on modern Windows 10 host laptops or ESXi servers using virtualization.

From a manufacturer support perspective, Siemens established the formal virtualization boundary in PCS 7 V7.1 SP2. That release introduced validated support for VMware vSphere (ESXi) and VMware Workstation with certified real-time communication drivers. SIMATIC PCS 7 V6.1 SP1 (released in 2005) was engineered strictly for bare-metal installations on Windows XP Professional SP2 (for Single Stations and ES) and Windows Server 2003 (for OS Servers). While Siemens does not certify or troubleshoot virtualized V6.1 environments, maintaining a virtualized V6.1 image is the industry-standard method for offline logic modification and legacy project maintenance.

Technical Challenges of Running PCS 7 V6.1 in Virtual Environments

Deploying PCS 7 V6.1 SP1 inside a hypervisor introduces several specific technical challenges:

Industrial Ethernet Communication and CP Emulation: Bare-metal PCS 7 V6.1 systems heavily utilized dedicated PCI communications processors such as the CP 1613. Virtual machines cannot access physical PCI cards without complex VM direct path I/O (PCI passthrough). Engineers must configure SIMATIC NET SOFTNET-IE using a standard virtual network adapter (Intel E1000 emulation) operating in Bridged Mode to support layer-2 ISO Industrial Ethernet transport protocols.
Legacy Authorization Keys (Yellow Floppies vs. ALM): PCS 7 V6.1 was in the transition phase between the legacy Floppy Disk Authorization system (AuthorsW.exe with AX NF ZZ folders) and Automation License Manager (ALM V2/V3). Hypervisors on modern PCs without physical 3.5-inch floppy drives require creating virtual floppy disk images (.flp / .img) or using USB floppy drives to transfer license keys.
Real-Time Determinism and Hardnet Drivers: High-availability controller communication (S7-400H) and large-scale OS server redundancy can experience communication dropouts in virtualized environments due to hypervisor CPU scheduling latency.

PCS 7 Version Virtualization Support and Hypervisor Compatibility Matrix

The following table compares official virtualization status and technical prerequisites across PCS 7 versions:

PCS 7 VersionOfficial Virtualization SupportSupported HypervisorsGuest Operating SystemNetwork Adapter TypePCS 7 V6.1 SP1Unsupported (User Responsibility)VMware Workstation 10/12, ESXi 5.5Windows XP Pro SP2 (32-bit)Intel E1000 Bridged (Softnet-IE)PCS 7 V7.0 SP3Unsupported (Test benches only)VMware Workstation 10/12Windows XP Pro SP3 (32-bit)Intel E1000 BridgedPCS 7 V7.1 SP2+Officially CertifiedVMware vSphere 4.1 / 5.0Windows XP / Server 2003VMXNET3 / E1000 CertifiedPCS 7 V8.2Officially CertifiedVMware vSphere 5.5 / 6.0Windows 7 SP1 / Server 2008 R2VMXNET3 Dedicated Virtual SwitchPCS 7 V9.0 SP1Officially CertifiedVMware vSphere 6.5 / ESXi 6.7Windows 10 LTSB / Server 2016VMXNET3 Enterprise vSwitch

Step-by-Step Procedure to Configure Virtualized PCS 7 V6.1 on Windows XP

To configure an operational PCS 7 V6.1 SP1 virtual machine for engineering and maintenance:

Create the Virtual Machine Container:
- In VMware Workstation or ESXi, create a new virtual machine.
- Set the Guest OS to Microsoft Windows XP Professional (32-bit).
- Allocate 2 vCPU cores, 2048 MB (2 GB) RAM (Windows XP 32-bit cannot utilize more than 3.2 GB), and a 60 GB virtual disk formatted as IDE or LSI Logic SCSI.
- In the VM network settings, select Bridged: Connected directly to the physical network, and check Replicate physical network connection state.
Install Windows XP Professional and Prerequisites:
- Install Windows XP Professional Service Pack 2 (32-bit) from installation ISO.
- Install VMware Tools to enable graphics acceleration and mouse integration.
- In Windows XP, set Windows Firewall to Off and disable all energy-saving standby modes.
- Configure Internet Information Services (IIS) and Message Queuing (MSMQ) via Windows Components.
Install PCS 7 V6.1 SP1 and SIMATIC NET:
- Mount the SIMATIC PCS 7 V6.1 SP1 installation media.
- Execute setup and select the Engineering Station (ES) package.
- Install SIMATIC NET V6.3 / V6.4 (Softnet-IE).
- Reboot the virtual machine when prompted.
Transfer License and Configure Network Communication:
- Attach a virtual floppy disk containing the PCS 7 V6.1 license keys, or launch Automation License Manager (ALM) to transfer licenses from a USB stick.
- In Windows XP Control Panel, open Set PG/PC Interface.
- Set the interface parameter assignment to TCP/IP -> VMware Virtual Ethernet Adapter (or Intel PRO/1000 adapter).
- Assign a static IP address to the virtual network adapter matching your plant control network subnet.

Verification

Verify virtualized engineering operations:
1. Launch SIMATIC Manager in the Windows XP virtual machine; confirm that it opens without license or component errors.
2. Open an existing PCS 7 V6.1 project; verify that CFC charts, SFC charts, and hardware configurations load properly.
3. Connect the host PC physical Ethernet port to an S7-400 controller or test rack; ping the controller from the Windows XP command prompt.
4. In SIMATIC Manager, execute PLC -> Accessible Nodes; verify that the S7-400 CPU and communication processors are detected.

Limitations and Operational Precautions

Uncertified for Production Control: Do not utilize virtualized PCS 7 V6.1 as a 24/7 production OS server. Lack of hardware clock synchronization and real-time network determinism can cause server redundancy failovers.
Physical CP Card Incompatibility: Communications processors requiring dedicated PCI hardware (CP 1613, CP 5611) cannot be used in standard VMs; communication must rely on Softnet-IE TCP/IP.
Commercial Accuracy Notice: Ensure that legacy PCS 7 licenses (6ES7658-...) transferred to virtual machines comply with Siemens End User License Agreements (EULA).

Engineer FAQ

Does Siemens provide technical support for PCS 7 V6.1 on virtual machines?

No. Siemens officially released virtualization support starting with PCS 7 V7.1 SP2. Virtualizing V6.1 is completely under the user's technical responsibility.

Which hypervisor is best for running Windows XP with PCS 7 V6.1?

VMware Workstation 10 or 12, and VMware ESXi 5.5 to 6.0, offer the most stable legacy hardware virtualization and bridged networking drivers for Windows XP.

How can I transfer licenses to a virtual machine without a floppy drive?

Use virtual floppy disk software (such as WinImage or VMware virtual floppy .flp files) to present the authorization keys to AuthorsW, or use ALM via USB.