Does Windows restrict AMT remote desktop connections?

[guarddog]

I downloaded ME firmware v8.1.70.1590 (5MB) from this site and flashed it onto 12 different Intel NUC machines (DC53427HYE). All is well on 10 of them.

I use Intel Manageability Commander to connect/manage of all them, remote desktop, disk redirection – everything is great. I installed Windows on all of them using the disk redirection.

A problem has popped up on two of them (after installing, installing patches and registering the OS).

If I try and initiate a remote desktop connection it connects and disconnects instantly.

On the host OS it will flash a little computer icon with red X in the top right of the screen, so I know I am connecting and am being actively denied by something but I can’t figure out what.

I do not have any restriction limiting KVM, user consent is not required.

Anyone know what setting causes this? I’m fine in BIOS, can even install Windows from scratch again but once Windows is up and running after it finishes the install I am ‘kicked out’.

[guarddog]

I wanted to determine if this was a Windows issue or not.

I installed the latest Debian on the system (via remote desktop). Installer boots, do all configuration, formatting disk etc. All remotely.

Reboot and when it should take me to the login prompt I get disconnected. If I try and connect, I have the exact same symptom as Windows, just disconnects me instantly.

This is just totally weird.

[plutomaniac]

Since I never had a 5MB system and thus no actual/hands-on AMT/KVM/SOL etc knowledge, I suggest you ask for help or tips at the relevant Intel forums. All I can think of is something being wrongfully configured at MEBx or that these two Engine regions need to cleaned and reflashed because something is broken at the DATA section. But I cannot be sure because I lack 5MB features knowledge and it’s best if obvious stuff are checked/excluded first from knowledgeable, on the subject, people.