AMTconfig Service Failing?
Filed under:
Intel vPro Technology
3rd Party Products
Submitted by Terry Cutler on 30 April, 2007 - 11:42.
Update (July 2007): AMTconfig service 1.3 will resolve errors found in version 1.2. Please refer to Article 35954 on Altiris Knowledgebase. Hotfix posted at ftp://ftp2.altiris.com/Download/KB35954/
.
Original post: With an increasing number of Intel® vPro™ processor technology deployments in Altiris management environments, key learnings and ideas are starting to be shared. Here is one such example - if others have key learnings or requests - please comment or share.
In some environments, provisioning and configuration operations may fail to complete. The administrator may receive an error code of 137, or an error that a previous request has been queued yet does not appear to complete. Systems will appear as "UnProvisioned" yet will not move to a "Provision" state, even with a default profile enabled under the "Resource Synchronization" menu. The provisioning logs will show similar reports and errors.
If you are experiencing these types of errors - check the status of the AMTconfig service. This service performs much of the provisioning, configuration, and maintenance operations associated with the Intel® vPro™ processor technology platform. Development teams have been notified and are working on isolating\resolving the issue - the exact cause (whether environmental, application, .NET 2.0, or other) is being determined.
As shown in test and production environments - a current workaround is to set the service recovery options to restart the service automatically. The image below shows where and how this is done.
This applies only to version 1.2.3 of the service.
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
(10 votes)
- Login or register to post comments
- 3336 reads
- Printer-friendly version
Good post
Glad to see a post like this go up. We've been experiencing the 137 error you describe. We've also had 602 errors (clock sync worker exception) and problems with AMT grabbing the wrong FQDN for systems. We've had some success reducing errors by applying the latest bios & ME firmware for the HP 7700p systems we have.
Have you talked with Altiris support?
Have you talked with Altiris support for additional assistance? In the next article I'm working on (not the one I just submitted) - will be talking more about the Altiris provisioning interface. There's a maintenance option to sync clocks. Curious if this has been done.
Also - interested to know what BIOS, AMT firmware, and AMT drivers are loaded on system (Part 2 of the Enterprise integration articl will discuss this). Right now - HP systems are BIOS 2.09revC, AMT version 2.1.4.
In the process...
I believe the clock sync process is turned on (that is what is producing the error). I will have to double-check that on Monday.
We are in the process of talking with support. The first go-around we discovered the out of date bios, so we are in the process rolling out the update. The HPs we received came with 1.10 BIOS and 2.1.1 AMT. We are updating them to 2.10revA and AMT 2.1.3 which were in the latest BIOS softpaq for the dc7700p USDT.
Narrowed down our 137 issues
We've narrowed down our 137 errors. What seems to be happening is during the provisioning process AMT is grabbing a DHCP address, but by the time the HELLO packet reaches the server the client computer has booted into Windows and grabbed a different DHCP address, invalidating the first. The server then tries to respond to the HELLO packets via the wrong IP address and 137 errors ensue. This continues until the power is pulled from the PC and replaced, without letting it boot into Windows. AMT pulls a DHCP address again and provisioning then takes place correctly. Everything is fine after that.
Hotfix near release
Please review the KB Article at https://kb.altiris.com/article.asp?article=35954&p...
Download and Install SCS 3.2.1
When originally posted - this article referred to pre-OOBM 6.2 environments
With the current release of Altiris Out-of-band setup and configuration (part of OOBM v6.2.1035) - SCS 3.0.2.6.1 is included.
As stated at http://juice.altiris.com/node/4082 and http://communities.intel.com/docs/DOC-2032, it is strongly recommended that SCS 3.2.1 be installed. This is available from Altiris at http://kb.altiris.com - article#40076
After installing the update - ensure you check\update the SSL settings (see article http://juice.altiris.com/node/3690)