Were these autocreated printers or mapped network printers? The former can be deleted from the console easily, the latter could be removed via a script that enumerates printers and deletes any with a specified server name. Puzzled about the permissions. If they can map new printers, I don't know why they wouldn't be able to delete old ones. Have you tried restarting the spooler service? CW On 6/2/05, Chris McNally <cmcnally@xxxxxxxxxxxxxxxxxxx> wrote: > I have a number of orphaned printers in user sessions, left over from > moving the printers to new servers. Users are unable to delete the old > printers and it is causing confusion, they get an access denied but I > can't find where to tweak the permissions. Can someone point me in the > right direction please. > > ******************************************************** > This Weeks Sponsor: ThinPrint GmbH > Now available: The new version .print Engine 6.2 with SSL encryption > and certificate management. > http://www.thinprint.com > ********************************************************** > Useful Thin Client Computing Links are available at: > http://thin.net/links.cfm > ThinWiki community - Excellent SBC Search Capabilities! > http://www.thinwiki.com > *********************************************************** > For Archives, to Unsubscribe, Subscribe or > set Digest or Vacation mode use the below link: > http://thin.net/citrixlist.cfm > ******************************************************** This Weeks Sponsor: ThinPrint GmbH Now available: The new version .print Engine 6.2 with SSL encryption and certificate management. http://www.thinprint.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm ThinWiki community - Excellent SBC Search Capabilities! http://www.thinwiki.com *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm