Lastly you can use a special Ninite network installer.exe which you’d use if you want to manually install it on a machine (non-domain joined for example) msi available so you can script something together (GPO, SCCM, PDQ Deploy, MDT, etc) There are a number of ways you can install the agent: Installation literally takes seconds and no reboot is necessary. In typical Ninite fashion, the agent is only a few hundred Kilobytes. What I really like about the new management interface is that because it is so easy to use I feel confident giving my colleagues on the service desk staff access to run wild with it.īelow I will briefly go over the installation of the agent and then move on to summarise the different tabs in the Ninite Appsheet web interface. You can also set exceptions here so don’t worry guys, that finance application will still have access to Java 6 (kill me now). You now have the ability to set policies so that updates are checked for and applied hourly. Policies!!! I’m really excited about this one.Easily patch a single application on all machines or all applications on a single machine – the flexibility to patch your machines makes life a lot easier here.
You can instantly see an overview of your estate in the Overview tab
I don’t mean to make it sound like scripting it to make it work in your environment is difficult – it really isn’t but sometimes it can be tricky to implement for machines that are either not on the domain or simply not on the premises to receive those updates. To automate the process of deploying or updating applications you previously had to script something together and schedule the. exe which you can either run by double clicking or by using switches in the CLI (NinitePro.exe). Up until now, Ninite has been completely agentless. Ninite has long been my number one tool for deploying, updating and removing popular 3rd party applications… I especially enjoy the feeling of removing Flash and Java from any where I can get my hands on 🙂
0 kommentar(er)
