Ninite helps us patch 3rd party applications, and complements CM's Windows and MS Office patching.
Both CM and Ninite can patch select applications which already exist on a computer, however they got installed. The table below lists some ways they differ operationally.
- By "CM", we are also meaning the use of WSUS in CM to pull in packaged updates coming from Flexera for systems put into "managed systems" groups.
Criteria | Ninite | CM | Notes |
---|---|---|---|
Number of apps patched, if already exist on system | Many, many apps patched. | Firefox, Flash, iTunes, Java, and Chrome patched. Others? See right => | Where does Cornell document CM's currently patched 3rd party apps? Process to add? All packaged by Flexera? |
Timely availability | Immediately available, and we control directly | Sometimes protracted delayed availability. And then staged deployed over 1.5 weeks via first a test group, and then on to all "managed" systems. | What gates initial availability from CIT's Managed Desktop (MD) group? (Why would there be much of a Cornell-side availability delay, especially as compared to Ninite? |
Visibility of outcomes, and ease of ad hoc review | Clear, fast web-based view by authorized IT staff. | CM has report capabilities so if crafted to meet needs, swell. Less so for ad hoc query interests. Flexera reporting back is NOT visible to TSPs, right? | What value might Flexera's reports have to us TSPs managing systems? |
Infrastructure requirements | None | AD and CM. AND must be in a group accepting all Windows/ Office updates. | For sensitive or research machines, CIT's updates are often not appropriate. |
Reliability | Pending. Presumed good. | Data points: Firefox will often install 32-bit version on systems with a 64-bit installed(?!). Firefox will sometimes "update" to an OLDER version(?!). | |