Quantcast
Channel: LANDESK User Community : Document List - All Communities
Viewing all articles
Browse latest Browse all 6338

What logs will help me troubleshoot AMT/vPro issues and where are they located?

$
0
0

Client Side Logs

 

Log: AMTMon.log (not used in LDMS 9.5)

Location: C:\Program Files\LANDesk\LDClient 

Purpose: Checks the vPro chipset to see if it is provisioned or not. Send a notification to the core for provisioning.

 

Log: AMTConfig.log

Location: C:\Program Files\LANDesk\LDClient

Purpose: Initial configuration log

 

Core Side Logs

 

Log: AMTProvMgr2.log

Location: C:\Program Files\LANDesk\ManagementSuite\log

Purpose: Main provisioning log for all vPro provisioning

 

Log: AMTDiscService.log (not used in LDMS 9.5)

Location: C:\Program Files\LANDesk\ManagementSuite\log

Purpose: Good for HELLO packet problems. Some communication is also logged.

 

Log: AMTConfigDLL.log

Location: C:\Windows\Temp

Purpose: Web Service Log that's good for problems during the move from UDD to the database or the client config web service call. Used with console redirection as well when talking to the "LANDesk Console Redirection Service" (ipmiredirectionservice.exe) on the core server.

 

Log:AMTConfigDLL.log

Location: %temp%

Purpose: Logs information regarding commands sent to the client. (Example: Right-click "Intel vPro Power On"

 

Log: ServerSetup.log

Location: C:\Windows\Temp

Purpose: Web Service Log. Used in conjunction with AMTMon.exe on the client for auto provisioning.

 

Log: IpmiRedirectionService.log

Location: C:\Program Files\LANDesk\ManagementSuite\log

Purpose: Used in conjunction with console redirection (Intel KVM, etc.)


Viewing all articles
Browse latest Browse all 6338

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>