Publish client print queues as managed preferences?

Hello,
I followed the documentation from Papercut NG on Mac printing, section Publishing the printer via Workgroup Manager to get the defined print queues for my client machines published as managed preferences.
I set up the print queues on the server. On the client, I configured the server print queues using the local Administrator account and printed successfully a few test pages. I then logged in with an Open Directory account with admin privileges. I then open Workgroup Manager, select a Computer Group, click Preferences, select Printing. I enable Manage Always, but the list of Available Printers remains empty, contrary to what the screenshot tells me from the referred article.
Environment:
+ Snow Leopard Server 10.6.1 on a MacMini.
+ Snow Leopard 10.6.1 on a MacPro.
Am I missing something?
Ringo

Similar Messages

[Solved] Lightweight print queue manager recommendations?

My wife uses fluxbox and is very happy with it, but she is not really a command line user. However, once in a while she needs to look at her print queue and sometimes delete a print job. lpq and lprm are out of the question, although I suppose I could write a bash script for her to do that easily. Also, I don't want to confuse her with the cups interface as this requires root login to delete print jobs.
Anyone know of a small print queue GUI manager that is lightweight and does not require a load of KDE or Gnome libraries? I don't see one in the AUR that is not KDE based.
Last edited by lagagnon (2012-03-10 00:04:52)

lagagnon wrote:That requires root login and root password to delete stuff on the queue.
Are you sure? Looks like /etc/cups/cupsd.conf can be tweaked, e.g.:
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
Require user @OWNER @SYSTEM susan
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM susan
Order deny,allow
</Limit>
Where the user you want to allow is named, of course, susan.
This is in cups 1.4.8, anyway.

Printing w/Leopard & AD-based Windows Print Queues:

