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

Transcription

1 HP ProLiant Server OS Deployment for System Center Configuration Manager 2007 Troubleshooting Assistant HP Part Number: Part Number Published: November 2010 (First Edition)

2 Notices Copyright 2009, 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Part Number November 2010 (First Edition) Microsoft, Windows, Windows Server, Windows Vista, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Intended audience This document is for the person trained in network software administration and who understands concepts like TCP/IP, NTP, NFS, DNS, directory services (such as Active Directory and LDAP), and asynchronous serial communications.

3 Contents 1 Navigation tips Overview...5 About this guide Troubleshooting...7 Introduction...7 Installation issues...7 Custom action does not appear in the menu...7 Deployment pack does not completely uninstall...7 Create Server Deployment Task Sequence wizard reports error...8 Administrator console issues...8 Enabling UI debug logging...8 MMC Crash, Exception, or "Property Not Found" errors when loading custom action...8 Driver issues...8 File renaming...8 Modifying a boot image...9 Drivers import, but fail when updating the WinPE boot image...9 WinPE and task sequence issues...9 Task sequence template does not work after generation...10 WinPE never starts the task sequence...10 System booted PXE and waiting for PXE server to respond...10 Target system failed to run the new or updated configuration file...10 Command Prompt is not available from the HP WinPE boot images...10 Drivers have been added to the boot image, but are not loading...10 Servers do not boot using PXE...11 Default boot order does not enable PXE to boot when a valid drive exists...11 When using a Reboot action after initializing an array controller, the task sequence fails...11 Task Sequence fails with Failed to Download Policy...12 Task sequence does not run again even after clearing the PXE advertisement...12 Task sequence fails after an upgrade...12 Log files are not returned from the client...12 Log files are returned, but not the output files...13 Task step execution does not change after configuration XML file changed...13 Task Sequence fails at Apply Operating System with Failed to make volume X:\ bootable...13 System environment variables are not carried over to next action in the task sequence...14 Windows Server 2008 setup installer fails when deployed on ProLiant server with SAS drives...14 General issues...14 Log files appear to be cut off...14 Frequently asked questions Technical support...15 HP contact information...15 Contents 3

4 1 Navigation tips Navigating in the HTML document To navigate through the documentation sequentially: Click the Next arrow () for the next topic Click Previous arrow () for the previous topic Navigating using the Internet browser toolbar: To return to the last page you viewed, click the Back button on the browser toolbar. To return to one of the last nine pages you viewed in this session, click the down arrow to the side of the Back or Forward button on the browser toolbar, and then click the page you want from the list. Navigating to documentation on the HP website From the URLs in this guide, you may need to make several selections to get to your specific server documentation. For online access to technical documentation, self-help resources, live chat assistance, community forums of IT experts, technical knowledge base, remote monitoring and diagnostic tools, go to the HP Technical Support website. For the latest versions of selected technical documentation, go to the HP Technical Documentation website. 4 Navigation tips

5 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. Support Matrix for HP Server Integration with Microsoft System Center Products For more detailed information about the supported HP hardware, software, and operating systems, please refer to the Support Matrix: For System Center Operations Manager, Configuration Manager, and Virtual Machine Manager, see For System Center Essentials, see 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: About this guide 5

6 a. 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". b. Copy the _Installer.Log file, located at: {AdminUI Install Directory}\XmlStorage\Extensions\bin\Deployment\ <OEM>\<Product>\setup c. Copy the _ComponentsInstalled.xml file, located in the same directory as (b) above. 4. If the issue occurred while running a task sequence: a. 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 b. 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. c. Copy the files is used as input to the configuration task, such as configuration INI or XML files. d. 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: a. 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) b. A detailed description of the computer(s) being configured (model, hardware configuration, RAID controllers, and NIC details) c. 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? 6 Overview

