Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
User Accounts 1
- Thread starter PinkTaco
- Start date
-
1
- #2
I copied this from somewhere on the web, see if it leads you anywhere.
"Subject: Setting Restricted Login Hours on XP Standalone System
I recently had to contact Microsoft Tech Support for assistance on this so I wanted to post the article on the web incase someone else had this same issue.
Situation: You want to restrict the logon days / times of a user account in XP and are a standalone machine.
Reason: You may wish to restrict teens who arrive home before adult supervision from accessing your broadband always on connection, limit employees to only work hours access etc..
Steps:
To Set restrictions:
Click Start
Click Run
Type cmd in the run box and press enter.
The following is a sample of what you would type:
net user testuser /times:M-F,5pm-9pm; Sa,6am-9pm;Su,6am-9pm
Where testuser is the local account name.
To Remove Restrictions:
Click Start
Click Run
Type cmd in the run box and press enter.
The following is a sample of what you would type:
net user testuser /times:all
Where testuser is the local account name."
137978 - Using NET USERS to Manage Local User Accounts on a Workstation
Typing NET HELP USERS | MORE at a command prompt will give you the list of options and syntax.
What records of logon and logoff times have you got in your Event Viewer, have you looked in there? Use the Security Log and use the Filter option to narrow down your search.
This is an example of what is in there.
Event Type: Success Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 528
Date: 4/10/2003
Time: 8:06:43 AM
User: xxxx
Computer: xx
Description:
Successful Logon:
User Name: xxxx
Domain: xx
Logon ID: (0x0,0x11760D)
Logon Type: 2
Logon Process: User32
Authentication Package: Negotiate
Workstation Name: xx
Logon GUID: {00000000-0000-0000-0000-000000000000}
"Subject: Setting Restricted Login Hours on XP Standalone System
I recently had to contact Microsoft Tech Support for assistance on this so I wanted to post the article on the web incase someone else had this same issue.
Situation: You want to restrict the logon days / times of a user account in XP and are a standalone machine.
Reason: You may wish to restrict teens who arrive home before adult supervision from accessing your broadband always on connection, limit employees to only work hours access etc..
Steps:
To Set restrictions:
Click Start
Click Run
Type cmd in the run box and press enter.
The following is a sample of what you would type:
net user testuser /times:M-F,5pm-9pm; Sa,6am-9pm;Su,6am-9pm
Where testuser is the local account name.
To Remove Restrictions:
Click Start
Click Run
Type cmd in the run box and press enter.
The following is a sample of what you would type:
net user testuser /times:all
Where testuser is the local account name."
137978 - Using NET USERS to Manage Local User Accounts on a Workstation
Typing NET HELP USERS | MORE at a command prompt will give you the list of options and syntax.
What records of logon and logoff times have you got in your Event Viewer, have you looked in there? Use the Security Log and use the Filter option to narrow down your search.
This is an example of what is in there.
Event Type: Success Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 528
Date: 4/10/2003
Time: 8:06:43 AM
User: xxxx
Computer: xx
Description:
Successful Logon:
User Name: xxxx
Domain: xx
Logon ID: (0x0,0x11760D)
Logon Type: 2
Logon Process: User32
Authentication Package: Negotiate
Workstation Name: xx
Logon GUID: {00000000-0000-0000-0000-000000000000}
. Audit principles apply to connection start and end.
The audit log appears in the Security log in Event Viewer. To enable this feature:
Click Start, click Control Panel, click Performance and Maintenance, and then click Administrative Tools.
Double-click Local Security Policy.
In the left pane, double-click Local Policies to expand it.
In the left pane, click Audit Policy to display the individual policy settings in the right pane.
Double-click Audit object access.
Select the Success check box for the security objects you want audited for successful use.
To audit unsuccessful access to these objects, select the Failure check box.
To enable auditing of both, select both check boxes.
Click OK.
The XP restrictions on connections will not bounce someone who is logged on prior to the end of the limit you set and stays connected. It only bars new logons. To end connected sessions you can use Third-Party tools. An inexpensive one is Sleepy:
The audit log appears in the Security log in Event Viewer. To enable this feature:
Click Start, click Control Panel, click Performance and Maintenance, and then click Administrative Tools.
Double-click Local Security Policy.
In the left pane, double-click Local Policies to expand it.
In the left pane, click Audit Policy to display the individual policy settings in the right pane.
Double-click Audit object access.
Select the Success check box for the security objects you want audited for successful use.
To audit unsuccessful access to these objects, select the Failure check box.
To enable auditing of both, select both check boxes.
Click OK.
The XP restrictions on connections will not bounce someone who is logged on prior to the end of the limit you set and stays connected. It only bars new logons. To end connected sessions you can use Third-Party tools. An inexpensive one is Sleepy:
- Status
Similar threads
