(unless the remote box has restarted and you haven't logged into it in person)
Does this include boxes that auto start into a user account? I have some Boinc only machines and have set all of them to auto logon to an account that then crunches, would Team Viewer work in those cases? Would each pc have to use the same account name? I use UltraVNC now but have to use a password for each pc when I log in from another pc. It isn't hard or anything like that, in fact it's pretty easy, but I cannot log in from outside my home network. That is probably a user setting that I haven't found yet though.
Some VNC solutions allow you to save the password for each computer in a configuration file, so you can launch the viewer and log on to the remote with a single double-click (or single click from the quick launch bar). I have TightVNC set up to do that - if you trust the physical security of the viewer machine, of course.
As to logging in from outside the home network, that's probably more a case of opening the appropriate port in your router's firewall, and forwarding it to the machine you're most likely to want to control remotely. Or several ports, if you want to access multiple machines. Again, think through the security implications before you do that.
There are solutions which allow you access to the entire home network, but your typical home/SoHo router probably doesn't support them. For many years, I specified Draytek/Vigor routers for my business clients: they allow you to create a VPN connection to the router itself, without exposing even one port to the outside world for pass-through. That seems to be a pretty robust solution.
(unless the remote box has restarted and you haven't logged into it in person)
Does this include boxes that auto start into a user account? I have some Boinc only machines and have set all of them to auto logon to an account that then crunches, would Team Viewer work in those cases? Would each pc have to use the same account name? I use UltraVNC now but have to use a password for each pc when I log in from another pc. It isn't hard or anything like that, in fact it's pretty easy, but I cannot log in from outside my home network. That is probably a user setting that I haven't found yet though.
I suppose not, but I don't have any set up that way. On my Win7 box, Boinc starts at Windows start, even before I log in, but it doesn't find the GPU until I exit Boinc Manager and restart it. The XP box doesn't have that problem; I don't know why.
When I'm using one of my own computers to remote into another with Teamviewer, I just double click the Teamviewer app icon on my desktop. It opens up and communicates with their server, then gives me a list of all my computers that are set up to be remoted into. I double click one of those and I'm in; if it has restarted and I haven't logged into it in person, I have to enter its password, otherwise I don't. If I'm using Teamviewer web access (from work), I have to use my username and password to get into the site, but from that point its the same as using the app.
When you first set up Teamviewer on a host, it will give you a machine ID and (I think) a password, but after you get it fully set up you won't need those any more.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
(unless the remote box has restarted and you haven't logged into it in person)
Does this include boxes that auto start into a user account? I have some Boinc only machines and have set all of them to auto logon to an account that then crunches, would Team Viewer work in those cases? Would each pc have to use the same account name? I use UltraVNC now but have to use a password for each pc when I log in from another pc. It isn't hard or anything like that, in fact it's pretty easy, but I cannot log in from outside my home network. That is probably a user setting that I haven't found yet though.
I suppose not, but I don't have any set up that way. On my Win7 box, Boinc starts at Windows start, even before I log in, but it doesn't find the GPU until I exit Boinc Manager and restart it. The XP box doesn't have that problem; I don't know why.
When I'm using one of my own computers to remote into another with Teamviewer, I just double click the Teamviewer app icon on my desktop. It opens up and communicates with their server, then gives me a list of all my computers that are set up to be remoted into. I double click one of those and I'm in; if it has restarted and I haven't logged into it in person, I have to enter its password, otherwise I don't. If I'm using Teamviewer web access (from work), I have to use my username and password to get into the site, but from that point its the same as using the app.
When you first set up Teamviewer on a host, it will give you a machine ID and (I think) a password, but after you get it fully set up you won't need those any more.
Yes, a web-based solution like that, with an intermediate server, removes the need to configure an open port in the router. But that leaves you reliant on the continued provision of the centralised service - and as we just saw with logmein, that can be withdrawn or have its conditions of service changed without notice. And you have to trust the service provider's security...
Solutions like VNC use point-to-point protocols, with no central third-party provider. That makes them harder to set up, but - it might be argued - more resilient, especially within a home network.
(unless the remote box has restarted and you haven't logged into it in person)
Does this include boxes that auto start into a user account? I have some Boinc only machines and have set all of them to auto logon to an account that then crunches, would Team Viewer work in those cases? Would each pc have to use the same account name? I use UltraVNC now but have to use a password for each pc when I log in from another pc. It isn't hard or anything like that, in fact it's pretty easy, but I cannot log in from outside my home network. That is probably a user setting that I haven't found yet though.
I suppose not, but I don't have any set up that way. On my Win7 box, Boinc starts at Windows start, even before I log in, but it doesn't find the GPU until I exit Boinc Manager and restart it. The XP box doesn't have that problem; I don't know why.
When I'm using one of my own computers to remote into another with Teamviewer, I just double click the Teamviewer app icon on my desktop. It opens up and communicates with their server, then gives me a list of all my computers that are set up to be remoted into. I double click one of those and I'm in; if it has restarted and I haven't logged into it in person, I have to enter its password, otherwise I don't. If I'm using Teamviewer web access (from work), I have to use my username and password to get into the site, but from that point its the same as using the app.
When you first set up Teamviewer on a host, it will give you a machine ID and (I think) a password, but after you get it fully set up you won't need those any more.
Yes, a web-based solution like that, with an intermediate server, removes the need to configure an open port in the router. But that leaves you reliant on the continued provision of the centralised service - and as we just saw with logmein, that can be withdrawn or have its conditions of service changed without notice. And you have to trust the service provider's security...
Solutions like VNC use point-to-point protocols, with no central third-party provider. That makes them harder to set up, but - it might be argued - more resilient, especially within a home network.
On my Win7 box, Boinc starts at Windows start, even before I log in, but it doesn't find the GPU until I exit Boinc Manager and restart it.
BOINC can only start prior to Windows login if you have it installed as a service, and when you do that, BOINC will not find the GPU because of separate sessions running the drivers and the Windows user account.
If you didn't install BOINC as a service, your BOINC will not start prior to you logging in. You will first have to log in, and only then will BOINC be one of the user-installed programs that's going to run. That a GPU cannot be found at such a stage may be due to BOINC loading way earlier than the full desktop videocard drivers. That depends on how much Windows has to load at login, how fast the hard drive is that everything needs to be read off of, how much fragmentation is going on on that drive, how much memory you have, how fast this memory is, how big the Windows swap file is, and really a whole myriad of other things, including how busy the CPU is when it (also) needs to load all that stuff.
BOINC is one of the things that can load and start reasonably quickly, earlier mostly than e.g. the AMD Catalyst Control Center. As soon as BOINC loads up the CPUs, everything else that still needs to load will have to wait, despite BOINC apps running at low priority. They still need to load, and may take up memory that is needed to load other programs.
On my Win7 box, Boinc starts at Windows start, even before I log in, but it doesn't find the GPU until I exit Boinc Manager and restart it.
BOINC can only start prior to Windows login if you have it installed as a service, and when you do that, BOINC will not find the GPU because of separate sessions running the drivers and the Windows user account.
If you didn't install BOINC as a service, your BOINC will not start prior to you logging in. You will first have to log in, and only then will BOINC be one of the user-installed programs that's going to run. That a GPU cannot be found at such a stage may be due to BOINC loading way earlier than the full desktop videocard drivers. That depends on how much Windows has to load at login, how fast the hard drive is that everything needs to be read off of, how much fragmentation is going on on that drive, how much memory you have, how fast this memory is, how big the Windows swap file is, and really a whole myriad of other things, including how busy the CPU is when it (also) needs to load all that stuff.
BOINC is one of the things that can load and start reasonably quickly, earlier mostly than e.g. the AMD Catalyst Control Center. As soon as BOINC loads up the CPUs, everything else that still needs to load will have to wait, despite BOINC apps running at low priority. They still need to load, and may take up memory that is needed to load other programs.
I'm using WinPatrol, which isn't too difficult to use. It also allows for switches on the program. So in the case here, where I start boinc.exe, I can add --detach_console as parameters and that'll start the client and close the command line window.
Then when boincmgr.exe starts 2 minutes later, I have set as parameters /a /s, to tell that the client started already and that the manager can go to the system tray.
Regarding the problem with remote desktop stopping GPU tasks, I was wondering if the explanation still applies, at least under Windows 10. The reason why I ask this is:
1. Often the tasks continue crunching for about 1 minute after starting the remote desktop session before the tasks revert to the "GPU missing, waiting to run" status. If I correctly understand the explanation given, I would imagine the GPU would disappear the moment the remote desktop session is established and the tasks would instantly stop.
2. The Windows 10 Task Manager shows other tasks (such as Google Chrome) continuing to use the GPU even during the remote desktop session. (Or what does it mean when the "Processes" tab shows GPU activity and stuff like "GPU 0 - 3D" in the "GPU Engine" column?)
RE: RE: (unless the
)
Some VNC solutions allow you to save the password for each computer in a configuration file, so you can launch the viewer and log on to the remote with a single double-click (or single click from the quick launch bar). I have TightVNC set up to do that - if you trust the physical security of the viewer machine, of course.
As to logging in from outside the home network, that's probably more a case of opening the appropriate port in your router's firewall, and forwarding it to the machine you're most likely to want to control remotely. Or several ports, if you want to access multiple machines. Again, think through the security implications before you do that.
There are solutions which allow you access to the entire home network, but your typical home/SoHo router probably doesn't support them. For many years, I specified Draytek/Vigor routers for my business clients: they allow you to create a VPN connection to the router itself, without exposing even one port to the outside world for pass-through. That seems to be a pretty robust solution.
RE: RE: (unless the
)
I suppose not, but I don't have any set up that way. On my Win7 box, Boinc starts at Windows start, even before I log in, but it doesn't find the GPU until I exit Boinc Manager and restart it. The XP box doesn't have that problem; I don't know why.
When I'm using one of my own computers to remote into another with Teamviewer, I just double click the Teamviewer app icon on my desktop. It opens up and communicates with their server, then gives me a list of all my computers that are set up to be remoted into. I double click one of those and I'm in; if it has restarted and I haven't logged into it in person, I have to enter its password, otherwise I don't. If I'm using Teamviewer web access (from work), I have to use my username and password to get into the site, but from that point its the same as using the app.
When you first set up Teamviewer on a host, it will give you a machine ID and (I think) a password, but after you get it fully set up you won't need those any more.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
RE: RE: RE: (unless the
)
Yes, a web-based solution like that, with an intermediate server, removes the need to configure an open port in the router. But that leaves you reliant on the continued provision of the centralised service - and as we just saw with logmein, that can be withdrawn or have its conditions of service changed without notice. And you have to trust the service provider's security...
Solutions like VNC use point-to-point protocols, with no central third-party provider. That makes them harder to set up, but - it might be argued - more resilient, especially within a home network.
RE: RE: RE: RE: (unle
)
Thanks to both of you, that does help.
N9JFE wrote:On my Win7 box,
)
BOINC can only start prior to Windows login if you have it installed as a service, and when you do that, BOINC will not find the GPU because of separate sessions running the drivers and the Windows user account.
If you didn't install BOINC as a service, your BOINC will not start prior to you logging in. You will first have to log in, and only then will BOINC be one of the user-installed programs that's going to run. That a GPU cannot be found at such a stage may be due to BOINC loading way earlier than the full desktop videocard drivers. That depends on how much Windows has to load at login, how fast the hard drive is that everything needs to be read off of, how much fragmentation is going on on that drive, how much memory you have, how fast this memory is, how big the Windows swap file is, and really a whole myriad of other things, including how busy the CPU is when it (also) needs to load all that stuff.
BOINC is one of the things that can load and start reasonably quickly, earlier mostly than e.g. the AMD Catalyst Control Center. As soon as BOINC loads up the CPUs, everything else that still needs to load will have to wait, despite BOINC apps running at low priority. They still need to load, and may take up memory that is needed to load other programs.
One option is to set some of the user-installed non-service programs to load later, after Windows has started. Some tools to help you achieve this can be found here: http://www.makeuseof.com/tag/3-small-windows-freewares-delay-program-launch-startup/
RE: N9JFE wrote:On my Win7
)
Thanks. I'll try to remember to check those out when I'm home.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
I'm using WinPatrol, which
)
I'm using WinPatrol, which isn't too difficult to use. It also allows for switches on the program. So in the case here, where I start boinc.exe, I can add --detach_console as parameters and that'll start the client and close the command line window.
Then when boincmgr.exe starts 2 minutes later, I have set as parameters /a /s, to tell that the client started already and that the manager can go to the system tray.
Regarding the problem with
)
Regarding the problem with remote desktop stopping GPU tasks, I was wondering if the explanation still applies, at least under Windows 10. The reason why I ask this is:
1. Often the tasks continue crunching for about 1 minute after starting the remote desktop session before the tasks revert to the "GPU missing, waiting to run" status. If I correctly understand the explanation given, I would imagine the GPU would disappear the moment the remote desktop session is established and the tasks would instantly stop.
2. The Windows 10 Task Manager shows other tasks (such as Google Chrome) continuing to use the GPU even during the remote desktop session. (Or what does it mean when the "Processes" tab shows GPU activity and stuff like "GPU 0 - 3D" in the "GPU Engine" column?)