[gptalk] WAS RE: Re: Disabling Computer Accounts
- From: "Darren Mar-Elia" <darren@xxxxxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Thu, 25 Jan 2007 13:39:27 -0800
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/
************************
Other related posts:
