"Properties Script Failed" error quick guide for Out of Band Management Solution for Intel vPro

Article:TECH37701  |  Created: 2007-12-06  |  Updated: 2008-05-07  |  Article URL http://www.symantec.com/docs/TECH37701
Article Type
Technical Solution



Issue



A common error seen in the AMT logs when trying to provision Intel vPro systems is "Properties Script Failed." This error indicates that a provisioning attempt has failed and leaves the system in an unprovisioned state. Use this guide to understand the common problems associated with this error and how to work around them, including details of how to obtain more information.This error in and of itself is generic and the cause for it may vary.

Introduction

Generic errors are often the hardest to troubleshoot because of the lack of details. With the error "Properties Script Failed," the Out of Band Provisioning piece (OOBProv.exe) has returned an error when trying to provision an Intel vPro system. The errors returned by OOBProv vary, but the Intel SCS component produces this generic error when provisioning isn’t successful. The error by OOBProv is not logged by default. Learn here how to get that error details and the most common causes and their resolutions.


Environment



Notification Server 6.0 SP3 R4
Out of Band Management 6.2
Intel SCS 3.0

Cause



Issue: FQDN

The most common cause of this error is the inability of the OOBProv process to discover what the FQDN (Fully Qualified Domain Name) is for a given hello packet. The identifier used to link to the FQDN is the UUID. This Universally Unique Identifier is contained within the hello packet including the IP address of the system. This IP address can be used to identify the FQDN via DNS; however, this can be a risky method due to the possibility that the IP address is no longer accurate.


Solution



Out of Band Trace Logging

Trace logging can be invaluable in discovering the cause of this generic error message. While the trace data can often be difficult to sift through, it is the place to discover the true cause of the issue.

Setting Up the Trace

