See matching posts in thread - WebUI access issue after MC 3.3...
See matching posts in thread - Manage ProxySG WebUI with Radiu...
The sample image below shows the Intel AMT WebUI of a system configured via the stated setup: It is possible to change this setting after the initial configuration event
When using Microsoft Internet Explorer to connect to the Intel AMT WebUI, enable Integrate Windows Authentication in the browser s Advanced Internet Options and restart the browser. Check the Intel AMT WebUI URL is specified using the client FQDN and not an IP address or other address alias otherwise Kerberos authentication will fail. Check the current Windows user (operating the WebUI or logged onto the Altiris console) is included in the Intel AMT ACL clients Check the current Windows user (operating the WebUI or logged onto the Altiris console) is not a member of a large number of Windows groups
4 attachments
To force a system to hang or bluescreen, try the SysInternals utility NotMyFault To generate a Password attack, attempt to login to the WebUI of a target client (http://ipaddress:16992) using the wrong UserID and password
2 Comments - no search term matches found in comments.
The Altiris 7 environment will attempt this automatically. If using the WebUI to directly access a system, the FQDN and Intel AMT port number must be specified
7 attachments
Utilize this account as a backup to validate Intel vPro Technology is responding, accessing via Intel AMT WebUI. Perhaps a better approach - and something seen in other management consoles - is to use Active Directory integration with a Kerberos group\user account
See matching posts in thread - Hi Aboonaim, just to confirm, you are saying tha...
See matching posts in thread - We manage each ASG independently; lately admins ...
See matching posts in thread - We've got an external certificate on the server ...