Equebal Ahmad Blog

Recently we had an issue with a site where OSD was taking long time on random basis. When I was trying to gather more information about similar issues I come across below article. This article very well describe IP6To4 tunnel adapter and it’s impact in network / AD environment. http://blogs.technet.com/b/askpfeplat/archive/2013/11/18/ipv6-for-the-windows-administrator-the-2002-6to4-tunnel-address-and-its-impact.aspx The OSD was extremely slow on random basis. Even few MBs file were taking hours to download. As described in above article, the public IP address was being used in this site as well. The IP 6to4 tunnel adapter was also enabled on SCCM server and client workstations. Once we disabled the IP 6to4 tunnel adapter on SCCM server the build started working fine. We have also disabled this adapter on all workstations via GPO as it may also impact network performance.  It’s over a month now and issue has not been reported back. 

Do you have a batch file which you want to run on multiple remote machines? The below powershell script can simplify this task. I have used this script to remotely repair SCCM client on multiple machines by executing batch files. The steps are quite simple Copy the below code to powershell script file. Provide list of machines in computers.txt file in same folder where you kept the script. Copy your batch file ‘MyFile.bat’  in same folder. Run the script.     Code: #Get current path $invocation = (Get-Variable MyInvocation).Value $directorypath = Split-Path $invocation.MyCommand.Path $Inputfile = $directorypath + "\computers.txt" $BatchFile = "c:\windows\temp\MyFile.bat" $source = $directorypath + "\Myfile.bat"   Get-Content $inputfile | ForEach-Object {     $computer = $_     $TargetPath = "\\$computer\admin$\temp\"     Write-Host  "==============================="       #Copy s...