To get a list of network adapter GUIDs, use a PowerShell command similar to the following:
Get-WmiObject -Class Win32_NetworkAdapter | ? { $_.NetEnabled } | Select-Object
-Property Name,GUID;
Cheers,
Trevor Sullivan
From: [email protected] [mailto:[email protected]] On
Behalf Of Robert Marshall
Sent: Monday, September 23, 2013 12:57 PM
To: [email protected]; 'Daniel Ratliff'
Subject: RE: [mssms] Disabling IPv6 in a Task Sequence
More Info on the tool I mentioned earlier:
http://archive.msdn.microsoft.com/nvspbind
It’s not seamless to use, you need to know the GUID of the Adapter rather than
a name but if you know the adapter name you can invoke the tool twice, once to
get a GUID then to unbind using the GUID.
It becomes very easy to setup in a task sequence, you create a package\program
with the EXE and a VBS as content, and get the program to invoke the VBS.
I use the VBS to run the EXE using the name of the adapter I setup in the Apply
Network Settings step making it a reliable adapter name, and I capture the GUID
in the output, then I invoke the EXE again to unbind IPV6 from the adapter
using the GUID as a reference. I can ping probably send VBS tomorrow but it
really is a 10 minute job to write.
Robert
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of [email protected]
<mailto:[email protected]>
Sent: 23 September 2013 14:54
To: [email protected] <mailto:[email protected]> ; Daniel
Ratliff
Subject: RE: [mssms] Disabling IPv6 in a Task Sequence
nvspbind.exe ... bit of automation coding required, but doable.
"[email protected] <mailto:[email protected]> " <[email protected]
<mailto:[email protected]> > wrote:
I unbind v6 from all adapters using a cmd line tool when customers demand
disablement of it. I'll ping the tool name later. is far cleaner than trying to
unstitch from the OS something that is built-in.
Daniel Ratliff <[email protected] <mailto:[email protected]> > wrote:
By removing that adapter you forfeit any easy means of turning it back on one
day. I would recommend the DisabledComponents method as Jimmy mentioned, that
is the recommended method and disables it for all adapters.
Daniel Ratliff
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Stephen Murley
Sent: Sunday, September 22, 2013 5:50 AM
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Disabling IPv6 in a Task Sequence
We disable IPv6 on image deployment. Personally, I voted against doing this but
was outvoted as apparently our networking guys said our network wasn’t ready
for IPv6 …
I think we might do a Group Policy as well, and it was 2 years ago that we did
all this so I’d need to ask colleagues next week. As far as I know we disable
the TEREDO Adaptor which has the desired effect:
cmd.exe /c devcon\i386\devcon.exe REMOVE *TEREDO
I’ll check next week and ask. Certainly on our deplooyed computers users cannot
alter any IPv6 settings.
IFrom: [email protected] <mailto:[email protected]>
[mailto:[email protected]]
<mailto:[mailto:[email protected]]> On Behalf Of Jimmy Martin
Sent: 20 September 2013 21:20
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Disabling IPv6 in a Task Sequence
Search ipv6 fffffff
Sent from my Windows Phone
_____
From: Trevor Sullivan
Sent: 9/20/2013 3:09 PM
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Disabling IPv6 in a Task Sequence
Why are you disabling IPv6? Bad, bad idea.
Cheers,
Trevor Sullivan
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Scott Kenyon
Sent: Friday, September 20, 2013 1:28 PM
To: '[email protected]'
Subject: [mssms] Disabling IPv6 in a Task Sequence
Has anyone done this, if so could use some help on a script or something to
disable IPv6 during image deployments
Thanks
Scott Kenyon
Sr. Computer Specialist
Dean of Medicine Information Technology
UW School of Medicine
850 Republican Street, Box 358047
Seattle, WA 98109
Phone: 206.685.2825
ServiceDesk: 206.221-2459 | <mailto:[email protected]> [email protected]
[email protected] <mailto:[email protected]>
<http://www.uwmedicine.org/> uwmedicine.org
<http://uwmedicine.org/>
The above email may contain patient identifiable or confidential information.
Because email is not secure, please be aware of associated risks of email
transmission. If you are communicating with a UW Medicine Provider or
Researcher via email, your acceptance of the risk and agreement to the
conditions for email communications is implied. (See
http://www.uwmedicine.org/Global/Compliance/EmailRisk.htm.)
The information is intended for the individual named above. If you are not the
intended recipient, any disclosure, copying, distribution or use of the
contents of this information is prohibited. Please notify the sender by reply
email, and then destroy all copies of the message and any attachments. See our
Notice of Privacy Practices at http://uwmedicine.washington.edu.
This message and any files transmitted with it may contain legally privileged,
confidential, or proprietary information. If you are not the intended recipient
of this message, you are not permitted to use, copy, or forward it, in whole or
in part without the express consent of the sender. Please notify the sender of
the error by reply email, disregard the foregoing messages, and delete it
immediately.
P Please consider the environment before printing this email...
_____
<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the
use of the recipient to whom it is addressed. If you are not the intended
recipient then copying, distribution or other use of the information contained
is strictly prohibited and you should not rely on it. If you have received this
email in error please let the sender know immediately and delete it from your
system(s). Internet emails are not necessarily secure. While we take every
care, Plymouth University accepts no responsibility for viruses and it is your
responsibility to scan emails and their attachments. Plymouth University does
not accept responsibility for any changes made after it was sent. Nothing in
this email or its attachments constitutes an order for goods or services unless
accompanied by an official order form.
The information transmitted is intended only for the person or entity to which
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information
in error,
please contact the sender and delete or destroy the material/information.
<<image001.png>>
