Posts

Showing posts from June, 2014

Power Shell stuff

1.  Replacing characters in csv file using below sample code: $csv001 = import-csv "C:\Users\sumeet.kumar\Desktop\Services\Scripts\Power Shell Scripts\Sending reboot notification\Computers with last logged on user from collection Username0.csv" $csv001 | foreach-object { $_.username0 = $_.username0.replace("Domain\","") } $csv001 | export-csv  "C:\Users\sumeet.kumar\Desktop\Services\Scripts\Power Shell Scripts\Sending reboot notification\Computers with last logged on user from collection Username001.csv" -notype Reference: http://social.technet.microsoft.com/Forums/windowsserver/en-US/0ad9ad37-b99b-418a-b139-34752b0927dc/powershell-importcsv-then-replace-character-then-exportcsv 2.  Appending characters in csv file using below code: $csv003 = import-csv "C:\Users\sumeet.kumar\Desktop\Services\Scripts\Power Shell Scripts\Sending reboot notification\Computers with last logged on user from collection Username001.csv" $csv003 | fo...

'Failed to insert OSD binaries into the WIM file' when injecting network drivers into Boot Image SCCM 2012

Issue: Today when I was trying to PXE boot Lenovo T440s for the first time, image started failing at “Task Sequence Window comes” (TS window wasn’t appearing). Tried This… After this I assumed that can be a problem with the LAN drivers, immediately I started injecting boot image with Lenovo’s Latest LAN drivers BUT it failed with following below error. Error Message: “Failed to inject a ConfigMgr driver into the mounted WIM file” The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = “Failed to insert OSD binaries into the WIM file”; ErrorCode = 2152205056; File = “e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp”; Line = 4262; ObjectInfo = “CSspBootImagePackage: reRefreshPkgSrcHook”; Operation = “ExecMethod”; ParameterInfo = “SMS_BootImagePackage.PackageID=”S0100002″”; ProviderName = “WinMgmt”; StatusCode = 2147749889; }; Resolution: Tried following steps:   We ...