Test Case

Show / Hide direct link   <MAIN> 3632PA: AMT Power control options Test - PP-80503



Version 1.7
Created on 02/03/2007 16:22:13  by Imthias Subaier
Summary
Preconditions
Status:   New
Priority:   Medium
BASIC INFORMATION
Section:S/W Test Require attachment:No
Team:Network Group:Advanced Function
Lessons Learned:No Phase:SIV (BBFV), SIT
Locations:Inhouse: AWS and Cambridge, Inhouse: AWS, Inhouse: Cambridge, Compal, Flextronics, Quanta, Wistron Owned By:Eiji Ogata/LENOVO
Objective:To confirm the reliability of AMT
CRITERIA
Checking remote control by send various power option commands to managed Intel AMT devices. They are grouped under Power options in the Server information console (double-click the device in the My devices list, then click Power options).
Various boot options may be used together. For example, you can do a reboot and enable Serial-over-LAN (SOL) and IDE-Redirection together. Or you can send a power-on command, start SOL, and then enter the BIOS.
EUT QUANTITY
1 system
EQUIPMENT
Network
Critical Attribute:[0] : ETN - Ethernet

CONFIGURATION
REFERENCE PROCEDURE
ME state Text description

M0- All Intel AMT features are functional
M1- Only client initiated features will be functional
M-Off System Defense feature only available when system is plugged into
a power outlet. If the system is not plugged into a power outlet,there will be no Intel AMT functionality

This page determines when the Management engine is powered on. This will help
reduce the power used by the system and conserve battery life. For example if
Mobile: ON is S0 ME WOL in S3, S4-5/AC” is selected the ME will be powered OFF (Moff):
• When the system is powered on and not connected by an AC power source
• When the System is in S4 (Hibernate) or S5 (powered off) and connected by an
AC power source

When the system is in S3 (Standby), the ME will be turned on, but can be turned on
by a WOL (Wake ME on LAN command)

If “Mobile: ON in S0” is selected the ME will only be off when the system is powered
and not plugged into the wall by an AC power source. When the system is in any
other state the ME power states will be determined by the settings inside the MEBX.

A WoL (Wake ME on LAN) option means that the ME will remain in the M-Off state
until a “wake” command is sent through the LAN.
STATISTIC INFO
Operating System Win81-64bit Win81-32bit Win10-32bit Win10-64bit Win7- 64bit Win7- 32bit Total
Test Points
Duration
Workload
# Step actions Win81-64bitWin81-32bitWin10-32bitWin10-64bitWin7- 64bitWin7- 32bit
1 No ME functionality loss after M1->M0 transition AAAAAA
2 ME Power Management Support on AC AAAAAA
3 II-4 Power Transitions AAAAAA
4 Shutdown/Reboot/Wakeup clients using LanDesk Mgmt Suite AAAAAA
5 AMT Remote Boot Manager AAAAAA
DETAILS
ATTENTION!! Please follow below information.
1. Please check Error and Warning message in Event Viewer before you start the test case and after you complete the test case, and report it to your team lead, then arrange to open defect, if needed.

2. Perform All Test in Battery Mode (Some of the test items need to perform in AC Mode, follow each Test Case).

3. All Test Activity should be performed with AMT Enabled as Default (applicable on vPro enabled systems).

4. Please check Usability / Cosmetic issues (correct sentence/appropriate display/etc.) and open defect, if needed.

Known Limitations - UR-2763

Starting from AMT 6.0, we have only 2 power policies in MEBx by Intel design. [ECR09513]

Note:

Only the following 2 power control options will be available starting from AMT 6.0:
a. Mobile:ON in S0
b. Mobile:ON in S0, ME Wake in S3/AC, S4-5/AC






