Hi guys, ding
Could you please confirm whether IPAM supports monitoring DHCP on Windows Server 2016?
If so, what are the requirements?
TIA,
Deltona
It's not officially supported at this time, but I can say we are running it in our lab with no issues. If you take a look at the roadmap, you'll see we're working on making it official.
Hi ding,
Thanks for the swift reply. I've looked at the roadmap page and deduced that support for Windows Server 2016 referred to the platform OS that Orion IPAM can be installed on.
I've tried to monitor DHCP on a Windows Server 2016 but get access denied error. The domain account used has the same required privileges as those mentioned in the current admin guide.
Could you perhaps confirm with the lab whether any additional privileges are required, and if so, which one(s)?
Thanks.
Hey Vic! In our lab, a local user was created (with no additional privileges). I double-checked with the team and they said in order to successfully connect to the DHCP server, you should create a separate local user with the same creds as the user on the DHCP server. Hope this helps!
I have a 2016 server in a sandbox environment that I am running it on with no issues.
Got it, thanks!