Anyone have some advice on how to resolve this once and for all? I'm tired of seeing this constant warning. I imagine the solution is to somehow give the primary polling engine's machine account rights to read the remote registry on all of the polling engines, but I'm not sure if that would work and how to go about that. So it's kind of a damned if you do, damned if you don't situation going on. Net version on the remote polling engines, but then I get a warning from the SolarWinds installer about using a 'Domain Admin Account' with the resolution being to use a local non-domain account.

If I use an AD account (and the AD account I use does have local admin privileges), it can detect the. I'm guessing that the local non-AD account can't read the remote registry's of the remote engines. The issue seems to be that for upgrades and installs, we use a local (non AD) admin account to run the installer, which is recommended by the Admin guide. The Remote Registry service is running on all of the APE's and AWE's. Net version on the Scalability Engines (Additional Polling Engines and Additional Web Servers).

We have 3 separate Orion Environments (Dev, QA, and Production), and whenever I run the upgrade installer or look in the 'My Orion Deployment' section of the web console, all of the environments complain that they can not detect the.

Checking .net version