That's strange. If I remember correctly, you have an AMT 6.0 system (a DQ57TM board, I believe), I wouldn't expect an issue there.
There's something straightforward you can try that might work-around the behavior you're seeing. If you go into the View menu in the Commander, select the "Advanced Properties" option. In the Advanced Properties that comes up, select the Networking tab, then uncheck the "Use WSMAN first when available" checkbox.
After that, reconnect to your AMT system, and see if you're seeing the same behavior.
After unchecking the checkbox it did start working. It talks about a known issue with allocating 3PDS(or is it 3DPS, I've seen both) in the release notes and I didn't realize there was a work-around. Thank you for your help!
Is there a way to do the same thing in the Outpost Tool? I checked but couldn't find a setting.
It is 3PDS, ThirdParty Data Store (3DPS is a typo).
There is no comprable checkbox setting in Outpost. I'm assuming from your question the old Outpost worked but the new one is not; is this a correct assmption? If so, did you notice in the Release Notes that the new DTK no longer uses a native WS-MAN client? Are you sure you have WinRM configured properly on the Intel AMT system where you are trying to execute Outpost?