This blog is divided into 3 sections - understanding the basics,

addressing common Intel SCS errors

, and

how to generate an Intel SCS debug log.

 

If only solutions were perfect, errors resolved automatically, and tuning was never required nor needed. Then again, that's what many of us get paid to do and handle. The intent here is to focus on common Intel® vPro™ configuration and provisioning errors with Intel Setup and Configuration Services (SCS). More importantly, the article intent is to provide some insight on the correction needed or tasks to handle common errors.

 

The Basics

Deploying Intel® vPro™ enabled solutions presents many working parts. In a lab environment - these "always" work well. In a production environment, determining the cause of an error could be difficult. Generally speaking, to isolate the scenario take into consideration the management console, the vPro configuration services (e.g. Intel® SCS), the OEM firmware and drivers, and the infrastructure. The lab environment comes in handy to isolate components and aspects, especially when so many variables are present.

 

In stepping through each item, consider the following basic points:

 

  • OEM hardware and drivers - Check the update page for the latest BIOS and Firmware on the platform. The BIOS update will often include the Intel® AMT firmware. The drivers to be checked are mentioned Management Engine Interface (MEI), Local Management Service (LMS), Serial over LAN (SoL), and User Notification Service (UNS).  NOTE: UNS applies to AMT 3.0 and higher versions.

 

  • Intel® SCS version - Don't know what version if running?  Check the AMTconfig service properties or version listed in the SCSconsole.  More on SCS and AMT versions

    here

    .  Version 3.2 is the latest.  If running version 1.x, an update to version 3.x is recommended.  Check first with preferred system management vendor on supported setups, upgrade paths, and so forth.

 

  • Infrastructure - Ensure a ProvisionServer DNS record exists for the target DNS domain, and that this pointer record resolves to the server running AMTconfig (e.g. Intel SCS).  Ensure proper resolution of the DNS entry for the FQDN of ProvisionServer (e.g. ProvisionServer.company.com)

 

  • Verbose Logging for SCS events - Within the SCSconsole, access the  Change the Log Level to "Verbose" mode. This will log all informational, warning, and error messages and events in the SCS log. This is good to see when a hello packet is received, when the ProvisionServer attempts to provision the target system, and so forth.  When changing this setting, you may also want to decrease the log retention level to a few days or shorter timeframe than the default value. Depending on the number of systems managed or attempting to provision, setting the log level to "verbose" may rapidly grow the size of the IntelAMT database. 

 

Image of SCSconsole and setting logging to verbose mode !Verbose logging.gif!

Image of SCSconsole viewing log events in verbose mode !SCSlog.gif!