Description
Communication between the core and the agent is vital to many portions of LANDESK. Knowing that the core can connect to the client, on the right port, and receive a good response can make troubleshooting a lot easier. The LANDESK agent in many ways can be used as a basic web browser and can help with resolving problems with:
Remote Control failing to connect
Software Distribution
Invoking a Security and Inventory Scan from the Console
Agent Status (Icons in the console) failing to display
and much more...
1. Connect to the web server and see a LANDESK Management Agent title bar in a web page.
HTTP://Computername:9595
2. Perform an CBAPing and get the Computername, Operating System, and Inventory ID as a response.This is a good test to make sure DNS is working as well and the machine in question is really the machine you are attempting to connect with.
HTTP://Computername:9595/allowed/ldping
3. Connect to the Remote Control Service. (Note: The service doesn't have a web page so the following screenshot is a normal response)
4. To view running providers: (Note: A much longer list will be displayed if Real-time Inventory and Monitoring is enabled on the client. Without the longer list Alerting/Monitoring will not function properly)
HTTP://Computername:9595/LDClient/ldprov.cgi/index
Inventory and Security Scans Invoked Through a Right-click in the 32-bit Console (Process):
Process and log entries are located below. The following document has more detailed information on how to test/fix this functionality: DOC-5480
1. The 32-bit console makes a call to a webservice called corerequest.asmx: (Note: The 200 code in the line below indicates a success)
Example IIS log entry:
2011-11-03 18:48:40 POST /landesk/managementsuite/core/core.secure/corerequest.asmx - 80 SNOOPY\ADMINISTRATOR fe80::94c8:7e37:5edc:768d%11 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4927) 200 0 0 5060
2. The webservice contacts the LANDESK Management Agent Service on the client. (C:\Program Files\LANDesk\Shared Files\residentagent.log) The Management Agent Service then launches Servicehost.exe:
Example log entries:
Thu, 03 Nov 2011 10:08:13 1772: Entering ServiceHostThreadProc, thread id 3012
Thu, 03 Nov 2011 10:08:13 1772: Handling request from 192.168.47.210
Thu, 03 Nov 2011 10:08:13 1772: Service host (process) 292 handlings request from socket 540
Thu, 03 Nov 2011 10:08:13 1772: Socket error 0 was classified as non recoverable
Thu, 03 Nov 2011 10:08:13 1772: Socket 540 closed gracefully
Thu, 03 Nov 2011 10:08:13 1772: Socket closed, client has disconnected
Thu, 03 Nov 2011 10:08:13 1772: Request handling complete
Thu, 03 Nov 2011 10:08:13 1772: Exiting ServiceHostThreadProc
3. Servicehost.exe launches the application in question. (C:\Program Files\LANDesk\Shared Files\Servicehost.log) (Note: Servicehost.exe uses vulscan.exe to launch an inventory scan)
Example log entry:
Thu, 03 Nov 2011 10:08:13 292: Service Host Started, Host jtrafele-xpsp3.localdomain:9594, Peer 192.168.47.210, IP Address 192.168.47.147
Thu, 03 Nov 2011 10:08:13 292: Public key path C:\Program Files\LANDesk\Shared Files\cbaroot\certs
Thu, 03 Nov 2011 10:08:13 292: X509 Authentication via d301c06e
Thu, 03 Nov 2011 10:08:13 292: Request Received "POST /services/exec HTTP/1.1"
Thu, 03 Nov 2011 10:08:13 292: Exec: Exec: Launch request <"C:\Program Files\LANDesk\LDClient\vulscan.exe" /id=9 /run ldiscn32.exe /NTT=SNOOPY:5007 /S="SNOOPY" /I=HTTP://SNOOPY/LDLogon/ldappl3.ldz /NOUI -f> (sync 0, timeout 300)
Thu, 03 Nov 2011 10:08:13 292: EOF encountered parsing HTTP headers, client closed connection.
Thu, 03 Nov 2011 10:08:13 292: Service host has finished