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:
B)
The Add-IpamServerInventory cmdlet adds a new infrastructure server to the IP Address
Management (IPAM) server inventory. Use the fully qualified domain name (FQDN) of the server to
add to the server inventory.
C)
The Add-DhcpServerInDC cmdlet adds the computer running the DHCP server service to the list
of authorized Dynamic Host Configuration Protocol (DHCP) server services in the Active Directory
(AD). A DHCP server service running on a domain joined computer needs to be authorized in AD so
that it can start leasing IP addresses on the network.
Add-IpamServerInventory; Add-DhcpServerInDC
Shouldn’t it be B and E since DHCP discovery does not work if IPAM is on same box with DHCP?
0
1
It is A&E
A: At least one IPv4 scope must be present
E: You can not discover any DHCP Servers as long as the DHCP role is installed on the same IPAM server.
2
2
C & E should be the correct answer
Important
If the DHCP server role is installed on the same server with IPAM, DHCP servers will not be discovered on the network.
https://technet.microsoft.com/en_us/library/jj878313(v=ws.11).aspx
4
0
C & E are the correct answers.
3
0
The given answer is incorrect, because you cannot not in stall IPAM on a DHCP server, so the first step is to uininstall DHCP !
0
0
It is not recommended that you install IPAM on the same server as your DHCP service.
https://technet.microsoft.com/en-gb/library/jj878342(v=ws.11)#IPAM Server
https://technet.microsoft.com/en-gb/library/jj878312(v=ws.11)
DHCP servers need to be authorised in AD. We cannot see from this question whether this server has been authorised, so we can only presume it is not and needs authorising in AD.
https://technet.microsoft.com/en-us/library/jj590712(v=wps.630).aspx
Answer is C and E.
3
0
you’re right with E but I would highlight the technical restriction rather than just to “not recommend”.
When it comes to the other point: same might be according to IPv4 scope. It is not stated that they created one. So it could also be an issue, as we just don’t know what prelimenary tasks the guys accomplished or not in advance… :-/
I’m getting the feeling that the amount of WTF questions in this 412 exam could be significantly higher than 410 and 411 🙁
2
0
Cant decide between A & E because of the below statement from a Technet trouble shooting article
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.
And C & E
As fgsfd comment seems correct also!
Leaning towards C & E
0
0
i test it in lab
i think it A and C
because you need to do both actions on Server2, to discover it by IPAM.
you cant discover DHCP on Server1 anyway, so deleting role ist nesessary
0
0
THEREFOR ANSWERS E AND C –> not A & C
1
0
I believe the provided answer to be correct. IPAM discovery requires the DHCP server to be authorized in AD, regardless of if it has any scopes configured (eliminating A and D). Reference: https://technet.microsoft.com/en-us/library/jj878313(v=ws.11).aspx#DHCP
While it is not recommended to install IPAM on a DHCP server, it is still possible to do so and have it work. Reference: https://technet.microsoft.com/en-gb/library/jj878342(v=ws.11)#IPAM
Even though the DHCP server roles were installed, it was not stated that they were authorized, therefore IPAM cannot discover them. If we wanted IPAM to do it all automatically, then we’d just authorize the two servers. Since authorizing Server1 wasn’t a provided option, we have to manually add it to the IPAM inventory, which is accomplished via Add-IpamServerInventory.
0
0
+1
Thank you for explaining this. I was leaning towards B,C because DHCP can be installed, it just won’t discover. Therefore we have to add server 2 manually by running the Add-IpamServerInventory cmdlet.
But, before we do, we should run the Add-DhcpServerInDc cmdlet on server 2 to manually authorize it as a DHCP.
0
0
No need to create an IPv4 if we run Add-IpamServerInventory cmdlet on server 1 and manually add the DHCP server2.
No need to run the Add-DhcpServerv4Policy cmdlet either if we are manually adding the DHCP server on server1 and manually authorizing it on server2. It will authorize to AD automatically.
0
0
This question really annoys me, so I tested in a lab.
Server discover does not work with DHCP and IPAM roles installed on the same server, so part of the solution is E.
To discover a DHCP server however, it needs to be both authorized and have a scope configured (A + C). Since we can only select 2 possible answers, I guess we need to assume that server 2 was authorized during post deployment tasks.
B will manually add server 2 to the IPAM inventory, however the question states “ensure that you can use IPAM to discover the DHCP infrastructure”.
So I think the answer is A+E.
Another shitty question.
0
0
Ms say
If the DHCP server role is installed on the same server with IPAM, DHCP servers will not be discovered on the network.
0
0
So… without a doubt, the answer is…
A) On Server2, create an IPv4 scope.
E) On Server1, uninstall the DHCP Server server role.
I did this in my lab: Created 3 servers because there is more to this setup than just two servers with DHCP.
In brief:
Create 3 servers. 1 DC, 2 DHCP. Server1 is the DC. Install DHCP on Server2 and 3. Then try installing IPAM on Server2. It will not install. It acts like it does but then you try running any PS commands or look for the services and it’s not there. I Uninstalled DHCP and tried IPAM first then installed DHCP. Nothing functions. I uninstall DHCP, IPAM, and reboot. Then re-install JUST IPAM on Server2.
Follow the steps to install and setup IPAM on server2.
https://blogs.technet.microsoft.com/canitpro/2013/08/15/step-by-step-setup-windows-server-2012-ipam-in-your-environment/
When Provisioning the IPAM server, I Chose “Manual” rather than GPO because we only have 2 servers to worry about.
Configure Server Discovery. Select root and “ADD”. Leave all checked for DNS and DHCP.
Start Server Discovery. At this point, it will discover your DC and DHCP server on Server3. It does take a few minutes to discover.
***You may have noticed that ONLY the DC is discovered.
In Server3 DHCP server, setup the IPv4 Scope and restart the DHCP service in Server Manager.
Go to Server2, IPAM server and restart the “Start Server Discovery”. When completed, go to Server Inventory and click refresh icon located at top of screen.
Now you should see both Servers DC and DHCP.
But Damn if there is an error that states “Unblock IPAM server” with a big Effing… RED X!
Aha…!
Follow this link to a “T” on DHCP server3 and restart the DHCP service and finally refresh the Server Inventory!
https://technet.microsoft.com/en-us/library/jj878311(v=ws.11).aspx
Hot Damn!
Hope this helps!
0
0
Well this sucks!
I was reading up on Jeff’s comment above @ June 15, 2017 at 3:40 pm and I did a test.
I deleted my IPv4 Scope, restarted the DHCP service and on Server2 (IPAM server) I ran “Add-IpamServerInventory”. And son of a bitch! The DHCP showed up on the IPAM server without a scope on the DHCP server.
So… Like a turd, I must retract my statement above and go with…
B) On Server1, run the Add-IpamServerInventory cmdlet.
E) On Server1, uninstall the DHCP Server server role.
Hey, but at least I got E right. Right?
sigh…
0
0
FYI… The Jeff @ June 15, 2017 at 3:40 pm is not this Jeff.
Guess I will have to go with a new handle.
0
0
Answer: E…and unknown
IPAM Discovery doesn’t work when installed on a DHCP server.
We know DHCP role is installed on Server2, but don’t know if any scopes have been configured. We do know the discovery would fail regardless because DHCP is installed on the IPAM server.
Best guess Answer: E & A
1
0
Do not make assumptions. If it doesn’t say you created a scope, then you didn’t create a scope. You only installed DHCP on both servers, and creating a scope is not part of the installation, that’s post-installation.
And since Microsoft says you can’t install IPAM on a DHCP server (or at least recommends against doing so), then go the way Microsoft wants you to do it (even if there is a workaround to this).
So the best answer, in my opinion as MS would want it to be, would be A and E. Also remember, while this question doesn’t say it, you generally want to go the easiest and less stressful way to do it. I think it’s easier to just uninstall DHCP from a server and create a scope on the other, than to run a few PS commands.
0
0