Next to last task to migrate all our Novell files, Groupwise, applications, and Novell services from our 5.0 Server to a new 6.5 Small Business Suite is our legacy printing.
Brand new to NDPS Printing. We have set up iPrint, NDPS Broker, and iPrint Manager.
When we installed the NDPS Broker, all the Print Objects dissappeared from NWADMIN32. Kind of disconncerting, but printing is still working, and the objects are all now in iManager.
iManager has the function to migrate QMS to iPrint. We used it on one of our remote printers, connected to a port on an Extendnet 100x Printer controller. It looks like it has created the printer, and in the printer object, the spooling location is pointed to our new server SYS Volume. Is the setup complete for that printer?
We have done all this remote from our offices, (love Novell Remote Manager!) and are going on location to test it this afternoon.
The legacy objects for the printer are still in place. Does this mean that Spooling location and the Print Queue are not the same thing? Is the path for a print job using this setup going to be . . .
(1) Workstation (via IP) --> Spooling Locationon new server (via IP) --> Print Queue on old server (via IPX) --> Printer
or . .
(2) Workstation (via IP) --> Spooling Location on new server (via IP) --> Printer
If it is (1), then I have more work to do before I can down the old server and remove it.
Can anyone tell me if this is a legitimate way to convert our old Queue based printing? Have I missed something? It looks altogether too easy. I remember cautions somewhere that the print queues for legacy printing were married to the server they are created on.
Any help or comments greatly appreciated.
Paul Ray
Programming Languages -- .BAT Files
Preffered editor -- EDLIN
Brand new to NDPS Printing. We have set up iPrint, NDPS Broker, and iPrint Manager.
When we installed the NDPS Broker, all the Print Objects dissappeared from NWADMIN32. Kind of disconncerting, but printing is still working, and the objects are all now in iManager.
iManager has the function to migrate QMS to iPrint. We used it on one of our remote printers, connected to a port on an Extendnet 100x Printer controller. It looks like it has created the printer, and in the printer object, the spooling location is pointed to our new server SYS Volume. Is the setup complete for that printer?
We have done all this remote from our offices, (love Novell Remote Manager!) and are going on location to test it this afternoon.
The legacy objects for the printer are still in place. Does this mean that Spooling location and the Print Queue are not the same thing? Is the path for a print job using this setup going to be . . .
(1) Workstation (via IP) --> Spooling Locationon new server (via IP) --> Print Queue on old server (via IPX) --> Printer
or . .
(2) Workstation (via IP) --> Spooling Location on new server (via IP) --> Printer
If it is (1), then I have more work to do before I can down the old server and remove it.
Can anyone tell me if this is a legitimate way to convert our old Queue based printing? Have I missed something? It looks altogether too easy. I remember cautions somewhere that the print queues for legacy printing were married to the server they are created on.
Any help or comments greatly appreciated.
Paul Ray
Programming Languages -- .BAT Files
Preffered editor -- EDLIN