Hello,
We lately have found that compliance status doesn't update after deploying new packages.
For example, we pushed a new Lifecycle controller version to a bunch of servers. After, we did an inventory update and the servers were still non-compliant. However, the package was installed (confirmed when we tried to install it manually). Restarting DSM services on the remote servers didn't helped. Only a server reboot fixed that. Obviously we can't reboot all our servers just to update the compliance status.
OME is 1.3, managed servers are Win 2008 R2 or 2012 R2 using OMSA 7.3 or 7.4.
JP