Lansweeper logo
Home Download Features Demo Buy now Help Support forum
 
    Most requested support articles:
  Lansweeper troubleshooting guide.
  The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
  WMI Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
  How to configure the windows firewall using group policies.
  Support:  
 support@lansweeper.com  
Skype: Lansweeper  
  Mo-Fri 9h-17h CET  
Welcome Guest Search | Active Topics | Log In | Register

Untag as favorite
LSpush takes a while on newer computers
Jono
#1 Posted : Thursday, February 02, 2012 10:59:29 PM

Rank: Premium user

Groups: Member, Premium Users
Posts: 41
Location: Metro Detroit
Hello,

I have LSpush running as an item in our logon script that is initiated by Active Directory. LSclient used to be done in just a couple of seconds. LSpush also takes just a couple of seconds on older computers (WXP with IE8), but on newer computers (W7 and IE9) it takes up to a minute or more to complete.

Is this a problem or is this expected behavior?

Thanks,
Jono
Lansweeper
#2 Posted : Friday, February 03, 2012 10:40:36 AM

Rank: Administration

Groups: Administration, Premium Users
Posts: 10,378
LsClient does not perform any actual scanning, so it is normal for LsPush scans to take longer. A minute does seem unusually long however.

Could you try running LsPush manually on one of the affected machines.
- First, run it with the /file parameter and see how long it takes for the scan to complete.
- Then run LsPush with direct server connection and the /showresult parameter to verify how long it takes for the server connection to be established. You will receive feedback as to whether or not the connection succeeded.
Jono
#3 Posted : Friday, February 03, 2012 4:21:22 PM

Rank: Premium user

Groups: Member, Premium Users
Posts: 41
Location: Metro Detroit
Hello - Thanks for the reply.

The times turned out as follows:
- "LsPush /file" takes about 8 seconds to complete.
- "LsPush server /showresult" takes about 10 seconds to complete.

If I run the logon script (which does the tasks below) from the logon server's NETLOGON folder after the computer is completed booted, it takes about 14 seconds, the last 10 seconds being LsPush.

The logon script doesn't do much:
- Sets the time
- Removes mappings to 2 network drives
- Maps those 2 network drives
- LsPush

Anyway, perhaps the problem is that the computer is still going through its bootup process which causes the logon script the run slowly as it competes for client resources. The computer that I'm using to test has an Intel i5 2.53 GHz processor (which is dual core), and 4GB RAM; the OS is W7 32-bit.

Does that sound like a logical explanation for it?

I guess it's not ultimately too much of an issue as LsPush eventually succeeds in every case.

Jono
Lansweeper
#4 Posted : Tuesday, February 07, 2012 2:51:45 PM

Rank: Administration

Groups: Administration, Premium Users
Posts: 10,378
Most likely the delay is indeed caused by the computer not being fully booted and the necessary WMI classes not being available yet.
Users browsing this topic
Guest
Untag as favorite
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Contact: E-mail Lansweeper - Skype : Lansweeper
Copyright 2004 - 2011 © Hemoco bvba