SMBKitchen: Disabling IPv6… or not

Our next step according to the Exchange deployment assistance is to…. excuse me?  Disable IPv6? 


If you’ve been a SBSer for any number of years you’ll know is is a step that one shouldn’t do on a SBS box  (see http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx )


So, I’m going to first bug this in connect as I don’t think this is a valid step and then I’m going to ignore it and go onto the next step


Ignore the following and click next on the instructions


Disable IPv6 on Exchange 2007 servers


Estimated time to complete: 5 minutes

Before you install Exchange 2013, you might need to disable IPv6 on some of your Exchange 2007 servers. Some connections between Exchange 2007 and Exchange 2013 don’t work correctly when IPv6 is enabled and an Exchange 2007 server has both the Mailbox and Client Access server roles installed.

If you have Exchange 2007 servers that have both the Mailbox and Client Access server roles installed, complete the following steps on each of those servers to disable IPv6 on them.

Do the following on each Exchange 2007 server in your organization that has both the Mailbox and Client Access server roles installed:

  1. Open the Registry Editor on your Exchange 2007 Client Access server.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
  3. If the DisabledComponents entry doesn’t exist, do the following to create it:
    1. In the Edit menu, click New, and then click DWORD (32-bit) Value.
    2. Type DisabledComponents and then press enter.
  4. Double-click DisabledComponents.
  5. In the Value data field, enter 0xFFFFFFFF.
  6. Click OK.
  7. Reboot the server.

To verify that you’ve correctly set the DisabledComponents in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\, do the following:

  1. Open a Windows command prompt.
  2. Run the following command:

 



  1. Reg Query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents
    

If the DisabledComponents entry is properly set, you’ll see the following:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
    DisabledComponents    REG_DWORD    0xFFFFFFFF

If you see a value other than 0xFFFFFFFF for the DisabledComponents entry, or if you receive the error ERROR: The system was unable to find the specified registry key or value., the entry isn’t set correctly. Verify that you placed the DisabledComponents entry in the correct path and that it’s spelled correctly.

One Thought on “SMBKitchen: Disabling IPv6… or not

  1. Jeff Vandervoort on February 27, 2014 at 6:36 am said:

    Hi Susan, thanks for this blog entry.

    I just got to the same step and disabled IPv6 on the SBS2008 by using the registry entry, and rebooted it. Major connectivity issues after that. For example, Win 7 clients had to be disconnected from the LAN from bootup through logon; then they’d work. Set DisabledComponents to 0 and rebooted the SBS and it was back to normal.

    So I’m all in favor of not disabling IPv6, but you never came back to confirm that the Bad Things that EX2013 Deployment Wizard promised did not come to pass.

    Were you able to complete the migration successfully with IPv6 enabled?

    Thanks!

Post Navigation