Your network contains an Active Directory domain named contoso.com. The domain contains a server named Server1. The domain contains a standalone server
named Server2 that is located in a perimeter network. Both servers run Windows Server 2012 R2.
You need to manage Server2 remotely from Server1.
What should you do?
A.
From Server1, run the Enable-PsRemotingcmdlet.
B.
From Server2, run the winrm command.
C.
From Server2/ run the Enable-PsRemotingcmdlet.
D.
From Server1, run the winrm command.
Maybe B?
Why not be? the first thing to do to configure a server for remote manager is to configure wimrm. right?
Why not B? the first thing to do to configure a server for remote management is to configure wimrm. right?
So i think to allow Sever 1 to remotely manage Server 2 you need to configure Server 2 for remote management. am I right? somebody correct me if I am wrong.
on server2 you need run winrs command
Pretty sure remote management is already enabled by default in windows 2012 R2. Maybe C?
http://www.iransec.ir/technical-articles/microsoft-technologies/powershell/1453-windows-powershell
“In many cases, you will be able to work with remote computers in other domains. However, if the remote computer is not in a trusted domain, the remote computer might not be able to authenticate your credentials. To enable authentication, you need to add the remote computer to the list of trusted hosts for the local computer in WinRM. To do so, type:
winrm s winrm/config/client ‘@{TrustedHosts=”RemoteComputer”}’
Here, RemoteComputer should be the name of the remote computer, such as:
winrm s winrm/config/client ‘@{TrustedHosts=”CorpServer56″}’”
So for our scenario, on Server1 run
winrm s winrm/config/client ‘@{TrustedHosts=”Server2″}’
to add Server2 to your trusted hosts (which is not required, if Server1 would manage another domain joined computer)
The Powershell approach with the same result is using
Set-Item wsman:\\localhost\Client\TrustedHosts Server2