Douglas Crawford's community posts

MISMATCH VERSION!
Thanks so much!
I thought I had all the machines on 7.1.1.0.
The sender was on the old version.
OK learned my lesson.  First sign of trouble
always check for version mismatch.  I might
have thought if they talked at all, they would work
except for new features... bad assumption.

Doesn't this point to an issue of the inability for the current version to convert an old address book into
its new format?  Or is it assumed users will recreate their address books?

Hi

Attached is a screen for data transfer from a Win10 computer across the internet to another Win10 computer.
The originating and destination network is Comcast business with 40Mbps.
roughly then, 4MByets/sec measured rate.
See attached speed test which was for the sending side.
Then see attached File Transfer progress.
Is something wrong that the transfer is only achieving 289 K Bytes per second?  
That's less than 1/10th of theoretical speed.
This is making our file transfer a lot longer than we anticipated.
What do you think?

Thanks
DC

Do consider "breahting" - fading in and out.  That gives us the best fighting chance to operate/see
what is underneath it!

THANK YOU for the hint on updating.  I'll get to it ASAP.
-DC

I'll have to crack the nut of a remote install as I'm not there to complete the GUI dialg boxes.
We'll see.  I really have to be careful about disturbing the running state of the PCs.

Its probably a unique situation hard to reproduce.  It may have had something to do with the host machine in some sort of distress. RU V7.1.0.0 was used, with WIn10 version 20H2 build 19042.1415 host and the Win7SP1  at the viewer (don't know how to get any better version info on that)  I would look into whether your mechanism for rebooting built into the Power Control is robust enough to work when windows itself is in distress, and add
a low level reboot option if possible.  Though I've offered several times, I think giving you folks access to the host machines in these cases would be the most powerful way for you to experience these rather than trying to reproduce it.

.

Yes, when I said I was unable to force a reboot, I was using the Power Control connection mode.
Though I was able to get to a connection, it seems RU was unable to effect the reboot apparently
due to whatever was wrong with Windows (10).  That's why I was recommending maybe bypassing windows
for the reboot if you are able (and if you don't already do that).  I mean maybe you need to offer a
low level reboot in addition to a normal windows reboot so that you have an option of treating windows
nice or not if it isn't cooperating.

My past few posts have had a tense tone.  I apologize for this.  Let me explain
and give credit as it is deserved.
I just went live with a remote system and things have not been so smoothly.
I have lost control of one remote computer and I really hoped to avoid that.
That said, I am so impressed with the service that RU personnel give to this site
that I have full confidence in the company and product.
I have operated RU through a few versions and over the past year it has helped
us immensely.  I have previously mentioned being thrilled with its overall reliability
and performance, as its overhead has never caused us any issues.
This is still true.
The response time and quality of support on the board is way above my usual
experience with this sort of mechanism.  Usually it is the lay community chiming in.
You folks really listen and try very hard to work with the information we provide.
That is impressive.  Keep up the good work.  Hopefully we will help you nudge this product along
with real world feedback, and I'll try to contain my frustrations with Mr. Murphy and his ever present Law.
Many thanks and best to you all in the new year.
Doug C.

This was involved in that headless debacle but I am past that.  I put monitors on all the remote computers
and this is a later problem that arose after this machine was in service for 24-48 hours.
Quite clearly I was able to connect to the machine and even get the full control mode opened up, but
I was unable to force a reboot.  I think this demonstrates that even though RU can get into the machine
and even show its desktop, you can't depend on RU to be able to reboot the machine.
This is forcing me to consider obtaining power management equipment that I can control over the web
in order to power cycle a computer.  Bummer.  I was hoping that RU would be able to reset the machine
if I was able to connect to it.  Perhaps consider employing a software reset mechanism that is not dependent on
a windows API... bios call maybe?