<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Intel Communities : All Content - Intel® vPro™ Expert Center</title>
    <link>http://communities.intel.com/community/openportit/vproexpert</link>
    <description>All Content in Intel® vPro™ Expert Center</description>
    <language>en</language>
    <pubDate>Fri, 27 Nov 2009 19:09:54 GMT</pubDate>
    <generator>Clearspace 2.5.9 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-27T19:09:54Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>SCCM Certificates required for child sites?</title>
      <link>http://communities.intel.com/message/75468</link>
      <description>&lt;!-- [DocumentBodyStart:4a9aa7b0-91e1-4119-bcab-4bdc7a654b7a] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;As long as the two OOB service points exist in the same DNS namespace, differing hostnames should not matter. You will need to import the certificate (&lt;em&gt;include the certificate chain, and the private key, when you export it&lt;/em&gt;) directly into the properties page of the &lt;em&gt;Out of Band Component Configuration&lt;/em&gt; node in the ConfigMgr console.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Cheers,&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Trevor Sullivan&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://trevorsullivan.wordpress.com"&gt;http://trevorsullivan.wordpress.com&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:4a9aa7b0-91e1-4119-bcab-4bdc7a654b7a] --&gt;</description>
      <pubDate>Fri, 27 Nov 2009 19:09:54 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/75468</guid>
      <dc:date>2009-11-27T19:09:54Z</dc:date>
      <clearspace:dateToText>1 day, 5 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>AMT Web UI - SCCM Provisioned</title>
      <link>http://communities.intel.com/message/75299</link>
      <description>&lt;!-- [DocumentBodyStart:a613533a-5c9d-4473-b031-169e2fc78974] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;&lt;span style="text-decoration: underline;"&gt;&lt;a class="jive-link-external-small" href="http://support.microsoft.com/kb/908209"&gt;This scarcely documented registry key&lt;/a&gt;&lt;strong&gt; IS REQUIRED&lt;/strong&gt;&lt;/span&gt; &lt;em&gt;however &lt;/em&gt;when i had input the key previously, i incorrectly setup a DWORD of iexplore instead of the correct value of iexplore.exe.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;BTW im on a Windows 2008 server with Internet Explorer 7. You would think M$ would have adressed this issue by now&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:a613533a-5c9d-4473-b031-169e2fc78974] --&gt;</description>
      <pubDate>Wed, 25 Nov 2009 23:49:05 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/75299</guid>
      <dc:date>2009-11-25T23:49:05Z</dc:date>
      <clearspace:dateToText>2 days, 18 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Internal Enterprise Root CA Cert Expiration</title>
      <link>http://communities.intel.com/message/75267</link>
      <description>&lt;!-- [DocumentBodyStart:9d69af09-30fc-4945-ab30-9c3f4571556a] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Thats what i wanted to confirm; whether or not the hash stays the same upon a cert renewal.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks!&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:9d69af09-30fc-4945-ab30-9c3f4571556a] --&gt;</description>
      <pubDate>Wed, 25 Nov 2009 20:37:08 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/75267</guid>
      <dc:date>2009-11-25T20:37:08Z</dc:date>
      <clearspace:dateToText>3 days, 4 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Known Issues, Best Practices, and Workarounds</title>
      <link>http://communities.intel.com/docs/DOC-1247</link>
      <description>&lt;!-- [DocumentBodyStart:9999aa93-a92c-4cf7-9f10-7efafe625b62] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;&lt;div class="toc" style="border: 1px dashed black; padding: 10px"&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Best_Practices"&gt;Best Practices&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Automatically_disabling_the_Intel_AMT_Privacy_Notification_window"&gt;Automatically disabling the Intel® AMT Privacy Notification window&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Changing_Terminal_Emulation_Type"&gt;Changing Terminal Emulation Type&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Customizing_the_Intel_AMT_Status_dialog_box"&gt;Customizing the Intel® AMT Status dialog box&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_AMT_platform_may_have_up_to_8_client_certificates_that_can_define_different_8021x_profiles"&gt;Intel® AMT platform may have up to 8 client certificates that can define different 802.1x profiles&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#How_To_Remove_the_CMOS_Battery_on_a_Lenovo_ThinkPad_T400"&gt;How To Remove the CMOS Battery on a Lenovo* ThinkPad* T400&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Root_certificate_size_limit_is_2048bits"&gt;Root certificate size limit is 2048-bits&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#How_to_hide_the_IntelR_Management__Security_Status_IMSS_tool_system_tray_icon"&gt;How to hide the Intel(R) Management &amp;amp; Security Status (IMSS) tool system tray icon&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Tips_on_ME_firmware_updates"&gt;Tips on ME firmware updates&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#IntelR_AMT_does_not_allow_multiple_simultaneous_commands"&gt;Intel(R) AMT does not allow multiple simultaneous commands&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Password_issue_causes_WebUI_to_report_The_system_may_be_under_attack_in_the_event_log"&gt;Password issue causes WebUI to report "The system may be under attack" in the event log&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#BIOS"&gt;BIOS&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#F10_does_not_exit_BIOS_on_HP_clients"&gt;F10 does not exit BIOS on HP clients&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#The_TCPIP_DHCP_Mode_setting_in_MEBx_must_be_enabled_for_remote_control_of_an_IntelR_AMT_platform"&gt;The TCP/IP DHCP Mode setting in MEBx must be enabled for remote control of an Intel(R) AMT platform&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#After_reflashing_a_full_image_is_a_clear_CMOS_required"&gt;After reflashing a full image, is a "clear CMOS" required?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Remote_BIOS_update_with_AMT_Commander_does_not_see_BIOS_update_files"&gt;Remote BIOS update with AMT Commander does not see BIOS update files&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#IntelR_AMT_Event_log_includes_Platform_Event_Traps_from_the_BIOS"&gt;Intel(R) AMT Event log includes Platform Event Traps from the BIOS&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Client_Drivers"&gt;Client Drivers&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Using_Intel_vPro_technology_and_Linux"&gt;Using Intel vPro technology and Linux&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Linuxbased_wireless_drivers"&gt;Linux-based wireless drivers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Wireless_management_does_not_work_when_the_operating_system_is_running"&gt;Wireless management does not work when the operating system is running&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#LMSSOL_driver_setup_program_fails_to_install_privacy_icon_if_installation_path_includes_square_brackets"&gt;LMS/SOL driver setup program fails to install privacy icon if installation path includes square brackets&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Infrastructure"&gt;Infrastructure&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Is_an_IDER_recommended_over_a_WAN"&gt;Is an IDE-R recommended over a WAN?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Firewalls_may_not_let_Intel_AMT_clients_communicate_with_management_consoles"&gt;Firewalls may not let Intel® AMT clients communicate with management consoles&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Secondary_DNS_IP_makes_Intel_AMT_configuration_fail_in_basic_formerly_SMB_mode"&gt;Secondary DNS IP makes Intel® AMT configuration fail in basic (formerly SMB) mode&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#ME_NIC_remains_at_lowest_negotiated_speed_and_half_duplex_mode_after_booting"&gt;ME NIC remains at lowest negotiated speed and half duplex mode after booting&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#GenScript_produces_errors_on_Windows_Vista_OS_Windows_Server_2008_and_clients_with_8021x_profiles"&gt;GenScript produces errors on Windows* Vista OS, Windows* Server 2008, and clients with 802.1x profiles&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Usage_of_Locally_Administered_Address_on_IntelR_Active_Management_Technology_enabled_systems"&gt;Usage of Locally Administered Address on Intel(R) Active Management Technology enabled systems&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#ICMP_Router_Discovery_Protocol_IRDP_is_not_supported"&gt;ICMP Router Discovery Protocol (IRDP) is not supported&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#ISV"&gt;ISV&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Altiris"&gt;Altiris&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Troubleshooting_DNS_when_configuring_Altiris"&gt;Troubleshooting DNS when configuring Altiris&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Can_the_Default_provisionserver_naming_conventions_be_changed"&gt;Can the Default 'provisionserver' naming conventions be changed?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Hardware_inventory_on_Altiris_console_requires_Altiris_inventory_solution"&gt;Hardware inventory on Altiris* console requires Altiris* inventory solution&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#LANDesk"&gt;LANDesk&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#No_drivers_required_for_bare_metal_provisioning"&gt;No drivers required for bare metal provisioning&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Need_to_set_LANDesk_root_certificate_as_trusted_certificate"&gt;Need to set LANDesk* root certificate as trusted certificate&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#LANDesk_Management_Suite_88_SP2_patch_fixes_loss_of_inband_connectivity"&gt;LANDesk* Management Suite 8.8 SP2 patch fixes loss of in-band connectivity&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#LANDesk_88_SP2_console_requires_repeated_deletion_of_two_directories_when_provisioning"&gt;LANDesk* 8.8 SP2 console requires repeated deletion of two directories when provisioning&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Microsoft_ConfigMgr_see_also_httpcommunitiesintelcomopenportdocsDOC1627cf"&gt;Microsoft ConfigMgr (see also: http://communities.intel.com/openport/docs/DOC-1627#cf)&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Enabling_native_no_translation_required_support_within_Microsoft_SCCM_SP1"&gt;Enabling native (no translation required) support within Microsoft SCCM SP1&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Virtual_adapters_may_cause_network_discovery_to_fail"&gt;Virtual adapters may cause network discovery to fail&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Microsoft_SCCM_unable_to_use_Intel_AMT_features_when_run_on_Microsoft_Vista_Operating_System"&gt;Microsoft* SCCM unable to use Intel® AMT features when run on Microsoft* Vista* Operating System&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Microsoft_SCCM_2007_SP1_hotfix_rollup_KB960804_includes_KB959040"&gt;Microsoft* SCCM 2007 SP1 hotfix roll-up KB960804 includes KB959040&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SoLIDER_fails_on_Microsoft_SCCM_2007_SP1_with_twotiered_PKI_model"&gt;SoL/IDER fails on Microsoft SCCM 2007 SP1 with two-tiered PKI model&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Failure_of_collectionbased_power_control_in_Microsoft_SCCM_SP1"&gt;Failure of collection-based power control in Microsoft* SCCM SP1&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Cannot_provision_HP_DC7700_using_Microsoft_ConfigMgr_SP1_and_PKI_method"&gt;Cannot provision HP* DC7700 using Microsoft* ConfigMgr SP1 and PKI method&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Management_Engine"&gt;Management Engine&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Maximum_number_of_agents_that_can_be_monitored_simultaneously"&gt;Maximum number of agents that can be monitored simultaneously&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#HewlettPackard_6910P_returns_UUID00000_during_activation"&gt;Hewlett-Packard 6910P returns UUID=00000 during activation&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Running_virtual_machines_and_DHCP_can_cause_Intel_AMT_to_be_inaccessible"&gt;Running virtual machines and DHCP can cause Intel AMT to be inaccessible&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Wildcard_certificates_are_currently_not_supported_for_remote_configuration"&gt;Wildcard certificates are currently not supported for remote configuration&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#No_inventory_data_available"&gt;No inventory data available&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Weybridge_issue_causing_network_disconnects_impacting_Dell_Optiplex_755"&gt;Weybridge issue causing network disconnects; impacting Dell Optiplex 755&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Synchronizing_the_operating_system_and_the_Intel_AMT_hostname"&gt;Synchronizing the operating system and the Intel AMT hostname.&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Best_Practices_Setting_up_application_servers_and_Internet_Explorer_for_IntelR_AMT_Kerberos_support"&gt;Best Practices: Setting up application servers and Internet Explorer* for Intel(R) AMT Kerberos support&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Network_issues_with_NS_Lookup"&gt;Network issues with NS Lookup&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Does_Intel_AMT_30_support_Windows_2000_Active_Directory"&gt;Does Intel AMT 3.0 support Windows 2000 Active Directory?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Switching_from_NAC_to_8021x_results_in_loss_of_connectivity"&gt;Switching from NAC to 802.1x results in loss of connectivity&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Using_IntelR_AMT_wirelessly_without_user_intervention"&gt;Using Intel(R) AMT wirelessly without user intervention&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Cannot_provision_a_system_that_uses_an_underscore_in_the_host_name"&gt;Cannot provision a system that uses an underscore in the host name&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Does_the_Intel_SCS_automatically_push_updates_to_the_CRL_Certificate_Revocation_List_to_clients"&gt;Does the Intel SCS automatically push updates to the CRL (Certificate Revocation List) to clients?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Firewalls_may_not_let_IntelR_AMT_clients_communicate_with_management_consoles"&gt;Firewalls may not let Intel(R) AMT clients communicate with management consoles&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Cisco_ACS_Certificate_Configuration_for_Intel_AMT"&gt;Cisco ACS Certificate Configuration for Intel AMT&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#What_are_some_common_hardware_issues_that_are_tracked_by_Intel_AMT"&gt;What are some common hardware issues that are tracked by Intel® AMT?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#QA_on_customized_Intel_AMT_firmware"&gt;Q&amp;amp;A on customized Intel® AMT firmware&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Wrong_IP_address_for_Intel_ME_on_Lenovo_M58p_using_Hypervisor"&gt;Wrong IP address for Intel ME on Lenovo M58p using Hypervisor&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Microsoft_Systems_Management_Server_SMS_Addon"&gt;Microsoft Systems Management Server (SMS) Add-on&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Fix_available_Microsoft_System_Management_Server_SMS_Addon_V30_has_local_echo_when_using_Serial_over_LAN_SoL"&gt;Fix available: Microsoft System Management Server (SMS) Add-on V3.0 has local echo when using Serial over LAN (SoL)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Fix_available_Using_the_Intel_AMT_addon_for_Microsoft_SMS_2003_on_a_Dell_755_returns_a_UUID_error"&gt;Fix available: Using the Intel AMT add-on for Microsoft SMS 2003 on a Dell 755 returns a UUID error&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Fix_available_The_Intel_AMT_Addon_for_Microsoft_SMS_is_unable_to_communicate_with_the_SCS_over_a_standard_HTTP_connection"&gt;Fix available: The Intel AMT Add-on for Microsoft* SMS is unable to communicate with the SCS over a standard HTTP connection.&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Do_management_workstations_running_the_SMS_console_and_SMS_Addon_require_patches_as_outlined_in_the_documentation_for_the_IntelR_AMT_Addon_for_Microsoft_SMS"&gt;Do management workstations running the SMS console and SMS Add-on require patches as outlined in the documentation for the Intel(R) AMT Add-on for Microsoft SMS*?&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#OEM"&gt;OEM&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#BIOS_760071"&gt;BIOS&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Lenovo_M55p_returns_UUID00000_during_activation"&gt;Lenovo* M55p returns UUID=00000 during activation&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Dell_755_returns_a_duplicate_UUID_during_activation"&gt;Dell* 755 returns a duplicate UUID during activation&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Ctrl__P_prompt_missing_when_CMOS_battery_unplugged"&gt;Ctrl + P prompt missing when CMOS battery unplugged&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#When_Intel_AMT_is_disabled_there_is_a_HECI_driver_problem_in_the_HP_dc7800"&gt;When Intel AMT is disabled, there is a HECI driver problem in the HP* dc7800&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#What_does_the_Intel_AMT_status_application_dialog_box_signify"&gt;What does the Intel AMT status application dialog box signify?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Are_there_DLLs_in_the_operating_system_that_access_vPro"&gt;Are there DLLs in the operating system that access vPro?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Unattended_install_of_IntelR_AMT_client_softwaredrivers_not_working_properly_on_Microsoft_Windows"&gt;Unattended install of Intel(R) AMT client software/drivers not working properly on Microsoft Windows*&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SoLIDER_does_not_work_with_the_Lenovo_X61_Tablet"&gt;SoL/IDER does not work with the Lenovo* X61 Tablet&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SoLIDER_cant_be_disabled_on_Lenovo_M55p"&gt;SoL/IDER can’t be disabled on Lenovo* M55p&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#BIOS_password_screen_unavailable_on_HP_systems_during_SoL_session"&gt;BIOS password screen unavailable on HP* systems during SoL session&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Dell_D630c_laptops_reboot_when_sent_a_shutdown_command_via_Intel_AMT"&gt;Dell* D630c laptops reboot when sent a shutdown command via Intel® AMT&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#The_look_of_the_BIOS_Setup_screens_using_SoL_depends_on_OEM_support_for_terminal_emulation_modes"&gt;The look of the BIOS Setup screens using SoL depends on OEM support for terminal emulation modes&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Platform_Averill"&gt;Platform: Averill&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Are_the_Weybridge_SoL_and_HECI_drivers_backwardcompatible_with_Averill"&gt;Are the Weybridge SoL and HECI drivers backward-compatible with Averill?&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Profiles"&gt;Profiles&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SCS"&gt;SCS&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_SCS_returns_an_error_during_a_partial_unprovision"&gt;Intel SCS returns an error during a partial unprovision&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Validation_of_SCS_service_users_takes_over_30_minutes_when_installed_in_a_large_Active_Directory_environment"&gt;Validation of SCS service users takes over 30 minutes when installed in a large Active Directory environment&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Setup_and_Configuration_Service"&gt;Setup and Configuration Service&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#GoDaddy_requires_HighAssurance_SSL_certificates"&gt;GoDaddy* requires High-Assurance SSL certificates&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Using_static_IP_addresses_and_Basic_formerly_known_as_SMB_mode"&gt;Using static IP addresses and Basic (formerly known as SMB) mode&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Error_displays_when_provisioning_HP_6910p"&gt;Error displays when provisioning HP* 6910p&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Will_PKICH_consistently_support_wildcard_certificates_across_IntelR_AMT_versions"&gt;Will PKI-CH consistently support wildcard certificates across Intel(R) AMT versions?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SCS_service_crashes_due_to_excessive_logs"&gt;SCS service crashes due to excessive logs&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Network_Load_Balancing_of_SCS_Servers"&gt;Network Load Balancing of SCS Servers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Is_SNMP_Trap_Service_required_for_SCS"&gt;Is SNMP Trap Service required for SCS?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#IntelR_AMT_Active_Directory_error_message"&gt;Intel(R) AMT Active Directory error message&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Organizational_Unit_Field_in_Configuration_Parameters_must_be_populated_to_complete_provisioning"&gt;Organizational Unit Field in Configuration Parameters must be populated to complete provisioning&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Unable_to_access_web_interface_using_Kerberos_authentication"&gt;Unable to access web interface using Kerberos authentication&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Is_Static_IP_addressing_possible_in_Enterprise_Mode"&gt;Is Static IP addressing possible in Enterprise Mode?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Is_it_possible_to_have_an_operating_system_with_static_IP_address_and_Intel_Management_Engine_in_DHCP_mode"&gt;Is it possible to have an operating system with static IP address and Intel® Management Engine in DHCP mode?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Cannot_log_into_SCS_Console_with_Enterprise_Admin_account"&gt;Cannot log into SCS Console with Enterprise Admin account&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_MEBX_Web_UI_and_remote_admin_passwords_are_not_automatically_synchronized"&gt;Intel® MEBX, Web UI, and remote admin passwords are not automatically synchronized&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Using_international_keyboards_to_create_MEBx_passwords_via_Setup_and_Configuration_Service_SCS"&gt;Using international keyboards to create MEBx passwords via Setup and Configuration Service (SCS)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#What_is_the_Authorized_column_in_SCS"&gt;What is the Authorized column in SCS?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SOAP_error_0xCFFF06AC_when_attempting_remote_configuration"&gt;SOAP error (0xCFFF06AC) when attempting remote configuration&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Local_Manageability_Service_LMS_does_not_allow_host_VPN_traffic_when_environment_detection_is_not_defined"&gt;Local Manageability Service (LMS) does not allow host VPN traffic when environment detection is not defined&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Unable_to_remove_wireless_profiles_in_Intel_SCS"&gt;Unable to remove wireless profiles in Intel SCS&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Time_synchronization_errors_using_IntelR_SCS_3x_and_Active_Directory"&gt;Time synchronization errors using Intel(R) SCS 3.x and Active Directory&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SCS_Installation_Account_Security_Requirements"&gt;SCS Installation Account Security Requirements&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#SCS_50_Does_Not_Support_64bit_Operating_Systems"&gt;SCS 5.0 Does Not Support 64-bit Operating Systems&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#The_SCS_Console_Operator_role_does_not_appear_to_give_users_the_right_to_access_the_security_keys"&gt;The SCS Console Operator role does not appear to give users the right to access the security keys&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Consistent_RCFG_failure_with_SCS"&gt;Consistent RCFG failure with SCS&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#How_often_are_log_files_purged_in_Intel_SCS"&gt;How often are log files purged in Intel SCS?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Is_the_Intel_SCS_supported_on_EMT64_bit_versions_of_Microsoft_Windows_Server"&gt;Is the Intel® SCS supported on EMT64 bit versions of Microsoft Windows* Server?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Cant_import_setupbin_made_with_USBFILE2EXE_into_the_SCS"&gt;Can't import setup.bin made with USBFILE2.EXE into the SCS&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#The_SCS_Console_Operator_role_does_not_appear_to_give_users_the_right_to_access_the_security_keys_218611"&gt;The SCS Console Operator role does not appear to give users the right to access the security keys&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Minimum_security_requirements_for_installing_IntelR_SCS"&gt;Minimum security requirements for installing Intel(R) SCS&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#IntelR_SCS_is_only_supported_on_English_versions_of_Windows_Server_2008"&gt;Intel(R) SCS is only supported on English versions of Windows* Server 2008&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Provisioning"&gt;USB Provisioning&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_provisioning_only_effective_on_factory_new_systems"&gt;USB provisioning only effective on "factory new" systems&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Key_Configuration_Guidelines"&gt;USB Key Configuration Guidelines&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Compatibility_Matrix_for_Intel_Centrino_with_vPro_Technology_Intel_AMT_25"&gt;USB Compatibility Matrix for Intel® Centrino® with vPro Technology (Intel® AMT 2.5)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Compatibility_Matrix_for_Intel_vPro_Technology_Intel_AMT_3x"&gt;USB Compatibility Matrix for Intel® vPro™ Technology (Intel® AMT 3.x)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Compatibility_Matrix_for_Intel_vPro_Technology_Intel_AMT_4x"&gt;USB Compatibility Matrix for Intel® vPro™ Technology (Intel® AMT 4.x)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Compatibility_Matrix_for_Intel_vPro_Technology_Intel_AMT_5x"&gt;USB Compatibility Matrix for Intel® vPro™ Technology (Intel® AMT 5.x)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#USB_Provisioning_Tips_for_Lenovo_T61"&gt;USB Provisioning Tips for Lenovo T61&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#What_is_the_maximum_number_of_PIDPPS_pairs_that_can_be_used_during_USB_provisioning"&gt;What is the maximum number of PID/PPS pairs that can be used during USB provisioning?&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Automating_PIDPPS_key_generation_using_LANDesk_utility"&gt;Automating PID/PPS key generation using LANDesk utility&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;pre&gt;&lt;/pre&gt;&lt;p&gt;Check back often -- I'll be adding more content to this wiki on a weekly basis, at minimum. Don't see what you need? Send your wishlist to &lt;a class="jive-link-external-small" href="http://communities.intel.com/people/michelegartner"&gt;Michele Gartner&lt;/a&gt;.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Best_Practices"&gt;Best Practices&lt;/h1&gt;&lt;h4 id="Automatically_disabling_the_Intel_AMT_Privacy_Notification_window"&gt;Automatically disabling the Intel® AMT Privacy Notification window&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A Privacy Notification window automatically displays when each user logs into the Intel® AMT system.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;End users can disable this window by selecting the "Do not display this message" checkbox.&lt;/p&gt;&lt;p&gt;However, you can also disable the Privacy Notification window and still keep the application running by modifying a registry key.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;To modify the registry key:&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Open the registry and locate this key: HKEY_LOCAL_MACHINE\Software\Intel\Network_Services\atchk&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Create a new dword value named +MinimizePrivacyIconAtStart +and set it to 00000001.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.9.2007&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Changing_Terminal_Emulation_Type"&gt;Changing Terminal Emulation Type&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Some vendor BIOS versions only support the display of specific emulation types. Using this command, specific ISVs will be able to redirect and emulate without issue.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This command only applies to users running Altiris, HP Openview, and Microsoft SMS.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;On the console machine:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;At the &lt;strong&gt;Start&lt;/strong&gt; menu, select &lt;strong&gt;Run&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;In the &lt;strong&gt;Open&lt;/strong&gt; field, enter &lt;strong&gt;CMD&lt;/strong&gt; and click &lt;strong&gt;OK&lt;/strong&gt;. A command window opens.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;At the command prompt, type &lt;strong&gt;telnet&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;In the telnet session, type &lt;strong&gt;set term ansi&lt;/strong&gt; or &lt;strong&gt;set term vt100&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Type &lt;strong&gt;quit&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Your terminal emulation type is now set to ANSI or VT100, depending on what you entered. You can re-enter the telnet session at anytime and type d to verify the emulation type.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;NOTE:&lt;/strong&gt; If you do not properly quit the telnet session, the setting will not be saved.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;6.11.2008&lt;/p&gt;&lt;h4 id="Customizing_the_Intel_AMT_Status_dialog_box"&gt;Customizing the Intel® AMT Status dialog box&lt;/h4&gt;&lt;p&gt;&lt;span&gt;You can view the status of Intel AMT on a machine by double-clicking the system tray icon and choosing Status. This dialog box displays whether Intel AMT is enabled or disabled. It also has a hyperlink that allows the user to visit a site for more information about Intel AMT. You can customize this hyperlink to go to any site you wish. For example, you may want to modify it to point to your organization’s help desk page or to the Intel® vPro™ Expert Center (&lt;/span&gt;&lt;a class="jive-link-external-small" href="http://www.intel.com/go/vproexpert"&gt;http://www.intel.com/go/vproexpert&lt;/a&gt;&lt;span&gt;).&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;This procedure applies to Intel® AMT 2.5 and greater. See the readme file, included in the download, for more information.&lt;/p&gt;&lt;ol start="1"&gt;&lt;li&gt;Download the files to modify the registry.&lt;/li&gt;&lt;li&gt;The files are located here: &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-1797"&gt;http://communities.intel.com/docs/DOC-1797&lt;/a&gt; &lt;ol start="1"&gt;&lt;li type="a"&gt;Save the OemUrlRegistry.zip file to your desktop.&lt;/li&gt;&lt;li type="a"&gt;Extract the files: oementry.re_ and readme.txt.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li value="3"&gt;Customize the hyperlink. &lt;ol start="1"&gt;&lt;li type="a"&gt;Open oementry.re_ in a text editor.&lt;/li&gt;&lt;li type="a"&gt;Edit the destination hyperlink. The default entry is: "OemUrl"=&lt;a class="jive-link-external-small" href="http://www.intel.com/vpro"&gt;http://www.intel.com/vpro&lt;/a&gt;.&lt;/li&gt;&lt;li type="a"&gt;Rename oementry.re_ to oementry.reg.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li value="4"&gt;Run the *.reg file to modify the registry. &lt;ol start="1"&gt;&lt;li type="a"&gt;Double-click oementry.reg.&lt;/li&gt;&lt;li type="a"&gt;A cautionary dialog box displays. Click OK.&lt;/li&gt;&lt;li type="a"&gt;An information dialog box displays that the registry was modified. Click OK.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li value="5"&gt;Restart the computer.&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Intel_AMT_platform_may_have_up_to_8_client_certificates_that_can_define_different_8021x_profiles"&gt;Intel® AMT platform may have up to 8 client certificates that can define different 802.1x profiles&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Some users need to move a PC between several networks.  For example, a support technician may support multiple clients that require different client certificates.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Users may install up to 8 client certificates.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;2.24.2009 QA1312&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="How_To_Remove_the_CMOS_Battery_on_a_Lenovo_ThinkPad_T400"&gt;How To Remove the CMOS Battery on a Lenovo* ThinkPad* T400&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If the administrator forgets the MEBx password, the only way to clear the password is to remove the CMOS battery.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;To remove the CMOS battery on a Lenovo* ThinkPad* T400 you must remove the keyboard to get to the battery. The battery is located under the palm rest. Please refer to the Lenovo* instructions at the following URL**: &lt;a class="jive-link-external-small" href="http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-71484"&gt;HTTP://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-71484&lt;/a&gt;.&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;p&gt;**This URL to a non-Intel web site is provided for the reader's convenience. This is not an endorsement or recommendation by Intel of the site or products.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;strong&gt;Note for Intel(R) Anti-Theft (Intel AT) Technology users&lt;/strong&gt;: if your PC is enrolled in an Intel AT service, and you remove the CMOS battery, the ME may detect this as tampering and lock the system.  You will then need the Intel AT passphrase to unlock the system after you reboot.&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;em&gt;&lt;strong&gt;WARNING&lt;/strong&gt;:&lt;/em&gt; &lt;span&gt;&lt;strong&gt;To avoid personal injury or property damage, follow the manufacturer's safety instructions that apply henever accessing the inside of the product.&lt;/strong&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;strong&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;em&gt;CAUTION:&lt;/em&gt; &lt;span&gt;There is the danger of explosion if the battery is incorrectly replaced. When replacing the battery, use only the battery recommended by the equipment manufacturer and follow the manufacturer's instructions. Electrostatic Discharge&lt;/span&gt; &lt;span&gt;ESD) can damage disk drives, boards, and other parts. We recommend that you perform all procedures at an ESD workstation.&lt;/span&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.9.2009 QA1330&lt;/p&gt;&lt;h4 id="Root_certificate_size_limit_is_2048bits"&gt;Root certificate size limit is 2048-bits&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Intel(R) AMT is incompatible with a 4096-bit PKI if Intel(R) AMT systems need to validate a certificate chain containing this key size. For example, in 802.1X networks.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If a customer already has a PKI with a 4096-bit root certificate, you can work around this issue by adding a 2048-bit root CA and then using this to issue certain certificate (for example, RADIUS).&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;4.2.2009 QA1341&lt;/p&gt;&lt;h4 id="How_to_hide_the_IntelR_Management__Security_Status_IMSS_tool_system_tray_icon"&gt;How to hide the Intel(R) Management &amp;amp; Security Status (IMSS) tool system tray icon&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;To hide the IMSS system tray icon, delete the key at the following registry location:&lt;br/&gt;HKLM\Software\Microsoft\WindowsCurrentVersion\Run\Picon\"C:\Program Files\Common Files\Intel\Privacy Icon\PrivacyIconClient.exe"&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;4.2.2009 QA1342&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Tips_on_ME_firmware_updates"&gt;Tips on ME firmware updates&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;To successfully upgrade your ME firmware, follow the guidelines listed below.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;&lt;span style="font-size: 12pt;"&gt;Version number format for ME firmware&lt;br/&gt;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;&lt;div&gt;Intel(R) AMT firmware versions use the following format:&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;&lt;strong&gt;W.X.Y.ZZZZ&lt;/strong&gt;&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;W = platform&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;X = major version&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;Y = minor version&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;ZZZZ = build number&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;p&gt;&lt;span style="font-size: 12pt;"&gt;&lt;strong&gt;Rules for successful upgrades&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;(1) The platform number (W) of the update must match the existing firmware.&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;(2) The major number (X) of the update must be the same, or higher, than the existing firmware. The only two exceptions are: 2.0 can only be upgraded to 2.1 or 2.2; version 2.5 can only be upgraded to 2.6.&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;(3) The minor version (Y) for the update must be greater than, or equal to, the minor version for the existing version if the major version is unchanged (for example, 3.0.0 to 3.0.1).&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;(4) Always use the FWUPDLCL utility from the upgrade toolkit.&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;(5) &lt;strong&gt;ME Firmware Local Updates&lt;/strong&gt; must be enabled in the MEBx, or the &lt;strong&gt;Local FWU Override Counter&lt;/strong&gt; and &lt;strong&gt;Local Firmware Override Qualifier&lt;/strong&gt; must be set appropriately to allow an override.&lt;/div&gt;&lt;div&gt;&lt;br/&gt;&lt;/div&gt;&lt;div&gt;TIP: Run MEInfoWin.exe against the platform, or log-on to the MEBx (on the local machine) to check, or change, the ME Firmware Local Update setting. You can also check or change the status of the FWU Override Counter and FWU Override Qualifier settings.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.11.2009 QA1359&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="IntelR_AMT_does_not_allow_multiple_simultaneous_commands"&gt;Intel(R) AMT does not allow multiple simultaneous commands&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;For an example of this problem, if a SoL session is active from the Microsoft* SCCM Out of Band console, then the Intel® AMT firmware will not process a collection-based power control command from the console.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div id="solution"&gt;Intel® AMT firmware will ignore a second command if it is still processing an active command. This is a security feature.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.11.2009 QA1327&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Password_issue_causes_WebUI_to_report_The_system_may_be_under_attack_in_the_event_log"&gt;Password issue causes WebUI to report "The system may be under attack" in the event log&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The password policy is configured by the OEM during manufacturing. The primary setting allows a one-time chagne from Admin/admin to a unique password and to have both the remote and local access synched-up. If you changed the password on the remote client you will have two passwords. This is intended to allow customers to have a unique password for local access and to allow the user to change it randomly to ensure the security of the system.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div id="solution"&gt;The system was working as designed. The local MEBx password and the WebUI remote passwords may be different if the user has changed the MEBx password on the local machine.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;11.12.2009 QA1389&lt;/p&gt;&lt;h1 id="BIOS"&gt;BIOS&lt;/h1&gt;&lt;h4 id="F10_does_not_exit_BIOS_on_HP_clients"&gt;F10 does not exit BIOS on HP clients&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;During a SoL session to an HP* client, pressing F10 does not exit BIOS.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Press ESC and 0 (zero) at the same time as an alternative to exit BIOS.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.30.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="The_TCPIP_DHCP_Mode_setting_in_MEBx_must_be_enabled_for_remote_control_of_an_IntelR_AMT_platform"&gt;The TCP/IP DHCP Mode setting in MEBx must be enabled for remote control of an Intel(R) AMT platform&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;Current tools from Intel do not control the TCP/IP DHCP Mode setting. Additionally, only an un-provisioned platform will give you the option to set this option locally.&lt;/div&gt;&lt;div&gt;&lt;br/&gt;Disabling TCP/IP DHCP Mode requires an onsite physical touch to either do a clear CMOS, or from MEBx, to do a full unprovision. All tools related to remote provisioning, un-provisioning, or updating/modifying Intel® AMT firmware settings require that TCP/IP already be enabled. There is also no known in-band solution using ISV applications.&lt;/div&gt;&lt;div&gt;&lt;br/&gt;If the TCP/IP DHPC Mode setting is set to NONE, then the IP address is 0.0.0.0 and the ME cannot receive or execute any commands.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;When purchasing a system, customers should verify that their OEM has a tool to remotely turn on the TCP/IP setting before deploying systems with the TCP/IP setting disabled.&lt;br/&gt;&lt;br/&gt;In some cases where the DHCP Mode setting in the MEBx is Enabled, but the user is not ready to provision the systems already deployed, they will see heavy DHCP network traffic. To avoid heavy network traffic on the DHCP server caused by the hello packets from numerous unprovisioned systems, set the Manageability Feature Selection setting to NONE and keep the TCP/IP DHCP Mode setting enabled.&lt;br/&gt;&lt;br/&gt;If the systems with the TCP/IP DHCP Mode disabled are already deployed, and the OEM doesn't have a tool to remotely enable this setting, the administrator must go to each system and either clear CMOS, or do a full unprovision from MEBx.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;3.3.2009 QA1309&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="After_reflashing_a_full_image_is_a_clear_CMOS_required"&gt;After reflashing a full image, is a "clear CMOS" required?&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;Is a "Clear CMOS" required after a full image flash?&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;No, the "clear CMOS" is not required, but is recommended on systems with legacy BIOS code (as opposed to UEFI) if problems arise after full image flash (i.e., the Clear CMOS can be used as a "fix" for post-flash issues).&lt;/div&gt;&lt;br/&gt;&lt;div&gt;Also, it is recommended that you use an image tool with full erase, program, and reboot steps; perform an update on a duplicate/test environment first; use defaults, then compare updated file to source file BEFORE rebooting (should be 100% compare). After reboot, go into BIOS and set optimal defaults.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;6.1.2009 QA1355&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Remote_BIOS_update_with_AMT_Commander_does_not_see_BIOS_update_files"&gt;Remote BIOS update with AMT Commander does not see BIOS update files&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;When using AMT Commander to perform a remote BIOS update using SOL/IDE-R, AMT Commander does not display the text of the BIOS update files; it only displays the bootable ISO files.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;&lt;div&gt;Problem is likely with terminal emulation between remote system running AMT Commander and target system where BIOS update is to be performed. AMT Commander (part of AMT SDK) contains many terminal emulators, not just the common vt100 or PC ANSI. Ensure that the AMT Commander terminal emulation matches the target system's terminal emulation (contact target system OEM if necessary).&lt;/div&gt;&lt;br/&gt;&lt;div&gt;Also, some OEM's supply a local keyboard lockout feature during remote SOL/IDE-R sessions. This can get corrupted so that the remote keyboard is locked out, not the local one. If this happens, the target system OEM must supply an update for the corrupt feature. AMT Commander contains a control for local keyboard lock; make sure this is set to off.&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;5.27.2009 QA1356&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="IntelR_AMT_Event_log_includes_Platform_Event_Traps_from_the_BIOS"&gt;Intel(R) AMT Event log includes Platform Event Traps from the BIOS&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;Some events listed in the Intel(R) AMT event log are generated by the BIOS and simply passed through to the Intel(R) AMT event log. For example, if the system fails to boot using the PXE option, you may see a "System boot failure" event in the log. The source may say Intel(R) AMT only because it was passed by the BIOS to the Intel(R) AMT firmware.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;&lt;div&gt;No solution is required. This is expected behavior.&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;6.1.2009 QA1345&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Client_Drivers"&gt;Client Drivers&lt;/h1&gt;&lt;h4 id="Using_Intel_vPro_technology_and_Linux"&gt;Using Intel vPro technology and Linux&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Where can I find more information about Intel vPro technology on Linux?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Information about Linux support is available at the &lt;a class="jive-link-external-small" href="http://openamt.org/"&gt;Open Source Intel AMT Drivers and Tools\&lt;/a&gt; site.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;10.11.2007&lt;/p&gt;&lt;h4 id="Linuxbased_wireless_drivers"&gt;Linux-based wireless drivers&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Where can I find the most recent Linux drivers for an Intel vPro system?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Visit &lt;a class="jive-link-external-small" href="http://www.intellinuxwireless.org/"&gt;http://www.intellinuxwireless.org/&lt;/a&gt; to download Intel wireless drivers.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.9.2007&lt;/p&gt;&lt;h4 id="Wireless_management_does_not_work_when_the_operating_system_is_running"&gt;Wireless management does not work when the operating system is running&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Wireless management does not work when the operating system is running.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Check if there are missing or faulty Intel AMT drivers (HECI &amp;amp; LMS/SOL) in Microsoft Windows*. Get the latest drivers from the OEM's web site and install them. Once the drivers are installed, the Intel(R) Management Engine should work properly with the wireless connection.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.30.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="LMSSOL_driver_setup_program_fails_to_install_privacy_icon_if_installation_path_includes_square_brackets"&gt;LMS/SOL driver setup program fails to install privacy icon if installation path includes square brackets&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If the path to the LMS/SOL driver setup.exe contains square&lt;br/&gt;brackets, then the driver will be installed but the privacy&lt;br/&gt;icon will not be installed. For example, setup will fail with&lt;br/&gt;this path: c:\drivers\[HP]\lms_sol\setup.exe.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue is expected to be fixed in Intel® AMT 4.2.&lt;/p&gt;&lt;div id="solution"&gt;To workaround the issue, remove the square brackets from the&lt;br/&gt;path.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;4.2.2009 QA1333&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Infrastructure"&gt;Infrastructure&lt;/h1&gt;&lt;h4 id="Is_an_IDER_recommended_over_a_WAN"&gt;Is an IDE-R recommended over a WAN?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Is there a performance hit for IDE-R over a WAN?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;We do not recommend using an IDE-R session to boot large CD-ROM images over a WAN. Instead, we recommend using a stripped down IDE-R image that can load up a network stack on the AMT client. The network stack can be used to access local shares at the branch that have the tools you need to either rebuild the OS or diagnose problems.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.8.2008&lt;/p&gt;&lt;h4 id="Firewalls_may_not_let_Intel_AMT_clients_communicate_with_management_consoles"&gt;Firewalls may not let Intel® AMT clients communicate with management consoles&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The wired LAN NICs are not recognized by the Intel® AMT management consoles. They do show up in the DHCP listings. Only the wireless NICs were discovered as Intel® AMT devices. IPCONFIG on each notebook shows IP addresses assigned to both WLAN and LAN NICs.&lt;/p&gt;&lt;p&gt;When the firewalls are turned off, the Intel® AMT consoles can communicate with the LAN NICs.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Firewalls can prevent clients from registering an FQDN (fully qualified domain name), which prevents them from being discovered by the console. Verify that the firewall is not configured to block these kinds of requests.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.25.2008&lt;/p&gt;&lt;h4 id="Secondary_DNS_IP_makes_Intel_AMT_configuration_fail_in_basic_formerly_SMB_mode"&gt;Secondary DNS IP makes Intel® AMT configuration fail in basic (formerly SMB) mode&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When configuring Intel® AMT in basic (formerly SMB) mode during boot up, some values for the secondary DNS server IP address make the configuration fail.&lt;/p&gt;&lt;p&gt;If a secondary DNS server's last octet value is 223 or higher, the configuration fails.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This is a known issue in the Intel® Management Engine and will be fixed in the next release. The current workaround is to change the secondary DNS server's IP address, or to not use the secondary DNS server at all in the configuration.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.25.2008&lt;/p&gt;&lt;h4 id="ME_NIC_remains_at_lowest_negotiated_speed_and_half_duplex_mode_after_booting"&gt;ME NIC remains at lowest negotiated speed and half duplex mode after booting&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When you reboot the system and enter a SoL/IDER session, the ME NIC will remain in the lowest negotiated speed setting and half duplex mode if the SoL/IDER session remains connected during boot. The NIC does not renegotiate to the highest available speed or full duplex mode after the operating system boots.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;To force the ME NIC to renegotiate to full speed/full duplex mode, disconnect the SoL/IDER session then reconnect.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.25.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="GenScript_produces_errors_on_Windows_Vista_OS_Windows_Server_2008_and_clients_with_8021x_profiles"&gt;GenScript produces errors on Windows* Vista OS, Windows* Server 2008, and clients with 802.1x profiles&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The Intel® WS-MAN translator package used with Microsoft* SCCM 2007 SP1 generates some errors due to scripting language changes introduced in Windows* Vista.&lt;br/&gt;The scripts will not run correctly on Microsoft* Vista and Microsoft* Server 2008 operating systems. Also, wired 802.1X scripts produced by GenScript only execute properly the first time they are run.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;An updated version of the WSMAN translator is available.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.3.2009 QA1322&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Usage_of_Locally_Administered_Address_on_IntelR_Active_Management_Technology_enabled_systems"&gt;Usage of Locally Administered Address on Intel(R) Active Management Technology enabled systems&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;An incompatibility exists between Intel(R) Active Management Technology (Intel(R) AMT) and Locally Administered Address (LAA) environments. As a result, Intel AMT enabled systems configured to work in LAA environments might encounter LAN disconnects.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A Locally Administered Address (LAA) is an option allowing users to set their own MAC address on the platform and thus bypass the Burned-in address (BIA) MAC. Intel AMT was not designed to support LAA environments and there are no plans to add this capability in the near future.&lt;br/&gt;&lt;br/&gt;Intel recommends avoiding usage of LAA together with Intel AMT technology to avoid this issue.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;5.18.2009 QA1350&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="ICMP_Router_Discovery_Protocol_IRDP_is_not_supported"&gt;ICMP Router Discovery Protocol (IRDP) is not supported&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;ICMP turned on by DHCP Option 31. ICMP is not supported by Intel(R) AMT technology.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;No solution is available.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p&gt;11.25.2009 QA1377&lt;/p&gt;&lt;h1 id="ISV"&gt;ISV&lt;/h1&gt;&lt;h2 id="Altiris"&gt;&lt;strong&gt;Altiris&lt;/strong&gt;&lt;/h2&gt;&lt;h4 id="Troubleshooting_DNS_when_configuring_Altiris"&gt;Troubleshooting DNS when configuring Altiris&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;DNS configuration issues display when configuring Altiris.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use these troubleshooting tips to help resolve DNS configuration issues with Altiris:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Verify that the Altiris host has fully qualified records in the DNS infrastructure. This would constitute an &lt;strong&gt;&lt;em&gt;A&lt;/em&gt;&lt;/strong&gt; record for &lt;strong&gt;&lt;em&gt;forward lookups&lt;/em&gt;&lt;/strong&gt; and a &lt;strong&gt;&lt;em&gt;PTR&lt;/em&gt;&lt;/strong&gt; record for &lt;strong&gt;&lt;em&gt;reverse lookups&lt;/em&gt;&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Make sure the Intel Setup and Configuration Service (SCS) is up and running on the box.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Upgrade the SCS Console to the current version. This process is not supported by Altiris and is only for troubleshooting.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;&lt;strong&gt;IMPORTANT:&lt;/strong&gt; When you upgrade, only install the console. DO NOT upgrade the entire SCS application.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;To upgrade to the current version:&lt;/strong&gt;&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;div style="margin-left: 2em"&gt;&lt;ol start="1"&gt;&lt;li&gt;Download the SCS package at &lt;a class="jive-link-external-small" href="http://softwarecommunity.intel.com/articles/eng/1025.htm"&gt;http://softwarecommunity.intel.com/articles/eng/1025.htm&lt;/a&gt;.&lt;br/&gt;&lt;/li&gt;&lt;li&gt;When the download is complete, open the ZIP file and double-click &lt;strong&gt;3.1.0.7.zip&lt;/strong&gt;.&lt;br/&gt;&lt;/li&gt;&lt;li&gt;Double-click &lt;strong&gt;AMTConsole.zip&lt;/strong&gt; and run &lt;strong&gt;AMTConsole.exe&lt;/strong&gt;.The console will prompt you to use the fully qualified domain name. An SSL session may be necessary to connect to it, depending on the server configuration. The console client works like a web browser and a URL is required to connect to the SCS, for example: &lt;a class="jive-link-external-small" href="http://server.something.com/atmscs"&gt;http://server.something.com/atmscs&lt;/a&gt; or &lt;a class="jive-link-external-small" href="https://server.something.com/atmscs"&gt;https://server.something.com/atmscs&lt;/a&gt;.&lt;br/&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;12.20.2007&lt;/p&gt;&lt;h4 id="Can_the_Default_provisionserver_naming_conventions_be_changed"&gt;Can the Default 'provisionserver' naming conventions be changed?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Can Intel AMT firmware be reconfigured to change the default 'provisionserver' naming convention to a value of a customer's choosing?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The provisionserver value is hard coded and cannot be changed. It is recommended that the customer set up a second A record or a CNAME record in the DNS that points the provisionserver.yourdomain.com to the ISV server.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.8.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Hardware_inventory_on_Altiris_console_requires_Altiris_inventory_solution"&gt;Hardware inventory on Altiris* console requires Altiris* inventory solution&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Altiris* has a complete Server and Client inventory application/service that is independent of Intel(R) AMT features. An agent is required to obtain this level of support in Altiris* products.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div id="solution"&gt;Refer to the following URL**: &lt;a class="jive-link-external-small" href="http://www.symantec.com/business/inventory-solution%20(servers"&gt;HTTP://www.symantec.com/business/inventory-solution&lt;/a&gt; (servers), or &lt;a class="jive-link-external-small" href="http://www.symantec.com/business/solutions/projects/projectdetail.jsp?solid=sol_infrastruct_op&amp;amp;solfid=sol_client_management&amp;amp;projectid=client_discovery_inventory"&gt;http://www.symantec.com/business/solutions/projects/projectdetail.jsp?solid=sol_infrastruct_op&amp;amp;solfid=sol_client_management&amp;amp;projectid=client_discovery_inventory&lt;/a&gt; (clients). &lt;br/&gt;**This URL is provided for the reader's convenience.?It should not be construed as an endorsement by Intel of the products or services on the web site.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p&gt;11.25.2009 QA1338&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h2 id="LANDesk"&gt;LANDesk&lt;/h2&gt;&lt;h4 id="No_drivers_required_for_bare_metal_provisioning"&gt;No drivers required for bare metal provisioning&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A customer with LANDesk* LDMS 8.8 or similar provisioning server does not need to load drivers or an OS image on the Intel(R) AMT clients to perform bare-metal provisioning.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;No drivers are required for bare-metal provisioning of an Intel(R) AMT client. The system administrator will, however, need to pre-populate the provisioning server database with the client configuration information (UUID, FQDN, OU if Active Directory is used, Profile). Refer to the LANDesk documentation for information on how to enter the client configuration information into LDMS 8.8. The Intel AMT client will send out a hello packet as soon as the network and power cables are plugged in. If the provisioning server is found, and the client configuration information is in the provisioning database, then the client will be provisioned.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.28.2008&lt;/p&gt;&lt;h4 id="Need_to_set_LANDesk_root_certificate_as_trusted_certificate"&gt;Need to set LANDesk* root certificate as trusted certificate&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;In the default configuration, the LANDesk root certificate is not trusted by the Microsoft* CA. The user is then unable to use the WebUI.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;From Microsoft* Internet Explorer, add the LANDesk* root certificate to the list of trusted certificates.&lt;/div&gt;&lt;br/&gt;&lt;ol start="1"&gt;&lt;li&gt;Open Microsoft* Internet Explorer.&lt;/li&gt;&lt;li&gt;Choose Tools-&amp;gt;Internet Options.&lt;/li&gt;&lt;li&gt;Click on the Content tab.&lt;/li&gt;&lt;li&gt;Click on the Certificates tab.&lt;/li&gt;&lt;li&gt;Under the Trusted Root Certificates tab, import the root certificates.&lt;/li&gt;&lt;li&gt;Under the Intermediate Certificate Authorities tab, import the intermediate certificates.&lt;/li&gt;&lt;li&gt;Verify that the certificate used can be traced back to the root.&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.10.2009  QA1370&lt;/p&gt;&lt;h4 id="LANDesk_Management_Suite_88_SP2_patch_fixes_loss_of_inband_connectivity"&gt;LANDesk* Management Suite 8.8 SP2 patch fixes loss of in-band connectivity&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;After provisioning, the in-band network connection on some Intel(R) AMT systems may shut down. The LANDesk console will then place the systems in remediation. These Intel(R) AMT systems can, however, still be managed with LANDesk* OOB tools and the Intel(R) AMT Web GUI. This is an intermittent issue. The time between provisioning the system and the loss of in-band connectivity ranges from a few minutes to about an hour.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;&lt;div&gt;If you have LANDesk* Management Suite 8.8 SP2, and you have lost in-band connectivity, but you can still access the remote systems using OOB tools, try the following patch or upgrade to a later LANDesk* service pack (SP3 or later). The URL** for the patch is: &lt;span style="color: #0000ff;"&gt;&lt;a class="jive-link-external-small" href="http://community.landesk.com/downloads/ServicePack/LD-88-AMT-CR20525-88.zip"&gt;HTTP://community.landesk.com/downloads/ServicePack/LD-88-AMT-CR20525-88.zip&lt;/a&gt;&lt;/span&gt;&lt;/div&gt;&lt;br/&gt;&lt;div&gt;&lt;span style="font-size: 10pt; color: #000000; font-family: Arial;"&gt;**This URL to a third-party site is provided for the reader's convienience.  This should not be construed as a &lt;span style="font-size: 10pt; color: #000000; font-family: Arial; mso-fareast-font-family: SimSun; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA; mso-bidi-font-family: Arial;"&gt;recommendation by Intel &lt;/span&gt;for the products or services provided by the third party.&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.11.2009  QA1344&lt;/p&gt;&lt;h4 id="LANDesk_88_SP2_console_requires_repeated_deletion_of_two_directories_when_provisioning"&gt;LANDesk* 8.8 SP2 console requires repeated deletion of two directories when provisioning&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The RootCA and the SubCA directories must be deleted repeatedly to enable provisioning to continue.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;&lt;div&gt;No solution exists at this time. The issue is expected to be fixed in v8.8 SP3.&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;10.09.2009  QA1349&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h2 id="Microsoft_ConfigMgr_see_also_httpcommunitiesintelcomopenportdocsDOC1627cf"&gt;Microsoft ConfigMgr &lt;span style="font-size: 10pt;"&gt;(see also:&lt;/span&gt; &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-1627"&gt;&lt;span style="font-size: 10pt;"&gt;http://communities.intel.com/openport/docs/DOC-1627#cf&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: 10pt;"&gt;)&lt;/span&gt;&lt;/h2&gt;&lt;h4 id="Enabling_native_no_translation_required_support_within_Microsoft_SCCM_SP1"&gt;Enabling native (no translation required) support within Microsoft SCCM SP1&lt;/h4&gt;&lt;p&gt;A BIOS update is available to provide native support within Microsoft SCCM SP1 for Dell 755, HP DC7800, and Lenovo M57p computers.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;p&gt;OEM Model&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Link to BIOS Update&lt;/p&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Dell 755&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://support.dell.com/support/downloads/download.aspx?c=us&amp;amp;l=en&amp;amp;s=gen&amp;amp;releaseid=R185551&amp;amp;SystemID=PLX_PNT_P4_755&amp;amp;servicetag=&amp;amp;os=WLH&amp;amp;osl=en&amp;amp;deviceid=15256&amp;amp;devlib=0&amp;amp;typecnt=0&amp;amp;vercnt=6&amp;amp;catid=-1&amp;amp;impid=-1&amp;amp;formatcnt=1&amp;amp;libid=1&amp;amp;fileid=253423"&gt;Click here.&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Lenovo M57p&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&amp;amp;lndocid=MIGR-69827"&gt;Click here.&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;HP DC7800&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=12454&amp;amp;prodSeriesId=3459241&amp;amp;prodNameId=3459245&amp;amp;swEnvOID=2105&amp;amp;swLang=13&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=vc-59639-1"&gt;Click here.&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.23.2008&lt;/p&gt;&lt;h4 id="Virtual_adapters_may_cause_network_discovery_to_fail"&gt;Virtual adapters may cause network discovery to fail&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When discovering vPro systems via a console that has a virtual adapter enabled with an IP address assigned, such as Microsoft SCCM, the discovery process may fail if the virtual adapter IP address is used for the discovery process.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Before performing the discovery, disable any virtual adapters that were created by software such as VMWare.*&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.30.2008&lt;/p&gt;&lt;h4 id="Microsoft_SCCM_unable_to_use_Intel_AMT_features_when_run_on_Microsoft_Vista_Operating_System"&gt;Microsoft* SCCM unable to use Intel® AMT features when run on Microsoft* Vista* Operating System&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When the Microsoft* SCCM management console is run on a Microsoft* Vista* SP1 operating system, all Intel® AMT based objects and functionality is missing.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;No solution is available at this time.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;1.29.2009 (QA1304)&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Microsoft_SCCM_2007_SP1_hotfix_rollup_KB960804_includes_KB959040"&gt;Microsoft* SCCM 2007 SP1 hotfix roll-up KB960804 includes KB959040&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Microsoft* System Center Configuration Manager 2007 Service Pack 1 (SP1) hotfix roll-up KB960804 includes KB959040 (a fix to enable PKI provisioning with Intel® AMT 2.2 and 2.6.) The original description of the roll-up incorrectly omitted the KB959040 hotfix.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;To get KB959040 hotfix, users may download the KB960804 hotfix roll-up.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Refer to the Micorsoft* support website for more information about the hotfix packages. The Microsoft* URL** is: &lt;a class="jive-link-external-small" href="http://support.microsoft.com/kb/960804"&gt;http://support.microsoft.com/kb/960804&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;&lt;span style="font-size: 8pt;"&gt;**This URL is provided for the reader's convenience. It is not an endorsement of products or services by Intel Corporation.&lt;/span&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;2.24.2009 QA1323&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="SoLIDER_fails_on_Microsoft_SCCM_2007_SP1_with_twotiered_PKI_model"&gt;SoL/IDER fails on Microsoft SCCM 2007 SP1 with two-tiered PKI model&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;SoL and IDER fails using Microsoft* SCCM in an environment with a Root CA and a Subordinate Issuing CA.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue has been fixed by a hotfix for Microsoft* SCCM 2007 SP1. URL for hotfix** &lt;a class="jive-link-external-small" href="http://support.microsoft.com/hotfix/kbHotfix.aspx?kbnum=960804"&gt;HTTP://support.microsoft.com/hotfix/kbHotfix.aspx?kbnum=960804&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;&lt;span style="font-size: 8pt;"&gt;**This URL is provided for the reader's convenience. It is not an endorsement of products or services by Intel Corporation.&lt;/span&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;2.24.2009 QA1319&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Failure_of_collectionbased_power_control_in_Microsoft_SCCM_SP1"&gt;Failure of collection-based power control in Microsoft* SCCM SP1&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;In a Microsoft* SCCM hierarchy with a central site and a primary child site, power control operations from the central site work for some clients and fail for others. The same power control operations work correctly from the child site.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Not all client settings are being transferred up the Microsoft SCCM hierarchy to the central database. This issue will be resolved in the Microsoft SCCM SP2. Alternatively, system administrators may change the TlsMode setting in the dbo.AMT_MachineProperties table in the SCCM site database, it should be set to "1" for each client.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;10.09.2009 QA1362&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Cannot_provision_HP_DC7700_using_Microsoft_ConfigMgr_SP1_and_PKI_method"&gt;Cannot provision HP* DC7700 using Microsoft* ConfigMgr SP1 and PKI method&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The HP* DC7700 with Intel(R) AMT firmware build 2.2.10.1039 has a date/time stamp issue with the certificates that prevents remote provisioning. The Microsoft ConfigMgr logfile AMTOPMGR.LOG shows error 0x80090308 that indicates a problem with the certificate.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Update the firmware to to 2.2.20 or later. The firmware is available on the HP* website.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;11.16.2009 QA1364&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Management_Engine"&gt;Management Engine&lt;/h1&gt;&lt;h4 id="Maximum_number_of_agents_that_can_be_monitored_simultaneously"&gt;Maximum number of agents that can be monitored simultaneously&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;How many agents can the Intel Management Engine monitor at one time?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This data is undocumented, however, testing shows that Intel AMT 2.0 can monitor up to sixteen agents.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;NOTE:&lt;/strong&gt; The number of agents that can be monitored depends on how the ISV is implementing agent presence.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;12.20.2007&lt;/p&gt;&lt;h4 id="HewlettPackard_6910P_returns_UUID00000_during_activation"&gt;Hewlett-Packard 6910P returns UUID=00000 during activation&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;HP 6910p returns a hello packet of UUID=00000 during activation.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This is a known issue with the firmware and will be fixed when the 2008 platform is released.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Meanwhile, your customers can request a BIOS update from HP to work around this issue.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;12.20.2007&lt;/p&gt;&lt;h4 id="Running_virtual_machines_and_DHCP_can_cause_Intel_AMT_to_be_inaccessible"&gt;Running virtual machines and DHCP can cause Intel AMT to be inaccessible&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Using DHCP in a virtual machine can cause Intel AMT to become inaccessible when you close the virtual machine session. This is because your computer and Intel AMT will now have different IP addresses.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;To work around this issue, exit the virtual machine session(s) and then do one of the following:&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Reboot your system.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;OR&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Release and renew the IP address as follows:&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Click Start and choose Run.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Enter cmd and click OK.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;At the command prompt, type:&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;/ul&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;em&gt;ipconfig /release&lt;/em&gt;&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;br/&gt;&lt;strong&gt;&lt;em&gt;ipconfig /renew&lt;/em&gt;&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;This is a known issue and will be updated as more information is available.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.24.2008&lt;/p&gt;&lt;h4 id="Wildcard_certificates_are_currently_not_supported_for_remote_configuration"&gt;Wildcard certificates are currently not supported for remote configuration&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When provisioning enterprises with multiple domains via remote configuration, individual certificates are required for each domain that needs to communicate with the Management Console. Wildcard certificates are currently not supported.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Wildcard certificate support is a feature request for AMT 3.2 (Weybridge) and AMT 2.6 (Centrino).&lt;/p&gt;&lt;p&gt;Meanwhile, you can workaround this issue by deploying an SCS server and a certificate for each domain.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;MORE INFORMATION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue will be updated as more information becomes available.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.24.2008&lt;/p&gt;&lt;h4 id="No_inventory_data_available"&gt;No inventory data available&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Inventory data does not appear after provisioning an Intel AMT client, even though the provisioning process was successful and without errors.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;POST needs to occur for the data transfer to take place. The inventory data resides within the BIOS SMI tables and cannot be successfully transferred to the Intel Management Engine and viewed by the WebUI or retrieved programmatically. The BIOS and ME handshake must occur during POST to transfer data. Make sure the system has run through POST, so that the inventory data is transferred from BIOS into ME.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.30.2008&lt;/p&gt;&lt;h4 id="Weybridge_issue_causing_network_disconnects_impacting_Dell_Optiplex_755"&gt;Weybridge issue causing network disconnects; impacting Dell Optiplex 755&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Currently shipping non-provisioned Intel(R) vPro(TM) or Intel(R) AMT PCs on some Weybridge configurations may report a network disconnect/reconnect on five minute cycles when the 24 hour provisioning period expires while in a low power state. An unused security feature of Intel(R) AMT triggers the network disconnect and then resets the network connection on 5 minute cycles.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue has been resolved in the A09 BIOS release from Dell for the Optiplex 755. The BIOS release is available at the following URL:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://support.us.dell.com/support/downloads/download.aspx?c=us&amp;amp;l=en&amp;amp;s=gen&amp;amp;releaseid=R181510&amp;amp;formatcnt=1&amp;amp;libid=0&amp;amp;fileid=247483"&gt;http://support.us.dell.com/support/downloads/download.aspx?c=us&amp;amp;l=en&amp;amp;s=gen&amp;amp;releaseid=R181510&amp;amp;formatcnt=1&amp;amp;libid=0&amp;amp;fileid=247483&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://support.us.dell.com/support/downloads/download.aspx?c=us&amp;amp;l=en&amp;amp;s=gen&amp;amp;releaseid=R181510&amp;amp;formatcnt=1&amp;amp;libid=0&amp;amp;fileid=247483"&gt;Click here for the update.\&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;h4 id="Synchronizing_the_operating_system_and_the_Intel_AMT_hostname"&gt;Synchronizing the operating system and the Intel AMT hostname.&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Is there an automated way to synchronize the operating system and Intel(R) AMT hostname?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-1431"&gt;Intel(R) AMT Reflector tool\&lt;/a&gt; is now available on the Intel(R) vPro(TM) Expert Center.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;See the &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-1171"&gt;Tools wiki\&lt;/a&gt; for more helpful vPro tools.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;h4 id="Best_Practices_Setting_up_application_servers_and_Internet_Explorer_for_IntelR_AMT_Kerberos_support"&gt;Best Practices: Setting up application servers and Internet Explorer* for Intel(R) AMT Kerberos support&lt;/h4&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Verify that your Internet Explorer settings are correct for pass through authentication.&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Open Internet Explorer and choose Tools &amp;amp;gt; Internet Options &amp;amp;gt; Advanced Tab.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Select Enable Integrated Windows Authentication. Exit and restart Internet Explorer before attempting to access the Intel AMT device.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Install these Kerberos patches on the system you will use to access the Intel(R) AMT device.&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;WindowsServer2003-KB899900-X86-ENU.exe&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;WindowsServer2003-KB908209-X86-ENU.exe&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;WindowsServer2003-KB899900-X86-ENU.reg&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;If you are using Windows XP* as the operating system for the computer used to access the Intel AMT web interface, then install these patches:&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;WindowsXP-KB899900-X86-ENU.exe&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;WindowsXP-KB908209-X86-ENU.exe&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;WindowsXP-KB899900-X86-ENU.reg&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Ensure that the time settings for the Intel AMT client(s), domain controllers, and the application server are synchronized.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Before provisioning:&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Create an AMT OU on the domain controller existing on the domain on which your Intel(R) AMT devices reside. For example, if your device exists on child.parent.com, and your provisioning server (or Intel SCS) resides on parent.com, then create an OU for AMT objects on child.parent.com.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;IMPORTANT:&lt;/strong&gt; If there are multiple domains, then add an OU to each domain.&lt;/p&gt;&lt;/blockquote&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Provision your Intel AMT client.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;5.30.2008&lt;/p&gt;&lt;h4 id="Network_issues_with_NS_Lookup"&gt;Network issues with NS Lookup&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A single vPro machine can be accessed via WebUI, but does not appear in DNS. Its name does not get resolved in NSLookup?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;NSLookup does not use the standard client resolver routines but uses similar routines of its own. If true, this means a valid name-IP record could be cached on the client and being used by IE to resolve the name even though NSLookup fails to resolve the name and there is no DNS record.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;To determine this, do the following:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;In the command prompt program, enter &lt;strong&gt;ipconfig /displaydns&lt;/strong&gt; to inspect the cache for the dns record.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Enter &lt;strong&gt;ipconfig /flushdns&lt;/strong&gt; to clean out records and retry (it should fail if there is no DNS record).&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;6.13.2008&lt;/p&gt;&lt;h4 id="Does_Intel_AMT_30_support_Windows_2000_Active_Directory"&gt;Does Intel AMT 3.0 support Windows 2000 Active Directory?&lt;/h4&gt;&lt;p&gt;For support of Windows 2000 Active Directory, AMT 3.2 is required. Intel AMT 3.2  was released to the OEMs during Q1 2008. Please contact your OEM to find out when the update will be publically available.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;6.13.2008&lt;/p&gt;&lt;h4 id="Switching_from_NAC_to_8021x_results_in_loss_of_connectivity"&gt;Switching from NAC to 802.1x results in loss of connectivity&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;In an EAC*-enabled network, where a NAC or NAP server is deployed and configured to request “posture” or SoH, Intel® AMT connectivity may be lost to clients that are not in H0 state if the server configuration is modified to work with 802.1x only.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If the NAC/NAP server configuration is changed to work with 802.1x only, then do one of the following:&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Restart LAN switch ports, or&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Restart the clients.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;6.25.2008&lt;/p&gt;&lt;h4 id="Using_IntelR_AMT_wirelessly_without_user_intervention"&gt;Using Intel(R) AMT wirelessly without user intervention&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Intel AMT wireless connectivity is not available when the operating system is running and the user is not logged in.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;To work around this issue, configure the Single Sign On (SSO) driver to maintain a wireless connection. Once the SSO properties are set according to the table below, Intel® AMT will be able to connect to the wireless profile using Microsoft* Windows  credentials before the user actually logs on.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;SSO Properties&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;&lt;strong&gt;Pre-logon.&lt;/strong&gt; This feature is identified with the “SSO” term. It allows you to connect to a  wireless profile using the Windows credentials entered by the user before the actual Windows log-in.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;&lt;strong&gt;Persistent.&lt;/strong&gt; This feature allows you to connect to a wireless profile that doesn’t require user credentials (but alternatively requires “system credentials”), in case the user is not logged on (either after reboot or after log-off). In order to use it, the IT admin has to configure such a profile that doesn’t rely on user credentials.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;&lt;strong&gt;Security.&lt;/strong&gt; Profiles for pre-logon and persistent connect are stored securely on the machine, cryptographically bound to the machine so that it cannot be transferred to another machine. The profiles are shared across all users on the machine, but certain user-based credentials such as PACs are stored on a &lt;strong&gt;per-user&lt;/strong&gt; basis.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;NOTES&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Microsoft Windows XP users: Using persistent connection adds a service to handle establishing connections when users are not logged on.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Microsoft Vista users: The persistent connection is enabled on a per profile basis if the configured EAP (Extensible Authentication Protocol) method supports authentication with machine credentials.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.16.2008&lt;/p&gt;&lt;h4 id="Cannot_provision_a_system_that_uses_an_underscore_in_the_host_name"&gt;Cannot provision a system that uses an underscore in the host name&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Cannot provision a system that uses an underscore in the host name.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Special characters cannot be used in host names. DNS host names may only contain dash "-", letters or numbers. Underscores and other special characters are not supported by the RFC's that define host name conventions. Some DNS servers, including Microsoft's, can support host names outside of the RFC specifications. See the links below for more information.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;MORE INFORMATION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;span&gt;Microsoft KB article 909264: &lt;/span&gt;&lt;a class="jive-link-external-small" href="http://support.microsoft.com/kb/909264"&gt;http://support.microsoft.com/kb/909264&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;RFC 952: &lt;/span&gt;&lt;a class="jive-link-external-small" href="http://www.ietf.org/rfc/rfc952.txt"&gt;http://www.ietf.org/rfc/rfc952.txt&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;RCF 1123: &lt;/span&gt;&lt;a class="jive-link-external-small" href="http://www.ietf.org/rfc/rfc1123.txt"&gt;http://www.ietf.org/rfc/rfc1123.txt&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.5.2008&lt;/p&gt;&lt;h4 id="Does_the_Intel_SCS_automatically_push_updates_to_the_CRL_Certificate_Revocation_List_to_clients"&gt;Does the Intel SCS automatically push updates to the CRL (Certificate Revocation List) to clients?&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The CRL does not automatically update on the clients. It needs to be pushed down from the SCS, by pushing it to individual AMT clients via the Operations screen, or to all clients via the Global Operations screen in the SCS Console.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;MORE INFORMATION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The Certificate Revocation List contains the revoked certificates maintained by a CA. It is used when Intel AMT clients are configured to use Mutual TLS (MTLS) authentication.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.5.08&lt;/p&gt;&lt;h4 id="Firewalls_may_not_let_IntelR_AMT_clients_communicate_with_management_consoles"&gt;Firewalls may not let Intel(R) AMT clients communicate with management consoles&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The wired LAN NICs are not recognized by the Intel AMT management consoles. They do show up in the DHCP listings in the Microsoft SMS* and Altiris* demos. Only the wireless NICs were discovered as Intel AMT devices. IPCONFIG on each notebook shows IP addresses assigned to both WLAN and LAN NICs.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;When the firewalls are turned off, the Intel AMT consoles can communicate with the LAN NICs.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Firewalls can prevent clients from registering an FQDN (fully qualified domain name), which prevents them from being discovered by the console. Verify that the firewall is not configured to block these kinds of requests.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.5.08&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Cisco_ACS_Certificate_Configuration_for_Intel_AMT"&gt;Cisco ACS Certificate Configuration for Intel AMT&lt;/h4&gt;&lt;p&gt;See &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-2044"&gt;this article&lt;/a&gt; to find specific configuration information.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;10.15.08&lt;/p&gt;&lt;h4 id="What_are_some_common_hardware_issues_that_are_tracked_by_Intel_AMT"&gt;What are some common hardware issues that are tracked by Intel® AMT?&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;ASF Sensor Events&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;p&gt;Temperature&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;Voltage&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;Fan&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;Chassis Intrusion&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;System FW Error (descriptor codes and descriptions are in the ASF spec 2.0) Examples:&lt;/p&gt;&lt;p style="padding-left: 30px;"&gt;Unrecoverable hard disk/ATAPI/IDE device failure&lt;/p&gt;&lt;p style="padding-left: 30px;"&gt;No video device detected&lt;/p&gt;&lt;p style="padding-left: 30px;"&gt;FW ROM corruption detected&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;BIOS Events&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;p&gt;System Boot Failure&lt;/p&gt;&lt;/li&gt;&lt;li&gt;&lt;p&gt;BIOS errors&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;OS Events&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;p&gt;OS Hangs&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;12.4.08&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="QA_on_customized_Intel_AMT_firmware"&gt;Q&amp;amp;A on customized Intel® AMT firmware&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;DESCRIPTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;&lt;strong&gt;Scenario:&lt;/strong&gt; a customer would like to have an OEM deliver systems with custom Intel® AMT firmware settings and client certificate.&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;strong&gt;QUESTION 1:&lt;/strong&gt; Will the customized firmware force the customer to use only customized firmware or BIOS updates for future releases?&lt;br/&gt;&lt;strong&gt;ANSWER 1:&lt;/strong&gt; The custom settings and client certificate will be preserved across firmware or BIOS updates if the OEM inserts the customized bits before the descriptor region manufacturing bit is locked.&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;strong&gt;QUESTION 2:&lt;/strong&gt; Can an OEM customize all the Intel® AMT management engine settings?&lt;br/&gt;&lt;strong&gt;ANSWER 2:&lt;/strong&gt; Yes. All the features seen on the web GUI can be customized by an OEM.&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;strong&gt;QUESTION 3:&lt;/strong&gt; Does Intel have a list of default settings for each OEM?&lt;br/&gt;&lt;strong&gt;ANSWER 3:&lt;/strong&gt; No. Customers should contact their OEM for the latest available information.&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;strong&gt;Caution:&lt;/strong&gt; The custom settings and client certificate will not be preserved across updates if the OEM programmed the firmware after setting the descriptor manufacturing bit. This will require users to reinstall the client certificates before the systems can be managed.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Customers should work with their OEM to develop a custom firmware image, then run a small pilot program to test it. Clear the CMOS and then try to reprovision the systems.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;2.13.09 QA1308&lt;/p&gt;&lt;h4 id="Wrong_IP_address_for_Intel_ME_on_Lenovo_M58p_using_Hypervisor"&gt;Wrong IP address for Intel ME on Lenovo M58p using Hypervisor&lt;/h4&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;For a system runing a Hypervisor on a platform with Intel(R) AMT 4.x or 5.x, the mismatch between the IP address assigned to the physical hardware and the guest operating system will prevent the manageability software from communicating with the Intel ME.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div&gt;To sync-up the IP addresses, do the following:&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li&gt;Modify the configuration settings so that Dom0 is configured to use the virtual MAC address.&lt;br/&gt;&lt;/li&gt;&lt;li&gt;Assign #1 Guest operating system with the physical MAC address of the Intel ME NIC.&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div&gt;This soluton will produce the following result:&lt;/div&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li&gt;The hardware initialization then the VMM and Dom0 will be brought-up.&lt;br/&gt;&lt;/li&gt;&lt;li&gt;Dom0 will provide the physical MAC address to the #1 Guest operating system, and virtual MAC addresses for each subsequent guest operating system.&lt;br/&gt;&lt;/li&gt;&lt;li&gt;The #1 Guest operating system will initiate a DHCP request with the physical MAC address.&lt;br/&gt;&lt;/li&gt;&lt;li&gt;The management console will now be able to communicate with the Intel ME using the IP address assigned to #1 Guest operating system.&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.11.2009  QA1366&lt;/p&gt;&lt;h1 id="Microsoft_Systems_Management_Server_SMS_Addon"&gt;Microsoft Systems Management Server (SMS) Add-on&lt;/h1&gt;&lt;h4 id="Fix_available_Microsoft_System_Management_Server_SMS_Addon_V30_has_local_echo_when_using_Serial_over_LAN_SoL"&gt;Fix available: Microsoft System Management Server (SMS) Add-on V3.0 has local echo when using Serial over LAN (SoL)&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When performing SOL/IDER with SMS Console V3.0, the SOL console screen is set for local echo to be on and it cannot be disabled.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue is fixed in version 3.1 of the SMS Add-on, which you can download at &lt;a class="jive-link-external-small" href="http://softwarecommunity.intel.com/articles/eng/1356.htm"&gt;http://softwarecommunity.intel.com/articles/eng/1356.htm&lt;/a&gt;.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;Updated 2.8.2008&lt;/p&gt;&lt;h4 id="Fix_available_Using_the_Intel_AMT_addon_for_Microsoft_SMS_2003_on_a_Dell_755_returns_a_UUID_error"&gt;Fix available: Using the Intel AMT add-on for Microsoft SMS 2003 on a Dell 755 returns a UUID error&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Using the Intel AMT add-on for Microsoft SMS 2003 on a Dell 755 returns this error:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Current system UUID is different from last discovered UUID. Please rediscover the system.&lt;/em&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;An Intel AMT add-on for Microsoft SMS 3.0 hot fix 3 is available online at &lt;a class="jive-link-external-small" href="http://www.intel.com/software/sms-add-on"&gt;http://www.intel.com/software/sms-add-on&lt;/a&gt;.&lt;br/&gt;This hot fix removes the continuity check between the SMBIOS and the Digest UUID, which was determined to be an unnecessary check.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;MORE INFORMATION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://downloadcenter.intel.com/detail_desc.aspx?strstate=live&amp;amp;productid=2609&amp;amp;dwnldid=11609&amp;amp;agr=n&amp;amp;lang=eng&amp;amp;prdmap=2609"&gt;Click here to download the hot fix\&lt;/a&gt;.&lt;br/&gt;Please review the &lt;a class="jive-link-external-small" href="http://downloadmirror.intel.com/11609/ENG/Release%20Notes%20Add-on%203.0.pdf"&gt;release notes\&lt;/a&gt; and the &lt;a class="jive-link-external-small" href="http://downloadmirror.intel.com/11609/ENG/SMS%20Add-on%20Quick%20Start%20Guide.pdf"&gt;Read Me\&lt;/a&gt; file to learn more.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;12.20.2007&lt;/p&gt;&lt;h4 id="Fix_available_The_Intel_AMT_Addon_for_Microsoft_SMS_is_unable_to_communicate_with_the_SCS_over_a_standard_HTTP_connection"&gt;Fix available: The Intel AMT Add-on for Microsoft* SMS is unable to communicate with the SCS over a standard HTTP connection.&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The Intel AMT Add-on for SMS will communicate with the SCS over an HTTPS/SSL connection, however it will not communicate over an insecure HTTP/non-SSL connection, even if TCP port 80 is defined in the Intel AMT Add-on configuration.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Upgrading to version 3.1 of the Intel AMT Add-on for SMS resolves this issue. The update can be obtained from: &lt;a class="jive-link-external-small" href="http://softwarecommunity.intel.com/articles/eng/1356.htm"&gt;http://softwarecommunity.intel.com/articles/eng/1356.htm&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.8.2008&lt;/p&gt;&lt;h4 id="Do_management_workstations_running_the_SMS_console_and_SMS_Addon_require_patches_as_outlined_in_the_documentation_for_the_IntelR_AMT_Addon_for_Microsoft_SMS"&gt;Do management workstations running the SMS console and SMS Add-on require patches as outlined in the documentation for the Intel(R) AMT Add-on for Microsoft SMS*?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SMS Add-on documentation states that two hot fixes and registry patches are required. Are these patches/hot fixes required on the workstations that are running the Microsoft SMS console and Intel AMT add-on only?&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Are they required only if the end user from that workstation is planning to use the web interface?&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Are they required for the SMS add-on to function properly?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;These patches are required on a management workstation if you wish to access the web interface on vPro clients.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;5.8.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="OEM"&gt;OEM&lt;/h1&gt;&lt;h2 id="BIOS_760071"&gt;&lt;strong&gt;BIOS&lt;/strong&gt;&lt;/h2&gt;&lt;h4 id="Lenovo_M55p_returns_UUID00000_during_activation"&gt;Lenovo* M55p returns UUID=00000 during activation&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Lenovo M55p systems return a hello packet of UUID 00000 during activation. This problem occurs on machines that shipped with factory-default BIOS of 36 or less.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A firmware update to version AMT2.1.0.1032 is available from Lenovo to resolve this problem. Contact your Lenovo representative if you need this update.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;A BIOS update is not required, but is recommended. Visit the Lenovo web site and navigate to the Support &amp;amp; downloads section of the site to find BIOS 37a.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;10.19.2007&lt;/p&gt;&lt;h4 id="Dell_755_returns_a_duplicate_UUID_during_activation"&gt;Dell* 755 returns a duplicate UUID during activation&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Dell 755 returns a duplicate UUID 00000 during activation.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A BIOS update (version A04) resolves this issue and is available on Dell's web site.&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://support.dell.com/support/downloads/download.aspx?releaseid=R171367&amp;amp;fileid=233339"&gt;Click here to download the A04 BIOS update.\&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Note: If you are using the Intel AMT add-on for Microsoft SMS 2003, then you also need to download Hot fix 3. See &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-1247"&gt;Using the Intel AMT add-on for Microsoft SMS 2003 on a Dell 755 returns a UUID error\&lt;/a&gt; for instructions.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.24.2008&lt;/p&gt;&lt;h4 id="Ctrl__P_prompt_missing_when_CMOS_battery_unplugged"&gt;Ctrl + P prompt missing when CMOS battery unplugged&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When the CMOS battery is unplugged from the HP 7800p, the Ctrl+P command for accessing the Intel Management Engine is missing.&lt;/p&gt;&lt;p&gt;When SCS is opened and the refresh button is selected, the Intel AMT device does not appear.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Use the following steps to the resolve this issue:&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Press F-10, when prompted during the boot, to access the BIOS on the system.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;In the BIOS choose the advanced menu -&amp;amp;gt; Power-On Options and select the “MEBx Setup Prompt”&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Use the right arrow key to cycle it to “Displayed.”&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Press F-10 to accept the change.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Go to the file menu and select Save Changes and Exit.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;The Ctrl-P prompt will reappear.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.7.2008&lt;/p&gt;&lt;h4 id="When_Intel_AMT_is_disabled_there_is_a_HECI_driver_problem_in_the_HP_dc7800"&gt;When Intel AMT is disabled, there is a HECI driver problem in the HP* dc7800&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;In vPro-capable HP dc7800 systems, when Intel AMT is turned on, everything works fine. When the Intel AMT driver is turned off in the Intel Management engine, the Intel HECI driver in the operating system causes an error to occur in the device manager: "device cannot start".&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Follow these steps to correct this problem:&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Boot the client and press &lt;strong&gt;Ctrl + P&lt;/strong&gt; to access the AMT/ME configuration settings.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Go to the Intel ME Configuration and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Type &lt;strong&gt;Y&lt;/strong&gt; to continue.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select &lt;strong&gt;Intel ME Features Control&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select &lt;strong&gt;Manageability Feature Selection&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select &lt;strong&gt;None&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Press &lt;strong&gt;ESC&lt;/strong&gt; to go back to the main screen.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;The system will reboot.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Go into device manager and verify that there are no failed devices.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.14.2008&lt;/p&gt;&lt;h4 id="What_does_the_Intel_AMT_status_application_dialog_box_signify"&gt;What does the Intel AMT status application dialog box signify?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;On brand new vPro systems, the Intel AMT Status Application dialog box displays the Intel AMT Status as "Enabled" even though Intel AMT has not been configured. Are OEMs shipping systems with Intel AMT enabled (provisioned)?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The Intel AMT status application is designed to show if the Intel AMT is or is not enabled in the Intel Management Engine. It does not reflect if a system has been provisioned/configured. Even when Intel AMT is disabled in the Intel Management Engine, the Intel Management Engine can still be accessed. OEMs do not ship provisioned systems unless that service is requested and purchased by the customer.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.14.2008&lt;/p&gt;&lt;h4 id="Are_there_DLLs_in_the_operating_system_that_access_vPro"&gt;Are there DLLs in the operating system that access vPro?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Are there DLLs, in the operating system, that access vPro?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Individual OEMs manage the Microsoft Windows drivers that use Intel vPro technology. To access current drivers for clients, visit the OEM’s website.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.14.2008&lt;/p&gt;&lt;h4 id="Unattended_install_of_IntelR_AMT_client_softwaredrivers_not_working_properly_on_Microsoft_Windows"&gt;Unattended install of Intel(R) AMT client software/drivers not working properly on Microsoft Windows*&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Command line switches are not working properly to enable a silent install with the Intel AMT drivers.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The issue is that the wrong hyphen/dash character is being used. If the code is copied from an MS Word* document, the regular hyphen is replaced with another hyphen-like character which causes the command line options to work incorrectly.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Typing the command, rather than copy and paste, solves this problem.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;h4 id="SoLIDER_does_not_work_with_the_Lenovo_X61_Tablet"&gt;SoL/IDER does not work with the Lenovo* X61 Tablet&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SoL/IDER sessions do not work on the X61 tablet.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue is resolved using the 1.07 BIOS release.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Visit the Lenovo web site and navigate to the Support &amp;amp; Downloads section of the site to find BIOS 1.07.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;h4 id="SoLIDER_cant_be_disabled_on_Lenovo_M55p"&gt;SoL/IDER can’t be disabled on Lenovo* M55p&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Unchecking SoL and IDER, under the network tab, isn’t disabling the feature on the Lenovo M55p.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Update the BIOS to version 37a or newer versions. Visit the Lenovo web site and navigate to the Support &amp;amp; Downloads section of the site to find BIOS 37a or later.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.4.2008&lt;/p&gt;&lt;h4 id="BIOS_password_screen_unavailable_on_HP_systems_during_SoL_session"&gt;BIOS password screen unavailable on HP* systems during SoL session&lt;/h4&gt;&lt;p&gt;This problem occurs when the Terminal Emulation Mode is not set correctly in the BIOS.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Here is the screen when Terminal Emulation Mode is set to VT100 through BIOS:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1375/Altiris_uisng_SOL_with_HP_VT100.JPG"&gt;&lt;img height="506" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1375/620-506/Altiris_uisng_SOL_with_HP_VT100.JPG" width="620"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;How to switch Terminal Emulation Mode:&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Open the HP ProtectTools Security Manager, click &lt;strong&gt;BIOS Configuration&lt;/strong&gt;, and then select &lt;strong&gt;System Configuration&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;In the &lt;strong&gt;AMT Options&lt;/strong&gt; section, change &lt;strong&gt;Terminal Emulation Mode&lt;/strong&gt; to &lt;strong&gt;ANSI&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1377/HP_BIOS_changed_to_ANSI_mode.JPG"&gt;&lt;img height="524" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1377/620-524/HP_BIOS_changed_to_ANSI_mode.JPG" width="620"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The BIOS Password screen is now available during SOL sessions.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1376/Altiris_uisng_SOL_with_HP_ANSI.JPG"&gt;&lt;img height="506" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1376/620-506/Altiris_uisng_SOL_with_HP_ANSI.JPG" width="620"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;4.25.2008&lt;/p&gt;&lt;h4 id="Dell_D630c_laptops_reboot_when_sent_a_shutdown_command_via_Intel_AMT"&gt;Dell* D630c laptops reboot when sent a shutdown command via Intel® AMT&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Sending the "power down" command to the Dell* D630c notebook immediately shuts it down, but then it automatically re-boots.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue is resolved in BIOS version A02 for the Dell* D630c. You can download the BIOS update package from Dell at the following URL**:&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://support.dell.com/support/downloads/download.aspx?c=us&amp;amp;cs=555&amp;amp;l=en&amp;amp;s=biz&amp;amp;releaseid=R177765&amp;amp;SystemID=LATITUDE_D630C&amp;amp;servicetag=&amp;amp;os=WLH&amp;amp;osl=en&amp;amp;deviceid=15745&amp;amp;devlib=0&amp;amp;typecnt=0&amp;amp;vercnt=2&amp;amp;catid=-1&amp;amp;impid=-1&amp;amp;formatcnt=1&amp;amp;libid=1&amp;amp;fileid=241799"&gt;Click here.&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;br/&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;**&lt;/span&gt;&lt;span style="color: #000000; font-family: Times New Roman;"&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;This Wiki contains links to other Internet sites. Such links are not endorsements of any products or services in such&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt;"&gt;&lt;span style="color: #000000;"&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;sites, and no information in such site has been endorsed or approved by Intel, Inc.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.25.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="The_look_of_the_BIOS_Setup_screens_using_SoL_depends_on_OEM_support_for_terminal_emulation_modes"&gt;The look of the BIOS Setup screens using SoL depends on OEM support for terminal emulation modes&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;Intel® AMT supports several terminal emulation modes. These are used to display the BIOS Setup GUI when using SoL. The look and feel may vary between manufacturers. Intel® AMT supports VT52, VT100, VT100+, and ANSI terminal emulation modes.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;&lt;span style="font-size: 10pt;"&gt;&lt;span style="color: #000000;"&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;Check your OEM BIOS documentation for information about the supported terminal emulation modes and how to select the mode. Usually, the terminal emulation mode option will be in the Intel® AMT section of the BIOS Setup utility. Use ANSI mode for a more graphical looking display.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;3.3.2009 QA1332&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Platform_Averill"&gt;Platform: Averill&lt;/h1&gt;&lt;h4 id="Are_the_Weybridge_SoL_and_HECI_drivers_backwardcompatible_with_Averill"&gt;Are the Weybridge SoL and HECI drivers backward-compatible with Averill?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Are the Weybridge SoL and/or HECI drivers backward-compatible with Averill? Can they be used and supported on an Averill platform?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Backward compatibility depends on the OEM and if they choose to support the drivers and platforms. For instance, HP does support the same drivers for 7700's, 7800's and 6910p, but other OEMs may not support the same drivers.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Profiles"&gt;Profiles&lt;/h1&gt;&lt;h2 id="SCS"&gt;&lt;strong&gt;SCS&lt;/strong&gt;&lt;/h2&gt;&lt;h4 id="Intel_SCS_returns_an_error_during_a_partial_unprovision"&gt;Intel SCS returns an error during a partial unprovision&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Partial unprovisioning of a system fails. The SCS log reports the following messages: "SOAP Failure (21): cannot partially unprovision AMT" or "SOAP Failure(21): cannot GetLowAccuracyTimeSync"&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The partial un-provision command requires a FQDN to work. Accurate client DNS records are required to provide an FQDN for this functionality.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;h4 id="Validation_of_SCS_service_users_takes_over_30_minutes_when_installed_in_a_large_Active_Directory_environment"&gt;Validation of SCS service users takes over 30 minutes when installed in a large Active Directory environment&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Validation of SCS service users takes over 30 minutes when installed in a large Active Directory environment&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue is scheduled to be resolved in Intel(R) AMT SCS 5.0, to be released by the end of Q2.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h1 id="Setup_and_Configuration_Service"&gt;Setup and Configuration Service&lt;/h1&gt;&lt;h4 id="GoDaddy_requires_HighAssurance_SSL_certificates"&gt;GoDaddy* requires High-Assurance SSL certificates&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The standard domain-only validation SSL certificates from the GoDaddy Certificate Authority are not suitable for Intel AMT remote configuration. These types of certificates do not contain the OU information required by the firmware to accept them.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If GoDaddy is used as the CA, then request a High-Assurance SSL certificate, which should include the OU information required by the Intel AMT client.&lt;/p&gt;&lt;p&gt;For more information, see the &lt;a class="jive-link-external-small" href="http://softwarecommunity.intel.com/UserFiles/en-us/Intel_AMT_SCS_Installation_and_User_Manual.pdf"&gt;Intel AMT SCS Installation and User Manual\&lt;/a&gt;, Chapter 3, section “Preparing Intel AMT for Future Configuration.”&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.25.2008&lt;/p&gt;&lt;h4 id="Using_static_IP_addresses_and_Basic_formerly_known_as_SMB_mode"&gt;Using static IP addresses and Basic (formerly known as SMB) mode&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Intel AMT functionality works in DHCP IP with Enterprise mode and SMS. However, SMS does not find asset information from the vPro machine when using Static IP with Basic mode.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Static IP addresses are not recommended. If they must be used, then the Intel Management Engine and the operating system will each need their own static IP address in order for AMT to function properly.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.25.2008&lt;/p&gt;&lt;h4 id="Error_displays_when_provisioning_HP_6910p"&gt;Error displays when provisioning HP* 6910p&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Setup and Configuration Service (SCS) reports an error when provisioning Hewlett-Packard (HP) 6910p computers when using Wake on LAN (WoL) power policies 4 and 5.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This error occurs for all HP platforms shipped in 2007 and there is no workaround. HP does not support these power policies and the SCS is accurately reporting that they are unsupported.&lt;/p&gt;&lt;p&gt;Escalate this known issue to your HP sales representative.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;1.25.2008&lt;/p&gt;&lt;h4 id="Will_PKICH_consistently_support_wildcard_certificates_across_IntelR_AMT_versions"&gt;Will PKI-CH consistently support wildcard certificates across Intel(R) AMT versions?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Will the PKI-CH implementation currently available in Intel AMT 2.2, Intel AMT 2.6, and Intel AMT 3.0 consistently support wildcard RCFG certificates?&lt;/p&gt;&lt;p&gt;Intel AMT 2.6 supports wildcards; but Intel AMT 2.2 and 3.0 do not. Will Intel AMT 2.2 and 3.0 will support wildcard certificates?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;There are no plans to enable support for wildcard certificates in Intel AMT 2.2 or any future updates for that generation of hardware. There are plans to support wildcard certificates in the future release of Intel AMT 3.2&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.4.2008&lt;/p&gt;&lt;h4 id="SCS_service_crashes_due_to_excessive_logs"&gt;SCS service crashes due to excessive logs&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SCS service crashes repeatedly due to excessive logs. In the SCS Win Log, the OLE database error for timeout is displayed.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Reduce the database logs to a reasonable size, based on available processes.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;h4 id="Network_Load_Balancing_of_SCS_Servers"&gt;Network Load Balancing of SCS Servers&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Are there any known issues or limitations in pointing provisionserver.company.com to a Network Load Balancing address that balances between two or more SCS servers (all are in the same domain)?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SCS support team confirmed that this is a supported configuration, provided all the SCS servers point back to a single SCS database.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;2.27.2008&lt;/p&gt;&lt;h4 id="Is_SNMP_Trap_Service_required_for_SCS"&gt;Is SNMP Trap Service required for SCS?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Is the Microsoft Windows* SNMP trap service required in the latest SCS version?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SNMP trap service is not required for installing or using SCS, but it is required for the Intel® AMT Add-on for SMS* V3.0 to receive PET alerts from Intel AMT clients per the SMS manual.&lt;/p&gt;&lt;p&gt;It is used as a receiver for platform trap events. Clients can be configured to send platform traps to an SNMP service. Since the Intel AMT Add-on is capable of configuring clients, an SNMP trap service is required during installation for a complete solution.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.4.2008&lt;/p&gt;&lt;h4 id="IntelR_AMT_Active_Directory_error_message"&gt;Intel(R) AMT Active Directory error message&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;After setting the properties for the Intel AMT system, the status goes to InProvisioning, but nothing changes. The logs contain the following message: Cannot create AD AMT Object: Failed on CreateDSObject with ht-73207ty, - Process Delayed.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This error message normally occurs for the following reasons:&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;The AD schema extension has not been applied&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;The Schema extension has been applied, but the SCS service user does not have necessary permissions to AD OU to create and manage Intel AMT ME objects.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;If the extension for the AD schema is not needed, then uncheck the Active directory Integration checkbox in the SCS General Settings screen to prevent SCS from trying to create AD objects during provisioning.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.4.2008&lt;/p&gt;&lt;h4 id="Organizational_Unit_Field_in_Configuration_Parameters_must_be_populated_to_complete_provisioning"&gt;Organizational Unit Field in Configuration Parameters must be populated to complete provisioning&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;SCS cannot complete provisioning of a system if the Configuration Parameters do not have a value specified in the OU column, even if the SCS is not using the Integrated with Active Directory option. Users must either manually add a value (during the manual process) or define a value when using remote tools like the RCT.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This is a known issue with SCS and it is slated to be corrected in SCS 5.0.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.4.2008&lt;/p&gt;&lt;h4 id="Unable_to_access_web_interface_using_Kerberos_authentication"&gt;Unable to access web interface using Kerberos authentication&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The web interface cannot be accessed using Kerberos authentication. When the Firefox web browser was used, Admin authentication could be accessed, but the https digest could not be accessed. Internet Explorer* cannot access either Admin authentication or Https digest.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If the AD schema is not extended, the Kerberos user authentication will not work. Using digest users resolves this issue.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.21.2008&lt;/p&gt;&lt;h4 id="Is_Static_IP_addressing_possible_in_Enterprise_Mode"&gt;Is Static IP addressing possible in Enterprise Mode?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;What is the technical limitation of having static IP addresses in an Enterprise Mode environment and what would be workarounds that would allow a customer to use both? Since DHCP dynamically updates DNS, if you manually entered DNS suffix in Intel(R) Management Engine and maintained DNS manually then would that allow customers to use static IP addresses with enterprise mode?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;While this is not recommended, the DNS entries can be maintained as described in the question. Multiple computer entries, in the management console, will be needed for managing clients that use Static IP.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.21.2008&lt;/p&gt;&lt;h4 id="Is_it_possible_to_have_an_operating_system_with_static_IP_address_and_Intel_Management_Engine_in_DHCP_mode"&gt;Is it possible to have an operating system with static IP address and Intel® Management Engine in DHCP mode?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Is it possible to have an operating system setup with static IP address and Intel Management Engine setup for DHCP mode? Can the IP address of the operating system and Intel Management Engine be on different subnets? Or do they need to be on same subnet?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This scenario is not supported and has not been tested.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.21.2008&lt;/p&gt;&lt;h4 id="Cannot_log_into_SCS_Console_with_Enterprise_Admin_account"&gt;Cannot log into SCS Console with Enterprise Admin account&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SCS console can only be logged into using the initial setup account that is provided during SCS installation. Any attempts to log in with a user account that has enterprise admin rights and has been added to SCS Users and Groups fail. The error message received is: Login Failed and the reason is: The remote server returned an error: (502) Bad Gateway.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The root cause is that the customer has an Internet Explorer* configuration that uses a proxy. On the https connection, both the SCS console login and the SCS service uses the same proxy settings and that causes it to fail with error 502 bad gateway. Un-checking the use of the proxy in Internet Explorer solves the problem.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;3.21.2008&lt;/p&gt;&lt;h4 id="Intel_MEBX_Web_UI_and_remote_admin_passwords_are_not_automatically_synchronized"&gt;Intel® MEBX, Web UI, and remote admin passwords are not automatically synchronized&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;Changing the Intel® MEBX password from the local console will not change the Web UI or remote admin passwords.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Before the Intel® AMT system is provisioned, changing the Intel MEBX password from the local console will also change the remote admin password.  After the system is provisioned, changing the local Intel MEBX password will &lt;em&gt;not&lt;/em&gt; change the remote admin password.  During provisioning, the Intel MEBX password and the remote admin password can be set.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;04.28.2009&lt;/p&gt;&lt;h4 id="Using_international_keyboards_to_create_MEBx_passwords_via_Setup_and_Configuration_Service_SCS"&gt;Using international keyboards to create MEBx passwords via Setup and Configuration Service (SCS)&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When creating a MEBx password via SCS and deploying to client machines located in different countries, IT administrators are advised that international keyboards may have different layouts for Latin characters. This may result in password failures as a result of entering the same password on two different keyboards supporting different languages.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;As an example, a multi-national company headquartered in France may deploy a client to one employee in France and Japan. Because the keyboard layouts are different, the passwords may be inadvertently different and may fail when entered on a different keyboard.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Below is a comparison of different language keyboards.&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1348/CommonKeys.gif"&gt;&lt;img height="395" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1348/509-395/CommonKeys.gif" width="509"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Japanese keyboard&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1349/keyboard_japanese.gif"&gt;&lt;img height="183" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1349/537-183/keyboard_japanese.gif" width="537"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;US English keyboard&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1386/Keyboard-US.GIF"&gt;&lt;img height="171" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1386/533-171/Keyboard-US.GIF" width="533"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When creating your password, use character keys that are common between all keyboards and follow the guidelines below. These guidelines assume that the password is user-defined. In high security instances, the password will be auto-generated and you will need to compare the keyboard layout diagrams to help determine your MEBx password.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;The following is a list of keyboard keys that are common keys for all keyboard types: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, B, C, D, E, F, G, H, I, J, K, L, N, O, P, R, S, T, U, V, X&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;EXCEPTION:&lt;/strong&gt; These keys are not common between Japanese and US keyboards: 2, 8, and 9. Be sure to use the illustrations above to verify common keys when creating passwords.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Note: Passwords can be created using characters generated by the Key and Shift Key&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;MEBx passwords require special characters to ensure security. Use SHIFT+N, where N equals 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9, to include special characters in your password.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;For example, if your strong password is JOK&amp;amp;F49!, you would relay this password to international users as:  &lt;a href="http://communities.intel.com/servlet/JiveServlet/showImage/102-1247-106-1355/password.gif"&gt;&lt;img height="32" src="http://communities.intel.com/servlet/JiveServlet/downloadImage/102-1247-106-1355/195-32/password.gif" width="195"/&gt;&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Passwords using the A,M,Q,W,Y and Z keys can cause problems and are not recommended.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;5.7.2008&lt;/p&gt;&lt;h4 id="What_is_the_Authorized_column_in_SCS"&gt;What is the Authorized column in SCS?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The Intel(R) AMT Systems screen of the SCS web console has a column titled Authorized. All the systems that are provisioned show up as False. What does this column mean?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The Authorized column signifies systems that can be provisioned that have not been authorized to complete the process.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;5.8.2008&lt;/p&gt;&lt;h4 id="SOAP_error_0xCFFF06AC_when_attempting_remote_configuration"&gt;SOAP error (0xCFFF06AC) when attempting remote configuration&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;When attempting to use the latest SCS with RCT 3.3 with a Remote Config Cert from GoDaddy, this error displays in SCS: Cannot handle provisioning exception: (0xCFFF06AC) SOAP Failure (23): getFullCoreVersion: SSL error - SSL authentication failed in tcp_connect(): check password, key file, and CA file.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The remote config certificate needs to be in the personal store of the SCS service account.&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Log into your server with the SCS service account.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Launch MMC.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select &lt;strong&gt;File &amp;gt; Add/Remote Snap-in&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select &lt;strong&gt;Certificates&lt;/strong&gt; from the snap in menu and click &lt;strong&gt;Add&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;When prompted, select &lt;strong&gt;My user account&lt;/strong&gt; and click &lt;strong&gt;Finish&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Click the &lt;strong&gt;Close&lt;/strong&gt; button to close the snap-in selection window.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Click &lt;strong&gt;OK&lt;/strong&gt; to close the snap-in Add/Remove menu.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Open &lt;strong&gt;Certificates&lt;/strong&gt;, then open &lt;strong&gt;Personal&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Right-click the Personal folder, select &lt;strong&gt;All Tasks&lt;/strong&gt; and then &lt;strong&gt;Import&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Use the wizard to import your remote configuration certificate into personal store of your SCS service account.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;6.13.2008&lt;/p&gt;&lt;h4 id="Local_Manageability_Service_LMS_does_not_allow_host_VPN_traffic_when_environment_detection_is_not_defined"&gt;Local Manageability Service (LMS) does not allow host VPN traffic when environment detection is not defined&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;If environment detection is not configured, Intel AMT VPN connection cannot be enabled even though there is no direct relationship between these two.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Define the DNS suffix in the environment detection list with one which matches with the host's list of DNS suffixes.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;To define the suffix:&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Open the Intel SCS Console.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Expand the &lt;strong&gt;Configuration Service Settings&lt;/strong&gt; branch.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select &lt;strong&gt;Profiles&lt;/strong&gt;. The Profiles screen displays.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Select the profile to be modified.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Click &lt;strong&gt;Edit&lt;/strong&gt;. The Profile Configuration dialog box displays.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Display the &lt;strong&gt;Network&lt;/strong&gt; tab.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Click &lt;strong&gt;Environment Detection&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;In the Environment Detection dialog, click &lt;strong&gt;Add&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Enter up to five domain suffixes that define permitted domains within the enterprise network. The Intel AMT device uses this list to determine whether the platform is operating inside or outside the enterprise network. Management consoles can define the behavior of the device when it is outside the enterprise, including setting a policy that will block network traffic.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9. Click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.18.2008&lt;/p&gt;&lt;h4 id="Unable_to_remove_wireless_profiles_in_Intel_SCS"&gt;Unable to remove wireless profiles in Intel SCS&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Error code 998 displays when trying to remove a wireless profile in the SCS, indicating that the profile is in use.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This error is generated if the wireless profile you are using is assigned to a system profile within the SCS. In order to delete the wireless profile, first remove it from any system profiles.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.18.2008&lt;/p&gt;&lt;h4 id="Time_synchronization_errors_using_IntelR_SCS_3x_and_Active_Directory"&gt;Time synchronization errors using Intel(R) SCS 3.x and Active Directory&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The client machine logs errors related to setting the time when time synchronization is enabled in Intel SCS 3.x and the OS is also using Active Directory to synchronize system time.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;|&lt;strong&gt;RESOLUTION&lt;/strong&gt;|Disable time synchronization in SCS 3.x.|&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.28.2008&lt;/p&gt;&lt;h4 id="SCS_Installation_Account_Security_Requirements"&gt;SCS Installation Account Security Requirements&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;What are the minimum security requirements required for the account which is installing SCS?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The account needs to be a member of the local administrators group and an administrator on the SQL server.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;7.28.2008&lt;/p&gt;&lt;h4 id="SCS_50_Does_Not_Support_64bit_Operating_Systems"&gt;SCS 5.0 Does Not Support 64-bit Operating Systems&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;SCS 5.0 does not support 64-bit operating systems. Customers using 64-bit operating systems need to use SCS 5.1 or later.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;At this time there is no workaround for SCS 5.0 to support 64-bit operating systems. This issue is not documented in the SCS 5.0 documentation.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;SCS 5.1 supports 64-bit operating systems.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;9.25.2008&lt;/p&gt;&lt;h4 id="The_SCS_Console_Operator_role_does_not_appear_to_give_users_the_right_to_access_the_security_keys"&gt;The SCS Console Operator role does not appear to give users the right to access the security keys&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SCS Console Operator role does not appear to give users the right to access the security keys, which conflicts with the documentation and is a pre-requisite for an operator performing a pre-provisioning function.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This issue was fixed in SCS 5.0.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;11.25.2008&lt;/p&gt;&lt;h4 id="Consistent_RCFG_failure_with_SCS"&gt;Consistent RCFG failure with SCS&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Remote configuration fails consistently when attempting to provision clients with SCS. The error message in the SCS log is 'Cannot handle provisioning exception: (0xCFFF06AC) SOAP Failure (23): getFullCoreVersion: SSL_ERROR_SSLerror:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error - SSL connect failed in tcp_connect()'&lt;br/&gt;&lt;br/&gt;The provisioning server has the correct (non-wildcard) RCFG certificate and certificate chains from the signing Certificate Authority. The client domain name from the DHCP server (option 15) matches the domain in the RCFG certificate and the SCS domain. The server also correctly provisions clients using the TLS-PSK method.&lt;br/&gt;&lt;br/&gt;The Clients can also be correctly provisioned using RCFG when connected to a separate test network.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p class="MsoNormal" style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="margin: 6pt 0in; line-height: 11pt; mso-line-height-rule: exactly;"&gt;Intel® AMT supports a maximum encryption key length of 2048-bits.&lt;/div&gt;&lt;span style="font-size: 10pt; color: #000000; font-family: Verdana;"&gt;&lt;/span&gt;&lt;div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;12.4.2008&lt;/p&gt;&lt;h4 id="How_often_are_log_files_purged_in_Intel_SCS"&gt;How often are log files purged in Intel SCS?&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;How often does the SCS purge log files and can the retention date be configured?&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;There are maintenance procedures that SCS executes once every five minutes: cspi_cleanRequestStatus and cspi_cleanLog. These procedures did not execute automatically in SCS 3.3 and earlier.&lt;br/&gt;&lt;br/&gt;This was fixed in SCS 3.3. Both procedures will execute automatically. The default value of cspi_cleanRequestStatus is five days.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;12.4.2008&lt;/p&gt;&lt;h4 id="Is_the_Intel_SCS_supported_on_EMT64_bit_versions_of_Microsoft_Windows_Server"&gt;Is the Intel® SCS supported on EMT64 bit versions of Microsoft Windows* Server?&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div id="solution"&gt;The 3.x versions of the SCS are not supported on EMT64 versions of Windows Server. SCS 5.0 is supported in 32-bit mode on EMT64 enabled versions of Windows* Server.&lt;br/&gt;&lt;br/&gt;Download SCS 5.0 at &lt;a class="jive-link-external-small" href="http://software.intel.com/en-us/articles/download-the-latest-version-of-intel-amt-setup-and-configuration-service-scs"&gt;http://software.intel.com/en-us/articles/download-the-latest-version-of-intel-amt-setup-and-configuration-service-scs&lt;/a&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;12.4.2008&lt;/p&gt;&lt;h4 id="Cant_import_setupbin_made_with_USBFILE2EXE_into_the_SCS"&gt;Can't import setup.bin made with USBFILE2.EXE into the SCS&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The USBFile version 2 utility was used to create PID/PPS pairs, but the SCS console cannot import the setup.bin file. It displays an error message indicating the supplied setup.bin has an incorrect file format.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;div id="solution"&gt;USBFILE2's file format is not supported by the SCS at this time. Use the -v 1 switch with USBFILE2 to force it to create a v1 file, or use the original USBFILE utility.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;12.4.2008&lt;/p&gt;&lt;h4 id="The_SCS_Console_Operator_role_does_not_appear_to_give_users_the_right_to_access_the_security_keys_218611"&gt;The SCS Console Operator role does not appear to give users the right to access the security keys&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The SCS Console Operator role does not appear to give users the right to access the security keys, which conflicts with the documentation and is a pre-requisite for an operator performing a pre-provisioning function.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This is a known issue and will be fixed in SCS 5.0.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.25.2008&lt;/p&gt;&lt;h4 id="Minimum_security_requirements_for_installing_IntelR_SCS"&gt;Minimum security requirements for installing Intel(R) SCS&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;The user installing Intel® SCS must be a member of the local&lt;br/&gt;administrators group and a SQL administrator. The user&lt;br/&gt;installing the software does not need to be a domain&lt;br/&gt;administrator.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;4.2.2009 QA1326&lt;/p&gt;&lt;h4 id="IntelR_SCS_is_only_supported_on_English_versions_of_Windows_Server_2008"&gt;Intel(R) SCS is only supported on English versions of Windows* Server 2008&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;SOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Check future versions of Intel SCS to determine if it is supported on non-English versions of Microsoft* Windows* Server 2008.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/p&gt;&lt;p&gt;9.18.2009 QA1381&lt;/p&gt;&lt;h1 id="USB_Provisioning"&gt;USB Provisioning&lt;/h1&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="USB_provisioning_only_effective_on_factory_new_systems"&gt;USB provisioning only effective on "factory new" systems&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;USB provisioning failed after multiple attempts.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;This is by design. USB provisioning only works on a "factory new" system, meaning that it has never been provisioned. Once Intel(R) AMT is provisioned, the one-touch USB method will not work again until the CMOS battery is pulled and reset.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;11.9.2007&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="USB_Key_Configuration_Guidelines"&gt;USB Key Configuration Guidelines&lt;/h4&gt;&lt;p&gt;Use these criteria when preparing a key for USB provisioning:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Keys should only be formatted with Intel SCS. Keys should be formatted as a FAT16 device with a null volume label.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Setup.bin must be the first file on the key. If the file is overwritten, or erased and then re-added, it may no longer be the first file on the key. Always reformat the key before a new setup.bin file is copied to it.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Keys should be 2GB or less. FAT16 cannot address more than 2GB on these devices.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Purchased keys should not have any preinstalled software on them.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Keys should only be used for USB key provisioning and not for any other purpose.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;Keys should never have been created as a bootable device.&lt;/p&gt;&lt;/li&gt;&lt;li type="ul"&gt;&lt;p&gt;BIOS settings can impact USB provisioning. If you experience problems, load the manufacturer's default BIOS settings before doing USB provisioning.&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;12.20.2007&lt;/p&gt;&lt;h4 id="USB_Compatibility_Matrix_for_Intel_Centrino_with_vPro_Technology_Intel_AMT_25"&gt;USB Compatibility Matrix for Intel® Centrino® with vPro Technology &lt;em&gt;(Intel&lt;/em&gt;® &lt;em&gt;AMT 2.5)&lt;/em&gt;&lt;/h4&gt;&lt;p&gt;&lt;em&gt;The keys marked YES are acceptable for USB provisioning. The keys marked NO are not recommended for USB provisioning. New keys were used in these tests.&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;p&gt;System&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Model&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;BIOS&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;SanDisk 1GB&lt;/p&gt;&lt;p&gt;Cruzer Micro&lt;/p&gt;&lt;p&gt;SDCZ61024A10&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Kingston 1GB&lt;/p&gt;&lt;p&gt;DT1001GBKR&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Sony 1GB&lt;/p&gt;&lt;p&gt;Micro Vault&lt;br/&gt;Classic&lt;/p&gt;&lt;p&gt;USM1GJ&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;PNY 2GB Optima&lt;/p&gt;&lt;p&gt;Pro Attached&lt;/p&gt;&lt;p&gt;Enhanced for&lt;/p&gt;&lt;p&gt;Windows ReadyBoost&lt;/p&gt;&lt;p&gt;PFD02GHSPFS&lt;/p&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Acer&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;TravelMate 6592&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.53&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Dell&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Latitude D630c&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A09&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;FSC&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;LifeBook E8410&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.16&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;HP&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;2510p&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;F.0D&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;HP&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;6910p&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;F.16&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Lenovo&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;ThinkPad T61&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;7LETB9WW(2.24)&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Lenovo&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;ThinkPad X61 Tablet&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;7SET31WW(1.19)&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Lenovo&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;ThinkPad X300&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;7TUJ05US (1.08)&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Samsung&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;NP-P55&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;07AY&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Toshiba&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Protege M700&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.40&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Toshiba&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Tecra M9&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;1.90&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Not supported&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;*Fujitsu-Siemens Corporation (FSC) and Toshiba do not support USB provisioning on their Intel® Centrino® Pro processor technology platform.&lt;/p&gt;&lt;p&gt;04.23.09&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="USB_Compatibility_Matrix_for_Intel_vPro_Technology_Intel_AMT_3x"&gt;USB Compatibility Matrix for Intel® vPro™ Technology (Intel® AMT 3.x)&lt;/h4&gt;&lt;p&gt;The keys marked YES are acceptable for USB provisioning. The keys marked NO are not recommended for USB provisioning. New keys were used in these tests.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;pre&gt;&lt;/pre&gt;&lt;table border="0" cellpadding="2" class="jiveNoBorder" style="[object]"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;p&gt;System&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Model&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;BIOS&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;SanDisk 1GB&lt;/p&gt;&lt;p&gt;Cruzer Micro&lt;/p&gt;&lt;p&gt;SDCZ61024A10&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Kingston 1GB&lt;/p&gt;&lt;p&gt;DT1001GBKR&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Sony 1GB&lt;/p&gt;&lt;p&gt;Micro Vault&lt;br/&gt;Classic&lt;/p&gt;&lt;p&gt;USM1GJ&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;PNY 2GB Optima&lt;/p&gt;&lt;p&gt;Pro Attached&lt;/p&gt;&lt;p&gt;Enhanced for&lt;/p&gt;&lt;p&gt;Windows ReadyBoost&lt;/p&gt;&lt;p&gt;PFD02GHSPFS&lt;/p&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Intel Desktop Board&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;DQ35JO&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;86.A.0954.2008.0922.2331&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;FSC&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Esprimo P5925&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;6.00 R1.15.2584.A1&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Dell&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Optiplex 755&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A11&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;HP&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;dc7800&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;01.24&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Lenovo&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;ThinkCentre M57p&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;2RKT57AUS&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;04.23.09&lt;/p&gt;&lt;h4 id="USB_Compatibility_Matrix_for_Intel_vPro_Technology_Intel_AMT_4x"&gt;USB Compatibility Matrix for Intel® vPro™ Technology (Intel® AMT 4.x)&lt;/h4&gt;&lt;p&gt;&lt;em&gt;The keys marked YES are acceptable for USB provisioning. The keys marked NO are not recommended for USB provisioning. New keys were used in these tests.&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table border="0" cellpadding="2" class="jiveNoBorder" style="[object]"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;p&gt;System&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Model&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;BIOS&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;SanDisk 1GB&lt;/p&gt;&lt;p&gt;Cruzer Micro&lt;/p&gt;&lt;p&gt;SDCZ61024A10&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Kingston 1GB&lt;/p&gt;&lt;p&gt;DT1001GBKR&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Sony 1GB&lt;/p&gt;&lt;p&gt;Micro Vault&lt;br/&gt;Classic&lt;/p&gt;&lt;p&gt;USM1GJ&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;PNY 2GB Optima&lt;/p&gt;&lt;p&gt;Pro Attached&lt;/p&gt;&lt;p&gt;Enhanced for&lt;/p&gt;&lt;p&gt;Windows ReadyBoost&lt;/p&gt;&lt;p&gt;PFD02GHSPFS&lt;/p&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Acer&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;TravelMate 6493&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;v1.02&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Dell&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Latitude E6400&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;A11&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Fujitsu&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;LifeBook 8420&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;v1.06&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;HP&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;EliteBook 6930P&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;68PCU ver F.0E&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Lenovo&lt;/td&gt;&lt;td&gt;&lt;p&gt;T400&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;7UET43WW (1.15)&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Lenovo&lt;/td&gt;&lt;td&gt;X200&lt;/td&gt;&lt;td&gt;6DET30WW (1.07)&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Toshiba&lt;/td&gt;&lt;td&gt;Tecra A10&lt;/td&gt;&lt;td&gt;1.90&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;04.23.09&lt;/p&gt;&lt;h4 id="USB_Compatibility_Matrix_for_Intel_vPro_Technology_Intel_AMT_5x"&gt;USB Compatibility Matrix for Intel® vPro™ Technology (Intel® AMT 5.x)&lt;/h4&gt;&lt;p&gt;&lt;em&gt;The keys marked YES are acceptable for USB provisioning. The keys marked NO are not recommended for USB provisioning. New keys were used in these tests.&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table border="0" cellpadding="2" class="jiveNoBorder" style="[object]"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;p&gt;System&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Model&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;BIOS&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;SanDisk 1GB&lt;/p&gt;&lt;p&gt;Cruzer Micro&lt;/p&gt;&lt;p&gt;SDCZ61024A10&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Kingston 1GB&lt;/p&gt;&lt;p&gt;DT1001GBKR&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Sony 1GB&lt;/p&gt;&lt;p&gt;Micro Vault&lt;br/&gt;Classic&lt;/p&gt;&lt;p&gt;USM1GJ&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;PNY 2GB Optima&lt;/p&gt;&lt;p&gt;Pro Attached&lt;/p&gt;&lt;p&gt;Enhanced for&lt;/p&gt;&lt;p&gt;Windows ReadyBoost&lt;/p&gt;&lt;p&gt;PFD02GHSPFS&lt;/p&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Lenovo&lt;/td&gt;&lt;td&gt;&lt;p&gt;M58p&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;5CKT40AUS&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;Yes&lt;/p&gt;&lt;/td&gt;&lt;td style="[object]"&gt;&lt;p&gt;No&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;HP&lt;/td&gt;&lt;td&gt;dc7900&lt;/td&gt;&lt;td&gt;786G1 v01.11&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Dell&lt;/td&gt;&lt;td&gt;OptiPlex 960&lt;/td&gt;&lt;td&gt;A01&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;td style="[object]"&gt;Yes&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;04.23.09&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="USB_Provisioning_Tips_for_Lenovo_T61"&gt;USB Provisioning Tips for Lenovo T61&lt;/h4&gt;&lt;p&gt;Use these tips when provisioning a Lenovo T61 notebook:&lt;/p&gt;&lt;ul&gt;&lt;li type="ul"&gt;&lt;p&gt;Don't attempt to USB provision after a forced power off (holding the power button for 5 seconds).  Only attempt a USB provision after a normal shutdown or restart.&lt;/p&gt;&lt;/li&gt;&lt;li&gt;If the USB key fails to provision, load the factory BIOS defaults and try again. If this does not resolve the issue, then do the following:&lt;/li&gt;&lt;/ul&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1" style="padding-left: 60px;"&gt;&lt;li type="ol"&gt;&lt;p&gt;Disable Intel(R) AMT from the BIOS.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Boot the system with the USB key.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Re-enable Intel AMT from the BIOS.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Provision the system using the USB key.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;2.12.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="What_is_the_maximum_number_of_PIDPPS_pairs_that_can_be_used_during_USB_provisioning"&gt;What is the maximum number of PID/PPS pairs that can be used during USB provisioning?&lt;/h4&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;PROBLEM&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;Customers activating a high number of systems using One Touch/USB provisioning may run into performance degradation attempting to import these keys in a management console.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;&lt;strong&gt;RESOLUTION&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;There is no theoretical limit to how many PID/PPS pairs can be on a USB key, but there may be a threshold above which the performance degrades significantly.  At this time, the largest known deployment using USB provisioning was with a 30,000 PID/PPS pair.  Altiris* was unable to process this setup.bin file, however the Intel SCS Console was able to import these keys despite the timeout error that the console indicated.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;4.29.2008&lt;/p&gt;&lt;h4 id="Automating_PIDPPS_key_generation_using_LANDesk_utility"&gt;Automating PID/PPS key generation using LANDesk utility&lt;/h4&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;There is a utility available in your LANDesk installation that allows you to quickly generate a specific numbers of PID/PPS pairs for USB provisioning. Follow these instructions; the steps represent a standard installation.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;ol start="1"&gt;&lt;li type="ol"&gt;&lt;p&gt;Open Windows Explorer and navigate to your LANDesk program files.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Open the managementsuite folder and locate AMTUSBFile.exe.&lt;/p&gt;&lt;/li&gt;&lt;li type="ol"&gt;&lt;p&gt;Open a command window and navigate to the path where AMTUSBFile.exe resides. Use the table below to run the utility.&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;p&gt;To do this...&lt;/p&gt;&lt;/th&gt;&lt;th&gt;&lt;p&gt;Then type this and press Enter...&lt;/p&gt;&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;List all available parameters&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;AMTUSBFile.exe –h&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Generate X number of pairs&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;AMTUSBFile.exe –c &lt;em&gt;current ME password&lt;/em&gt; &lt;em&gt;new ME password&lt;/em&gt; –n &lt;em&gt;number of pairs&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;For example, to generate 625 records would take ~1 second:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;AMTUSBFile.exe –c admin Landesk1! –n 625&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Import the keys from the generated setup.bin to the LANDesk database&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;AMTUSBFile.exe –i&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; LANDesk uses an encrypted string when saving credentials to the database. Sometimes, this encrypted string is invalid to databases, such as Oracle. If this occurs, you may need to run the command several times before the keys are added. Records already imported will not be imported again.&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;p&gt;Verify the list of records in the database&lt;/p&gt;&lt;/td&gt;&lt;td&gt;&lt;p&gt;AMTUSBFile.exe –g&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;6.27.2008&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;*Other names and brands may be claimed as the property of others.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:9999aa93-a92c-4cf7-9f10-7efafe625b62] --&gt;</description>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">usb_provisioning</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">linux</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">amt</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">lenovo</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">uuid</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">hp</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">centrino_pro</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">vpro</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">altiris</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">sms</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">usb</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">scs</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">tools</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">troubleshoot</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">intel_expert</category>
      <pubDate>Mon, 12 Nov 2007 15:34:27 GMT</pubDate>
      <author>steve.lewis@intel.com</author>
      <guid>http://communities.intel.com/docs/DOC-1247</guid>
      <dc:date>2007-11-12T15:34:27Z</dc:date>
      <clearspace:dateToText>3 days, 6 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>Unable to Provision Windows 7 via SCCM</title>
      <link>http://communities.intel.com/message/75177</link>
      <description>&lt;!-- [DocumentBodyStart:259872d8-864f-4254-b69d-5830515faa54] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Mike,&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Glad to hear you got things working finally. Remote provisioning with Configuration Manager &lt;span style="text-decoration: underline;"&gt;does&lt;/span&gt; require you to be using DHCP. Static IPs can be used if you are provisioning in SMB mode (I think). I don't typically get into the SMB side of things.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I'll add this to my checklist for remote provisioning issues for ConfigMgr &lt;img height="16px" src="http://communities.intel.com/images/emoticons/happy.gif" width="16px"/&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Cheers,&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Trevor Sullivan&lt;/strong&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:259872d8-864f-4254-b69d-5830515faa54] --&gt;</description>
      <pubDate>Wed, 25 Nov 2009 09:36:03 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/75177</guid>
      <dc:date>2009-11-25T09:36:03Z</dc:date>
      <clearspace:dateToText>3 days, 15 hours ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>Do it yourself - Power on, patch, and go back to sleep with 4, free .exes</title>
      <link>http://communities.intel.com/community/openportit/vproexpert/blog/2009/11/24/do-it-yourself--power-on-patch-and-go-back-to-sleep-with-4-free-exes</link>
      <description>&lt;!-- [DocumentBodyStart:a2b4e79b-38fc-462c-9f42-99b68dac79e9] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Having worked with Intel Active Management Technology and Intel vPro Technology since version 1.0, it seems to me that there are a whole host of possibilities for those who are do-it-yourself-ers. One is the ability to programmatically wake a system, remotely trigger a process such as a software patch, and then put the system back to sleep. As it turns out, this is not so hard, even for me who has a limited scripting (read batch file) capability. The video chronicles the results of my effort.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;object height="350" width="425"&gt;&lt;param name="movie" value="http://www.youtube.com/v/ZF-ElKoPCOc"/&gt;&lt;param name="wmode" value="transparent"/&gt;&lt;embed height="350" src="http://www.youtube.com/v/ZF-ElKoPCOc" type="application/x-shockwave-flash" width="425" wmode="transparent"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Disclaimer: this is not meant as a how-to or best method. Rather, it is an exploration of what’s possible, meant to educate and stimulate conversation. With that out of the way, let’s get to the fun stuff.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;To accomplish this goal I knew I'd need some help via command line tools. I did an Internet search and found these 4 freely downloadable tools that made it all possible. They are;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;R&lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-1767"&gt;&lt;span style="color: #800080;"&gt;emote Control Util &lt;/span&gt;&lt;/a&gt;- to determine the current power state and turn the system on.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;P&lt;a class="jive-link-external-small" href="http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx"&gt;&lt;span style="color: #800080;"&gt;sService&lt;/span&gt;&lt;/a&gt; - to start a process remotely&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;P&lt;a class="jive-link-external-small" href="http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx"&gt;&lt;span style="color: #800080;"&gt;sShutdown&lt;/span&gt;&lt;/a&gt; - to put the system back to sleep&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;s&lt;a class="jive-link-external-small" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&amp;amp;displaylang=en"&gt;&lt;span style="color: #800080;"&gt;leep.exe&lt;/span&gt;&lt;/a&gt; - so the batch file can sleep while an event takes place.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;The setup is simple; 2 systems. One is the console that executes the batch file and these commands. The other is my vPro system. I setup and configured my it using &lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-4354"&gt;&lt;span style="color: #800080;"&gt;this Use Case Reference design&lt;/span&gt;&lt;/a&gt; (another of my batch file creations). That is to say, there's no TLS and I'm using only the admin account. I then ran the batch file on the console system which triggered the whole process. The process is as follows:&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;1.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Remote control util gets vPro's original power state via AMT (on, sleep, hibernate, or off)&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;2.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Remote control util power's on vPro via AMT&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;3.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Remote control util get's vPro's new power state to verify it has turned on&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;4.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;ping vpro and check the TTL. Once it changes to &amp;lt;=128 the OS has booted. &lt;a class="jive-link-blog-small" href="http://communities.intel.com/community/openportit/vproexpert/blog/2008/11/04/simple-easy-way-to-validate-machine-state-with-ping"&gt;&lt;span style="color: #800080;"&gt;For more info&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;5.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;PsService starts a process on vPro. I used notepad but it could be anything, including triggering a download and run of software patch&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;6.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;PsService exits when the process finishes&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;7.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;PsShutdown gracefully places vPro back to it's original sleep state&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l0 level1 lfo1; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot; mso-fareast-font-family: Arial;"&gt;&lt;span style="mso-list: Ignore;"&gt;8.&lt;span style="font-family: &amp;amp;quot;"&gt;     &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Remote control util get's vPro's new power state to verify it has returned to it's original power state&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Couple of notes.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol;"&gt;&lt;span style="mso-list: Ignore;"&gt;·&lt;span style="font-family: &amp;amp;quot;"&gt;         &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;I set an auto login on my vPro so I could see the process. However, PsService will work without a user being logged in. Also, it can run processes in the back ground so an end user would not be able to interact.&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol;"&gt;&lt;span style="mso-list: Ignore;"&gt;·&lt;span style="font-family: &amp;amp;quot;"&gt;         &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;I used Notepad as my remote process since it made it easy to see success. However, any process can be started. In fact, PsService supports downloading the executable to run. As such, it may be possible to download and then run a patch or batch file as part of this whole process&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="text-indent: -0.25in; margin: 2.4pt 0in; mso-list: l1 level1 lfo2; tab-stops: list .5in;"&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol;"&gt;&lt;span style="mso-list: Ignore;"&gt;·&lt;span style="font-family: &amp;amp;quot;"&gt;         &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;I used a single vPro system. But, with a simple loop the same core batch file could trigger this action on many vPro systems.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-size: 10pt; color: #333333; font-family: &amp;amp;quot;"&gt;Hope you found this post enjoyable and thought provoking. If you have your own do-it-yourself vPro ideas, or want to recreate this one, please share. And, hey, who says batch files are dead?&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:a2b4e79b-38fc-462c-9f42-99b68dac79e9] --&gt;</description>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">vpro</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">remote_control</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">remotecontrolutil</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">do_it_yourself</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">amt</category>
      <pubDate>Thu, 19 Nov 2009 23:54:40 GMT</pubDate>
      <author>jacob.gauthier@intel.com</author>
      <guid>http://communities.intel.com/community/openportit/vproexpert/blog/2009/11/24/do-it-yourself--power-on-patch-and-go-back-to-sleep-with-4-free-exes</guid>
      <dc:date>2009-11-19T23:54:40Z</dc:date>
      <clearspace:dateToText>1 week, 2 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Success Story: Packet Vision Achieves up to a 200% Performance Increase in IPTV Advertising Insertion Stream Density by Migrating to the Intel® Xeon® Processor 5500 Series</title>
      <link>http://communities.intel.com/docs/DOC-4495</link>
      <description>&lt;!-- [DocumentBodyStart:2d40d1d0-a943-4678-b9c6-ea817df7b6cb] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:2d40d1d0-a943-4678-b9c6-ea817df7b6cb] --&gt;</description>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">nehalem</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">service_provider</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">success_story</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">case_study</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">xeon</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">xeon_5500</category>
      <pubDate>Tue, 24 Nov 2009 17:01:10 GMT</pubDate>
      <author>sally.sams@intel.com</author>
      <guid>http://communities.intel.com/docs/DOC-4495</guid>
      <dc:date>2009-11-24T17:01:10Z</dc:date>
      <clearspace:dateToText>4 days, 7 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>Intel® vPro™ Technology and HP SDP* for Telecom Operators</title>
      <link>http://communities.intel.com/docs/DOC-4493</link>
      <description>&lt;!-- [DocumentBodyStart:06f8f486-5f75-4324-9168-cf57c5b66067] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:06f8f486-5f75-4324-9168-cf57c5b66067] --&gt;</description>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">solution_brief</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">service_provider</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">vpro</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">hp_sdp</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">hp</category>
      <pubDate>Tue, 24 Nov 2009 16:22:37 GMT</pubDate>
      <author>sally.sams@intel.com</author>
      <guid>http://communities.intel.com/docs/DOC-4493</guid>
      <dc:date>2009-11-24T16:22:37Z</dc:date>
      <clearspace:dateToText>4 days, 8 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>PC Refresh Cycles and Windows 7 … what’s the financial connection?</title>
      <link>http://communities.intel.com/community/openportit/vproexpert/blog/2009/11/23/pc-refresh-cycles-and-windows-7-what-s-the-financial-connection</link>
      <description>&lt;!-- [DocumentBodyStart:38f6bd86-2dd4-420c-b212-c3e1db7da1ad] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p class="MsoNormal" style="margin: 0in 0in 10pt;"&gt;&lt;span style="font-family: Calibri; color: #000000; font-size: 12pt;"&gt;It’s understandable that in today’s economy that you might consider pushing out your PC refresh cycle to save cash today.&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;&lt;span style="mso-spacerun: yes;"&gt; &lt;/span&gt;This is an area of cost cutting that many companies consider so you’re not alone.&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;But if you have considered, or are considering, pushing out your PC refresh cycle, have you factored in all of the costs that impact that decision?&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;&lt;span style="mso-spacerun: yes;"&gt; &lt;/span&gt;These costs include the unexpected costs of supporting older machines once the warranty has expired, higher energy costs compared to new machines, and more.&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;The total cost of ownership starts to increase out in time and will eventually reach a point where it makes more sense to replace your PCs versus continuing to maintain them.&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;But how do you know what the optimal replacement time is?&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;&lt;span style="mso-spacerun: yes;"&gt;And is &lt;/span&gt;delaying your refresh really the best financial decision?&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="margin: 0in 0in 10pt;"&gt;&lt;span style="color: #000000;"&gt;&lt;span style="font-family: Calibri;"&gt;&lt;span style="font-size: 12pt;"&gt;There are strong financial reasons to refresh PCs now and, with the Windows 7 operating system, there are even stronger reasons to do so with PCs powered by Intel® Core™ 2 processors with vPro™ technology.&lt;span style="mso-spacerun: yes;"&gt;   &lt;/span&gt;Join me for a webcast on Tuesday, December 1&lt;/span&gt;&lt;span style="font-size: 10pt;"&gt;&lt;sup&gt;st&lt;/sup&gt;&lt;/span&gt;&lt;span style="font-size: 12pt;"&gt;, where I’ll walk  through our analysis on the PC refresh cycle and the framework we use, discuss the true cost of older PCs and how to assess your own PC refresh cycle, and share our experience with Windows 7 as part of the Technical Adopter Program (TAP).&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;&lt;span style="mso-spacerun: yes;"&gt; &lt;/span&gt;I’ll also be joined by Amy Stephan from Microsoft who will provide more insight into why it makes sense to refresh now and why Windows* 7 and New PCs with Intel® vPro™ Technology are better together.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class="MsoNormal" style="margin: 0in 0in 10pt;"&gt;&lt;span style="color: #000000;"&gt;&lt;span style="font-size: 12pt;"&gt;&lt;span style="font-family: Calibri;"&gt;Register now at:&lt;span style="mso-spacerun: yes;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;a class="jive-link-external-small" href="http://webcasts.techrepublic.com.com/abstract.aspx?docid=1177231&amp;amp;tag=content;rightCol"&gt;http://webcasts.techrepublic.com.com/abstract.aspx?docid=1177231&amp;amp;tag=content;rightCol&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:38f6bd86-2dd4-420c-b212-c3e1db7da1ad] --&gt;</description>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">microsoft</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">pc_refresh</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">vpro</category>
      <pubDate>Tue, 24 Nov 2009 04:23:28 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/community/openportit/vproexpert/blog/2009/11/23/pc-refresh-cycles-and-windows-7-what-s-the-financial-connection</guid>
      <dc:date>2009-11-24T04:23:28Z</dc:date>
      <clearspace:dateToText>4 days, 20 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>Webinars: Learn More About Intel vPro Technology</title>
      <link>http://communities.intel.com/docs/DOC-3492</link>
      <description>&lt;!-- [DocumentBodyStart:19820187-4025-4ff5-8fcd-2d8985cc96fa] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;&lt;div class="toc" style="border: 1px dashed black; padding: 10px"&gt;&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Getting_Started"&gt;Getting Started&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Introduction_to_Intel_vPro_Technology"&gt;Introduction to Intel® vPro™ Technology&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Management_Consoles"&gt;Management Consoles&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Microsoft_System_Center_Configuration_Manager"&gt;Microsoft System Center Configuration Manager&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Activate_Today_Realize_ROI_with_Intel_vPro_Technology_and_Microsoft_System_Configuration_Manager"&gt;Activate Today! Realize ROI with Intel® vPro Technology and Microsoft System Configuration Manager&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_vPro_Technology_with_Microsoft_System_Center__Session_1"&gt;Intel® vPro™ Technology with Microsoft System Center - Session 1&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_vPro_Technology_with_Microsoft_System_Center__Session_2"&gt;Intel® vPro™ Technology with Microsoft System Center - Session 2&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Symantec_Altiris"&gt;Symantec Altiris&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Enhancing_the_Symantec_Management_Platform_Altiris_with_Intel_vPro_Technology"&gt;Enhancing the Symantec Management Platform (Altiris) with Intel® vPro™ Technology&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Activate_Today_Realize_ROI_with_Intel_vPro_Technology_and_Symantec_Altiris"&gt;Activate Today! Realize ROI with Intel® vPro Technology and Symantec Altiris&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Lower_Your_IT_Manageability_Costs_with_Intel_vPro_Technology_and_Symantec_Altiris_CMS"&gt;Lower Your IT Manageability Costs with Intel vPro Technology and Symantec Altiris CMS&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Technologies"&gt;Technologies&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Dynamic_Virtual_Client"&gt;Dynamic Virtual Client&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Introduction_to_Dynamic_Virtual_Client_with_Intel_vPro_Technology"&gt;Introduction to Dynamic Virtual Client with Intel vPro Technology&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_AntiTheft_Technology"&gt;Intel Anti-Theft Technology&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Securing_Your_Environment_with_Intel_AntiTheft_Technology"&gt;Securing Your Environment with Intel Anti-Theft Technology&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Intel_AntiTheft_Technology_with_Absolute_Software"&gt;Intel® Anti-Theft Technology with Absolute Software&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Microsoft_Windows_7"&gt;Microsoft Windows 7*&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Use_Cases"&gt;Use Cases&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Power_Management"&gt;Power Management&lt;/a&gt;
