andyj2009 wrote:
>
> I found the "iPrint Windows 7 support - NetWare 65 Support Pack 8b"
> patch. Does it mean if I want to allow Windows 7 client to use iPrint, I
> have to patch the server to NW6.5 SP8B?
SP8, yes. There is no SP8b. You're confusing the iPrint patch (which is
for NW6.5 SP8 Servers only), and the Netware Service Pack itself. You
have to patch Netware to SP8, and *then* apply the above iPrint patch on
top of it.
> I am currently on SP7 and I
> heard issues with SP8
Where? What? Seriously, there are no issues with SP8. At least none that
SP7 wouldn't have too.
> I wonder how many people have used SP8B and if they run into any issues
> with iPrint? Saw some posts about server abend when uploading Windows 7
> drivers.
I haven't seen any problems, but I only have a handful of drivers.
CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
But,, we havent managed to get win7 to accept any drivers from iprint
either if the drivers isn't allready installed in the
workstation...which off course make the idea of iprint somewhat...dumb
On Fri, 04 Dec 2009 21:26:02 GMT, andyj2009
<andy...@no-mx.forums.novell.com> wrote:
>
>I found the "iPrint Windows 7 support - NetWare 65 Support Pack 8b"
>patch. Does it mean if I want to allow Windows 7 client to use iPrint, I
>have to patch the server to NW6.5 SP8B? I am currently on SP7 and I
>heard issues with SP8 so I prefer not to have to update the servers if
>possible.
>
>I wonder how many people have used SP8B and if they run into any issues
>with iPrint? Saw some posts about server abend when uploading Windows 7
>drivers.
>
>Andy
> I wonder how many people have used SP8B and if they run into any issues
> with iPrint? Saw some posts about server abend when uploading Windows 7
> drivers.
I upgraded our servers to SP8 mainly so that I could then added the
iPrint patch for Win7 support. Been running SP8 for a couple of weeks
now with no issues.
--
Joe Marton
Novell Knowledge Partner
Haven't had much problem with iPrint client 5.30 but 5.32 is out to fix
a couple of vulnerabilities.