• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 475
  • Last Modified:

the screens are not automatically timing out and prompting for a login after leaving the pc

We have a new network with windows 7 workstations and a Windows 2008 R2 server. We have noticed on both that when leaving the computers or the server unattended for a bit....after returning there isn't the usually computer has been locked, please hit ctrl alt del to login.....like we are used to on our previous XP workstations and Server 2003......  a nice feature that doesn't seem automatic anymore??  what do we do to have this work as before?
0
holcomb_frank
Asked:
holcomb_frank
1 Solution
 
MdraggaCommented:
The lock usually happens after a period of inactivity when the screen saver comes up. Have you looked at the screen saver settings to see if the On resume, display logon screen box is checked?

http://www.sevenforums.com/tutorials/15322-screen-saver-password-protection-enable-disable.html
0
 
Sikhumbuzo NtsadaCommented:
Use power options in control panel
0
 
bitlaCommented:
Control Panel-->All Control Panel Items-->Power Options. Click "Change plan settings" of the selected plan. Please check if the computer is set to enter Sleep Mode after idling for 10 minutes.
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
jasonhdzCommented:
You can set the inactivity period on the screen saver.  Right click the desktop > Properties.  Look for the screen saver and check password protected.  You can set this as a GPO Administrative Templare for all pc on your network as well.  
0
 
jasonhdzCommented:
Have you Tried a clean reboot of both systens and then apply the settings individually on both machines?  
Reason is because i have both OS at the testing lab and is working fine.
0
 
holcomb_frankAuthor Commented:
It would seem that in the past, lets say a SBS 2003 domain controller and a Windows XP workstation......   I was always under the understanding that the if the workstation or server were left idle for a set period of time, the screen lockout would appear and that it would require a username and password to log back in as a security feature. And that this feature was not a result of the screen saver password setting on each work station, but was set by group policy from the server when you log into the domain. And that at each workstation, the option to change the passworded screen saver would be greyed out.

Now in Windows 7 , SBS 2008 environment it's totally dependent on the screen saver of each workstation and each user could possibly change this unless i edit the registry or local policy to prevent it??
0
 
jasonhdzCommented:
You can control all this settings, including the registry keys from the GPO console at your Domain Controller.  Then apply that GPO to your desired Organizational  unit.  The GPO has two sets: one at the domain setting and you can also apply local pc settings.  A work around would be to apply the settings on pc that the common image distribution will be extracted  and then use the image for
every workstation.  However, at the domain GPO you could set User Right Permissions to take away user privileges for changing the pc settings (from power settings to desktop properties).
0
 
holcomb_frankAuthor Commented:
I will have to look deeper at the domain GPO , i don't want to restrict everything.....most users have admin permissions.....but we want to avoid a user walking away from a workstation without logging out or locking it.....  in the past I think this was by default from the domain controller.....it would appear that newer os's don't set these features by default any more?
0
 
jasonhdzCommented:
after you applied the setting in the administrative template on the GPO, you force an update.  you can test one single workstate and run the command in command prompt gpupdate.exe

I have tried it at home with my Windows 2008 Domain Controller and Win7 client and XP and it is working.  
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now