It looks like installing it on an Exchange mailbox server (in an Exchange DAG) caused the Information Service to shutdown briefly....which cased database failovers in the DAG, which made our Exchange admin unhappy.
We use the Solarwinds agent for all our Windows servers. We generally install it using SCCM to automate the installs and have done that on hundreds of Windows servers of all sorts of flavours from Windows Server 2008R2 to Windows Server 2016. This is the first time I've seen it cause a disruption.
Anybody have thoughts on what circumstances could lead to disruption by installation of the Solarwinds agent?