Skip to content

26th August 2022 (Europe 1)

Scope

We have worked hard to deliver a great MindSphere experience. These release notes are relevant for MindSphere release by August 2022 and include new and adjusted features or fixed issues. If you find other issues, please give us your feedback by contacting our MindSphere Support.

MindSphere Remote Service

Applicable for

  • MindAccess IoT Value Plan
  • MindSphere Packaging and Pricing

What's new?

  • MRS UI V.2 now supports creation and editing of devices in primary and secondary networks.
  • Recently released "Data & Server Option" supports exciting use cases with data intelligence apps. For example, data ingest to MindSphere may be additionally encrypted.

Note

Most functional extensions of MindSphere Remote Service become only available under new MindSphere packaging and pricing. So please reach out to your Sales representative to have your subscription to IOT value plan upgraded accordingly.

System Requirements for MindSphere Remote Service (MRS)

Browser-based access to MindSphere Remote Services App on MindSphere

  • Microsoft WindowsTM 10 version 1909: Google ChromeTM (version 68 or newer)
  • Recommended screen resolution: 1280x1024 and 1920x1080 with zoom level 100%

Requirements for service personnel's PCs hosting MRS Service Endpoint (former Operator Client) as entry point for network-to-network access

  • Service Endpoint (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 ® 10 Version 1909
  • Linux ® Debian 9
  • Linux ® RedHat 7.6
  • Google Chrome TM version 68 or newer

Requirements for accessed devices hosting MRS Device Endpoint (former Device Client) as end point for network-to-network access

  • Device Endpoint (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 ® 10 Version 1909
    • Linux ® Debian 9
    • Linux ® RedHat 7.6

Requirements for transmitting application protocols with Remote Service

  • 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, SSH) or for the incoming Remote Engineering protocols
  • Native Remote Desktop Protocol (RDP) can only be launched from Windows ® based Operator PCs supporting this Remote Login protocol
  • The download package of the Service Endpoint (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 ® based Operator PCs

Known issues

  • There is no auto-assignment of RDP (and Ping) to Service Assets in secondary Device Networks - these must be assigned manually via MRS Protocol Applications
  • Service Assets may be serviced without upfront registration by means of On-Demand Devices via MRS V.1. Such On-Demand Devices have an expiration date, and they will show up in the MRS device tree until then. The expiration date is not enforced, so manual de-registration is necessary.
  • 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 "Lock Connectivity" targeting an entire site deactivated when working on the related Service Asset to ensure its proper setup.
  • In rare occasions, a gateway device might not display devices in secondary networks, which are connected to it. Please restart the gateway device or add another device.
  • Notification on successful deletion of devices in secondary networks, which are connected to an IPsec router, might not disappear, even though the device was successfully deleted - please relaunch MRS.
  • MRS V.2 displays up to 10 Protocol Applications assigned to one particular Device.

Any questions left?

Ask the community


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


Last update: August 26, 2022