Using DattoRMM to deploy CW RMM via scripting???

Submitted ⁨⁨6⁩ ⁨months⁩ ago⁩ by ⁨terminhell@lemmy.dbzer0.com⁩ to ⁨technology@lemmy.world⁩

Does anyone know how Connectwise RMM does scripting deployments FROM other RMM tools? We are having a tough time trying to figure out how to pass our site tokens through as part of an installation script from DattoRMM, and none of the documentation seems to align correctly. Someone told us it would be something like

msiexec /q /i “%tempdir%\AsioAgentIinstaller.msi” TOKEN=@RMMSiteToken@ /L*V “%tempdir%\AsioAgentInstaller.log”

but we’re not seeming to have much luck with that.

Has anyone successfully scripted their deployment/migration from DattoRMM to CWRMM, and if so, how? We’re absolutely vexed at this.

source

Comments

Sort:hotnew top

d3Xt3r@lemmy.nz ⁨6⁩ ⁨months⁩ ago
This is a general tech community, mostly centered around news and end-user topics., so it’s very unlikely you’ll get an answer here. Might want to try asking on Reddit or some dedicated Datto/Connectwise forum.

source
claytonburns@lemmy.world ⁨6⁩ ⁨months⁩ ago
Strangely enough, I may be able to help…

When creating the component in Datto RMM, you should be able to upload the MSI file. Then you can call it via the script by just giving it the file name (the component uploads the file to the working directory).

For the token, you can create a variable called %token% via the UI, which will cause Datto RMM to prompt the token every time the component is scheduled.

So your batch “script” would be:

msiexec /qn AsioAgentInstaller.msi TOKEN=%token%
source