7 3 Troubleshooting Introduction The following information is designed to help resolve some common installation, setup, and operating problems that might occur when you install and implement the HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager To begin, select one of the following: Installation issues Administrator console issues Driver issues WinPE and task sequence issues General issues Installation issues The following sections provide troubleshooting information for installation issues with the HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager 2007: Custom action does not appear in the menu Deployment pack does not completely uninstall Create Server Deployment Task Sequence wizard reports error Custom action does not appear in the menu Configuration Manager uses information stored in WMI to load the custom action assemblies from disk. This WMI information is imported into the site system WMI database during installation through the use of MOF files. If there is an error during importation or if the WMI information is incorrect, the MMC might encounter an exception when trying to load the assembly because the file name or assembly name is not found. Verify if the appropriate WMI class for HP_ProLiantDeployment exists under root\sms_<sitecode>\sms_tasksequencestep\ SMS_TaskSequenceAction. If the class does not exist, the custom action does not appear in the menu. Re-install the site server files using the installer. WMI CIM Studio, a useful tool for viewing and editing WMI information, is available from the Microsoft website. Deployment pack does not completely uninstall The uninstallation process does not remove the HP customized boot images and all drivers created during installation. These remaining images and drivers are tied to task sequence packages, and removing them might invalidate otherwise working task sequences that you are using. If you are no longer using the boot images and drivers created by this product, you can delete them from the console. To uninstall the kit, chose one of the following methods: Locate the HP ProLiant Server OS Deployment for Configuration Manager 2007 at the Add/Remove Program (or the Programs and Features in Windows Server 2008) Control Panel, and then launch Uninstall. The kit is removed from the system. Re-run the original kit installer. Introduction 7

8 Create Server Deployment Task Sequence wizard reports error The Create Server Deployment Task Sequence might report a Unable to add the task sequence to the Task Sequence Package error after installation. This usually happens after the uninstallation and reinstallation of the HP ProLiant Server OS Deployment kit. To resolve this issue, you must restart Configuration Manager console or restart the Configuration Manager server. Administrator console issues The following sections provide information for installation issues with the HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager 2007 kit: Enabling UI debug logging MMC Crash, Exception, or "Property Not Found" errors when loading custom action Enabling UI debug logging If you customized the configuration XML and have an incorrect XML, the actions in the UI might not work properly. Turning on debug logging on the Admin UI part of the custom action might resolve this issue. Logging is enabled by setting the Debug Logging key (DWORD value in the base registry key for the OEM) to a value of 1. For example, HKLM\SOFTWARE\Microsoft\ SMS\Deployment\HP\ProLiant\Debug Logging to 1. The debug log file is saved within the OEM installation directory within the \AdminUI directory. MMC Crash, Exception, or "Property Not Found" errors when loading custom action Configuration Manager uses information stored in WMI to load the custom action assemblies from disk. This WMI information is imported into the site system WMI database during installation through the use of MOF files. If an error occurs during importation or if the WMI information is incorrect, the MMC might encounter an exception when attempting to load the assembly, because the file name or assembly name is not found. Verify that the appropriate WMI class HP_ProLiantDeployment exists under root\sms_<sitecode>\sms_tasksequencestep\ SMS_TaskSequenceAction. If the class does not exist, the custom action does not appear in the menu. Re-install the site server files using the installer. WMI CIM Studio, a useful tool for viewing and editing WMI information, is available from the Microsoft website. Driver issues File renaming The following sections provide troubleshooting information for installation issues with the HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager 2007 kit. File renaming Modifying a boot image Drivers import, but fail when updating the WinPE boot image Some driver vendors supply files that are named differently, depending on the operating system they apply to (for example, driver_w2k.sys, driver_w2k3.sys, and driver_w2k3_64.sys apply to Windows 2000, Windows Server 2003, and Windows Server 2003 x64 Edition). The installation program renames the files to its base names before installing the driver, such as renaming to driver.sys.. If the installation program renames files prior to installation, then the driver injection into the WinPE image fails, because the correct file names are not present. 8 Troubleshooting

