Victor León

Hello, According to the official Microsoft Teams Hardware Requirements, the new Microsoft Teams Desktop Client is not supported on Windows 10 LTSC. Hardware requirements for Microsoft Teams - Microsoft Teams | Microsoft Learn

Hello, most likely the computer account was not created successfully in AD, or some other AD-related issue such as replication across the domain controllers. I am guessing the computer renaming logic for Instant Clones failed, and it kept the cp-template computer name.

Hello, not possible as there is a UPN validation during TrueSSO flow. If it asks for account, there won't be a real TrueSSO authentication. Disabling TrueSSO might be the way to go if you need to access the VDI desktop with a different AD credential.

Hello, The authentication via UAG will be through port 443 as follows. Regardless of having a certificate installed in the UAG or not. client> 443 > UAG > 443 > CS. So, yes 443 has to be open in the external firewall for incoming connection request. Once the user is authenticated the network flow for the session protocol is as follows in a default configuration scenario: client > 8443 > UAG > 22443 > VDI_desktop Just to confirm, you may want to try with this command.. perhaps you are just missing parameters. try: netstat -ano | findstr 443

Hello, If I recall correctly, the geolocation pop is due to the e911 feature on Microsoft Teams which tries to get the user location and needs to ask for user consent. I am not aware of any GPO to turn it off. You may want to try a few options for this scenario The user can turn off location sharing or can turn off the pop up from the client settings The admin can turn off e911 feature from teams admin console (can't test this myself)

Hello, There will be a dump file in the client log bundle. You can use WinDbg to review the file. Is the faulting module: C:\Windows\SYSTEM32\ntdll.dll ? We are working on a fix with above module coming with 2406.1

Hello, In Horizon Console, select Settings > Servers. On the Connection Servers tab, select a Connection Server instance and click Edit. On the General tab, select the Enable Host Redirection option.

Hello Try this as it might help. Stop the services in your CSs. Go to the location "<INSTALLDIR>\VMware\VMware View\Server\broker\webapps" in all non-working CS. Delete the rest folder. Restart the connection server. Refer to: https://docs.vmware.com/en/Management-Packs-for-vRealize-Operations-Manager/1.2.1/Horizon/GUID-670DC88E-4509-416C-8CD3-AB488C1423D0.html

Hello, You might be facing this issue, please check. https://kb.omnissa.com/s/article/94217

Hello, Yes, the packaging machine must be domain joined and an appropriate version of the App Volumes agent must be installed. Check in your AVM Admin UI if the VM shows up under Directory>Computers. If the machine is missing from the list, then it will not be available when you create the package. If its missing, make sure you can ping the virtual machine and resolve the DNS name of the VM. There must be a Computer Object in AD also.

Hello, It is built-in into flexengine.exe

Hello, For all those having issues with DEM not picking up settings when you install it in a Horizon Cloud Next-Gen environment, I hope this will help. IF you specify the config file path through the Horizon Universal Console, the DEM agent will run as if you installed it explicitly in No-AD mode. If you don't configure that, the agent is just installed, in a kind of "dormant" fashion. If you then apply config via GPO, it will pick that up. Then, we have 2 possible solutions. 1. Do not specify the config file path through the Horizon Universal console. 2. Install the DEM agent in the Golden Image. DEM Agent (FlexEngine) installation Walkthrough

Hello, As a workaround, you can import the certificate via MMC to the certificates 'Personal' store. Then, at last reboot the service 'VMware Horizon Security Gateway Component'. The friendly name of the new certificate must be 'vdm'. It must be lowercase. Also, you need to change the old certificate friendly name to something else. This KB might be helpful. https://kb.omnissa.com/s/article/2082408

Yes probably. You will have to check and confirm though.

Hello, GPO (Exclude specific kinds of files from being uploaded) will help to exclude Shortcuts from syncing to OneDrive. https://learn.microsoft.com/en-us/sharepoint/use-group-policy#exclude-specific-kinds-of-files-from-being-uploaded