Hello ​@Kylar34 - Thank you for the guide! Can I ask if you have inlcuded the steps outlined in https://beyondtrustcorp.service-now.com/kb_view.do?sysparm_article=KB0016983 / KB0016983 in your guide?

​@PhillC You realize the whole point of an MSI is to make installation easier? Why doesn’t the .msi function as every other MSI? We shouldn’t need a wrapper for it.

​@PhillC I did reference that guide, and that process wouldn’t work in our environment.

Hello ​@Kylar34 - Understood, thank you for sharing your script. It’s good to see other ways of handling integrations or configurations within other systems!

​@Kylar34 Their guide won’t work because, for the “Install Command” you need to reference the batch file (install.bat), and NOT their canned command line as their guide suggests. 

Hello ​@BobF  - if our KB is wrong, I’ll be happy to get some changes in place. Can you outline which step in our guide you believe to be wrong, and I’ll get a review going here.

Step 5.1 shows a screenshot of the Install Command in Intune with the wrong command line. It should be the install.bat, not the full msiexec command line. 

I’m confused as to why you need to package it twice with the content prep tool. We had no issues packaging it once with the tool and pointing to an install.bat. The install.bat contains only the msiexec command line and a 10 second /wait.

If you want an easy way to grab the uninstall command and msi code, and have an easy way to test all of the commands before packaging, run the install in a windows sandbox and pull that info from the registry.

we also deploy through intune but use powershell scripting for it: 

command

Start-Process "msiexec.exe"  -ArgumentList "/i bomgar-scc-win64.msi KEY_INFO=YOURKEY /quiet /L*v C:\windows\logs\bomgar-scc-win64-MSI_Install.log" -Wait

We've had cases where we had to uninstall the old installer to replace with the newer and we've embedded an uninstall with the old key in the same powershell script. In Intune then you use: powershell -Ex Bypass -windowstyle Hidden -file Install-BTRS.ps1 instead of the actual MSI.

I do remember somewhere that the MSI installer is a user-mode installer and was better to encapsulate it in a powershell to have installed as a SYSTEM installer. 

Also for the detection rule, not recommended to include a version it, when your BTRS agents start to update, the detection rule is false and you will have the agent in an install loop until you've updated the detection method.