Scalefusion July 9th, 2024 Release Notes
- 16 Jul 2024
- 1 Minute to read
- Print
- PDF
Scalefusion July 9th, 2024 Release Notes
- Updated on 16 Jul 2024
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Version Information:
- Scalefusion Dashboard: v53.3.0
- Scalefusion MDM Agent (agent app for Windows): v15.0.15
Release Notes:
- User Activation Count for OneIdP Users
Before moving to SSO, IT Admins must ensure users join the Directory, activate accounts, and reset passwords without which users cannot access services. Activation includes resetting passwords or enrolling a device. The user activation count on the Directory page, gives them an idea on how many users have activated versus of how many have not yet activated. The Directory shows activation stats, allowing reminders to be sent to users pending activation. This aids in transitioning smoothly to OneIdP SSO by tracking activated and pending users. - Multi-Group selection in DeepDive
Admins can now select multiple groups in DeepDive to see a consolidated report of all selected groups. - Addition of new Device Properties
We have extended the default properties that are available with $device. We now support $device with the following:- machine_name
- public_ip
- ip_address
- device_mac_address
- exchange_id
- ethernet_mac_address
- bluetooth_mac_address
- Android Profiles: OEM Configuration Duplicity Issue
Whenever an Android Device Profile is cloned, OEM configurations (if any) will not get cloned. - Issue Fixes in Windows
- A white screen is visible on attempting to re-login using Keycard after locking the system.
- Optimized the handling of SMB2 queries that the client performs to detect the user information resulting in fewer calls to the Active Directory for a domain joined device.
- Fixed issue, where if OneIdP Keycard or Location is configured via Webkit method then an error is shown on device lock/unlock indicating that Microsoft Edge cannot access a particular storage location.
- Fixed issue where the ScreenTime report double-counts the application usage thereby showing wrong usage results.
Team:
- Team Scalefusion
Was this article helpful?