Quantcast
Channel: Ivanti User Community : Popular Discussions - Agent Deployment
Viewing all articles
Browse latest Browse all 8000

Installing agent off network adds 10 minutes to the install time

$
0
0

We have a script that runs after our systems are imaged that install several pieces of software and the system is not always on the network at the time.  The LANDesk agent is the first thing to install after a system is imaged and since 9.5 SP1 it is taking 10 minutes longer to install the agent (it is taking about 10-14 minutes to install where it only takes 5-6 minutes to install while on the network).

 

I ran procmon on a system off the network and found that there appears to be a 10 minute timeout trying to get the ResolveDeviceID and GetHashFile from the core server.  Note the agent was started at 9:46 and finally finished at about 10:02

 

Vulscan log (c:\programdata\vulScan\vulscan.log) entry retrying over and over again:

Fri, 15 Nov 2013 10:01:30 Action SOAPAction: "http://tempuri.org/GetHashForFile" failed, socket error: 11004, SOAPCLIENT_ERROR: 5.  Status code: -1, fault string:

 

Vulscan log (c:\programdata\vulScan\vulscan.log) entry giving up after 10 minutes:

Last status: Failed: No response from core

Self update Failure: Core did not return requested file hashes.  Error: 80004005

Fri, 15 Nov 2013 10:01:30 ERROR: Socket timeout of 600000 milliseconds was exceeded.  Giving up

 

softmon log (c:\programdata\vulScan\softmon.log) entry retrying over and over again:
Fri, 15 Nov 2013 09:59:13 Action SOAPAction: "http://tempuri.org/ResolveDeviceID" failed, socket error: 11004, SOAPCLIENT_ERROR: 5.  Status code: -1, fault string:

 

softmon log (c:\programdata\vulScan\softmon.log) entry giving up after 10 minutes:

Fri, 15 Nov 2013 09:59:28 ERROR: Socket timeout of 600000 milliseconds was exceeded.  Giving up

 

Has anyone else seen this issue?


Viewing all articles
Browse latest Browse all 8000

Trending Articles