9 Modifying a boot image During the installation of the deployment kit, you might have to modify WinPE boot image to insert drivers and other changes, which enable the OEM toolkit utilities to function. By default, the installation program makes a copy of the Configuration Manager default boot image (boot.wim) and then mounts the file, makes changes, and then unmounts the file. The modified boot.wim file contains the base set of changes needed by the toolkit. Network and storage drivers must be added so that boot devices (such as array controllers) function and that the machine has the appropriate network drivers to communicate with the network in WinPE. These drivers must be added through the driver catalog within the OS Deployment node of the Configuration Manager Administrator Console. HP has integrated drivers from the latest SmartStart Scripting Toolkit into the HP ProLiant Server OS Deployment kit. However, drivers required for newer ProLiant servers must be added manually to ensure access to the newer devices. For more detailed information about the supported HP hardware, software, and operating systems, please refer to the Support Matrix for HP Server Integration with Microsoft System Center Products: For System Center Operations Manager, Configuration Manager, and Virtual Machine Manager, see For System Center Essentials, see Configuration Manager stores two boot images that help to distribute for machines booting to PXE. The boot.wim file is the base boot image, which contains no Configuration Manager specific files. When you add drivers to a boot image and then update the boot image on a distribution point, Configuration Manager takes the base boot.wim file. Configuration Manager then adds the drivers from the driver catalog, along with other Configuration Manager files, and creates a new WIM file, named boot.<packageid>.wim. For example, boot.sms00001.wim, this new WIM file is then distributed to the assigned PXE distribution points for your site. Drivers import, but fail when updating the WinPE boot image Drivers might be loaded together in a common directory and contain a TXTSETUP.OEM file. This can also occur with only one driver in a directory. By default, Configuration Manager chooses the TXTSETUP.OEM file for its source of import information for the drivers and, if this file is present, does not display any associated INF files. This might cause issues, so load the drivers individually, using their own respective INF files. To prevent issues, rename any TXTSETUP.OEM files in the driver directory so that you can select the INF files and import the drivers individually. WinPE and task sequence issues The following sections provide troubleshooting information for installation issues with the HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager 2007 kit: Task sequence template does not work after generating (Task sequence template does not work after generation, WinPE and task sequence issues ( WinPE and task sequence issues (page 9))) WinPE never starts the task sequence System booted PXE and waiting for PXE server to respond Target system failed to run the new or updated configuration file Command Prompt is not available from the HP WinPE boot images Drivers have been added to the boot image, but are not loading Servers do not boot using PXE Default boot order does not enable PXE to boot when a valid drive exists When using a Reboot action after initializing an array controller, the task sequence fails WinPE and task sequence issues 9

