Please forgive the technical nature of this post but there are a lot of "techy" users on this site so I feel comfortable asking it.
I am a system administrator for a medium-sized company (~2000 employees), and both my boss and I have many years of experience in IT. In the olden days of managing printers in a Windows environment, the standard procedure was to give them static IP addresses (preferably on their own subnet if feasible), create a virtual IP port on the print server, and then share it out with a friendly name that users can connect to. Many companies still do it this way to this day, even though there are now a dozen print protocols to choose from and modern printers understand Windows networks just fine. Static IP addresses just aren't necessary anymore and there are plenty of better ways to do this these days.
A few years ago when we opened a new facility, I proposed the idea of using host names instead of static IP addresses during our network infrastructure planning meetings. My boss rejected the idea at the time, because 1) what we've been doing works fine, and 2) there was too much other stuff going on to go changing things up. The only fruit from that discussion was that we got rid of the printer VLAN and started using DHCP reservations in the regular workstation scopes.
I've also mentioned the idea a couple times since to other colleagues as well, and I mostly get the "That's just the way it's always been done" response.
Fast-forwarding to today, we had an org change recently and we contracted out printer maintenance to a local office equipment company. Our last "printer guy" just retired, so the task of managing network printers has fallen to the help desk. Since then, our printer situation has been... inconsistent to put it mildly.
The problem here is that while the help desk does have permissions to manage the print server, they don't have permissions to create DHCP reservations, so they've just been improvising their own ways to do printer changes. There has been a uptick in incidents where a printer doesn't work because of an expired address lease, and or an occasional IP conflict where there was an in-scope static address set on the device. Today I just happened to discover that one of our biggest VLANs was ~85% full because of duplicate reservations and a couple dozen other stale reservations that nobody ever purged out.
So now, I would like to propose this idea again, given that now we have a legitimate problem with the old-school ways. Honestly, this issue isn't that big a deal in the grand scheme of things; I'm just getting annoyed with fixing dumb printer issues lately. But given that this idea has been rejected before, how should I float it again without sounding like I'm just banging on the same drum?