Home > Intel Communities > Open Port IT Community > Intel® vPro™ Expert Center > Microsoft Manageability

Blog Posts

69 Posts 1 2 3 Previous Next
0

One of the new additions to Config Manager SP2 is native support of wireless access for managing clients with AMT.  Microsoft has built in support for configuring enterprise level wireless profiles such as WPA2-Enterprise.  These are wireless profiles that support RADIUS authentication using an authentication server to decide whether or not a given client is allowed to access the network.  Config Manager SP2 does not support wireless profiles that use pre-shared keys (PSK).  If you use security standards like WPA2-PSK/WPA2-Personal in your environment you will need to use the scripting framework tool to generate a script that can configure this option outside of Config Manager.

Mohan Veeramachaneni has put together several guides that explain how to configure the back-end RADIUS authentication components and access point configuration.

Cisco ACS

Configure Cisco ACS Server for Navigating Secure Networks with AMT/vPro

Microsoft NPS

Simple Configuration of Microsoft NPS as Radius for 802.1X - Part 1

Simple Configuration of Microsoft NPS as Radius for 802.1X - Part 2

Microsoft IAS

Step-by-step Guide for Navigating Secure Networks (802.1x) with Intel® AMT™ using Microsoft® SCCM SP1 & Microsoft® Radius (IAS)

Matt Royer has a blog entry that covers wireless profile management in Config Manager SP2.  The process he outlines is still the same in the release version of SP2.

http://communities.intel.com/community/openportit/vproexpert/microsoft-vpro/blog/2009/06/05/a-closer-look-at-sccm-sp2-beta-oob-wireless-management-wireless-profile-management

Key things to remember about wireless management with Config Manager

  • Config Manager will not update a wireless profile that is currently in use.
  • Config Manager now uses DNS entries to resolve client names.  You may run into a case where a client has switched between a wired or wireless connection and AMT is temporarily inaccessible due to delays in DNS update propagation.  DNS caching on your Config Manager server can also cause this to occur.  You can try running the “ipconfig /flushdns” command from a command prompt to clear the local DNS cache on your Config Manager server.
  • Launching a Serial-over-LAN session over a wireless connection while the client’s OS is using that same connection will cause the wireless network to be cut off to the OS.
0 Comments Permalink
0

Microsoft has just released System Center Configuration Manager Service Pack 2.  In addition to providing feature parity with SP1 and AMT firmware versions 3.2.1, 4.0 and 5.0, the following new features are supported:

  • Wireless management with up to 8 wireless profiles
  • End point access control: 802.1x support
  • Audit logging
  • Support for different power states
  • Power control options at the collection level
  • Data storage
  • Scheduling configuration for in-band provisioning

 

You can download it from the following location:http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140#tm

 

--Matt Royer

0 Comments Permalink
0

The Intel WS-MAN Translator build 568 has just been released.  The new features of this build included:

 

  • Validated with Microsoft System Center Configuration Manager 2007 Service Pack 2
  • Enhances legacy support for wireless profiles, 8021.x profiles, and 3rd party data storage
  • Enhanced Kerberos authentication and Kerberos ticket handling

 

There are known issues and feature gaps with the previous versions (builds less than 568) of the Intel WS-MAN and Microsoft SCCM SP2.  It is recommended that customers upgraded to Intel WS-MAN Translator build 568 when upgrading to SCCM SP2.  SCCM SP1 customers will also see stability and performance increases by upgrading to this WS-MAN Translator build.

 

--Matt Royer

0 Comments Permalink
0

An updated version of the SCS to SCCM migration utility has just been released.  For those customers that were previously activated on the SMS Add-on and the Intel SCS, this utility will help ease your migration to SCCM SP1 or the upcoming SCCM SP2.  This new version has been tested and validated to support up to SCS 5.x and SCCM SP2.

The SCS to SCCM migration utility is used to prepare Intel® Active Management Technology (Intel® AMT) systems, that were configured using the Intel® Setup and Configuration Service (Intel® SCS) and managed by any management console, to be configured and managed by Microsoft* System Center Configuration Manager (SCCM).

The migration utility is an executable (SCS_2_SCCM_Migration_Utility.exe) that performs the following:

  1. Creates a Comma Separated Values (CSV) file containing information on all Intel AMT systems configured by the Intel SCS that are to be migrated. This CSV file includes the data about these systems that is needed by SCCM and is imported to SCCM before the actual migration.
  2. Performs a series of tasks (including partial unconfiguration) that bring the Intel AMT systems to a state that will enable the SCCM to configure them.
  3. Removes the records of the migrated Intel AMT system from the SCS database.

Once the Intel AMT systems are unconfigured they will send out “Hello” messages to SCCM, which will then configure the systems.

The SCS to SCCM migration Utility can be downloaded from the following location: http://software.intel.com/en-us/articles/intel-amt-setup-and-configuration-service-scs-to-microsoft-system-center-configuration-manager-sccm-system-migration/

--Matt Royer

0 Comments Permalink
1

PROs002 class overview

 

Wired/wireless & Indepent of OS / Power state

*today is the announcement of SCCM SP2

Extending the wireless capabilities of SCCM

SANY0087.JPG

 

 

Config Mgr 2k7 features:

*setup & config

*discovery / inventory/audit

*remote console

* power control

 

*Bring vpro scenarios to your groups & collections – just making it part of your daily cycle’s.

“huge extension” in the out of band scenario

 

Power Management:

(site configuration, client relationship, collection based management).  Ability to do specific targeting to the client.

 

Help desk efficiency

·      remotely restart computer

·      interactive remote boot

·      remotely interact with bios

·      review core system HW inventory and audit info

3 Key messages for SCCM SP2

*Automate deployments

Increase Deployment reliability

