GPO Registry and Startup Scripts failing to apply

robke

1/19/24, 12:11 AM

I've been working on a relatively simple GPO to lock down some machines that will act as "kiosks". All the policies/preferences etc that I've set have worked fine except for registry changes (using Computer Config > Preferences > Windows Settings > Registry) and startup scripts in an attempt to have the registry changes occur via a batch/PS script (Computer Config > Policies > Windows Settings > Scripts). In both cases, gpresult doesn't show these changes attempting to be made at all. They don't show up in my results.html anywhere whatsoever.

The OU that my GPO is applying to is blocking inheritance and there are no "enforced" GPOs above mine.

Anyone have any experience with this? Again, every single other change I've made in the GPO has worked (or at least I can see them in gpresult to see if/why they're failing to apply).

0 + 2

windows

group-policy

Pierrot8086

8/21/24, 9:09 PM

do you have computer where you want to apply this gpo in the security filtering or only Authenticated users? Best regards,

Jan

8/22/24, 5:34 AM

Create a new GPO, do not modify anything else. Put in a dummy script that does not change anything important on the target machine and see if that script is now getting applied.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: GPO Registry and Startup Scripts failing to apply

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.