Our company is slowly moving all of our customers away from our RMM in favor of Intune.
However, we still want the ability to use ConnectWise Control to remote onto the host directly.
We made this script to deploy it.
You need to get the msi url and setup a secure variable, but after that, it's super painless to deploy in NMM.
Feel free to message me if you want help getting this setup in your environment.
Hey Dave, would love your help getting this going - we wanted to deploy the CW Agent , but it dont seem like its the old school labtech version in the scripted actions repository. Its asking for Token and CW Automate (Labtech) dont have that anywhere?
Hey, Domenick DIS. Welcome to the forums. 🙂
There was another post (Scripted Actions for ConnectWise Automate – Nerdio Help Center) that talked about implementing this.
I found a way to generate the Token, but never heard back from the original poster on that to know if that worked/helped.
We went with the CW Control (ScreenConnect) deployment because we're working towards no longer needing CW Automate (LabTech) and managing as much as we can with Intune/Update Rings/Azure Arc/Azure Update.
Does any of that help?
Dave, Thanks - I was looking at that too. I was confused regarding the server password part - considering you need both a username AND a password
Domenick DIS, did you happen to see Marcos Artiaga great script he created for deploying ConnectWise over in the Using Connectwise RMM (Asio) With AVD Hosts / Deploying RMM Via Script thread?
I think that may get you what you need.
https://help.nerdio.net/hc/en-us/community/posts/20743245878925/comments/21364927437325
Hi Dave, I was trying to deploy the Screenconnect app on the AVDs and found this article. I am struggling to understand the Secure Variable portion of this article.
Can you please tell me what do we need to enter in $CWControl?
Welcome to the community, Aman Patel 🙂!
Unfortunately, I'm no longer with the company where I made that scripted action (and don't have access to NMM at my current company 😞, yet) so I'll have to do my best to recreate it from memory.
When you copy the URL from your control instance, it will look something like this:
https://control.MSPCompanyName.com/Bin/ScreenConnect.ClientSetup.msi?e=Access&y=Guest&c=MSP%20Customer%201A%202B%20C3&c=AVD&c=&c=&c=&c=&c=&c=
To make it so you can use the same scripted action in multiple accounts, you have to break the URL apart.
The first part is standard for all of your installs and gets the variable name of $URL1
https://control.MSPCompanyName.com/Bin/ScreenConnect.ClientSetup.msi?e=Access&y=Guest&c=
The second part is your secure variable that you enter at the account level.
This is the Company Name (as it exists in ScreenConnect) but in URL Encoded format.
NOTE: You can use a website (like URL Encoder https://www.urlencoder.io/) to help you with the conversion if you're like me and can't remember all of the %20 %2A coding you need to do for a URL)
MSP%20Customer%201A%202B%20C3
Example:
ScreenConnect Company Name = MSP Customer 1A 2B C3
Converted Company Name = MSP%20Customer%201A%202B%20C3
The Converted Company name is what you use as the value in the CWControl (secure variable) at the account level.
The next portion is the last part of the URL which should be fairly consistent where you're basically putting the values for the rest of your install parameters.
&c=AVD&c=&c=&c=&c=&c=&c=
It gets assigned the $URL2 variable.
The last variable ($URL) combines it all together to work like it normally would to install ScreenConnect.
$URL = $URL1+$SecureVars.CWControl+$URL2
The next line in the scripted action downloads the ScreenConnect agent to the computer.
The last line executes/installs the downloaded installer.
Hopefully that helps, but if not, let me know and I can see if I can provide additional clarity. 🙂
Please sign in to leave a comment.
Comments (6 comments)