Gpupdate not updating policy

28-May-2019 11:02 by 5 Comments

Gpupdate not updating policy - how to improve you dating relationship

Many of my students relate stories of making changes to Group Policy settings.

gpupdate not updating policy-89gpupdate not updating policy-23gpupdate not updating policy-65gpupdate not updating policy-32

But it’s the wrong tool for its most common use: immediately applying a setting change.

then go into Regedit and remove that user from the profilelist and restart the computer and log in as the user and there you go new GP's downloaded from the server and everything is fine.

just make sure to back up all user files and anything else they want cause it will all be deleted when you do this. Ok fixed this problem just in case anyone else ever has it here was the fix I cam up with.1st I have no idea why half the computers did this but the easy fix was to log in to the users computer as the domain admin.

With Windows Server 2012 and Windows 8, you can remotely refresh Group Policy settings for all computers in an organizational unit (OU) from one central location by using the Group Policy Management Console (GPMC).

Or you can use the Invoke-GPUpdate Windows Power Shell cmdlet to refresh Group Policy for a set of computers, including computers that are not within the OU structure—for example, if the computers are located in the default computers container.

Ok fixed this problem just in case anyone else ever has it here was the fix I cam up with.1st I have no idea why half the computers did this but the easy fix was to log in to the users computer as the domain admin.

go to the users folder and remove the users folder that is having the trouble.ok did a move about two weeks ago from an old Small biz server 2003 to server 2008 R2 we had a file redriect going for the mydocs on the old SBS 03 server.moved all the files to the new R2 server and told the GP that the new home folder was on the new R2 server.I've seen this a few times and it's usually been a profile problem.Delete (or rename) the affected profile folder and the corresponding registry items for the user (HKLM\software\microsoft\windows nt\current version\profilelist\s-1-5-21-xxxxx), and try logging them in again.When the Resultant Set of Policy settings does not conform to your expectations, a best practice is to first verify that the computer or user has received the latest policy settings.