Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1059 views

Can't find way to update NDPS driver

I have a new NDPS printer on a Netware 6.5SP8 server. The printer is
being installed to the same IP address etc. as the old printer, so I
simply want to modify the existing NDPS printer to update to the new driver.

Can't find any way to make this work.

I *finally* got NWADMIN working, for the most part, with an update to
deal with the TLS issue; however, if I try to add drivers via the
resource manager on the broker, the "Browse" button does nothing, so I
can't get to the files in their location.

In addition, the printer comes with an INF file and CAT file and DLLs,
but no CAB file & nothing Novell-related either.

In iprint, I get an error when trying to Manage the NDPS printer;
apparently this issue is well-known and I haven't seen a fix for it.
(Every tab under Manage gives its own variant of the same error, i.e.
"exception reading printer control" etc.) I am running iManager on an
XP workstation that has both the Novell client, and NDPS as well as
iprint components, installed ... and ippsrvr.nlm is already loaded on
the server, of course.

So I am stuck for finding a way to update the driver. Any hints or
suggestions to work around the tools not working? Is there some way to
perhaps put the driver files somewhere so that I won't have to browse to
them? Some way to make imanager work on managing the NDPS printer?

The only thing I've found so far is to go to each workstation & manually
update the driver, then reboot and then manually force a configuration
update, then set the settings I want everyone to use. I have tried
building a package with snapshot to deploy these changes but that, too,
doesn't seem to work.

Any method at all that would let me update the driver associated with
the printer object, without visiting each & every workstation, would be
appreciated.
0 Likes
5 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

De,
> I *finally* got NWADMIN working, for the most part, with an update to
> deal with the TLS issue; however, if I try to add drivers via the
> resource manager on the broker, the "Browse" button does nothing, so I
> can't get to the files in their location.



Run nwadmin32 /disabletlsmgr

> In addition, the printer comes with an INF file and CAT file and DLLs,
> but no CAB file & nothing Novell-related either.
>

Google for pdrvgen

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
Absent Member.
Absent Member.

Thanks. FWIW, I've been using the /disabletlsmgr, but it hasn't helped.
NWADMIN32 abruptly stopped working, when a few days before it had been
just fine from the very same stations. Using the switch didn't help.
What helped eventually was doing a whole new installation of it from the
5.19 (?) version that is supposed to fix the TLS issue ... installing
over the existing one didn't help, but making a new install in a
different location did it. [Novell client 4.91SP5 on XP/SP3.]

The browse issue was separate, and apparently was confined to one
workstation. I've seen this issue before, but so long ago that I can't
even remotely remember what caused it.

So I was able to bring the driver in using the Resource Management. Now
I'm stuck because I can't find any place that lets me associate that
driver with the existing printer object. On top of that, when I renamed
the printer in both the NDPS screen and ConsoleOne, it apparently only
pushed the rename to *some* workstations and others still show the old name.

Anyway, basic stupid question (after reading through every doc I could
find): Having added the driver to the resources, how do I get NDPS to
know that is the driver for the printer in question? I know I can
change the driver from the client side in Windows, but NWADMIN etc. seem
to persistently want to associate the old printer driver with that
printer. I'm sure there is somewhere to change it: where??

Thanks. This is frustrating, but there's finally approval to move
forward with iprint; however, since iprint sets up through the same
object in NWADMIN (and doesn't seem to work for me imanager) I still
need to resolve the issue of having the printer object associated with
the right driver.

-- DE





Anders Gustafsson wrote:
> De,
>> I *finally* got NWADMIN working, for the most part, with an update to
>> deal with the TLS issue; however, if I try to add drivers via the
>> resource manager on the broker, the "Browse" button does nothing, so I
>> can't get to the files in their location.

>
>
> Run nwadmin32 /disabletlsmgr
>
>> In addition, the printer comes with an INF file and CAT file and DLLs,
>> but no CAB file & nothing Novell-related either.
>>

> Google for pdrvgen
>
> - Anders Gustafsson (Sysop)
> The Aaland Islands (N60 E20)
>
>
> Novell has a new enhancement request system,
> or what is now known as the requirement portal.
> If customers would like to give input in the upcoming
> releases of Novell products then they should go to
> http://www.novell.com/rms
>

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

De,
> So I was able to bring the driver in using the Resource Management. Now
> I'm stuck because I can't find any place that lets me associate that
> driver with the existing printer object. On top of that, when I renamed
> the printer in both the NDPS screen and ConsoleOne, it apparently only
> pushed the rename to *some* workstations and others still show the old name.
>
> Anyway, basic stupid question (after reading through every doc I could
> find): Having added the driver to the resources, how do I get NDPS to
> know that is the driver for the printer in question?


Not exactly sure what you have done so far and you also mention C1 which has
no support for NDPS, but from NWadmin32:

1. To add drivers:
- Select broker, details, resource management, Add
- Select desired win version (ie 2000), Add

2. To associate drivers
- Printer Object, details, configuration, highligt "Default printer config",
Modify
- Drivers tab, select uploaded driver

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
Absent Member.
Absent Member.

Thanks.
Anders Gustafsson wrote:
....
> 1. To add drivers:
> - Select broker, details, resource management, Add
> - Select desired win version (ie 2000), Add

That was the part I got to after wrestling to get NWADMIN working.
(I think the NWADMIN issue was actually a broken plug-in.)
>
> 2. To associate drivers
> - Printer Object, details, configuration, highligt "Default printer config",
> Modify
> - Drivers tab, select uploaded driver


That was the thing I couldn't find, for some reason; thank you for
answering what I know is a basic basic question.

Got it all updated now.


-- DE
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

De,
> Got it all updated now.
>

You are welcome!

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

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.