This might be a longshot, and there are several "if's", involved. But it might be worth a try if the conditions are met. 1. IF you use the RDP feature of Remote Utilities, then the remote computer at least has that capability. The idea here is that you can use the native RDP server built into Windows. Which brings up IF #2. 2. IF you have used this feature in RU, then you would need to open a port in the remote computers router, since the RU host is not running. Ideally, you would know how to access this router over the web. Then you could possibly telnet/SSH into the router to open the port. IF, you don't know the wan IP address to access the router, you could probably get this when your remotes post to your website. Most control panels for the web management allow for logging of all IP addresses that connect to your site, along with other details about the connection. 3. If there is anyone there that could possibly help you out, all you would need to do is get them to download the host from RU, and run it with default settings. On my remotes that wouldn't finish installation, I copied the host msi to the machine, then ran the msi, and it detected that a previous installation needed to finish first, I agreed to that, and it finished the install without problem.
That's about all I can offer. I Hope that it might be of use to you... Benny
Hello Conrad; First of all, let me say that I finally got everything working. However, it wasn't all smooth sailing. I guess I must be in the minority, but this upgrade for me was a struggle. Below, I'll describe what happened, and the solutions that worked for me. 1. The upgrade to 188.8.131.52 was flawless. All of my viewers, hosts, and server upgrades went smooth as silk. No problems whatsoever. 2. The following day, I tried upgrading to 184.108.40.206. That's when the wheels fell off. On my main viewer machine "Windows 7", I tried installing the viewer. Got the errors described in another post. Following the directions in the other post, I tried to uninstall viewer using the Windows Control Panel Programs and Features. This didn't work, as Windows couldn't find the necessary uninstall files. I eventually uninstalled viewer using the uninstall viewer shortcut in the "All Programs"-"Remote Utilities-Viewer" folder, then manually deleting the config_4.xml file. Re-booted machine, then reinstalled viewer. Success !! EXCEPT, General Address book was there but was now empty..... Solved this by restoring a backup from day before... Thank You for this automatic backup feature. Viewer required complete re-configuration, including license key. I guess all of that was in the config file I deleted. OK, viewer is at this point operational, Full Control, File Transfer etc worked fine. Until.... 3. Click on RDP file to open rdp connection... Would not work. Got more errors, couldn't open .rdp file. Every computer in my address book was like this for RDP. Could not even open the file using MS RDP. Opened the files in notepad, and each and every one of my .rdp files were corrupted. Only the top 4-5 lines in the file were visible, and it looked like a foreign language instead of the usual parameters. I just happened to backup the whole viewer folder before upgrading, in case I wanted to downgrade. At this point, I copied my backups back into the rdp folder. After trying to open another rdp connection, it corrupted that file instantly. I didn't click on any other rdp connections in viewer, until I could figure out what was going on. I finally figured out that the files were being corrupted, as soon as I right click on a connection and select "Properties". Didn't even have to go to the RDP tab. As soon as properties for that connection was selected, bang, the file was corrupted. The only work around I found for this, was to open the properties dialog for the connection, leaving that dialog up while I navigated to my backup, and copy/paste the file back into the rdp folder, then finally closing the properties dialog box. This finally got my RDP connections working, however, I had to do this for each and every one of my connections. Now I feel good about this particular viewer, except I had to do this whole procedure to my other two viewers as well. They all did this exact same thing. One other Win 7 machine and 1 old XP machine. 4. Upd ated RU server, the only problem was, I got the errors about it needing to uninstall the previous version, but the Control Panel uninstall didn't work for that either. Uninstalled using the same procedure as for viewer. Not as painful, but I did have to use a different remote software to get at my RU server to do the work, as the server is in another location. 5. Several of my hosts would not completely install upgrade using the remote install tool. Again, another remote software was used to complete the uninstall-reinstall of the new version. Finally, I got everything up and running smoothly again. I really do like the new viewer, more accurate online/offline status, search tool, and the ability to se t the connection type for double click in the viewer. This upgrade was nowhere near as easy as the previous upgrade, but I guess it might just be my setup, as I haven't seen any other posts in the forum talking about these problems. Thanks again Conrad. Still love this software...
I can assure you that we are not greedy :) It's only that we cannot always implement all that we (and our customers) want as fast as we would like to. That's software development - it always takes more time than initially planned.
Thanks Conrad; You have a fine product, and the price it great !!!
Hello Conrad, I have tried your suggestions above, and still no dice. It seems that no matter what I try, the parameter winposstr:s:0,1,300,70,1450,900, gets changed to default winposstr:s:0,1,0,0,1600,900, no matter how I try to save it. All other parameters remain unchanged. With a direct connection, I can click on the .rdp file itself and everything works correctly. It's only when I use the viewer to connect, that the values get overwritten. I can't figure out where the viewer is picking up the default values from. I know that the last two parameters "1600,900" is the screen resolution of the viewer computer. Thanks Conrad for your help.
I am all for cloud/web based infrastructure, IF the price of the software doesn't skyrocket !! I left LMI because they became greedy. Went to RealVNC with paid subscriptions for the last few years. Now they have gone to cloud based, and the price is suddenly 10 times more than the old platform, they got greedy also !! Just hoping the same thing doesn't happen with Remote Utilities. I really like how RU works.
You must apply the code on the same Viewer where you customized the Host or Agent.
None of the hosts require a "Key". Only the viewer. Any number of licensed viewers can connect to any host. You can use the same license key for all of your viewer machines. You are only limited to how many addresses you can have in your address book, by the type of license. Free = 10, Mini = 50, Per-Operator = Unlimited. Hope that helps..
Hello Conrad, I am trying my best to figure out how to save my RDP screen position. I can edit the .rdp files and position the remote desktop exactly where I want it. Specifically, the parameter "winposstr:s:0,1,300,70,1450,900". This is for a 1024 x 768 window on a 1600 x 900 viewer computer. The other parameters "desktopwidth:i:1024" and "desktopheight:i:768", all remain as they should. However, each time I open the RDP connection from within viewer, the winposstr parameter gets defaulted to the top left corner of the local screen "winposstr:s:0,1,0,0,1600,900". I've tried changing the default.rdp file and the individual rdp files to no avail. Everything else works just fine, Full Control, View Only, all work great. Just can't get RDP to save the remote screen position. Any work arounds you know for this. Thanks in advance for your help. Benny Tucker