HOTSPOT
You have two servers that run Windows Server 2012. The servers are configured as shown in the following
table.
You need to ensure that Server2 can be managed by using Server Manager from Server1.
In the table below, identify which actions must be performed on Server1 and Server2. Make only one selection
in each row. Each correct selection is worth one point.
Answer: 
Explanation:
You should modify the trustedhosts list on the server running server manager, which is server 1
http://technet.microsoft.com/library/hh831453.aspx
1
0
Correct.
0
0
I love bean
1
0
Agree with bean
0
0
bean is correct
0
0
Bean is right.
http://msdn.microsoft.com/en-us/library/dd759202.aspx
0
0
YES – NO
NO – YES
NO – YES
would be my answer. is this correct?
0
0
It shoud be
Server 1 Server2
Yes No
Yes No
No Yes
Is this correct
0
0
Sorry
That would be
Server1, Yes No No | Server2 No Yes Yes – Jason is correct..
0
0
Always modify the trusted host list on the CLIENT machine you are using to connect to the server with. Even if the client machine is another server itself.
Just did all this to manage a 2012R2 hyper-v server from Win8.1 Pro machine.
0
0
According to this article it’s wrong
1. On the computer that is running Server Manager, add the workgroup server name to the TrustedHosts list. This is a requirement of NTLM authentication. To add a computer name to an existing list of trusted hosts, add the Concatenate parameter to the command. For example, to add the Server01 computer to an existing list of trusted hosts, use the following command.
Set-Item wsman:\localhost\Client\TrustedHosts Server01 -Concatenate -Force
2.
Determine whether the workgroup server that you want to manage is in the same subnet as the computer on which you are running Server Manager.
If the two computers are in the same subnet, or if the workgroup server’s network profile is set to Private in the Network and Sharing Center, go on to the next step.
If they are not in the same subnet, or if the workgroup server’s network profile is not set to Private, on the workgroup server, change the inbound Windows Remote Management (HTTP-In) setting in Windows Firewall to explicitly allow connections from remote computers by adding the computer names on the Computers tab of the setting’s Properties dialog box.
3. To override UAC restrictions on running elevated processes on workgroup computers, create a registry entry called LocalAccountTokenFilterPolicy on the workgroup server by running the following cmdlet.
https://technet.microsoft.com/library/hh831453.aspx
So the answer is:
Server 1: Modify the trusts hosts file in computer running server manager, which is Server 1.
Server 2: Set the network profile to private in work group computer, which is server 2
Server 2: Override UAC resitrction in a work group computer, which is server 2.
0
0
Modify the TrustedHosts list command “Set-Item” must be run always on the server that is running Server Manager, not on the client server.
From Technet: “On the computer that is running Server Manager, add the workgroup server name to the TrustedHosts list”
Source: https://technet.microsoft.com/en-us/library/hh831453.aspx
0
0
Tested on my Lab:
WinServer 2012 R2 Full GUI DC, trying to access through Server Manager another server (WinServer 2012 R2 Core in Workgroup). After adding the workgroup server to server manager I got a Kerberous error.
After adding the workgroup server in the TrustedHosts list on the server running server manager it worked.
0
0