Extend remote deployment scenarios to inpocrporate (reboot via id-r-reboot to PXE services.

 

Service pack 2 – MS SCCM

-       vPro integration

-       win7 enablement

-       Better together keeps ringing thru.

SANY0092.JPG

 

Here's what we have been waiting for..  SCCM SP2 - RC ready to go.

 

SANY0093.JPG

1 Comments Permalink
0

Check out Jeff Wettlaufer and Matt Royer talking about their upcoming class and partnership.

 

 

Key in the class is the integration elements and what we (Intel & Microsoft) have been working on.    PROs002 is the class code for the session.

0 Comments Permalink
0

This information is based on Microsoft’s Release Candidate of System Center Configuration Manager Service Pack 2 and is subject to change.

 

There are several new features / changes that are coming with ConfigMgr SP2 related to AMT / vPro functionality.  As noted in previous articles, some of the more obvious changes are:


OOB Wireless Management: Wireless Profile Management

    • Provide configuration of up to eight (8) wireless profiles per site that are available to AMT clients assigned to that site
    • Set the wireless information during AMT provisioning and configure all required profile settings (SSID, key management, encryption, etc.
    • Send wireless profile operations to the Intel translator on AMT systems with revisions earlier than 3.2.

End Point Access Control: 802.1x support

    • Provision 802.1x settings on AMT wireless clients during AMT provisioning
    • Send 802.1x settings operations to the Intel translator on AMT systems with revisions earlier than 3.2.1

Data Store (3PDS)

    • Write string data into 3PDS on AMT through OOB management console

Access Monitor: Audit Log

    • Enable or Disable Audit Log (no critical event settings)
    • View Audit Log through OOB Console

Remote Power Management

    • Power State Configuration

 

 

However, Microsoft has also made some more subtle changes between SCCM SP1 and SP2 to improve the end user experience that you may have not notice.

 

  • In-band Provisioning attempt schedule:  With SCCM SP1, in-band provisioning was hard coded to initiate once every 24 hours.  SCCM SP2 now supports the ability to set the provisioning attempt schedule to a configurable value within the Out of Band Management Properties - Provisioning Schedule Tab.
  • Handling wired and wireless contented clients with in-band provisioning:  To provision an AMT / vPro client with SCCM 2007, first stage provisioning must be completed on the wired interface.  With SCCM 2007 SP2, the wired interface information will be sent along with the AMT One Time Password (OTP) during agent initiated in-band provisioning.  Second stage provisioning can then occur over either wireless or wired interface (which one is resolved by DNS).
  • Out of Band Provisioning disabled by default:  The ability to use Out of Band provisioning (provisioning through AMT hello packet initiation) is configurable and defaulted to disabled with SCCM 2007 SP2.  If you are using Out of Band provisioning, you will need to enable it after upgrading from SCCM SP1 to SCCM SP2.  This is configured on the Out of Band Management Properties - General Tab.
  • Opening the Out of Band Console ensures an updated Kerberos token:  With SCCM SP1, occasionally you would run into a scenario where the Out of Band Management Console would attempt to connect with an expired or involved Kerberos token; this would prevent OOB Console from properly authenticating with the AMT / vPro Client.  This was common if you tried to connect to an AMT / vPro client immediately after an AMT client reprovision.  The Out of Band Management Console with SCCM SP2 now refreshes the Kerberos token to ensure a proper connection.
  • AMT / vPro client provisioning prevented if Configuration Manager Client is blocked or not approved:  If an SCCM client is block or not approved within with the site server, SCCM will not allow you provision an AMT / vPro client.
  • AMT PKI Certificates are revoked during an Update Management Controller:  If you have wired or wireless 802.1x authentications being used, SCCM will revoke these certificates and new certificate will be requested & issued.  As a clarifying note, the AMT TLS certificate used to secure the manageability traffic will not be revoked during this process.
  • Power control available for collection execution:  SCCM SP2 now allows the execution of an AMT power control on an entire collection just by right clicking on the collection and selecting Out of Band Management -> Power Control.  Previously with SCCM SP1, you were required to multi-select all the clients in that collection to perform the same function.
  • Serial over LAN (SOL) requires manual initiation with the Out of Band Management Console:  With SCCM SP1, when you opened the Out of Band Management Console, the SOL session was automatically started.  In SCCM SP2, you are now required to open and close the Serial over LAN connection via a new button or with the new Tools menu option.
  • IDE-Redirect Log renamed: What was previous known as the System Audit Log in SCCM SP1 within the Out of Band Management Console has been renamed to IDE-Redirect Log.  This was done to allow the AMT Audit Log to assuming that name.
  • Working with AMT Data Storage: Within SCCM SP2, you are now able to interact with the AMT / vPro 3rd Party Data Store through the new button added in Out of Band Management Console labeled Data Storage.  Note that the data storage is limited to ASCII characters and length of 4096 bytes.

 

 

--Matt Royer

0 Comments Permalink
0

Microsoft System Center Configuration Manager can provision an AMT / vPro client in two different capacities: Bare metal and Agent Initiated.  Bare metal provisioning begins with the AMT client sending a “hello packet” to the SCCM Out of Band Service Point; if the AMT client is approved and authorized to be provisioned, SCCM will initiated the provisioning process.  Agent Initiated provisioning begins with the SCCM Client Agent pulling down the “Automatic Provisioning” policy from the SCCM Policy Server; if the SCCM Client Agent receives the policy, the Agent will negotiated a One Time password (OTP) with the AMT ME firmware and send the provisioning request along with the OTP to the Out of Band Service point to begin the provisioning process.


Bare Metal / Hello Packet Initiated Provisioning
For Bare Metal provisioning to work properly on AMT / vPro Clients with firmware 2.x, there are a couple of prerequisites that must be met.


SCCM Server


AMT Client

  • AMT Firmware version that support PKI provisioning with SCCM.  For AMT 2.x Desktops and Laptops, you will want to ensure that you have a minimum of AMT Firmware 2.2.20 (Desktop) and 2.2.20 (Laptop).  Note: For AMT Desktops with firmware 3.x, you will want to ensure that you have firmware 3.2.2 or above to meet the minimal requirements.  AMT Laptops with firmware 4.x and Desktops with firmware 5.x have the minimum requirements meet from the initial firmware release.

 

SCCM Client Agent Initiated Provisioning
In addition to the prerequisites needed for Bare Metal provisioning, SCCM Agent initiated provisioning requires a couple additional items.


AMT Client

  • AMT ME / HECI Driver installed (available from your OEM driver website)
  • Execution of RNGSeedCreator.exe (Download available from here: http://communities.intel.com/docs/DOC-3807).  RNGSeedCreator.exe is an executable that is ran on an AMT / vPro client with firmware version 2.x that has never been configured or provisioned; this utility generates a random number for the firmware to support the OTP used during the SCCM Agent Initiated Provisioning process.  For SCCM PKI provisioning to complete successfully, the random number generated by RNGSeedCreator.exe must be completed prior to initiating provisioning via the SCCM Client Agent.Note: AMT / vPro clients with firmware version 3.x and higher do not need to have the RNGSeedCreator.exe ran prior to SCCM Agent Initiated provisioning.

 

 

If your AMT clients do not meet the minimal firmware version for PKI based provisioning (Bare Metal or Agent Initiated), you can use the software distribution capabilities within SCCM to remotely upgrade the AMT firmware and drivers; check out the following Blog / Video which walks you through creating this software package.  Similar to upgrading the AMT firmware with SCCM Software distribution, you can also use the same Software Distribution process to run the RNGSeedCreator.exe utility on your 2.2 (Desktop) and 2.6 clients.  If you wish to combine the firmware upgrade and RNGSeedCreator.exe execution into a single SCCM advertisement, you can construct a single task sequence that runs both the Firmware upgrade and RNGSeedCreator.exe software packages.  A guide on how to accomplish this has been included in the RNGSeedCreator download package.

 

 

Once the firmware has been upgraded to the minimal firmware version to support PKI provisioning and the RNGSeedCreator.exe has been run, SCCM Agent Initiated provision can complete successfully on 2.2 and 2.6 clients.


--Matt Royer

0 Comments Permalink
0

Microsoft has recently updated the Configuration Manager Documentation Library for out of band management for SP2, including revisions to troubleshooting issues.  Some of these revisions are also applicable to Configuration Manager 2007 SP1, but they can't publish them with their monthly updates because of the new SP2 content.  Rather than waiting until SP2 is released, they have included the revisions here that affect existing customers using out of band management in Configuration Manager 2007 SP1.

 

http://blogs.technet.com/configmgrteam/archive/2009/08/13/updated-troubleshooting-information-for-out-of-band-management-sp1.aspx

 

 

--Matt Royer

0 Comments Permalink
0

Microsoft has released a really great blog on the “Security Best Practices for Out of Band Management in Configuration Manager 2007 SP1”.  The following topics are covered in great detailed and is a definite read.  http://blogs.technet.com/configmgrteam/archive/2009/08/05/updated-security-best-practices-for-out-of-band-management-in-service-pack-1.aspx

 

  • Request customized firmware before purchasing AMT-based computers
  • Use in-band provisioning instead of out of band provisioning
  • Manually revoke certificates and delete Active Directory accounts for AMT-based computers that are blocked by a Configuration Manager 2007 SP1 site 
  • Control the request and installation of the provisioning certificate
  • Ensure that you request a new provisioning certificate before the existing certificate expires
  • If the provisioning certificate is revoked, delete it from the certificate store on the out of band service point site system server, and remove it from the out of band management component configuration properties
  • If you must revoke a provisioning certificate supplied by an internal CA, revoke the certificate in the Certification Authority console
  • Use a dedicated certificate template for provisioning AMT-based computers
  • Use out of band management instead of Wake On LAN
  • Use a dedicated OU to publish AMT-based computers
  • Use Group Policy to Restrict User Rights for the AMT Accounts
  • Use a dedicated collection for in-band provisioning
  • Restrict who has the Media Redirection right and the PT Administration right
  • Retrieve and store image files securely when booting from alternative media to use the IDE redirection function
  • Minimize the number of AMT Provisioning and Discovery Accounts

 

--Matt Royer

0 Comments Permalink
2

Here is a demonstration I created on how to setup a SCCM advertisement to remotely and securely wake-up (boot) Intel vPro systems and push an automated BIOS upgrade.  I wanted to show a useful and real-world Intel vPro Use Case that you can use today.  If there are other Use Cases you would like to see, please post your comments and I will get more of these types of videos posted.

 

Thanks,

Bill

 

2 Comments Permalink
1

SCCM Log Parser Script

Posted by Dan Brunton Jun 25, 2009

Reading through the wealth of information in SCCM logs can be a challenge, especially if you are provisioning a lot of systems at one time.  I've put together a VBScript example to help make the job of debugging provisioning problems easier.  This script will parse through the log file you specify and create a new log file containing entries relevant to the string you are searching for.  The most common usage for this would be to look through the amtopmgr.log for all entries related to a specific computer name.  This script will first go through the log and find all the thread values associated with the computer name, then, it will take any log entry with any of those thread values and place it in a new file and launch it in the SMS Trace (Trace32) application.  The idea is that having all these entries, not just the lines with the computer name, will paint a more complete picture of what has gone on during the provisioning process and cut back on the time spent looking for relevant log entries by hand.  Here's some information on how to run the script.

Required parameters:

/l: - The SCCM log file you want to parse, typically amtopmgr.log

/s: - The search string, often a computer name, you want to parse the logs for

Optional parameters:

/o: - The name of the parsed log file this script will produce.

      If no name is specified, the file will be named:

      <specified computer name>.log

Example: cscript sccmlogparse.vbs /l:amtopmgr.log /s:vProPC /o:parsedlog.log

You can download the script here:

http://communities.intel.com/docs/DOC-3400

1 Comments Permalink
0

Whenever you make a change to your Out-of-Band configuration settings in SCCM you need to push that change out to your Intel® AMT clients.  Normally you have to go through each of your collections that has AMT systems in it and tell SCCM to manually update the management controller configuration.  It is possible to automate this process using a script that makes WMI calls to the SCCM server, requesting it update the management controllers in your clients.  This can be scheduled as an advertisement to be run automatically.  This package contains documentation that outlines the required security, creation of the update task and an example VBscript.  You can download the package here:

 

http://communities.intel.com/docs/DOC-3399

0 Comments Permalink
3

The SCCM Out-of-Band (OOB) Management Console is a stand-alone executable that is typically launched from within the SCCM console application itself. There may be cases where different groups in an IT department will want to make use of the OOB access to clients, but should not have access to the other features of SCCM in order to maintain proper separation of duties and best known security practices. It is possible to use existing technologies to launch the OOB Management Console outside of the SCCM console application itself. This package contains documentation that explains the required SCCM security configuration and includes and example VBScript.  You can download the package here:

 

http://communities.intel.com/docs/DOC-3398

3 Comments Permalink
1

In order for Microsoft Systems Center Configuration Manager to provision a vPro system, via bare-metal provisioning, it needs to know its UUID (Also referred to as a GUID), MAC address, short name and FQDN.  This information can be collected into a CSV file and imported into SCCM manually, or automatically by leveraging a script and WMI.  This package will outline the security configuration and point you to resources you can use to create a script to automate this process.  You can get a copy here:

 

Update 6/25/2009:  An updated version of the script is available at the link below.

 

http://communities.intel.com/docs/DOC-3067

1 Comments Permalink
2

This information is based on Microsoft’s beta release of System Center Configuration Manager Service Pack 2 and is subject to change.

Within the SCCM SP2 beta, Microsoft has included support for AMT Audit Log.  Audit Log was introduced in AMT version 4 and provides a mechanism to captures the occurrence of significant AMT events and who performed those actions.

Before you begin, you must configure SCCM SP2 on which AMT Audit Log events it turns on.  This can be done by selecting Out of Band Management properties under "Site Database" -> "Site Management" -> <Site Code> -> "Site Settings" -> "Component Configuration" -> “Audit Setting” Tab.

AuditLog-Settings.jpg

Unlike other AMT feature enablement with SCCM, Audit log is not enabled during Provisioning or through the Update Management Controller process; it must be performed as a post provisioning step.  To enable the AMT Audit log, you must right click on the AMT client and select “Out of Band Management” -> “Enable Auditing and Apply Audit Log Settings”.  You can also disable and clear the audit log from this menu as well.

AuditLog-Enable.jpg

Once enabled on the AMT Client, you can access the AMT Audit Log through the Out of Band Management Console available through right clicking on the AMT client and select “Out of Band Management” -> “Out of Band Management Console”.

AuditLog-OOBC.jpg

--Matt Royer

2 Comments Permalink
0

This information is based on Microsoft’s beta release of System Center Configuration Manager Service Pack 2 and is subject to change.

As noted in one of the previous posts, SCCM SP2 has extended support for AMT / vPro Wireless Out Of Band use cases.  If we open Out of Band Management Component Configuration under "Site Database" -> "Site Management" -> <Site Code> -> "Site Settings" you will notice that there is a new tab for “802.1X & Wireless”.

OOBM-WirelessTab.jpg

When you click the new icon, you will be given the opportunity to create your AMT wireless profile.

OOBM-WirelessTab-New.jpg

There are a couple of interesting things to point out.  First, SCCM SP2 supports AMT wireless security types of WPA-Enterprise and WPA2-Enterprise; WPA-Personal and WPA2-Personal are not supported

OOBM-WirelessTab-SecurityType.jpg

Second, the encryption method can be either TKIP or AES.

OOBM-WirelessTab-EncryptionMethod.jpg

Third, you will notice that 802.1x authentication is required for the wireless connection supporting the Client Authentication methods of EAP-TLS, EAP-TTLS/MSCHAPv2, or PEAPV0/EAP-MSCHAPv2.

OOBM-WirelessTab-ClientAuthentication.jpg

The 802.1x trusted root certificate can be loaded from either a file or pulled directly from your CA infrastructure.

OOBM-WirelessTab-ServerAuthentication.jpg

OOBM-WirelessTab-TrustedRootCertificate.jpg

The Radius Client Certificate (depending on the Authentication method chosen) will allow to you choose a desired certificate template from one of your Microsoft Enterprise Certificate Authorities. 

OOBM-WirelessTab-ClientCertificateTemplate.jpg

OOBM-WirelessTab-RadiusClientCertificate.jpg

Once the wireless settings have been configured in the Out of Band Management Component Configuration, the certificate request will be generated for the AMT client and the wireless settings will be pushed to the AMT client during the initial provisioning or when a “Update Management Controller” is performed on the client.

--Matt Royer

0 Comments Permalink
1

Note: This information is based on Microsoft’s beta release of System Center Configuration Manager Service Pack 2 and is subject to change.

Besides extending ConfigMgr support for new Operating Systems (Windows 7, Windows Server 2008 R2, Windows Server 2008 SP2, Windows Vista Sp2) and Branch Cache (peer to peer content distribution), ConfigMgr SP2 significantly evolves their native support for AMT / vPro use cases and features.  As noted in the SCCM SP2 release notes, extension of the Intel vPro Technology support expands into:

OOB Wireless Management / Wireless Profile Management

·         Provide configuration of up to eight (8) wireless profiles per site that are available to AMT clients assigned to that site

·         Set the wireless information during AMT provisioning and configure all required profile settings (SSID, key management, encryption, etc.)

·         Send wireless profile operations to the Intel translator on AMT systems with revisions earlier than 3.2.1

End Point Access Control / 802.1x support

·         Provision 802.1x settings on AMT wireless clients during AMT provisioning

·         Send 802.1x settings operations to the Intel translator on AMT systems with revisions earlier than 3.2.1

Persistent Data Storage

·         Non Volatile Memory or Third Party Data Store (3PDS)

·         Write string data into 3PDS on AMT through OOB management console

Access Monitor: Audit Log

·         Enable or Disable Audit Log (no critical event settings)

·         View Audit Log through OOB Console

Remote Power Management: Power State Configuration

·         Enable configuration of the power policy settings and include in provisioning settings when provisioning an AMT system

If you are interested in taking a closer look at the SCCM SP2 beta build, you can get access to the download by going to https://connect.microsoft.com and signing up for access.

--Matt Royer

1 Comments Permalink
1

Steve Rachui at Microsoft has put together a great PKI validation script.  The script itself validates PKI in two ways.  First, it can be used to verify third-party remote configuration certificates from the vendors supported by AMT.  Second, the script can verify that your PKI environment is properly configured to support AMT provisioning.  The script itself needs to be run from a server to work correctly.  Check out Steve’s blog to get all the details.

http://blogs.msdn.com/steverac/archive/2009/05/18/tool-to-verify-amt-certificates.aspx

1 Comments Permalink
15

Updated August 2009

 

These instructions are for Windows 7 builds 7077 and beyond.

 

Several Intel based platforms contain Management Engine Interface (MEI) and Serial over LAN (SOL) devices.  Windows 7 drivers for these devices have been made available to OEMs for currently shipping platforms (2008 / 2009 model desktop and mobile PCs).  MEI and SOL Windows 7 driver support for previous generation PCs (2007 desktop and mobile) is planned for early Q1, ’10.

 

To enable Windows 7 testing and evaluation,  prior to driver availability, MEI and SOL Vista drivers, either pre-loaded on your PC or available from the OEM, can be installed on the Windows 7 Release Candidate or RTM OS builds by utilizing Windows 7 compatibility mode.  The following instructions can be used to install the MEI and SOL Vista drivers:

 

 

  1. Locate or download the released MEI and SOL Vista drivers from your OEM
  2. Locate the setup.exe file for the device to be installed
  3. Right click on the setup.exe and select properties
  4. Select the Compatibility tab
  5. In the compatibility mode section check the box “Run the program in compatibility mode for:”
  6. Select the following in the drop down “Windows Vista (Service Pack 2)”
  7. At the bottom of the properties window set the privilege level by checking the box in front of “Run the program as an administrator”
  8. Click Apply
  9. Click OK to exit out of the properties window
  10. Double click on the setup.exe and follow the normal install/setup steps
15 Comments Permalink
3

SCCM allows the right click menu items in the SCCM console to be customized.  We utilized this capability to demonstrate how configuration of custom AMT support could be added to SCCM.  Since SCCM SP1 does not support wireless AMT configuration, we added some basic support for this to the SCCM menu system. 

The attached zip contains files that show how to add right click menu items to Altiris, how to make wireless configuration scripts and how to use both of these capabilities to embed wireless AMT configuration support directly into SCCM. This package is intended as a demonstration only.

This package contains the following components:

1.             Genscript: This utility creates a VB script that pushes wireless profiles, certificates and AMT configuration data to an arbitrary client.  The Genscript utility and user guide are included in this package. The latest version can be found here: http://software.intel.com/en-us/articles/intel-ws-management-translator/.

2.             XML files: For the demonstration, there are two XMLs needed: vpro_client.xml and vpro_colleciton.xml.  One pushes settings to an entire collection and the other pushes settings to a single member. The single member XML file calls push.vbs directly.  The collection XML calls gp_exe.vbs which calls push.vbs on all the collection members.

3.             Wireless configuration script generated by Genscript: This script is executed with the client’s hostname and domain name as command line arguments.  It conducts certificate requests, configures the client with those certificates and configures a wireless AMT profile.  For details on Genscript and how to use it to generate wireless configuration scripts refer.

4.             Push.vbs: This script takes a hostname as a command line argument and calls a wireless configuration script. The name of this script is hard coded in push.vbs along with the domain suffix to use.  For simplicity I hard coded which wireless configuration script to use. By default, this script is hard coded as vpro_config_update.vbs.

5.             Gp_exe.vbs: This script calls push.vbs for all the members of a particular collection. It is based on the sms_ping.vbs script.  It takes the target collection as a command line argument and then calls push.vbs for each hostname.

6.             Add_to_Collection.vbs – This script adds a client instance to a particular collection.  It is used to populate a ‘Push Failed’ collection with client instances for clients that fail a wireless settings push. The collection ID for the destination collection is hard coded in the script.

7.             Delete from Collection.vbs – This script removes client instances from a particular collection. It is used to remove client instances from the ‘Push Failed’ collection when a wireless settings push succeeds for that client.

8.             Clear_collection.vbs – This script clears the contents of a given collection.  It is useful for clearing the ‘Push Failed’ collection.

 



3 Comments Permalink
2

Microsoft has just announced that they are accepting participation nominations for the System Center Configuration Manager SP2 Technology Adoption Program (TAP).  The full announcement can be found here https://connect.microsoft.com/content/content.aspx?ContentID=11121&SiteID=16
(Note: you will need to log into the Microsoft Connect website to view the announcement):

As detailed within the announcement, Microsoft is extending new OS support along with improving on the Intel AMT integration with SCCM SP2.  From the announcement, the key AMT / vPro enhancement are:

·         OOB Wireless Management: Wireless Profile Management

·         End Point Access Control: 802.1x support

·         Persistent Data Storage: Non Volatile Memory or Third Party Data Store (3PDS)

·         Access Monitor: Audit Log

·         Remote Power Management: Power State Configuration

Additional detail on these new features can be referenced in the announcement.

To submit your participation nomination for the SCCM SP2 TAP, you will need to fill out the nomination survey (link located in the Nomination section of the announcement).

--Matt Royer

2 Comments Permalink
0

We have two checklists on the Expert Center to help you plan your vPro and Microsoft SCCM deployments. The Discovery Checklist was just published today. Take a look!

 

Discovery Checklist for Microsoft SCCM

Use this checklist to start gathering the information required for deploying Intel® vPro™ technology in your enterprise.

 

Infrastructure Prep Checklist for Microsoft SCCM

Use this checklist to ensure prerequisites are completed before deploying Intel® vPro™ technology in your enterprise.

0 Comments Permalink
0

Microsoft has just released Hotfix KB960804.  This is a hotfix rollup package that addresses issues that involve the Out of Band Management (OOB) feature in Microsoft System Center Configuration Manager 2007 Service Pack 1 (SP1). These issues are documented in the following Microsoft Knowledge Base articles: (Even if you have all or some of the other Hotfixes installed that are included in this rolled up HotFix, it is recommended that you install KB960804 Roll-up Hotfix)

 

  • 954718: You cannot use the Out of Band Management console in Configuration Manager 2007 to connect to computers that use versions of Intel AMT that are earlier than version 3.2.1
  • 955114: The SMS_Executive service process may crash when the System Center Configuration Manager 2007 SP1 Hierarchy Manager handles the site control (.ct2) file from child sites that are running the RTM version of Configuration Manager 2007
  • 955126: The SMS_Executive service process (Smsexec.exe) in System Center Configuration Manager 2007 may crash if you have Intel AMT-related software installed
  • 955355:  A distinguished name that contains more than 100 characters and that is discovered from Active Directory for an AMT host causes the SMS_EXECUTIVE service to crash in System Center Configuration Manager 2007
  • 956337: System Center Configuration Manager 2007 Service Pack 1 is unable to remove AMT user ACLs during the provisioning process for AMT 2.x computers
  • 957183: You cannot add a group as an AMT user account in Configuration Manager 2007 Service Pack 1 if the group name has more than 20 characters
  • 957469: The Out of Band Power control function does not work for clients that have the Intel AMT 4 or Intel AMT 5 chipset in System Center Configuration Manager 2007 Service Pack 1
  • 959700: The Out of Band Management console in Configuration Manager 2007 Service Pack 1 cannot connect to AMT-enabled computers
  • 960741: The SMS_Executive service process crashes on a Configuration Manager 2007 Service Pack 1 site server when you use Intel WS-MAN Translator to provision computers that are equipped with AMT 3.2.1 chipsets
  • 961328: System Center Configuration Manager 2007 Service Pack 1-based systems cannot provision AMT 2.2/2.6 clients in PKI mode and AMT 2.1/2.5 clients in PSK mode

 

--Matt Royer

0 Comments Permalink
1

Intel® Client Manageability Add-on for Microsoft* SMS 2003 version 5.0.1 has been released.

 

Version 5.0.1 contains the following improvements:

  • Check all IPs for site boundaries
  • Read machines from SCS in chunks of 1000

 

The lastest version of the Add-on can be downloaded here.

 

--Matt Royer

1 Comments Permalink
0

If you want to have the Intel Manageability Tool Kit interoperate with a vPro client that has been provisioned by Microsoft System Center Configuration Manager SP1, there are two key things you need to do: Configure Manageability Commander to trust the Issuing Certificate Authority of AMT Web Certificates and to authenticate with a Kerberos user that has access to the vPro Client.

Before configuring Manageability Commander, you will need to obtain a copy of the Root Certificate Authority Certificate that the vPro Client AMT Web Server Certificate was issued from. This is the same Certificate Authority that was configured in “Microsoft System Center Configuration Manager Console” -> “Out of Band Component Configuration” -> "Site Database" -> "Site Management" -> "Site" -> "Site Settings" -> "Component Configuration" -> "Out of Band Management" -> "General Tab" -> "Certificate Template".
OOBM_Prop.JPG

If you are issuing AMT Web Server Certificates from a subordinate certificate authority, you should still use the certificate from the Root Certificate Authority the SubCA is chained up to.

Cert1.JPG

 

 

Export a copy of the Root CA

1)   To export of a copy of the Root CA Certificate, you can open your local certificate store, select “Trusted Root Certificate” -> “Certificate” and search for the proper Root CA Certificate. If you do not have the Root CA certificate in your trusted root store, your CA Administrator can obtain a copy for you from the CA by selecting the “Properties” of the Certificate Authority and selecting “View Certificate”.

2)   Once you have the certificate open, select the “Detail” tab and then select “Copy to File”.cert2.JPG

3)   When the “Certificate Export Wizard” appears, click “Next”.
export1.JPG

