Quantcast
Viewing all articles
Browse latest Browse all 1968

How to force OME to update the Patches needed by clients

So we're trying to use OME to monitor our hardware and see what they are out of date on as far as BIOS, Firmware, Drivers, etc.  Our problem, and many people's problem from what I've read so far, is how to get OME to update it's list after patches are applied.

I just installed a patch for a SAS device which OME said was successful.  I then restarted all the DSM services on the client and did a new inventory /status from within OME, and it was still reflecting the package was out of date.  I then remoted into the client to check and found that in OMSA the new version was listed so it did install fine.

I then installed a Network card patch which OME said failed although the OME log said it worked with code 2 because it needed to reboot.  After the reboot OME still had the old version but OMSA now had the new version so it did work.

If I have to remote into each machine every time (or run OMSA for each machine) to see it patches worked that kind of defeats the point of using OME since I have to go touch every machine manually.

Does anyone have a guaranteed way of getting OME to update it's information?

Thanks.


Viewing all articles
Browse latest Browse all 1968

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>