The most valuable aspect of the solution would be separation from the Windows operating system. Prior to our BlueCat usage, we were doing Windows DHCP and Windows DNS on the outside. Not being dependent on the Windows operating system, which routinely needs patching, reboots, et cetera, is great. Our BlueCat environment is now free of any of those vulnerabilities of Microsoft. Integrity is largely easy to use. It depends on whether you're coming from a Windows, Linux, or Unix background. If you have a background with Unix-based DHCP or name services, it's a little easier to adopt. Coming from a Windows background, where you traditionally use Windows for either of these functions, it's not hard. However, it's easier if you already have Linux or Unix experience. We witnessed the benefits of Integrity almost immediately. Since we had to reboot our Windows servers every month for patching, and with the new updates coming out for the Windows environment on a monthly basis - it was challenging. After switching to BlueCat, we don't have to reboot just for the patch. We can deploy. And since we run a high availability platform we can take one node down and still keep services alive without production impacts. Integrity provides very close to a single pane of glass view of our IP address space. It would be more so if we were more prudent. It has the potential. A single pane of glass is a buzzword. It's very common. Everybody's looking for that. It would be nice if we were diligent and disciplined enough to record everything in our BlueCat environment. However, we don’t. Integrity helps reduce human error, more or less. Integrity helped us to reduce downtime. Given that, in a Windows environment, if we are following our best practice of patching on a monthly basis, that's about an hour or a month. We used to have a few hours a month per device or a couple of hours a month per device. Now we just don't have any downtime. We've reduced our downtime by 100%. Integrity helped consolidate tools in that we now have a much better configuration standard. It is BlueCat. It's all BlueCat. No more Windows, Linux, DHCP servers, aside from Bluecat BDDS. So, the configuration standard is being met and achieved every time, whereas there was always an opportunity to not maintain a standard when we were doing individual configurations. BlueCat helped us free up IT staff for other projects to some extent. Not a substantial amount - and not really a measurable amount. We do have two primary engineers who operate this environment, and their workloads have certainly gotten better to where they can spend time doing other things. Integrity helped us to improve the network stability due to a lack of downtime. If we're not having downtime when we're rebooting a Windows DHCP server, that means the clients continue to operate as they're expected without downtime failures. BlueCat saved us money in terms of a life-and-death scenarios and the stress factors that surround a healthcare environment. We generally don't have downtime in our DHCP environments anymore. The clinics and the hospitals can continue to operate and not be in that position to be down. DHCP is a core NECESSARY service that you don't miss till it's not working. And sometimes, that does mean that there are lives on the line. So from a medical hospital health care stance, absolutely saves us. I don't know if you can put a price on life, however, for our use case, it's pretty significant for us.