4)   Select “DER encoded binary X.509(.CER)” and click “Next”.
export2.JPG

5)   Select a location to export the certificate to and then click “Next”.
export3.JPG

6)   On the “Complete the Certificate Export Wizard”, click ‘Finish”.
export4.JPG

 

 

Trusting your Root Certificate Authority in Manageability Commander

Now that you have a copy of the Root CA certificate, you are able to configure Manageability Commander so that it can manage a vPro client provisioned by SCCM.

1)   If you have not already done so, you can download a copy of the Manageability Tool Kit from the following location: http://software.intel.com/en-us/articles/download-the-latest-version-of-manageability-developer-tool-kit/. Follow the onscreen instructions on how to install it.

2)   Once Manageability Tool Kit is install and Manageability Commander is open, select “File” -> “Certificate Manager”.
commander1.JPG

3)   In the “Certificate Manager” window, ensure you delete all other existing certificates by highlighting them and clicking the “Delete” button. After which, select “Import”.
commander2.JPG

4)   Browse for the Root Certificate Authority Certificate you exported (which is the Root CA Certificate that is chained up from your AMT Web Server certificates) and click “Open”.
commander3.JPG

5)   Back in the “Certificate Manager” window, click the “Refresh Displayed Certificates” button. You should now see your CA in the “Trusted Root Certificates” list. Click “Close” to exit the Certificate Manager window.
commander4.JPG

 

 

