m1k3yr's Posts

Just upgraded from 7.13 to 2212.1 and seeing the same message. F5 in front of connection servers. Environment seems to be working fine. We have 3 pods.  First Pod is for testing and digital signage and I don't have those messages.  Second Pod is for production use and is seeing the messages.  I have not updated the third Pod yet as it is the other production pod.   

Did you ever get an answer on this?  I have a similar problem where it appears that some of the machines do a dhcp release but not all.  Seems to have started back in January?  Maybe sooner.  We just went to 7.13.1 and we are also running Windows 10 20H2.   We have tried all kinds of work arounds but bottom line is that the VDI machines are not releasing during shutdown, DHCP does not release IP, and does not update DNS.  New machines are built but have the old DNS record so IP is wrong.    

Wow, we have been going around in circles on this one.  Only thing we could do was to roll back our images a few months and avoid doing windows updates. We are using Windows 10 20H2, AppVol 2.18.0, Horizon View 7.13.1. In additional to Print-To-PDF not working, we also observed USB label printers quit working. I did notice that in the base images, prior to being deployed, PDF printing worked.  I was thinking it was a particular AppVol and was going to have to narrow it down to which one(s) was causing the issue.   Thank you all for posting about this.

We will be testing Imprivata with App Volumes soon but our Production VDI was built with Unidesk and Imprivata is usually not a problem.  It does have a few oddities with RFID readers and needing to detect VMware Horizon View Agent during install but that's all been documented and once the layer was built, its built.  Nothing else needed to be done and it behaves like any layered app would.  We've built batch files which automated the Imprivata install setup so when a new Imprivata Hotfix comes out, we build a new layer, run the batch file install we wrote, and we're done.  Upgrading the 1800+ VDI clients is just a un-check here and a new check there.  Next maint cycle and they all come up with the hotfix version installed and the old version gone! The trick could be that Imprivata (now this is older versions before 5.0 but I think it still holds true today) needs to see the VMware View Agent during install or else it doesn't install the little bits needed to pass creds though the different login screens correctly.  So if I understand App Volumes correctly, you need to make something where the Vmware Agent and the Imprivata can see each other during the Imprivata install.  There are several ways to do this in Unidesk but not 100% sure on App Volumes.  And since Imprivata makes changes to some Windows OS files, not sure how that would work exactly in App Volumes either.  We are testing the waters to see if anything has changed since we started VDI with Unidesk a few years ago.  Still just setting up the test environment for App Volumes. Lastly, you may have to get with your VMware sales rep to get after Imprivata.  We had a small problem (just a registry key for the RFID readers) at the beginning and we could not figure it out.  Imprivata had a few old docs on the issue but still wasn't much help.  Our Vmware got with a higher VMware rep, who got with a higher Imprivata rep, who figured it out.  FYI, we are running Vsphere 6.01?, View 6.02, Unidesk 2.9.4, Imprivata 5.1.207.48, 1800+ VDI machines, Teradici2 zero clients, RFIDeas readers. Mike