0 Replies Latest reply on May 7, 2009 8:59 AM by DanHam

    Information mismatch - EPO vs Client

      We are running about 500 machines on 3.61, and in some instances when you look at client node properies for DAT/agent etc info and check against the actual client machines, they are different. So when running compliance reports we have machines showing far behind the current update, but then we check them, they are OK.

      Rather is there any consistent reason why this happens and is there a quicker method to correct this other than uninstall/reinstalling the CMA?

      It doesnt happen alot; maybe 5% of the total, but its annoying, and the "refresh" option on the server console does nothing.

      Any insights are appreciated!