User-ID Agent placement (Domain Controller)

[Wildman85]

Hi all,

I've read the best practice guide and I can't see anything that says the agent SHOULDN'T be installed onto a domain controller.

Any experiences with that here?

We currently have the agent installed onto two Windows Server 2012 R2 member servers that are close to the DC's but will be retired soon and I need to evaluate my options. Just makes sense to put them on the DC's but am I not sure if there is a Palo recommendation not to do this?

Thanks,

[OtakarKlier · Accepted solution]

Hello,

In the past I have put it onto domain controllers without any issues.

Regards,

[TerjeLundbo · Accepted solution]

We have also installed User-ID agents on all our domain controllers (mix of Windows Server 2012 and 2016) without any problems.

[mharding · Accepted solution]

You absolutely can. In the case of the Credential Filter for phishing detection, you have to install the UserID on the RODC.

But there's also a train of thought that the bare minimum should be installed on the domain controllers because they hold the keys to the kingdom. The less software installed, the less vulnerabilties you'll have on the server. 

It mostly depeneds on your environment. Small office with six employees, I'm going to install on the domain controller. Large enterprise with multple domain controllers, I'll setup a seperate server close to to the domain controllers for UserID.