PrepAway - Latest Free Exam Questions & Answers

You need to manage DHCP on Server2 by using the DHCP console on Server1

Your network contains an Active Directory domain named contoso.com. The domain
contains two servers named Server1 and Server2.Server1 runs Windows Server 2012
R2.Server2 runs Windows Server 2008 R2 Service Pack 1 (SP1) and has the DHCP Server
server role installed.
You need to manage DHCP on Server2 by using the DHCP console on Server1.
What should you do first?

PrepAway - Latest Free Exam Questions & Answers

A.
From the Microsoft Management Console on Server1, add a snap-in.

B.
From Windows PowerShell on Server1, run Install-WindowsFeature.

C.
From Windows Firewall with Advanced Security on Server2, create an inbound rule.

D.
From Internet Explorer on Server2, download and install Windows Management
Framework 3.0.

Explanation:
The DHCP snap-in isn’t available unless the DHCP feature is installed. Server 1 is stated to
not have DHCP installed, so the snap-in therefore cannot be added. We must add the DHCP
server role.
References:
Training Guide: Installing and Configuring Windows Server 2012 R2, Chapter 6 Network
Administration, p.228

29 Comments on “You need to manage DHCP on Server2 by using the DHCP console on Server1

  1. Klaus says:

    Answer B is correct, but the explanation isn’t.
    You don’t need to install DHCP server role (actually answer B states to install a FEATURE, not a ROLE), but you have to install Remote Server Administration Tools, that is actually a Feature in Windows Server 2012 R2.




    0



    0
    1. David says:

      This would only be required if you were managing the server using new Server Manager. Since we are only going to be using the snap-in that simply needs to be installed on Server 1.




      0



      0
  2. Fernando says:

    To be able to fully manage remote servers that run Windows Server 2008 or the R2 Service Pack 1 operating system, you should install the .NET
    Framework 4 on Server2 first followed by the Windows Management Framework 3.0.




    0



    0
  3. Fernando says:

    I was wrong.
    Correct Answer: B
    Section: (none)
    Explanation
    Explanation/Reference:
    Explanation:
    The DHCP snap-in isn’t available unless the DHCP feature is installed. Server 1 is stated to not have DHCP installed, so the snap-in therefore cannot be
    added. We must add the DHCP server role.




    0



    0
  4. rajen says:

    When the DHCP role is installed, it appears that the firewall rules are automatically added. This means you only need to add the DHCP Manager MMC snap-in which is a Role Administration Tool feature.
    So the correct answer is B.




    0



    0
  5. JoeTech says:

    On my lab I built two machines added them to Domain. 1 was 2012 and the other 2008R2. On the 2008R2 box I installed DHCP. From 2012 I did not have a DHCP console avaialable until I installed the feature with install-Windowsfeature DHCP -IncludeManagmentTools
    After that installed I was able to launch DHCP console and then connect to the 2008R2 box and manage DHCP. So I believe B is correct answer




    1



    0
  6. bbyipp says:

    tested in lab and implemented in production with the following for reference:
    management computer: w10 with (1) server manager installed (same as server1 in this question) + RSAT specifically DHCP
    W2008R2: (2) take the default installation with remote management NOT turned on (unchecked) + (3) .Net 4.5 install + (4) windows management framework 5.0 for W2008R2 + (5) restart
    ==> from management computer\s server manager, I can right-click to launch DHCP manager to manage W2008R2 remotely.
    So, there is no sequence for (1), (2), (3) and (4). And these are the minimum steps. At the end, the remote management on W2008R2 is still OFF.

    Answer B and C but no sequence.




    0



    0
  7. Gilbert is lost. says:

    B is correct, first thing to do is to install the Feature from RSAT called “DHCP Server Tools” and you can do this using the powershell command Install-WindowsFeature.

    Only after the DHCP Server Tools is installed it will be possible to add the DHCP Snap-in into MMC.




    0



    0
  8. TheoneTruePotato says:

    We need to squash this once and for all.

    YOU DO NOT NEED TO ENABLE PS REMOTING, WINRM, OR OPEN ANY FIREWALL RULES
    YOU DO NOT NEED TO INSTALL .NET or Management framework on 2008 Server.
    YOU DO NOT NEED TO MODIFY A SINGLE THING ON THE 2008 R2 Server
    WHEN YOU INSTALL DHCP ROLE ON 2008R2 it automatically opens the firewall ports needed for management.

    Just Tested In a lab.

    Server1 2012R2 With nothing installed
    Server2 2008R2 with only DHCP role installed, No updates
    Both domain joined.

    1. Install Management tools on Server1 using Install-windowsfeature
    2. Open DHCP Console, Connect to Server2

    Either use Powershell or server manager to install the server tools/management tools.




    0



    0

Leave a Reply