In terms of the product itself - no. Deployment of the product is very straightforward; there are a lot of resources available to assist you in finding the answer to any deployment question you might come up with. There is a large community of people working on IdentityIQ. If you come across a problem there’s always someone around that’s done that before and has suggestions.

The main challenge has been that each client’s environment is different; from the way in which they configure their ‘managed’ systems, to constraints imposed by the client’s SOE (standard operating environment), to the client’s infrastructure topology, to change control and migration processes and tools the client wants to/has to use.

One of the main challenges is for clients to understand and accept that IdentityIQ implementations are not a systems development/coding exercise; rather IdentityIQ deployment is more about configuration than coding.

We encountered major issues with the Active Directory connector caching configurations and concurrent major release upgrades. If you are running SailPoint 5.3, you need to update to 5.5, 6.0, 6.1, and 6.2 before upgrading to 6.3, it was a mess.

No issues encountered.

We had no issues with the deployment.

Yes - Some application connectors (namely Lotus Notes) - have some fundamental flaws. But the major issue was cleaning up, what we expected to be, authoritative data - specifically HR data, and users not in HR (eg. contractors, etc) and ensuring global consistency and adherence to standards.

Yes, of course. Every time, when you implement a project for a customer you will encounter some issues.  The primary question - how quickly the vendor will help you with issues, or how strong are the programmers and engineers in your team to find a solution in-house.

No, the deployment is pretty straightforward.

No, but we encountered some bugs after the implementation and they were fixed.

No issues encountered.

No issues encountered.