18^th February 2022 (Europe 1)¶

Scope¶

We have worked hard to deliver a great MindSphere experience. These release notes are relevant for MindSphere Release in February 2022 and include new and adjusted features, fixed issues as well as known issues for Subscribers of Capability Packages. If you find other issues, please give us your feedback by contacting our MindSphere Support.

MindSphere Remote Service¶

Applicable for

• MindAccess IoT Value Plan
• Subscribers of Capability Packages

What's new?¶

• The Device and Operator Clients can now assign their installation directory as their default root directory used, for instance for File Transfer operations
• Within this release, we have improved handling of links between Remote Service devices and Asset Manager for primary and secondary devices
• Within this release, we have improved Web Application in Remote Service (Engineering Option) in-app information. The Web Application does not display listener ports anymore as this is assigned automatically.

System Requirements for MindSphere Remote Service (MRS)¶

Browser-based access to MindSphere Remote Service App¶

• Microsoft Windows^TM 10 version 1909: Google Chrome^TM (version 68 or newer)
• recommended screen resolution: 1280x1024 and 1920x1080 with zoom level 100%

Requirements for service personnel's Operator PCs hosting MRS Operator Client (entry point for secure remote service connections)¶

• Operator Client can be downloaded from MRS
• Validated Hardware
• Processor: 32-bit or x64-based (Intel or AMD)
• Display size / resolution: 1280x1024 and 1920x1080 with zoom level 100%*

• Disk space occupied by Operator Client: 32MB

• Validated Operating Systems and Browsers

• Microsoft Windows ^TM 10 Version 1909
• Linux ® Debian 9
• Linux ® RedHat 7.6
• Google ChromeTM version 68 or newer

Requirements for Serviced Assets hosting MRS Device Client (end point for secure remote service connection)¶

• Device Client can be downloaded from MRS
• Validated Hardware
• Processor: 32-bit or x64-based (Intel or AMD)
• RAM: 0.5GB

• Disk space occupied by Device Client: 32MB

• Validated Operating Systems

• Microsoft Windows^TM 10 Version 1909
• Linux ® Debian 9
• Linux ® RedHat 8

Requirements for Remote Service protocols¶

• Operating system of Operator PC must provide clients for the used outgoing Remote Login protocols (e.g. RDP, VNC), whilst Engineering Tools used remotely on Operator PC typically have built-in clients for such protocols
• Operating system of Serviced Assets must provide servers for the incoming Remote Login protocols (e.g. RDP, VNC) or for the incoming Remote Engineering protocols
• Native Remote Desktop Protocol (RDP) can only be launched from Windows^TM based Operator PCs supporting this Remote Login protocol
• The download package of the Operator Client contains a Windows driver (installer file MRSTransparentProxy.msi) for Proxy-Unaware protocol
• Remote Engineering via Proxy-Unaware protocol is only available on Windows^TM based Operator PCs

Known issues¶

• There is no auto-assignment of RDP (and Ping) to secondary Service Assets. These must be assigned manually via MRS Protocol Applications.
• Service Assets may be serviced without upfront registration by means of On-Demand Devices. Such On-Demand Devices have an expiration date, and they will show up in the MRS asset tree until then. The expiration date is not enforced, so manual de-registration is necessary.
• Connectivity status of secondary Service Assets behind a gateway might not be shown as "connected", even though the secondary Service Asset can be accessed.
• Configuration changes are tracked in audit trail and system logs. Selected changes could be also be propagated via email notifications, which are not available for connection establishment or file transfers.
• It is recommended to have "Red Button" deactivated when working on the related Service Asset to ensure its proper setup.

Any questions left?

Ask the community

Except where otherwise noted, content on this site is licensed under the Development License Agreement.