What is needed is to wrap all of those up with in an intunewin file and call the PoSh as the install string. InstallExtreme.ps1 (that is what I'm going to share below, and you can use as a reference) UninstallPreviousVersions.cmd (provided by BB to uninstall previous versions by product code)īluebeamRevueXtreme.mst (the file you create with your BB configuration tool) Once you've run the configuration tool and use the enterprise media for distribution, you will have several files that you can wrap into a script for deployment (file names might be a little different):ĪRP_Modifier.exe (sets the correct edition in Programs and Features)īluebeamRevu.msi (the actuall Revu install for both standard and extreme) MSFT - This posting is provided "AS IS" with no warranties and confers no rights.I can share how I do it for ConfigMgr and Intune. Any additional files and folders that are required by the software’s Setup program must be available from the location that you specify for the software setup files.The software installation will fail on computer when you use these options. If command-line arguments are required, they must be enteredĪs Name=Value pairs (such as TRANSFORMS=custom_transform.mst).ĭo not specify options, such as /q or /quiet, as command-line arguments. In most cases, Windows Installer (.msi) and Windows Installer Patch (.msp) files do not require any command-line arguments to be installed by Windows Intune. If your software uses any other type of Setup file, or requires user interaction during setup, that software cannot be installed by using The Windows Installer files must support silent installation, that is, without requiring user intervention.You shouldn't need to upload the MSIEXEC.exe either, just upload the MSI and provide the supported command line arguments. You can't specify quiet paramenters, it will fail for MSI.
0 kommentar(er)
