Windows 7 Deployment - TCP/IP v6 - Automate Removal


  • Hello-

    Is there a way to automate the removal of IPv6?  We use WDS with MDT to deploy Win7 machines.  The most recent custom WIM file already has the "DisabledComponents" value in the registry.  For existing 7 machines, we just used GPO to push out that reg value.  But for the network adapter, it still has the IPv6 ticked. 

    We thought by making sure the custom WIM file had that unchecked, that all would be cool. Unfortunately, when building a new machine, it resets that.

    Is there a post-build script that we can insert into a Task Sequence that will uncheck that?


    Wednesday, February 22, 2012 3:15 PM


All replies



    As you are using the WDS with MDT to deploy the system, in order to get the answer effectively, it is recommended to post a new question in Setup Deployment Forum for further discussion.

    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.



    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    TechNet Community Support

    Thursday, February 23, 2012 6:04 AM

    Go to the table with

    Disable IPv6

    click on "Fix this problem"

    Download the msi package and then you can set that up in MDT as an application and run it in task sequence

    • Marked as answer by Dave-LVP Thursday, February 23, 2012 3:06 PM
    Thursday, February 23, 2012 6:15 AM
  • The checkbox is still there but the article says that as long as the reg value is inserted, it will effectively kill IP6 on all interfaces:

    "Therefore, even if the DisabledComponents registry key is set to disable IPv6, the check box in the Networking tab for each interface can still be checked. This is expected behavior."

    Hopefully I interpreted that correctly. 

    Thursday, February 23, 2012 3:08 PM