locked
Server GPO - apply once and do not reapply is not working RRS feed

  • Question

  • Hi,

    we do have a couple of terminal server (running Server 2016). We are trying to configure some settings via group policy and the "Apply once and do not reapply" option.

    Sadly it's just not working. The "apply once id" is correctly added to HKLM\Software\Microsoft\GroupPolicy\Client\Runonce" (or the corresponding path in HKCU), but its still applied every time we run a gpupdate, reboot or login. We tried it for a registry item as well as for a file creation. 

    Item level targeting is not active; we also recreated all settings, to be sure they do not have the same id (which at least seemed to be a problem for runonce in the past). 
    We are using loopback mode - but as far as I am aware loopback mode is not affecting runonce (or am I wrong)?

    Any idea what else might go wrong here?

    Thanks a lot


    Monday, July 20, 2020 11:26 AM

All replies

  • Hi,

    Thank you for posting in our forum

    This issue occurs because the Registry GUID for the RunOnce registry value on the client computer is created regardless of whether the Group Policy preference settings are applied or not.

    Note The Registry GUID is created in one of the following locations, depending on whether the Group Policy preferences setting applies to a computer or to a user:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Group Policy\Client\RunOnce
    HKEY_CURRENT_USER\Software\Microsoft\Group Policy\Client\RunOnce

    A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

    If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

    Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
    http://support.microsoft.com/contactus/?ws=support

    Hope this information can help you
    Best wishes
    Vicky

    This "Group Policy" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details


    "Group Policy" forum will be migrating to a new home on Microsoft Q&A!

    We invite you to post new questions in the "Group Policy"  forum's new home on Microsoft Q&A!

    For more information, please refer to the sticky post.


    Tuesday, July 21, 2020 9:06 AM
  • Hi,

     

    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

     

    Best Regards,

    Vicky


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 24, 2020 7:46 AM
  • Hi,

     

    Just want to confirm the current situations.

     

    Please feel free to let us know if you need further assistance.

     

    Best Regards,

    Vicky 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 27, 2020 8:37 AM
  • Hi Vickydad,

    thanks for you reply. Actually our configuration was totally fine, just the profile (fslogix) was broken. After we deleted the profile anything worked fine and as we expected.

    I read about the hotfix but as it was some years old i expected it the be included in the current (patched) version of Windows Server 2016. 

    Thanks a lot 

    Monday, July 27, 2020 11:21 AM