Identity collector realistic requirements question

[Vladimir]

Since Identity Collector is, realistically, the only viable option for Identity Awareness, I am looking into deploying it for one of my clients.

Reading the requirements section / Best Practices, I am seeing following:

A minimum of 12 CPU cores

A minimum of 16 GB of RAM

A minimum of 60 GB of free disk space

...and the CPU core count seems to be absolutely outrageous and the memory allocation is way too generous, for the client that has less than 100 employees.

Can someone share their experience with Identity Collector in SMB environments and what would be a more realistic hardware (or virtual hardware) allocation to the servers hosting it?

Thank you,

Vladimir

[Wolfgang]

We are running without problems for a customer 200 clients, running as service on one of the domaincontrollers. 4CPU, 12GB RAM, 80GB disk. Virtual system. Most of the rules are user based, no problem at all, no performance problem seen.

[Vladimir]

Thank you! This sounds more inline what I would've expected. Pretty sure that IDC will be deployed on domain member servers, due to client's security requirements. In which case it'll likely use even less RAM. My last run-in with IDC still required LDAP Account Unit to be configured (using AD account with Log Reader permissions). DO you know if it is still the case?

[Wolfgang]

Our small customer has no requirements and keep it simple as possible and they don‘t want to pay for more  licenses 😉

The needed user rights for the IDC are described in the documentation, it has to be member of the event reader group. LDAP account unit is still needed, you need this to browse the ActiveDirectory to add groups or users to access roles. That‘s nothing what the IDC does, IDC matches only logged in users and their actual IP address and send this information to the gateway.