I. No ME functionality loss after M1->M0 transition
a. Put AMT host in S3/M1
b. Return to S0/M0
c. Test that AMT functionality is still available (RCO, HW Asset Inventory,
Event Manager, SOL/IDER over both LAN and WLAN)
d. Repeat with S4 / S5.
II-1 ME Modes
Objective: Verify that the BIOS invokes MEBx regardless the current ME state, either
on normal operation or when ME is temporary disabled.
1. Configure the Intel AMT platform.
2. Make sure MEBx is accessible
3. Enter MEBx and disable ME via the ME Menu-> Intel? ME State Control.
4. Shut down the machine after the changes are applied.
5. Power up the machine and make sure MEBx is accessible.
6. Shut down the machine and take the power cord out, wait 10 seconds and
reconnect the power cable.
7. Power up the machine and make sure MEBx is accessible. Re-enable ME via the
ME Menu->Intel? ME State Control.
II-2 ME Sx mode
Objective: Verify that the Intel AMT platform implements support for the ME power
policy so that the platform can be managed in all supported/specified states.
Intel AMT enables remote management of the platform across all platform power
states (assuming AC is available). The supported power policies can be configured via
MEBx. The following tests verify that remote management is available in all platform
power states.
1. Select the Power Package for continuous ME operation on S3/AC and S4-5/AC
2. For each of the states in the table below, use the WebUI console to remotely
access the Intel AMT platform?s system information. Ensure the console is able to
successfully access the platform in each state.
Platform State Intel AMT State
S0 ? BIOS Setup Functional
S0 ? DOS Functional
S0 ? Windows Functional
S3 ? Standby Functional
S4 ? Hibernation Functional
S5 ? Power Down Functional

Note: to connect thro webui, login to AMT client machine from any remote system using the following URl
https://<machine>:16993 in enterprise mode
http://<machine>:16992 in small business mode
username: admin
password: AMT client password

II.3 ME Power Management Support on AC

1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC and S4-5/AC.
3) Ping AMT through the LAN interface; AMT should send a reply.
4) Move the host to sleep mode (S3).
5) Ping AMT through the LAN interface; AMT should send a reply.
6) Power-Up the host (S0), and move the host to hibernate mode (S4).
7) Ping AMT through the LAN interface; AMT should send a reply.
8) Power-Up the host (S0), and power down the host (S5).
9) Ping AMT through the LAN interface; AMT should send a reply.
10) Remove the machine"s AC connection.
11) Re-connect the machine to AC.
12) Ping AMT through the LAN interface; AMT should send a reply (AMT might
start replying after a few seconds" delay).

II-4 Power Transitions

Mobile : ON in S0
1. Install Intel AMT 6.0 - Management Engine Interface , Local manageability service & SOL driver and restart.
2. Configure AMT device in non-TLS mode.
3. Goto Intel IMEBEx menu ==> Intel ME General Settings ==>Power control ==> Intel ME ON in Host Sleep States
4. Select the option Mobile: ON in S0. Save and boot into OS.
5. Connect AMT system to AC adapter and ping through the LAN / WLAN interface; AMT should send a reply .
6. Move the client to sleep mode (S3). Ping AMT through the LAN interface; AMT should not send a reply.
7. After few seconds resume by pressing Fn key.
8. Move the client to sleep mode (S4). Ping AMT through the LAN interface; AMT should not send a reply.
9. After few seconds resume by power button.

10.Move the client to sleep mode (S5). Ping AMT through the LAN interface; AMT should not send a reply.
11. After few seconds resume by power button.

12.Make sure that no error appears while ping and system boot up.
13. Repeat steps 5 - 12 in DC mode. Result should be same as AC adapter plug in.

Mobile : ON in S0, ME Wake in S3, S4-5 (AC only)
1. Install Intel AMT 6.0 - Management Engine Interface , Local manageability service & SOL driver and restart.
2. Configure AMT device in non-TLS mode.
3. Goto Intel IMEBEx menu ==> Intel ME General Settings ==>Power control ==> Intel ME ON in Host Sleep States
4. Select the option Mobile: ON in S0,ME Wake in S3, S4-5 (AC only). Save and boot into OS.
5. Connect AMT system to AC adapter and ping through the LAN / WLAN interface; AMT should send a reply .
6. Move the client to sleep mode (S3). Ping AMT through the LAN interface; AMT should send a reply.
7. After few seconds resume by pressing Fn key.
8. Move the client to sleep mode (S4). Ping AMT through the LAN interface; AMT should send a reply.
9. After few seconds resume by power button.

10.Move the client to sleep mode (S5). Ping AMT through the LAN interface; AMT should send a reply.
11. After few seconds resume by power button.

12.Make sure that no error appears while ping and system boot up.
13. Repeat steps 5 - 12 in DC mode. AMT should send a reply in S0 mode but should not reply in S3/S4/S5 state.


Shutdown/Reboot/Wakeup clients using LanDesk Mgmt Suite

Step 1:Remote shutdown
  1. Click Start | Programs | LANDesk | LANDesk Management Suite.
  2. Right click on the target device.
  3. Select Shut Down.
  4. Confirm that the client system shuts down

Step 2:Remote reboot
  1. Click Start | Programs | LANDesk | LANDesk Management Suite.
  2. Right click on the target device.
  3. Select Reboot.
  4. Confirm that the client system reboots

Step 3:Remote wakeup
  1. Comfirm that the client machine supports the WON(Wake On LAN).
  2. Click Start | Programs | LANDesk | LANDesk Management Suite.
  3. Right click on the target device.
  4. Select Wakeup.
  5. Confirm that the client system wakes up


AMT Remote Boot Manager
Step 1:Bring up Remote Boot Manager
  1. LANDesk Management Suite | Right-click the device | Intel vPro Options | Intel vPro Remote Boot Manager.

Step 2:Normal operation
  1. In the Remote Boot Manager select Power off and Normal boot. Then hit Send. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)
  2. In the Remote Boot Manager select Power on. Then hit Send.
  3. In the Remote Boot Manager select Reboot and Normal boot. Then hit Send. The client machine will reboot immediately. (No warning messages will be displayed on the client.)
