Article
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.
First, download the Softerra LDAP Browser from http://www.softerra.com/download.htm. Next you need to create a connection to an eDirectory server which contains a partion of the ou where the existing NDPS printers exist. Next we need to export some data that we will manipulate later. So from the export menu, select LDIF.

Next fill out the export form with the following information:
Note that we are only exporting the nDPSPrinterInstallList attribute. Once the export is complete, open the file in your favorite text editor. TextPad and UltraEdit are two that will allow multi-line editing and this is a requirement for this process. Here is a first look at what the export looks like.
The first thing we want to do is remove the line breaks. The following Replace Operation in UltraEdit will do this for us. We are literally searching for a line break followed by a space, followed by some other data. We are replacing that with the data following the space.
Once this query is complete, this is what we have.
As you can see, we still have some cleanup to do. Our next replace function will remove the line break which shows in the above shot as a small square. The best way to do that is to highlight the square and then hit CTRL-R for replace. This is the result.
Next we need to remove the _NW using the following replace function.
Here we are literally searching for _NW and replacing it with nothing. Finally, we need to change the attribute name from nDPSPrinterInstallList to iPrintICMPrinterList
Now all we have to do is use the file to get the information back into eDirectory. Copy the file to your linux server. Then run the following command from the server.
ldapmodify -x -s eDirectoryServerIP -D cn=admin,o=org -W -f filename
Now you should be able to go into iManager and select a user and their old printers should be reflected as new iPrint Printers. As long as they have the iPrint client already installed, the next time they log into eDirectory, the new printers should be pushed down to them.
Watch for another article coming soon on how to use ldap to set the Default Printer for them.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
Re: Forcing Printers to Users after iPrint Migration
Submitted by ecyoung on 23 February 2010 - 12:19pm.
I took part in the beta for iPrint Client Management (ICM). That was back in May 2006. I'll never understand why Novell felt it was necessary to create brand-new schema for ICM, rather than re-using the NDPS RPM schema. Because of that decision, we ran into this problem (NDPS RPM printers do not get migrated to iPrint ICM). We waited a couple years for Novell to address this, but then moved on to a non-Novell solution. Hopefully your article will be helpful to someone else.
- Be the first to comment! To leave a comment you need to Login or Register
iPrint Migration
Submitted by mbruner1 on 23 February 2010 - 12:51pm.
I can honestly say that the newest miggui does a good job of at least getting the printers migrated. The key to at least getting the printers to migrate is to have a r/w replica of the container on the target server prior to attempting to migrate the printers. However, I've not been able to successfully migrate the print drivers. Therefore, manually copy the drivers over to the OES2 box and then use the cool tool script to insert the drivers. After that, I simply have to go to each printer and select the right driver. It is still not perfect, but it is a heck of a lot better than having to re-insert every single driver into the driver store. I hope that helps.
Michael
- Be the first to comment! To leave a comment you need to Login or Register









2