Yes, and it most definitely will. For example, in the upcoming update we'll store the settings in a different registry entry than where they are stored now. Instead of:
Aaron Levinson wrote:
This approach to determining the Internet ID programmatically is fragile, since the way in which this information is stored by Remote Utilities could easily change in a future version of the software.
Thank you for the suggestion. I will forward it to our developers and we'll see what we can do.
In another post, I saw that a user was wondering if it were possible to bind Remote Utilities to a specific network interface. The response was that this was possible in older versions of Remote Utilities but hasn't been available for some time. I'm not asking for a way to do this from the Remote Utilities Host UI--what I am asking for is a command-line option for the /start command that would provide the ability to specify a specific network interface to bind to. On a system with multiple network interfaces, Windows' TCP/IP implementation frequently makes bad choices when it comes to picking the best network interface to use. For example, on a system with a fast Ethernet connection and multiple slower mobile broadband network connections, it usually picks one of the slow mobile broadband network connections, sometimes the slowest of the mobile broadband connections. Windows TCP/IP appears to decide which network interface to pick based on the combination of the interface metric and gateway metric, and it frequently assigns poor choices for the values for each of these metrics. It is possible to change them, and I've done that, but it doesn't work reliably, and the settings will sometimes revert to the defaults after rebooting the system.
* Website time zone: America/New_York (UTC -4)