66 lines
2.8 KiB
Plaintext
66 lines
2.8 KiB
Plaintext
Copyright (C) 2011 Intel Corporation
|
|
|
|
Intel(R) Active Management Technology (Intel(R) AMT):
|
|
A short description of the User Consent Sample code for the usage of developers.
|
|
|
|
User consent sample application:
|
|
--------------------------------
|
|
This sample shows the usage of the User Consent feature of Intel(R) AMT managed
|
|
machine using WS-Management.
|
|
|
|
How to run the sample:
|
|
----------------------
|
|
1. Open "UserConsent.csproj" in Microsoft Visual Studio* and build the project.
|
|
An output file "UserConsent.exe" should be created.
|
|
2. Make sure that Intel.Wsman.Scripting.dll is located in the same place as the
|
|
"UserConsent.exe" file.
|
|
3. Make sure that the Intel(R) AMT device has been activated on the target
|
|
machine.
|
|
4. Use the generated executable as described in the command usage (type the
|
|
command to get the usage instructions).
|
|
|
|
Supported operations:
|
|
----------------------
|
|
The sample demonstrates the following flows:
|
|
-flow : Try to perform a full user consent flow.
|
|
-status : Display The user consent required and state properties.
|
|
-timeout : Display the user consent code and display timeout properties.
|
|
-start : Try to start a user consent pop up at the host.
|
|
-sendCode : Send consent code.
|
|
-getMonitor : Display the current default monitor.
|
|
-setMonitor : Change the default monitor.
|
|
-cancel : Cancel a previous user consent code request.
|
|
|
|
|
|
The -flow options:
|
|
(for more details on the flow - see attached file(UserConsent-FlowDiagram.pdf) )
|
|
------------------
|
|
This flow can only be executed if system is powered-up.
|
|
This flow executes the following steps:
|
|
1. Check the user consent (OptIn) status:
|
|
If OptInRequired property is not NONE, consent is required for some
|
|
operations.
|
|
If the OptInState property is not RECEIVED the flow will continue (If needed
|
|
- the state will reset to "not-started"),otherwise the flow will be
|
|
terminated.
|
|
2. Start consent.
|
|
3. Check if Sprite is supported :
|
|
* If not supported - Reboot the system (consent will be displayed via MEBx).
|
|
4. If needed- Switch the monitors.
|
|
5. Sent consent code. You will have three trials to supply the correct code.
|
|
|
|
General Notes:
|
|
--------------
|
|
1. The Consent flow requires a Reboot when discrete gfx and integrated gfx are
|
|
not present in the platform. In this case user consent pop-up will be
|
|
displayed from MEbx, after the target system was rebooted. The full flow
|
|
supports a reboot operation as described in the RemoteControl sample (can be
|
|
found in this module: Samples\RemoteControl). However, it is preferable to
|
|
reboot the target platform gracefully (by a different method) after the start
|
|
consent command.
|
|
2. This sample uses the Intel.Wsman.Scripting library.
|
|
|
|
-------------------------------------------------------------------
|
|
* Other names and brands may be claimed as the property of others.
|
|
|