So I always try to find MSI’s as they are easier and faster to install via SCCM. This ok, if you want silent installs via SCCM you have to create a script install. My biggest mistake was giving users a means to request new software titles to be added to the Software Center in SCCM via the Service Desk as long as there is business justification or requirements of course!Īs you know a lot of programs these days, don’t provide MSI installations files. No admin rights needed, they click install, chrome gets installed! Nice For example, Firefox and Chrome are optional installs via the SCCM software Center. Software that wasn’t on the base image, is pushed out via SCCM, with some elements being available via the Software Center for people to install as required. Grumpy Admin is Grumpy! We have a very tight IT ship internally, no thanks to me – I recently did a win10 client deployment and locked my users down, so they can’t just install any old stuff they want on the laptops. ► The Application Shortcut Folder default value (configurable in the Install Parameters) must contain reference to.

► The Application Folder default value (configurable in the Install Parameters) must contain a reference to either, ,, predefined windows installer folders. The Application Folder and Application Shortcut Folder, and all their sub-folders, will be automatically redirected to per-user/per-machine locations if certain configuration rules are met: In Install Parameters, set the install type to: Per-machine if the user is an #administrator, per-user otherwise.

If you asked yourself this question, then you should know that in order to allow the user to choose the #installation type at run-time, you need to add the InstallType dialog to the project (Dialog Editor Page).

'How do I make the #MSI package install per-user or per-machine?' ❓

Advanced installer msi