I enable a screensaver on a win95 machine running the scheduler in
polling mode, and it kicked off OK. Whether it is the scheduling mode
that allowed it to work, or the way the screensaver checks for activity,
I don't know, but just a guess, Either activity from the scheduler, or
communication between the server and client is seen as activity by the
screensaver, preventing it from activating the same way keyboard or
mouse
activity would.


Anderson, Vincent wrote:
>
> We have a group of Windows 95 machines that we are backing up with ADSM.
>  We use the ADSM scheduler in prompted mode to back these machines up at
> night automatically.  We also require the users to use a screen saver
> that is password protected.
>
> The problem is that the screen saver does not always kick in.  It seems
> to vary from machine to machine as to how reliable the problem is.  The
> complaints began soon after the scheduler was implemented on these
> machines earlier this week.
>
> Has anyone seen this before?  If so, what have you done about it?  If
> not, do you have any suggestions on where to look for clues?
>
> These machines are running the V2 client.  Might an upgrade to V3 help?
>
> Vince Anderson
> Rutgers University