Re: GPO doesn't take effect on the clients

Howdie!

MSExchangeStudent schrieb:
The 2 DC's in my company is listed under that OU.

You configured a Computer Configuration-policy and you therefore need to have machine objects in that OU.
Are the workstations joined to the domain (correctly?)

Yes. There are a default domain policy that i assume work 100% because it autimatically give evyone access to the internet if you join the domain.

The 2 DCs are listed under that OU? Did you link the policy to the "Domain Controllers" OU or did you just move the DCs out there into a seperate OU?

Do the workstations' DNS settings point to a Domain Controller (as the only, primary source)?
Yes. That is set in the network properties to pick up the DNS automatically and all the pc's point to 192.168.150.101 as the DNS. This is also the pc that i try to work on the GPO through AD

So 192.168.150.101 is your Active Directory Domain Controller, right? The client's DNS must point to the IP of a Domain Controller.

If nothing helps, try that:

Go create an OU. Put an Active Directory account of a workstation into that OU. If you wish, the guy next to you's machine. Then create a Group Policy at that exact you just created and configure the Computer Configuration\... setting. Does that work? If not, what does "rsop.msc" say after you tried "gpupdate"?

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
.

Relevant Pages

  • Re: client not connetct to domain
    ... DNS is configured in that DC, where the client's DNS is pointing to? ... Restoration of System State ... Checking Group Policy ... Host records that map the name of the domain controller to its IP ...
    (microsoft.public.windows.server.active_directory)
  • Re: Group Policy issue and Solution?
    ... domain controllers was not properly registered in dns or dns was not working ... Normally you want the first domain controller ... and then itself in it's list of preferred dns servers. ... I don't know of a way to prevent a user to logon if Group Policy is not ...
    (microsoft.public.windows.group_policy)
  • Re: Event ID 1053
    ... Even though DNS looked fine and tested out okay, ... >> problems getting my Group Policy updates from my Domain Controller. ...
    (microsoft.public.windows.server.general)
  • Re: Error message when opening a Domain Group Policy Object
    ... The dns problem could be causing the problem opening Group policy. ... The next thing I would do is to run netdiag and dcdiag on the domain ... point to themselves or another domain controller in the domain running AD ...
    (microsoft.public.win2000.security)
  • Re: Event ID 1094 on clients
    ... the domain controller points to itself and the domain clients only point to AD domain ... controllers running dns with the domain zone - never an ISP dns server. ... Running netdiag and then ... "Windows could not set the security on Group Policy ...
    (microsoft.public.win2000.group_policy)