Owners Manual
Table Of Contents
- Dell Client Integration Pack for Microsoft System Center 2012 SP1 Configuration Manager And System Center 2012 Configuration Manager Version 3.1 User’s Guide
- Introduction
- Using DCIP With Configuration Manager
- Dell Warranty Utility
- Dell Intel vPro AMT Plugin
- 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 Client Integration Pack for Microsoft System Center Configuration
Manager (DCIP for Configuration Manager.)
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
mentioned in support.microsoft.com/kb/936707/.
Windows XP Installation Fails
Installation of Windows XP operating system will fail 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 OS. 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 miniutes to
provide ample time for the system to complete the reboot process. ME will maintain control even after the OS has rebooted
if the reboot completes in under 10 minutes. To give control back to the OS immediately, the user must select Tools > Link
Preference > OS owns Wireless. In that case, the KVM connection will be lost during the transfer process. To re-establish the
connection, the user must select Connection > Start. Also note that when control of the wireless link is automatically reverted
back as a result of the Link Preference Timeout expiring, there is no loss of connectivity. There are individual timeout values for
the each shutdown/reboot operation (defined in KVMView 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
28 Troubleshooting