10 Task Sequence fails with Failed to Download Policy Task sequence does not run again even after clearing the PXE advertisement Task sequence fails after an upgrade Log files are not returned from the client Log files are returned, but not the output files Task step execution does not change after configuration XML file changed Task Sequence fails at Apply Operating System with Failed to make volume X:\ bootable System environment variables are not carried over to next action in the task sequence Windows Server 2008 setup installer fails when deployed on ProLiant server with SAS drives Task sequence template does not work after generation The generated HP ProLiant Server OS Deployment task sequence is a template and requires customized settings to function properly. The HP ProLiant Server OS Deployment kit also comes with a number of sample configuration files for each setting. Therefore, you must select and update the configuration files appropriately before advertising to the client server. WinPE never starts the task sequence Check the SMSTS.LOG file at X:\windows\temp\smstslog\smsts.log. If a package does not download you might not have the appropriate network drivers installed. If they are not installed, then the machine cannot communicate with Configuration Manager. Verify your driver catalog to ensure you have the correct network drivers available and installed into the boot image, and update the boot image to your distribution points. You might need additional network or storage drivers in the boot image to enable the WinPE boot to function correctly. You must add those through the Drivers option in the Operating System Deployment node. Verify that all packages referenced in the task sequence are available from the distribution point. WinPE validates all packages to make sure they are available before processing the task sequence. System booted PXE and waiting for PXE server to respond Verify that both HP WinPE boot images are updated to the PXE distribution point. You can also verify the PXE service point status from the Configuration Manager console>system Status>Site Status>Site>Component Status>SMS_PXE_SERVICE_POINT for status message. Target system failed to run the new or updated configuration file You must manually update the distribution point for the HP ProLiant Server OS Deployment Integration package when you modify, add, or remove the configuration file for the SmartStart Scripting Toolkit. Command Prompt is not available from the HP WinPE boot images WinPE Command Prompt is for debugging purposes only. You must manually select Enable command support in the HP WinPE boot images properties to enable this feature. You must also update the distribution point after WinPE property is updated. Drivers have been added to the boot image, but are not loading The original boot.wim file (WinPE boot image) created during SCCM installation is copied and modified with HP-specific drivers and other files. Your task sequences that use the HP deployment tools must use this boot image, or the tools might not work properly. Verify that the image you loaded the drivers into is the same one being used by the task sequence. This error occurs when administrators maintain multiple boot images. 10 Troubleshooting

11 Servers do not boot using PXE PXE is an extension of DHCP, which uses a broadcast type of communication. Broadcast communication uses standard timeout values that are not readily changeable. As a result, a computer waits for a default time frame to receive a DHCP or PXE response before timing out and causing a failure condition. Each time a server is rebooted, it must renegotiate the connection to the switch. Some network switches arrive configured with default settings that might incur connectivity delays. The settings on the switch might cause a DHCP or PXE timeout, because they fail to negotiate a connection in time. NOTE: The HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager 2007 uses PXE services provided by Windows Deployment Server. Insight Control server deployment, which is part of the Insight Control suite, provides its own PXE services. Insight Control server deployment and ProLiant OS Deployment must not both be installed at the same time, as networking issues might arise. The following features might be affected by negotiation timeouts: Spanning Tree Protocol (STP) STP is a protocol that prevents loops and provides redundancy within a network. A networking device using this algorithm might experience some latency as it collects information about other network devices. During this period of information collection, servers might boot to PXE and time out while waiting for a response from Windows Deployment Services. To prevent these issues, disable the STP or enable PortFast on end-node ports for the target server. For further information, see the manufacturer's user guide. EtherChannel or Port Aggregation Protocol (PAgP) EtherChannel enables multiple links between devices to act as one fast link that shares the load between the links. Running the EtherChannel Protocol in automatic mode might cause a connectivity delay of up to 15 seconds. To eliminate this delay, switch to a manual mode, or turn off this feature. Speed and duplex negotiation If auto-negotiation on the switch is set to off and the server is not configured to that speed and duplex setting, then the switch does not negotiate with that server. Default boot order does not enable PXE to boot when a valid drive exists When an active partition is created on a hard drive, it automatically becomes a bootable device if a valid operating system has been installed. If your PXE NIC installs after the hard drive in the boot order, then hard drive tries to boot before PXE and boot to Windows, or cause an Invalid System Partition error if Windows is not installed. To resolve this issue, verify that PXE is placed before the hard drive in the boot order. The boot order can be set by using the Set Boot Order actions in the deployment kit. This boot order can also be reviewed and set at the system ROM-based Setup Utility by pressing F9 at boot up. If PXE is first in the boot order, the computer does not actually boot to PXE unless Configuration Manager has a task sequence for it to run. When using a Reboot action after initializing an array controller, the task sequence fails Configuration Manager 2007 does not support a task sequence to reboot back to PXE. It can reboot back to WinPE or to an installed OS, both of which require a disk partition and the appropriate installed software. Without a disk partition, Configuration Manager fails when attempting to reboot during a task sequence, because it expects to copy WinPE to the disk. The management point tracks when a machine has booted to PXE to run a task sequence, and once a WinPE and task sequence issues 11

