Resolving Missing WinCC OS in SIMATIC Manager After Migration: AS-OS-Engineering and Windows Compatibility

In legacy SIMATIC PCS 7 migrations (such as upgrading from PCS 7 V5.2 to V6.1), the issue where the WinCC Operator Station (OS) disappears from the SIMATIC Manager Component View and PC Station tree after project migration is caused by either the missing installation of the 'AS-OS-Engineering' add-on package or running the software on an unsupported operating system (such as Windows 2000 instead of Windows XP Professional SP2/SP3). SIMATIC Manager relies on COM/DCOM interfaces registered by AS-OS-Engineering to display and manage WinCC .mcp projects. Under Windows 2000, modern V6.1 database objects fail to register due to outdated cryptographic and DCOM subroutines, causing SIMATIC Manager to silently suppress the OS object. Installing PCS 7 V6.1 on a validated Windows XP SP3 platform with full AS-OS-Engineering components restores complete OS visibility.

Role of AS-OS-Engineering in SIMATIC Manager Integration

In the SIMATIC PCS 7 environment, WinCC is not operated as a detached standalone SCADA system; it is embedded directly into the Step 7 SIMATIC Manager project tree as an 'Operator Station' (OS) object. This integration is governed by the AS-OS-Engineering software suite.

AS-OS-Engineering registers specialized ActiveX components, shell extensions, and database bridge DLLs (such as s7uvx.dll and s7os_eng.dll) into the Windows registry. These components allow SIMATIC Manager to detect the WinCC .mcp database file, manage network connections, compile tags from CFC charts, and trigger OS downloads.

Root Cause Analysis: Why the OS Object Disappears After Migration

When a user migrates a PCS 7 V5.2 project to V6.1 and finds the OS object missing from the PC Station container, the failure is traced to two primary root causes:

Missing AS-OS-Engineering Component: During custom or selective installations of WinCC V6.1, engineers sometimes fail to select the 'AS-OS-Engineering' option. Without this component, SIMATIC Manager treats the WinCC folder as unrecognized foreign data and hides the OS object from the project hierarchy.
Operating System Incompatibility (Windows 2000): PCS 7 V6.1 SP1 and higher was architected for Windows XP Professional SP2 / Windows Server 2003. Attempting to run PCS 7 V6.1 on legacy Windows 2000 fails because Windows 2000 lacks the updated COM+ infrastructure, modern Microsoft Data Access Components (MDAC), and cryptographic service providers required by Microsoft SQL Server 2000. During migration, the project migrator cannot register the SQL Server database schema, resulting in an aborted OS object link.

Operating System Compatibility: Windows 2000 vs Windows XP SP3

Siemens publishes strict operating system compatibility matrices for every PCS 7 release. For legacy systems:

PCS 7 V5.x: Strictly compatible with Windows NT 4.0 and Windows 2000 Professional.
PCS 7 V6.0: Compatible with Windows 2000 Professional SP3/SP4.
PCS 7 V6.1 SP1 to SP4: Strictly mandated for Windows XP Professional SP2 / SP3 and Windows Server 2003 SP1 / SP2. Windows 2000 is officially deprecated and unsupported for V6.1.

When the engineering environment is installed on Windows XP SP3, all required DLLs register cleanly, allowing SIMATIC Manager to attach to the WinCC SQL Server instance.

Step-by-Step Procedure to Restore Missing OS Objects

To recover the missing OS object on a properly configured Engineering Station:

Platform Validation: Ensure the host PC or virtual machine is running a clean, validated installation of Windows XP Professional SP3 (32-bit).
Install Complete PCS 7 Engineering Suite: Run the official PCS 7 V6.1 setup. Select Package Installation > Engineering Station. Verify that AS-OS-Engineering is checked under the WinCC component list.
Re-Migrate Project: Copy the original V5.2 project archive to the local drive. Launch the WinCC Project Migrator on the V6.1 station to convert the database.
Reinsert OS Object if Missing: If the OS object still does not appear in SIMATIC Manager:
- In Component View, right-click the PC Station and select Insert New Object > SIMATIC PC Station.
- In HW Config, insert a WinCC Appliance / WinCC Application into Slot 1.
- Open the PC Station in SIMATIC Manager, right-click the OS object, select Open Object, and link it to the migrated .mcp project file.

Comparison of Legacy PCS 7 Version OS and Platform Dependencies

The following table compares legacy PCS 7 versions, their native operating systems, and core database architectures:

PCS 7 VersionMandated Windows OSDatabase EngineAS-OS Integration ArchitecturePCS 7 V5.2Windows 2000 Professional SP2Sybase SQL AnywhereClassic Step 7 V5.1 DCOM ShellPCS 7 V6.0Windows 2000 SP3/SP4Microsoft SQL Server 2000AS-OS-Engineering V6.0PCS 7 V6.1 SP1-SP4Windows XP Professional SP2/SP3Microsoft SQL Server 2000 SP4AS-OS-Engineering V6.1 (Enhanced COM+)PCS 7 V7.1 SP3/SP4Windows XP SP3 / Windows Server 2003Microsoft SQL Server 2005 SP3AS-OS-Engineering V7.1PCS 7 V8.2Windows 7 SP1 (64-bit) / Server 2008 R2Microsoft SQL Server 2014Modern AS-OS-Engineering V8.2

Verification

Verify OS object integration in SIMATIC Manager:
1. Open SIMATIC Manager on the Windows XP station; expand the Multiproject and select the PC Station.
2. Confirm that the WinCC OS object (e.g., OS(1)) appears in the right pane with its standard blue WinCC icon.
3. Right-click the OS object and select Open Object; verify that WinCC Explorer launches and opens the project without error dialogues.
4. Right-click the OS object, select Compile; confirm that the 'Transfer AS/OS Connection Data' wizard opens and successfully maps the S7 connection to the AS controller.

Limitations and Operational Precautions

Never attempt to force PCS 7 software installation on an unsupported operating system release by modifying compatibility flags in the setup configuration files (Setup.ini). Unsupported OS environments experience silent COM registration failures, random database disconnections, and corruption of the Step 7 project database (.s7p). Always verify the exact service pack requirements in the official Siemens PCS 7 Readme before building an engineering machine.

Engineer FAQ

What does the 'AS-OS-Engineering' package actually do?

AS-OS-Engineering is the software bridge between Step 7 (PLC engineering) and WinCC (SCADA visualization). It enables SIMATIC Manager to create OS stations, configure connections in NetPro, and compile tags and alarms directly from CFC into WinCC.

Why did the OS object vanish on Windows 2000 but reappear on Windows XP?

PCS 7 V6.1 introduced new DCOM security models and SQL Server 2000 SP4 components that are incompatible with Windows 2000 core libraries. Under Windows 2000, the OS shell extension failed to load, so SIMATIC Manager hid the object.

Can I re-link a WinCC project if the OS object in SIMATIC Manager was accidentally deleted?

Yes. Insert a new WinCC Application in the PC Station in HW Config. Then in SIMATIC Manager, right-click the OS object, choose Properties, and browse to the existing .mcp file on disk.