Windows Forum

Ask something
Discussion Locked

Citrix Printing Only Domain Admin can pr

0 helpful
6 replies

by paul

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Thru Wordpad all can print. In a product we have installed only Domain Admins can print. The server is a member server. All is okay. Everyone has change rights to the system32 and temp folders. They have full control on the spool folder. Ran Regmon.They get Denied Access on spoolss.exe. They have FULL rights to the file. I've tried "local" accts and nada. ONLY Dom. Admins can print. HELP. URGENT. I have an MCSE, been on the phone with Citrix AND Microsoft. To the winner is 750 points.

6 replies

by dc1

Do the users have rights to the print driver that they are trying to use?

by stillatit

As I understand you, any user can use Wordpad to print a document. This indicates to me that the printer, printer driver, spooler, etc., are all working and all have proper permissions for all users.

If that is the case, looking at the product you have installed, here are some basic questions. Answering them may bring you to an answer:
a) What is the product intended to do?

b) When the product was installed, did it insist on defining a printer at that time?

c) With Citrix, typically if a user on a fat client logs in and has local or network printers defined, those printers are automatically enabled on the user's Citrix session. Is this happening correctly? Can users print wordpad documents to these printers? Can your product print to these printers?

d) Does the product try to write information into its own directory? If so, do all users have appropriate rights to this directory? (You can find this out by logging on as a domain admin admin, printing something from the product, then doing a find on hard disk for all files modified in the last 1 day. If anything in that directory shows up, you have your culprit.)

Good luck.

by stillatit

One more thing just occurred to me. Pick a normal user, turn all auditing on for that user, have the user try to print, and see what failures log. Don't forget to turn the auditing back off when done.

This discussion is closed to new replies.