The errors have been fixed last week via Security and bugfix errata for Univention Corporate Server and today we also released an important update Security and bugfix errata for Univention Corporate Server which required to re-execute the joinscripts of the monitoring packages.
Zabbix is an enterprise-class open source distributed monitoring solution. Zabbix is released under the GPL, thus it is free of charge for both commercial and non-commercial use. A complete text of the license is available at
One of Guru3D's favourite hardware diagnostic tools, Everest, has been upgraded to version 5.00
Everest offers accurate hardware information and diagnostics capabilities, including online features, memory benchmarks, hardware monitoring, and low-level hardware information. EVEREST Home Edition is optimized for Microsoft Windows XP and Windows Server 2003 operating systems, and it fully supports the Vista / XP look & feel.
Note also that if video to the monitor fails, that often flash is still successful, and that serial console could be used instead for first account setup (which also makes debugging and fixing video issues easier).
The Marie Reay 5.02 is a learning space located on the Marie Reay Teaching Centre Building. This space is used for mid-scale teaching and seminar. The room is equipped with wireless presentation capability, laptop input connections, Echo360 lecture capture, an ANU resident PC and microphones.
The first time a Solstice Pod running Solstice 6 is plugged in out of the box (or after a factory reset), a new series of screens will launch on the connected HDMI monitor. This tool walks through checking connections to a network, the internet, and the Solstice Cloud management portal that are needed to fully deploy a Solstice Pod. It provides tips for resolving common issues, QR codes linking to further resources, and information about other available services.
On Solstice Pods connected to dual display monitors set to Extend or Seamless Extend (Welcome Screen settings), the welcome screen will be mirrored on both monitors rather than the background spanning both screens and the instructions appearing on only one screen. Custom background images may also fail to load for Pods set to these extended display modes.
Automatic peripheral switching between the Solstice Pod and video room system. To integrate with a video room system, an administrator will configure the Solstice Pod to signal an external USB switch via RS-232 or HTTP-based API calls, enabling it to use attached display monitors and peripherals while Solstice is in use. This feature also supports direct switching between Solstice and all-in-one video conferencing devices that accept HTTP-based API calls, such as the Poly Studio X30 and X50. Note: Mersive recommends turning off sleep mode settings for video room systems and all-in-one devices in a Solstice VRI configuration.
Display switching between Solstice and video room system. When users are connected to the Solstice Pod, the display monitor and audio/video peripherals will be switched to be used by Solstice, and Solstice will remove the video room system input post. When all users have disconnected, the Solstice interface will be automatically hidden, peripherals will be switched back to the room system, and the video room display will be restored.
Video room system monitoring service (optional). If the custom overlay message is displayed, the Solstice Video Room Service should be installed side-by-side on the video room system device. This service ensures that the overlay message will not be displayed during active video room calls. If using a custom video room system image on a host device, this service should be packaged with that image when it is created. The Solstice Video Room Service will be available for download shortly following the Solstice 5.5 release at mersive.com/download-admin/.
Automatic Display Power Management Based on Room Occupancy. Solstice can now leverage a USB camera attached to the Pod as a room occupancy sensor for Solstice display power management, providing an automated, touchless sleep/wake functionality. The feature requires a supported USB camera attached to the Pod and can be enabled in Solstice Dashboard or Solstice Cloud. When Solstice detects that a person is in the room, Solstice will immediately resume the HDMI out signal, resulting in a touchless power on for the display. When this feature is enabled and Solstice detects that the room has been vacant for the configured period of time (Immediate, 5, 10, 15 minutes), then the HDMI out signal to the display will be turned off, allowing the display monitors to use their own sleep settings. Learn more about this feature
Location Services. Solstice will use environmental scans (such as WiFi SSIDs and Bluetooth) to estimate the location of Pods using AI models that learn over time. Using this information, the Solstice app will reorder the list of discovered Pods to list displays that are closest first, allowing users to quickly connect to the Pod that they are physically nearby, streamlining the connection process. Location services also allow Solstice Cloud admins to visualize Pod locations on an interactive map. Additionally, location services help to facilitate the automatic categorization of Pods by country, city, and building to be used with Solstice Cloud monitoring, management, and data analysis. Solstice Cloud users can use these location-based categories to quickly sort and filter Pods, allowing them to analyze meeting trends by location, or setup location-specific email alerts. Gen3 Pods only.
This new JFR event is enabled by default. The java.security.debug=properties system property will also now print initial security properties to the standard error stream. With this new event and the already available jdk.SecurityPropertyModification event (when enabled since it is not enabled by default), a JFR recording can now monitor the initial settings of all security properties and any subsequent changes.
It is now possible to monitor deserialization of objects using JDK Flight Recorder (JFR). When JFR is enabled and the JFR configuration includes deserialization events, JFR will emit an event whenever the running program attempts to deserialize an object. The deserialization event is named jdk.Deserialization, and it is disabled by default. The deserialization event contains information that is used by the serialization filter mechanism; see the ObjectInputFilter specification. Additionally, if a filter is enabled, the JFR event indicates whether the filter accepted or rejected deserialization of the object. For further information about how to use the JFR deserialization event, see the article Monitoring Deserialization to Improve Application Security. For reference information about using and configuring JFR, see the JFR Runtime Guide and JFR Command Reference sections of the JDK Mission Control documentation.
Starting from WMS v. 5.02.20201015.2, a new version of the library is available. The library supports the new oAuth2 authorization and it is recommended to use it in order to ensure more secure performance of your integrations.
Starting from WMS v. 5.02.20201015.2, a new version of the library is available. The library supports oAuth2 authorization and it is recommended to use it in order to ensure more secure performance of your integrations.
If monitored users are not added to roster of a manager (the user whose credentials are used to access Wallboard), their user statuses are displayed as "Offline" with Light blue icon regardless their actual user statutes (ringing/ talking/ paused etc).
If monitored users are not connected to Collaboration/ x-bees, but added to roster, then only "Offline" status are displayed with Light Blue icon, while other statuses are displayed with the appropriate icons. So, if a user has a connected WP device, but is not logged into Collaboration/ x-bees, when the phone is ringing, Light Blue icon changes to Red phone icon etc.