Adding a Client to Manageability Commander

Once the Root CA certificate has been trusted, you can now add the client (that is provisioned by SCCM) you want to manage via Manageability Commander.

1)   To add the vPro client, select “File” -> “Add” -> “Add Intel® AMT Computer”.
commander5.JPG

2)   When the “Add Intel® AMT Computer” window appears, enter in the full qualified domain name (FQDN) of the client you want to manage. If you want Manageability Commander to use Kerberos authentication of the local user logged, leave the Username and Password blank. If you want to specify a different Kerberos user then the local logged on user, enter in the desired Kerberos user as domain\user and the appropriate password. Click “OK” to close the “Add Intel® AMT Computer” window.
commander6.JPG

3)   Once you have added the vPro client, you should see it in the list of clients to manage. Right click on the client, and select “Connect”.
commander7.JPG

4)   Once connected, you can invoke any of the vPro / AMT use cases that the Manageability Commander Tool supports on the client provisioned and also managed by SCCM.
commander8.JPG

 

 

 

 

Debugging Connection

If you are having connection issue, you can perform some general troubleshoot by viewing the debug information.

1)   To view the debug information, select “Help” -> “Show Debug Information...”
debug1.JPG

2)   Once the “Manageability stack” window opens, you can see additional detail of any issues encountered.
debug2.JPG

 

 

 

 

