Community
Headless remote PC
Links used in this discussion
Links used in this discussion
John Wood,
User (Posts: 6)
May 08, 2019 7:59:23 am EDT
Support level: Free or trial
RemoteUtilities v6.10. I'm trialling Remote Utilities using Internet-ID. Remote PC is running Win10.
With a screen connected, everything seems to run as expected, but I want to run the remote PC headless. When I remove the screen, all I see is a blank screen in the Viewer.
How do I set it up to see a (virtual ?) remote screen?
Thanks for any tips.
With a screen connected, everything seems to run as expected, but I want to run the remote PC headless. When I remove the screen, all I see is a blank screen in the Viewer.
How do I set it up to see a (virtual ?) remote screen?
Thanks for any tips.
Nijel Terry,
User (Posts: 55)
May 08, 2019 1:34:32 pm EDT
Support level: Pro
Did you try legacy capture mode & installing the monitor driver? https://www.remoteutilities.com/support/kb/full-control-and-view-mode-isn-t-working-or-is-unstable/
John Wood,
User (Posts: 6)
May 08, 2019 2:56:29 pm EDT
Support level: Free or trial
Thanks Nijel,
Installing the monitor driver seems to have done the trick. I did look at that earlier, but the install option wasn't available.
NB I also found that the host software didn't restart itself, so I had to restart it after changing the settings. That could only be done with direct access to the remote machine.
Cheers, John
Installing the monitor driver seems to have done the trick. I did look at that earlier, but the install option wasn't available.
NB I also found that the host software didn't restart itself, so I had to restart it after changing the settings. That could only be done with direct access to the remote machine.
Cheers, John
Nijel Terry,
User (Posts: 55)
May 09, 2019 11:15:07 pm EDT
Support level: Pro
Hi John,
I sometimes have the same issue when upgrading host's or changing host settings that require restarting the host. It varies from PC to PC & I haven't isolated the cause yet. I use two different remote programs as a precaution & make sure I'm logged in on my secondary program before doing any host upgrade or host restarts. In almost all cases rebooting the host computer will auto-start the host with Windows, if this is your only option I'd recommend scheduling a system restart in Task Scheduler to occur just after you upgrade or restart the host on remote machines.
I hope this helps.
Best,
Nijel
I sometimes have the same issue when upgrading host's or changing host settings that require restarting the host. It varies from PC to PC & I haven't isolated the cause yet. I use two different remote programs as a precaution & make sure I'm logged in on my secondary program before doing any host upgrade or host restarts. In almost all cases rebooting the host computer will auto-start the host with Windows, if this is your only option I'd recommend scheduling a system restart in Task Scheduler to occur just after you upgrade or restart the host on remote machines.
I hope this helps.
Best,
Nijel
Conrad Sallian,
Support (Posts: 3074)
May 10, 2019 11:42:03 am EDT
Hello,
Just wanted to add my two cents. Starting version 6.10.8.0 we improved the installation process for the Host (you may have noticed that - there's now .exe Host available and also the installation window changed a bit). The purpose of this improvement was to make sure that the Host service restarts guaranteed after the simple update instead of delegating this task to Windows msi which wasn't always reliable in this respect. So if you are updating from 6.10.8.0 to 6.10.9.0 you are already using the new process (unfortunately, it doesn't work retrospectively, i.e. updating from 6.10.5.0 and earlier to 6.10.9.0 won't trigger this mechanism).
Yet, even with that precaution made there may be situations when Host service may not start due to some reasons, such as a/v software activity or security policy (this is true about Windows Server especially). We cannot control these factors though, unfortunately, and it is up to the user/customer to take them into account.
Thanks.
Just wanted to add my two cents. Starting version 6.10.8.0 we improved the installation process for the Host (you may have noticed that - there's now .exe Host available and also the installation window changed a bit). The purpose of this improvement was to make sure that the Host service restarts guaranteed after the simple update instead of delegating this task to Windows msi which wasn't always reliable in this respect. So if you are updating from 6.10.8.0 to 6.10.9.0 you are already using the new process (unfortunately, it doesn't work retrospectively, i.e. updating from 6.10.5.0 and earlier to 6.10.9.0 won't trigger this mechanism).
Yet, even with that precaution made there may be situations when Host service may not start due to some reasons, such as a/v software activity or security policy (this is true about Windows Server especially). We cannot control these factors though, unfortunately, and it is up to the user/customer to take them into account.
Thanks.
* Website time zone: America/New_York (UTC -5)