Can I install PaperCut on a Domain Controller?

KB Home   |   Can I install PaperCut on a Domain Controller?

Main.InstallingPaperCutonDomainController History

Hide minor edits - Show changes to output

July 10, 2018, at 06:53 PM by Aaron Pouliot - Fixed with input from Alan
Changed line 16 from:
We have heard it on good authority and seen several anecdotes firsthand that configuring a print server as a Domain Controller can cause issues†. Apparently the act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail in specific scenarios.
to:
We have heard it on good authority and seen several anecdotes firsthand that configuring a print server as a Domain Controller can cause issues. Apparently the act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail in specific scenarios.
July 10, 2018, at 06:52 PM by Aaron Pouliot -
Changed line 22 from:
If you only have physical Windows server that acts as a domain controller, and cannot add any other physical servers, then add the Hyper-V role and set up a virtual machine  to act as a dedicated print server. This is a no-cost solution that won't require purchasing any additional licenses from Microsoft and uses your existing infrastructure.
to:
If your only Windows server is the domain controller and you cannot add any other physical servers, then consider adding the Hyper-V role to this server so that you can set up a virtual machine to act as a dedicated print server. At the time of this writing, a Standard Windows Server license allows you to set up two additional Windows servers as virtual machines. This is a no-cost solution that won't require purchasing any additional licenses from Microsoft and uses your existing infrastructure.
July 10, 2018, at 06:29 PM by Aaron Pouliot - Added examples from Microsoft's forum as a footnote.
Changed lines 33-35 from:
†https://social.technet.microsoft.com/Forums/ie/en-US/b351ce18-3847-477a-93b3-4746cbd7d14b/print-server-problem-after-dcpromo?forum=winserverprint,
https://social.technet.microsoft.com/Forums/ie/en-US/735dd476-ebaa-47b1-9d6b-01662b04e54d/access-denied-creating-local-port-server-2012-only?forum=winserverprint,
https://social.technet.microsoft.com/Forums/ie/en-US/3fcb8b97-f66c-45ce-ab42-32e4c47fbd43/migrated-to-2012-no-one-can-print-now?forum=winserverprint
to:
† Firsthand examples from Microsoft's forum: 
* https:
//social.technet.microsoft.com/Forums/ie/en-US/b351ce18-3847-477a-93b3-4746cbd7d14b/print-server-problem-after-dcpromo?forum=winserverprint
* https://social.technet.microsoft.com/Forums/ie/en-US/735dd476-ebaa-47b1-9d6b-01662b04e54d/access-denied-creating-local-port-server-2012-only?forum=winserverprint
* https://social.technet.microsoft.com/Forums/ie/en-US/3fcb8b97-f66c-45ce-ab42-32e4c47fbd43/migrated-to-2012-no-one-can-print-now?forum=winserverprint
July 10, 2018, at 06:26 PM by Aaron Pouliot - Added category Implementation, links
Changed lines 16-18 from:
The act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail in specific scenarios.

to:
We have heard it on good authority and seen several anecdotes firsthand that configuring a print server as a Domain Controller can cause issues†. Apparently the act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail in specific scenarios.
Changed lines 29-35 from:
[-Keywords: Domain Controller, DC-]
to:
''Categories:'' [[Category.Implementation|+]]
----
[-Keywords: Domain Controller, DC, Mobility Print-]
----
†https://social.technet.microsoft.com/Forums/ie/en-US/b351ce18-3847-477a-93b3-4746cbd7d14b/print-server-problem-after-dcpromo?forum=winserverprint,
https://social.technet.microsoft.com/Forums/ie/en-US/735dd476-ebaa-47b1-9d6b-01662b04e54d/access-denied-creating-local-port-server-2012-only?forum=winserverprint,
https://social.technet.microsoft.com/Forums/ie/en-US/3fcb8b97-f66c-45ce-ab42-32e4c47fbd43/migrated-to-2012-no-one-can-print-now?forum=winserverprint
July 10, 2018, at 06:11 PM by Aaron Pouliot - Added input from Alan Morris.
Changed line 16 from:
The act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail.
to:
The act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail in specific scenarios.
July 10, 2018, at 06:10 PM by Aaron Pouliot - Added some input from Alan.
Added lines 15-18:
!!!!3. Domain Controllers just don't make good print servers
The act of promoting a server to domain controller resets the permissions on the Windows spool folder and will interfere some rendering tasks necessary for Windows printing, causing print jobs to fail.

Added lines 22-23:

If you only have physical Windows server that acts as a domain controller, and cannot add any other physical servers, then add the Hyper-V role and set up a virtual machine  to act as a dedicated print server. This is a no-cost solution that won't require purchasing any additional licenses from Microsoft and uses your existing infrastructure.
April 02, 2018, at 05:07 PM by timg - formatting
Changed lines 3-4 from:
"''We're new to PaperCut and we're trying to decide where to install the PaperCut software. Can we install it on our Domain Controller?"''
to:
Q: We're new to PaperCut and we're trying to decide where to install the PaperCut software. Can we install it on our Domain Controller?
Changed line 9 from:
!!!1. It muddles up your infrastructure
to:
!!!!1. It muddles up your infrastructure
Changed line 12 from:
!!!2. It won't work with Mobility Print
to:
!!!!2. It won't work with Mobility Print
Changed lines 15-16 from:
!!So what should I do instead?
to:
Q: So what should I do instead?
Changed lines 19-20 from:
!!Still have questions?
to:
Q: Still have questions?
March 15, 2018, at 05:14 PM by Aaron Pouliot -
Changed line 9 from:
!!1. It muddles up your infrastructure
to:
!!!1. It muddles up your infrastructure
Changed line 12 from:
!!2. It won't work with Mobility Print
to:
!!!2. It won't work with Mobility Print
March 15, 2018, at 05:12 PM by Aaron Pouliot -
Changed lines 16-18 from:
Set up a dedicated print server in your environment to install PaperCut on. This can be a virtual machine or an old desktop.

