Title: Message
This works for Win2000 only it says.  What if you don't want a GPO to apply to an XP box?  Put the XP box in a group and restrict access in the GPO rights to that group?
-----Original Message-----
From: Narkinsky, Brian [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 9:36 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Weird GPO question

Perfect exactly what I needed.

 

Brian

 

-----Original Message-----
From: Fuller, Stuart [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 5:32 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Weird GPO question

 

Brian,

 

Look at Group Policy loopback - See http://support.microsoft.com/default.aspx?scid=kb;en-us;231287

 

-Stuart

 


From: Narkinsky, Brian [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 2:26 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Weird GPO question

We are trying to develop a GPO to enforce a screensaver/workstation locking.  We have it working fine as long as we apply it to the Users OU.  However here is the problem.

 

We want to enforce this policy by machine.  We have lots of laboratory equipment that people watch the screen "hands off"

 

SO we don't want these machines locking.  I thought if I applied the GPO to an OU with computer accounts in it the users would pick up the settings when they logged onto that machine.  But the only way they pick it up is if I apply it to the users OU. 

 

SO how do I make a user setting apply to a group of machines? I was thinking of modifying the templates so the the Screen Saver settings are in the machine section.  But am I missing something here.

 

Forgive me if I sound/am terribly confused.

 

Brian

 

 

 

Brian Narkinsky

System Manager

Department of Environmental Protection

MS 6520

2600 Blairstone RD

Tallahassee, FL 32399

phone (850)245-8314

fax (850)412-0400

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail is confidential, may contain proprietary information
of the Cooper Cameron Corporation and its operating Divisions
and may be confidential or privileged.

This e-mail should be read, copied, disseminated and/or used only
by the addressee. If you have received this message in error please
delete it, together with any attachments, from your system.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to