PowerShell domain or trusting domain can also be remote _powershell

The default is to open PS remotely via enable-psremoting, and Kerberos authentication is initiated. This method is only suitable for two computers in the same domain or in the trusting domain of the designated computer (name can be suffix). However, it does not support cross-domain, extraterritorial, or IP addresses.

To make it work, you need to change the remote way of your computer. Please execute the following command with administrator privileges:

Copy Code code as follows:

Ps> Set-item Wsman:\localhost\client\trustedhosts-value *-force

If this path is illegal, you may need to first turn on the PS remote (using "Enable-psremoting–skipnetworkprofilecheck–force") on your computer.

Once you have changed, you can use NTLM authentication. But keep in mind that these domain-specific computers, you will use the "–credential" parameter to specify the relevant user and password.

Support Powershell3.0 and future versions

Setting up Windows PowerShell remote processing

You can use Windows PowerShell remote control to run a Windows PowerShell cmdlet to manage WCF and WF services located on a remote computer, or to manage system services, monitoring data, or staging databases located on a remote AppFabric server. To do this, open the Windows PowerShell Console, point to the remote computer, create a remote Windows PowerShell session, and then execute the cmdlet on the remote server.
To use Windows PowerShell remote control, you must do the following:
Install Windows PowerShell 2.0 on the client and remote server computers.

Enable the Windows PowerShell Remote control feature on the remote server computer.

Use Windows PowerShell listeners to configure the WinRM NT service (Microsoft implementation of the Wsman protocol) so that this service can listen for Windows PowerShell from remote Windows PowerShell clients Please.