![]() |
|
#26
|
|||
|
|||
|
I have tons of workstations with huge performance/startup delays because of the startup scan. Is there a way i can disable it in the admin console so i can push out a new config file? Don't really feel like changing it manually on 500+ computers.
Thanks |
|
#27
|
||||
|
||||
|
Well, am I the only one not noticing any performance hit with the startup scan turned on? I use the default settings untouched (except for the startup splash screen off) and only after seeing this thread is that I knew about the startup scan. I'm happy with v4.2 64bit.
|
|
#28
|
||||
|
||||
|
FYI I presented this discussion back in November.
http://www.wilderssecurity.com/showthread.php?t=257685 That thread discusses how you can lower the priority. The startup scan is most noticable on older, slower machines. Newer dual and quad core systems with plenty of memory is not as noticeable. |
|
#29
|
|||
|
|||
|
Quote:
Hi Olavski, I just recently addressed this issue myself on some of the older workstations within the company. What I did was create a new configuration file, and created 2 new scheduled tasks. Both called Automatic startup file check (one for user login, and the other for on successful update.) With these scheduled tasks, I changed their default priority from Lowest to When Idle. Doing this resolved a lot of complaints about performance. Don't forget to click on the "Change ID" button to override ESET's defaults. Hope this helps! ![]() JC
__________________
Geosoft. Operating EEA 5.x on 190 nodes, across 6 satellite offices on 6 ERA 5 servers. |
|
#30
|
|||
|
|||
|
Quote:
That looks like an option i might give a try, thanks. |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|