🔶 Platform
Highlights
🖥️ Unified DaaS management from Portal. New centralized administration of virtual environments (machines, desktops, catalogs, delivery groups, sessions, and templates) from a single interface with complete operational control.
🔗 Automation with Webhooks. Real-time integration with external systems using automatic HTTP notifications for platform events.
🤖 AI-driven reports. Instantly generate custom reports from natural language descriptions, no technical knowledge needed.
⚙️ More flexible and precise alert configuration. You can now adjust alert severity and exclude them from the WRI calculation.
🗂️ Enhanced organizational context for devices. New visibility of Workspace Groups directly from the device detail to simplify operational analysis and segmentation.
🧹 Mass device removal. More agile and efficient management in cleanup and maintenance tasks through batch deletion.
Portal
🚀 New Features
-
DaaS. New unified management capability for virtual environments enabling administration of virtual machines and desktops, catalogs, delivery groups, sessions, and templates from a single control center. Facilitates monitoring of global status, resource optimization, and execution of operational tasks, reducing the complexity of managing this type of infrastructure.
-
Webhooks. Allows platform-generated events to be integrated with external systems through configurable HTTP notifications. Each event can trigger automatic actions in third-party tools, enabling advanced automation scenarios.
-
Create with AI - Reports. Generate custom reports from natural language requests. AI interprets the query, analyzes the data, and returns results in table format with the possibility to:
- Refine queries through additional requests
- Export to CSV
- Save as reusable report
- Schedule automated runs
- Send results by email
🔨 Improvements
-
New tab Workspace Groups in the device detail view to identify its organizational membership.
-
From Alert Configuration you can now:
- Edit the severity level of an alert.
- Exclude alerts from Workspace Reliability Index (WRI) calculation.
- Assign a minimum threshold of 60 minutes for logging event activation.
-
Mass device removal is allowed from device removal.
-
Possibility of hiding marketplace visibility from sub-organizations.
Workspaces
🔨 Improvements
- Displaying the host FQDN during microservices execution to enhance traceability.
- New column Free system disk in the devices list.
- Greater clarity in device deletion task text, making the action and origin explicit.
- Automatic error logging when attempting to run an unregistered microservice in Workspaces to facilitate diagnosis.
- Viewing the execution window of final user microservices.
- Jobs created from flows configured as Detection only are no longer marked as system jobs, improving their classification.
- Export limit to Excel of 10,000 records to improve platform stability.
- End-user microservices execution window.
Bug fix
This version includes an improvement in stability and state consistency, highlighting:
- Wake on LAN (WoL) scheduling jobs now send to Portal with the correct tenant property for the workspace group.
- Installation of FlexxAgent on versions above the allowed upper limit is prevented.
- Corrected Flexxible Remote Assistance operator behavior that incorrectly marked some reopened dynamic sessions as attended and prevented reconnection.
- Corrected reporting errors in session microservices jobs.
- Resolved an error in dashboards view: Object reference not set to an instance of an object6.
- Corrected an error when opening server and VCC role details caused by an incorrect path in the
ComplianceResultproperty. - Corrected the agent's
first send totalscalculation, which could reference an incorrect device. - Re-enabled
DisconnectandLogoffactions from Portal to work correctly. - Prevented overwriting all custom fields when a microservice updated only a subset of them.
- Mitigated potential CSV injection in exported data through prior value sanitization.
- Reduced delays in Wake on LAN (WoL) retries when using multiple intermediate devices.
- Corrected startup behavior in environments with different time zones to ensure proper scheduling and state.
- Flow messages use the language configured by the user.
- Corrected incorrect switch to not-reporting status for devices powered off the next day.
- Resolved empty log messages generated by compliance checks to ensure meaningful information in logs.
- Ensured correct order of events by ensuring
OperationsAuditreceives the job creation message before the device creation notification. - Corrected cases where a Wake on LAN (WoL) job ended in
Error, but the final device status was displayed asOn. - WoL scheduling now displays the intermediate device configured from the workspace or reporting group.
- Handled Wake on LAN (WoL) scheduling cases where no intermediate device is found to prevent unexpected failures.
- Ensured correct status update of associated devices from
in progresstocompletedwhen jobs finish correctly. - Corrected the visibility of the
Acceptbutton in the notification bar when the message exceeds the screen width. - Corrected titles of jobs for user flows and microservices executed by the universal agent.
- Jobs that automatically change reporting groups now correctly update device status upon completion.
- PatchOS jobs are now visible for the selected tenant and correctly displayed in Portal.
- Resolved an object reference error when forcing compliance checks.
- Scheduled microservices originated from Flows now include the target device in the created job.
- Normalized all date/time fields to UTC across the platform to ensure timestamp consistency (not limited to
emittedAt). - Corrected compliance filter to return accurate results.
- Scheduled jobs for flows and microservices now include an
Operation Namewhen created for future execution. - Restored correct management of Event Hub connection string for integrations with FXXOne.
- Reduced time needed to disable the alert
Multiple errors in event log. - Corrected
Select allbehavior to meet user expectations. - Corrected marking devices as completed in restart and forced restart jobs when they finish successfully.
- Managed absence of Chrome executable to prevent unhandled
System.IO.FileNotFoundExceptionerrors. - Improved FlexxAgent autostart to tolerate longer initialization times and prevent failures when startup is delayed.
- The
taskstatusAPI endpoint now returns expected fields even in jobs that finish with errors. - The job
Install Intel EMA agentnow correctly reports installation failures instead of ending asCompletewhen the agent is not installed. - Notification dates are now normalized and consistently displayed across the platform.
- Restored the visibility of the
ownerfield in the job list.
🔶 FlexxAgent Cross-Platform
⭐ New Flexxible agent
- FlexxAgent Cross-Platform version 26.1.501.196 is now available.
New Features
-
End-user microservices execution window.
-
Agent logs from Portal. Now the device detail view allows you to see which logs this agent has left during its installation.
-
Support for detection of UDS as broker.
Improvements
- Internal performance optimizations and reduction of resource consumption.
- General stability, resilience, and fault tolerance improvements.
- Inclusion of remote assistance type in reports.
- Extension of CustomFields support.
- Script reporting executed in microservices within Flows and end-user microservices.
- Optimization of the reporting system through sending differentials, reducing the volume of data sent.
- Improvement in error control and management in metric sending.
- Avoid domain calls when using local users in domain-joined workspaces.
- Blocking of agent update or restart operations during active remote assistance sessions.
- Inclusion of detailed log information for remote assistance sessions.
- Microservices with partial errors now correctly notify the operation as an error.
- Improvement in retrieval of user-directed notification translations.
- Optimization of pending patch queries.
- Automatic recovery of the previous agent configuration in case of corruption detection.
- Recovery of the agent from backup if the original executable has been deleted.
- Use of HTTP/2 in backend communications.
Bug fix
-
Incorrect information sending to backend during restart operations that could remain in Pending state resolved.
-
⚠️ Missing detailed list information in some operation responses.
-
⚠️ Notifications may remain visible to users after their defined end date.
-
Improved sorting of notifications by severity.
-
Corrected background color, blinking, and hand cursor type in notifications.
-
Added support for scheduled notifications.
-
Corrected a behavior where popup notifications did not always close automatically after 3 days.
-
Improved agent startup on devices with very limited resources.
-
Corrected incorrect hypervisor detection on AVD machines.
-
Resolved an issue where BIOS version could display an incorrect value.
-
Adjusted Wake on LAN data reporting for wireless networks.
-
Fixed duplicate logon time reporting.
-
Resolved an error when updating the agent while the executable was in use.
-
Fixed an issue where some antivirus appeared duplicated in Antivirus details and their version was not reported.
-
Adjusted the installer to generate a random temporary name.
-
Fixed the flow logging, which was not correctly deleted under certain situations.
-
Corrected an incorrect message when executing a flow successfully.
-
Resolved the behavior where the session agent could be blocked if the installation process took a long time.
-
Corrected a behavior where not all processes were closed on agent termination.
-
Solved an issue where Get All PnP Devices returned only devices with errors instead of all devices.
-
Resolved the reporting of the Product in the list of installed applications.
-
Fixed incorrect values in AfKTime and FocusTime under certain situations.
🔶 FlexxAgent
🎯 New version
- FlexxAgent version 26.2.1 is now available.
Improvements
- Ensuring mass reboot jobs do not leave devices in timeout state when the reboot completes correctly.
- For scheduled Wake on LAN (WoL) and shutdown operations, the workspace group's name is included for more context.
- Avoid using a VCC role as an intermediate machine in Wake on LAN operations.
- Ensure Wake on LAN (WoL) jobs finish with complete details of results and status information.
- Detection time for updates reduced from 10 to 2 minutes.
- Greater resilience on startup: a failure in a single subprocess doesn't impede the complete agent start.