For those interested, I have written an overview of printing in Leopard 10.5.0 to Windows print servers (published queues Active Directory). Your mileage may vary. This document contains the good the bad and the ugly.
Objective:
Get Leopard based Macs to print to AD published SMB print queues hosted on Windows 2003 print servers. Sounds easy, huh?
Overview:
Print Servers:
Windows 2003 print servers.
Printers:
All the printers in my test were all new HP network b/w printers or network MFP b/w printers. All of them were less than 2 years old. None of them were consumer-grade home USB printers.
Mac Clients:
My test clients were Intel MacBook Pros and Intel iMacs running 10.5.0 Leopard. All of them had user AD accounts and all Macs were bound to AD using Directory Utility (or dsconfigad)
The AD clients have a unique naming convention at my company. In my environment we use the initials of the person for their login name (SAM). Example:
Real “human” Name: “Stephen Paul Jobs”
Long Active Directory Name: “Steve Jobs”
Short Active Directory Name: “spj”
“Legacy” NT Names: “domain\spj”
Full domain name (used for email etc): “[email protected]”
(you get the idea...)
Note: My Mac clients are not in an Open Directory domain. No “Magic Triangle” in this environment. Pure AD for the sake of this example. I am not managing the Mac clients via MCX in this scenario.
Print Protocols:
All the print queues hosted on the print servers were standard SMB/CIFS print queues. The syntax (UNC) looks like this:
smb://print_server.domain/queue
(This syntax is invisible to most users printing to AD-published printers (or any network based printer really) . Most users will have no idea what protocols are being used.)
Procedures:
Part 1: Set up a new printer from an existing AD-published print queue:
From the Apple menu select “System Preferences...” (or launch it from /Applications). The Printer Setup Utility app no longer exists. Apple has discontinued it fro various reasons.
Click on the Printer & Fax pane.
Click the “+” button on the left. This will launch the Apple Printer Browser (called “AddPrinter”, and lives in /System/Library/CoreServices), which looks similar to the previous browser in Tiger. The Printer Browser by default will usually show network printers vai Directory Services (AD/OD etc) as well as Bonjour printers and Mac OS X based shared printers – if they are shared via IPP and LPR under certain circumstances).
Select the desired AD-published print queue you want to print to by highlighting it in the browser list and clicking the “Add” button. (Note: Print queues published via Active Directory will show up as “Open Directory” printers, even though this is not 100% technically correct.)
Before the queue will be added, you will be prompted to authenticate as a local administrator. If you are not an admin you are screwed. Enter your name and password.
Once the print queue is added, it will show up on your Mac in several ways (barring any bugs – see below). Here are the ways to tell if you have added the print queue successfully:
A The new print queue will now be displayed in the Print & Fax system pref pane (but not always – see below).
B You will see a printer proxy application in ~/Library/Printers/ which corresponds to your new print queue. This is the print monitor app that will show up in your Dock when you print to the queue.
C You can see the new print queue via the CUPS admin page at http://localhost:631/printers.
D You can see your new print queue from the Terminal by typing this command: “lpstat –v” (type “man lpstat” for more info on the lpstat and related commands)
E You can also see your printers by launching an print-enabled application such as TextEdit or Safari and printing a page. You will be presented with Leopard’s new print dialog box (which now includes a print preview pane). From the “Printer” drop-down menu you can see all of your printers. You can add a printer from here too (which takes you to the steps listed above)
(of course, most end users will only use option A listed above. The other options are more abstract and complicated)
Now that the AD print queue has been setup on your Mac, you can print to it (maybe).
Part 2: Printing to an AD-published print queue:
Open a document you want to print.
Choose “Page Setup...” from the File menu if you need to configure the job. (Optional)
Choose “Print” from the File menu.
From the Print dialog box, choose the desired print queue from the Printer menu
Click the Print button.
You will need to authenticate with a valid Active Directory username and password. You don’t have to have administrator credentials, but you have to verify that you are a domain member. In my environment, my Windows print server doesn't require authentication, but for some reason Leopard or CUPS makes you authenticate. (See below). Not only is this a major PIA, but the authentication dialog box itself is formatted to include the wrong credentials format for authentication in the first place.
Volia! Done. Easy huh? Not really. Read on for the ugly stuff.
My Complaints and Caveats:
OK, so here’s where I vent, complain and scratch my head. Join in on the fun.
Sometimes shared print queues don’t show up in the Print & Fax system preference pane after they have been added. I have no idea why. The local CUPS admin page (http://localhost:631) on my Mac test clients can see the connected queues, and the queues show up in ~/Library/Printers. The “lpstat –v” command shows the connect queues too. But for some reason, sometimes network print queues that I have previously setup (and use regularly) don’t show up in the Leopard Print & Fax preference pane. Local USB printers always show up fine for me.
2. When challenged to authenticate a print job to a Windows print server (AD), the Mac’s authentication dialog box pre-populates the AD user’s name in the “Name” field incorrectly. Example:
A user named “Joe Is Cool” (short name “JIC”) prints a job to the print server. The print auth dialog box challenges him for a name and password. It is pre-populated already with the name of “Cool, Joe”. When a valid AD password is entered, the job is rejected (it fails authentication and gets put on hold – which is hard to see this unless you explicitly look at the Printer.app proxy tool in the Dock). However, if the user replaces “Cool, Joe” with his official AD short name of “JIC” and then enters his AD password, the print job is accepted and printed. I wish Apple didn’t try and pre-populate the dialog box! Can this be avoided or prevented?
In my environment, my Windows print server doesn't even require authentication, but for some reason Leopard or CUPS makes you authenticate. I’m working with my Windows administrators to figure this out. It will only accept user names with the short name format. It will not accept long (full) names or NT legacy names.
3) The Printer Setup Utility app, which used to live in /Applications/Utilities, no longer exists. Apple has discontinued it for various reasons. Mainly security and simplicity. I wish it was still available, but the system pref pane works fine (well, usually)
4) Active Directory-based print queues will show up in the OS X Printer Browser as “Open Directory” printers, even though this is not 100% technically correct. Why can’t OS X tell the difference between OD queues and AD queues and label them as such?
5) Leopard has locked down the ability to add network printers. You now must be a local administrator in 10.5 or later. I understand the importance of this security measure in certain environments, but why can’t there be an option in the Security preference pane to “Allow non-admins to add printers”? This would make me very happy.
6) Setting the default printer and resetting the CUPS system now require you to right-click in the left side of the Print & Fax pane. There no longer is a button or menu option to do this.
7) Sometimes after a job has printed the printer proxy app (from ~/Library/Printers) stays in the Dock and won’t go away.
Conclusion
Please chime in on your experiences, bugs, opinions and comments.
Message was edited by: Daniel Stranathan

