AMT is provisioned and I can manage the pc remotely. Even KVM, console and redirection works.
The problem I have is with enabling Outpost on this managed pc. I am using latest "Manageability_Developer_Tool_Kit_7_0_11340_2". I imported certificate to Outpost. But still error prevents me to connect.
Below is screenshoot of error and ME information. What am I missing here?
Anyway I don't have any extra users setup in AMT. Only admin and I use one and only password. So that couln't be the source of problem.
Yes LMS service is up and running automaticaly.
I donwloaded Open source DTK and now I can manually connect Outpost tool.
But when I try to setup Outpost service with "managebility Outpost tool - configuration and control" tool then I get an error. I attached the error message...
So there is progress but not completelz there yet :).
Here are some more things to try: (I did finally see the error - it was right up on top of the file....)
Browse to localhost:16992 or 16993 and make sure something happens. You should connect to 16992 since you do not have TLS implemented.
If in Mutual-auth mode, Outpost will need a client certificate to log in. (This should not be applicable to you.)
Check the username/password. The user account needs to have local access rights. If remote only, it will not work.Are you using your ip address to connect, or are you typing in a host name? If you are trying with the host name, you might want to try it with the actual IP address as well. Have you input a host name for the ME? Just posing questions - I'm not actually sure if you have to do so or if you haven't and you try to connect to the ME using your host name that that is part of the OS configuration, if it would be able to resolve it.
But localy on managed pc this Outpost service still does not work.
Yes I am using IP to connect, never host name. Yes I am trying all this with windows administrative priviliges. I am not using certificate with Outpost anymore.
I tried localhost:16992 on managed pc but it does not open anything.
How do I setup AMT user account and check if it has local access rights? And honestlly what does it have to do with not being able to run Outpost as a service level where no AMT priviledges are being asked for?
I am getting out of ideas on this one. Outpost service wors for me fine on some old AMT 4 machine, but here on AMT 7 it's a nightmare...
I just got a new DE67-HA (specifically because of AMT), and have ran into an odd issue (contrary to configuration instructions). AMT seems properly enabled in BIOS, yet when I enter the ME BIOS EXTENSION (via Ctrl P), I am not asked for a password, I don't any references to changing/setting passwords, and I don't see how to proceed beyond that point.
Please assist. Thank you.