--Matt Royer

0 Comments Permalink
0

 

Microsoft has just released a hotfix to address AMT 4 / AMT 5 power control within System Center Configuration Manager 2007 Service Pack 1.

 

 

 

 

 

System Center Configuration Manager 2007 (KB957469):

 

  • Description: The Out of Band Power control function does not work for clients that have the Intel AMT 4 or Intel AMT 5 chipset in System Center Configuration Manager 2007 Service Pack 1

  • http://support.microsoft.com/kb/957469

 

 

 

 

Please reference the following WIKI for a comprehensive list of required software bundles and hotfixes for SCCM SP1 and vPro/AMT Out of Band Management: http://communities.intel.com/openport/docs/DOC-1897

 

 

 

 

 

 

 

 

--Matt Royer

0 Comments Permalink
0

Use case guides were just published for Microsoft SCCM, as well as the Intel Client Manageability Add-on for Microsoft SMS (formerly known as the Intel AMT Add-on for Microsoft SMS).

 

These guides are often referred to as recipe book or solution guides. They will show you how to set up power on/off, remote diagnosis and repair, and more.

 

Check them out here:

 

Use Case Guide for Microsoft System Center Configuration Manager (SCCM)

 

Use Case Guide: Intel(R) Client Manageability Add-on for Microsoft SMS