I have noticed several of the changes in our system when printing to an AD printer from a Leopard client. I have one issue that is pretty odd and I'm not sure what is going on. When printing an Excel worksheet, I get prompted for AD credentials. After submitting the job, the print queue says "Waiting for Authentication", I have to press the Resume button and then the authentication dialog pops up. I successfully authenticate (My auth dialog is populated correctly and the remember to keychain option is selected) and the job prints fine. If I print the same document again (without closing the worksheet or Excel), or any other worksheet, I still have to reauth. I can print just fine to the same printer from Textwriter and I do not need to authenticate. Weird...

Server Print Queue Clogging

Hi, I am running Leopard Server in a small office with mixed Windows XP, Vista and Mac 10.6 clients. I am not an IT administrator, but I own the company and have been teaching myself on a DIY basis. These forums are a very helpful source of information for me.
We have a DELL MFP 1600n printer connected to the server via USB. Users can print to the printer. However, very frequently, the print queue will get clogged or jammed and the network printer will go into a paused state. It usually happens when a user tries to print a PDF or .jpg file. I resolve the problem by going manually into the print queue through System Preferences on the server and deleting the PDF or jpg, clicking resume, and then the remaining docs in the queue usually print as normal.
I don't see why I am getting so many frequent clogs/jams in the first place -- the Dell specs show it has 32MB of RAM so shouldn't it be able to handle a moderately large PDF?
Is there a special method for configuring printer services on Leopard Server that will help resolve this problem? Do I need a different printer?
Also, can I assign a user limited privileges that would enable him/her to go in and clear the jammed print queue without giving full access to everything else on the server? Currently, only I can do it and it is a hassle because it needs to be done at least once per day.

Magnify your issue by 145 and that is what I've been dealing with. I'm running a print server with 145 printers and 1800 users, and until recently, I've had to periodically clear the queues and un-pause the printers. Huge PITA.
I still don't know what is causing certain jobs to pause the printers, but here's how I am managing the symptoms to this problem.
Create a launchdaemon to run periodically (mine runs every 120 seconds)
Have it run a script with the following two lines:
cancel -a `lpstat -t | grep disabled | awk '{print $2}'`
cupsenable `lpstat -t | grep disabled | awk '{print $2}'`
The first line cancels all jobs in paused printers.
The second line re-enables any paused printers.
It won't stop certain jobs from hanging the printer, but it will "un-stick" them and eliminate the huge backlog of jobs that pile up as a result of it being paused all day.
FYI...we are running mostly Xerox Phaser 8550 and 8560 printers.
Hope this helps.

HP 8620 all-in-one: scanner becomes unavailable in print queue window when computer sleeps

