The link you provided is not working
admin.millikin.edu/.../iprint-driver-copy-1.1.tar.gz

This worked awesomely!

There was a small typo in the script for vista64, so I resolved that and added support for win7 - the updated version is available from here

This scriptsfor me. I appreciate all efforts done around this as it will help with my migration project. My previous remarks were meant for the other script to migrate printer agents from Netware to OES2. I am not able to get that script to work. Has any one gotten this to work?

iPrint Linux XML Generator Script for moving printers from NetWare to OES Linux

www.novell.com/.../iprint-linux-xml-generator-script-moving-printers-netware-oes-linux

It worked for me. Thanks to Jmeldrum for writing the script and jareddbaber for submitting his comment which made the script work.

I needed to add a / after winXP to get this to work.
./iprint-driver-copy-1.0.sh -p /tmp/resdir/ENGLISH/Prndrv/winXP/ -r

I posted this in the wrong topic

After reading the instructions, I realized that some of the instructions were not very clear. I have modified the instructions to make them more clear. The -p should point to the place where the drivers were copied to. Let me know if it works for you.

All I get are lots of error messages that it cannot access /var/opt/novell/iprint/resdir/drivers/.... and that it cannot access resource.zip.

It would be nice if it worked bcause we didn't migrate, we setup a different Tree and moved all the users into it.

I'm more than a bit disgusted that OES2 has no printer drivers at all. We shouldn't have to migrate them. All the latest drivers should have been included!

There are advantages.

1. The migration fails and you would like to still copy over drivers and use the iPrint Linux XML Generator Script to import the printers. The only additional step would be that you would need to associate the driver with the printer agents through iManager. Here is the link for that script:

www.novell.com/.../iprint-linux-xml-generator-script-moving-printers-netware-oes-linux

2. You can also copy over drivers that are in a broker but are not currently associated to a printer agent. The regular migration utility does not copy drivers over in this type of situation.

You can also combine multiple brokers into one folder structure and then run the utility and it will get rid of all the duplicates drivers when the driver store loads. You now have consolidated multiple brokers into one driver store.

I can see where this could come in handy if something goes wrong, but are there any advantages to using this script over the general migration utilities?
P