- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
What step were you on when you got the error? Can you attach the whole log?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Is it only failing on KVM? It looks like access denied which may be related to needing an additional password for KVM if using VNC - the RFB - remote frame buffer password.
It would be good to know what version of AMT your client has and other version information (SCS, etc.)
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I wrote this "troubleshooting" blog that might help: https://software.intel.com/en-us/blogs/2012/08/08/intel-kvm-port-requirements-and-troubleshooting-tips
Colleen and I will also discuss further.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Bob,
You will get such error when trying to reconfigure (update AMT settings) AMT already configured to CCM (Client Control Mode - default mode for HBC - Host Based Configuration) with SCS AMT profile that has KVM Redirection Settings with "User consent code required before beginning KVM Session" checkbox unchecked- see example below.
Client Control Mode by definition and Intel AMT Technology design requires User Consent Code for ALL redirection operations and this can't be changed/disabled even by AMT Administrator or RCS without moving AMT to ACM.
I guess your Intel vPro system is Wireless AMT only (LAN Less) tablet or 2in1 so default possible AMT configuration mode is CCM only.
So AMT technology rejects invalid requests to change Consent Code settings in CCM with such error, while rest of AMT re-configuration is completed successfully.
I have seen exactly same error with AMT 9.5 system in scenario as described above.
Move to ACM (or direct configuration to ACM) is possible for AMT 7-9.5 systems with AMT LAN only (+ requires AMT PKI Provisioning certificate that will match DHCP Option 15 domain suffix).
New Intel AMT 10 allows Wireless only MovetoACM change but with DNS PKI suffix defined in Intel ME FW (via MEBx or One Touch USB Preconfiguration.
If you want to get Wireless Only AMT 7 + system configured in ACM you may use 2 stage/ phase configuration:
- Perform USB Local Configuration to ACM (USB One touch configuration requires system reboot and USB flash drive with setup.bin file created using USBFile.exe tool from Intel AMT SDK). It will configure AMT to ACM setting AMT digest administrator password to
<New MEBx Password> from setup.bin file.
then follow up with second stage - perform AMT HBC configuration (with XML profile file) using ACUConfig.exe with /AdminPassword <New MEBx Password> - which acctually just updates AMT settings with parameters which USB can't configure but keeping AMT in ACM.
AMT profile used can change AMT digest admin password to new one (that is not visible in plain text like in setub.bin file).
rgds
darek
