Setting this parameter to FALSE will cause an unquantifiable percentage of cloud connections to fail. Note that session data relayed via our cloud service is encrypted end-to-end, so cannot be deciphered by RealVNC, nor anyone else. However, intermediate network hardware may mean this is not possible, so the cloud service automatically falls back to relaying session data this ensures cloud connections succeed.
Where possible, the cloud service then negotiates peer-to-peer sessions between endpoints, so session data is transmitted directly between them this is likely to be more performant. The physical display adapter in the agent machine will be used instead.Specify FALSE to prevent cloud connections to the VNC Server computer if they would be relayed via RealVNC’s cloud service.Īll cloud connections are brokered by RealVNC’s cloud service. With the config file in place, KRC sessions to the agent will not use the Mirage driver. Resolutionĭisable the Mirage driver using the following steps: -ġ) download the attached file - KaseyaRemoteControlHost.zip - and extract nfigĢ) copy to the Kaseya agent installation directory on the agent machine in question - usually C:\Program Files (x86)\Kaseya\ The Mirage driver is a 3rd party "mirror driver" (or virtual display driver) used by default on agents running Windows Vista/2008 or earlier operating systems for performance optimization, but some applications do not work correctly with such drivers. There may be a conflict between the 3rd party application and the "Mirage driver" used by KRC. When remote controlling an agent with Windows Vista/2008 or earlier operating systems, a specific 3rd party application does not display correctly in the remote session. 3rd party application on older Windows OS does not display correctly in KRC session
0 kommentar(er)
