IPv6 group policy setting for privacy and address randomization

Our campus network requires we set two options on Windows computers for IPv6 using netsh:

netsh interface IPV6 set global randomizeidentifier=disabled store=persistent
netsh interface IPV6 set privacy state=disable store=persistent

I want to propagate this by group policy but would prefer not to have it as a startup script because it really only needs to be run once, not as added baggage to each and every boot. There are several IPv6 settings available in group policy, but these two are not among them.

Does anyone know where these settings are stored or any good way to propagate these settings? I'm hoping to be able to push a registry entry or something like that.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Unfortunately, these settings are stored in NSI, and are not exposed through the registry at all. There is no publicly available method for changing these settings other than NETSH.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MichaelSparksAuthor Commented:
I haven't heard of NSI before, what is that?
Network Store Interface; it's an internal array for interface configuration. I shouldn't have mentioned it; it's not publicly available.
MichaelSparksAuthor Commented:
Found a solution. Group Policy, Computer Configuration, Windows Settings, Preferences, Registry, add the netsh command to SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce and set it to action replace and apply once and do not reapply.

It turns out this works without having to create a batch file too, just enter the full netsh ... command with options.

I like this because it doesn't run every time adding baggage to the boot process and it doesn't use a batch file that has to be distributed or reached over the network, which also might slow down bootup, especially for mobile clients.
MichaelSparksAuthor Commented:
Helpful info that there is no other way than netsh to change those settings, but didn't answer the question of how to propagate the setting using AD.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.