I just bought a new printer/scanner/fax - HP 8620 all-in-one. I have Mac OSX 10.9.3 and the most up to date drivers/software from the HP website (april 2014). I have connected the printer via ethernet cable to our wireless router. I have installed as per intructions.
When my computer goes to sleep, or the printer goes to sleep, I will return to the computer to find that the "scanner" is not available (ie greyed out when I go to "open scanner" in the print queue or system preferences, or try to use "HP scan". I tried a few things, like uninstall/reinstalling, and have worked out that if I reboot my computer the scanner option seems to "whiten" again (ie become available).
Is there a way to prevent this happening???? I don't have time to be rebooting every time I need to use the scanner!

You can't use the scan button on the printer. You have to start the scan from OS X.
See this:
Mac Basics: Using a scanner
http://support.apple.com/kb/ht4505
Austin

Print Queue Management via Server Admin not working

We have Xserves (10.5.8) running the Print Service for queue management to our printers. Clients print through the server just fine.
When the printer jams or is otherwise paused, print jobs pile up in the queue as expected. The queue can be seen and managed by logging into the server, going to Server Preferences/Print & Fax and selecting the print queue.
However, when the queue for the paused printer is viewed within Server Admin/Print, the queue shows as empty and therefore can't be managed. We want to use Server Admin for this function because:
1) Server Admin can be run remotely on a workstation, so no login to the server required.
2) We can assign Print Service management rights to select non-admins so they can manage the queues.
Any ideas on why Server Admin fails to show spooled jobs? Is it working for anyone else?
I am using Server Admin version 10.5.3 which are the latest available that comes with Server Admin Tools 10.5.7. We had been running 10.5.7 on the Xserve and it didn't work then either.

Here's a bit more information about our setup and our experiences with Apple's CUPS implementation:
On the server, all printer queues are set up with only lpr and ipp sharing enabled with the PPD setting for each printer set to Generic Postscript. We found that setting the PPD to the printer specific one on the server caused problems when clients tried to use printer specific options, like paper tray selection, etc.. The selection would be undone, apparently because the driver on the server would override the previous settings. Using Generic Postscript allows the client PPD settings to go through unmodified. Our printers are general a mix of HP LaserJets and some Sharp Copiers.
All clients use lpd to the server queues with the printers' actual PPDs configured. Using ipp is superior in that printer feedback (jams, out of toner, etc) makes it back to the clients, but ipp only works when the client, the server, and the printer are on the same network. If the ipp client is not on the same network, the client spooler immediately goes into a paused state and the print job is stuck on the client.
Using lpd to the server queues works reliably, but there is no feedback to the client. Jobs disappear from the client queue and go to the server, appearing to the user as a successful print. If the printer is down, there's nothing they can see or do about it.

Is the print server over-writing client printing preferences with defaults?

I'm testing a new 2012 R2 print server, and have set the printing defaults by clicking on the printer in Print Management and 'set defaults'. I used this to set things like double-sided printing etc.
When the printers are added to the test client workstations (manually, not by group policy), we then have to add in some details in printing preferences to authenticate that client to the printer. A valid access code, and print mailbox that tally with
the same settings on the printer. It's tedious, but that's what our current printers demand.
What's happening with the new 2012 R2 print server in testing is that it seems to be overwriting these authentication preferences and returning all the printing preferences to the defaults set on the print server.
It's likely that this is a feature or setting that I'm just not aware of, could anyone tell me please how to set those printing preferences as 'first time' preferences that can then be edited on the workstation, and persist?

Would you know of any resource where I could learn all the ins and out of printer management in 2012? A blog/a book/MVA course?
I assume you are using the General tab of the printer properties , then clicking Preferences to set the
Users defaults with the device specific data.
There are two ways to open up the Printing Preferences dialogue for shared printers that I'm aware of.
Open the Print Management console, open the print server, and printers. (1) Right Click on the printer and Set Printing Default or (2) Right Click on the printer, Properties, then from General Tab click Preferences.
Do changes made via both of those routes have the same affect regarding default settings that are given to the client or is there a difference between them?
I have been using method (1) above, but if there's any difference I'd be interested to know.
When it comes to adding the printers to the clients, there are also two options. (A) Control Panel, Printers, Add Printer, and add from directory. (B) In Windows Explorer, browse to the print server and double click the printer name to connect
it.
Is there any difference between those two routes? I had been using method (B), and then editing the preferences... when then seemed to be overwritten by the server defaults. Yesterday I used method (A) and so far the printing preferences for
the test clients have not yet been overwritten.

Kerberised printing to AD print queues from OD Clients

Hello,
I am trying to print to AD print queues from OS X 10.5.4 and my users keep getting requests for authentication. I heard that the printing to AD print queues was now kerberised and working in OS X leopard. The users are from the AD and log in fine with managed preferences from the Open Directory.
What do i need to do to get this working properly?
It is the only thing that is stopping me integrating OS X into my Active Directory.

