HP

HP ProLiant Server OS Deployment for System Center Configuration Manager 2007 Troubleshooting Assistant

 English
  HP ProLiant Server OS Deployment for System Center Configuration Manager 2007 Troubleshooting Assistant > Chapter 2 Overview   

About this guide

This guide is intended to help users of the HP ProLiant Server OS Deployment for Configuration Manager 2007 troubleshoot issues during installation and operation. You must be familiar with the Operating System Deployment feature in Configuration Manager before using the HP ProLiant Server OS Deployment kit.

For complex issues, prior to reviewing this trouble shooting assistant, HP recommends reviewing the Microsoft product documentation and the HP ProLiant Server OS Deployment for Configuration Manager 2007 User Guide and HP Server Integrations with Microsoft System Center Products Support Matrix.

Before proceeding with troubleshooting the issue and calling support:

  • Verify your task sequence action settings.

    The primary cause of task sequence failures is related to the settings you provide in the task sequence steps. Be sure to verify the task sequence steps for the following:

    • Valid environment or task sequence variable references.

    • Valid file references. You must use DOS 8.3 naming whenever possible. Do not use file names with embedded spaces.

    • Valid directory references. When capturing files from a target computer, ensure that the destination directory already exists. The process does not automatically create directory structures.

    • Valid package reference. You must ensure that all packages referenced in the task sequence are available from the distribution point.

  • Verify the log files, and use debug logging.

    The HP custom actions in the deployment kit provide an option for capturing the SMSTS.LOG file from WinPE and bringing it back to the SCCM server. It also enables extended logging by the custom action to assist with troubleshooting issues. Enabling the logging ("Logs / Return Files" tab in the action) assists in resolving these issues. For more details, see the HP ProLiant Server OS Deployment User Guide.

  • Gather the appropriate information.

    When you call HP Support, you must have information ready to efficiently resolve your issue.

Before you contact HP, perform the following procedure:

  1. Export the task sequence you are using by right-clicking the task sequence and selecting Export.

  2. If the issue appears, the collect screen captures of the relevant portions.

  3. If the issue is related to installation of the product or occurs soon after installation:

    1. Copy the MSI installation log, located in the temporary files directory (locate using the %TEMP% environment variable). This file is usually located in a "1" directory and has a random name that is formatted like "MSI<RandomChars>.LOG".

    2. Copy the _Installer.Log file, located at:

      {AdminUI Install Directory}\XmlStorage\Extensions\bin\Deployment\<OEM>\<Product>\setup

    3. Copy the _ComponentsInstalled.xml file, located in the same directory as (b) above.

  4. If the issue occurred while running a task sequence:

    1. Copy the SMSTS.LOG file from where WinPE might be stored:

      1. In X:\Windows\Temp\Smstslog for PXE boot

      2. On a local (for example, C: or D:) drive under \Smstslog

      3. With an SMSTSLOG<Time-Based-Name> .LOG file

    2. Copy the custom action logs is saved using the Retrieve the task sequence log file from the client when this action runs checkbox on the custom action Logs/Return files tab. You must select the Enable extended/debug logging by this action checkbox.

    3. Copy the files is used as input to the configuration task, such as configuration INI or XML files.

    4. Copy the SetupAPI.APP.LOG and SetupAPI.DEV.LOG from WinPE stored in X:\Windows\inf for PXE boot.

  5. A complete, detailed explanation of the issue, including:

    1. The exact point of failure (for example, the action running when the process failed, a description or screen captures of error messages and error codes)

    2. A detailed description of the computer(s) being configured (model, hardware configuration, RAID controllers, and NIC details)

    3. A description of other circumstances, such as

      1. Has this task sequence or action ever worked? When did it stop working?

      2. If it had worked before, what is different now? Is the task sequence being applied to different computer types, is it using different configuration files, different task sequence variables, or has something else been modified?
©