Set action to take when logon hours expire - logoff does not work Windows 2008 and Vista ??

[Old Rookie]

Are others having any luck with this setting to work?? I am testing this
with a Windows 2008 domain controller and Vista Ultimate SP1 domain member
computer. I configured the setting in user configuration\administrative
templates\windows components\windows logon options and set it to be enabled
with the action of logoff. Test GPO is linked to the domain with domain user
in the default user container. No filtering on the GPO and no other domain
linked GPO other than default GPO that does not have this setting
configured. DNS, etc is correctly configured for the domain and client
computer. I logged on as user, ran rsop.msc on domain member computer, and
it showed that the setting I configured was applied to the domain user via
test GPO I configured.

I configured AD user account logon hours to be 6:00 AM to 9:00 PM. Ran
Gpudate on server, rebooted domain member computer, and logged on as test
user at 8:30 PM. Waited for 9:00 PM to come around and nothing happened. At
9:10 PM I tried to access share on the server and got access denied message
to to logon hours expired. Then I logged off of the domain member computer
and could not logon again because it showed logon hours had expired. But
what I really want to see is the user being logged off at 9:00 PM per the GP
setting I set and as described in the GP setting for logoff as shown below.
Other settings I have configured in the test GPO for user configuration are
working fine.

Thanks for any advice.

Steve

"This policy controls which action will be taken when the logon hours expire
for the logged on user. The actions include lock the workstation, disconnect
the user, or log the user off completely."

[unknown]

Hi,

Have you finally found how to make it work ?

Best Regards,
Julien.



Old Rookie wrote:

Set action to take when logon hours expire - logoff does not work Windows 2008 and Vista ??
11-Mar-09

Are others having any luck with this setting to work?? I am testing this
with a Windows 2008 domain controller and Vista Ultimate SP1 domain member
computer. I configured the setting in user configuration\administrative
templates\windows components\windows logon options and set it to be enabled
with the action of logoff. Test GPO is linked to the domain with domain user
in the default user container. No filtering on the GPO and no other domain
linked GPO other than default GPO that does not have this setting
configured. DNS, etc is correctly configured for the domain and client
computer. I logged on as user, ran rsop.msc on domain member computer, and
it showed that the setting I configured was applied to the domain user via
test GPO I configured.

I configured AD user account logon hours to be 6:00 AM to 9:00 PM. Ran
Gpudate on server, rebooted domain member computer, and logged on as test
user at 8:30 PM. Waited for 9:00 PM to come around and nothing happened. At
9:10 PM I tried to access share on the server and got access denied message
to to logon hours expired. Then I logged off of the domain member computer
and could not logon again because it showed logon hours had expired. But
what I really want to see is the user being logged off at 9:00 PM per the GP
setting I set and as described in the GP setting for logoff as shown below.
Other settings I have configured in the test GPO for user configuration are
working fine.

Thanks for any advice.

Steve

"This policy controls which action will be taken when the logon hours expire
for the logged on user. The actions include lock the workstation, disconnect
the user, or log the user off completely."

Previous Posts In This Thread:

On Wednesday, March 11, 2009 10:53 PM
Old Rookie wrote:

Set action to take when logon hours expire - logoff does not work Windows 2008 and Vista ??
Are others having any luck with this setting to work?? I am testing this
with a Windows 2008 domain controller and Vista Ultimate SP1 domain member
computer. I configured the setting in user configuration\administrative
templates\windows components\windows logon options and set it to be enabled
with the action of logoff. Test GPO is linked to the domain with domain user
in the default user container. No filtering on the GPO and no other domain
linked GPO other than default GPO that does not have this setting
configured. DNS, etc is correctly configured for the domain and client
computer. I logged on as user, ran rsop.msc on domain member computer, and
it showed that the setting I configured was applied to the domain user via
test GPO I configured.

I configured AD user account logon hours to be 6:00 AM to 9:00 PM. Ran
Gpudate on server, rebooted domain member computer, and logged on as test
user at 8:30 PM. Waited for 9:00 PM to come around and nothing happened. At
9:10 PM I tried to access share on the server and got access denied message
to to logon hours expired. Then I logged off of the domain member computer
and could not logon again because it showed logon hours had expired. But
what I really want to see is the user being logged off at 9:00 PM per the GP
setting I set and as described in the GP setting for logoff as shown below.
Other settings I have configured in the test GPO for user configuration are
working fine.

Thanks for any advice.

Steve

"This policy controls which action will be taken when the logon hours expire
for the logged on user. The actions include lock the workstation, disconnect
the user, or log the user off completely."


Submitted via EggHeadCafe - Software Developer Portal of Choice
Adding WCF Service References
http://www.eggheadcafe.com/tutorials/aspnet/a1647f10-9aa4-4b0c-bbd9-dfa51a9fab8e/adding-wcf-service-refere.aspx

[Florian Frommherz [MVP]]

Howdie!

Post by unknown
Have you finally found how to make it work ?

The main problem is that that GPO doesn't actually log you off after
your working ours expire but cut off SMB connections to file servers. At
least that's what it did when I last looked at it. You might want to
think about having a script or scheduled task the forces the user to log
of at a certain time.

A question you need to ask yourself is: do you really want to log the
user off the hard way? What is with files and documents the user has
open unsaved? Can applications handle this or will they break database
files and stuff? You surely want to have some kind of assurance you're
not blamed for corrupt data that comes from forced log offs. I guess
users won't be happy to be forcefully logged off.

Cheers,
Florian