Overview

As part of our commitment to maintaining a secure, efficient, and robust technical infrastructure, Magic Memories is transitioning away from our self-hosted ScreenConnect instance and standardizing all remote management capabilities under NinjaOne.

While change can introduce temporary adjustments to daily workflows, consolidating our tools allows us to better protect our systems, automate repetitive tasks, and ensure compliance with global security standards. This article outlines why we are making this change, what it means for you, and the next steps required to ensure a smooth transition.

Why Are We Making This Change?

The decision to retire our self-hosted ScreenConnect instance was driven by a combination of security compliance, operational efficiency, and a push toward better system automation.

Enhanced Security & Compliance

During a recent independent third-party cybersecurity assessment required to secure a major enterprise contract, investigators identified that our self-hosted ScreenConnect environment was running an outdated version. This version contained a known vulnerability that could allow unauthorized users to bypass authentication.

To maintain the trust of our global partners and protect our infrastructure, we must eliminate these vectors. Transitioning to a fully managed platform like NinjaOne removes the risk of running outdated, self-hosted software.

Process Standardization & Long-Term Efficiency

Admittedly, ScreenConnect offered a path of least resistance for quick, manual workarounds. However, relying on these shortcuts often meant bypassing standard procedures, leaving gaps in documentation and system uniformity.

By standardizing our workflows within NinjaOne, we ensure that proper processes are followed systematically. While configuring changes in NinjaOne may require a few extra steps initially, it benefits everyone in the long run through automation.

Example: Instead of manually dragging and dropping software onto a single computer during a live session, taking the time to build a standardized deployment package in NinjaOne means that every future machine deployed to that site will automatically inherit that software out of the gate—saving hours of manual troubleshooting down the line.

Operational & Cost Efficiency

While financial considerations weren't the sole driver, maintaining the status quo carries significant overhead. Renewing our perpetual ScreenConnect license costs thousands of dollars annually. When combined with underlying hosting costs and the internal SysOps resources required to constantly patch, monitor, and maintain a self-hosted server, it represents a significant effort and labor cost.

Because NinjaOne, which features identical, top-tier remote access capabilities, is already integrated into our environment and included in our existing licensing, continuing to pay for both tools is no longer practical nor sustainable.

Timeline & Next Steps

• The Shutdown Date: While we have roughly 80 days (as of 8th of July 2026) to complete this process, we have not yet finalized the official shutdown date for the ScreenConnect server. A definitive timeline will be communicated as soon as it is established.

• Onboarding: You do not need to wait for ScreenConnect to go dark before moving over. We are ready to begin provisioning user access to NinjaOne immediately.

Required Actions

For Country, Regional, and Site Managers

If you manage external clients who currently utilize ScreenConnect to access machines, please reach out to them proactively to inform them of this upcoming change. (Note: You only need to notify active clients who currently use ScreenConnect; there is no need to inform clients who do not use the tool.)

For All Remote Access Users (Access Audit)

Corporate IT is conducting a comprehensive audit of remote access permissions during this migration. Access permissions will not automatically copy over from the old system. To gain access to the new NinjaOne portal, you must raise a support ticket with the following information:

• The email address of the user requiring NinjaOne access.

• The specific site code(s) they have a business need to access.

• The specific machines required.

• Requesting access to "All" machines is generally unacceptable unless you are a Country Manager or have a unique, verified business case. Please be specific in your requests.

• Good Examples: "Capture PCs only", "All SITE PCs except for Workflow Server", or "Only production PCs."

Once your ticket is approved and processed, you will receive an invitation to the new portal. You will log in securely using your existing Google Credentials (SSO).

Frequently Asked Questions (FAQ)

Will I automatically be granted the same access I had before?

No. We are taking this opportunity to audit remote access. You will need to request remote access to be reinstated.

 How do I sign up for NinjaOne?

Please do not sign up for NinjaOne until you receive an invite via email. We will provide documentation on how to sign up for NinjaOne, including how to store the required 2FA codes in 1Password.

How will I sign into NinjaOne?

You will use your Magic Memories Google credentials to sign into NinjaOne.

How will clients sign into NinjaOne?

Clients will use their Magic Memories-issued Google credentials to sign into NinjaOne.

If NinjaOne is not installed on a device, can I still remote into it?

No. NinjaOne must be actively installed on the target machine for remote access to function.

Where do I download the new NinjaOne installer?

To make this transition as easy to remember as possible, our existing download link will remain active. While the URL remains unchanged from the ScreenConnect days (scdl = ScreenConnect DownLoad), the contents have been updated to host the new NinjaOne installers only moving forward. Please use this link for all future installs: https://u.mmem.co/scdl