To enable trace logging in Out of Band Management, follow these steps:

  1. Go to Start > Run, type Regedit, and click OK.
  2. Browse to HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > eXpress > Notification Server > ProductInstallation > {09954bad-a09c-43ce-b8ad-407b6b93c936}.
  3. Create a DWORD value within the above key named TraceLevel (case sensitive).
  4. Set the value at FF hex, or 255 decimal, as shown in this screenshot:

  1. Download dbgview.exe (DebugView from Sysinternals/Microsoft) from www.sysinternals.com (you'll be redirected to Microsoft), click on the Miscellaneous section, and download Debugview. Note that you can use another debugger program to capture the trace elements, but this utility is free to download and use.
  2. Execute dbgview.exe.
  3. Ensure all Capture options are checked under the Capture menu.
  4. Leave the trace running and when the Properties Script Failed message appears in the AMT Log; there should be corresponding entries in the trace.
  5. Use the Save command when trace logging in complete.

Tips for examining the log

The trace elements are not user friendly to read, but text messages should appear. The following details provide assistance when reading the trace data in conjunction with this error:

  • Do not actively use the Provisioning nodes in the Altiris Console as this will generate a lot of trace data.
  • Search for "OOBProv" to find entries related to the Properties Script Failed error.
  • A common cause for this issue is the FQDN.Try searching for FQDN and see what messages are being logged.

An example of a common log entry with an FQDN mapping problem is displayed here:

000123712741.16528320[736] [D][44424] Searching by uuid = 'FA535827-ECD4-11DB-BBDA-4BC2BCEE001A'...

000123722741.16528320[736] [D][44424] Executing 'sp_OOBSC_FindResource', parameters:

000123732741.16528320[736] [D][44424] @UUID: FA535827-ECD4-11DB-BBDA-4BC2BCEE001A [String]

000123742741.16552734[736] [D][44424] @FQDN:[String]

000123752741.16552734[736] [D][44424] @HostName:[String]

000123762741.16577148[736] [D][44424] @IP:[String]

000123772741.16577148[736] [D][44424] @MAC:[String]

000123782741.28198242[736] [D][44424] Result:

000123792741.28222656[736] [D][44424] Executing 'sp_OOBSC_FindResource', parameters:

000123802741.28222656[736] [D][44424] @UUID: 275853FA-D4EC-DB11-BBDA-4BC2BCEE001A [String]

000123812741.28295898[736] [D][44424] @FQDN:[String]

000123822741.28295898[736] [D][44424] @HostName:[String]

000123832741.28295898[736] [D][44424] @IP:[String]

000123842741.28295898[736] [D][44424] @MAC:[String]

000123852741.32055664[736] [D][44424] Result:

000123862741.32275391[736] [D][44424] Can't find resource for 'FA535827-ECD4-11DB-BBDA-4BC2BCEE001A'

000123872741.32275391[736] [D][44424] No FQDN/ADOU found in NS DB for 'FA535827-ECD4-11DB-BBDA-4BC2BCEE001A'

000123882742.61450195[736] [D][44424] No FQDN/ADOU found for 'FA535827-ECD4-11DB-BBDA-4BC2BCEE001A', new AMT mapping can't be created

Note that the FQDN search would find this entry.

Useful Search strings include:

  • FQDN
  • UUID
  • Can’t
  • Error
  • Exception
  • OOBprov
  • Failed

Issue: FQDN

The most common cause of this error is the inability of the OOBProv process to discover what the FQDN (Fully Qualified Domain Name) is for a given hello packet. The identifier used to link to the FQDN is the UUID. This Universally Unique Identifier is contained within the hello packet including the IP address of the system. This IP address can be used to identify the FQDN via DNS; however, this can be a risky method due to the possibility that the IP address is no longer accurate.

The following methods can be used to rectify this situation so that the FQDN can be obtained by OOBProv.

DNS Lookup

In Out of Band Management, the default install does not try to attempt an FQDN acquisition using the IP address. This was done being sensitive to the way IP addresses can be reassigned, especially when a system is going through a build or imaging process. Items such as PXE boots, AMT IP requests, and OS reconfigurations including name changes can change the IP address assigned to the physical device.

Note: If you are using the Altiris Agent is the provisioning and system configuration process, see the subsequent section entitled OOB Discovery for a recommended way of resolving the FQDN. If you are not using the Altiris Agent, continue with this section.

The method for DNS lookup to use the reported IP address in the AMT’s hello packet for FQDN resolution is located under the configuration of the Resource Synchronization. In the Altiris Console browse to View > Solutions > Out of Band Management > Configuration > Provisioning > Intel AMT Systems and click on Resource Synchronization. See the screenshot below for details. Check the option entitled:

  • Use DNS IP resolution to find FQDN when assigning profiles.

Once this option is checked, OOBProv will use DNS to try and find the IP Address of the system.

OOB Discovery

For those systems that are managed within the Altiris Notification Server infrastructure, the best method to allow provisioning is to run the OOB Discovery (Out of Band Discovery) Task.This task executes by the Altiris Agent and does a check to see if the system is AMT capable.If it is, the following information will be collected and placed within the Altiris database relating to AMT:

  • _ResourceGuid
  • AMT Capable
  • AMT Enabled
  • IDE Redirection Enabled
  • Serial Over LAN Enabled
  • Network Interface Enabled
  • UUID

This data correlates by _ResourceGuid to the basic NS Resource tables, namely Inv_AeX_AC_Identification and Inv_AeX_AC_Location.The Location table contains the FQDN captured by the Altiris Agent, and is passed to OOBProv at provisioning time.

The Task for OOB Discovery is located in the Altiris Console under View > Solutions > Out of Band Management > Configuration > Out of Band Discovery, as shown in this screenshot:

The default collections account for all managed systems in the following collections:

  • All 32-bit Windows XP Computers
  • All 64-bit Windows XP Computers
  • All Windows 2000 Professional Computers.

If you are using Windows* Vista systems, add the Vista collections so they are included in this Discovery policy.

This policy executes the file located at: C:\Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\OOB\Discovery (path may vary if Notification Server was installed on a different drive or to a different path).The files in use are

  • ClientUtility.exe
  • ClientUtility64.exe
  • BMAPI.dll
  • BMAPIa.dll

The command line used for Discovery is:

ClientUtility.exe -mode:discovery

Noted in the screenshot above, the policy is set to Run once ASAP. This means each system will only ever run the OOB Discovery Task once. This also means any new computers receiving the task will also execute it once. This should be sufficient for most environments, but if another discovery needs to be run, a schedule can also be set in additional to the ASAP option.

Other Issues

When discovering the issue using the trace log, the issue may not be caused by the inability to find the FQDN of the system. In these cases the logs should provide details on what’s causing the error. Search the Altiris Knowledgebase at https://kb.altiris.com.

You can refine the search to Out of Band Management by looking under the Search Within section and selecting Altiris Products from the All Categories drop-down. A new Product drop-down will appear. Choose Out of Band from this drop-down, which will subsequently show a version drop-down.

This screenshot demonstrates this:

It’s possible the trace logs will not reveal where the problem is coming from. If this is the case, we must rely on the AMT Logs to see if the issue is detailed by Intel SCS directly.Look for errors surrounding the "Properties Script failed" entries to see if they are paired with another error message. Also check the Action Log to see what actions were attempted when Provisioning failed.

If another common cause for this issue is discovered, this document will be updated accordingly.

Conclusion

This document provides solutions for the most common cause of this error. Since the message "Properties script failed" is generic for "Something went wrong with Provisioning," it’s possible the problem comes from another source. If none of the above helps, contact Support Services for further assistance (a support agreement may be required).

Legacy ID



39540


Article URL http://www.symantec.com/docs/TECH37701


Terms of use for this information are found in Legal Notices