Forefront/Windows Installer gone wild?
Has anyone heard of anything like this happening? On Monday afternoon, I had a 2008r2 server go haywire and eat up every bit of memory it had(and then some), the processor & disk usage was also much, much higher than normal. It was basically
dead. After a reboot, it was performing reasonably well, but was still extremely "busy" and by the following morning, had once again devoured all it's RAM & had become unresponsive. After another reboot, it returned to normal where it has remained
since then.
After doing some extensive research in the logs, I'm 95% conviced that this was all due to an attempt by Forefront to update it's definitions-which is logged in event viewer as failed. My theory is that after the 1st reboot-Installer picked up
where it left off & tried to update them again-and failed for a 2nd time.
Following the final reboot, Forefront was able to successfully update the definitions and there was finally a "windows installer has entered the stopped state" event in the log-and everything was once again happy.
Anyone ever heard of something like this happening? I have over 100 servers & had just this 1 freak out on me.
February 2nd, 2012 1:45pm
seek assistance here
http://social.technet.microsoft.com/Forums/en-US/FCSNext/threadshttp://www.virmansec.com/blogs/skhairuddin
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2012 2:25am
seek assistance here
http://social.technet.microsoft.com/Forums/en-US/FCSNext/threadshttp://www.virmansec.com/blogs/skhairuddin
February 3rd, 2012 10:18am


