If they are not on line between 6 and 7am, then the schedule will not catch
them.
Might I suggest an 8 hour duration.  If they login during the day, hopefully
they
will be found and backed up.

But if you use login scripts, it might be best to use that instead.  So the
first time
a user logs in each day, a backup is done.  But check a date/time stamp on a
file
or registry entry to see you don't do it multiple times in one day.  You
might even
not 'touch' the file till a successful backup completes (in an exit script?)

We don't backup laptops, not that it is not a good idea.

> -----Original Message-----
> From: Simeon Johnston [SMTP:simeonuj AT INDIVISUALLEARNING DOT COM]
> Sent: Wednesday, May 28, 2003 10:52 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Understanding schedules
>
> I'm trying to setup client schedules for several offsight laptops (win2k
> 5.1 server/client).
> I setup the schedule and associate everyone to it.  It all looks good.
> Except they keep missing the scheduled window.  These laptops have no
> set time (and I don't want to have a set time) that they are online.
> I left the duration at 1 hour and the period is 1 day.  It starts at
> 6am.
> What I'd like is a schedule that will run all day and whenever the
> client is connected start backing up right then.
>
> A few questions that have been bugging me.
> Is there a way to query the clients schedule?  When it will attempt to
> backup, or the schedule it got from the server?
> What exactly does the duration option do?  Is this how long the client
> has to start a backup session?  If so then I should set it to something
> like 5min.  If it's just how long the client has to login and GET the
> schedule then I should have this running all day (24hours).
>
> I think I'm just very confused.  Any help would be appreciated.
>
> sim