&lt;/li&gt;
&lt;ul&gt;&lt;ul&gt;&lt;li&gt;
&lt;a class="jive-link-anchor-small" href="#Energy_Efficient_Performance_with_Intel_vPro_Technology_and_Verdiem_Surveyor"&gt;Energy Efficient Performance with Intel® vPro™ Technology and Verdiem Surveyor&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h3 id="Getting_Started"&gt;Getting Started&lt;/h3&gt;&lt;h6 id="Introduction_to_Intel_vPro_Technology"&gt;&lt;a class="jive-link-blog-small" href="http://communities.intel.com/community/openportit/vproexpert/blog/2009/08/19/resources-and-recording-from-intro-to-intel-vpro-technology-webinar"&gt;Introduction to Intel® vPro™ Technology&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;Jeff Torello covers the basics of Intel vPro Technology in this webinar. Learn what it is, how you can use it to simplify your IT environment, and next steps for activating your PCs with Intel vPro technology.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 8.19.09&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-external-small" href="http://webcasts.techrepublic.com.com/vc_landing.aspx?viewid=1163333"&gt;&lt;strong&gt;The Bottom Line on Hardware Refresh&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;IT capital budgets are more challenging than ever. Many IT departments have postponed their PC refresh, but applying models from the corporate finance office can reveal the true costs of older hardware. Intel and Dell subject matter experts take an in-depth look at the balance sheet to help you determine an optimal refresh cycle.&lt;/p&gt;&lt;h3 id="Management_Consoles"&gt;Management Consoles&lt;/h3&gt;&lt;h4 id="Microsoft_System_Center_Configuration_Manager"&gt;Microsoft System Center Configuration Manager&lt;/h4&gt;&lt;h6 id="Activate_Today_Realize_ROI_with_Intel_vPro_Technology_and_Microsoft_System_Configuration_Manager"&gt;&lt;a class="jive-link-external-small" href="http://webcasts.techrepublic.com.com/abstract.aspx?docid=989985"&gt;Activate Today! Realize ROI with Intel® vPro Technology and Microsoft System Configuration Manager&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;Join the team from the Intel vPro Expert Center for an informative Webcast on the ROI savings and activation process for PCs with Intel® vPro™ technology and Microsoft System Configuration Manager.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 7.15.09&lt;/em&gt;&lt;/p&gt;&lt;h6 id="Intel_vPro_Technology_with_Microsoft_System_Center__Session_1"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/Training/2009-05-08%2010.06%20Intel_%20vPro_%20Technology%20with%20Microsoft%20System%20Center%20_%20Session%201.wmv"&gt;Intel® vPro™ Technology with Microsoft System Center - Session 1&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;This webinar covers the important prerequisites for the infrastructure and configurations necessary in Microsoft System Center Configuration Manager (SCCM) to take advantages of the Intel vPro use cases – Power Management and Remote Diagnostic and Repair.  After this session, you will have a general understanding how to configure your SCCM SP1 environment to support Intel vPro technologies and start leveraging the use cases to improve support for the end customer.  For detailed explanation of all configuration steps, it will be necessary to review the online training session: &lt;a class="jive-link-external-small" href="http://bit.ly/Hn2n"&gt;http://bit.ly/Hn2n&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 5.8.09&lt;/em&gt;&lt;/p&gt;&lt;h6 id="Intel_vPro_Technology_with_Microsoft_System_Center__Session_2"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/Training/2009-05-22%2010.00%20Intel_%20vPro_%20Technology%20with%20Microsoft%20System%20Center%20_%20Session%202.wmv"&gt;Intel® vPro™ Technology with Microsoft System Center - Session 2&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;The webinar covers Intel(r) vPro technology features, such as built-in manageability, proactive security, and energy-efficient performance. This session will demonstrate how you can take advantage of Microsoft System Center's Configuration Manager 2007 SP1 to provision, discover, accomplish help desk features to break/fix, and do remote power control for Intel vPro clients.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 5.22.09&lt;/em&gt;&lt;/p&gt;&lt;h4 id="Symantec_Altiris"&gt;Symantec Altiris&lt;/h4&gt;&lt;h6 id="Enhancing_the_Symantec_Management_Platform_Altiris_with_Intel_vPro_Technology"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/Training/IntelvPro_Symantec.wmv"&gt;Enhancing the Symantec Management Platform (Altiris) with Intel® vPro™ Technology&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;Terry Cutler, a Solution Architect at Intel, discusses the benefits of using the Symantec Management Platform to manage your PCs with Intel vPro technology. Terry demos several use cases in this webinar.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 9.2.09&lt;/em&gt;&lt;/p&gt;&lt;p style="padding-left: 30px;"&gt;&lt;a class="jive-link-blog-small" href="http://communities.intel.com/community/openportit/vproexpert/blog/2009/09/04/resources-and-recording-from-symantec-altiris-intel-vpro-webinar"&gt;Resources and recording from Symantec Altiris &amp;amp; Intel vPro webinar&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h6 id="Activate_Today_Realize_ROI_with_Intel_vPro_Technology_and_Symantec_Altiris"&gt;&lt;a class="jive-link-external-small" href="http://webcasts.techrepublic.com.com/abstract.aspx?docid=989983"&gt;Activate Today! Realize ROI with Intel® vPro Technology and Symantec Altiris&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;Join the team from the Intel vPro Expert Center for an informative Webcast on the ROI savings and activation process for PCs with Intel® vPro™ technology and Symantec Altiris.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 7.8.09&lt;/em&gt;&lt;/p&gt;&lt;p style="padding-left: 30px;"&gt;&lt;a class="jive-link-blog-small" href="http://communities.intel.com/community/openportit/vproexpert/activation/blog/2009/07/17/recording-and-qas-available-activate-today-realize-roi-with-intel-vpro-technology-and-symantec-altiris"&gt;Recording and Q&amp;amp;As Available: Activate Today! Realize ROI with Intel® vPro Technology and Symantec Altiris&lt;/a&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h6 id="Lower_Your_IT_Manageability_Costs_with_Intel_vPro_Technology_and_Symantec_Altiris_CMS"&gt;&lt;a class="jive-link-external-small" href="http://www.advancedmarketplace.com/webinar"&gt;Lower Your IT Manageability Costs with Intel vPro Technology and Symantec Altiris CMS&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;Nearly 90 percent of an organization’s IT budget and time is spent keeping their business running securely and smoothly. When provisioned with Altiris solutions, computers with Intel vPro processor technology allow unprecedented ability to solve business IT problems.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 4.16.09&lt;/em&gt;&lt;/p&gt;&lt;h3 id="Technologies"&gt;Technologies&lt;/h3&gt;&lt;h4 id="Dynamic_Virtual_Client"&gt;Dynamic Virtual Client&lt;/h4&gt;&lt;h6 id="Introduction_to_Dynamic_Virtual_Client_with_Intel_vPro_Technology"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/training/webinar_intro_to_dvc.htm"&gt;Introduction to Dynamic Virtual Client with Intel vPro Technology&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;This webinar will go over the spectrum of client computing models and guide you towards the model that accomplishes centralized management, policy-driven data security with client-side computing. Intel® vPro™ Technology can be leveraged to ease your Windows 7 operating system enterprise deployment and reduce the end user disruptiveness the transition may cause.&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;a class="jive-link-blog-small" href="http://communities.intel.com/community/openportit/vproexpert/emergingcomputing/blog/2009/11/18/watch-it-on-demand-intro-to-dvc-recording-now-available"&gt;Watch it on-demand! Intro to DVC recording now available&lt;/a&gt;&lt;/p&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 11.17.09&lt;/em&gt;&lt;/p&gt;&lt;h4 id="Intel_AntiTheft_Technology"&gt;Intel Anti-Theft Technology&lt;/h4&gt;&lt;h6 id="Securing_Your_Environment_with_Intel_AntiTheft_Technology"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/training/2009-06-23_VirtualConferenceSeries_Intel_AntiTheft.wmv"&gt;Securing Your Environment with Intel Anti-Theft Technology&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;Today’s business environment is extremely difficult. All types of organizations are being asked to do more with less. And with the cost and impact of PC theft, security has become even more important to corporations and IT leaders. Join us to hear how IT professionals can take advantage of new technologies to protect their business. Join Dr. Larry Ponemon (Ponemon Institute), Mike Schulien (Intel), and Geoff Glave (Absolute Software) as they discuss the impact of data breaches, Intel Anti-Theft technology, and Computrace Software from Absolute.&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-wiki-small" href="http://communities.intel.com/docs/DOC-3266"&gt;Click to read the Q &amp;amp; As.&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 6.23.09&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h6 id="Intel_AntiTheft_Technology_with_Absolute_Software"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/training/2009-06-05%2010.02%20Intel_%20Anti_Theft%20Technology%20Overview.wmv"&gt;Intel® Anti-Theft Technology with Absolute Software&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;This webinar introduces Intel® Anti-Theft Technology (Intel® AT). Intel AT provides a set of hardware and software security building blocks to disable lost/stolen laptops with a poison pill, disable access to data, and allow simple and secure reactivation for recovered laptops.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 6.2.09&lt;/em&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;h4 id="Microsoft_Windows_7"&gt;Microsoft Windows 7*&lt;/h4&gt;&lt;p class="Comm-BodySub"&gt;&lt;strong&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/training/webinar_intro_to_Win7Tech.html"&gt;Windows 7 and Intel vPro Technology - Technical Overview&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&lt;p class="Comm-BodySub"&gt;&lt;span lang="PT-BR"&gt;This webinar will give you a technical overview of the Windows 7 operating system and Intel® vPro™ Technology and how they complement each other to enhance the manageability and security of the business client. The webinar will also focus on how Intel® vPro™ Technology can be leveraged to ease your Windows 7 operating system enterprise deployment and reduce the end user disruptiveness the transition may cause.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;a class="jive-link-blog-small" href="http://communities.intel.com/community/openportit/vproexpert/blog/2009/11/18/miss-the-win7-and-intel-vpro-technical-webinar-recording-now-available"&gt;Miss the Win7 and Intel vPro technical webinar? Recording now available.&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 11.18.09&lt;/em&gt;&lt;/p&gt;&lt;h3 id="Use_Cases"&gt;Use Cases&lt;/h3&gt;&lt;h4 id="Power_Management"&gt;&lt;strong&gt;Power Management&lt;/strong&gt;&lt;/h4&gt;&lt;h6 id="Energy_Efficient_Performance_with_Intel_vPro_Technology_and_Verdiem_Surveyor"&gt;&lt;a class="jive-link-external-small" href="http://www.vproexpert.com/E24VZ/Training/2009-06-19-EnergyEfficientPerformance_IntelvProandVerdiem.wmv"&gt;Energy Efficient Performance with Intel® vPro™ Technology and Verdiem Surveyor&lt;/a&gt;&lt;/h6&gt;&lt;p&gt;The webinar focuses on Intel® vPro™ technology's energy efficient performance and how it can save money by reducing PC energy usage. This session includes demos of specific use cases with Verdiem Software.&lt;/p&gt;&lt;p&gt;&lt;em&gt;Aired 6.19.09&lt;/em&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:19820187-4025-4ff5-8fcd-2d8985cc96fa] --&gt;</description>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">roi</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">energy_efficiency</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">power_management</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">symantec</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">sccm_sp1</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">anti-theft</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">training</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">vpro</category>
      <category domain="http://communities.intel.com/tags?containerType=14&amp;container=2005">webinar</category>
      <pubDate>Fri, 17 Jul 2009 20:54:49 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/docs/DOC-3492</guid>
      <dc:date>2009-07-17T20:54:49Z</dc:date>
      <clearspace:dateToText>5 days, 31 minutes ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