Separating
out server roles in your environment onto separate machines is widely regarded as common sense. Installing PaperCut on a separate server just for printing will give you piece of mind that printing and Active Directory won't adversely affect each other and will be much easier to troubleshoot if things go awry.
to:
Set up a dedicated print server in your environment to install PaperCut on. This can be a virtual machine or an old desktop.  Separating out server roles in your environment onto separate machines is widely regarded as common sense IT. Installing PaperCut on a separate server just for printing will give you piece of mind that printing and Active Directory won't adversely affect each other and will be much easier to troubleshoot if things go awry.
March 15, 2018, at 05:12 PM by Aaron Pouliot -
Added lines 2-3:

"''We're new to PaperCut and we're trying to decide where to install the PaperCut software. Can we install it on our Domain Controller?"''
March 15, 2018, at 05:10 PM by Aaron Pouliot -
Changed line 7 from:
!!It muddles up your infrastructure
to:
!!1. It muddles up your infrastructure
Changed line 10 from:
!!It won't work with Mobility Print
to:
!!2. It won't work with Mobility Print
Added lines 17-19:

!!Still have questions?
Let us know if  you need assistance! We're happy to help.  Feel free to leave a comment below to ask questions or [[https://www.papercut.com/contact/|reach out to us directly]] if you're unsure.  We can get you connected with experts to help you set up PaperCut in your organization in the best possible way.
March 15, 2018, at 05:03 PM by Aaron Pouliot -
Changed line 5 from:
While there are a number of scenarios where it would be perfectly okay to install PaperCut on a Windows Domain Controller, this is something that we would not recommend for a number of reasons.
to:
While there are a number of scenarios where it would be perfectly okay to install PaperCut on a Windows Domain Controller, this is something that we would not recommend for a number of reasons which we've detailed below.
March 15, 2018, at 05:03 PM by Aaron Pouliot -
Added lines 15-16:

Separating out server roles in your environment onto separate machines is widely regarded as common sense. Installing PaperCut on a separate server just for printing will give you piece of mind that printing and Active Directory won't adversely affect each other and will be much easier to troubleshoot if things go awry.
March 15, 2018, at 04:56 PM by Aaron Pouliot -
Changed lines 1-2 from:
(:title Should I install PaperCut on a Domain Controller?:)
to:
(:title Can I install PaperCut on a Domain Controller?:)

Yes... but that doesn't mean it's a good idea.

Changed lines 8-9 from:
Imagine if you start having a problem with your print server or have to upgrade, and need to reboot the server.  What normally should be an easy and simple operation now gives you gray hairs because you have to worry whether your users will still be able to log in, or whether your Domain Controllers will continue to replicate successfully.
to:
Imagine if you start having a problem with need to install updates and need to reboot the server, or have a problem that requires taking the print server offline temporarily.  What normally should be an quick and easy job now gives you gray hairs because you have to worry whether your users will still be able to log in, or whether your Active Directory will continue to replicate successfully.
Changed lines 11-12 from:
Domain Controllers also often need to act as DNS servers. When the Mobility Print application and the DNS service are both running on the same machine, they will often end up fighting over the traffic on port 53, with mixed results.  Just don't do it.
to:
Domain Controllers often also act as DNS servers. When the Mobility Print application and the DNS service are both running on the same machine, they will often end up fighting over the traffic on port 53, with mixed results.  Just don't do it.
Changed line 14 from:
Set up a dedicated print server in your environment to install PaperCut on. This can be a virtual machine or an old desktop, either would be better than installing it on the Domain Controller.
to:
Set up a dedicated print server in your environment to install PaperCut on. This can be a virtual machine or an old desktop.
March 15, 2018, at 04:36 PM by Aaron Pouliot -
Changed line 1 from:
(:title Should I install PaperCut on a Domain Controller? Title:)
to:
(:title Should I install PaperCut on a Domain Controller?:)
March 15, 2018, at 04:32 PM by Aaron Pouliot -
Added lines 1-15:
(:title Should I install PaperCut on a Domain Controller? Title:)

While there are a number of scenarios where it would be perfectly okay to install PaperCut on a Windows Domain Controller, this is something that we would not recommend for a number of reasons.

!!It muddles up your infrastructure
Imagine if you start having a problem with your print server or have to upgrade, and need to reboot the server.  What normally should be an easy and simple operation now gives you gray hairs because you have to worry whether your users will still be able to log in, or whether your Domain Controllers will continue to replicate successfully.

!!It won't work with Mobility Print
Domain Controllers also often need to act as DNS servers. When the Mobility Print application and the DNS service are both running on the same machine, they will often end up fighting over the traffic on port 53, with mixed results.  Just don't do it.

!!So what should I do instead?
Set up a dedicated print server in your environment to install PaperCut on. This can be a virtual machine or an old desktop, either would be better than installing it on the Domain Controller.

----
[-Keywords: Domain Controller, DC-]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on July 10, 2018, at 06:53 PM
Printable View   |   Article History   |   Edit Article