Creating an Intel SCS Service (AMTConfig) Log a.k.a. How to Enable Debug Logging
Having issues with the AMTConfig service and don't mind reading debug logs, or you need to escalate an issue to Intel or Altiris? The following process can capture debug logging for the AMTConfig service.
Here's how to enable logging for the Intel SCS Service (AMTConfig) in conjunction with Out of Band Management Solution and Provisioning.
Debug logging of the SCS service and the SOAP API web service components is turned off by default, which means that the log files (scs_win_server.log, scs_server.log) will not be created.
Turn on Debug Log
Create the following registry key on the service's machine:
HKEY_LOCAL_MACHINE\SOFTWARE\Intel\AMTConfServer\Log\LogLevel – Optional values 'V' for verbose, 'W' for warnings and errors, 'E' for only errors.
If the above registry key is not created then the debug insertion is turned off.
Set the Log File Name
- HKEY_LOCAL_MACHINE\SOFTWARE\Intel\AMTConfServer\LogFile – full path of the web service's log file (including extension).
- HKEY_LOCAL_MACHINE\SOFTWARE\Intel\AMTConfServer\LogServerFile – full path of the SCS service's log file (including extension).
After changing the registry settings, the AMTConfig service must be restarted to implement the new settings.
Second, there might be issues with insufficient writing privileges to the folder specified at the registry (try C:\xxx.log).
Nevertheless, the following registry setting causes the SCS service to use its defaults (C:\\scs_server.log):
[HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\AMTConfServer\Log]
"LogLevel"="V"
About Endpoint Management Community Blog
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
Different than OOBM GUI settings?
Is this different than the AMT logging options available in the OOBM GUI? There are options to change the logging level, and a view showing the log (as well as controls to export it, etc). One of the logging levels is verbose (debug)...
Shawn Faucher | Lead PC Technician
Armstrong Teasdale LLP
Web Service versus AMTConfig Service
The logging is different. The debug logging detailed here is directly linked to the AMTConfig service, while the log in the GUI shows the Web Service logging. The two may have similar entries, but they are from different sources.
If Intel can chime in and confirm or deny, that would be helpful!
Joel Smith
Symantec Services Group (SSE)
Sr. Principal Support Engineer
GUI interface vs. SCS logs
To check the status of incoming hello packets, provision process, and so forth - the GUI interface is easier and does not require a registry edit.
Within the Altiris OOBM interface, under Configuration, Provisioning, then General - set the logging to errors, warnings, or verbose.
Under Configurations\Logs - the administrator can check Action Status, Logs (which is set per previous sentence), and Security logs. If the logs are set to verbose mode, the administrator will see each successfully provisioned system - you will note that a new PID\PPS is created along with other actions.
If more indepth debugging is needed - the tech tip above which creates the SCS_server.log and so forth could be used. However, this is best interpreted by the development\support teams. It is also well complemented with other system logs, mini dump files (from Dr. Watson), and so forth.
The opinions expressed on this site are mine alone and do not necessarily reflect the opinions or strategies of Intel Corporation or its worldwide subsidiaries
Would you like to reply?
Login or Register to post your comment.