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.
This website uses cookies. By continuing to browse or login to this website, you consent to the use of cookies. Learn more.
OK
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-13 16:26
1209 views

iPrint printer doesn't show up in C1

We installed our first OES SP2 Linux server with most of the netware
services installed, including iPrint. IPrint is configured, we can
install the client and drivers for both Windows and LInux clients from
the servername/ipp web page, and can print from both. But the printer
doesn't show up in eDir (8.7.3.7) in ConsoleOne or iManage. Thus, we
cannot associate the iPrint policy with a printer.

We have not run rug updates on the linux box yet. Install was done
straight from the SP2 download.

We are running iPrint on an OES Netware box and that is not a problem.

Not sure this is the right forum since this seems a potential iPrint,
OES Linux, or eDir problem. I posted this to the oes.linux.printing
forum but received no response.

How can we install and print to a printer that doesn't show up in
eDir?

Thoughts?

Lyle
0 Likes
Reply
Report Inappropriate Content
6 Replies
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-13 17:42

Update: OK, I found the object, but, as indicated in an earlier post,
C1 doesn't know anything about iPrint objects. The printer was showing
as a ? object. iManager did see it as a printer. Now the problem is
that I am trying to associate that iprinter with a Zen policy to push
the printer, but when I browse for the printer in the iPrint policy in
C1, the ? object does not show up as an available printer because it
doesn't know it's a printer.

iPrint printers created on iprint on an OES Netware box DO show up as
iprint printers.

How can I convince C1 to let me use that printer?

Lyle

On Tue, 13 Jun 2006 15:26:07 GMT, luzuml@nicc.edu wrote:

>We installed our first OES SP2 Linux server with most of the netware
>services installed, including iPrint. IPrint is configured, we can
>install the client and drivers for both Windows and LInux clients from
>the servername/ipp web page, and can print from both. But the printer
>doesn't show up in eDir (8.7.3.7) in ConsoleOne or iManage. Thus, we
>cannot associate the iPrint policy with a printer.
>
>We have not run rug updates on the linux box yet. Install was done
>straight from the SP2 download.
>
>We are running iPrint on an OES Netware box and that is not a problem.
>
>Not sure this is the right forum since this seems a potential iPrint,
>OES Linux, or eDir problem. I posted this to the oes.linux.printing
>forum but received no response.
>
>How can we install and print to a printer that doesn't show up in
>eDir?
>
>Thoughts?
>
>Lyle

0 Likes
Reply
Report Inappropriate Content
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-13 19:07

Further investigation indicates that the iprint objects that can be
seen and used in a Zen policy vs those that can't are different
types. The older ones that were created with OES NW have an object
type of NDPS Printer. The ones that aren't recognized are
iPrintPrinter type.

The C1 I am running is coming from a NW server, not from the OES Linux
server. Is that a C1 snapin issue? To include these objects in a Zen
policy should I be running the C1 from the Linux server. Just how
would I do that on my windows workstation? Or is there something to
copy to my C1 installation to make them work?

Lyle
0 Likes
Reply
Report Inappropriate Content
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-13 21:12

luzuml@nicc.edu wrote:
> Further investigation indicates that the iprint objects that can be
> seen and used in a Zen policy vs those that can't are different
> types. The older ones that were created with OES NW have an object
> type of NDPS Printer. The ones that aren't recognized are
> iPrintPrinter type.

So do you see objects in C1 that have the right name, wrong object
class? Then you should see the Other tab having interestingly named
attributes.

> The C1 I am running is coming from a NW server, not from the OES Linux
> server. Is that a C1 snapin issue? To include these objects in a Zen
> policy should I be running the C1 from the Linux server. Just how
> would I do that on my windows workstation? Or is there something to
> copy to my C1 installation to make them work?

C1 has never been able to manage NDPS/iPrint. It has always been
iManager or NWadmin that manages them.

Also, if you get the latest iPrint NPM from Novell, and extract the
file, you will see you have two NPM's. One for managing older
NDPS/Netware objects and a second for newer iPrint/Linux objects. Get
the second one.
0 Likes
Reply
Report Inappropriate Content
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-14 21:09

On Tue, 13 Jun 2006 20:12:37 GMT, Geoffrey Carman <geoffc@yorku.ca>
wrote:

>luzuml@nicc.edu wrote:
>> Further investigation indicates that the iprint objects that can be
>> seen and used in a Zen policy vs those that can't are different
>> types. The older ones that were created with OES NW have an object
>> type of NDPS Printer. The ones that aren't recognized are
>> iPrintPrinter type.

>
> So do you see objects in C1 that have the right name, wrong object
>class? Then you should see the Other tab having interestingly named
>attributes.

They do have the right name. I can't say they have the wrong object
class, because I don't know what that should be. All I can say is that
the object classes of the ones we can assign to a Zen iPrint policy in
C1 are class "NDPS Printer". The ones that Zen can't see in the iPrint
policy in C1 are class "iPrintPrinter". That seems like a logical
class to me, since that's what they are, but something does not like
something.

>
>> The C1 I am running is coming from a NW server, not from the OES Linux
>> server. Is that a C1 snapin issue? To include these objects in a Zen
>> policy should I be running the C1 from the Linux server. Just how
>> would I do that on my windows workstation? Or is there something to
>> copy to my C1 installation to make them work?
>
>C1 has never been able to manage NDPS/iPrint. It has always been
>iManager or NWadmin that manages them.

