UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1369 views

NDPS to iPrint issues, installs NDPS first then converts to iPRint

NW6.5 server with NDPS printers. I just recently started to use iPrint.
Lets say I have a laptop that has the iPrint client installed. I
delete ALL of the printers on the laptop, then I restart the laptop and
login to netware. When the printers start pushing down, they are NDPS
printers and not IPP printers. Now I haven't changed anything in
imanager but I assumed that since the iprint client is installed, the
NDPS would just turn off and IPP would take over. Am I wrong? I am
still using NDPS printers on 100s of clients so I cant turn off NDPS all
together.
0 Likes
8 Replies
Absent Member.
Absent Member.


Do you happen to be automatically deploying NDPS printers using Remote
Printer Management at all?


--
Dave31

CNE 6 / CNE OES
0 Likes
Absent Member.
Absent Member.

Justin, you are wrong! The iPrint client does not "turn off" the NDPS
client - they are independent of each other. So you are right too!

Okay what you have is a case of two printer management agents installed on
one machine: the NDPS agent and the iPrint agent. There is nothing wrong
with this per se, but it is bad design (imo).

What can happen with both clients installed:
1. The NDPS client searches the user/container/group objects for NDPS
deliever printers. This is often referred to as Remote Printer Management
and the management tool for this is usually nwadmin. Okay, so NDPS finds
one or more printers and installs them if they are not already installed
on the workstation or if the adminstrator (you) has enabled the "Update
Driver" function in Remote Printer Management.

2. iPrint client can, if told to, upgrade any ndps client installed
printers to the iprint printer agent. The process of upgrading removes the
NDPS installed printer. Now we can get race and deadlock situations where
the two clients try to perform operations on the same thing at the same
time... Even if there is no race/deadlock what happens the next time you
login? NDPS checks for installable printers, finds them, installs them.
And what does iPrint do? Convert them. Rinse and repeat endlessly.

There are three solutions to this:

1. Remove the automatic updating of ndps printers, so that when an ndps
enabled client logs in it does not find anything to do. Workstations with
previously set up ndps printers will continue to work fine.

2. Remove the NDPS client from workstations that have the iPrint client.
Really it only makes sense to have just one print system, eh?

3. Disable iPrints automatic upgrade feature. Edit the file
\\iprint-server\sys\apache2\htdocs\ippdocs\iprint.ini, find the line
that says 'UpgradeNDPSPrinters=#' and change the value to 0 (do not
upgrade).

Hope that helps!

Ron Neilly
UBC Okanagan

On Tue, 18 Sep 2007 14:41:24 +0000, Justin wrote:

> NW6.5 server with NDPS printers. I just recently started to use iPrint.
> Lets say I have a laptop that has the iPrint client installed. I
> delete ALL of the printers on the laptop, then I restart the laptop and
> login to netware. When the printers start pushing down, they are NDPS
> printers and not IPP printers. Now I haven't changed anything in
> imanager but I assumed that since the iprint client is installed, the
> NDPS would just turn off and IPP would take over. Am I wrong? I am
> still using NDPS printers on 100s of clients so I cant turn off NDPS all
> together.

0 Likes
Absent Member.
Absent Member.

Ron Neilly wrote:
> Justin, you are wrong! The iPrint client does not "turn off" the NDPS
> client - they are independent of each other. So you are right too!
>
> Okay what you have is a case of two printer management agents installed on
> one machine: the NDPS agent and the iPrint agent. There is nothing wrong
> with this per se, but it is bad design (imo).
>
> What can happen with both clients installed:
> 1. The NDPS client searches the user/container/group objects for NDPS
> deliever printers. This is often referred to as Remote Printer Management
> and the management tool for this is usually nwadmin. Okay, so NDPS finds
> one or more printers and installs them if they are not already installed
> on the workstation or if the adminstrator (you) has enabled the "Update
> Driver" function in Remote Printer Management.
>
> 2. iPrint client can, if told to, upgrade any ndps client installed
> printers to the iprint printer agent. The process of upgrading removes the
> NDPS installed printer. Now we can get race and deadlock situations where
> the two clients try to perform operations on the same thing at the same
> time... Even if there is no race/deadlock what happens the next time you
> login? NDPS checks for installable printers, finds them, installs them.
> And what does iPrint do? Convert them. Rinse and repeat endlessly.
>
> There are three solutions to this:
>
> 1. Remove the automatic updating of ndps printers, so that when an ndps
> enabled client logs in it does not find anything to do. Workstations with
> previously set up ndps printers will continue to work fine.
>
> 2. Remove the NDPS client from workstations that have the iPrint client.
> Really it only makes sense to have just one print system, eh?
>
> 3. Disable iPrints automatic upgrade feature. Edit the file
> \\iprint-server\sys\apache2\htdocs\ippdocs\iprint.ini, find the line
> that says 'UpgradeNDPSPrinters=#' and change the value to 0 (do not
> upgrade).
>
> Hope that helps!
>
> Ron Neilly
> UBC Okanagan
>
> On Tue, 18 Sep 2007 14:41:24 +0000, Justin wrote:
>
>> NW6.5 server with NDPS printers. I just recently started to use iPrint.
>> Lets say I have a laptop that has the iPrint client installed. I
>> delete ALL of the printers on the laptop, then I restart the laptop and
>> login to netware. When the printers start pushing down, they are NDPS
>> printers and not IPP printers. Now I haven't changed anything in
>> imanager but I assumed that since the iprint client is installed, the
>> NDPS would just turn off and IPP would take over. Am I wrong? I am
>> still using NDPS printers on 100s of clients so I cant turn off NDPS all
>> together.


