Sign in
 

none
Latent TCPIP Settings Causing GPUPDATE errors

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello All

    I am having a problem with GPO settings I have removed causing errors with gpupdates.

    I was having some issues with the 6to4 IP address showing up in the DNS and causing some connection issues, so I originally disabled the 6to4 adapter via GPO (Computer \ Policies \ Administrative Templates \ Network \ TCPIP Settings \ IPv6 Transition Technologies \ 6to4 State - configured and set to disabled). 

    Later we decided it would be better to simply disable the IP Helper service - so we did this system-wide, then set this policy setting back to "Not configured."

    However, now whenever my clients do a GPUpdate, they all end up with an error for the TCPIP settings.  The error message in the RSOP shows that it cannot apply TCPIP settings because the service (the IP Helper service) is not running.

    Why is it still trying to apply TCPIP settings if I set them all back to Not Configured? How do I clear out this error without having to re-enable the IP Helper service everywhere?

    Thanks in advance!

    Thursday, April 7, 2016 9:22 PM
    |

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    > Why is it still trying to apply TCPIP settings if I set them all back to
    > Not Configured? How do I clear out this error without having to
    > re-enable the IP Helper service everywhere?
     
    Lets have a look at this setting in tcpip.admx:
         <policy name="6to4_State"
    clientExtension="{cdeafc3d-948d-49dd-ab12-e578ba4af7aa}" class="Machine"
    displayName="$(string.6to4_State)"
    explainText="$(string.6to4_State_Help)"
    presentation="$(presentation.StateSelection)"
    key="Software\Policies\Microsoft\Windows\TCPIP\v6Transition">
     
    The important part is that this setting is delivered to the client
    computer via ADM templates, BUT it has its own client side extension
    defined.
     
    If you configured settings that contain this extension, it will be
    invoked on each subsequent policy processing. And if you removed the
    last setting for this extension, it will recognize that and not be
    called again (usually, at least :-)).
     
    In your GPO, you removed the settings. But since the IP helper was
    disabled earlier, it cannot process this removal.
     
    Friday, April 8, 2016 12:19 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Quick update: I completely disabled the GPO that previously held these settings, and I still get an error message about TCPIP settings failing to apply because the service is not started.

    Is there something latent on the client that needs to get flushed or refreshed?

    Thursday, April 7, 2016 9:46 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    > Why is it still trying to apply TCPIP settings if I set them all back to
    > Not Configured? How do I clear out this error without having to
    > re-enable the IP Helper service everywhere?
     
    Lets have a look at this setting in tcpip.admx:
         <policy name="6to4_State"
    clientExtension="{cdeafc3d-948d-49dd-ab12-e578ba4af7aa}" class="Machine"
    displayName="$(string.6to4_State)"
    explainText="$(string.6to4_State_Help)"
    presentation="$(presentation.StateSelection)"
    key="Software\Policies\Microsoft\Windows\TCPIP\v6Transition">
     
    The important part is that this setting is delivered to the client
    computer via ADM templates, BUT it has its own client side extension
    defined.
     
    If you configured settings that contain this extension, it will be
    invoked on each subsequent policy processing. And if you removed the
    last setting for this extension, it will recognize that and not be
    called again (usually, at least :-)).
     
    In your GPO, you removed the settings. But since the IP helper was
    disabled earlier, it cannot process this removal.
     
    Friday, April 8, 2016 12:19 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Martin,

    Thank you for your reply, it was very helpful.

    I temporarily re-enabled the IP Helper, performed a GPUpdate, then disabled it again, did another GPUpdate, and the error seems to have been resolved!

    Friday, April 8, 2016 1:24 PM
    |