SCCM 2012 - Drivers

Hi,
I am using SCCM 2012 SP1 version, Some specific drivers are working only if I reimport.
Is there any specific reason or is it a bug. Any advice please
EX: I imported drivers for 6550B model almost a month before and it worked at that time. When I tried it today, no drivers got updated. It worked fine only after I reimport the drivers.
Regards, Pratap

Hi,
I dont think there is a problem with SCCM, there are many ways in managing drivers.
As part of the import process for the device driver, Configuration Manager reads the provider, class, version, signature, supported hardware, and supported platform information that is associated with the device. Once a driver has been imported and has the
same above listed infomration, Configuration Manager will not overwrite this as the information already exists in the driver catalog.
By default, the driver is named after the first hardware device that it supports; however, you can rename the device driver later. The supported platforms list is based on the information in the INF file of the driver. Because the accuracy of this information
can vary, manually verify that the device driver is supported after it is imported into the driver catalog.
I usually categorize them into two , the good and the bad.
Good drivers install using theier inf files \ pnp device id's. In a OSD Deployment task sequence this type of drivers are aplied by the AUTO APPLY Driver Tasksequence step.
When dealing with bad Drivers , you have two options:
Option 1 : Import the drivers and include them driver package, In a OSD Deployment task sequence this type of drivers are aplied by the APPLY Driver Package Tasksequence step.
Option 2: Refer to the vendors website, and create a software package to deploy the driver. Some Vendors have guides and detailed information on how to install these type of drivers and thier relevant applications silently.
Please refer to
http://technet.microsoft.com/en-us/library/hh301101.aspx for more information.
Further, deal with one driver at a time, every driver can be managed diffrently during the deployment process.

Similar Messages

SCCM 2012 R2 Boot WIM DISM - Drivers Failing -hr:0xc0000135‏

Hello OSD Experts,
I have upgraded my SCCM 2012 RTM to SP1(Not installed any Cumulative updates) then to SCCM 2012 R2 Successfully... I did not get any errors.
Before Upgrade my SCCM 2012 RTM/SP1 Images are removed from DP Targets.
Now my next high priority task is I wanted to integrate my Hardware models NIC & Mass Storage Drivers to my Boot Images, So that my OSD will work without any issues. But am getting errors, when I try
to add by DISM command to the Boot Images.
I have taken Default boot.wim file from SCCM 2012 R2 and copy pasted to my work location and ran the DISM command... however I am not successful in this for integration.
Has anyone have already have solution for this let me know.
<<<AV is in Disabled state during DISM.. Still no Luck>>>
<<<<<I tried to ran the DISM on Windows 8 & Windows 2008 R2>>>>>
Attached my DISM.Log @OneDrive... http://1drv.ms/1gdUi6w
Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
DISM Manager: PID=3200 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr:0xc0000135)
DISM.EXE: Unable to start the servicing process for the image at 'E:\Boot_WIM\SCCMR2_WIMS\X86\Temp'. HRESULT=C0000135
<<< I have already checked this link but no luck... http://social.technet.microsoft.com/Forums/en-US/6b9facc4-9174-4ae7-a8a0-98d88d7f8a95/dism-error-0xc0000135-when-attemptign-to-add-drivers-to-mounted-2012-image?forum=mdt
>>>
Thank you In Advance,
HunBoy Started learning from this page

Hi,
You could use SCCM console to add these drivers. From the SCCM console, go to Operating Systems -> Drivers. Right click and select Import Drivers and follow the wizard. Or go to Operating Systems -> Boot Images -> Right click the boot image in question
-> select Properties. Select the Drivers tab and click on the add button on the right and then select the NIC drivers.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Problems with E531 network drivers in SCCM 2012 R2

