u/Jealous_Tennis7718

Two HP DL560 Gen10 hosts running Hyper-V, Citrix VDI on top. We bought a T4 per host to test GPU acceleration and the idea was to split each card over multiple VMs, 4 or 8 or whatever it can handle. Later (in two to three years) we'll upgrade our environment to new servers.

Then I went to install it and got stuck (bad investigation? who can say but fugg me). The vGPU package has no host driver for Windows Server at all, the Host_Drivers folder is ESXi and KVM stuff only? So am I supposed to run the guest driver installer on the Hyper-V host itself, or is there a separate download I'm not finding? And where do you even get the right files, is that the licensing portal only? It seems that licensing portal is not complete for Hyper-V.

From what I can find in the docs Hyper-V never supported normal vGPU, and GPU-P on Server 2025 doesn't list the T4 as supported. Which would mean DDA, whole card to one VM, is the only thing we get. Fine if that's true, I just want to be sure before I go back to my boss with it.

If DDA is the answer, is dropping the T4 into one multi session VDA and letting everyone share it inside that VM a reasonable setup, or does that fall over in practice?

Hyper-V is staying, so no ESXi suggestions please.

Since this morning, Outlook has started crashing whenever we try to copy something using the right-click context menu.

I’m seeing this on my local machine, but it’s also happening in our Citrix environment. A few colleagues are affected so far, and I’m worried more users may start running into the same issue.

The strangest part is that it happens both locally and in Citrix, which makes me wonder if this could be related to a recent Microsoft/Office update rather than something specific to our environment. Also in safe mode (outlook.exe /safe) this exact issue happens.

Has anyone else seen Outlook crashing when using right-click copy today or earlier? Any known workarounds or recent updates that might be causing this?

Hi all,

I’m running into a strange issue in a Citrix DaaS / MCS environment and I’m hoping someone has seen this before.

When I boot a newly provisioned VDA, the machine shows up correctly in Citrix DaaS and appears to be up to date. However, once a user logs in, all application shortcuts in the Windows Start Menu show with a red background and a white X, as if the applications are unavailable.

https://preview.redd.it/oruh09t6tg3h1.png?width=331&format=png&auto=webp&s=bceaa5ec6c0c39d6280dd63c0458245ea7753156

The weird part is that the applications themselves launch without any issue. So functionally everything works, but every app icon in the Start Menu looks like it is unavailable or broken.

Example: the Command Prompt shortcut shows the red X overlay, but launching Command Prompt works fine.

What I have tried so far:

• Cleared the local WEM agent cache / local database
• Refreshed the WEM agent cache
• Rebooted the VDAs
• Re-provisioned the machines from the image through MCS
• Manually refreshed the WEM agent from within the user session
• Checked that the VDA is visible and healthy in Citrix DaaS

None of this changes the behavior. The icons remain the same after rebooting, refreshing, or reimaging the machines.

This happens for every application, not just one specific shortcut. The applications are present and accessible, but the Start Menu icons keep showing as unavailable.

Has anyone seen this before in a Citrix DaaS / MCS / WEM setup?

I’m especially wondering if this could be related to:

• WEM application existence checks
• Start Menu shortcut processing
• Icon cache corruption
• Agent cache synchronization
• Something being captured or left behind in the MCS master image
• A profile or Start Menu cache issue

Any pointers on where to look next would be appreciated.