Step 3:Reboot with IDE-R
IDE Redirection allows an administrator to reboot a client using a device or image that is not located on the client device. This allows the administrator the flexibility to have diagnostic and repair images located in a folder on the management console or a shared folder on the network. From the management console the administrator can reboot the client and redirect the boot process to one of these remote images. The client will boot from this remote image and allow the administrator to remote diagnose and fix the system problem on the client.
  1. In the Remote Boot Manager select Reboot, IDE-R boot, Boot Device (CD or Floppy or image), and the location of the boot image (physical console drive or .iso file and location). Then hit Send. (No warning messages will be displayed on the client.)
  2. In the Remote Boot Manager select Reboot, IDE-R boot, Enable Console Redirection, Select ANSI or VT100, Boot Device (CD or Floppy or image), and the location of the boot image (physical console drive or .iso file and location). Then hit Send. (No warning messages will be displayed on the client.)

Step 4:Reboot into BIOS
This option allows an administrator to remotely reboot a client and enter the BIOS over a Serial-Over-LAN connect to make and save changes to the client BIOS.
  1. In the Remote Boot Manager select Reboot, Normal Boot and Enter BIOS setup option on power on. Then hit Send. (No warning messages will be displayed on the client.)
  2. In the Remote Boot Manager select Reboot, Normal Boot, Enter BIOS setup option on power on, and Enable Console Redirection. Then hit Send. (No warning messages will be displayed on the client.)

Step 5:Try other options
  1. Try other options as you wish


AMT Web Page Remote Control
  1. Launch the AMT Webpage by http://<Machine>:16992 for Small Business Mode and https://<Machinet>:16993 for Enterprise Mode
  2. Go to Remote Control and select Turn Power off. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)
  3. Select Cycle Power off and on. Try all the boot options. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)
  4. Select Reset. Try all the boot options. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)

