ScreenConnect offers secure and dependable remote access, ensuring you can support your end users effortlessly, no matter where they are or what time it is.
Note:
- ScreenConnect is available for Windows devices only.
- To use ScreenConnect with Atera, you'll need to have a valid ScreenConnect account. If you don't have one, you can sign up at ScreenConnect (along with your account, you'll also receive access to a ScreenConnect management console).
- If you have existing customer/host listings, groupings, or hierarchies on your ScreenConnect management console, Atera will not touch them. We won’t overrun any of the existing organizational structure. However, if there are no hosts listed on the console, then the hosts you add on Atera will be copied to the ScreenConnect management console.
- The installation of ScreenConnect from Atera can be done only using the .MSI installer. It does not support installation via .EXE.
Configure ScreenConnect settings
When setting up ScreenConnect within Atera, you'll need your:
- ScreenConnect URL: The unique web address for your specific instance.
- Instance ID: The unique identifier for the ScreenConnect instance used to manage and connect to target devices.
- ScreenConnect installer URL: The URL used to download the software.
We'll describe locating all of this below.
To set up ScreenConnect in Atera:
1. Go to Admin > Monitoring and automation > Remote access settings.
The Remote access settings page appears.
2. From the ScreenConnect tab, toggle Configure ScreenConnect license.
3. Enter your ScreenConnect URL, Instance ID, and Installer URL.
Note: For help locating each, see:
4. Click Save.
You can now remotely connect to your end users via ScreenConnect.
Note:
- Please make sure that pop-ups for Atera are enabled in your browser.
- Please ensure there are no spaces in your ScreenConnect Installer URL — especially when copying over self-hosted ScreenConnect Installer URLs.
ScreenConnect URL and instance ID
To locate your ScreenConnect Instance ID:
1. Open your 'File Explorer' and click This PC.
2. Click OS (C:).
3. Navigate to Program Files (or Program Files x86 for 32-bit computers).
3. Search for 'ScreenConnect Client'.
The ScreenConnect Instance ID is the number/letter combination that appears in parenthesis (see image below).
2. Copy the ScreenConnect Instance ID so you can paste it into Atera:
ScreenConnect installer URL
To locate your ScreenConnect installer URL (Windows):
1. Log in to your ScreenConnect Dashboard ("https://[your-company].screenconnect.com").
Note: This is the URL located on the Instances page (described above).
The ScreenConnect Dashboard appears.
2. From the Access page, click Build +.
The Build Installer window appears.
3. Select Windows (.msi) from the Type dropdown and fill out the rest of the fields as needed.
4. Click Copy URL > Copy.
Note: You can also use your own self-hosted ScreenConnect Installer URL.
5. Enter it in the Installer URL field within Atera
Connect with ScreenConnect
You can remotely connect via the Devices page, Agent console, Site page, and within a ticket.
You can remotely connect via the Devices page, Agent console, Customer page, and within a ticket.
Note: The first time you connect to a device, ScreenConnect will automatically be installed. It may take up to a minute for the installation to complete, but once installed, the remote connection will begin automatically.
Devices page
To connect from the Devices page:
From Devices (on the sidebar), locate the device and click Connect.
Note: If ScreenConnect isn't your default remote access tool, click the Connect dropdown menu and select ScreenConnect.
Agent Console
To connect from the Agent Console:
1. From Devices (on the sidebar), select the device.
The Agent Console appears.
2. Click Connect.
Note: If ScreenConnect isn't your default remote access tool, click the Connect dropdown menu and select ScreenConnect.
Site page
To connect from the Site page:
1. From Sites (on the sidebar), select the site.
The Site page appears.
2. From the Devices tab, locate the device and click Connect.
Note: If ScreenConnect isn't your default remote access tool, click the Connect dropdown menu and select ScreenConnect.
Customer page
To connect from the Customer page:
1. From Customers (on the sidebar), select the customer.
The Customer page appears.
2. From the Devices tab, locate the device and click Connect.
Note: If ScreenConnect isn't your default remote access tool, click the Connect dropdown menu and select ScreenConnect.
Ticket page
To connect from within a ticket:
1. From Tickets (on the sidebar), select a ticket.
The Ticket page appears.
2. Click Connect in the Requester info tile (right-hand side of page).
Note: If ScreenConnect isn't your default remote access tool, click the Connect dropdown menu and select ScreenConnect.
ScreenConnect Q and A
Q. What happens if there is a previous ScreenConnect host on my customer’s computer?
A. If there is already a ScreenConnect host installed on your target computer, Atera won't reinstall the host. You'll be able to remotely connect with your customer from the Atera platform, using the host.
If there is no host installed, once you set up the integration and initiate a connection with the customer, we'll automatically deploy the latest version of the host to your customer.
Q. Is ScreenConnect included in the Atera subscription cost?
A. ScreenConnect remote access is included in the Atera subscription at no additional cost. However, it is a BYOL (Bring Your Own License) integration, so you'll need to purchase a license directly from ScreenConnect if you don't already have one.
Q. Where can I purchase ScreenConnect remote access?
A. You can purchase the license from ScreenConnect's site
Q. What about other remote access integrations?
A. We currently have integrations for Splashtop, AnyDesk and TeamViewer. If there are any other integrations you'd like to see, let us know via Ideas and Feedback
Q. What about the Splashtop remote access integration? Will it remain free?
A. Splashtop remote access will remain unchanged, so you can continue to enjoy it, and yes, it will remain free.