Netware 6.5 Sp6
200 printer agents all with bespoke Pcounter print charging parameters.

As I stated in a previous post

We have about 130 secure printer agents running on one print manager.

We need to duplicate these printer agents onto another server with a
print manager, giving them a slightly different name AND making them

It was pointed to pagen.exe as a great tool for doing this. The problem
with this tool is that it takes a dumb csv file and recreates the
database. We use Pcounter print charging, and this adds extra blocks of
info to the NDPS database, and this needs to be preserved in the
duplicated system, as it would take a long time to manually input all of
the charging paramaters in again per printer. These Pcounter bits are
not in the csv file.

I have come up with a working solution as follows -

setup - one tree, two servers, one running print manager 1 and the
other print manager 2.

Print manager 1 holds the current working set of secure Pcounter enabled
printers and we need to get a complete copy of these printers to print
manager 2, with all pcounter info intact.

1) Unload print manager 1, and backup the NDPS folder associated with
this manager.
2) Use console one to export the LDIF of print manager 1 (we will call
this LDIF 1)
3) Edit the PADBTXT.CSV file from print manager 1, and use perl or some
other method to append the 'printer agent name' and 'NDS printer object'
with a 'u' or some other character after the printer name to denote it
is insecure, and to rename. Also set the 'SSL required' field from 1 to 0.
4) Reload print manager 1.
5) Use pagen.exe against the newly edited csv file and create the new
set of printers in print manager 1.
You should now have your original set of 'pcountered' printers plus a
'dumb renamed copy' of the printers in print manager 1 (ie without the
Pcounter bits).
6) Unload print manager 1
7) Use console one to export the LDIF of print manager 1 (we will call
this LDIF2).
8) use perl or another method to change the printerToPAIDMappings so
that the newly created printers point to the original printer locations
in the NDPS database. this can be achieved by putting appending the 'u'
or other character you chose in step 3 to the original printer agent
name in this field and then deleting the duplicate for example -

This -

printerToPAIDMappings: cn=au4,ou=printers,ou=csi,ou=cs,o=pwf#1181146995#1
printerToPAIDMappings: cn=au4u,ou=printers,ou=csi,ou=cs,o=pwf#1181202823# 1

becomes -

printerToPAIDMappings: cn=au4u,ou=printers,ou=csi,ou=cs,o=pwf#1181146995# 1

9) use console one to rename print manager 1 and then import the edited
LDIF2 file.

10) Load print manager 1

11) Run the server consolication utility (the print manager 1 console
will still show the duplicate printer agents you created, but SCU will
only show one set as you deleted the duplicates from the LDIF file
before recreating print manager 1)

12) migrate the printer agents from print manager 1 to print manager 2

13) SCU preserves the Pcounter info in the NDPS database and so print
manager 2 will now have all of you printers with correct pcounter settings.

14) unload printmanager 1

15) Use console one to rename print manager1 and import LDIF 1 (from step 2)

16) restore the backed up NDPS directory from step 1 to the server
running print manager 1 (where it originally came from)

17) load print manager 1

18) print manager 1 will now be running all your printer agents with
pcounter bits working.

What you have achieved is two servers in the same tree running the same
printers with all charging parameters intact. The print managers
printers are the same names on the console (think of it as an alias
name), but they actually point to different NDPS printer objects in the