{"id":1399,"date":"2014-02-11T15:18:43","date_gmt":"2014-02-11T14:18:43","guid":{"rendered":"http:\/\/sccmfaq.wordpress.com\/?p=1399"},"modified":"2014-02-11T15:18:43","modified_gmt":"2014-02-11T14:18:43","slug":"sccm-2012-r2-osd-error-0x87d00267","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=1399","title":{"rendered":"SCCM 2012 R2 – OSD Error 0x87d00267"},"content":{"rendered":"

Hi, here’s Martin again.
\nWell, as written in a recent Blog Post (http:\/\/blog.hosebei.ch\/2013\/11\/21\/sccm-2012-install-windows-7-on-ssd-fails-with-error-0x87d00267\/), I was thinking of, that the Problem should be resolved, but we had still the same issues.
\nCause of we had nailed down the Problem to the Network, someone came up with the idea to set the Network Speed of the NIC instead of using auto configuration.
\nWhen searching for the method to set the Network Card to 100Mbit Full Duplex this by command line we ended up on this excellent blog on TechNet:
\nhttp:\/\/blogs.technet.com\/b\/networking\/archive\/2009\/01\/08\/configuring-advanced-network-card-settings-in-windows-server-2008-server-core.aspx
\nSo we wanted to set this Key (“*SpeedDuplex”) while on OSD to 4, as it means that the Network Card will set up the Network Connection with 100Mbit\/s FullDuplex. The Import of Registry Keys might not be a good Option, because the IDs can Change, as far as I know. So I wrote a small powershell script to Change the value, you can download it here:
\n[office src=”https:\/\/skydrive.live.com\/embed?cid=65440BAA507106AD&resid=65440BAA507106AD%21732&authkey=AFTgTDaIgttuqf0″ width=”98″ height=”120″]
\nand you will find the code also here:
\n# Description: This script set the NIC speed from automatic to 100 Full Duplex
\n# Usage: powershell.exe -executionpolicy bypass -file \"Set_NIC_Speed.ps1 -NicSpeed Auto\/100MB\"
\n# Author: Martin W\u00fcthrich, itnetx gmbh
\n#
\n#Exit Codes:
\n#1: No startup parameters defined
\n#2: Wrong startup parameter. Only Auto and 100MB allowed<\/p>\n

#-----------------------------
\n#Check Input Param
\n#-----------------------------
\nParam($NicSpeed)
\nIf($NicSpeed) {}
\nElse {
\n Write-Host \"You have to define the new NIC-Speed with a startup parameter Auto or 100MB.\"
\n exit 1
\n}<\/p>\n

#Set NIC Speed Value
\nIf($NicSpeed -eq \"100MB\") {
\n $NICSpeedValue = 4
\n $NICSpeedValueOld = 0
\n }
\nElseIf($NicSpeed -eq \"Auto\") {
\n $NICSpeedValue = 0
\n $NICSpeedValueOld = 4
\n }
\nElse {
\n Write-Host \"Wrong parameter omitted! Auto or 100MB are available values.\"
\n Exit 2
\n }<\/p>\n

$GetNICKey = Get-Item -Path HKLM:SYSTEMCurrentControlSetControlClass\"{4d36e972-e325-11ce-bfc1-08002be10318}\"<\/p>\n

ForEach($SubKey in $GetNICKey.GetSubKeyNames()){
\n If($SubKey -eq \"Properties\"){
\n #Do nothing, because no access to this key
\n }
\n Else {
\n $Nic = Get-Item -Path ($GetNICKey.PSPath + \"\" + $SubKey)
\n If ($Nic.GetValue(\"*SpeedDuplex\") -eq $NICSpeedValueOld) {
\n #Write-Host $Nic.Name
\n Set-ItemProperty -Path $Nic.PSPath -Name \"*SpeedDuplex\" -Value $NICSpeedValue<\/p>\n

}
\n }
\n }<\/code>
\nWe are still seeking for the issue of this Problem, and we use this script as a Workaround. But as so far, we can stage now our Computers with SSD again.<\/p>\n

If you ask yourself, why I didn’t use a VBScript, just because VBS will be more and more unusable for Scripting. Change now to powershell, or learn “Would you like to get fries to that” \ud83d\ude09
\nHope this helps.<\/p>\n","protected":false},"excerpt":{"rendered":"

Hi, here’s Martin again. Well, as written in a recent Blog Post (http:\/\/blog.hosebei.ch\/2013\/11\/21\/sccm-2012-install-windows-7-on-ssd-fails-with-error-0x87d00267\/), I was thinking of, that the Problem should be resolved, but we had still the same issues. Cause of we had nailed down the Problem to the Network, someone came up with the idea to set the Network Speed of the NIC […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[],"class_list":["post-1399","post","type-post","status-publish","format-standard","hentry","category-operating-system-deployment"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1399","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1399"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1399\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1399"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1399"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1399"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}