Test Case

Show / Hide direct link   <MAIN> 4509PA: Intel AMT 8.0 verification with LANDESK 9.0 - PP-80452



Version 1
Created on 25/10/2011 17:05:09  by PSI_PA_NW_Japan
Summary
Preconditions
Status:   New
Priority:   Medium
BASIC INFORMATION
Section:S/W Test Require attachment:No
Team:Network Group:Basic Function
Lessons Learned:No Phase:FVT, SIV (BBFV), SIT
Locations:Inhouse: AWS and Cambridge, Inhouse: AWS, Inhouse: Cambridge, Compal, Flextronics, Quanta, Wistron Owned By:Eiji Ogata/LENOVO
Objective:To verify all the AMT functions using LANDesk application
CRITERIA
All AMT functions to work correctly as per the criteria mentioned in the Detail section
EUT QUANTITY
Two systems
EQUIPMENT
PA Networking facilities and Intel LANDesk server.
Critical Attribute:[0] : WLS - Wireless

CONFIGURATION
REFERENCE PROCEDURE
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 AMT 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.

Intel AMT 8.0 verification with LANDESK 9.0
Test Item
Check Item / Criteria / Information
Configuration
Result
Win XP
Win 7
Win 8
MEBx configuration (Simple configuration)

1. On the Intel AMT device, start the ME BIOS (press Ctrl-P at the device boot). Enter default password ?admin? and change the MEBx password to ?iAMT-8.0? so that everyone can share the same password for our test.
2. Select Intel(R) AMT Configuration -> Manageability Feature Selection and choose Enabled.
3. If the device has been previously managed or its previous state is unknown, then fully un-provision it by selecting Unconfigure Network Access -> Full Unprovision
4. Select Network Setup -> Intel(R) ME Network Name Settings -> Host Name and input a same name as a computer OS host name. Enter vprodemo.com in the Domain Name field
5. Make sure in TCP/IP Settings -> Wired LAN IPV4 Configuration -> DHCP Mode is Enabled.
6. Ensure that following is selected as the Intel AMT Configuration -> SOL/IDER/KVM. Choose the Save and Exit option in the AMT BIOS.
- Username & Password ENABLED
- SOL ENABLED
- IDE ENABLED
7.Connect the system to a network, and select Activate Network Access.
8.Exit MEBx and boot to the system
  • Check if the MEBx password has been reset successfully
  • Check if un-provision is done successfully if the system has been configured before.
  • Check if the Network settings are saved properly.
Standalone
A
A
A
LANDESK 9.0 Configuration
1.In the LANDESK server Launch the LDMS Console
2.Select Cofiture -> Intel vPro options -> General Configuration..., in the Password field, enter the MEBx password (e.g. iAMT-8.0) and click OK
3.Select Tools -> Configuration -> Unmanaged Device Discovery, notie that the Unamanged Device Discovey panel appear at the bottom.
4.Click on Scan network, Click on New configuration -> More and ensure that Discover Intel vPro AMT devices is checked.
5.Enter IP address of the AMT device in Starting IP and Ending IP, then input 255.255.255.0 as Subnet Mask.Click Add button, and click Scan now.
6.After network scanning is done, Close the scanning windows.
7.At the right portion of the Unmanaged device Discovery window, go to Intel Vpro list, check if the client system is detected and listed.
8.Right click on the device found and select Move to Inventory Database
9.Wait for a while, make sure the client AMT is moved to the LANDESK database.
  • Check if AMT client machine is detected
  • Check if AMT client is moved to Intel vPro inventory list successfully
  • No warning messages should be displayed on the client.
A
A
A
LANDESK 9.0 Intel vpro Device Management
Remote Control via Intel KVM
1. Launch LANDESK 9.0 Management Console, go to Configure -> Intel vPro options -> KVM Configuration, confirm Enable KVM function is enabled.
2. In the inventory database, right-click the AMT client, select -> Intel vPro KVM -> User Consent -> Enable User Consent and then click OK.
3. Right click on the AMT client and select Remote conrol via Intel KVM.
4. KVM session should start successfully.


