Fixlet to disable IPv6 on Win7 and 2008 Machines

Content Authoring
1

(imported topic written by virtual4ever)

I am new to tivoli endpoint manager and was given the task of creating a fixlet to disable IPv6 on our client computers.I want to create a fixlet to edit the registry based on the instructions in this Microsoft article. http://support.microsoft.com/kb/929852. What is the best starting point to get this fixlet started ? I have both 32 and 64bit clients.

Thanks for you help in advanced.

2

(imported comment written by SystemAdmin)

Based on the Microsoft article you referenced, I’ve created a fixlet to disable IPv6 on Win7 and Server 2008 clients.

It’s in the attached .ZIP file. I STRONGLY recommend you test it on several computers before deploying it broadly. I only tested it on my Win7 workstation.

Unzip the attached file and import it using your console.

Please let me know if it does what you wanted.

3

(imported comment written by virtual4ever)

Thanks for the help with this fixlet… after reading a few post and different examples I was able to create one on my own. However I noticed that you have “of native registry” as part of your relevance clause, which wasn’t use on the one I created. What’s the reason for using this clause and why did you use dword=11 ? please have a look at the one I created and let me know if you have any suggestions.

Thanks

4

(imported comment written by SystemAdmin)

As I understand it “of native registry” tells the client to look in the registry using the x86/x64 methods as appropriate. It’s a more generic way of looking at the registry.

I used dWord 11 because that’s what the Microsoft article indicated would “disable” the IPv6 components most completely (0x11). When I tested the fixlet, it removed all reference to IPv6 from the “IPCONFIG /all” output after a reboot.

5

(imported comment written by SystemAdmin)

I looked at your Fixlet. You did a good job.

One difference in the Relevances is that I looked for any machine that either didn’t have the DisableComponents value or where it didn’t match what I was going to set it to. You look for systems where DisableComponents either didn’t exist or was set to 0. Before I wrote the fixlet, I created a retrieved property to pull the DisableComponents value (or return N/A). I got back some strange values from a handful of computers. Given that we are not using IPv6, I was surprised to see it. They were all VMware guest OS’s. I wanted my fixlet to target anything with IPv6 enabled since I’d have the ability to target using the Retrieved property if I needed to avoid a particular set of systems.

In re-reading the Microsoft Article, I think I prefer your setting of dword:ffffffff. The difference is that using dword:ffffffff does the same as 0x11 but configures the computer to prefer the IPv4 protocol while leaving the IPv6 loopback adapter in place, while dword:0x11 simply disables everything except the loopback adapter.

If you want it, the relevance for my retrieved property is in the attached TXT file.