Actually, related to this somewhat a perhpas rhetotical question.
I was wondering why companies the size of Dell have not adopted a process naming standard using a prefix or suffix that would at least allow one to associate a process as at least appearing to originate with software of that company?
I know this wouldn't keep deviants from hijacking a process.
A name like "agent.exe" might just as well be named "generic_process.exe".
I tried disk cleanup, but it didn't help. My agent.exe seems to be related to " Installshield update service". It is grinding my computer to a halt. How can I get rid of it?
Interesting, Your symptoms some familiar. These days once I see agent.exe hogging the system, I reboot and it goes away. Neverthess with your info I searched the web and discovered the following from DMorriseau on
"You might want to check the settings you have set up for the Program Updates in Control Panel as to how frequently it checks for updates and which applications are being checked. Since this is a terminal server that appears to be used for production, you might want to consider turning off automatic update checking and do it manually."
My machine is a laptop. I typically shut it down at night, I checked my autoupdate settings and discovered
that the update was scheduled for 3:00 am. The chance that the machine will be off at that time is probably
nearly 100%. I wonder if there is another threshold where if an update hasn't occurred in so much time, then an update is triggered anyway.
The docs for autoupdate suggest that one submit update manually at the end of the day. The machine can be
set to shutitself off once that task is complete. I do something similar for big downloads/uploads.
I just did a reboot and agent.exe has not come back. I actually had to hold the switch to turn off the computer because the Start menu would not even come up. I don't know what changed, but the computer is much better. I have the Task Manager minimized so that I can monitor the CPU usage. Maybe I can correlate agent .exe with a program if it returns. Wish I know what was causing it.
atthecorner
4 Posts
0
August 11th, 2006 13:00
I was wondering why companies the size of Dell have not adopted a process naming standard using a prefix or suffix that would at least allow one to associate a process as at least appearing to originate with software of that company?
I know this wouldn't keep deviants from hijacking a process.
A name like "agent.exe" might just as well be named "generic_process.exe".
-m
KissFan73
87 Posts
0
August 14th, 2006 18:00
Just curious.
normbarb
14 Posts
0
September 22nd, 2006 01:00
atthecorner
4 Posts
0
September 22nd, 2006 02:00
http://community.installshield.com/showthread.php?t=149852
"You might want to check the settings you have set up for the Program Updates in Control Panel as to how frequently it checks for updates and which applications are being checked. Since this is a terminal server that appears to be used for production, you might want to consider turning off automatic update checking and do it manually."
My machine is a laptop. I typically shut it down at night, I checked my autoupdate settings and discovered
that the update was scheduled for 3:00 am. The chance that the machine will be off at that time is probably
nearly 100%. I wonder if there is another threshold where if an update hasn't occurred in so much time, then an update is triggered anyway.
The docs for autoupdate suggest that one submit update manually at the end of the day. The machine can be
set to shutitself off once that task is complete. I do something similar for big downloads/uploads.
Good Luck.
normbarb
14 Posts
0
September 22nd, 2006 09:00