PDQ Deploy to Microsoft Windows 10 Enterprise for Virtual Desktops

PDQ Deploy apparently doesn't recognize some of my desktop VMs as being Windows 10. Specifically, these are VMs used for Windows Virtual Desktop in Azure. They are fairly standard Windows 10 machines, Release 1909. PDQ Inventory shows them with O/S "10", Name "Windows 10 Enterprise for Virtual Desktops".

When I set the O/S Version condition to All Versions, apps deploy just fine, like any other machine. But if I change the conditions to limit O/S Version to Windows 10, these machines fail with "Not run due to Operating System condition" leading me to believe that something in Enterprise for Virtual Desktops is throwing it off.

Not a showstopper, as the workaround is to eliminate the condition, but it would be nice to have them included.

 

Thanks!

 

0

Comments

4 comments
Date Votes
  • Hi Corey, I'll suggest to get in touch with the support guys. There might be a bug.

    0
  • Did you ever find a solution to this?

    0
  • No, I didn't, and I never did get around to asking Support. Like I said, I can work around it, but it would be nice if modifications could be made to recognize "Windows 10 Enterprise for Virtual Desktops" as Windows 10.

    0
  • I know this is kind of an old thread but I ran into this when trying to patch some pooled AVD machines in my environment. I opened a ticket with PDQ support. I did find a work-around though - clone the Windows 10 update package and change the OS condition from Windows 10 to Windows Server 2019.

    Although PDQ Inventory sees "Windows 10 Enterprise for Virtual Desktops" as the OS name, PDQ Deploy considers it a Server 2019 OS. The reason for this is explained in this Microsoft doc: https://docs.microsoft.com/en-us/azure/virtual-desktop/windows-10-multisession-faq#why-does-my-application-report-windows-10-enterprise-multi-session-as-a-server-operating-system 

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post