I am with a start up company trying to put together a design for a
network. We are going to be using Server 2003 R2 on a HP server.
I would like to know what upside and/or downside there is to having a
print server on a domain controller, or is it better to partition a
drive on the server and set up a print server on it?

i look forward to your response

Thank you for your and support

I see no issue with using a DC as your print server.
I am not following you on the seperate partition idea.
You would have to choose another server to be the
print server not another drive.
<jsdranger@hotmail.com> wrote in message news:
>I am with a start up company trying to put together a design for a
> network. We are going to be using Server 2003 R2 on a HP server.
> I would like to know what upside and/or downside there is to having a
> print server on a domain controller, or is it better to partition a
> drive on the server and set up a print server on it?
>
> i look forward to your response
>
> Thank you for your and support
>

I think his question about disk space is the issue that a very active
print server could use a lot of disk space in the spooling process,
which would me a major disaster if it caused the sys volume to run out
of space. As with most Windows server, having two partitions, one for
sys, one for other data, is the best way to go. I would make sure your
print server uses space on the non-system partion. Typically, I allow
myself 1GB of space for spooler usage.

But I agree, there is typically no issue with using a DC for a print
server.