Conrad et al, Its a bit unclear as to the recommended sequence and timing for upgrading all components. Normal recommendation is to upgrade viewers and servers first, then upgrade hosts. But.... 1. it it takes several days to upgrade all hosts, will the V7 viewer provide effective access to V6.10 hosts in the interim ? 2. Since your recommendation is also to do "staged" host upgrades question 1 also applies... 3. has any testing been done in regards pushing msi-host updates via Azure/End-Pointmanager(Intune)
I also don;t see any indication sin the release notes, but has there been any changes that could have positive impact on accessing active laptops with closed lids ? currently, using legacy-mode "sometimes" works, but not always....
A bit more information for everyone. I suspect this also may be related to specific video drivers/cards. Our own environment encompasses several different make/models of PC. All are running the same version of Win10 and RemoteUtilities. The behavior is not consistent across different PC model/makes. We see this behavior on all our older Dell 5xxx series, but not on any of our slightly newer 6xxx series Dells. Our newer HPs seem fine as do most of our Asus PC's. Hence my suspicion that it is something related into some video drivers/cards.
Interestingly, it seems to be associated to the host. If I change the display scaling to 199% on the viewer, but leave the host at 150%, the cursor artifact remains. so it would seem that it is the host that is sending the "block" to the viewer.
Hi Conrad. It happens in just about any app that has text entry ( Word, Edge, IE, Excel). No changes to default Win10 cursor or display properties. I'm doing some further checking as I think it may be associated with default Win10 display scaling as the host I see it on is a new laptop which Windows defaults to 150% scaling because of the screen resolution. In this case the host and viewer are identical with the same default 150% screen scaling.
I definitely has to do with the win10 default display scaling... If I change the display scaling to 100% on the host the artifact disappears. changing host display back to the default 150% displays the cursor as the uploaded image
running 184.108.40.206 viewer and host on win 10 . Whenever the cursor is positioned to an inputtable field in the host window the cursor changes to a large black block and "ins ert" icon.. quite distracting though it does not seem to affect functionality. I saw this same behavior was observed in 220.127.116.11
Its almost like the text insert icon is se t on a black background..
Is there any specific reason that the remote screen response is significantly slower with Windows 10. I was hoping that the Beta would help improve the response time. It is particularily noticeable on any type of Win10 "system" screen/dialogs such as the login or lock screens. For example, It fairly consistently takes 20-30 seconds for the lock screen to respond to a mouse click or enter key. Once your in an application( e.g. MSWord) it seems to get better, but response is still a little more laggy than Win7 was. We're seeing this on multiple hosts and clients, even when accessing on fullspeed cable internet. We're running via internet-id using the free id server. We've already hit the common spots by dropping the color depth to 8 bits, and turning off Aero, and removing wallpaper. Its almost like Win10 does some type of "mode switch" when display system dialogs that causes huge delay.. Anyone else seeing this type of performance anomally or have further suggestions?