Check the following options through Wireless using Remote Boot Manager [UR-1918DS]

Check the functionality of Shutdown, Reboot, SOL/IDE-R boot and Boot from CD-ROM with AMT Remote boot Manager using wireless in addition to wired





I. No ME functionality loss after M1->M0 transition
a. Put AMT host in S3/M1
b. Return to S0/M0
c. Test that AMT functionality is still available (RCO, HW Asset Inventory,
Event Manager, SOL/IDER over both LAN and WLAN)
d. Repeat with S4 / S5.
II-1 ME Modes
Objective: Verify that the BIOS invokes MEBx regardless the current ME state, either
on normal operation or when ME is temporary disabled.
1. Configure the Intel AMT platform.
2. Make sure MEBx is accessible
3. Enter MEBx and disable ME via the ME Menu-> Intel? ME State Control.
4. Shut down the machine after the changes are applied.
5. Power up the machine and make sure MEBx is accessible.
6. Shut down the machine and take the power cord out, wait 10 seconds and
reconnect the power cable.
7. Power up the machine and make sure MEBx is accessible. Re-enable ME via the
ME Menu->Intel? ME State Control.
II-2 ME Sx mode
Objective: Verify that the Intel AMT platform implements support for the ME power
policy so that the platform can be managed in all supported/specified states.
Intel AMT enables remote management of the platform across all platform power
states (assuming AC is available). The supported power policies can be configured via
MEBx. The following tests verify that remote management is available in all platform
power states.
1. Select the Power Package for continuous ME operation on S3/AC and S4-5/AC
2. For each of the states in the table below, use the WebUI console to remotely
access the Intel AMT platform?s system information. Ensure the console is able to
successfully access the platform in each state.
Platform State Intel AMT State
S0 ? BIOS Setup Functional
S0 ? DOS Functional
S0 ? Windows Functional
S3 ? Standby Functional
S4 ? Hibernation Functional
S5 ? Power Down Functional

Note: to connect thro webui, login to AMT client machine from any remote system using the following URl
https://<machine>:16993 in enterprise mode
http://<machine>:16992 in small business mode
username: admin
password: AMT client password

II.3 ME Power Management Support on AC

1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC and S4-5/AC.
3) Ping AMT through the LAN interface; AMT should send a reply.
4) Move the host to sleep mode (S3).
5) Ping AMT through the LAN interface; AMT should send a reply.
6) Power-Up the host (S0), and move the host to hibernate mode (S4).
7) Ping AMT through the LAN interface; AMT should send a reply.
8) Power-Up the host (S0), and power down the host (S5).
9) Ping AMT through the LAN interface; AMT should send a reply.
10) Remove the machine"s AC connection.
11) Re-connect the machine to AC.
12) Ping AMT through the LAN interface; AMT should send a reply (AMT might
start replying after a few seconds" delay).

II-4 Power Transitions

G3/MOff to S0/M0:
1) Make sure that host is off (S5) and machine is running on DC power (battery),
i.e. NOT connected to AC power.
2) Power up host (S0).
3) Start pinging AMT. After a few seconds, AMT should start replying.

S3/MOff to S0/M0:
1) Make sure that host is in sleep mode (S3) and machine is running on DC power
(battery), i.e. NOT connected to AC power.
2) Power up host (S0).
3) Start pinging AMT. After a few seconds, AMT should start replying.

S3/MOff to S3/M1:
1) Make sure that host is on (S0) and machine is running on DC power (battery),
i.e. NOT connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC.
3) Ping AMT using the LAN interface; AMT should send a reply.
4) Move machine to sleep state (S3).
5) Ping AMT using the LAN interface; AMT should NOT reply.