0 Comments Permalink
6

Microsoft SCCM 2007 SP1 Intel vPro Training Videos

We’re pleased to announce the availability of Microsoft SCCM 2007 SP1 Intel vPro Training videos. During a recent training event in Redmond, Washington, we had the cameras rolling for this detailed and robust training experience and it is now available for you to experience and utilize.

 

Below is an overview and link for each training section.

 

Introduction

 

Technical overview of Microsoft System Center Configuration Manager 2007 SP1 support of Intel vPro technology with specific focus on supported use cases, provisioning process and infrastructure prerequisites for Intel vPro Out of Band Management.

Lab Module One

 

Configuration steps of Active Directory and PKI infrastructure to support Intel vPro Out of Band Management within Microsoft System Center Configuration Manager 2007 SP1.

Lab Module Two

 

Steps for Microsoft System Center Configuration Manager 2007 SP1 OOB Service Point installation, OOB Component Configuration and Network Discovery for Management Controllers.

Lab Module Three

 

Steps for creating a collection for housing Intel vPro clients and configuring that collection for automatic provisioning of the Out of Band Management Controllers.

Lab Module Four

 

Installation overview for the Microsoft System Center Configuration Manager 2007 SP1 client agent and initiation of Intel vPro client provisioning.

Lab Module Five

 

