During the iPrint migration, all of the drivers are migrated, the existing printers are renamed adding _NW to the end of the names, and the new iPrint Printers are created. The users assigned to the old printers are assigned to the new printers as well, but there is a caveat. That only allows the users to install the printers from the web page at http://serveraddress/ipp. It does not force install the printers for the users. Here is how you can work around this.
Let’s face the fact, assigning iPrint printers in iManager, especially if the users are in a different container than the iPrint Printer, can become very tedious and time consuming. First you have to wait for the browse window to choose a printer, then wait for the browse window to browse for the users or groups, and finally select all of your users. Well what if you had 5 executives that needed to have access to every Xerox Printer in the organization and these printers existed in multiple containers? Let’s say there were 35 of these printers. This could take hours. I’ll demonstrate how to do it in less than 5 minutes.
Gary Croxford has a simple tip for resolving a Java error that sometimes occurs when you load printer drivers in iManager.
Provides an internet protocol handler (prnt:) to install printers on Windows 2000/XP clients via an HTML page similar to Novell’s iPrint maps.
2 extra printer scripts, one that collects the number of printed pages since the last time the script was run, and another script that collects the number of jobs since last script run time. Can generated an event if defined thresholds are exeeded. Used for collecting information on printer usage. The scripts are modifyed copies…