2

Our ACCPACC administration software runs on an off-site dedicated hosted computer, running Windows 2003 Server with a completely different NT DOMAIN.

We have many users connecting to that computer remotely to perform administrative tasks such as printing cheques, printing invoices, printing POs, packing slips and so on. Basically the setup is that we are all connecting using Remote Desktop Protocol (local computers are Mac OS.X, XP SP3, Vista and Windows 7).

At our office we have a DOCUCOLOR 242 printer. When printing from the ACCPACC software, it prints to the local printer in our office. This is because we are using RDP features to connect printer ressources to the remote computer.

This almost works now. I had to install the printer driver software on the remote 2003 Server for the printer sharing to work. Now, everyone is able to print black and white but color is out.

NOTES:

  • Normal users on that Windows 2003 server are running as part of a Group Policy Object to restrict what can be done.
  • I took one of these normal users and gave him all domain administrator rights, no effect still B&W only.
  • I took this account and moved it OUT of GPO policies, as a normal account instead, no effect still B&W only.
  • It seems only MY account (which is domain administrator AND a normal account not part of the GPO objects) can actually print with color. This is the account that was used for installing the printer driver software.

How can I manage to get everyone to print in color?

Any suggestions as to what to try next?

2
  • Can they print locally in colour?
    – Sam Cogan
    Commented Aug 3, 2009 at 18:20
  • Yes they can. Their local printers settings are set by default to use color. Commented Aug 4, 2009 at 1:42

2 Answers 2

1

Did you install the PCL6 or PCL5c driver? The 'c' in PCL5c stands for colour. You may also be interested in the Xerox Global Driver (it's for network deployments), and make sure that the print drivers installed locally match up to the print drivers installed remotely.

Check the event logs for print driver mismatches: http://support.microsoft.com/kb/239088

Someone has already suggested Server 2008 but if you don't want to spend $$$$$$$ (just $$) you might be better off using thinprint.

EDIT: Are you sure the print properties on the remote server are correct? I've seen a few printers where you have a dropdown hidden in the printer properties that contains "Auto" and "Black and White", "Auto" being colour.

1
  • We switched to ThinPrint. It's great. Commented Apr 12, 2010 at 5:08
-1

Upgrade to Windows Server 2008?? http://technet.microsoft.com/en-us/library/cc753853%28WS.10%29.aspx Seems that with 2008, you will have full printing capabilities.

2
  • TS EasyPrint is not perfect just yet. If you match up Windows 7 and Server 2008 R2 it works like a dream, but on Windows XP and Vista there are some formatting issues, as well as legacy print drivers not playing well. Commented Feb 3, 2010 at 6:34
  • That's a BIG solution to what should be a small problem... Commented Apr 12, 2010 at 5:08

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .