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.
1956 views

iPrint from NW65 SP5 on Win 7

Good day,

We are in the process of evaluating Windows 7.

The task to get iPrint to work on Windows 7 fell on my shoulders.

The problem I have is that, running iPrint on NW65 SP5, I cannot find a way to load a Windows 7 driver on the broker (I am using iManager Version 2.5.20051102).

I have tried loading iprntnw65sp8b, using both option A and B, but then I ran intro problems where the RMS tab doesn't show the various tabs for XP, Vista, Etc.

Is there any way to get iPrint to work on Windows 7 with our current Netware configuration?

Any help would be grately appreciated.

I know I am asking for the impossible and i KNOW i should update to SP8, but for various reasons, I can't at the moment. Due to legacy business systems we are forced to keep our Netware systems running on NW65 SP5. Yes we are in the process of sorting this out, so we can upgrade. Also I inherited the environment in this state, so nothing I could do to prevent us arriving at this point.
0 Likes
6 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Hi,

koosbrits wrote:
>
> Any help would be grately appreciated.


No help whatsoever possible, sorry. There is *no* chance on SP5, period.

> I know I am asking for the impossible and i KNOW i should update to
> SP8, but for various reasons, I can't at the moment. Due to legacy
> business systems we are forced to keep our Netware systems running on
> NW65 SP5.


I seriously wouldn't know any whatsoever technical or political reason
why *any* system or software would require a certain netware service
pack, and not work with a newer one. Can you elaborate why this is the
case? Or is this just one of those vendor statements that isn't backed
by anything?

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Absent Member.
Absent Member.

Basically we've got custom written software that drives provisioning of services. The powers that be are afraid that if we extend the schema, or change too much in the environment that the whole house of cards will come tumbling down.

To make matters worse, the person who wrote the software has since moved to New Zeeland.

We are in the process of implementing proper IDM using Novell's IDM, from which the provisioning will then happen, so I hope it will be sorted out soon.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Hi,

koosbrits wrote:
>
> Basically we've got custom written software that drives provisioning of
> services. The powers that be are afraid that if we extend the schema, or
> change too much in the environment that the whole house of cards will
> come tumbling down.


Well, that's wat testbeds are for I guess. 😉 But I really can't imagine
any reason why a newer SP should break anything.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Absent Member.
Absent Member.

I dare say (having spent much of the day dissecting it) that if you replace all iprint related nlms with the newer versions (which is pretty much what the b2 pack is), you'll have a system that's perfectly capable of providing the print services you need, but you're definitely going to need imanager 2.7.2 or 2.7.3 somewhere to actually put the drivers there and tell the printers which ones to use.
0 Likes
Absent Member.
Absent Member.

OK here's what I did:

1. Set up a NW6.5 SP8 server.
2. Install iManager 2.7.2 on it.
3. Next upgrade iManager to 2.7.3 using iman273_FTF1.npm thats shipped with iprntnw65sp8b.
4. Follow the steps in TID 3424524.
5. Load the rest of the files onto the servers, as described in iprntnw65sp8b.
6. Load the driver for Windows 7 into the broker.
7. Assign the driver in the manager to the broker.
8. Go to the server/ipp page and install the printer.

Of course I cannot say how stable the print server will be in a production environment. I did all this using servers that I built on VMWare Workstation 7.

Thank you to everyone who replied and thank you to Ted Tronson who told me about TID 3424524.
0 Likes
Absent Member.
Absent Member.

koosbrits wrote:
> OK here's what I did:
>
> 1. Set up a NW6.5 SP8 server.
> 2. Install iManager 2.7.2 on it.
> 3. Next upgrade iManager to 2.7.3 using iman273_FTF1.npm thats
> shipped with iprntnw65sp8b.
> 4. Follow the steps in TID 3424524.
> 5. Load the rest of the files onto the servers, as described in
> iprntnw65sp8b.
> 6. Load the driver for Windows 7 into the broker.
> 7. Assign the driver in the manager to the broker.
> 8. Go to the server/ipp page and install the printer.
>
> Of course I cannot say how stable the print server will be in a
> production environment. I did all this using servers that I built on
> VMWare Workstation 7.
>
> Thank you to everyone who replied and thank you to Ted Tronson who told
> me about TID 3424524.
>
>


Koosbrits,
nw65sp8b patch is obsolete now, you can download nw65sp8b-2 patch from
the following link

http://download.novell.com/Download?buildid=rDJnqwI0jYk~

With this you can skip step 3 (for that go through readme section in
above link)

regards
Karna

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.