> Thanks for the feedback.
> I'd have to map back to a printer on the PC, not one of the network
> devices. The accountants have personal printers for confidentiality
> and check runs.
> Perhaps add a user id test to the login script? If user = xxxxx and
> login location = yyyy then map printer. Wouldn't want everyone in the
> office using the private printer.
> Does that sound reasonable?
> On Thu, 11 Dec 2008 21:27:30 -0000, "Anthony [MVP]"
> <anthony[ at ]no-reply.com> wrote:
>>What you could do is, in Terminal Services, only enable printing to mapped
>>"Marten" <absolute88[ at ]hotmail.com> wrote in message
>>news:ruc2k4d2ofs7vagdeuvpvuoukrmrioah0j[ at ]4ax.com...
>>> We are a multi site organization running 2003 Standard domain
>>> controllers at each site. All DCs are in the same domain and therefore
>>> sharing the AD. Each office has its own networked printers and I
>>> haven't had to worry too much about printing issues before. But one
>>> has arised that hopefully I can get some suggestions for.
>>> Our accounting systems is running through terminal services from head
>>> office. Lately, one satellite office has been acidentally printing
>>> confidential info to anther satellite office's printers.
>>> What I would like to do is set up printer security so that people who
>>> have logged in at a site can use the regional printers. While I do
>>> have a security group defined to list each site's native users
>>> (Site1-Home), I can't completely restrict the printers based on that
>>> as staff do travel between offices and will need to use the those
>>> regional printers when visiting.
>>> There is another regional security group that defines who in each
>>> office can use the accounting system (Site2-Acct). I could deny other
>>> sites' accountingf groups from the printer, but wouldn't that also
>>> block the user when visiting and not using the accounting system?
>>> Any suggestions?