PrepAway - Latest Free Exam Questions & Answers

You need to ensure that Server2 can be managed by using Server Manager from Server1

HOTSPOT
You have two servers that run Windows Server 2012 R2. 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.

PrepAway - Latest Free Exam Questions & Answers

Answer: See the explanation

Explanation:
Modify the TrustedHosts list – Server1
Set the network profile to Private- Server2
Override the User Account Control (UAC) restrictions by using the
LocalAccountTokenFilterPolicy registry entry – Server 2

On the computer that is running Server Manager, add the workgroup server name to the
TrustedHosts list.
References:
http://technet.microsoft.com/en-us/library/hh831453.aspx

2 Comments on “You need to ensure that Server2 can be managed by using Server Manager from Server1

  1. Gustello says:

    Wrong, UAC needs to be overridden on the steering computer:

    “if a user is not logged on by using the source computer’s built-in administrator account, the following WinRM registry key must be configured to allow remote access from the source computer. This change is required because of a User Account Control (UAC) limitation on non-administrator accounts that are members of the Administrators group. To change this registry key, run the following command on the source computer at a command prompt that is opened with elevated user rights:

    New-ItemProperty -Name LocalAccountTokenFilterPolicy -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -propertyType DWord -value 1

    Reference:




    0



    0
  2. JR says:

    Actually the answer given is correct:
    Server 1
    Server 2
    Server 2

    “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

    New-ItemProperty -Name LocalAccountTokenFilterPolicy -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -propertyType DWord -value 1”

    https://technet.microsoft.com/en-GB/library/hh831453.aspx




    0



    0

Leave a Reply