Limiting the time spent on Internet using the Active Directory

Have some kids and computers at home, that I want to have control over internet use. Want to set up that they get to use the internet like an hour for the day. There are many programs you can install on your computer that lets them be automatically logged off after an hour or more.

Controls the home network via Windows Server 2008, and wonder if there is any way to get the same effect by using the AD? Or so the kids can just go on a different computer and get an hour to. You can determine what the time the barn to get to log on, but that is not what I want to get to.

Someone who knows about any way to get to this?

You have the ability to control the length of a session, but there is no automatism in the control interval between two sessions.

What you can do is to create a script for login that checks when the user was logged in last, and if the time is now less than a session length + pause length that is not permitted sign or the like.

Now I'm not really a racer on scripting, but it is such a solution I see would be the most appropriate.

The alternative is to tell the children that, when they are disconnected so it must be a minimum of x hours / minutes before they log on again. So you can check your login in the log afterwards and follow up on any criminal against what you have said.

This can be a great way to teach children discipline perhaps.

Have thought of it to script it, but as you say, so it is not so steady on the scripting. With it I was wondering is if there are any for the complete solution for this? Built in the OS or 3 party software. There are many solutions for this on local computers, but it involves the active directory.

There you can do is to restrict the login to a certain time, for example, between 13 and 14 Then the users could not log on without this time. Was perhaps not quite what you wanted, since users do not choose for themselves when they want to use their time, but if it's interesting, you may find the option in the properties for the group/users, I believe. Was at least some such in Windows Server 2003, has never even used the 2008.

One of your problems that I see immediately is the example. that the profile is stored locally. If the user takes out the network cable before the login will not get the machine settings from the AD server, user gets logged in that way.