Thanks for letting me know.
I did find the mentioned link. I also found a link on the apple-scripts forum as well which utilizes the same implementation but in a package form for a more user-friendly deployment.
It can be found here if you are interested:
[http://www.apple-scripts.com/forum/viewtopic.php?f=2&t=125&p=470#p470]
Again this does not work in leopard.
To get around this in the end i decided to use Papercut NG as all i needed to do was manage the print queues via quotas. This does the job nicely as it is cross-platform and keeps the quota system in one place. Great as i can now print to the os x server print queue from os x and print to the AD queues from Windows all with their own authentication systems.
Message was edited by: Newbie-2-macs

Changeing preferences on network printer queue with Powershell

Hi,
I found a script on this page - http://gallery.technet.microsoft.com/scriptcenter/878e6bac-e2a1-4502-9333-5b1420f8b957 - that I am trying to adapt to work on my users computers and not only on servers. But I can't seem to figure out how to get a reference
to the network attached printers and change their preferences on the computer, the script only get the local ones.
The goal is to use only a portion of the script as a logon script for some users that need onesided printing as default.
param ($ChangeProp)
$host.Runspace.ThreadOptions = "ReuseThread"
Add-Type -AssemblyName System.Printing
$permissions = [System.Printing.PrintSystemDesiredAccess]::AdministrateServer
$queueperms = [System.Printing.PrintSystemDesiredAccess]::AdministratePrinter
$server = new-object System.Printing.PrintServer -argumentList $permissions
$queues = $server.GetPrintQueues()
function SetProp($capability, $property, $enumeration)
if ($PrintCaps.$capability.Contains($property))
$q2.DefaultPrintTicket.$enumeration = $property
$q2.commit()
write-host ($q.Name +" is now configured for " + $property)
write-host (" ")
else
write-host ($q.Name +" does not support " + $property)
write-host (" ")
try {
foreach ($q in $queues)
#Get edit Permissions on the Queue
$q2 = new-object System.Printing.PrintQueue -argumentList $server,$q.Name,1,$queueperms
# Get Capabilities Object for the Print Queue
$PrintCaps = $q2.GetPrintCapabilities()
switch ($ChangeProp)
{$_ -eq "twosided"}
SetProp DuplexingCapability TwoSidedLongEdge Duplexing
break
{$_ -eq "onesided"}
SetProp DuplexingCapability onesided Duplexing
break
{$_ -eq "mono"}
SetProp OutputColorCapability monochrome OutputColor
break
{$_ -eq "color"}
SetProp OutputColorCapability color OutputColor
break
{$_ -eq "staple"}
SetProp StaplingCapability StapleTopLeft Stapling
break
{$_ -eq "show"}
$DefaultTicket = $q2.DefaultPrintTicket
$TicketProps = $DefaultTicket | Get-Member -MemberType Property
write-host (" ")
write-host ($q.name)
foreach ($p in $TicketProps)
$PName = $p.name
$PropValue = $DefaultTicket.$PName
write-host ($p.name + " = " + $PropValue)
default
Write-Host ("$_ is not a valid parameter")
exit
catch [System.Management.Automation.RuntimeException]
write-host ("Exception: " + $_.Exception.GetType().FullName)
write-host $_.Exception.Message

Ok, I want to run this (some...) script on a users computer, not on a server, to be able to change their printer preferences. In this case, a network attached printer with duplex default from the server would get simplex as default.
We don't want to set up different queues on the server for different default settings. That's why we are trying with a script.
Running your script against my computer gets me (trimmed down a bit):
Get-ServerQueues -server it228d
InPartialTrust : False
ClientPrintSchemaVersion : 1
IsXpsDevice :
IsPublished : False
IsRawOnlyEnabled : False
IsBidiEnabled : False
ScheduleCompletedJobsFirst : True
KeepPrintedJobs : False
IsDevQueryEnabled : False
IsHidden : False
IsShared : False
IsDirect : False
IsQueued : False
QueueAttributes : 528
QueueStatus :
FullName : \\it228d\Skicka till OneNote 2010
HostingPrintServer : System.Printing.PrintServer
QueuePrintProcessor : System.Printing.PrintProcessor
QueuePort : System.Printing.PrintPort
QueueDriver : System.Printing.PrintDriver
DefaultPrintTicket :
UserPrintTicket :
SeparatorFile :
Description : \\it228d\Skicka till OneNote 2010,Send To Microsoft OneNote 2010 Driv
er,
Location :
Comment :
ShareName :
NumberOfJobs :
AveragePagesPerMinute :
UntilTimeOfDay : 60
StartTimeOfDay : 60
DefaultPriority :
Name : Skicka till OneNote 2010
Priority : 1
CurrentJobSettings :
PrintingIsCancelled : False
Parent :
PropertiesCollection : {UserPrintTicket, IsXpsEnabled, Description, Name...}
InPartialTrust : False
ClientPrintSchemaVersion : 1
IsXpsDevice : False
IsPublished : False
HasToner : True
IsTonerLow : False
IsWarmingUp : False
IsInitializing : False
IsProcessing : False
IsWaiting : False
IsNotAvailable : False
IsOutputBinFull : False
IsPrinting : False
IsBusy : False
IsIOActive : False
IsOffline : False
HasPaperProblem : False
IsManualFeedRequired : False
IsOutOfPaper : False
IsPaperJammed : False
IsPendingDeletion : False
IsInError : False
IsPaused : False
QueueAttributes : 16
QueueStatus : None
FullName : \\it228d\PDFCreator
HostingPrintServer : System.Printing.PrintServer
QueuePrintProcessor : System.Printing.PrintProcessor
QueuePort : System.Printing.PrintPort
QueueDriver : System.Printing.PrintDriver
DefaultPrintTicket : System.Printing.PrintTicket
UserPrintTicket : System.Printing.PrintTicket
SeparatorFile :
Description : \\it228d\PDFCreator,PDFCreator,
Location :
Comment : eDoc Printer
ShareName : PDFCreator
NumberOfJobs : 0
AveragePagesPerMinute : 0
UntilTimeOfDay : 60
StartTimeOfDay : 60
DefaultPriority : 1
Name : PDFCreator
Priority : 1
CurrentJobSettings : System.Printing.PrintJobSettings
PrintingIsCancelled : False
Parent :
PropertiesCollection : {UserPrintTicket, IsXpsEnabled, Description, Name...}
InPartialTrust : False
ClientPrintSchemaVersion : 1
IsXpsDevice : False
IsPublished : False
IsRawOnlyEnabled : False
IsBidiEnabled : False
ScheduleCompletedJobsFirst : True
KeepPrintedJobs : False
IsDevQueryEnabled : False
IsPendingDeletion : False
IsInError : False
IsPaused : False
QueueAttributes : 528
QueueStatus : None
FullName : \\it228d\Microsoft XPS Document Writer
HostingPrintServer : System.Printing.PrintServer
QueuePrintProcessor : System.Printing.PrintProcessor
QueuePort : System.Printing.PrintPort
QueueDriver : System.Printing.PrintDriver
DefaultPrintTicket : System.Printing.PrintTicket
UserPrintTicket : System.Printing.PrintTicket
SeparatorFile :
Description : \\it228d\Microsoft XPS Document Writer,Microsoft XPS Document Writer,
Location :
Comment :
ShareName :
NumberOfJobs : 0
AveragePagesPerMinute : 0
UntilTimeOfDay : 60
StartTimeOfDay : 60
DefaultPriority : 0
Name : Microsoft XPS Document Writer
Priority : 1
CurrentJobSettings : System.Printing.PrintJobSettings
PrintingIsCancelled : False
Parent :
PropertiesCollection : {UserPrintTicket, IsXpsEnabled, Description, Name...}
But on my computer I have four network printers that is not listed. And those are the ones I want to change the preferences on. Is there a way to do this?

Client stops print queue

I have approx 150 Panther and Tiger clients, both using Ethernet and 802.11G, print-served by a G5 Tiger Server. Often, a client user unintentionally somehow manages to stop the print queue, stopping print-services to that particular printer altogether. In order to find the offending client, I need to go around to each client to look for a printer icon in the Dock with a red exclamation point. Once found, I can restart the print queue from this client.
My questions are:
1) None of my users are advanced enough to purposefully stop the print queue. Is there a keyboard shortcut or print menu item that is easy to push by mistake - in other words, how can it be that my users repeatedly manage to accidentally stop my print queue? And how can set up my client to prevent accidental stops?
2) Is there a way I can restart the print queue from the server? Finding the offending client again and again can get a little tedious, and requires me to be present and available to do so, as none of my users are trained to restart the print queue from client.
Any thoughts are appreciated.
Regards,
Sigurd
G4 iBook, G4 iMac Mac OS X (10.4.5)
iBook G4, iMac G4, OSX Server Mac OS X (10.4.5)

