I've been testing setting the value to 0x20 (32 in decimal) which has resolved 
all the IPv6 problems I was experiencing.

0x20 = prefer IPv4.

I am anticipating bringing online a Direct Access service someday, and I know 
that that won't work if IPv6 is entirely disabled.
I am still testing this setting, but you might look into setting it to 0x20 
rather than 0xffffffff  For me, where our net switches drop all IPv6 traffic, 
0x20 has been good enough.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Scott Kenyon
Sent: Monday, September 23, 2013 11:52 AM
To: '[email protected]'
Subject: [mssms] RE: Disabling IPv6 in a Task Sequence

Thanks Mark....

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 | [email protected]<mailto:[email protected]>
[email protected]<mailto:[email protected]>
uwmedicine.org<http://www.uwmedicine.org/>
[Visit UW Medicine on.line]<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.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Friday, September 20, 2013 12:03 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Disabling IPv6 in a Task Sequence

After "Setup Windows and Configmr"

Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Scott Kenyon
Sent: Friday, September 20, 2013 2:52 PM
To: '[email protected]'
Subject: [mssms] RE: Disabling IPv6 in a Task Sequence

I've used that command, but it had not effect. Were in the task sequence do you 
insert this command? I could have it in the wrong location.

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 | [email protected]<mailto:[email protected]>
[email protected]<mailto:[email protected]>
uwmedicine.org<http://www.uwmedicine.org/>
[Visit UW Medicine on.line]<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.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Friday, September 20, 2013 11:31 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Disabling IPv6 in a Task Sequence

Do a Run Command Line task and use the following:
REG ADD HKLM\System\CurrentControlSet\services\TCPIP6\Parameters /v 
DisabledComponents /t REG_DWORD /d 4294967295


Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Scott Kenyon
Sent: Friday, September 20, 2013 2: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 | [email protected]<mailto:[email protected]>
[email protected]<mailto:[email protected]>
uwmedicine.org<http://www.uwmedicine.org/>
[Visit UW Medicine on.line]<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.








________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________



<<inline: image001.gif>>

Reply via email to