Thank you Ron for your advice.
0 Likes
Absent Member.
Absent Member.

Ron Neilly wrote:
> Justin, you are wrong! The iPrint client does not "turn off" the NDPS
> client - they are independent of each other. So you are right too!
>
> Okay what you have is a case of two printer management agents installed on
> one machine: the NDPS agent and the iPrint agent. There is nothing wrong
> with this per se, but it is bad design (imo).
>
> What can happen with both clients installed:
> 1. The NDPS client searches the user/container/group objects for NDPS
> deliever printers. This is often referred to as Remote Printer Management
> and the management tool for this is usually nwadmin. Okay, so NDPS finds
> one or more printers and installs them if they are not already installed
> on the workstation or if the adminstrator (you) has enabled the "Update
> Driver" function in Remote Printer Management.
>
> 2. iPrint client can, if told to, upgrade any ndps client installed
> printers to the iprint printer agent. The process of upgrading removes the
> NDPS installed printer. Now we can get race and deadlock situations where
> the two clients try to perform operations on the same thing at the same
> time... Even if there is no race/deadlock what happens the next time you
> login? NDPS checks for installable printers, finds them, installs them.
> And what does iPrint do? Convert them. Rinse and repeat endlessly.
>
> There are three solutions to this:
>
> 1. Remove the automatic updating of ndps printers, so that when an ndps
> enabled client logs in it does not find anything to do. Workstations with
> previously set up ndps printers will continue to work fine.
>
> 2. Remove the NDPS client from workstations that have the iPrint client.
> Really it only makes sense to have just one print system, eh?
>
> 3. Disable iPrints automatic upgrade feature. Edit the file
> \\iprint-server\sys\apache2\htdocs\ippdocs\iprint.ini, find the line
> that says 'UpgradeNDPSPrinters=#' and change the value to 0 (do not
> upgrade).
>
> Hope that helps!
>
> Ron Neilly
> UBC Okanagan
>
> On Tue, 18 Sep 2007 14:41:24 +0000, Justin wrote:
>
>> NW6.5 server with NDPS printers. I just recently started to use iPrint.
>> Lets say I have a laptop that has the iPrint client installed. I
>> delete ALL of the printers on the laptop, then I restart the laptop and
>> login to netware. When the printers start pushing down, they are NDPS
>> printers and not IPP printers. Now I haven't changed anything in
>> imanager but I assumed that since the iprint client is installed, the
>> NDPS would just turn off and IPP would take over. Am I wrong? I am
>> still using NDPS printers on 100s of clients so I cant turn off NDPS all
>> together.



Ron, If I choose solution 1 to remove the automatic updating of NDPS
printers, will it still auto update iPrint printers? Lets say I have
iPrint and NDPS installed on a laptop. The laptop is a fresh image and
we give it to a student. The laptop image does not have any printers
intalled. How can I have the certain printers that this students needs
automatically installed on her laptop using iPrint?
0 Likes
Absent Member.
Absent Member.

On Thu, 20 Sep 2007 15:20:32 +0000, Justin wrote:

> Ron Neilly wrote:
>> Justin, you are wrong! The iPrint client does not "turn off" the NDPS
>> client - they are independent of each other. So you are right too!
>>
>> Okay what you have is a case of two printer management agents installed on
>> one machine: the NDPS agent and the iPrint agent. There is nothing wrong
>> with this per se, but it is bad design (imo).
>>
>> What can happen with both clients installed:
>> 1. The NDPS client searches the user/container/group objects for NDPS
>> deliever printers. This is often referred to as Remote Printer Management
>> and the management tool for this is usually nwadmin. Okay, so NDPS finds
>> one or more printers and installs them if they are not already installed
>> on the workstation or if the adminstrator (you) has enabled the "Update
>> Driver" function in Remote Printer Management.
>>
>> 2. iPrint client can, if told to, upgrade any ndps client installed
>> printers to the iprint printer agent. The process of upgrading removes the
>> NDPS installed printer. Now we can get race and deadlock situations where
>> the two clients try to perform operations on the same thing at the same
>> time... Even if there is no race/deadlock what happens the next time you
>> login? NDPS checks for installable printers, finds them, installs them.
>> And what does iPrint do? Convert them. Rinse and repeat endlessly.
>>
>> There are three solutions to this:
>>
>> 1. Remove the automatic updating of ndps printers, so that when an ndps
>> enabled client logs in it does not find anything to do. Workstations with
>> previously set up ndps printers will continue to work fine.
>>
>> 2. Remove the NDPS client from workstations that have the iPrint client.
>> Really it only makes sense to have just one print system, eh?
>>
>> 3. Disable iPrints automatic upgrade feature. Edit the file
>> \\iprint-server\sys\apache2\htdocs\ippdocs\iprint.ini, find the line
>> that says 'UpgradeNDPSPrinters=#' and change the value to 0 (do not
>> upgrade).
>>
>> Hope that helps!
>>
>> Ron Neilly
>> UBC Okanagan
>>
>> On Tue, 18 Sep 2007 14:41:24 +0000, Justin wrote:
>>
>>> NW6.5 server with NDPS printers. I just recently started to use iPrint.
>>> Lets say I have a laptop that has the iPrint client installed. I
>>> delete ALL of the printers on the laptop, then I restart the laptop and
>>> login to netware. When the printers start pushing down, they are NDPS
>>> printers and not IPP printers. Now I haven't changed anything in
>>> imanager but I assumed that since the iprint client is installed, the
>>> NDPS would just turn off and IPP would take over. Am I wrong? I am
>>> still using NDPS printers on 100s of clients so I cant turn off NDPS all
>>> together.

>
>
> Ron, If I choose solution 1 to remove the automatic updating of NDPS
> printers, will it still auto update iPrint printers? Lets say I have
> iPrint and NDPS installed on a laptop. The laptop is a fresh image and
> we give it to a student. The laptop image does not have any printers
> intalled. How can I have the certain printers that this students needs
> automatically installed on her laptop using iPrint?


Hi Justin, that is a good question and as usual with me I will provide
more than one answer :-).

1. Auto UPDATE of iPrint printers.... This does not exist in a default
install of iPrint. There is an add-on capability called iPrint Client
Management (iCM) that can be used to provide most of the functionality of
NDPS Remote Printer Management (RPM). It is a free download from Novell.
What iCM does NOT give you is the ability to associate a printer to a
workstation object if you are using ZENWorks. Of course if you are using
ZENWorks you can use a workstation policy to associate a printer with the
workstations. ZENWorks rocks - highly recommended. There are other ways to
get printer drivers updated besides ZENWorks and iCM. For example you
could use login scripts and/or batch commands to execute the command-line
interface to iprint. The command is 'iprntcmd' and it can do everything
you need: add permanently, delete, add temporarily, list etc.

2. Auto INSTALL of iPrint printers. Pretty much see above answer. You get
to choose the tool you want: command-line (iprntcmd) via login
script/batch command, iCM, or ZENWorks.

At the University we are currently using login scripts to control delivery
of printers to lab workstations. One of the keys to this - part of our lab
design infrastructure - is the setting of environment variables to
identify a workstation as belonging in a particular lab. In our case we
call the environment variable "SGroup" and it will have a value such as
"IC2". This is then used to execute a specific container login script
which sets up the correct printer for that lab. But perhaps I digress a
bit off topic - after all I am now talking about directory design....

So let me finish by saying that everything that you want to do can be
done with one or more of the three tools listed above. Exactly HOW is
mostly a matter for you to determine based on intimate knowledge of
your environment, which you possess (and I do not ;-)....

Hope this helps - and keep asking questions!

Cheers,

Ron
0 Likes
Absent Member.
Absent Member.

Thanks for your advice Ron. Using ICM to push down printers and it is
MUCH better than NDPS. Quicker and more reliable. Thank you.
0 Likes
Absent Member.
Absent Member.

One more question for you. Lets say I am a member of three groups,
"Everyone", "Test", and "Admin". Lets say in ICM I set up the
"Everyone" printers 1,2,3 to be pushed down and I make in the client
configuration part under ICM to make sure the URL points to my server.
Now lets say also edit the "Test" group and add printers 5,6,7 but I do
not make the url change in the client configuration. What happens?
0 Likes
Absent Member.
Absent Member.

On Wed, 26 Sep 2007 20:15:27 +0000, Justin wrote:

> One more question for you. Lets say I am a member of three groups,
> "Everyone", "Test", and "Admin". Lets say in ICM I set up the
> "Everyone" printers 1,2,3 to be pushed down and I make in the client
> configuration part under ICM to make sure the URL points to my server.
> Now lets say also edit the "Test" group and add printers 5,6,7 but I do
> not make the url change in the client configuration. What happens?


Beats me! But if you test this out let us know 😉

Cheers,

Ron
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.