Your network contains an Active Directory domain named contoso.com. The domain contains two servers
named Server1 and Server2. Server1 runs Windows Server 2012. 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?
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.
B Server 1 needs to install DHCP feature first
0
0
I think Microsoft is famously leaving the fact that DHCP is not installed on server1 so B would be right.
1
0
The question now has 4 new choices for answers
A. From Windows Firewall with Advance Security on Server2, create an inbound rule
B. From IE on Server2, download and install Windows Management Framework 3.0.
C. From Server Manager on Server1, install a feature.
D. From the Windows PowerShell on Server 2 run Enable PSRemoting.
It is either C or D.
Does anyone know?
0
0
Answer D. would be correct as Enable-PSRemoting is for managing a remote server by Powershell commands. Thgis enables Remote Management on the target server Server2 and opens up the firewalls, starts the WinRM service, etc.
https://technet.microsoft.com/en-us/library/hh849694.aspx
The Enable-PSRemoting cmdlet performs the following operations:
— Runs the Set-WSManQuickConfig cmdlet, which performs the following tasks:
—– Starts the WinRM service.
—– Sets the startup type on the WinRM service to Automatic.
—– Creates a listener to accept requests on any IP address.
—– Enables a firewall exception for WS-Management communications.
—– Registers the Microsoft.PowerShell and Microsoft.PowerShell.Workflow session configurations, if it they are not already registered.
—– Registers the Microsoft.PowerShell32 session configuration on 64-bit computers, if it is not already registered.
—– Enables all session configurations.
—– Changes the security descriptor of all session configurations to allow remote access.
—– Restarts the WinRM service to make the preceding changes effective.
To run this cmdlet, start Windows PowerShell with the “Run as administrator” option.
0
0
I think it’s
D. From the Windows PowerShell on Server 2 run Enable PSRemoting.
0
0
Server Manager in Windows Server 2012 can manage Windows Server 2012, Hyper-V Server 2012, Windows Server 2008 SP2 and Windows Server 2008 R2 SP1
In Windows Server® 2012, you can use Server Manager to perform management tasks on remote servers.
Remote management is enabled by default on servers that are running Windows Server 2012. To manage a server remotely by using Server Manager, you add the server to the Server Manager server pool.
You can use Server Manager to manage remote servers that are running Windows Server 2008 and Windows Server 2008 R2, but the following updates are required to fully manage these older operating systems:
.NET Framework 4.0/4.5
Windows Management Framework 3.0
3
0
But question says Windows Server 2008 R2 Service Pack 1 (SP1), so I think no need to install framework. B would be the preferred choice.
0
0
There is another set of answer:
A. From Internet Explorer on Server2, download and install Windows Management Framework 3.0.
B. From the Microsoft Management Console on Server1, add a snap-in.
C. From Windows PowerShell on Server1, run Install-Windows Feature.
D. From Server Manager on Server2, enable Windows Remote Management.
Correct Answer: D
0
0
Configuring remote management of earlier versions of Windows Server
Server Manager can be used to remotely administer computers running versions of Windows Server older than Windows Server 2012. For Windows Server 2008 and Windows Server 2008 R2, Server Manager can be used to perform many of the tasks available in Server Manager, with the notable exception of adding or removing roles. To manage remote servers that are running Windows Server 2008 or Windows Server 2008 R2, you must first install the following updates, in the order shown:
1.
.NET Framework 4
2.
Windows Management Framework 3.0
The Windows Management Framework 3.0 download package updates WMI providers on Windows Server 2008 and Windows Server 2008 R2. The updated WMI providers enable Server Manager to collect information about roles and features that are installed on the managed servers.
3.
The performance update associated with Knowledge Base (KB) article 2682011 (or a superseding update), which enables Server Manager to collect performance data from Windows Server 2008 and Windows Server 2008 R2.
Answer: D
2
0
There is no mention of using the 2012 Server Manager to manage the 2008 server. There is no need for .NET or WMF in this scenario. It only mentions using the DHCP console. It also asks what you should do FIRST. You would first need to enable remote management Server2 and then install the DHCP manager (Role Administration Tools feature) on Server1.
Since enabling Remote Management from the Server Manager or through “winrm quickconfig” really is just opening firewall ports, and starting/configuring some other services that don’t relate to DHCP management, I think the answer would be C.
0
0
to do any remote management of the older version the WMF has to be updated. you probably had a hard time passing your test
2
0
I simulated this scenario in lab 2 machines members of the domain:
Windows Server 2008 R2 SP1
Remote management disabled
DHCP role installed
Windows Management Framework 3.0 is not installed
Windows Server 2012 R2
Just installed RSAT feature for DHCP
Summary I was able to manage Win 2008 machine through DHCP console from Win 2012 machine. I created new scope and made a reservation
We do not need to use Server Manager in this scenario –> no need to install Windows Management Framework 3.0 or enable remote management on win2008 machine
So answer would be:
C. From Windows PowerShell on Server1, run Install-Windows Feature.
3
0
When you configured your Lab, by default was Remote Management enabled or disabled.
As you have only mentioned Remote Management is disabled, I will take it is the default setting.
On Exam testing I am doing “Annette”, the answer is showing as C. Run Install-Feature, same as your.
However the answer explanation for C. is about enabling remote management and winrm.exe, etc.
0
0
I think you are right. 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.
The answer must be
B. From Windows PowerShell on Server1, run Install-Windows Feature.
0
0
The correct answer that is not really here should be: from the MMC console on server1, add a snap-in. By using the snap-in on the DHCP console in server1, you should be able to add the other server (server2) in this case and manage it. And no, it does not need to be enabled for remote management for that to happen. Try that yourself.
Trust me I did.
1
0
Madina/Tvegata are right.
Only after you’ve added ‘the role admin tool feature you’ll be able to add the snapin to a mmc. So B first, then A.
3
0
D
0
0
this question is in other VCE: Just a litte bit different
QUESTION 101
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. 5erver2 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?
A. From the Microsoft Management Console on Server1, add a snap-in.
B. From Server Manager on Server2, enable Windows Remote Management.
C. From Windows PowerShell on Server2, run Enable-PSRemoting.
D. From Server Manager on Server1, install a feature.
D is right answer?
0
0
https://technet.microsoft.com/en-us/library/hh921475.aspx
I think Answer is correct. A for – add a snap-in
Updated: June 24, 2013
Applies To: Windows Server 2012, Windows Server 2012 R2
In Windows Server® 2012 R2 and Windows Server® 2012, you can use Server Manager to perform management tasks on remote servers. Remote management is enabled by default on servers that are running Windows Server 2012. To manage a server remotely by using Server Manager, you add the server to the Server Manager server pool.
You can use Server Manager to manage remote servers that are running older releases of Windows Server, but the following updates are required to fully manage these older operating systems.
To manage servers that are running Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008 by using Server Manager in Windows Server 2012 R2, apply the following updates to the older operating systems.
• .NET Framework 4.5
• Windows Management Framework 4.0. The Windows Management Framework 4.0 download package updates Windows Management Instrumentation (WMI) providers on Windows Server 2012, Windows Server 2008 R2, and Windows Server 2008. The updated WMI providers let Server Manager collect information about roles and features that are installed on the managed servers. Until the update is applied, servers that are running Windows Server 2012, Windows Server 2008 R2 or Windows Server 2008 have a manageability status of Not accessible.
• The performance update associated with Knowledge Base article 2682011 allows Server Manager to collect performance data from Windows Server 2008 and Windows Server 2008 R2. This performance update is not necessary on servers that are running Windows Server 2012.
To manage servers that are running Windows Server 2008 R2 or Windows Server 2008, apply the following updates to the older operating systems.
• .NET Framework 4
• Windows Management Framework 3.0 The Windows Management Framework 3.0 download package updates Windows Management Instrumentation (WMI) providers on Windows Server 2008 and Windows Server 2008 R2. The updated WMI providers let Server Manager collect information about roles and features that are installed on the managed servers. Until the update is applied, servers that are running Windows Server 2008 or Windows Server 2008 R2 have a manageability status of Not accessible – Verify earlier versions run Windows Management Framework 3.0.
• The performance update associated with Knowledge Base article 2682011 allows Server Manager to collect performance data from Windows Server 2008 and Windows Server 2008 R2.
0
0
I find this question, and all of the possibel answers very confusing.
This question with the exact same wording is appering several times with different answer options.
The question states : using the DHCP console on Server1.
Doesn’t that mean the snap-in is already installed? Which would exclude A.
For the same reason I would exclude B. Why would you need to use Powershell on Server1 to install what feature?
That leaves C or D. As 2008 R2 does not have Management Framework 3.0 installed by default I would go for D.
However several articles on Technet refer to WinRm and Powershell command Enable PSRemoting and EnableWinRM which mention changes to the firewall to allow remote management. So I have not ruled out this option.
In a number of cases one answer to this exact same question was From Server Manager on Server1, install a feature because of the repetition of this answer (basically the same as answer B in this question) and the fact that the question is “What should you do first?” If the question is worded exactly the same then wouldn’t your action be the same, there is only one thing you can do first, right?
Any thoughts on what might be actually correct would be highly appreciated.
0
0
A. WRONG – Need to install DHCP role first
B. WRONG – DHCP is a role not a feature
C. WRONG – Don’t need this
D. CORRECT – This would be one of the steps required
0
0
i agree with you … sounds logic
0
0
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?
A. From Windows Firewall with Advanced Security on Server2, create an inbound rule.
B. From Internet Explorer on Server2, download and install Windows Management Framework 3.0.
C. From Server Manager on Server1, install a feature.
D. From Windows PowerShell on Server2, run Enable PSRemoting.
Correct Answer: C
0
0
Based on this Questions. Correct answer is B.
0
0
B- First thing is to install on Server1 the RSAT DHCP Server Tools Feature.
0
0
C is correct. DHCP is already installed on Server 2 and Remote management is also enabled by default on 2008
0
0
For me is B:
We need on server2 tool for managing DHCP.
So first we need to install this tool from RSAT – install WindowsFeature.
0
0
One more – look at Q.153 and answers.
After that I’m sure of my choice
0
0
Have you tested this on your lab? If you will then you will see that this process first requires the installation of Framework 3.0 to Server 2 which has windows server 2008 R2 SP1. Then enable winRM by using command winrm quickconfig.
Then that’s the time that you can manage it from Server1 with windows 2012 R2 installed.
This is the error i encountered during the test on my lab.
“verify winrm 3.0 service is installed 2008 r2, running, and required firewall ports are open”
I just follow this steps:
http://www.stugr.com/2012/09/manage-2008-from-2012-server-manager/
hope it will help you guys
0
0
c is correct
please see this link:
https://technet.microsoft.com/en-us/library/cc725989(v=ws.11).aspx
0
0
B!
You need to install RSAT of DHCP for dhcp management console.
Like this question:
https://www.aiotestking.com/microsoft/you-need-to-manage-dhcp-on-server2-by-using-the-dhcp-console-on-server1-11/
0
0