In follow-up to our recent post, we’re pleased to announce that MSP Anywhere-powered Take Control is now available with the MSP Remote Monitoring & Management mobile apps. It means you can run Take Control sessions directly from your phone or tablet for any devices using the MSP Anywhere engine.

To take advantage, select any server or workstation that’s using MSP Anywhere-powered Take Control, then on the Device Info screen, tap the Take Control button. This will launch the special Take Control companion app. The first time you use this you’ll be prompted to install the app, after that it will start the remote session automatically.

The MSP Anywhere app is fully featured, and gives you a great set of tools for remotely managing client devices. The ability to provide fully fledged remote support from your mobile is a great opportunity that you can work into your service offering, and may well give you a competitive advantage over your rivals. 

Note that the Take Control companion app can only be used by starting a remote session from within the main RMM app. If you open the Take Control app directly it won’t give you any options.

Here are a few screenshots to give you an overview…

Interact directly with your client’s computers from an iPad…

Use Take Control’s file transfer feature, seen here on an Android device…

Use the chat option for direct, one-to-one support with your clients…

The new MSP RMM Take Control apps are now available for download from the SolarWinds MSP store accounts for Apple and Android. Enjoy!

BUGFIX UPDATE: The problem affecting the TeamViewer-based Take Control feature in iOS mobile apps has been solved, thanks to a TeamViewer app update. Please ensure you’ve updated your TeamViewer app to v12.0.72275, which was released on December 21st.

For Android users: If the TeamViewer app does not launch when you select Take Control, please check to make sure the TeamViewer app permissions are set to allowed (go to Settings > Apps > TeamViewer > Permissions). You may need to restart your device. This should fix the issue on Android.