Intel vPro Options (Remote Boot Manager)
1. Right-click on the AMTdevice -> Intel vPro Options -> Intel vPro Remote Boot Manager.
2. In the Remote Boot Manager select Power off and Power on. Then hit Send. The client machine will shutdown immediately.
- In the Remote Boot Manager select Power on. Then hit Send.
- In the Remote Boot Manager select Reboot and Power on Then hit Send. The client machine will reboot immediately.
3.Normal boot - allows administrator to boot with the BIOS setting.
4.IDE-R boot 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.
a. 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.)
b. 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.)
4. Verify the function of Boot from CD/DVD and Boot from local hard drive
  • No warning messages should be displayed on the client.
  • Confirm Passcode is prompted in the AMT client after initiating a KVM session
  • No error message should appear when passcode is entered
  • Correct and complete information should be displayed.



  • Confirm Boot from CD/DVD and Boot from local hard drive will boot regardless of the booting sequence set in the BIOS.
A
A
A
Intel vPro Change Password
1. Right-click on the AMTdevice -> Intel vPro Options -> Intel vPro Change Pssword
2. Enter the new passwod, confirm new password and click OK
3. Launch web browser and type in the WebGUI URL (http://<ip>:16992), try to log in with the new password
Note: The vPro password here refers to the AMT network access password.
  • Intel vPro Password should be changed successfully
A
A
A
Intel vPro Wireless Profiles
1.Right-click on the AMT client -> Intel vPro Wireless Profiles
2.Verify the following buttons funcion properly:
- Create Profile - create a wireless profile
- Modify Profile - modefy profile settings
- Set Profile - apply a wireless profile to a managed device
-
  • Check if wireless profiles are created and saved successfully
  • Check if a wireless pofile is deployed when click Set Profile.
Note: to test vPro Wireless Profiles, AMT client Wireless should be enabled in the WebGUI
A
A
A
LANDESK 9.0 Agents Installation / Uninstallation
  • Create an agent configuration
1.Launch LANDesk Management Suite console, click Tools -> Configuration -> Agent configuration.
2.In the Agent Configuration menu, goto Public configurations -> Default Windows Configuration
3.Double click Default Windows Configuration
7.Check Default Configuration and click Save
  • Install Agent
1. From the client machine, locate and run %server%\\IDLOGON\WSCFG32.EXE.
2. On the Agent Configuration Utility window, confirm the follwing components are turned on, then click Install
/font>
3. After agent installation done, reboot the system
4. At the LDMS Console main window, select Network View -> LDMS-SERVERNAME -> Devices -> All devices and select AMT client machine,
5. Right click on the AMT client device and select Properties -> Agents tab, confim the following Components are Loaded
Common Base Agent status
Real-time inventory and monitoring
Remote control Agent status
  • Uninstall Agent
1. From the client machine, locate and run%server5\\IDMAIN\Uninstallwinclient.exe and reboot the system
2. At the LDMS Console main window, select Network View -> LDMS-SERVERNAME -> Devices -> All devices and select AMT client machine,
5. Right click on the AMT client device and select Properties -> Agents tab, confim Common Base Agent status, Real-time inventory monitoring and Remote control Agent status are not available
  • Check if Default Configuration is set successfully.









  • Check if Agent installer is launched successfully
  • Check if Agent components are loaded successfullly
A
A
A
LANDESK 9.0 Agent Real-time inventory and monitoring

1. Launch Agent installer
2. On the Agent Configuration Utility window, confirm Real-time Inventory and Monitoring is checked, then click Install

3. After agent installation doen, reboot the system
4. AT the LDMS console select the AMT client device
5. Right click on the client and select Real-time inventory and monitoring
6. The Real-time Inventory and monitoring web console will be launched

7. Confirm all the menus are functioning properly
  • System information
  • Remote session
  • Monitoring
  • Rulesets
  • Power options
LANDESK 9.0 Agent Remote Control
1. Rright-click on the AMT client and select -> Remote Contorl -> Remote Control
2. Confirm the remote desktop control window appears and user is able to do remote control of the system
3. Confirm all the Remote Control functions are working properly:
Remote Control
- Remotely view and control a device

Chat - Remotely chat with a user at a remote device
File Transer - Remotely tranfer files
Reboot - remotely reboot a device
Draw - Displays drawing on the remote screen
  • Comfirm Remote Control options are enabled after agent installation.
  • Confirm all remote control options are working properly.
A
A
A
LANDESK 9.0 Agent Presense Verification
1. In the LANDESK inventory database, select the AMT client
2. Go to Configure -> Intel vPro options -> Agent Presence
3. Set the Heartbeat times to 30 seconds and the Startup times to 60 seconds, then click Apply.
4. On the AMT client device, open Services Manager (Run services.msc) and Stop the LANDesk Mangement Agent service.
5. In a few munites, LANDesk Management Anget service will start automatically or you can start yourself.
6. On the LDMS Console, Select Tools -> Reporting / Monitoring -> Logs Confirm that the Agent Presence alerts are appeared.
7. Repeat Step 1-6 with wireless network.
  • No warning messages should be displayed on the client.
A
A
A
MEBx configuration (Simple configuration)Provisioning using USB Key in Intel AMT Client Device

1. On the Intel AMT system, Press F1 during boot up to go to BIOS Setup
2. Log in AMT client machine MEBx, select Unconfigure Network Access -> Full unprovision
3. In the LANDESK server Launch the LDMS console
4..Select Cofiture -> Intel vPro options -> General Configuration..., in the Password field, enter the MEBx password (e.g. iAMT-8.0) and click OK
5. Launch LANDESK Management Console, Click Configure -> AMT -> Intel vPro options -> ID Genration, and generate one or more PID/PPS pairs. When they are generated, print the list of key pairs for use in setting up the device.

6. In the AMT client MEBx, go to Intel AMT Configuration -> Remote Setup and Configuration -> TLS PSK
7. Select Delete PID and PPS** (make sure there"s no existing PID/PPS)
8. Select Set PID and PPS and ente the IDs generated in LANDESK in step 5
9. Enter Provisioning Server FQDN
10. Ensure that following is selected as the SOL/IDE-R.
- Username & Password ENABLED
- SOL ENABLED
- IDE Redirection ENABLED
11. Go to Password Policy. Try Selecting all the options available. Default Password only, During Setup and Configuration and Anytime. Make sure all the 3 functions are working correctly
12. Go to Secure Firmware Update. Make sure its Enabled.
  • Confirm No error messages displayed on the client.
A
A
A
Export PID/PPS verification
Export PIDs in Local Disk
1. In the LDMS Console, click Configure->Intel vPro options -> ID Generation
2. Select "Export AMT IDs to setup.bin file (0 out of 12 IDs are available for export)"
3. In Specify Intel vPro ME password (AMT v2.5 or greater), type password similar to ME password set in ME BIOS. (Optional)
4. Type Number of IDs to export.
5. Specify the location for setup.bin by clicking Browse button.
6. Save it to local disk.
7. Click Apply button.
8. Import/Export vPro IDs window will show message: "Setup.bin was successfully created."
9. Click OK.


Export PIDs in USB key
1. In the LDMS Console, click Configure->Intel vPro options -> ID Generation
2. Select "Export AMT IDs to setup.bin file (0 out of 12 IDs are available for export)"
3. In Specify Intel vPro ME password (AMT v2.5 or greater), type password similar to ME password set in ME BIOS. (Optional)
4. Type Number of IDs to export.
5. Specify the location for setup.bin by clicking Browse button.
6. Save it to USB key drive.
7. Click Apply button.
8. Message will prompt: "You specified <number> IDs to export from the management database. 0 IDs are currently available. Do you want to generate the additional <number> IDs needed before exporting?"
9. Click Yes
10. Import/Export vPro IDs window will show message: "Setup.bin was successfully created."
11. Click OK and Close.
12. On Generate Intel vPro AMT IDs window > View batch IDs drop down box, select "fromUSB"
13. PIDs should be listed with "fromUSB" Batch names.

















  • Confirm if setup.bin file is created in USB key drive.













A
A
A
1. At core, open command prompt
2. Goto ldmain folder
3. Type, getamtid


4. At core, open command prompt
5. Goto ldmain folder
6. Type, amtusbfile -dv
Note:
Core folder path is:
Documents and Settings\ITproadmin\My Document\File Share\LANDESK9.0\LD9.0-SP2-Coe\image
  • Confirm that the content of pid/psk is the same as when typing amtusbfile -dv
  • Confirm if the file setup.bin(saved at ldmain by default) has the same number of pid/psk as in DB
A
A
A
Import PIDs verification
Import PIDs from Local Disk
1. In the LDMS Console, click Configure->Intel vPro options -> ID Generation
2. Select "Import from USB key file"
3. Specify the location for setup.bin by clicking Browse button.
4. Locate setup.bin file from Local Disk.
5. Click OK and Apply button.
6. Message should appear: "The import was successful."
7. Click OK
8. Go back to Generate Intel vPro AMT IDs window.
9. View Batch IDs
10. PIDs and PPS imported from Local Disk will be viewed.

Import PIDs from USB key
1. In the LDMS Console, click Configure->Intel vPro options -> ID Generation
2. Select "Import from USB key file"
3. Specify the location for setup.bin by clicking Browse button.
4. Locate USB key drive and setup.bin file.
5. Click OK and Apply button.
6. Message should appear: "The import was successful."
7. Click OK
8. Go back to Generate Intel vPro AMT IDs window.
9. View Batch IDs
10. Select "fromUSB"
11. PIDs and PPS imported from USB key will be viewed.
  • Confirm the setup.bin file imported from Local Disk is viewed in Generate Intel vPro AMT IDs window












  • Confirm if setup.bin file created in USB key drive.
A
A
A
1. Plug in usb drive to AMT machine
2. Unprovision AMT(switch jumper)
3. Switch jumper back to normal, reboot AMT
4. After AMT booted up, reboot again, and then go to the MEBx
5..Set up the correct password, then you will also fill in Computer Name, TCP/IP configuration, Provisioning server, SOL/IDER configuration
7. Go back to core, click on, Device discovery\Intel AMT,
  • Confirm the AMT machine appears here
  • A
    A
    A
    1. Plug in usb drive to AMT machine(C1)
    2. Unprovision AMT(switch jumper)
    3. Switch jumper back to normal, reboot AMT
    4. After AMT booted up, reboot again, and then go to the MEBx
    5. Fill in the correct password, then you will also fill in Computer Name, set AMT to AMT/Enterprise mode, TCP/IP configuration, Provisioning server, SOL/IDER configuration
    6. Go back to core, open DB\UNMANAGEDNODES
    • Verify that there is a record for your amt machine at this table.
    A
    A
    A
    1. Plug in usb drive to AMT machine(C1)
    2. Unprovision AMT(switch jumper)
    3. Switch jumper back to normal, reboot AMT
    4. After AMT booted up, reboot again, and then go to the MEBx
    5. At bios, go to Intel(R) ME
    6. Gill in the correct password, then you will also fill in Computer Name, set AMT to AMT/Enterprise mode, TCP/IP configuration, Provisioning server, SOL/IDER configuration
  • Verify that you do NOT need to fill in PID/PSK. There is no where to find pid/psk to type in.
  • A
    A
    A
    1. Plug in usb drive to AMT machine(C1)
    2- Unprovision AMT(switch jumper)
    3. Switch jumper back to normal, reboot AMT
    4. After AMT booted up, reboot again, during reboot, press F2 to go in to BIOS
    5. At bios, go to Intel(R) ME
  • Verify if you can type in with the same password as the core has(Landesk configure services\intel AMT configuration)
  • A
    A
    A
    Provisioning using USB Key in Intel AMT Client Device
    1. Export PIDs to USB key (Please refer to the Export PIDs in USB key portion of this test case).
    2. Attach USB into Intel AMT client device"s USB port.
    3. Boot system.
    4. Upon reaching POST, message will show:
    "Found USB Key for provisioning Intel(R) AMT
    Continue with Auto Provisioning (Y/N)"
    5. Press Y key in system"s keyboard.
    6. Wait 25 to 30 seconds until message will show:
    "Intel(R)AMT Provisioning complete
    Press any key to continue with system boot..."
    7. Press any key to boot system to OS.
    • No error should appear in POST after performing USB key provisioning
    • System may able to connect to Intel AMT machine (LANDesk Server).
    A
    A
    A

    OTHER DETAILS
    EUT Quantity : Two systems 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)
    TEMS Reviewer Log:
    Review Logs
    Keywords:   None
    Requirements :   None
    Attached files :

    Update History:
    This document is not yet modified.