Even as we’re seeing more and more organizations switching to PrinterLogic as their preferred enterprise print management solution, there are clearly many who are still using print servers—despite the vast numbers of persistent Windows Server 2012 R2 printing problems. That comes down to a variety of reasons. Some of it is skepticism that our next-generation print management solution will actually live up to its claims. Some of it is institutional aversion to change and the comfort of the familiar, however problematic the status quo might be. Some of it is concern about cost of migration and realizing sufficient short- and long-term ROI.
In this brief blog post, I’m not going to dwell too much on those specific Windows Server 2012 R2 printing problems. What I’d like to do instead is to explain how to add a printer to Windows Server 2012 R2 and also the basics of how to configure a printer in Windows Server 2012 R2. Then I’ll compare that process with PrinterLogic’s far more streamlined and powerful approach to print management.
Basic print management in Windows Server 2012 R2 is not all that different from previous versions. Assuming you’ve already set up Print Management and the appropriate roles, to add a printer to Windows Server 2012 R2, you’ll need complete the following steps:
If you’re wondering exactly how to configure a printer in Windows Server 2012 R2, well, that’s slightly more nuanced because so much depends on your particular environment. Most of the necessary options can be found by locating the appropriate printer in Print Management (see above), right-clicking and selecting “Properties.” This will reveal a dialog box with multiple tabs, including one for general settings and more specific ones like Security and Sharing. And that’s about as much detail as this short space allows me. I don’t want to suggest any settings that might result in hard-to-troubleshoot Windows Server 2012 R2 printing problems such as driver conflicts, installation errors or spooler crashes.
In PrinterLogic, printer deployment and installation have the benefit of being both familiar and more efficient. If you already know how to add a printer to Windows Server 2012 R2, you’ll find PrinterLogic’s web-based GUI easy to navigate and intuitive. Yet the available options are more fine-grained and give you a much broader spectrum of control. What you’ll appreciate, too, is the centralized driver repository that makes installation, association and removal of print drivers a breeze. Furthermore, PrinterLogic is able to prevent the frequent driver conflicts that can cause printer installation issues and crash print spoolers, which in turn results in downtime and a surge in calls to the service desk from angry users.
Because PrinterLogic is able to eliminate print servers completely, it also eliminates all of the common Windows Server 2012 R2 printing problems while shrinking your infrastructure to a single-server solution that is able to deliver more functionality, higher availability and greater ease of use than Server 2012 R2 or any of its predecessors. PrinterLogic takes print management to a new level, so you and your support staff can stop worrying about how to configure a printer in Windows Server 2012 R2 and focus on other important tasks.
And if you’re still skeptical, remember than you can demo PrinterLogic for free. We also have a new software-as-a-service (SaaS) solution called PrinterCloud, which has all the same benefits but utilizes an advanced cloud-based platform.