SchwarzC
-
Posts
96 -
Joined
-
Last visited
SchwarzC's Achievements
-
Dear mlindgren1, did the 2312.1 upgrade fix this issue for you? BR
-
We actually found the culprit of this issue, in one of our AppStacks (App Volume) a different WebView2 seems to have installed itself, while we did an upgrade and went unnoticed, New Teams didn't like that. After repackaging all went back to normal.
-
Dear Stephen, first of all thank you for your answer and for your online materials, helped me a lot in the transition to 365. I am suspecting similar, I will first try with 16.8 and afterwards v17 For the driver we have the following (SVGA 3D disabled) For the clients, we only have one version that is 8.12.0.43490 but I will start with upgrade to the latest 8.13
-
Whats interesting is that we have similar setups, but different versions of our backend, only the Win 10 22H2 is the same, so it could be the culprit let me know if you have found out anything, I will do the same. My current plan is NV upgrade to 16.8 Horizon upgrade to 2312.1 Reinstall all agents with the latest version agents what is really strange is that we have not seen this problem once in our test group, but with some random users the problem has occurred more often, and we have a default config for all
-
We left everything on default So Allow BlastCodec Decoding Allow H.264 Decoding ALlow HEVC Decoding Allow AV1 Decoding On the VDI we see the following (HEVC 4:2:0)
-
Hello everyone, We've had reports from several users that the UI in Excel and other Office apps like Outlook isn't rendering properly. I've attached a screenshot so you can get an idea of what we're seeing. I suspect this might be related to hardware acceleration, as we're using NVIDIA GPUs in our environment. Here's a quick overview of our setup: Horizon 8 2212.2 Windows 10 22H2 (September patches applied) FSLogix (latest version) AppVolume 2406 DEM 2406 NVIDIA A16/NVIDIA A2 GPUs Shared Direct and Shared Passthrough GPU assignment policies VMs spread across GPUs for best performance Latest NVIDIA drivers (16.7) on Hosts and 538.67 on Windows BLAST only with Windows Devices as our underlying OS Interestingly, this issue isn't affecting all users—just a few here and there. Has anyone else experienced something similar, especially in environments with shared GPUs? Any tips or known fixes would be greatly appreciated! Thanks in advance!
-
Hello everyone, I'm encountering an issue with Microsoft Teams where the application randomly hangs at unpredictable intervals. The only way to resolve it is to quit the app and restart it. I have already used the "Report a Bug" feature in Teams, and we are running the latest version of the app. Teams is installed on the Golden Image with the correct switch and was working well for the last months, it started happening for one user and now more and more users are affected. Our current setup: Windows 10 22H2 (September patches applied) FSLogix (latest version) AppVolume (latest version) DEM (latest version) no Azure PRT Has anyone experienced similar issues, and if so, were there any solutions or workarounds you found helpful? Any advice would be greatly appreciated! Thank you in advance!
-
Hi Kristina, Thank you for the clarification! I appreciate the explanation. However, I noticed a slight discrepancy between the release notes and your response. My goal is to have users log in via Windows Hello for Business (WHFB) and then be automatically authenticated through the "Log In as Current User" feature to their Horizon Desktop. Based on the release notes, I thought this would work even with WHFB. Could the difference in how WHFB handles session tokens or credentials compared to a password-based login impact the auto-authentication with Horizon? (Please note that all devices are hybrid joined.) or am I complety on the wrong track here. Thank you!
-
Good day, This is my first post in the new forum, and I’m liking it so far! 😊 In the release notes for Horizon Client 2406, I noticed the following: Enhancement to Log In as Current User A new GPO on the client allows administrators to turn off support for Hello for Business while keeping the Log In as Current User feature operational. Could someone please confirm if this means the following? Instead of implementing Windows Hello Cert Trust (we are currently in the middle of this and it’s becoming quite challenging), can we implement Windows Hello for Business with Cloud Kerberos without causing interference with the Log In as Current User feature? For context, our setup allows internal users to log in as the current user. Does this require upgrading the back-end (Connection Servers) to version 2406 as well, or is it sufficient to upgrade just the clients? (We need to wait for Nvidia compatibility before upgrading the servers.) Thank you for your assistance!
.png.fca6171f848beb4e434645903a743380.png)