ScreenConnect in RDM with AD user

Hi,
Our developer that did the Screen Connect extension is currently on vacation. He is our expert in Screen Connect. I will assign him a ticket and he will respond to you as soon as he get back.

I'm not even sure if we support the AD authentication in Screen Connect but like I mentioned I'm not the expert.

Sorry about that

Regards

Hello,

We'll see what we can do to allow Active Directory login method for ScreenConnect. We'll have to create an environment that uses this login method but I'm hopeful it's possible.

Regards,

Hello,

We tested using ScreenConnect version 6 alongside RDM 11.6.7.0 and the ScreenConnect extension V 1.7. It is working as expected. Could you make a screenshot of the connection settings window and private message it to me? I'd like to see what the host and username look like.

Regards,

I have been using RDM with RDP for managing our servers remotely for several years now. We are at version 10.0.4.0, with no upgrades available.
We have discovered an issue with Windows 2012 Servers and using RDM/RDP in that some apps start crashing after closing an RDM session.
We also use ScreenConnect version 6.0.11 as our secondary connection method. We have found that ScreenConnect sessions do NOT suffer the same issue and so have started using ScreenConnect only with the 2012 servers. Finding that RDM supports ScreenConnect sessions, of course I would like to use RDm to manage those connections too.
However, I have not found anything telling me how to configure such with these versions. I installed the ScreenConnect Extension 1.7, then saw that it says "RDM version 12 or higher." How is that possible if my RDM says version 11.7.4 is the latest available?

I would really like to use RDM to manage our ScreenConnect sessions, can you help?

Hello,

Could you still try and see if ScreenConnect sessions work? You need to fill out all the appropriate information and make sure to specify in the "settings" tab of your screenconnect session the version (Extension, in your case). If you need further help or encounter issues, please post your error message and any additional information of your configuration.

The reason it says RDM 12 is because at the time of extension version 1.7, the next planned version was RDM 12, but we changed our minds and did a few more minor versions / beta versions. The ScreenConnect extension development process doesn't allow us to simply change the description of a published add-on version as far as I know, which is why it stayed that way for the moment.

Regards,

Thanks for the fast response Hubert.

Does RDM have to be restarted after installing the extension?
I am trying to set up the first entry and can't get past the first field.
You say to specify the port along with the IP address for the host.
The IP is no problem (although Screenconnect is using a relay server) but I cannot find anywhere a "port" setting in ScreenConnect.

The port by default for a screenconnect installation is 8040, which would mean you'd enter something like "Http://yourhost:8040". If the port is "80" you don't have to specify it, which would look like "http://yourhost".

You do not have to restart RDM after installation the screenconnect extension on your server.


Regards,

OK, I was able to create an entry, but I do not have a "settings" tab like shown in your instructions here: http://help.remotedesktopmanager.com/index.html?sessions_screenconnect.htm
I only have General and Invitation Emails so I cannot change "version."

I get "Unable to connect to the server. Please verify host, username and password."
I have "Host" set to http://XXX.XXX.XXX.XXX:8040

You must be using an older version of RDM, you will need to use the latest beta version (11.7.4.0) to be able to use ScreenConnect version 5 or later, with extension version 1.7.

Regards,

As I said earlier, we have version 10.0.4.0 of RDM with no upgrade protection.
Can I install the Beta over the top of my existing installation?

@nunjabusiness

What type of data source are you using? If you are using SQL Server, upgrading from RDM 10 to 11 requires a database upgrade. This means that all the other RDM users will also need to upgrade.

Prior to upgrade your local installation, you can download the zip file of RDM 11.7.4.0 here and deploy the content of your zip file in a folder like C:\RDM as example. When you will open RDM 11, select a local data source like SQLite or XML to test ScreenConnect.

I will send you a trial license of RDM via private message to test RDM 11 if needed.

I can also send me your current license of RDM via private message and I will verify in our system if your license allow you to install RDM 11 or if a renewal is required.

Best regards,

I am running a local SQL DB (compact edition?) so that would require all to upgrade?
We have three licensed users and I am pretty sure we are not entitled to an upgrade unfortunately.
My boss is not too keen on spending money on software we already bought, how much would it cost?
My "About" screen under License Information says:
"Free upgrade until: Saturday, November 1, 2014" so I am pretty sure that means I will not be getting anything free.

Hello,

Yes, if one of you update to RDM 11, everyone would need to update as well because of the database upgrade.

I just send you a private message for the renewal of your 3 licenses.

Best regards,

Thanks again, that is a good quote. Now I need to make sure I can make it work before buying it.
My plan is to install the trial of version 11 as a standalone copy and set up one of my screenconnect clients to see if it does how we expect.


I will be back for help I am sure. ;-)

OK, I have downloaded the beta zip file and extracted it into its own folder.
When I run remotedesktomanager64.exe it just focuses on my existing version 10 installation that is running.
Do I have to close the version 10 first or am I supposed to run something else?

Hello,

You can close your RDM 10 or enable the option Allow multiple instances in File -> Options -> Advanced.

Best regards,

OK, was able to get RDM beta to run now. Created Screenconnect group and tried to create first session.
First off, display does not offer tabbed, only External.
Settings tab, I chose "Extension" but it says I need to install it (I already have, twice).

Hello,

Yes, the session will be opened in external mode. We cannot open a ScreenConnect session in embedded mode.

Could you post a print screen of your session configuration + a print screen of the error message please.

Best regards,

Ahhh! OK, then that settles the issue anyway.
The only reason I wanted to use RDM for ScreenConnect was for the tabbed interface so I would not be having multiple windows open all over the place.
The current version we have is adequate for RDP and VNC if needed, so I guess we just have to live with multiple windows being open. Maybe ScreenConnect or somebody else will come up with an extension to dock them or handle them in a single parent app.
I really appreciate your help and efforts to assist me, we love your product and wish you well.