Technical overview of the Out of Band Management Console, Intel vPro Management Engine Interface and Intel AMT power control via Advertisements.

Lab Module Six

 

Configuration steps of the Intel WS-MAN Translator to support legacy Intel vPro clients (Intel AMT firmware versions less than 3.2.1).

Lab Module Seven

 

Provisioning legacy Intel vPro clients (Intel AMT firmware versions less than 3.2.1) through the Intel WS-MAN Translator using PSK provisioning.

Lab Module Eight

 

Overview of the Intel vPro migration process from the Intel SCS / Microsoft SMS 2003 Add-on to Microsoft System Center Configuration Manager 2007 SP1.

 

Please let us know if you have questions or comments regarding this material.

 

This resource along with other resources on the Intel vPro Expert Center can assist you in answering questions when deploying Intel vPro clients in conjunction with Microsoft System Center Configuration Manager 2007 SP1.

6 Comments Permalink
0

An updated version (release 1.1 - build 552) of the Intel WS-MAN Translator has just been released. Updated features include:

 

  • Provides support for running on 64-bit systems

  • Provides additional translation services for legacy systems such as wireless profiles, and 802.1x.

  • You can upgrade from existing builds by using this VB Script or it can be installed on its own.

 

To download the latest version, please visit: http://software.intel.com/en-us/articles/intel-ws-management-translator

 

 

 

 

 

 

 

 

