Implementing Group Policy

Hi there,

My network has 2 windows 2003 servers. one is Domain Controller and 2nd is additional domain controller. On Domain Controller i went to "Active Directory Users and Computers" and created a new Organizational Unit. Where i placed a computer and user name.

Right clicked OU and clicked properties. Added a new Group Policy and disabled Control Panel under "User Confinguration". Still the computer and user name are having Control Panel when they log in to domain.

Kindly guide in this issue what step i am missing to implement Group Policy, i am very new to this thing. It would be very helpful if you could guide me step by step implementation of Group Policies.

Thanks.
chatharAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Fatal_ExceptionConnect With a Mentor Commented:
Also, this can be caused by the client not being able to find a DNS server..   Check your IP config on the client and make sure your DNS server is being correctly enumerated there...  I will assume the DNS is running on your Domain Controllers, and you have given each of them static addresses...  you should have both addresses being given out for DNS resolution..  

You may want to also ck your DNS mgmt console on the servers to see if the forward lookup zone is being correctly enumerated too..

FE
0
 
Pete LongTechnical ConsultantCommented:
if your clients are XP troubleshoot them using the following

See what policies are being applied to XP

First
Click Start >run >cmd {enter}
gpupdate /force {enter}
Let the client reboot.

After a reboot
Click Start >run>mmc {enter}
File>add/remove snap in >add
Add in the “Resultant set of policy”

Get IT Done: Troubleshoot group policies with Windows XP's Resultant Set of Policy Wizard
http://techrepublic.com.com/5100-6270-1054826.html
0
 
JamesDSCommented:
chathar
It sounds like you policy has not yet replicated and/or not refreshed onto the client

if the client is XP then this should do it:

GPUPDATE /FORCE

If the client is 2000 then you will need to run the SECEDIT command to refresh machine_policy and user_policy

Also, use REPLMON from the resource kit to determine that your AD Domain is replicating correctly

Cheers

JamesDS
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
chatharAuthor Commented:
Still not working, i have windows 2000 workstations and i tried following commands:

SECEDIT /REFRESHPOLICY MACHINE_POLICY /ENFORCE

SECEDIT /REFRESHPOLICY USER_POLICY /ENFORCE

how can i verify if these changes are really implemented or not?

i have also restarted Client machine, tried logging in again. but no use.

Now i have also disabled "Run" form start menu to check if it works, Run option is still available on client machine.

about AD replication, it seems like replication is working fine cause the changes i make on DC are visible on ADC, even if i Edit Group Policy on ADC it is same as which i saved on DC.

i have also checked "Resultant Set of Policies" on OU and they show desired results, still i wonder y these changes are not implemented on workstation.
0
 
Fatal_ExceptionCommented:
Sounds to me like you forgot to set the security permissions on the GPO...  Go to your OU, then properties, then the GPO properties button, then the security tab...  Set the permissions for your users (or security group) to Read and Assign..  Then on the client machines, reboot each machine 3 times...  (with some GPO's, they must be rebooted a min of twice for the policy to take affect..  even secedit command will not force some policies to be pushed and accepted...)

FE
0
 
Fatal_ExceptionCommented:
BTW:  if the clients are XP Pro, then you can run the RSOP from them, and see exactly what policies they are using...  It is in the MMC (Mico Mgmt Console)..  you add the snap in and run RSOP...  but the easiest way to access it is:

Start > Run > rsop.msc (OK)

FE
0
 
chatharAuthor Commented:
i just check application log of client machine. whenever i run secedit command the application logs gets an error message

Windows cannot determine the user or computer name. Return value (1722)

what could be the reason.
0
 
fsaiexpertFSAI ExpertCommented:
You cannot restrict the control pannel for a computer, only a user. Double check the settings, remove the user teh ou, shut down and start (not reboot). Shut down agian, add the user to the ou and start again.

Make sure that the computer is connecting to the domain.
0
 
Fatal_ExceptionCommented:
Take the system out of the Domain and into a workgroup.  Delete the computer account from the Domain Controller, then go back to the client and rejoin it to the domain..  This should clear up the error message..

FE
0
 
Netman66Commented:
Two things to look for in addition to the posts above:

1)  Make sure SYSVOL on both servers is identical - if it isn't there are replication problems and the client is likely authenticating with the server that is missing information in SYSVOL.

2)  Check to make sure that the KDC Service is set to Automatic and is started - on both servers.

Advise.
0
 
chatharAuthor Commented:
Problem solved, thanks to "Fatal Exception", i had no DNS entries on client side :)
thanks for ur held dudes....!!!
0
 
Fatal_ExceptionCommented:
*grin*  DNS is the cause of most of these problems..  should have mentioned it first thing..  

Glad we got it solved..!!

FE
0
 
Pete LongTechnical ConsultantCommented:
<smile> good call
0
 
Fatal_ExceptionCommented:
*grin* back to you Pete..!!  I just got lucky, thats all...!!
0
All Courses

From novice to tech pro — start learning today.