• Connect 3.0 is Now Available
    I can understand why the decision was made (from a business perspective), but not a huge fan of the change to paid unattended access with no warning. I do like the enhancements and progress being made, but not letting folks know this feature was being turned off before an automatic update wasn't a great experience. I currently have 4 devices at 4 schools that I was remoting in to periodically, and to all of a sudden be told I couldn't do an unattended session, was an unpleasant surprise to say the least!

    For temporary fix/workaround, I've rolled back these 4 machines and set to not auto-update)

    I also have it on my personal home PC, and I'll never be there to accept an incoming connection, so not sure if you're wanting to force a paid subscription for those scenarios? I also have the software on our church Media PC, and may connect in to it to do something remotely periodically (even when no-one is there). Same for my Dad's home PC. I might connect into it to look at something when at a time he is not there to let me in. Those three scenarios are not paid solutions, so for me to pay to connect into those three, makes me want to look for another free solution for those particular cases. And I'd understand if you were OK with that from a business standpoint, just stinks for those of us who may be using it for non-interactive personal or small use-case scenarios.

    I am considering the purchase of (a) license(s) for my 4 school locations (, but still doesn't make sense for me to pay for the personal use cases).

    Don't want to come across as ungrateful for a product that I have not been paying for up to this point, but figured you deserved some honest feedback.

  • Deployment using msi

    Never told you thanks for the link to the command line install options, so a bit belated, but thanks!

    Any way we might be able to provide an encryption key with command line install? That might include pointing a already existing config file. I've discovered that copying a config file from a previously installed copy will keep the encryption key on the second machine. This is EXTREMELY helpful when wanting to have same security settings on a group of computers. Keeping track of separate encryption keys for EVERY SINGLE install is a bit too much so have gone to copying config files as part of installation in some of my use cases.

    Also, ability to set PIN and/or password, along with other settings of a silent install would be FANTASTIC! Again, this could be accomplished with being able to point to a config file with the installer command line options.

  • Has future update of remote assistant v2.3.0.52 changed?

    Noticing that when remoted into 2.4 machine, the "Check for Updates" is still not there in the Remote Desktop menu on the remote machine, same as @AlexSeidel said was the case in release 2.3.

    I have noticed this being a problem with not being able to remotely update some of my machines. On a couple of them, I still luckily happened to have a copy of another party's remote support app and was able to get Remote Desktop client updated within the other app's 5 minute connection timelimit.

    Would really really love to see remote update capability brought back in a 2.4 patch or when 2.5 get released. Makes is quite hard to not be able to remotely update those machines on 2.3 and 2.4.

    FYI, do absolutely LOVE the multi-connect support that we got in version 2.4!!!

  • Remote Assistant/Remote Desktop 2.4 release notes?/Name Change
    An noticed today that previously was on v2.4.0.47 and today Check for update, showed version so would be nice to know fixes in this last update as well if willing to share!

  • Deployment using msi
    Can you add my name to the request as well? Would love an MSI and/or silent install capabilities!

Jared Pickerell - DCEduCoop

Start FollowingSend a Message