Local policy edits not taking affect when using Set

[ddmee]

Hi, thanks for the module. It's very good. The help text from about_RegistryValuesForAdminTemplates.Help.txt was very helpful.

I found that when I set a local policy group option, the machine didn't update it's policy until after a reboot or until I ran the command gpupdate /force

So for instance, I ran the command
Set-PolicyFileEntry $env:systemroot\system32\GroupPolicy\Machine\registry.pol -Key 'Software\Policies\Microsoft\Windows\Explorer' -ValueName 'NoNewAppAlert' -Data 1 -Type DWord

The affect didn't take place until after I ran gpupdate /force

I think this is fine but I didn't see anyway in the help information or documentation on set-PolicyFileEntry that you need to then call gpupdate/reboot.

Is this expected behaviour of the module?

[dlwyatt]

Group Policy automatically refreshes on a schedule, but you can force it faster with the methods you mentioned.

…

On Jan 23, 2019, at 8:20 AM, Donal ***@***.***> wrote: Hi, thanks for the module. It's very good. The help text from about_RegistryValuesForAdminTemplates.Help.txt was very helpful. I found that when I set a local policy group option, the machine didn't update it's policy until after a reboot or until I ran the command gpupdate /force So for instance, I ran the command Set-PolicyFileEntry $env:systemroot\system32\GroupPolicy\Machine\registry.pol -Key 'Software\Policies\Microsoft\Windows\Explorer' -ValueName 'NoNewAppAlert' -Data 1 -Type DWord The affect didn't take place until after I ran gpupdate /force I think this is fine but I didn't see anyway in the help information or documentation on set-PolicyFileEntry that you need to then call gpupdate/reboot. Is this expected behaviour of the module? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[AGenchev]

hmm I'm on windows10 20H2 and there is no such file (registry.pol).
Moreover, the string "Password must meet complexity requirements" from gpedit.msc is not present in any of the .adml files in %SystemRoot%\PolicyDefinitions\en-US\

so it can't be traced to its registry key.

Do you have idea whether things have changed or just my windows 10 installation is broken ?

[metablaster]

hmm I'm on windows10 20H2 and there is no such file (registry.pol). Moreover, the string "Password must meet complexity requirements" from gpedit.msc is not present in any of the .adml files in %SystemRoot%\PolicyDefinitions\en-US\

so it can't be traced to its registry key.

Do you have idea whether things have changed or just my windows 10 installation is broken ?

"Password must meet complexity requirements" does not belong to administrative templates.

Registry.pol file is located in:

• C:\Windows\System32\GroupPolicy\Machine
• C:\Windows\System32\GroupPolicy\User

Note that GroupPolicy folder is hidden so you need to show hidden files in windows explorer options.
edit:
If you're on Window Home edition then the file won't exist because GPO is not available on Home editions.