We are having some serious issues with SCCM 2012 R2 operating system deployment (Windows 7) and the Thinkpad Edge E531 laptop - network drivers are not being applied during the imaging process. Do SCCM driver packages exist for this laptop?
I downloaded the ethernet drivers manually from here, extracted the files from the executable, imported the drivers into SCCM (it found them), and created a driver package for this model. I also added the drivers to the boot images.
I do not have an issue during the PXE phase, it is only during the Windows phase - and the laptop is unable to join the domain because it does not have network drivers.
In the OSD Task Sequence, I have tried both the auto-apply device drivers rule (default), and creating a special rule for Lenovo E531 with the WMI query: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%6885YU%" . The task sequences all work perfectly on virtual machines, so I am fairly certain this is a driver issue. I have tried Windows 7 x86, x64, and Windows 8.1 x64.
Any thoughts are welcome - I am new to this particular school district and have never deployed Lenovo in my previous environments. I am about to select a model for this year's laptop purchases and at this point, I am backing away from Lenovo due to this issue.

We do not create SCCM driver packs for the Edge line of products. As an alternative you can use Update Retriever to download hardware drivers for a selected model and then use the Export feature to create a folder containing the source files for the drivers. This can then be used in the Driver Import Wizard which will locate the INF files and only import the files referenced by the INF files.
You mention you are using SCCM 2012 R2. This means you should be using the Windows ADK for 8.1 which also means your boot images should be using Windows PE 5. For your boot images you should be using the Windows 8.1 driver (http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/herr01ww.exe)
In your OSD task sequence you need to be deploying Windows 7 drivers (http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/her101ww.exe)
Make sure you keep these separate. Meaning you should have a driver package for the Windows 7 drivers that you reference in an Apply Drivers task and this package should not include the Windows 8.1 drivers. Add just the 8.1 drivers to the boot image.

Import Drivers Fail- SCCM 2012 R2

Hello,
I am having issues with importing drivers and adding them to a driver package. The error message that I am receiving is "The SMS Provider reported an error." Our environment has a single SCCM 2012 R2 for the site. I looked through the SmsAdminUI
log file and found this:
[8, PID:5444][09/02/2014 16:32:48] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:32:55] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_B9DDE7DF4661034EC956AC906BFFD363E845403FB0986F0FE59D21EA87042303) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_B9DDE7DF4661034EC956AC906BFFD363E845403FB0986F0FE59D21EA87042303";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:32:59] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:03] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:09] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:13] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:17] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:17] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters)
at Microsoft.ConfigurationManagement.AdminConsole.Driver.PackagesToDriversControl.UpdatePackage(PackageInfo packageInfo)\r\nConfigMgr Error Object:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\nSystem.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n

Hello,
I am having issues with importing drivers and adding them to a driver package. The error message that I am receiving is "The SMS Provider reported an error." Our environment has a single SCCM 2012 R2 for the site. I looked through the SmsAdminUI log
file and found this:
[8, PID:5444][09/02/2014 16:32:48] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC)
has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
the driver already exists in the catalog..
http://technet.microsoft.com/en-us/library/2240a538-f7c1-4118-8b7b-894950dd5c34#ImportingWondowsDeviceDrivers
did you "Specify the option for duplicate drivers: Select how you want Configuration Manager to manage driver categories when a duplicate device drive is imported." ??
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Updating drivers already imported into SCCM 2012

Hi
We imported drivers for all our models into sccm when we set it up.
Obviously there are now new versions of these drivers.
What's the best way to remove the old and add new drivers to sccm?
This is NOT a question about updating drivers on clients but in sccm it self.
Kindest regards, Martin

Hi,
Please refer to the link below:
SCCM OSD driver best practices
http://hayesjupe.wordpress.com/sccm-2012-osd-driver-good-practice/
ConfigMgr Driver Injector
This tool will allow you to capture installed drivers on your workstations and then will
automatically import them in ConfigMgr 2012.
http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

OSD: TS deployed to Vista SCCM 2012 client, reboots then doesn't find network drivers

Hi,
We deploy SCCM 2012 client to a SCCM 2007 Vista pc.
We then deploy a task sequence to install Windows 7.
Everything works fine on a vm, it reboots in winpe then starts the task sequence. On a laptop however, it does not work. F8 shows it does not get an ip address, it seems as if no network adaptor is recognized.
However, the same task sequence works fine on the same laptop when pxe booting + I added the driver to winpe. Didn’t help. Please advise.
J.
Jan Hoedt

