Users Guide
Table Of Contents
- Dell Client Integration Pack for Microsoft System Center 2012 Configuration Manager Version 3.0 User’s Guide
- Introduction
- Using Dell Command | Integration Suite for System Center
- Inserting Dell Drivers Into A Windows PE Boot Image
- Creating Dell Client Driver Packages
- Dell Command | Configure Self-Contained-Executable File
- Importing Dell Command | Monitor
- Managing and updating distribution points
- Creating a task sequence
- Configuring task sequence actions
- Computer Association
- Advertising A Task Sequence
- Deploying A Task Sequence
- Dell Command | Warranty
- The Dell Command | Intel vPro Out Of Band Application
- Troubleshooting
- Authenticode signature
- Windows XP Installation Fails
- KVM over wireless
- Hardware inventory report memory speed is reported as zero
- Max password length change
- KVM power control to boot to OS in S3
- Windows XP(x86) OS Deployment Hangs During Installation
- Apply operating system task sequence action has a red bang
- Related reference
Troubleshooting
This section contains troubleshooting information for the Dell Command | Integration Suite for System Center.
Topics:
• Authenticode signature
• Windows XP Installation Fails
• KVM over wireless
• Hardware inventory report memory speed is reported as zero
• Max password length change
• KVM power control to boot to OS in S3
• Windows XP(x86) OS Deployment Hangs During Installation
• Apply operating system task sequence action has a red bang
Authenticode signature
If authenticode signature takes longer than usual to start because .Net is searching for the signature, follow the steps that are
mentioned in support.microsoft.com/kb/936707/.
Windows XP Installation Fails
Installation of Windows XP operating system fails if the mass storage driver to be installed is not selected in the task Sequence.
To do this in the Apply Driver Packages step ensure that you select the Mass Storage Driver that is required for the
operating system installation.
KVM over wireless
Anytime the user selects Tools Link Preference > OS owns Wireless, control of the wireless link is transferred from the Intel
Management Engine to the operating system. (ME gains control of the wireless link anytime a shutdown or reboot command is
selected from Tools Power Control.)
Whenever ME is given control of the wireless link (Link Preference), a timeout value is supplied that indicates how long ME is
to maintain control of the wireless link, after which, control is given back to the operating system. For example, a user selects
Reboot To OS to reboot the client operating system.
In order to maintain the KVM link, ME is first given control of the wireless link. The timeout is set by default to 10 minutes to
provide ample time for the system to complete the reboot process. ME will maintain control even after the operating system has
rebooted if the reboot completes in under 10 minutes. To give control back to the operating system immediately, the user must
select Tools > Link Preference > OS owns Wireless. In that case, the KVM connection is lost during the transfer process.
To reestablish the connection, the user must select Connection > Start. Also note that when control of the wireless link is
automatically reverted as a result of the Link Preference Timeout expiring, there is no loss of connectivity. There are individual
timeout values for each shutdown and reboot operation (defined in KVM View app.config settings) that can be configured
externally:
● LPTImeoutRebootToOS
● LPTimeoutRebootToBIOS
● LPTimeoutRebootToDiagnostics
● LPTimeoutRebootWithIDER
● LPTimeoutShutdown
For more information, see http://software.intel.com/sites/manageability/
AMT_Implementation_and_Reference_Guide/DOCS/Implementation%20and%20Reference%20Guide/default.htm.
5
Troubleshooting 29