Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

group policy update problems. 1

Status
Not open for further replies.

rizrizza

IS-IT--Management
Jan 18, 2006
42
US
so i finally got around to trashing the old admins group policies and re-worked them. my only problem is geting the computer on the domain to update to the new policies.

i went into the command line and did a gpupdate /force (client machine) and it says it's been updated so i restart the computer but nothing happens.

the only thing i've gotten to work is to take each computer off the domain then put it back on the domain which refreshes the policies.

my question is, is there an eisier more reliable way to do this?

Trying to do alot with what little I know. Thank you
 
Do a Gpupdate /f on the server, that (in theory) should refresh the policies and push out the new ones.
 
I'd do the local GPUPDATE /FORCE then reboot and then use GPRESULT to see what is being applied locally. Verify your permissions on the new GPOs and make sure they are applying to the OU where your computer accounts and users are located.

By removing the computer from the domain, the accounts will get created in the default location which would support this as a theory, but since I don't know if the existing accounts are in a custom OU or not I can't say for sure.

Also note that if you have installd GPMC, you can do modeling to see what will be applied.

I hope you find this post helpful.

Regards,

Mark
 
i was wondering just now, would a messed up DNS configuration cause the GPO to n ot refresh like it should?

i think it would explain why it works when i take the computers off the domain and then add them back on.

Trying to do alot with what little I know. Thank you
 
DNS problems can of course cause many issues in a domain.

make sure you have configured the workstations to only have your servers IP for their DNS. there should be NO ISP DNS there.

Same thing on the server NIC.

In DHCP, set the scope option for DNS to provide your internal DNS server.

In the DNS Server Snap-In, on the forwarders tab make sure you have the ISP DNS here.

I hope you find this post helpful.

Regards,

Mark
 
well thanks for pointing me in the right direction. i found multiple problems with the DNS.
1. old admin entered the wrong default gateway address.

2. ISP DNS addresses where on client machines, not the server. (again old admin)

after this was done GPO ran instantly, loggins where much much faster, and everybody has the internet. thanks everyone.

Trying to do alot with what little I know. Thank you
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top