...
Historian and Alarm redundancy replication keeps up on large projects, so the standby database synchronizes fully. Diagnostic tools can connect to the standby server, the standby no longer starts the Devices module Running when a device is Reserved or Remote, and Alarm Viewer respects a custom alarm-history table name.
...
Breaking Changes and Deprecations
The SolutionCenter API can no longer be enabled on a released build. The API has shipped disabled by default since 10.1.5 GA, pending security hardening work on the underlying service surface. Until this update, an operator could override that gate by setting both SolutionCenterApi.Enabled and SolutionCenterApi.AcceptRiskOnOldBuild to true in MachineSettings/TWebServices.json. That override is no longer available in a released build, and no configuration setting re-enables the API in the 10.1.5 line. Installations that had enabled the API this way will find it stops responding after this update. The API remains planned to become available in a future release once the hardening work completes.
Windows-Authentication logins relayed through a Secure Gateway now require the gateway’s Windows-Authentication mode. The runtime no longer accepts a Windows-Authentication claim as proof of identity; it is honored only when the connection itself was Windows-authenticated. If you run TSecureGatewayService with WA=false, set WA=true so the gateway relays over the runtime’s Windows-Authentication port — otherwise Windows-authenticated users through that gateway are refused after this update. Password-authenticated users through the same gateway are unaffected. The runtime must be started with /wa on .NET Framework for the Windows-Authentication port to exist.
...
Lifecycle and Support
Update 5d is planned as a free upgrade for every FrameworX 10.x customer, shipping with the platform’s standard within-major-version 100% compatibility commitment — every 10.1.x solution opens and runs without migration or rework. See Breaking Changes and Deprecations above for two configuration-level changes that may require an adjustment on affected installations.
The full lifecycle policy, version support phases, and end-of-support dates for older FrameworX and FactoryStudio versions are documented on the Product Lifecycle and End of Support page.
...