6) Connect machine to AC.
7) Ping AMT using the LAN interface; AMT should reply (might take several
seconds).
S3/M1 to S3/MOff:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC.
3) Ping AMT using the LAN interface; AMT should send a reply.
4) Move machine to sleep state (S3).
5) Ping AMT using the LAN interface; AMT should send a reply.
6) Remove machine"s AC connection.
7) Ping AMT using the LAN interface; AMT should NOT reply.

S4,5/MOff (with WOL) to M0:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for ME operation on
S0 only.
3) Ping AMT using the LAN interface; AMT should send a reply.
4) Enable Host Wake on LAN.
5) Move the host to Hibernation (S4).
6) Ping AMT using the LAN interface; AMT should NOT reply.
7) Power-Up host using a magic packet.
8) Ping AMT using the LAN interface; AMT should send a reply (might take several
seconds).
9) Make sure again the Host Wake On LAN is enabled.
10) Power down the host (S5).
11) Repeat steps 6-8.

S4,5/MOff (w/o WOL) to M0:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for ME operation on
S0 only.
3) Ping AMT using the LAN interface; AMT should send a reply.
4) Make sure that Host Wake on LAN is not enabled.
5) Move the host to Hibernation (S4).
6) Ping AMT using the LAN interface; AMT should NOT reply.
7) Power-Up host using the power-button.
8) Ping AMT using the LAN interface; AMT should send a reply (might take several
seconds).
9) Power down the host (S5).
10) Repeat steps 6-8.

S4,5/MOff (with WOL) to S4,5/M1:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for ME WoL on
S3/AC and S4-5/AC. If package doesn"t exist, consider the test as passed.
3) Ping AMT using the LAN interface; AMT should send a reply.
4) Using the web interface, configure the idle wake timeout to 1 minute.
5) Move the host to Hibernation (S4).
6) Wait for 3 minutes.
7) Ping AMT using the LAN interface; AMT should send a reply (first ping might be
missed).
8) Power up the host (S0).
9) Power down the host (S5).
10) Repeat steps 6-7.

S4,5/MOff (w/o WOL) to S4,5/M1:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for ICC on S3/AC
and S4-5/AC. If package doesn"t exist, consider the test as passed.
3) Ping AMT using the LAN interface; AMT should send a reply.
4) Using the web interface, configure the idle wake timeout to 1 minute.
5) Using the web interface, configure the sleep timeout to 1 minute.
6) Move the host to Hibernation (S4).
7) Wait 3 minutes.
8) Start pinging AMT. Within a couple of minutes, AMT should start replying.
9) Power up the host (S0).
10) Power down the host (S5).
11) Repeat steps 7-8.

S0/M0 to S3/MOff:
1) Make sure that host is on (S0) and machine is running on DC power (battery),
i.e. NOT connected to AC power.
2) Ping AMT using the LAN interface; AMT should send a reply.
3) Move machine to sleep state (S3).
4) Ping AMT using the LAN interface; AMT should NOT reply.

S0/M0 to S3/M1:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC and S4-5/AC.
3) Ping AMT; AMT should send a reply.
4) Move the host to Sleep state (S3).
5) Ping AMT; AMT should send a reply.

S0/M0 to S4,5/M1:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC and S4-5/AC.
3) Ping AMT; AMT should send a reply.
4) Move the host to Hibernate state (S4).
5) Ping AMT; AMT should send a reply.
6) Power up the host (S0).
7) Power down the host (S5).
8) Ping AMT; AMT should send a reply.

S0/M0 to S4,5/MOff (with WOL):
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S0 only.
3) Ping AMT; AMT should send a reply.
4) Enable Host Wake On LAN.
5) Move the host to Hibernate state (S4).
6) Ping AMT; AMT should NOT reply.
7) Wake the host using a magic packet.
8) Ping AMT; AMT should send a reply (might take several seconds).
9) make sure that How Wake ON LAN is enabled.
10) Power down the host (S5).
11) Repeat steps 6-7.

