Ah, that makes things easier. This link describes exactly what settings you need to set to work with AMT:
Ajith mentioned configuring the settings using the WinRM command line, but you can use the tool I mentioned previously to configure the appropriate settings as well. All the three settings in Ajith's blog are in the WinRM Client section.
TrustedHosts= specific IP addresses or domains that are trusted
This will support AMT configured locally with Digest authentication (instead of Kerberos) and without TLS encryption on the ongoing traffic. This is the easiest to work with during initial development (and requires the least network infrastructure), of course in an actual product depending on your security requirements you might want to support Kerberos authentication or TLS encryption on the traffic.
Must the described thing with the ADSIEDIT.msc realy be done?
As I understood, I need therefore RSAT (containing the ADSIEDIT.msc) & Windows Server.
The ADSIEDIT.msc- hint is the only hint, which I read and which I did not tried.
Since I can't imaging that this is the reason for receiving "Access is denied" on each simple winrm command.Hey guys, has nobody an idea, what can be the reason / and the solution for the described problem?