Re: AutoLogoff via Time Restrictions...

From: Bjørn Lunde (bjornlunde@hotmail.com)
Date: 11/04/02 

From: Bjørn Lunde <bjornlunde@hotmail.com>
Date: Mon, 4 Nov 2002 04:43:13 -0800

I think, perhaps, you could also in fact do this by
enabling the forced logoff as a GPO on the servers in
question, and not on the workstations.

This is, of course, the simplest (and best) solution,
and my apologies to you for serving you with my original
suggestion.

In my defence I can only say that the former would (I
think) also work.

Tell me how it works out.

Yours

Bjørn Lunde
>-----Original Message-----
>You can do it by using a combination of local and domain
>user accounts.
>
>If you have a windows 2000 domain, you may grant users
>access to resources throught domain user accounts. On
>these you can enforce log on restrictions (log on hours).
>You then enable the policy to force logoff when logon
>hours expire for the domain.
>
>If you want users to still be able to work using their
>workstations, they need to do so by using local user
>accounts. These will not be affected by the domain
policy.
>The workstations are in this scenario not members of the
>domain. I think I remember testing this for windows 2000
>Server and a Windows XP Professional workstation once,
and
>I think I also remember that it worked :)
>
>Good luck to you
>
>Regards,
>Bjørn Lunde
>
>
>
>>-----Original Message-----
>>
>>>From what I can tell Winexit works mostly for Idle time
>machines...
>>We are looking to force people off based on domain time
>restrictions.
>>The only policy I saw on the workstation was under
>>
>>\security\templates\setup security\local
>policies\security\options
>>
>>Automatically log off users when logon time expires
>>Automatically log off users when logon time expires
>(local)
>>
>>The local version is enabled... The other is 'not
>defined'
>>I'm under the assumption the the other one is
>for 'domain' logins but
>>I did not want to fool around with it unless I was
>sure...
>>
>>
>>On Sat, 2 Nov 2002 13:45:19 -0600, "Shenan T. Stanley"
>><shenans@hotmail.com> wrote:
>>
>>>Winexit screensaver from Resource Kit?
>>>The policies on the servers should also allow this - if
>they are logging
>>>into the domain and not just mapping the resources.
>>
>>.
>>
>.
>

Relevant Pages

  • Re: locking server
    ... >> console in our servers in case the admin forgets to do that. ... >> Amount of idle time required to disconnect session. ... >> Automatically log off users when logon time expires. ...
    (microsoft.public.windows.group_policy)
  • Re: locking server
    ... > console in our servers in case the admin forgets to do that. ... So far I have enabled(in the servers policy): ... > Automatically log off users when logon time expires. ...
    (microsoft.public.windows.group_policy)
  • locking server
    ... our servers in case the admin forgets to do that. ... Computer configuration> Windows settings> security settings> local ... Automatically log off users when logon time expires. ...
    (microsoft.public.windows.group_policy)
  • Re: locking server
    ... You can, of course, force the screensaver settings via GP - User ... console in our servers in case the admin forgets to do that. ... Automatically log off users when logon time expires. ...
    (microsoft.public.windows.group_policy)
  • RE: Optimize SMB on server to accomodate slow WAN link
    ... The lack of bursting is really a function of the carrier, ... especially if you have servers in the ... Advertising of shares/printers by workstations and servers ... the central office that they do not need to be connecting to. ...
    (microsoft.public.win2000.networking)