Upgrading from Intel WS-MAN Translator 1.0 to Intel WS-MAN Translator 1.1 (Build 552)

 

 

To upgrade a previous version of the Intel WS-Man Translator to a newer version, download the Update Translator VBScript and run it in the same folder that the latest Translator MSI is located. This will upgrade your WS-MAN Translator version and keep your previous configuration setting.

 

 

 

Fresh install of the Intel WS-MAN Translator

 

 

 

Generate a Certificate Request on SCCM Server for Intel WS-MAN Translator

 

  1. On the SCCM Server, go to Start &gt; All Programs &gt; Administrative Tools &gt; Internet Information Services (IIS)

  2. Expand Web Sites and Right Click on Default Web Site and select Properties
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1723/GenerateCert1.JPG!*

  3. In the Default Web Site Properties windows Select the Directory Security Tab. In the Secure Communications section, click the Server Certificate button
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1724/GenerateCert2.JPG!

  4. This will launch the Web Server Certificate Wizard. Click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1725/GenerateCert3.JPG!*

  5. In the IIS Certificate Wizard Window, select Create a new certificate . Click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1726/GenerateCert4.JPG!*

  6. Select Send the request immediately to an online certification authority. Click Next
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1727/GenerateCert5.JPG!

  7. Enter a Name for the certificate: WS-MAN Translator Server Certificate. Click Next
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1728/GenerateCert6.JPG!

  8. Enter Organization Information (Organization and Organizational Unit) and Click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1729/GenerateCert7.JPG!*

  9. Enter the Common name: This is the FQDN of your server you are installing the Intel WS-MAN Translator on and should be the same as the FQDN of your SCCM Server. Click Next
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1730/GenerateCert8.JPG!

  10. Enter in your Geographical Information. Click Next
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1731/GenerateCert9.JPG!

  11. Enter 443 for the SSL Port for this web site. Click Next
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1732/GenerateCert10.JPG!

  12. In the Choose a Certification Authority Window, select your issuing Certificate Authority. Click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1733/GenerateCert11.JPG!*

  13. Confirm your request and click Next
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1734/GenerateCert12.JPG!

  14. Once Wizard is complete, click Finished
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1735/GenerateCert13.JPG!*

 

Set Delegation for the SCCM Server

 

  1. On your Domain Infrastructure Image, Click Start &gt; All Programs &gt; Administrator Tools &gt; Active Directory Users and Computers &gt; vprodemo.com &gt; Computers. Right Click on SCCM Server and select Properties.
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/38-11434-1782/Computer.JPG!

  2. Check the box Trust Computer for Delegation and click OK
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/38-11434-1781/delegation.JPG!*
    Note: If you do not allow this, you will need to setup the WS-MAN Translator (during configuration steps) run time account with a user that has permission to the AMT client. At that point the credentials configured in the run time account are used to manage the client for Kerberos authentication.

 

Installing the Intel WS-MAN Translator

 

  1. On the SCCM Server, run the Intel WS-MAN Translator Setup

  2. In the Intel WS-Management Translator setup window, click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1736/Install1.JPG!*

  3. In the Intel WS-Management Translator setup window, click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1737/Install2.JPG!*

  4. During the installation, keep all of the Default settings until installation wizard is complete and install has finished.
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1738/Install3.JPG!
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1740/Install5.JPG!

 

Configuring the Intel WS-MAN Translator

 

  1. Click Start &gt; All Programs &gt; Intel WS-Management Translator &gt; wtranscfg.exe to configure the Translator

  2. In the WS-Translator Configuration Wizard Window, Set common setup accounts, Set TLS/forwarding options, & Set WinRM Options. Click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/38-11641-1935/config1.JPG!*

  3. In the Set initial setup password window, enter the password you configured within SCCM Out of Band Management Properties &gt; Provisioning setting Section &gt; MEBx Account. Click Next
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1719/ConfigTrans2.JPG!*

  4. In the Set Common Pre-Shared Key window, should select a more random and secure PID and PPS for security reasons. Click Next.
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1720/ConfigTrans3.JPG!

  5. In the Import Common Setup Certificate, Click Browse and select the Same Certificate you used in SCCM Out of Band Management Properties &gt; Certificates Section &gt; Provisioning Certificate. Click Next.
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1721/ConfigTrans4.JPG!

  6. In the Select TLS/forwarding options windows, select (default Options): Listening Port: 443 & Forwarding Port: 16993. For the Server Certificate: select the WS-Man Translator certificate created in previous step.
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1722/ConfigTrans5.JPG!

  7. Select Allow Basic Authoziation and Click Finished. Click OK to Restart the Translator Service.
    !http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/38-11641-1936/config2.JPG!

 

Configuring SCCM SP1 to use the Intel WS-MAN Translator

 

  1. Within System Center Configuration Manager Out of Band Management Properties &gt; Provisioning setting Section &gt; AMT Settings. Check the option for Enable support for Intel WS-MAN Translator. Once selected, click Apply.
    *!http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1717/ConfigSCCM1.JPG!*

 

--Matt Royer

0 Comments Permalink
1 2 3 Previous Next