The initial setup was straightforward and so was the implementation of the initial AD driver. It became a bit harder when we wanted to change user and group placements. Nothing you can't learn from docs and testing it yourself thoroughly though.

The initial deployment of the environment typically takes about a day to a day and a half to install and configure all the servers. Integrating applications can vary, with easy and well-documented integrations taking around 40 hours, while more complex ones may take up to 80 hours or more. However, integration with applications can vary in complexity, depending on their documentation and APIs. We prioritize integrations based on customer needs, starting with HR systems and adapting to their specific requirements for user configuration.

Typically, a deployment team consists of up to four people, depending on project size, with expertise in operating systems and integration. For ongoing management and maintenance, at most two people are required to monitor servers, and integrations, and address any issues that arise.

The initial setup was straightforward. The setup alone takes a couple of hours. Full deployment time depends on the customer and what they need.

The setup process is complex, attributed to our long journey with the product over more than ten years. A lot of capabilities were not available by default at that time. 

While installation is straightforward, customizing the system to meet specific needs and performance requirements demands expertise.

We use an on-premises deployment model.

The IDM engine setup is quiet straightforward it you master product. The Role base & workflow module is more complexe and the reporting module installation must be definitely improved.

The installation took a few hours. The installation was quite straightforward.

Its implementation is hard. It should also be easier to install. There should be an easier testing system for applications for students or consultants to try it themselves. If we are doing just testing, it's complicated because they are basically supporting SuSE and Red Hat. If we are doing testing, we don't want to pay for the server systems. There is no documentation and information about how to install it with some other Linux versions. There is no documentation for implementing it on other systems.

The deployment duration depends on what we are doing. We are not doing production systems. We are doing production-like teaching environments. We are basically running systems that can be production but the use is just for training purposes. Later this year, we are doing production environments. We are doing the whole process of how to create implementation, how to implement it with some applications for IDM, some applications with access management and SSO, and so on.

The initial setup of NetIQ Identity Manager is straightforward.

Very complex. Again, it does not run very well on Windows and we required a lot of customization to meet our business objectives.

The initial setup has medium complexity. It depends. The previous version was more complex. Now they've made it better. They knew that the tool was complex so they tried to enhance and simplify the installation. I would say it's not too hard today to get you going on the basics. The more approvals and workflows and the more components you add to it, the more complicated it gets and you need more specialized people. You just make sure that you train your personnel.

If this product was more widespread and people knew more about the language then you wouldn't have this issue about when you need to add people to the system.

IM products are someway framework solutions. Deploying a solution to an organization requires co-operation with many stakeholders and knowledge on the systems to integrate.

With a normal integration, for example with AD, it's a matter of configuration, but integration with the HR system it's a matter of designing processes - for example if the system is not a standard out of the box system.

For us the installation was easy. However, we are an IT company that understands what we are doing. I would consider the solution not to be easy to install if someone does not have the experience.

Given that identity management is itself an IT specialization that requires a lot of knowledge, the implementation is simple. That is to say, if it is clear that the tool is intended, sinceneeds can vary from a simple synchronization of keys to a complete and automated process.

Initial setup is straightforward if done by vendor requirements.

Any IDM will not be simple unless the environment is simple. We have a large complex environment, so setup was complex. Any IDM would have this.