For patch management, ManageEngine uses its own scheme for numbering patches. With some reliance upon this, it is a bit more cumbersome to translate patch numbers from CVEs to MS KB bulletin IDs to ManageEngine patch numbers for reporting purposes. It is possible to search for patches by MS KB number, but the system is better at finding them by ManageEngine patch number.
A second item we find a bit frustrating is that it can be a bit difficult to keep third party patches updated in the self-service portal. For example, if you publish [application] version 1.3.5 to the portal, and then version 1.4.2 is released, there's not an easy way to have the system automatically replace the older version of the software with the newer version in the portal. It would help to reduce administrative overhead if this could be automated somehow. This is especially applicable to one-off programs that remote users without local admin privileges may require on the fly (for example teleconferencing applications and plug-ins).
Finally, we like to use the product as a central repository for inventory, however it does not have the capacity to inventory anything other than computer systems that have the agent software installed. Review collected by and hosted on G2.com.