Thanks for your responses, this has been very helpful. I need to push out the 22.214.171.124 update anyway, so I'll just configure it appropriately.
Right now with the host on version 6.6.07 I verified on a test machine that the cached files are replaced for each successive print to the virtual printer. However, after restarting the Remote Utilities Host service the files were still in the common folder. The same with rebooting the computer - files are still present after reboot.
In my case we don't really use the remote printing functionality, so removing the printer will be my solution. This is not really a common scenario anyway, but just thought you should know that it wasn't working here on this version the way you described.
Great software, BTW, and it is also appreciated how responsive your team is on these forums.
Quick question: For some reason on a bunch of computers Windows set the RU printer as default. Some people went to print some confidential documents and when they didn't print they noticed they had printed to the Remote Utilities printer. They are now concerned about what happened to those documents. So what does happen in this case - are they just gone (hopefully) or are they waiting somewhere for someone to remote in to the computer at which time they will print out on the viewer's default printer?
On the first computer it did not have the monitor driver. I tried to do a remote install again but got an error that the install failed. Tried to to remove Remote Utilities manually to try again but Windows 10 crashed. I'm getting a lot of Windows errors (not blaming RU, this machine was a little unstable to start with).
Tried on a second computer with a new Windows 10 install which also had some basics software installed - Office 2013, Flash, Firefox and RU 6.3. After doing a remote install to upgrade this machine, it had a message on it saying "installing device" for about 20 minutes with no movement on the progress bar.
I got impatient and rebooted. After rebooting I received some messages on the screen stating: WIndows cannot find 'igfxEM.exe' and ‘igfxHK.exe’. I don’t know if installing the monitor driver is affecting these files. Rebooting again did not reproduce those errors, but the monitor driver is still not there and the “blank Screen” does not work still.
I tried to install 6.508 manually on that computer. First it said I needed to reboot, which I did. Then the install continued after I logged back in, but I received an error 2753 that RUserv.exe is not marked for installation.
I’m not seeing RU in Windows Programs and Features to remove, so at the moment I can neither remove nor install Remote Utilities.
I’m out of here for today – will pick this up in the morning and see what I can do.
Just testing 6.5 on Windows 10. I see one of the improvements on 6.5 is that locking the screen and input (clicking the padlock on the viewer screen when connected to a host) is now supposed to work on Windows 10 hosts. I am testing this on one computer that had the 6.3 host installed. I did a remote install to upgrade it to 6.5 and rebooted it. I did not see, as mentioned in the release notes for 6.5, anywhere to accept an additional driver.
Now when using this feature it seems to just do nothing (which is better than before when it would lock the remote computer).
I notice that when I try to enable the screen lock on a Windows 10 remote computer, while it does disable the remote screen and KB and mouse inputs at the remote computer, but it also locks it. On the RU Viewer I can enter a password to log back into the remote computer, but it immediately locks the computer again.
It also does not show the text for blank screen on the remote PC.
Version 126.96.36.199 on both ends, Windows 10 Pro both ends. Is this a known bug?