...
Criteria | Ninite | CM | Notes | |||||
---|---|---|---|---|---|---|---|---|
Number of apps patched, if already exist on system | Many, many apps patched. Including 100% of the ones CM currently patches. | 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. | RESEARCH-specific: For sensitive or research machines, CIT's updates and methods 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(?!). | ||||||
Use of campus | Yes | No | If off campus AND use VPN, then CM may work. | |||||
Use on campus 10-space areas | Pending. Updating works if use proxy storage (have not yet tried this). And initial call-in of a client must be on full-space to tie client to our collection. (Subsequent communications through proxy storage?) ITSO added all-but-one of the Ninite-related domains and we must now confirm sufficient. | Yes. | RESEARCH-specific concern. |