12 machine has booted to PXE for a task sequence, it cannot use PXE as a boot method again for that task sequence unless the advertisement is reset. If you need to perform a reboot to PXE within a task sequence, chose one of the following options: Use Reboot to PXE / USB, a custom action, which is available in the community through CodePlex. This custom action, written using C# and VBScript, connects to the Configuration Manager 2007 SDK and contains custom code to drive actions in the administrator console as well as the machine being deployed. Reboot To PXE / USB performs the steps to reboot to PXE. Use more than one task sequence, let the computer "fall off the end" of the first task sequence, and then manually reset the PXE advertisement for the computer. Task Sequence fails with Failed to Download Policy This error code (0x or 0x ) refers to a certificate validation issue. The SMSTS.LOG file displays an entry with any of the following text: CryptDecryptMessage ( &DecryptParams, pbencrypted, nencryptedsize, 0, &nplainsize, 0 ), HRESULT= no cert available for policy decoding The following are possible causes: Misconfiguration of your domain or site server, such as DNS not pointing to the site server or the site server not specifying a valid FQDN (which is referred to by the DNS listing). If your site server does not specify a FQDN and only specifies the NETBIOS name, and your DNS server refers to the FQDN, an incorrect lookup might cause this error. The certificate being used for PXE and boot media. Under the certificates under the Site Settings node, verify if any certificates are blocked or missing. Open the certificates, and ensure that they are actually installed into the certificate store. If not, install them. If the task sequence still fails, remove the package from the distribution point through Manage Distribution Points, and then add it back. This causes the package hash to be regenerated. Task sequence does not run again even after clearing the PXE advertisement You must ensure that the advertisement is set to Always rerun so that when you reset the PXE advertisement, the advertisement is applied to the computer regardless of whether it previously ran the task sequence. Task sequence fails after an upgrade When upgrading from a previous version of this product, existing task sequences using these custom actions are not automatically updated. In order to function correctly, each task sequence action that uses one of these custom actions must be opened and edited (such as adding a period to the description and then removing it). This enables the Apply button, which refreshes the properties of the custom action and saves any new data or formatting required to function with the new version. Log files are not returned from the client The following issues might cause failure of the task sequence to return files or logs back from the client: Failure of the client-side script prior to the file copy. This issue is usually evident in the log file. Repeat the task, and then press F8 during the task to display a command prompt. The Enable command support checkbox must be checked on the boot image properties > Windows PE 12 Troubleshooting

13 page and the SMSTS.LOG file open. In WinPE through PXE, the log file is located at X:\ Windows\Temp\Smstslog\smsts.log. The command being executed had an error but exited with code 0. This can occur when a severe error is encountered in the script while the script is set to ignore errors and use programmatic error handling and the error handling did not catch the error. Report this issue to HP. The task sequence cannot access the share or mapped drive to where the files must be copied. Log files are returned, but not the output files The following issues might cause failure of the task sequence to return files or logs back from the client: No return file parameters are specified in the configuration XML. Return file parameters specified in the configuration XML are incorrect. An error occurred with the operation of the utility that generates the output file. There is an error in the filename for the return file because of a null variable. Task step execution does not change after configuration XML file changed If you change the configuration XML, existing tasks are not changed unless they are edited. To fix the existing task steps: 1. Open the task sequence editor, go through each custom action step in the sequence, and then modify it. (For example, add a period in the description.) 2. Click Apply. The task sequence steps are now saved with the updated information from the new XML file. Task Sequence fails at Apply Operating System with Failed to make volume X:\ bootable This issue is indicated by log content similar to the following message: MakeVolumeBootable( pszvolume ), HRESULT= (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759) Failed to make volume E:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Unspecified error (Error: ; Source: Windows) ConfigureBootVolume(targetVolume), HRESULT= (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,326) Process completed with exit code This issue can be caused by the following: If you are using a Format & Partition action in your task sequence to partition the hard drives, select the Make this the boot partition checkbox. If you do not select this checkbox and the computer has a single hard drive, then the task sequence engine automatically makes one of the partitions the boot partition. If there are multiple drives, it cannot automatically determine which boot partition must be bootable. If both of the hard drives have never been partitioned, then there is a known bug in Windows PE that it cannot properly determine which drive it is booted from. This error might occur on a server with a RAID controller where you have just formed two or more RAID sets. The new RAID sets are completely raw because they have never existed before. The only workaround to this issue with multiple raw drives is to manually boot into Windows PE and run the diskpart WinPE and task sequence issues 13

