Endpoint Protection

The site status report keeps showing that our main SEPM servers memory usage is 179% or some other ridiculous number. Is it just a reporting problem on that server is there something that needs to be fixed?

Is your server consistently paging memory to disk? not enough RAM?

That will be slow and is not ideal.  I imagine the report is telling you that you are using 179% of your physical memory, meaning that if the server has 1GB, you are using an additional 800MB of virtual memory.

Not a show stopper, but again not ideal.

I agree with rwessen. It could very well be giving your correct numbers if you have a low amount of RAM. Is this slowing down the SEPM at all or is it still running smoothly. If it isn't a reporting error I would think a usage of 179% would slow down the machine considerably (you would definetely notice i think). Post back if you could with your hardware configuration on the machine.
Cheers,
Grant

What is the server specifications? RAM?

It's a VMWare server running 1GB of RAM but I have an identical machine with the same SEPM installed, same hardware and do not have this issue.

Well idealy running something in VMWare "should" be the same as a traditional machine, but there are always other bottlenecks and such that will not let it run exactly the same. How is this machine running? Is it laggy? Upgrading the memory should resolve this issue, but again if you are happy with the performance, then don't worry about it but I don't think it is an error in reporting (to answer your origional question).

I just checked in with one of our tech guys who is running the SEPM in VMWare as well. He has 512mb of RAM dedicated to it (which is well below recommended) and is reporting almost 200% usage. The minimum requirements are 1GB with 2GB - 4GB recommended (especially if you are also running and embedded database). Just thought you might want confimation on the 179%.
Cheers,
Grant

in my experience 1GB is never enough for a SEPM, I recommend at least 2GB, up to 4, particularly if you have the DB on the same machine. SEPM runs tomcat, which is java and java LOVES memory. The embedded DB seems to be a little less memory intensive, but default MS SQL install will take all the memory you let it. It does this to cache queries and speed up SQL.