How difficult the initial setup is depends on how you're approaching it. If it's a greenfield install, the setup's straightforward. It gets complicated if you already have another DHCP or DNS service in place and you need to migrate off of those. That isn't so much an issue on the Infoblox side because it concerns the proprietary natures of Microsoft DNS and DHCP or big iron or any other solution you're replacing. The time it takes to deploy Infoblox IPAM depends on whether it's a greenfield install or a migration. The migration can be tricky, especially if you have to do it in a scenario where you can't have any interruption at all to any of your users or clients. The people who handled deployment were primarily system administrator types, the folks that handled the existing DNS and DHCP solutions. After that, it becomes your network team, and your service desk can access the recording functions to look things up. Most of the solution is back-end within the IT environment. It's pretty seamless to do it right to the end users in the organization. The solution needs maintenance. It is not a very high-maintenance type of solution with updates coming up. Maintenance generally covers more troubleshooting issues, with some of the automated features not working for one reason or another. Infoblox has a smaller maintenance scale than a Microsoft solution, where you must maintain the OS, the DDE server, the DNS server, the clients, and so on. But Infoblox is not a complete set-it-and-forget-it.
