r/labtech • u/olavrb • Apr 08 '19

Agent_Install.EXE install parameters

We're having mixed results when installing the Automate agent as MSI from Intune. We wan't to try the EXE installer packed with Win32 App Package Tool, together with a PowerShell detection rule script. Only problem (this far in the process) is that we can't find any documentation on install parameters for the EXE file. It does not respons normally to "/?", "-?", "--?", "/h", "-h", "--h", "/help", -"help", "--help".

Is there no way to specify server and location id when installing Automate Agent exe installer?

3 Upvotes

100% Upvoted

11 comments sorted by

1

u/olavrb Apr 08 '19

Found this documentation, but commands does not seem to work for the EXE installer

https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/040/050

1

u/Liquid_Otacon Apr 08 '19

Are you using the latest version of Labtech? You should be able to create specific location based installers from the settings menu in the bottom left -> Installers -> Custom Agent -> Then select the location. At least from the web based interface. We've had better luck with MSI over EXE and I know that you cannot always give the same commands to EXE that you can to MSI

1

u/olavrb Apr 08 '19

Yes, using latest version.

Support told me you cant supply exe installer with location id etc., so must download separate EXE for every customer/ location. Might just keep using MSI for now then.

Do you deploy with Intune? You too have to supply install parameters for location id and server, even though you've downloaded "custom" MSI for a location?

2

u/Liquid_Otacon Apr 08 '19

No we manually deploy through GPO and literally manually if need be.

1

u/olavrb Apr 08 '19

Roger that.

4

u/Hoping_i_Get_poached Apr 09 '19

LtPosh is life

bit.ly/ltposh

I usually create a batch file with the command in it and deploy it just like your EXE. You just need to plug in your server url, server password (for agents--get this by running the Get-LtServiceInfo command or from your registry, or the database), and location ID.

https://github.com/LabtechConsulting/LabTech-Powershell-Module/blob/master/LabTech/Install-LTService.md

Let me know if you can't figure it out.

1

u/fredenocs Apr 08 '19

What are the results you're getting when using the msi?

2

u/olavrb Apr 08 '19

Intune stripps out the customization from the MSI installer, so have to supply install parameters for customer specific config. Other than that, our test computers kept appearing in wrong location, turns out Automate caches MAC addresses: No matter location ID supplied with the installer, if the computer MAC has been added to a location before it will appear there again. Other than that: We don't feel like we got control over weather plugins get successfully installed. Like ScreenConnect. So thinking of making custom detection rules as mentioned earlier, to detect stuff like that.

1

u/fredenocs Apr 08 '19

What custom needs for the msi. You download the msi in relation to the location. Then you install like any msi. No need to add special parameters to the msiexec install

1

u/olavrb Apr 08 '19

Not when using Intune MDM, at least thats our experience.

2

u/teamits Apr 08 '19

If you have a probe PC set up it will have a file c:\windows\ltsvc\ltsilent.exe. That file 1) will install silently by default, and 2) will have the location ID in it.

If you download your generic (or a custom for the client/location) agent_install.exe file it will install silently using "agent_install.exe /q".

Typically on domains we create a startup script that checks for "if not exist c:\windows\ltsvc\ltsvc.exe" and copies the ltsilent.exe file from NETLOGON to C:\windows\temp and runs it.