14 command to partition at least one of the drives. Rerun the task sequence. The known problem with Windows PE is fixed in Windows Vista SP1 (Windows PE that it derived from Windows Vista SP1).This issue applies only for customers who upgraded from SCCM RTM to SP1. Configuration Manager 2007 SP1 includes the SP1 version of the Windows Automated Installation Kit (WAIK). You must download and install Configuration Manager SP1. The product installer detects the version of WinPE that is currently in use by the default boot images. If the default boot images are not Windows Vista SP1, the product cannot install. System environment variables are not carried over to next action in the task sequence When a task sequence runs, commands are executed in a command shell. When that task ends, so does that command shell environment, causing the loss of any system variables defined within that task. Verify that variables that pass between tasks are set as Task Sequence variables, Collection variables, or Machine variables. Windows Server 2008 setup installer fails when deployed on ProLiant server with SAS drives An issue specific to OSD kit in the Broadcom NetXtreme II GigE VBD driver (bxvbd), included in the HP NC-Series Broadcom 1Gb Multifunction Driver for Windows Server 2008 component in the HP Windows Server 2008 Driver package, is causing the setup installer to fail. Disabling the Apply Driver Package and Apply Device Drivers tasks can temporarily resolve the issue. The Windows Server 2008 driver packages in the ProLiant OSD 1.10 kit removes the drivers with issues from PSP The default task sequence templates have been updated with 2 new tasks for G6 servers to resolve the issue. General issues The following section provides troubleshooting information for installation issues with the HP ProLiant Server OS Deployment Toolkit for Microsoft System Center Configuration Manager 2007 kit. Log files appear to be cut off Log files appear to be cut off When viewing logs with the Trace32 utility, view the logs using WordPad. Trace32 might not display the entire log file, and large increments of time might appear to be missing from the log. Frequently asked questions Can I deploy firmware updates using the deployment kit? Firmware must be applied as a standard "install software" action. SCCM only downloads one package per action, and since the client-side script and the toolkit utilities are a package, no additional packages can be downloaded. Can I deploy ProLiant Support Packs using the deployment kit? HP recommends the installation of ProLiant Support Packs after operating system is deployed. Similar to firmware, ProLiant Support Packs must be installed as a standard "install software" action. Can I just integrate the toolkit package with my boot image? The product does not currently support that option and requires the use of a package for the toolkit utilities. Can I install this kit on System Management Server 2003? No. This product is not supported for use with System Management Server 2003, since System Management Server 2003 OS Deployment capability is an add-on pack that uses a different architecture than the OS Deployment feature in Configuration Manager There are no plans to make this product backward-compatible. 14 Troubleshooting

15 4 Technical support HP contact information For the name of the nearest HP authorized reseller: See the Contact HP worldwide (in English) webpage. For HP technical support: In the United States, for contact options see the Contact HP United States webpage. To contact HP by phone: Call HP-INVENT ( ). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. If you have purchased a Care Pack (service upgrade), call For more information about Care Packs, refer to the HP website. In other locations, see the Contact HP worldwide (in English) webpage. HP contact information 15