CORRECTED (Previously BC) Your network contains an Active Directory domain named contoso.com. The
domain contains two member servers named Server1 and Server2.
You install the DHCP Server server role on Server1 and Server2. You install the IP Address Management
(IPAM) Server feature on Server1.
You notice that you cannot discover Server1 or Server2 in IPAM.
You need to ensure that you can use IPAM to discover the DHCP infrastructure.
Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.)
A.
On Server2, create an IPv4 scope.
B.
On Server1, run the Add-IpamServerInventory cmdlet.
C.
On Server2, run the Add-DhcpServerInDc cmdlet
D.
On both Server1 and Server2, run the Add-DhcpServerv4Policy cmdlet.
E.
On Server1, uninstall the DHCP Server server role.
Explanation:
http://technet.microsoft.com/en-us/library/jj590712.aspx
Add-DhcpServerInDC
Adds the computer running the DHCP server service to the list of authorized Dynamic Host Configuration
Protocol (DHCP) server services in Active Directory (AD).
IPAM should not be installed on a DHCP server.
http://technet.microsoft.com/en-us/library/jj878312.aspx
IPAM must be installed on a domain member computer. You cannot install IPAM on a domain
controller. If IPAM is installed on the same server with DHCP, then DHCP server discovery will be
disabled.
So I decided to test this in a lab. I used 3 vms on the same network. they were named dc1, dhcp, and ipam. They were all joined to an adatum.com domain. Dhcp only had the dhcp role on it. IPAM had the dhcp and IPAM role on it. The first thing I tried was using add-dhcpserverindc which authorizes DHCP. I did this on the DHCP vm. I could not discover it with IPAM. I even tried adding a scope to DHCP and it still did not show up in IPAM. I then unauthorized DHCP on the DHCP server and removed the role from the IPAM and DHCP vms. After a reboot, I reinstalled DHCP on the DHCP vm. I authorized it using the powershell command and verified it authorized by checking with adsi edit. I still could not discover DHCP in IPAM. As soon as I addedd an IPv4 scope to the DHCP vm, I was able to discover it within IPAM.
So either this question requires three answers, which would be A,C, and E, or I didn’t do something correctly or the question is wrong.
Bob,
I didn’t tried this in lab therefore I’ll not be a smart azz.
Check this link…. (if you haven’t found it by yourself already)
https://technet.microsoft.com/en-us/library/hh831622(v=ws.11).aspx
This is from MS directly. Specifically states that you need to have at least 1 DHCP scope configured.
https://technet.microsoft.com/en-us/library/jj878309(v=ws.11).aspx#discovery
Problem: A DHCP server is not discovered.
Solution: Verify that the DHCP server role is not installed on the IPAM server. Verify that at least one IPv4 scope is configured on a DHCP server, and that the IPAM server has a TCP/IP connection to the DHCP server. Also verify that DHCP INFORM request messages sent by IPAM server are not filtered on the network.
So A & E?
Adding a scope doesn’t make the server discoverable. Using the Add-DhcpServerInDc command tells the server to activate in Active Directory. A DHCP server that isn’t activated cannot be discovered.
So the question is clearly asking how to discover server 2 with IPAM. Answers C& E are correct.
https://technet.microsoft.com/es-es/library/jj590712(v=wps.620).aspx