Re: Login Time Restrictions

From: Joe Richards [MVP] (humorexpress@hotmail.com)
Date: 09/03/02


From: "Joe Richards [MVP]" <humorexpress@hotmail.com>
Date: Mon, 2 Sep 2002 20:57:10 -0400


This is still possible on W2K Pro just not with the tools given. You can do
one of the following

1. Write a script that knows how to set hours.
2. Write a program that displays a pretty GUI and then knows how to set
hours
3. Use user manager from domains from an NT4 machine to modify the W2K Pro
machine
4. Use Net User and the proper parameter

>From the NET USER Command NT4 help (this info doesn't exist in the W2K help)

/times:{times | all}
Specifies the times the user is allowed to use the computer. The times value
is expressed as day[-day][,day[-day]] ,time[-time][,time[-
time]], limited to 1-hour time increments. Days can be spelled out or
abbreviated (M,T,W,Th,F,Sa,Su). Hours can be 12- or 24-hour notation. For
12-hour notation, use AM, PM, or A.M., P.M. The value all means a user can
always log on. A null value (blank) means a user can never log on. Separate
day and time with commas, and units of day and time with semicolons (for
example, M,4AM-5PM;T,1PM-3PM). Do not use spaces when designating /times.

[Mon 09/02/2002 20:56:39.70]
G:\temp>net user joebob /times:M,12AM-11PM
The command completed successfully.

[Mon 09/02/2002 20:56:44.96]
G:\temp>net user joebob
User name joebob
Full Name
Comment Howdy
User's comment
Country code 000 (System Default)
Account active Yes
Account expires Never

Password last set 9/2/2002 8:56 PM
Password expires 12/1/2002 8:56 PM
Password changeable 9/2/2002 8:56 PM
Password required Yes
User may change password Yes

Workstations allowed All
Logon script
User profile
Home directory
Last logon 8/1/2001 3:46 PM

Logon hours allowed Monday 12:00 AM - 11:00 PM

Local Group Memberships
Global Group memberships *None
The command completed successfully.

[Mon 09/02/2002 20:56:46.52]
G:\temp>

--
Joe Richards
www.joeware.net
---
"Johnathon" <UPS10160@hotmail.com> wrote in message
news:a0a501c252af$a4209b70$37ef2ecf@TKMSFTNGXA13...
> Dear Newsgroup,
>
> I have a quick question that I am hoping that someone will
> know the answer to easily.  I have a lot of experience
> with Windows NT 4.0 but I am still learning where things
> have been moved to in Windows 2000 Professional.  One of
> these items is the ability to restrict a user from logging
> into a workstation between certain hours.  In Windows NT
> 4, an administrator could configure a user account to
> restrict login access between certain hours (for example
> between 9pm and 7am) by using a 24 hour time chart and
> selecting a start and stop time to restrict access.  But
> in Windows 2000 Prof., I cannot find this same feature
> anywhere.  I have a client who wants this ability and I
> need to know where I can find it again.  Can anyone help?
> If possible, please email me your answer at
> UPS10160@hotmail.com if it is possible.
>
> Thank you for your help!
>
> Johnathon
>


Relevant Pages

  • Re: Windows clock
    ... For XP Pro, this can be restricted via the Group Policy Editor. ... Go to Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment. ... you would have to restrict access to the TIMEDATE.CPL application. ...
    (microsoft.public.windowsxp.newusers)
  • Re: Error with User Accounts function in Control Panel
    ... registry - all of which solved the issues in Pro? ... Ramesh Srinivasan, Microsoft MVP [Windows Shell/User] ... The script is attempting to call the RegRead method within the ... is ticked but Fast User Switching unticked. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Basic Administration
    ... You don't say if you're using XP Pro or XP Home. ... Apply Local Policies to all Users Except Administrators on Windows ... the Group Policy Editor doesn't exist. ... Is there some way to restrict access to ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Multiple Sessions
    ... You can't restrict the number of users through AD. ... only works through Windows 2003 terminal services. ... can use a script or a third party utility to control how ...
    (microsoft.public.win2000.termserv.apps)
  • Error 13 from GetObject ("Type Mismatch")
    ... I wrote a program using VB 6, ... a script and the script works with Windows 2003 Server. ...
    (microsoft.public.win32.programmer.wmi)