Auto Driver Update

Hi,

I can't seem to find any documentation for how this feature works - or
rather is supposed to work. In limited testing I've found that the drivers
are updated always upon a reboot of the workstation and rarely while the
client workstation is up and the enduser logged in.

It would be great if there were some way to control this behaviour or at
least to know what the behaviour is supposed to be.

If it is supposed to update the driver while the user is logged in then I
need to figure out why it is failing to do that most of time.

Our environment consists of :

Server : NetWare 6.5 sp8
- ndpsm v3.03.02, May 18 2010
- ndpsgw v4.01.02, Mar 2 2010
- broker v3.00.12, Feb 20 2008
- pcountdp/pcountwi v5.40.01, May 30 2011

Clients : Windows XP sp3
- tested iPrint client v5.44, 5.64, 5.68
- Novell Client for Windows 4.91 sp4 and sp5.

Not sure where the problem lies; anybody got any clues or experiences to
share?

Thanks,

--
Ron Neilly
Network and Systems Coordinator
UBC Okanagan
Kelowna, BC, Canada
  • rjneilly;2137918 wrote:

    I've found that the drivers are updated always upon a reboot of the workstation and rarely while the client workstation is up and the enduser logged in.


    Same experience here, I will ask Novell if this is WAD and get back to you.

    Thomas
  • thsundel wrote:

    > Same experience here, I will ask Novell if this is WAD and get back to
    > you.
    >


    Thanks Thomas. Any word from Novell?

    Cheers,

    --
    Ron Neilly
    Network and Systems Coordinator
    UBC Okanagan
    Kelowna, BC, Canada
  • rjneilly;2140513 wrote:
    thsundel wrote:

    > Same experience here, I will ask Novell if this is WAD and get back to
    > you.
    >


    Thanks Thomas. Any word from Novell?

    Cheers,

    --
    Ron Neilly
    Network and Systems Coordinator
    UBC Okanagan
    Kelowna, BC, Canada


    Nothing more than that they would get back to me on Monday but I haven't received a response yet, but one thing that was suggested was that a reboot of the printer spooler might fire the printer update... Haven't yet tried it but please report back if you do try it. I will ping them again to get an official answer to this..

    Thomas
  • thsundel wrote:

    >
    > that a reboot of the printer spooler might fire the printer update...


    Thanks. What is this "printer spooler" you speak of :-) ?

    Is it:

    1. The Windows client print spooler? If so is the suggestion to do a net
    stop spooler/net start spooler?

    2. The iPrint server? If so is the suggestion to unload/load ndpsm.nlm and
    broker.nlm? Or is it to reboot the iPrint server?

    Cheers,
    --
    Ron Neilly
    Network and Systems Coordinator
    UBC Okanagan
    Kelowna, BC, Canada
  • rjneilly;2140552 wrote:
    thsundel wrote:

    >
    > that a reboot of the printer spooler might fire the printer update...


    Thanks. What is this "printer spooler" you speak of :-) ?

    Is it:

    1. The Windows client print spooler? If so is the suggestion to do a net
    stop spooler/net start spooler?

    2. The iPrint server? If so is the suggestion to unload/load ndpsm.nlm and
    broker.nlm? Or is it to reboot the iPrint server?

    Cheers,
    --
    Ron Neilly
    Network and Systems Coordinator
    UBC Okanagan
    Kelowna, BC, Canada


    The Windows workstation printer spooler sevice where you would like to "fire" the update iPrint driver event.

    Thomsad
  • thsundel wrote:

    > I will ping them again to get an official answer to this..
    >
    > Thomas
    >


    Looks like the ping response time is rather long ;-)

    I was just reading the latest iPrint for OES2 SP3 docs and they say that the
    update on the workstation can take place in a few seconds or as long as 24
    hours. No explanation for why nor what knob controls the timing of this
    event.

    Cheers,

    --
    Ron Neilly
    Network and Systems Coordinator
    UBC Okanagan
    Kelowna, BC, Canada