S0/M0 to S4,5/MOff (w/o WOL):
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S0 only.
3) Ping AMT; AMT should send a reply.
4) Make sure Host Wake ON LAN is not enabled.
5) Move the host to Hibernate state (S4).
6) Ping AMT; AMT should NOT reply.
7) Wake the host using the power button.
8) Ping AMT; AMT should send a reply (might take several seconds).
9) make sure that How Wake ON LAN is not enabled.
10) Power down the host (S5).
11) Ping AMT; AMT should NOT reply..

Sx/M1 to S0/M0:
1) Make sure that host is on (S0) and machine is connected to AC power.
2) Through MEBx or web interface, select the Power Package for continuous ME
operation on S3/AC and S4-5/AC.
3) Ping AMT; AMT should send a reply.
4) Move the host to Hibernate state (S4).
5) Power up the host (S0).
6) Ping AMT; AMT shoud send a reply (might take several seconds).
7) Power down the host (S5).
8) Power up the host (S0).
8) Ping AMT; AMT should send a reply (might take several seconds).
S4,5/M1 to S4,5/MOff with WOL:
Coverd by S0/M0 to S4,5/Moff with WOL case.
S4,5/M1 to S4,5/MOff w/o WOL:
Coverd by S0/M0 to S4,5/Moff w/o WOL case.



Shutdown/Reboot/Wakeup clients using LanDesk Mgmt Suite

Step 1:Remote shutdown
  1. Click Start | Programs | LANDesk | LANDesk Management Suite.
  2. Right click on the target device.
  3. Select Shut Down.
  4. Confirm that the warning message will be appeared on the client.

Step 2:Remote reboot
  1. Click Start | Programs | LANDesk | LANDesk Management Suite.
  2. Right click on the target device.
  3. Select Reboot.
  4. Comfirm that the warning message will be appeared on the client.

Step 3:Remote wakeup
  1. Comfirm that the client machine supports the WON(Wake On LAN).
  2. Click Start | Programs | LANDesk | LANDesk Management Suite.
  3. Right click on the target device.
  4. Select Wakeup.


AMT Remote Boot Manager
Step 1:Bring up Remote Boot Manager
  1. LANDesk Management Suite | Right-click the device | Intel vPro Options | Intel vPro Remote Boot Manager.

Step 2:Normal operation
  1. In the Remote Boot Manager select Power off and Normal boot. Then hit Send. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)
  2. In the Remote Boot Manager select Power on. Then hit Send.
  3. In the Remote Boot Manager select Reboot and Normal boot. Then hit Send. The client machine will reboot immediately. (No warning messages will be displayed on the client.)
Step 3:Reboot with IDE-R
IDE Redirection allows an administrator to reboot a client using a device or image that is not located on the client device. This allows the administrator the flexibility to have diagnostic and repair images located in a folder on the management console or a shared folder on the network. From the management console the administrator can reboot the client and redirect the boot process to one of these remote images. The client will boot from this remote image and allow the administrator to remote diagnose and fix the system problem on the client.
  1. In the Remote Boot Manager select Reboot, IDE-R boot, Boot Device (CD or Floppy or image), and the location of the boot image (physical console drive or .iso file and location). Then hit Send. (No warning messages will be displayed on the client.)
  2. In the Remote Boot Manager select Reboot, IDE-R boot, Enable Console Redirection, Select ANSI or VT100, Boot Device (CD or Floppy or image), and the location of the boot image (physical console drive or .iso file and location). Then hit Send. (No warning messages will be displayed on the client.)

Step 4:Reboot into BIOS
This option allows an administrator to remotely reboot a client and enter the BIOS over a Serial-Over-LAN connect to make and save changes to the client BIOS.
  1. In the Remote Boot Manager select Reboot, Normal Boot and Enter BIOS setup option on power on. Then hit Send. (No warning messages will be displayed on the client.)
  2. In the Remote Boot Manager select Reboot, Normal Boot, Enter BIOS setup option on power on, and Enable Console Redirection. Then hit Send. (No warning messages will be displayed on the client.)