We don't actually want to manage the iPrinters from C1 -- just assign
to a Zen policy. iManger can manage the printer as is, it seems. But
iManager can't assign to a Zen iPrint policy for Windows.

>
> Also, if you get the latest iPrint NPM from Novell, and extract the
>file, you will see you have two NPM's. One for managing older
>NDPS/Netware objects and a second for newer iPrint/Linux objects. Get
>the second one.

Thanks.

Lyle
0 Likes
Reply
Report Inappropriate Content
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-22 14:59

Any resolution on this issue? We've run into the same thing. We have a
similar setup, and also wish to push out printer assignments through Zen.

Thanks
belsam

> On Tue, 13 Jun 2006 20:12:37 GMT, Geoffrey Carman <geoffc@yorku.ca>
> wrote:
>
> >luzuml@nicc.edu wrote:
> >> Further investigation indicates that the iprint objects that can be
> >> seen and used in a Zen policy vs those that can't are different
> >> types. The older ones that were created with OES NW have an object
> >> type of NDPS Printer. The ones that aren't recognized are
> >> iPrintPrinter type.
>
> >
> > So do you see objects in C1 that have the right name, wrong object
> >class? Then you should see the Other tab having interestingly named
> >attributes.
>
> They do have the right name. I can't say they have the wrong object
> class, because I don't know what that should be. All I can say is that
> the object classes of the ones we can assign to a Zen iPrint policy in
> C1 are class "NDPS Printer". The ones that Zen can't see in the iPrint
> policy in C1 are class "iPrintPrinter". That seems like a logical
> class to me, since that's what they are, but something does not like
> something.
>
> >
> >> The C1 I am running is coming from a NW server, not from the OES Linux
> >> server. Is that a C1 snapin issue? To include these objects in a Zen
> >> policy should I be running the C1 from the Linux server. Just how
> >> would I do that on my windows workstation? Or is there something to
> >> copy to my C1 installation to make them work?
> >
> >C1 has never been able to manage NDPS/iPrint. It has always been
> >iManager or NWadmin that manages them.
>
> We don't actually want to manage the iPrinters from C1 -- just assign
> to a Zen policy. iManger can manage the printer as is, it seems. But
> iManager can't assign to a Zen iPrint policy for Windows.
>
> >
> > Also, if you get the latest iPrint NPM from Novell, and extract the
> >file, you will see you have two NPM's. One for managing older
> >NDPS/Netware objects and a second for newer iPrint/Linux objects. Get
> >the second one.
>
> Thanks.
>
> Lyle

0 Likes
Reply
Report Inappropriate Content
Anonymous_User
Absent Member.
Absent Member.
‎2006-06-22 15:49

Never mind ... found the solution.

There is a download - ZENworks 7 Desktop Management Snap-ins for ConsoleOne
1.3.6 - that brings the iPrint printers into ConsoleOne so you can set up a
policy.

Hope this helps someone
belsam


> Any resolution on this issue? We've run into the same thing. We have a
> similar setup, and also wish to push out printer assignments through Zen.
>
> Thanks
> belsam
>
> > On Tue, 13 Jun 2006 20:12:37 GMT, Geoffrey Carman <geoffc@yorku.ca>
> > wrote:
> >
> > >luzuml@nicc.edu wrote:
> > >> Further investigation indicates that the iprint objects that can be
> > >> seen and used in a Zen policy vs those that can't are different
> > >> types. The older ones that were created with OES NW have an object
> > >> type of NDPS Printer. The ones that aren't recognized are
> > >> iPrintPrinter type.
> >
> > >
> > > So do you see objects in C1 that have the right name, wrong object
> > >class? Then you should see the Other tab having interestingly named
> > >attributes.
> >
> > They do have the right name. I can't say they have the wrong object
> > class, because I don't know what that should be. All I can say is that
> > the object classes of the ones we can assign to a Zen iPrint policy in
> > C1 are class "NDPS Printer". The ones that Zen can't see in the iPrint
> > policy in C1 are class "iPrintPrinter". That seems like a logical
> > class to me, since that's what they are, but something does not like
> > something.
> >
> > >
> > >> The C1 I am running is coming from a NW server, not from the OES Linux
> > >> server. Is that a C1 snapin issue? To include these objects in a Zen
> > >> policy should I be running the C1 from the Linux server. Just how
> > >> would I do that on my windows workstation? Or is there something to
> > >> copy to my C1 installation to make them work?
> > >
> > >C1 has never been able to manage NDPS/iPrint. It has always been
> > >iManager or NWadmin that manages them.
> >
> > We don't actually want to manage the iPrinters from C1 -- just assign
> > to a Zen policy. iManger can manage the printer as is, it seems. But
> > iManager can't assign to a Zen iPrint policy for Windows.
> >
> > >
> > > Also, if you get the latest iPrint NPM from Novell, and extract the
> > >file, you will see you have two NPM's. One for managing older
> > >NDPS/Netware objects and a second for newer iPrint/Linux objects. Get
> > >the second one.
> >
> > Thanks.
> >
> > Lyle
>

0 Likes
Reply
Report Inappropriate Content
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.