I think I know what the root cause is, but not how to solve it.
In diskpart, I can see 3 volumes:
*Volume 0 = D-drive, DVD-rom,
*Volume 1 = no drive letter, partition of 400 GB
*Volume 2 = C-drive, label "Configuratio", type "removable" 4 GB
It should install to the 400 GB drive but it seems that its installing to the removable drive.
Not sure what that is since there is no USB attached. Probably it is the winpe temporarely mounted(?)
The behaviour I have is described
here and is also referring to USB.
=> I guess I have to tell the temporarely mounted drive to be f.e. Z when installing in full OS.
Any idea howto do this?
J.
Jan Hoedt

SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip

we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
Find below the smsts.log file
Main error in the log file is
No physical network adapters found   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151.   TSMBootstrap   2/12/2014 1:05:41 PM   1984 (0x07C0)
Xtract from LOG
SMSTSRebootDelay=60   Reboot   2/12/2014 1:01:56 AM   3496 (0x0DA8)
SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue.   Reboot   2/12/2014 1:01:56 AM   3496 (0x0DA8)
SMSTSRebootRequested=WinPE   Reboot   2/12/2014 1:01:56 AM   3496 (0x0DA8)
Process completed with exit code 0   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
!--------------------------------------------------------------------------------------------!   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
Set authenticator in transport   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
Set a global environment variable _SMSTSLastActionRetCode=0   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a global environment variable _SMSTSLastActionSucceeded=true   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Clear local default environment   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Updated security on object E:\_SMSTaskSequence.   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Save the current environment block   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Executing command line: "bcdedit.exe"   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
CreateProcess failed. Code(0x80070002)   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Command line execution failed (80070002)   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Staging boot image UNB0003A   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
ResolveSource flags: 0x00000000   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
SMSTSPersistContent: . The content for package UNB0003A will be persisted   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
Set authenticator in transport   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
WinHttp credentials set   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
List of files to be downloaded   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim    TSManager   2/12/2014 1:02:22 AM   1876
(0x0754)
VerifyContentHash: Hash algorithm is 32780   TSManager   2/12/2014 1:02:22 AM   1876 (0x0754)
Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim   TSManager   2/12/2014 1:02:25 AM   1876 (0x0754)
Copying boot image locally...   TSManager   2/12/2014 1:02:25 AM   1876 (0x0754)
Failed to find ADK installation root registry key   TSManager   2/12/2014 1:02:32 AM   1876 (0x0754)
Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim   TSManager   2/12/2014 1:02:32 AM   1876 (0x0754)
Applying image 1 to volume E:\_SMSTaskSequence\WinPE   TSManager   2/12/2014 1:02:32 AM   1876 (0x0754)
Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
Capturing WinPE bootstrap settings   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
==============================[ OSDNetSettings.exe ]===========================   OSDNetSettings   2/12/2014 1:02:36 AM   2064 (0x0810)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   OSDNetSettings   2/12/2014 1:02:36 AM   2064 (0x0810)
No adapters found with non-empty DNSDomainSuffixSearchOrder   OSDNetSettings   2/12/2014 1:02:36 AM   2064 (0x0810)
Adapter "ROOT\SYMC_TEEFER2MP\0000" not found   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
No physical network adapters found   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
OSDNetSettings finished: 0x00000000   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
Process completed with exit code 0   TSManager   2/12/2014 1:02:38 AM   1876 (0x0754)
Installing boot image to hard drive   TSManager   2/12/2014 1:02:38 AM   1876 (0x0754)
Backing up existing boot system before trying to set up new boot system   TSManager   2/12/2014 1:02:38 AM   1876 (0x0754)
BootLoader::backup: C:\, E:\_SMSTaskSequence\backup   TSManager   2/12/2014 1:02:39 AM   1876 (0x0754)
BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\   TSManager   2/12/2014 1:02:43 AM   1876 (0x0754)
Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD   TSManager   2/12/2014 1:02:43 AM   1876 (0x0754)
Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR   TSManager   2/12/2014 1:02:45 AM   1876 (0x0754)
Process completed with exit code 0   TSManager   2/12/2014 1:02:46 AM   1876 (0x0754)
Updated security on object E:\_SMSTaskSequence.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Save the current environment block   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object E:\_SMSTaskSequence.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Save the current environment block   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Expand a string: %_SMSTSMDataPath%\Logs   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
<![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">
   1/1/1601 12:00:00 AM   1995266923 (0x76ED5B6B)
==============================[ TSBootShell.exe ]==============================   TSBootShell   2/12/2014 1:04:01 AM   784 (0x0310)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'   TSBootShell   2/12/2014 1:04:01 AM   784 (0x0310)
Debug shell is enabled   TSBootShell   2/12/2014 1:04:01 AM   784 (0x0310)
Waiting for PNP initialization...   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Booted from fixed disk   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Found config path E:\_SMSTaskSequence   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Restoring boot system from E:\_SMSTaskSequence\backup   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Successfully loaded the BCD boot system   TSBootShell   2/12/2014 1:04:05 AM   796 (0x031C)
Successfully loaded an exported NTLDR boot system   TSBootShell   2/12/2014 1:04:05 AM   796 (0x031C)
BootLoader::restore: E:\_SMSTaskSequence\backup, C:\   TSBootShell   2/12/2014 1:04:05 AM   796 (0x031C)
Successfully merged logs from cache.   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Loading bootstrap settings from E:\_SMSTaskSequence\WinPE   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Loading saved WinPE settings   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00'   TSBootShell
2/12/2014 1:04:06 AM   796 (0x031C)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Configuring WinPE bootstrap settings   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Creating WinPE answer file   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Setting hive location to "X:\windows\system32"   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Getting namespace "Microsoft-Windows-Setup" for architecture "x86"   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Configuring global network settings   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Join type:    TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
DNS domain: exch1.mas.unb.com   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
DNS domain search order:    TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
IP filter sec enabled: false   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
No adapters found in environment. Performing global configuration only.   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Executing command line: wpeinit.exe -winpe   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
The command completed successfully.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Starting DNS client service.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Finalizing network settings   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
No adapters found in environment. Performing global finalization only.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Finalizing global network settings   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
DNS domain: exch1.mas.unb.com   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
DNS domain search order:    TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
DNS for WINS enabled: false   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
LMHosts file enabled: true   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Host lookup file:    TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
WINS scope ID:    TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
The command completed successfully.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
==============================[ TSMBootStrap.exe ]==============================   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL'   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Failed to open PXE registry key. Not a PXE boot.   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Resuming Task Sequence in WinPE   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'   TSMBootstrap
2/12/2014 1:05:40 AM   1984 (0x07C0)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'   TSMBootstrap
2/12/2014 1:05:40 AM   1984 (0x07C0)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat".   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Updating the local data path in the Task Sequencing Environment.   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogMaxSize to 1000000   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogMaxHistory to 1   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogLevel to 0   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogEnabled to 1   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogDebug to 1   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Command line for extension .exe is "%1" %*   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
==========[ TsProgressUI started in process 2004 ]==========   TsProgressUI   2/12/2014 1:05:41 AM   2008 (0x07D8)
Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
In dire need of help,
I have already gone through the below articles on the NET
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
Awating response,
Hasan Reza

Well Finally I sorted my issue ,
Just want to share the solution, may be it would be helpful to some one else and save some times
The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
Thanks,
Hasan Reza.
http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen

SCCM 2012 - Adding Operating System Installer (The specified path does not contain a valid operating system ..)

I have encountered the dreaded "The specified path does not contain a valid operating system or you do not have permission to access it. Specify a valid path" message that seems to be popular in many forums .... BUT, so far none of the "solutions"
have fixed the problem (of I don't understand the fix)
Configuration
SCCM 2012 SP1 5.0.7804.1000
WADK 8.100.26629.0 < Suggested Fix
Server 2008 R2
SCCM Administrator with UserID = SCCMAdmin
Steps / Fixes I have followed
I have configured a administrative share
\\caleb\sources$ to hold directories (such as Apps, Drivers, and OS) with the following NTFS Permissions
EVERYONE has Read and Execute, List folder, Read permissions<o:p></o:p>
SYSTEM has Full Control
<Suggested Fix
SCCMManagers (our group that has all SCCMManagers) has Full Control<o:p></o:p>
SCCMAdmin (the SCCM Admin account that we are using to import image) has Full Control<o:p></o:p>
Local Administrators (the local machine administrator) has Full Control
<Suggested Fix
<o:p></o:p>
Another Fix is to explicitly grant all permissions to the SCCM Administrator
<Suggested Fix
>Administrative Users ...
Properties of the SCCM Administrator (for us that is SCCMAdmin) has all the boxes checked<o:p></o:p>
Another suggestion I was able to glean was to Specify the Network Access Account
so I configured SCCMAdmin as the Network Access Account.
Another potential fix is that the image ISO file that has been downloaded is corrupt.   So, I downloaded the Win 7 (and Win 8.1) ISO's from MSDN and did a Checksum check.
I then mounted the ISO (on 2008R2 I use VirtualClone Drive) and copied the contents of the image to
E:\Sources\OS\en_windows_7_professional_with_sp1_vl_build_x86_dvd_u_677896 for Windows 7 with SP1
To double check,
I computed the Hash on the Install.WIM located in the Sources directory and compared with
the computed Has Tag for the Install.WIM on the ISO Image ... and the Hash tag of the WIM's matched (extracted vs what is contained within the ISO)<o:p></o:p>
I tried to load the images into SCCM 2012 using the "Operating System Installers" option
UNC to installer
\\caleb\sources$\OS\en_windows_7_professional_with_sp1_vl_build_x86_dvd_u_677896
Then I receive the lovely message <o:p></o:p>
"The specified path does not contain a valid operating system or you do not have permission to access it. Specify a valid path"<o:p></o:p>
<o:p> </o:p>
From
C:\Program Files (x86)\Microsoft Configuration
Manager\AdminConsole\AdminUILog\SmsAdminUI.log<o:p></o:p>
<o:p> </o:p>
\r\nSystem.Management.ManagementException\r\nGeneric failure \r\n
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
errorCode)
   at System.Management.ManagementObject.InvokeMethod(String
methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
   at
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String
methodClass, String methodName, Dictionary`2 methodParameters, Boolean
traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "Failed to get the image property from the source WIM
file due to error 80070002";
ErrorCode = 2147942402;
File ="e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspimagepackage.cpp";
Line = 586;
Operation = "ExecMethod";
ParameterInfo = "SMS_OperatingSystemInstallPackage";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n<o:p></o:p>
What am I missing ???? I assume something simple but, darn I'm stumped!!!

Hi,
Configuration Manager version
Windows AIK or Windows ADK Version
Windows PE versions for boot images customizable from the Configuration Manager console
Supported Windows PE versions for boot images not customizable from the Configuration Manager console
System Center 2012 Configuration Manager with no service pack
Windows AIK for Windows 7
Windows PE 3
None
System Center 2012 Configuration Manager with SP1
Windows ADK for Windows 8
Windows PE 4
None
System Center 2012 Configuration Manager with SP1 and cumulative update 2
Windows ADK for Windows 8
Windows PE 4
Windows PE 3.11
System Center 2012 Configuration Manager with SP1 and cumulative update 3
Windows ADK for Windows 8
Windows PE 4
Windows PE 3.11 and Windows PE 5
System Center 2012 R2 Configuration Manager
Windows ADK for Windows 8.1
Windows PE 5
Windows PE 3.11
Please try to install the Windows ADK for Windows 8.
http://www.microsoft.com/en-us/download/details.aspx?id=30652
For more information, please review the link below:
http://technet.microsoft.com/en-us/library/gg682187.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Patches missing in SCCM 2012

Hi,
We are using SCCM 2012 SP1 to deploy are pathes. Now we want to install kb2797052 but it is not in our Updates Repository in SCCM. When I check our WSUS server, it is in there. I've read a few threads about this issue telling to reinstall the SUP and
that this sometimes solves the problem but...
We have the problem in all of our 4 environments. Also other patches are missing like kb2553091...
All Classifications have been selected (though I see in WSUS drivers are not selected, in SCCM this classification does not exist).
For the products, we did not select everything, but all Windows OS products and Office are selected.
I could also see that in SCCM we have selected English and French, but in WSUS "download updates in all languages" is selected, even though WSUS was configured by SCCM at the time of installation.
Could it be that the language metadata is missing on certain patches and therefore not showing in SCCM? Can the language of a patch be checked in WSUS?
WiM

Hi,
I found this in my Wsyncmgr.log after Isync all the updates. KB2797052 has been superseded.
Skipped update e8b7a0b5-1350-414a-82ca-74b3a11d756b - Security Update for Microsoft Office 2010 (KB2553091), 64-Bit Edition because it was superseded
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Want to test OSD in Vmware Workstation SCCm 2012

Which Drivers needed and where to get VMware scsi controller drivers ,I got .flp file but don't know how to extract that
can any one provide link from where I can get Drivers needed for OSD in VMware workstation with SCCM 2012 for windows 7.

Narcoticoo is on the right track. VMWare have a process for this.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032184
You could use HyperV or Oracle VirtualBox - absolutely no drivers required to develop your solution..
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson
VMware has process of it's own, but my method works on every situation if you want to grab drivers from the installed OS.

Driver folders in sccm 2012. are they any use?

Hi I was wondering if any one can give me there thoughts on whether to use sccm 2012 driver folders
(not driver packages folders) and if so how.
In sccm 2007 I could see a purpose because you could create your "os/architecture/manufacturer/model/type of driver" folder structure using search folders and add driver categories to these search folder so you could manage the drivers before adding
them to the package.
In sccm 2012 you don't have search folders as such and in most cases the drivers belong to more than one driver model category so moving them into a specific model folder does not make sense.
As such I cannot see how to use the driver folder except for breaking the drivers up into there type e.g. network, graphics, usb etc.
Most article I have read only mentioned driver package folders
Your thoughts are most appreciated.
Cheers
Greg Turnbull

We initially started breaking down all drivers by model and OS. This worked at first, but after the first year or so we started having issues finding drivers in the drivers node because some drivers were applicable to multiple models as well as multiple
OS.
For instance, Intel HD graphics for the Lenovo Yoga is also used on the L440 and T540p. It also applies to Win7x64 and Win8x64, so which folder would this driver go into?
We ended up just moving everything into the root of the node and doing a search.
One item to note, if you leave everything in the root, it can take a long time to load and search, especially if you add the Supported Platforms column.
Daniel Ratliff | http://www.PotentEngineer.com

SCCM 2012 SP1 Boot Image

Hi Guys,
We upgraded to SCCM 2012 SP1 from the RTM yesterday and now our OS Deployment has stopped working. I have tried to update the DP's with the boot images and it keep failing to add drivers. I have also tried to add a Boot Image but this failing.
Any suggestion on what might be going wrong? Our upgrade processed completed successfully.
Kind Regards
TPark IT Technician

Hi,
I have removed all the drivers and I am now getting the following error.
Error: Boot image to update:
Microsoft Windows PE (x86)
　Error: Actions to perform:
Add ConfigMgr binaries
Add custom background
Enable Windows PE command line support
Optional components:
Scripting (WinPE-Scripting)
Startup (WinPE-SecureStartup)
Network (WinPE-WDS-Tools)
Scripting (WinPE-WMI)
　Error: The wizard detected the following problems when updating the boot image.
The SMS 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:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4630;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"ASH00001\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
I am only trying to Deploy Windows 7 images currently but we are looking to upgrade to Windows 8 at Christmas. Can I import a boot image from a Windows 7 or Windows 8 cd?

SCCM 2012 r2 with CU1 - XP Refresh

Hi Everyone,
Hoping someone out there can assist with this. I am doing a refresh for XP to win7. I have read
http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
and
http://www.windows-noob.com/forums/index.php?/topic/9418-referesh-task-sequence-from-xp-fails-on-sccm-2012-r2/
none of these work. I took a look at this and I was able to get pass the staging of the boot image
http://blogs.technet.com/b/brandonlinton/archive/2013/06/21/how-to-create-and-import-a-winpe-3-1-boot-image-for-use-in-configmgr-2012-sp1-cu2.aspx
however when the machine rebooted I received this. I also inject the nic drivers using dism and still the same issue. Any idea of a fix or how to go about refresh for
XP using sccm 2012 r2?
thanks all!

Hi,
Also ran into this issue, you're encountering this error because some components are missing in your WinPE image.
Note that this refresh scenario is not supported, however you can get this to work by manually customizing (especially importing WMI component) your WinPE image
before importing it ConfigMgr.
I made the script below, ran in on a base WinPE image from WADK for Windows 8 (a 6.2 version image so) to make it work (sorry for french comments Inside but I'm sure you'll get it :) ):
#Adapt these variables to you environment
$ADK = "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit" #Chemin d'ADK
$DismArchitecture = "amd64" #archi a utiliser pour DISM
$CompArchitecture = "x86" #archi a utiliser pour les composants
$MountDir = "e:\Mount" #point de montage a utiliser
$Wimdir = "E:\winpe.wim" #chemin du wim a modifier
$InjectDrivers = $TRUE #Choisir si il faut ajouter des pilotes ou non
$DriversDir = "E:\Pilotes\WinPE3.1_x86" #chemin contenant les pilotes
$AddCMTrace = $FALSE #Choisir si il faut ajouter cmtrace ou non
$CMTraceDir = "E:\Microsoft Configuration Manager\tools\cmtrace.exe" #chemin de cmtrace
$ChangeLocale = $TRUE #Choisir si il faut modifier les paramètre regionnaux ou non
$Locale = "fr-FR" #param regionnaux a utiliser
$DismFolder = "$ADK\Deployment Tools\$DismArchitecture\DISM" #ne pas modifier
$OptComponents = "$ADK\Windows Preinstallation Environment\$CompArchitecture\WinPE_OCs"; #ne pas modifier
$AddOPTComponents = $TRUE #Choisir si il faut ajouter des composants ou non
#liste des composants:
$ComponentList = @(
“$OptComponents\WinPE-WMI.cab”
“$OptComponents\$Locale\WinPE-WMI_$Locale.cab”
“$OptComponents\en-us\WinPE-WMI_en-us.cab”
“$OptComponents\WinPE-NetFx4.cab”
“$OptComponents\$Locale\WinPE-NetFx4_$Locale.cab”
“$OptComponents\en-us\WinPE-NetFx4_en-us.cab”
“$OptComponents\WinPE-HTA.cab”
“$OptComponents\$Locale\WinPE-HTA_$Locale.cab”
“$OptComponents\en-us\WinPE-HTA_en-us.cab”
“$OptComponents\WinPE-DismCmdlets.cab”
“$OptComponents\$Locale\WinPE-DismCmdlets_$Locale.cab”
“$OptComponents\en-us\WinPE-DismCmdlets_en-us.cab” );
#Composants pour WinPE 6.3: (a inserer a la place de NetFx4)
#“$OptComponents\WinPE-NetFx.cab”
#“$OptComponents\$Locale\WinPE-NetFx_$Locale.cab”
#“$OptComponents\en-us\WinPE-NetFx_en-us.cab”
#“$OptComponents\WinPE-PowerShell.cab”
#“$OptComponents\$Locale\WinPE-PowerShell_$Locale.cab”
#-----debut du script
#Creation du point de montage
New-Item -ItemType Directory -Force -Path $MountDir
#import de DISM
import-module $DismFolder
#montage de l'image
Write-Host "Mounting WIM file"
Mount-WindowsImage -ImagePath $Wimdir -Index 1 -Path $MountDir -ErrorAction Stop
#changement de locale
if($ChangeLocale -eq $TRUE)
Write-Host "Changing locale"
cd $DismFolder
dism.exe /image:$MountDir /set-syslocale:$Locale
dism.exe /image:$MountDir /set-userlocale:$Locale
dism.exe /image:$MountDir /set-inputlocale:$Locale
#ajout de cmtrace
if($AddCMTrace -eq $TRUE)
Write-Host "Adding CMTrace"
$CMTraceDest = $MountDir + "\Windows\System32"
Copy-Item -Path $CMTraceDir -Destination $CMTraceDest
#ajout des pilotes
if($InjectDrivers -eq $TRUE)
Write-Host "Injecting Drivers"
Add-WindowsDriver -Recurse -ForceUnsigned -Driver $DriversDir -Path $MountDir -Verbose -ErrorAction SilentlyContinue
#ajout des composants
if($AddOPTComponents -eq $TRUE)
Write-Host "Adding Optionnal Components"
foreach ($Component in $ComponentList)
Write-Host -Object (’Installing component: {0}’ -f $Component);
Add-WindowsPackage -Path $MountDir -PackagePath $Component -ErrorAction SilentlyContinue;
#demontage de l'image
Write-Host "Unmounting WIM file"
Dismount-WindowsImage -Path $MountDir -Save -Verbose
Mickael, My technet galleries contributions : ConfigMgr driver injector : http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d SCCM Collection splitter : http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06 ConfigMgr
TS Tools : http://gallery.technet.microsoft.com/TSTools-f9b01357

SCCM 2012 OSD; Not finding driver package during deployment

I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction. Specifically I am having trouble with device driver deployment while deploying my reference image.
I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image. I am not sure if it matters, but I manually built a reference
PC and using capture media (USB stick), I successfully captured my reference image. I have imported my drivers for the target PC into Config Manager and into a driver package. The driver package has been deployed to the distribution point
(DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim. Within the TS, I added an "Apply
Driver Package" step and pointed it to the aforementioned driver package. I added a WMI query to the step as follows
select * from Win32_ComputerSystem where Model like "HP Probook 6570b%."
Incidentally, I did a wmi query on the target PC to verify the model. I deployed the TS to the unknown computers collection and PXE booted the target PC. I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found." I checked the smsts.log log and found the following:
Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
for deployment. After more research I have done the following:
Deleted the Driver Package and recreated it and updated the TS step to point to this package.
Deleted and recreated the TS along with the driver package.
Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
When distributing content I verified it was successfully completed each time as per the console.
Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error. If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
Thanks in advance,
Mike G.

Thanks for responding.
Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points. I checked now (about 12 hours later) and the package is showing it has not finished updating. I checked the content status and
it is "waiting for content." I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1". This error would occur every 30 min after each time the DP retried to process
the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
it retried, the error cleared, however the package status is still waiting for content. I tried doing a validation on the package but so far there has been no change.

SCCM 2012: OSD to VHDX, deploy VHDX bare metal via TS?

Hi,
I wonder what your point of view is on the following scenario:
1.Deploy ts to vhdx
2.Deploy this vhdx to pc (bare metal) via another ts, this ts would then:
-wipe the disk
-make bootpartition
-add vdisk via bcdboot
It would give a lot of flexibility in terms of deployment speed (only 1 file to deploy, not that many reboots)backup (mount vhd to recover data),adding extra os, running clients vhd on hyperv host ...
Only issue would be how to add machine specific drivers.
Please advise.
J.
Jan Hoedt

Hello,
Only issue would be how to add machine specific drivers.
The answer is to this question. And in order to deploy VHD, you can follow this blog:
SCCM 2012 R2 – Create Virtual Hard Disk (VHD)

SCCM 2012 - Drivers

Similar Messages

Maybe you are looking for