cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
lumilux
Engaged Sweeper
I have a long scan time for the "Autorun" section (600-800 sec), which slows down our computer.
How can i resolve it and what is exactly scaned?
10 REPLIES 10
tlmjrd103t
Engaged Sweeper
http://www.lansweeper.com/forum/yaf_postst892_Login-script-not-running-under-some-logins.aspx

Thanks in advance!
tlmjrd103t
Engaged Sweeper
Glad I can be of help.

I have an issue of my own, though. Hope you will have a chance to take a look at my post.
Hemoco
Lansweeper Alumni
tlmjrd103t wrote:
Glad I can be of help.

I have an issue of my own, though. Hope you will have a chance to take a look at my post.

Which problem do you have?
Hemoco
Lansweeper Alumni
Thanks, I've seen this problem before and solved it for http://www.runscanner.net but didn't realise it also affected lansweeper.
tlmjrd103t
Engaged Sweeper
The first solution below worked for me. You can try to reinstall WMI if it fails. Hope this helps everyone!


Problem Description:
'Win32_StartupCommand' returns thousands of files (4000+) that look like they are comming from the windows system32 folder (C:\Windows\System32)

Cause:
If the windows registry string value "Startup" located at

"HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" has no value or points to a non-existant folder then the problem described above occurs. This folder can be pointed to a dummy folder that is empy to prevent this problem or you can set this value to:

"C:\Documents and Settings\Default User\Start Menu\Programs\Startup"



Other WMI Issues Can be solved by Reparing or Re-Installing WMI

See here for more info on repairing or reinstalling WMI:
http://windowsxp.mvps.org/repairwmi.htm
Hemoco
Lansweeper Alumni
open lsmanage
scan options/item wait time/autorun
lumilux
Engaged Sweeper
I check a different site with same result.
it seems this issue came after I did an update from 3.1 to 3.2
Where can I change the suggested settings?
Hemoco
Lansweeper Alumni
Lansweeper uses this wmi query on the client "Select * from Win32_StartupCommand"
You can set the "waittime" of this really high if you have problems with it.
lumilux
Engaged Sweeper
Only a few of our computer shows a scan time below 20 most of them above 100 up to 800