#PINGPLOTTER OLDER VERSION FULL#
#PINGPLOTTER OLDER VERSION SOFTWARE#
#PINGPLOTTER OLDER VERSION WINDOWS#

#PINGPLOTTER OLDER VERSION FULL#

The window with information regarding exiting full screen mode (attached), is visible - but not active. When we log into a full desktop for the first time, we get the usual prompts about USB redirection / Local folder access and so on (these haven't been supressed by GPO yet, on the current state of the PC's) - we also get the information window regarding exiting full screen mode. We have begun deploying 4.3.100 on a small scale, and on new PC's with clean installations of Windows, and no previous Receiver version, we see the following quite often: But not on VM's with another golding image, running on the exact same hosts, in the same AD OU and so on.Īny feedback, even 'you're a moron if you haven't tried this:' - I'll take anything :) So, basicly - I get short screen freezing on my VDA, and actual packet loss when pinging the VM at the same time. This led us to try out a different Xentools version, but alas no change was seen. Looking at the Xenservers running the VM, the packet loss matched a high CPU load on one of the VM cores. If I don't put any user load on the new golden image, I can still see small 'spikes' via Pingplotter with 50-100ms delay that aren't there, with a fully loaded server running the healthy image.

#PINGPLOTTER OLDER VERSION SOFTWARE#

This image has been thru a couple of versions over the last six months, and so its a bit difficult for me to replicate it 100% - although, I doubt that we are faced with a situation where only the magic combination of software works. Even a bone stock W2016 with the bare minimum of software needed: VDA, PVS - has the same issues.īut - the image that we currently have in production is working just peacy. Nothing definitive seems to make a difference.

#PINGPLOTTER OLDER VERSION WINDOWS#

Windows 2016: Clean from ISO, and varying levels of cumulative updates.Ĭlient software has been tried also, Receiver 4.9, 4.11, 1808 - HDX 2.3, 2.6 - all same result. Xentools: Three different version spanning 7.1, 7.1CU and latest as of a few weeks ago I've tried more of less every thinkable combination of: The MDT process is locked down pretty well, so there really isn't any difference in how the master images are prepared. And it doesn't take much more than 2-3 users for this to be noticable. In this period the VDA doesn't even respond to ping - and users that are logged in also notice that the HDX realtime connector status displays 'connected' when the screen freeze is done - kind of like the server looses all connection to the outside world.ĭepending on the amount of users, this can go from slightly annoying to absolutely unbearable. This is the same across several physical hosts. Short story long: whenever I try to create a new golden image using MDT, and implement this via our PVS, I end up with a VDA that - when 'pushed' - experiences short hang/freeze moments, upto 1-2 seconds.

Hope everyone is slowly gearing down for the holidays :)īut before doing so, I'm being taunted by our Xenapp environment at the moment, and could use the help of some fresh minds.

Pingplotter older version