Darren, I just needed to wait for the refresh interval. The screen saver GP is working! Thank you for your help! Chris -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Williams Sent: Friday, January 26, 2007 11:01 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: WAS RE: Re: Disabling Computer Accounts Darren, I linked the screen savers lock GP to the users OU but the policy is still not working. What am I overlooking? I set this GP up like the other ones and this is the only one that I can't get to work... Chris -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Thursday, January 25, 2007 2:32 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: WAS RE: Re: Disabling Computer Accounts Chris If you set the policy on the user configuration side of the GP Editor, then you need to link it to users to take effect. So if right now its linked to OU that only contains computers, it will not work. It would need to be linked to an OU containing the users you want to control. Darren -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Williams Sent: Thursday, January 25, 2007 2:31 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: WAS RE: Re: Disabling Computer Accounts Darren, I created a Group Policy for the workstations to Password protect when the screen saver comes on. I have it linked and enforced to the OU that contains all the workstations, however, the workstations aren't being password protected. Should I run GPUpdate? I have other GP's created, linked and enforced that work with no issues. Do I need to link the GP to the users instead of computers? I'm not sure what to do except go to each workstations display properties and check the box to password protect, which I don't want to have to do. Let me know what you can come up with? Thanks, Chris Williams, MCSE NT4 & 2000 -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Thursday, January 25, 2007 1:39 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] WAS RE: Re: Disabling Computer Accounts Chris- I'm a little confused on your question, since it was asked on this thread, which was started by Neil. What exactly is not working? -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Williams Sent: Thursday, January 25, 2007 11:24 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Disabling Computer Accounts Mathieu, I think you have my case confused with someone else. My issue is the Password protect group policy that for some reason is not being applied to the workstations... Chris -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Mathieu CHATEAU Sent: Thursday, January 25, 2007 11:04 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Disabling Computer Accounts hello, on the GPO to block, add IPSEC so to deny any non encrypted traffic (mandatory to encrypt). As only these stations uses IPSEC, they won't be able to connect to others workstations neither servers. The only solution for those bad boys is to stop the ipsec windows service, so you will enforce it started through the same GPO Regards, Mathieu CHATEAU http://lordoftheping.blogspot.com ----- Original Message ----- From: <neil@xxxxxxxxxxxxxxxx> To: <gptalk@xxxxxxxxxxxxx> Sent: Thursday, January 25, 2007 5:03 PM Subject: [gptalk] Disabling Computer Accounts > Hi all, > > Does anyone have any ideas on how best to achieve the following. > > I need to make a computer that is intially built into the domain - > virtually unusable until it is placed in the correct OU. > > I had thought of applying a very restrictive GPO to the default computers > OU which made it unusable but not quite sure which settings to apply and > if there are any issues with doing this. > > It is bascially to stop people bypassing build procedures and policies and > not putting the computer into the correct OU. > > Thanks for any thoughts :) > > Neil > *********************** > You can unsubscribe from gptalk by sending email to > gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by > logging into the freelists.org Web interface. Archives for the list are > available at //www.freelists.org/archives/gptalk/ > ************************ > *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ [For your protection, this messages has been scanned for viruses.] *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ [For your protection, this messages has been scanned for viruses.] *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ [For your protection, this messages has been scanned for viruses.] *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ [For your protection, this messages has been scanned for viruses.] *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************