Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm in the process of deploying a bunch of Win2K8R2 VMs via vSphere's deployment template stuff, and in the deploy specification it allows you to punch a list of commands to run. Aside from activating Windows (which it doesn't do), it works pretty well.

Does anyone know the command-line equivalent of going into a network adapter's properties and unchecking the IPv6 box? If I had that I could put that in the spec and not have to manually uncheck the IPv6 box.

share|improve this question
up vote 3 down vote accepted

this could do the trick ->

Here is a simplified command (thanks @jscott for the tip!):

reg add HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents /t REG_DWORD /d 000000ff /f

Microsoft provides instructions on how to disable IPv6, see the question titled: Q. How do I disable IPv6 in Windows Vista and Windows Server 2008?

share|improve this answer
And for GPO Settings:… – patricks Dec 23 '10 at 15:52
Ugh, a batch file to ECHO the command lines in the console? I would look at the REG command instead -- you could do this in one line. Aside: You may also want to consider including example code in your answers and providing a link to the source. Should the target site of your link go offline, your answer is now out-of-context. – jscott Dec 23 '10 at 15:53
@jscott: Done. Thanks for the info! – patricks Dec 23 '10 at 16:01
I added /f to the command to ensure overwrite without prompting. Thanks for improving your answer, +1. – jscott Dec 23 '10 at 16:06

I know we all do this (disable ipv6 because we're generally not using it internally in Windows domain environments) and oldskools's answer is just about the best way to do this but there are some words of caution that should be pointed out.

Microsoft test everything with ipv6 enabled and do not test current generation OS's (Vista, 7, W2K8/R2) with it disabled. So far this has never been a major issue for me but I have come across situations where this has caused problems (Exchange 2007 to 2010 upgrade). The reason that there is no longer a simple option e.g. (netsh ipv6 disable) to do this is that Microsoft would prefer it if we didn't do this.

Disabling ipv6 (or ipv4 for that matter) after you have installed the DNS server role on a server you will experience timeouts.

Even without ipv6 enabled you may find that some ipv6 activity (DNS again) is going on and if your DNS server is returning answers to AAAA requests then there may be additional name resolution traffic, and possibly requester side timeouts, while they are being dealt with.

This Technet Blog article expands on this, and specifically mentions that Microsoft's Common Engineering Criteria require ipv6 support to be enabled. At some point enabling ipv6 will be required and since there is no simple way (ie by GPO) to do this globally we're all looking at creating some work for ourselves in the future when we are forced to (re)enable it in order to remain supported by Microsoft.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.