Troubleshooting SIMATIC Management Console Network View Inventory Export Failures

In SIMATIC Management Console (SMMC), inventory data export under Network View failing—indicated by computer icons turning yellow and the export halting without generating files, while Plant View export functions normally—occurs when the export is executed over a Microsoft Remote Desktop (RDP) session or due to insufficient administrative DCOM tokens. The SMMC Network View export interacts with local shell components and COM interfaces that reject virtualized RDP desktop sessions. To resolve this, perform the inventory export directly from the local console session (or connect via 'mstsc /admin'), ensure only one SMMC exists in the network broadcast domain, and confirm user membership in 'SIMATIC Management Administrators'.

SIMATIC Management Console Architecture and Inventory Views

The SIMATIC Management Console (SMMC) provides centralized software and hardware lifecycle management for SIMATIC PCS 7 plants. It interrogates distributed Engineering Stations, OS Servers, OS Clients, and field controllers across the network using background services called SIMATIC Management Agents (SMAgent).

SMMC presents inventory data across two distinct operational perspectives:
1. Plant View: Evaluates the STEP 7 multiproject structure offline (configured hardware racks, MLFBs, software block versions, and Process Objects). This export processes local database files directly.
2. Network View: Queries the live physical network online (installed Windows operating system patches, firmware revisions, SIMATIC software packages, and license keys installed across physical PC stations). Network View export communicates dynamically with remote SMAgents.

Root Cause Analysis - RDP Session Virtualization and Export Halts

When an engineer right-clicks a computer in Network View, executes Determine inventory data (which succeeds), and then clicks Export inventory data..., the computer icon abruptly turns yellow, and the export wizard aborts without outputting Excel or XML files. This behavior is caused by:
- Remote Desktop (RDP) Protocol Virtualization: When accessing SMMC over standard Windows RDP, the session operates in a virtualized desktop context (Session ID >= 1). The SMMC export engine relies on Windows COM/OLE automation to launch background Excel/XML export threads. In virtualized RDP sessions with local drive or clipboard redirection, Windows security blocks the export token.
- Single SMMC Rule Violation: Siemens rules dictate that only one single SIMATIC Management Console may exist within a single network subnet. Running two consoles in the same broadcast domain causes agent communication race conditions.
- User Group Privileges: The active user must belong to local Windows group SIMATIC Management Administrators on both the console PC and all target agent stations.

Operational Comparison: Network View vs Plant View Exports

The table below contrasts the mechanisms, dependencies, and execution boundaries of SMMC inventory exports:

Attribute / ParameterPlant View ExportNetwork View Export (Target Issue)Resolution / Recommended ActionData SourceOffline STEP 7 Multiproject DBOnline Live PC Stations via SMAgentNetwork View requires active online agent handshake.Execution via RDPSupported (Works over RDP)Fails / Turns YellowMust execute on local console or mstsc /admin.User Group RequiredSIMATIC HMI / Windows AdminSIMATIC Management AdministratorsAdd domain user to local management group.Network ConsolesUnrestrictedStrictly One SMMC per SubnetDecommission duplicate SMMC installations.Output FormatXML / Microsoft Excel (.xlsx)Microsoft Excel (.xlsx)Local session required to bind OLE spreadsheet generator.

Step-by-Step Remediation Procedure for SMMC Inventory Exports

Access Workstation via Console Session:
- Avoid standard RDP sessions. Log directly onto the physical console of the SMMC workstation.
- If physical access is unavailable, open the Windows Run dialog on your client PC and connect using administrative console mode: mstsc /v:<SMMC_IP> /admin.
- In the RDP connection settings, navigate to Local Resources -> More: uncheck Local Drives and Printers redirection.
Decommission Duplicate Management Consoles:
- Audit the plant network to ensure only one PC station has the SIMATIC Management Console application active.
- If a second console exists on another ES, decommission or uninstall it to eliminate agent Pre-Shared Key (PSK) conflicts.
Verify Windows Security Group Memberships:
- On the SMMC station, open Computer Management -> Local Users and Groups -> Groups.
- Verify that the logged-on user account is an explicit member of SIMATIC Management Administrators.
Restart SMAgent Service on Target Stations:
- On target agent PCs, open services.msc and restart the SIMATIC Management Agent service.
Execute Network View Inventory Export:
- In SMMC, select Network View -> right-click the target station -> select Determine inventory data.
- Once determination reports success, right-click and select Export inventory data....
- Choose the export destination folder on a local hard drive (e.g., C:\SMMC_Exports\Inventory.xlsx). The export completes cleanly without icon color changes.

Verification

Verify export integrity through the following checks:
1. Confirm that computer icons in the SMMC Network View retain their normal green status throughout the export sequence.
2. Confirm that the export progress bar reaches $100\%$ and generates a formatted Microsoft Excel (.xlsx) workbook.
3. Open the exported spreadsheet: verify complete inventory tables listing installed PCS 7 component versions, installed Hotfixes, BIOS versions, and active license keys across all network nodes.

Limitations and Operational Precautions

Do not save SMMC export files directly to network mapped drives (e.g., Z:\), as network drive latency or SMB timeouts during large plant inventory aggregation can cause export thread aborts. Always save to local drive C: or D:, and subsequently copy the report to corporate servers. Furthermore, ensure that the SMMC database size does not exceed SQL Server Express limits (10 GB) in facilities with hundreds of managed nodes.