In Software Center (Application Model Deployment).

Once SubProcess (software install) completes and goes away, Sends “Stop-Process” signal to stop all Ninite.EXE processes.Monitors the SubProcess (MSIEXEC.EXE or TARGET.EXE).Waits for either MSIEXEC.EXE or TARGET.EXE Subprocess of Ninite.exe to start.Then launches the Ninite Installer.exe stub file which downloads the actual app installer and launches.The script then Downloads the Ninite.exe stub file from.You choose the App you want to install from the predefined list built into the script.Why would you want to do this? Automation, being able to leverage Ninite's Free Personal installers in the context of a Task Sequence or App Model deployment in your Personal ConfigMgr Home Lab. With the Pro version, you don't need my work around.īasically my solution is a powershell wrapper that downloads the ninite stub installer, runs the installer, waits for it to finish, then kills the installer dialog box. Please remember, this is for your personal lab, if it is for anything other than personal use, you’d have to get the Pro version. Awesome right? They figured out all of the command lines. Basically, you go to the website, you check the box next to the app(s) you want, and click 'Get your Ninite'. Also use it to help setup how many friend's and family's computers. I've been using it for years, when I get a new computer, or just want to make sure my apps are updated. If you're not familiar with, it's pretty awesome. Powershell to the rescue! It doesn’t make it completely silent, but it will allow you to automate it to work with the ConfigMgr App Model during OSD and Post OSD. What, you don't want to pay for pro when it’s your personal lab? I hear you.

How about, you leverage ’s ability to dynamically install the latest version of the app every time? Now you're asking, 'Isn't the command line version that supports silent install cost money?' Yes, yes, it does, to use ninite’s silent install, you need the Pro version. You probably don’t have time to keep your personal lab app deployments updated, so you keep deploying old versions. So you add Chrome, Reader, and a couple others (NOT JAVA). So you have a Personal ConfigMgr lab, but you want to add some app deployments to better simulate your actual environment.

Ninite chrome