5 out of 5.0, Reviewed Oct 24, 2016
IBM was fully engaged before, during, and after our implementation of their product. We continue to have regular touchpoints with IBM product support.
The product is very stable and developers tend to like using it. It is easy to make incremental changes.
Finding IT talent in the Service Gateway/API Management space can be difficult.
Understand the technical space with regard to knowledge resources.
4 out of 5.0, Reviewed Dec 9, 2015
We are using IEM for clients and it has worked so well that we are looking to deploy it for Servers as well. The user community and forums are great resources. Solution requires training and should be deployed in a Pilot-to-Scale program.
You'll love the features and functionality, but incremental licensing costs could be high, so choose add-ons wisely. Plan your Infrastructure architecture.
Breadth of features.
Fixlet scripting language is product-specific, I wish they used common scripting internally.
Provide more training to administrators prior to completing the rollout at scale.
Strong product with many capabilities.
IBM is head and shoulders above others in supporting their customers.
Fairly simple, but highly recommend working closely with IBM field support or third party integrator.
3 out of 5.0, Reviewed Dec 7, 2015
Works well for managing Windows clients. Good tool for asset inventory, reporting. Doesn't do much for UNIX and Linux clients.
Use IEM for inventory management, but use open source tools like Puppet or Chef for automation.
The IBM team did their best to answer some of our questions around UNIX and Linux support.
4 out of 5.0, Reviewed Oct 28, 2015
IBM has the local expertise to implement this product.
Ensure the vendor has local expertise support to drive the implementation.
The product has ease of use and less effort in mainteance. Vendor's expertise in implementing the product is also good.
3 out of 5.0, Reviewed Jun 15, 2015
Product does not easily do all we want...we can "make" it do what we want with it's proprietary programming language
Look at the total cost of ownership, look at what and where community expertise is (ie: what is ubiquitous in the industry - are there community support sites), look at where your organizational strengths are and leverage those... sometimes new technologies require building out an entire new skill set which requires more FTE (sometimes)
Now that it's installed, it does yield valuable endpoint information
It still required 3rd party integration... it does not do all we want it to (ie: puppet/chef-like config mgmt) and the response is always, you can "make" it do whatever you want by using our proprietary language.... the community support for this is not as high as others...
Been clearer on the initial installation/implementation requirements and clearer on the scale out requirements.
I would likely have considered Microsofts approach and not worried about the need for 3rd party integrations to complete the EM strategy
4 out of 5.0, Reviewed Jun 9, 2015
Fairly satisfied, works as advertised.
Have a good patching policy.
Hire experienced engineers for this specific product.