☐Navigate to Windows Settings > Update & Security > Troubleshoot > Windows Update, and select Run the Troubleshooter. Use these steps to identify why a Windows update failed to push to devices. Troubleshooting Dell Command | Monitor (BIOS Profile).Quick Tips for Dell Client Command Suite.Troubleshooting Dell Client Command Suite.Troubleshooting Workspace ONE AirLift Installation.
Verifying Workspace ONE UEM Sent the Correct Windows 10 Updates.Running the Windows Update Troubleshooter.Improving Performance with Content Delivery Network (CDN) Integration.Troubleshooting Windows 10 Peer to Peer Networks.Troubleshooting Applications Using Registry Keys and Event Viewer.Troubleshooting Application Sideloading.Troubleshooting MSI Apps Using EnterpriseDesktopAppManagement CSP.Group Policy (GPO) & MDM Policy (CSPs) Processing & Precedence.Troubleshooting Policies, GPOs, and Baselines.Understand and Troubleshoot Custom Settings Profiles.Using Event Viewer to Check Workspace ONE UEM Profile Settings.Using Fiddler to Validate Workspace ONE UEM Profiles.Troubleshooting Windows 10 Profiles in Workspace ONE UEM.
Troubleshooting Windows 10 Native OMA-DM (Access Work or School) Enrollments.
Logs are full of nonsense and the fix really is just as easy as restarting the service or server. At this point in time, I'm not sure where else to look. My initial theory was the EOL of flash as the first chunk of reports we got were running Horizon 7.9 or earlier which still use flash until we started getting reports of 7.11-8.0 having the same issue which more or less ruled that out as the cause. For reference, I have seen this happen with Horizon versions ranging from 7.5-8.0(2006). We use to get MAYBE 1 or 2 of these per week but since yesterday I have had at least 15-20 tickets about this same issue if not more. Has anyone else who uses VMware Horizon been getting a lot of "this desktop currently has no desktop resources available"? I know the fix is simply restarting the VMBlast service or the Terminal Server entirely since the main issue appears to be loss of communication in one way or another with the connection server and either of those actions will, in essence, re-establish communication with the Connection server, but that's pretty inconvenient, and "you just have to reboot it" does not sound too good to clients when they call asking for support.