Ah! This is what I had running:
#!/bin/bash
# This program deletes files older than 1 hour in /var/spool/cups
# and older than 5 minutes in /var/spool/cups/tmp .
# It also repairs permissions on SAMBA spool (for Windows printer sharing)
/usr/bin/find /private/var/spool/cups/ -type f -mmin +60 -delete
/usr/bin/find /private/var/spool/cups/tmp/ -type f -mmin +5 -delete
chmod 777 /var/spool/samba
Combine it with..
#!/bin/bash
/System/Library/StartupItems/PrintingServices/PrintingServices stop
rm -R /private/var/spool/cups/*
mkdir /private/var/spool/cups/tmp
/System/Library/StartupItems/PrintingServices/PrintingServices start
/usr/bin/enable `lpstat -p | grep 'disabled' | awk '{ print $2 }'`
And it might take care of itself.

Client Replaced - Managed Preferences no longer working

An iMac on my network came down with a hardware problem, so I replaced it with a different unit. I removed the computer from Workgroup Manager, gave the second one the same name and re-bound it to OD. Workgroup Manager can see the system in the Computer List, and I can add it to the Computer Groups I need, but the managed preferences of the group don't push out to the new system. I've since tried renaming it, but the problem remains.
The groups are working with all the other Macs that belong to them and the new unit is bound in the exact same way - is there some residual of the old machine that OSX server isn't liking? I've been pulling my hair out over this one.

Hi
If you've had the logic board replaced the new board will have a different MAC address - obviously. Managing hardware using Computer Lists is actually done using the MAC addressess (ethernet hardware address). Its not enough to name it the same. You have to remove it completely from the Computer List and browse for it again. Better still make a note of the new MAC address and manually add it.
You can find the MAC addresses (as well as the IP addresses) of any networked mac/pc/printer etc by issuing:
ping 192.168.x.255
Or whatever IP address range you are using. Let it run for a few seconds. Use Control C to stop the ping and issue:
arp -a
This should list all IP addresses and associated MAC addresses. If you keep a list of which client computer name is associated with which IP address and MAC address then you should have a clearer picture of your network topology. This is better achieved if the Server is also the DHCP Server.
Tony

HT1338 I'm trying to follow HP's instructions to add a driver for HP Color Laserjet CP 1215 which is connected to my Time Capsule. However, in System Preferences I can't "add" the printer to the print queue because I don't have a driver and you have to se

I’m trying to follow HP’s instructions to add a driver for HP Color Laserjet CP 1215 which is connected to my Time Capsule. However, in System Preferences I can’t “add” the printer to the print queue because I don’t have a driver and you have to select a driver before the add button becomes active. Therefore, the Mountain Lion software update doesn’t add driver software for the CP 1215 driver because I was unable to add the printer to the print queue.

This printer doesn't seem to be supported in ML:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01664444&lc=en&cc=us&dlc=en &product=412187#N2043
You could try the 1515 driver or use the Generic PostScript Printer PPD when adding the printer.
Hope this helps.

Windows 2008 R2 Terminal Server clients lose remote printer queues after logoff

There are similar issues to this already on the forums but not precisely like this as far as I can tell, and I have tried all the fixes mentioned in those other threads.
Windows 2008R2 terminal server connecting to a 2008R2 print server. A script maps a connection to the print server on login. Users can browse the print server, connect to print queues to add them, and the queues work OK at first. As soon as they logoff/login
again, the queues still appear in their list of printers but cannot be selected for printing ('Print' button is greyed out).
Domain administrator users can print OK always; this is only affecting regular-user accounts, so it is probably a security/permissions issue. Print queues configured on the terminal server itself are OK, this only affects the queues on the
print server.
No errors are generated in the Event Logs. No failures seen for the print spooler or anything else.
I have added Everyone with Full Control to C:\windows\system32\spool on the terminal server. Tried giving full permissions to all in the printer properties. Cleaned out all registry keys in Client Side Rendering Print Provider as mentioned in some other
threads. In group policy, client printer redirection and LPT port redirection is allowed, use Easy Print driver first, and the print server is in the Intranet zone for low security. The issue happens for all print queues on the print server with a variety
of drivers so I don't think it is driver-related.

A bad GPO being applied ??
If you isolate a user, remove all GPO (even loopback's one), connect manually to a printqueue to make him install's one. Logoff and reconnect and check again if the printqueue work good. The only right that could block you is the driver's installation, but
I really sure that you don't have that issue (as it would be logged anyway)
The admin. account often have less GPO that apply to him.
MCP | MCTS 70-236: Exchange Server 2007, Configuring
Want to follow me ? | Blog:
http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

Java Print Queue Manager

I am new to Java. I recently ran into a need to have a Java print queue manager to handle network printers. Is something like this already available or are there companies who can provide this?
Please email me with any comments ([email protected]).
Thank you in advance for any help.
Regards,
JS

Have a look at javax.print API. I'll warn you, it's limited, but it can dynamically discover networked printers.

Print queue doesn't open (and preference button doesn't work either)

Okay, this has been my only problem since upgrading to Leopard and it's kind of annoying. For some reason I have not been able to get my print queues to ever open up since upgrading. I have three printers currently installed:
• Apple LaserWriter 16/600 (via local network)
• Brother MFC-3220C (USB)
• Dymo LabelWriter Twin Turbo (USB)
After printing I have yet to see the print queue come up for any of the printers. Also, if I go in to the System Preferences and click on the "Open Print Queue" button nothing happens whatsoever--no message, no window, nothing. I have tried resetting the print system and that has also had no effect on the problem. I have tried this on all of my printers and it just does not work correctly. I have also tried deleting the printers and re-adding them as well as fixing permissions, neither of which solved the problem.
If anyone has any insight in to why this is happening or what I can do to fix the problem, please let me know, I would like to be able to use the print queues again. Thank you!

John Blanchard1 wrote:
The printer preferences are stores in <home>/Library/Preferences, and they are the com.apple.print files. You could throw those away and see if things improve. Also, does this happen with all the printers? If so, and your printers are easy to re-add, you could go to <home>/Library/Printers and delete the printers there and then re-add them. When going to <home>/Library/Printers, you could see if double-clicking on the printers there launches the proxy.
Thanks for the information, however I finally found out what the problem was. After looking at it deeper, it appears that I had some weird owners & groups for a bunch of my user files which must have been causing the problems. Even though it was permissions related, Repair Permissions in Disk Utility wasn't catching the bad permissions or solving the issue, I had to hit all of my folders and files with chown and chmod in terminal to force change the owners and permissions. After doing all of that, I FINALLY have working print monitors...YES! So, in other words, if anyone else experiences this problem (I'm not sure why they would) please feel free to ask me how I finally solved it for a more in depth explanation.

Publish client print queues as managed preferences?

Similar Messages

Maybe you are looking for