Step 5:Try other options
  1. Try other options as you wish


AMT Web Page Remote Control
  1. Launch the AMT Webpage by http://<Machine>:16992 for Small Business Mode and https://<Machinet>:16993 for Enterprise Mode
  2. Go to Remote Control and select Turn Power off. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)
  3. Select Cycle Power off and on. Try all the boot options. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)
  4. Select Reset. Try all the boot options. The client machine will shutdown immediately. (No warning messages will be displayed on the client.)

Check the following options through Wireless using Remote Boot Manager [UR-1918DS]

Check the functionality of Shutdown, Reboot, SOL/IDE-R boot and Boot from CD-ROM with AMT Remote boot Manager using wireless in addition to wired

AMT inventory summary using wireless [UR-1919DS]

Open the inventory summary

1. Open the LSM console (Start | All Programs | LANDesk | LANDesk System Manager). Double-click the AMT device in the My devices list, then click System information | AMT | Intel AMT options.


NOTE:
1. When you open the Inventory summary window, the data is queried real-time from the device, not read from the database, so the dialog may take a moment to display.
2. A good method to determine whether a device is configured in TLS or non-TLS mode is to open the inventory summary and verify the protocol type ? HTTP for non-TLS mode and HTTPS for TLS mode.
3. If you there is no entry in Inventory summary like this, you can update invenroty by next steps.


Updating the Intel AMT inventory
In LSM and LDSM you can manually update the Intel AMT inventory data that is stored in the database.

2. In LSM console, double-click the AMT device in the My devices list, then click System information | AMT | Intel AMT options | Update inventory. (In the LDMS Win32 console you can select multiple devices and update all of their inventories at the same time.)

NOTE: If you install the LANDesk agent on a device and the IP address of the device changes (for example, because DHCP gave it a new address or the device was moved to a different subnet), the Inventory scanner will automatically update the IP address in the database on the next inventory scan. However, if you do not have the agent installed, the only way to update the IP address in the database is to run this Update Inventory operation.

Updating the Intel AMT inventory through Wireless

Configure the client system through wireless and check the function

In LSM and LDSM you can manually update the Intel AMT inventory data that is stored in the database.

2. In LSM console, double-click the AMT device in the My devices list, then click System information | AMT | Intel AMT options | Update inventory. (In the LDMS Win32 console you can select multiple devices and update all of their inventories at the same time.)

NOTE: If you install the LANDesk agent on a device and the IP address of the device changes (for example, because DHCP gave it a new address or the device was moved to a different subnet), the Inventory scanner will automatically update the IP address in the database on the next inventory scan. However, if you do not have the agent installed, the only way to update the IP address in the database is to run this Update Inventory operation.

To Confirm the AMT Logs are generated

View the Intel AMT log page

1. Open the LSM console (Start | All Programs | LANDesk | LANDesk System Manager). Double-click the AMT device in the My devices list, then click System information | Logs | Intel AMT log.
NOTE: The log can be cleared, refreshed, and exported to a CSV file.



OTHER DETAILS
EUT Quantity : 1 system 1. "Please check Error and Warning message in Event Viewer before you start the test case and after you complete the test case, and report it to your team lead."
2. "Perform All Test in Battery Mode (Some of the test items need to perform in AC Mode, follow each Test Case)"
(All Test Activity should be performed with AMT Enabled)
Test Item
Win XP
Vista
Win-7
No ME functionality loss after M1->M0 transition
ME Power Management Support on AC
II-4 Power Transitions
Shutdown/Reboot/Wakeup clients using LanDesk Mgmt Suite
AMT Remote Boot Manager

TEMS Reviewer Log:03/05/2007 10:29:45 AM by Kazuo 1 Matsumoto/Japan/Lenovo/IDE (Review Comment: OK
Review Logs
Keywords:   None
Requirements :   None
Attached files :

Update History:
This document is not yet modified.