Ofir Dalal

Thank you, Cliff. I'll test PostgreSQL on a Linux system in a lab environment. Regarding ticket creation, the system didn't allow opening a ticket with a customer account. Yesterday, there was a problem with the Issue Type field in the drop-down menu being empty, and it's a required field. I'll check again with the customer to see if it's resolved. Do you know if the Horizon Session Recording Server will also support PostgreSQL on Windows environments? Unfortunately, the customer wants PostgreSQL to run only on a Windows system.

Hi everyone, I set up a Horizon Session Recording lab environment and transferred the database to PostgreSQL version 16.4. Once I finished the process, the application started writing to the DB, but I got the following error. When I checked the log file, this is the error I received during the save configuration: at Horizon.Recording.WebAPI.Controllers.SecureControllers.SetupController.Post(SetupConfiguration value) in C:\actions-runner\_work\HorizonRecording\HorizonRecording\Horizon.Recording.WebAPI\Controllers\SecureControllers\SetupController.cs:line 252| 2024-09-11 18:23:50.1645|ERROR|Horizon.Recording.WebAPI.Controllers.SecureControllers.SetupController|Failed to migrate machines to destination database: Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> System.InvalidCastException: Cannot write DateTime with Kind=Unspecified to PostgreSQL type 'timestamp with time zone', only UTC is supported. Note that it's not possible to mix DateTimes with different Kinds in an array/range. See the Npgsql.EnableLegacyTimestampBehavior AppContext switch to enable legacy behavior. at Npgsql.Internal.TypeHandlers.DateTimeHandlers.TimestampTzHandler.ValidateAndGetLength(DateTime value, NpgsqlParameter parameter) at Npgsql.Internal.TypeHandlers.DateTimeHandlers.TimestampTzHandler.ValidateObjectAndGetLength(Object value, NpgsqlLengthCache& lengthCache, NpgsqlParameter parameter) It seems to be an application error. I'm attaching info from the Postgres documents. - https://www.npgsql.org/doc/types/datetime.html The Omnissa documentation doesn’t have a compatibility matrix for supported database versions. I can’t reach support. Can this information be passed on to the relevant parties?

Does anyone know why the new version 24.03 of Intelligent Hub for Linux is only available for AMD/ARM processors and not for x86_64 architecture? See screenshots. 23.10: 24.03(x86_64 architecture is not available)

Hi, Running the command to check order of svdriver: fltmc instances -v c: If FSLogix(frxdrvvt) filter driver priority is before App Volume Agent(svderiver), please modify the Horizon Golden Image using an admin command prompt to run the following command: reg add "HKLM\SYSTEM\CurrentControlSet\services\svdriver\Instances\App Volumes Instance" /v Altitude /d "132000" /f Take a new snapshot of the Golden Image following best practices and publish it to a test pool for testing. The workaround, lower the svdriver altitude below frxdrvvt.

Hello Ninjas! Have you encountered the behavior where the Teams Outlook add-in only appears after Teams is opened? If the user opens Outlook before Teams is launched and authenticated via SSO, the plugin does load when Outlook is opened. However, it is not available when trying to schedule a meeting in Outlook while Teams is authenticating. If the user then closes Outlook and reopens it, the button for scheduling a Teams meeting appears. Environment details: Non-persistent Windows 10 22H2 VMware DEM Microsoft 365 FSLogix ODFC version 2210 (update 4) Does anyone have any ideas on how to overcome this behavior?

It sounds like you are experiencing the issue mentioned in the following KB article: https://kb.omnissa.com/s/article/97169?lang=en_US Please check if this is the case for you and apply the workaround if necessary.