Wonderware Intouch — Compatibility Matrix

She applied the fix. Then she exported the InTouch application from the Windows 7 machine—a sprawling, 8,000-tag monstrosity controlling fermenters, cookers, and the new CIP system. She imported it into a virtual machine container she’d spun up on the Windows 11 edge server. The container ran a simulated Windows 7 environment. It was ugly. It was unsupported. But the Compatibility Matrix had a second footnote: “Legacy applications may function within Type 1 hypervisors if network stack isolation is enabled.”

Marta let out a breath she didn’t know she’d been holding.

“The one where engineers annotate their own findings. Look at the entry for InTouch 10.1 SP3 with Historian 9.0 on NTFS volumes larger than 2TB. There’s a handwritten note—I swear it’s handwritten in the PDF—that says: ‘SQLite timestamp mismatch. Set registry key: HLM\Software\Wonderware\Historian\UseSystemTime=1.’ ” wonderware intouch compatibility matrix

“I know what it says. But the footnote about hypervisors gave me cover. Historian’s dead though. Any buried notes?”

“The real one?”

A pause. Keyboard clicks. “Okay, I’m looking at my internal copy—the one with the red ‘Draft – Not For Distribution’ stamp. Version 8.3 of the Matrix. See, there’s a master matrix and then there’s the real matrix.”

Two: The legacy SCADA system—Wonderware InTouch 10.1—was older than some of her interns. She applied the fix

She opened the Compatibility Matrix again. There was a footnote—tiny, almost invisible—next to InTouch 10.1’s DASMBTCP driver. “When migrating to newer OS kernels post-2020, DAServer heartbeat intervals may desynchronize. Resolution: Increase S heartbeat timeout from 30s to 90s in the ArchestrA System Management Console.”