Skip to content

Migrate from Remotely #192

New issue
New issue
Open
Open
Migrate from Remotely#192

Description

@sshnevis
sshnevis
opened on Nov 9, 2026

hi there.
I would like to discuss something with you.
At our company, we have about 80 computers across various pharmacies, all of which are currently equipped with Remotely. We are now looking to migrate to your service.
Do you have a proper guide or procedure for this transition? Or could you provide the necessary guidance?
I brought this up because you was the lead developer of Remotely.

Activity

  1. bitbound commented on Nov 9, 2026

    @bitbound
    bitbound
    on Nov 9, 2026
    Owner

    Hello there!

    I'm on vacation and on mobile right now, so I can't go into detail.

    But the general instructions I'd recommend is:

    • Create a persistent or time-based installer key in ControlR.
    • On the Deploy page in ControlR, copy the installation one-liner for each operating system.
    • Use Remotely's scheduled script run feature (or other deployment tool if you have one) to run the script on each device.
      -Once all the machines are working on ControlR, delete the installer key.

    Note that scheduled scripts haven't been implemented in ControlR yet, but it's up next after I finish ad-hoc attended remote control.

    Also, refer to the docs about 'ControlR_AppOptions__AgentClockSkewTolerance'. Temporarily set to null if devices are failing authenticate due to system clock sync issues.

    Let me know how it goes, either way. I'll follow up when I get back (after the 15th).

    Cheers!

    • Jared
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions