Re: NET user time restrictions
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Wed, 1 Feb 2006 00:04:10 +1100
"Justin Case" <jcase@xxxxxxxxxxx> wrote in message
news:drlut11ehg9dj643a7fdulds4v11tsgai2@xxxxxxxxxx
> On Tue, 31 Jan 2006 13:16:07 +1100, "Pegasus \(MVP\)" <I.can@xxxxxxx>
> wrote:
>
> >
> >"Justin Case" <jcase@xxxxxxxxxxx> wrote in message
> >news:vfhtt1lhikdeorr53tln3qv94ff36nrhb0@xxxxxxxxxx
> >> On Tue, 31 Jan 2006 09:41:07 +1100, "Pegasus \(MVP\)" <I.can@xxxxxxx>
> >> wrote:
> >>
> >> >
> >> ><jcase@xxxxxxxxx> wrote in message
> >> >news:1138655636.489876.120770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> >> I want to restrict useage to between 2:00 and 3:00 and 6:00 to 10:00
> >> >> monday to thursday. No problem, there I can get that to work.
> >> >> with: "net user test /time:monday-thursday,14:00-15:00;18:00-22:00"
> >> >>
> >> >> But I want to open the system with no restrictions friday to sunday.
> >> >> I can't get the second day & time range to be accepted.
> >> >> I've tried:
> >> >> How do I append "friday-sunday,all" to the above string?
> >> >> Everything I've tried results in "invalid day" (or time) "range
> >> >> entered"
> >> >>
> >> >> TIA
> >> >>
> >> >
> >> >I typed this command: net help user
> >> >and received this output:
> >> > /TIMES:{times | ALL} Is the logon hours. TIMES is expressed
as
> >> > day[-day][,day[-day]],time[-time][,time
> >> > [-time]], limited to 1-hour increments.
> >> > Days can be spelled out or abbreviated.
> >> > Hours can be 12- or 24-hour notation.
For
> >> > 12-hour notation, use am, pm, a.m., or
> >> > p.m. ALL means a user can always log on,
> >> > and a blank value means a user can never
> >> > log on. Separate day and time entries
with
> >> > a comma, and separate multiple day and
time
> >> > entries with a semicolon.
> >> >The key is in the very last word in the above paragraph.
> >> >
> >>
> >> yes, I've seen & read the very same help blurb as well as the
> >> knowledge base pertaining to the NET command. I've done it. Just as it
> >> says. I still can't get a *second* day and time range accepted.
> >
> >I such cases it's a good idea for you to post what you've
> >tried. I had no problem at all with this command:
> >
> >net user test /times:monday,12-13;tuesday,15-16
> >
>
> As stated, I'm want access monday - thurs, 2-3:00 and again at
> 6-10:00. I'm entering this successfully and it works as expected:
>
> "net user test /times:monday-thursday,14:00-15:00;18:00-22:00"
>
> That works OK.
>
> >What does your command look like?
> >
> I also want to allow unrestricted access fri sat & sun.
> So I enter: (it wraps in my newsreader)
> "net user test
> /times:monday-thursday,14:00-15:00;18:00-22:00;friday-sunday,all
>
> This results in "illegal day range..."
> So, you entered days individually. Is that the best way to do it?
A little bit of experimentation shows that the correct command is
net user test /times:monday-thursday,14:00-15:00,18:00-22:00;friday-sunday,0
0:00-24:00
The help text for the command (what you called "blurb") does in
fact say that the parameter "all" is used ***instead*** of a date/
time range. It reads "ALL means a user can always log on". It does
not say "ALL means a user can always log on on the specifiied day".
.
- Follow-Ups:
- Re: NET user time restrictions
- From: Justin Case
- Re: NET user time restrictions
- References:
- NET user time restrictions
- From: jcase
- Re: NET user time restrictions
- From: Pegasus \(MVP\)
- Re: NET user time restrictions
- From: Justin Case
- Re: NET user time restrictions
- From: Pegasus \(MVP\)
- Re: NET user time restrictions
- From: Justin Case
- NET user time restrictions
- Prev by Date: Re: Green Forward
- Next by Date: Re: Message when trying to reformat
- Previous by thread: Re: NET user time restrictions
- Next by thread: Re: NET user time restrictions
- Index(es):
Relevant Pages
|