I did it slightly differently, but only because my Dad was going through early-onset dementia and I sometimes couldn't talk him through what he needed to do his end. I ended up using
TeamViewer in 'Host Mode', i.e. the service was set to start automatically with Windows.
However, I changed the service from 'automatic' to 'manual' and provided a desktop shortcut (with keyboard shortcut of Windows key + T) to start
TeamViewer. The shortcut actually ran an
AutoHotkey script that started the
TeamViewer service running at his end. The script waited in the background for the
TeamViewer process to end (by me or him exiting) then monitored the desktop for the process which popped up
TeamViewer's 'Thank you for playing fair' dialog and closed it so he didn't accidentally choose the 'Buy license' option.
At my end I had another
AutoHotkey script which ran
TeamViewer and passed my dad's connection ID (which didn't change) and static password as 'start' parameters so I didn't have to remember either of them. (Actually, I had two scripts, one for 'normal' mode and the other to run the session in 'File Transfer' mode. Have a look at this
Command line parameters article for more info.)
Ethernet is simple; it's basically either physically connected or it's not. Wi-Fi is great for ease-of-use, depending on signal strength, but there are more factors at play thus more potential hiccups... none of which are good if you live any distance away.
My Dad's router was in his lounge; he was bed-ridden two rooms away. Signal strength was poor at the best of times and, weirdly, dropped out when care staff came to attend to him. It took me a while to realise that 2 care staff in between the router and laptop were enough to absorb enough signal strength to cause drop-outs... not to mention them microwaving meals and hot drinks plus using some weird personal walkie-talkie system (on the same 2.4GHz frequency band as Wi-Fi) between themselves and the main office. In terms of Wi-Fi it was a disaster at first... so I ended up using an
Ethernet-over-Power ('Powerline' EoP) base unit connected to the router and a short ethernet cable to his laptop from the
EoP slave unit in the mains socket closest to his laptop. After a bit of testing I realised that using the
EoP slave unit as a Wi-Fi repeater was not only sufficient but mostly reliable, so retired the ethernet cable.
Have you tried that with
TeamViewer? I found laptop-to-iPad mostly unusable in terms of my remote spatial control of his iPad. However, that was about 4-5 years ago so no doubt it has improved a lot since then. I never tried with an Android tablet... my Dad just couldn't get his head round the disconnected utilities and much preferred 'Siri' automation of what he wanted to do. We didn't have a tablet running Windows then but I think that would be ideal for use with
TeamViewer... if only an older person's eyes can deal with the screen res./touch screen combo.
The thing is... it worked for my Dad and I for many, many years and prevented the necessity of me making a 2-4 hour round trip depending on traffic.
I note that
TeamViewer now enforces an account sign-on for outbound connections which it never, ever used to... so be aware of that.
Hope this helps...