Jump to content


ingram59

Task sequence error BUT I AM getting an IP Address

Recommended Posts

Which one should I be looking at? There are a lot of them. Also, I was going to add a prestart command to the boot image, based on a couple KB articles that I read. When I updated the distribution point I got the following error. Ironically enough, the drive that I need is the one that is not injecting. However, if that was the problem to begin with, how would I be able to get an IP address as mentioned above? We ha a MS consultant on site a couple weeks ago and he built the image for us.

 

Also, according to the Drivers tab in the Boot image in question, the Realtek PCI GBE Family Controller IS Signed.

 

Error: Boot image to update:
Microsoft Windows PE (x64)
Error: Actions to perform:
Add ConfigMgr binaries
Set scratch space
Enable Windows PE command line support
Add drivers
Success: Boot image will include these drivers after update:
Broadcom NetLink Gigabit Ethernet
Intel® 82579LM Gigabit Network Connection
Intel® Ethernet Connection I217-LM
Intel® 82580 Gigabit Network Connection
Intel® 82579LM Gigabit Network Connection
Intel® Ethernet Connection I217-LM
Intel® 82580 Gigabit Network Connection
Broadcom NetLink Gigabit Ethernet
Intel® Ethernet Connection I217-LM
Optional components:
Scripting (WinPE-Scripting)
Startup (WinPE-SecureStartup)
Network (WinPE-WDS-Tools)
Scripting (WinPE-WMI)
Error: Failed to import the following drivers:
Realtek PCI GBE Family Controller - Failed to inject a ConfigMgr driver into the mounted WIM file
Error: The wizard detected the following problems when updating the boot image.
Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)";
ErrorCode = 2152205056;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4970;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"KHE00005\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
};

Share this post


Link to post
Share on other sites

SMSTS log file contents are listed below. I hilighted the lines in red that were errors in the log file. The Blue lines are the warnings.


Dino



LOGGING: Finalize process ID set to 944 TSBootShell 6/22/2016 4:54:12 PM 948 (0x03B4)

==============================[ TSBootShell.exe ]============================== TSBootShell 6/22/2016 4:54:12 PM 948 (0x03B4)

Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 6/22/2016 4:54:12 PM 948 (0x03B4)

Debug shell is enabled TSBootShell 6/22/2016 4:54:12 PM 948 (0x03B4)

Waiting for PNP initialization... TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

WinPE boot path: C:\SOURCES\BOOT.WIM TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

Booted from removable device TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

Found config path C:\ TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

Booting from removable media, not restoring bootloaders on hard drive TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

C:\WinPE does not exist. TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

C:\_SmsTsWinPE\WinPE does not exist. TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

Executing command line: wpeinit.exe -winpe TSBootShell 6/22/2016 4:54:12 PM 972 (0x03CC)

The command completed successfully. TSBootShell 6/22/2016 4:54:15 PM 972 (0x03CC)

Starting DNS client service. TSBootShell 6/22/2016 4:54:15 PM 972 (0x03CC)

Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\ TSBootShell 6/22/2016 4:54:16 PM 972 (0x03CC)

The command completed successfully. TSBootShell 6/22/2016 4:54:16 PM 972 (0x03CC)

==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 6/22/2016 4:54:16 PM 1180 (0x049C)

Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\ TSMBootstrap 6/22/2016 4:54:16 PM 1180 (0x049C)

Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 6/22/2016 4:54:16 PM 1180 (0x049C)

Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 6/22/2016 4:54:16 PM 1180 (0x049C)

Current OS version is 10.0.10586.0 TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Failed to open PXE registry key. Not a PXE boot. TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Media Root = C:\ TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

WinPE boot type: 'Ramdisk:SourceIdentified' TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Failed to find the source drive where WinPE was booted from TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Executing from Media in WinPE TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Verifying Media Layout. TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

MediaType = BootMedia TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

PasswordRequired = false TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

dwResult == 0L, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,499) TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Failed to find a valid network adapter. Please ensure that this machine has a network adapter and appropiate network drivers.

Unspecified error (Error: 80004005; Source: Windows) TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

Failed to find a valid network adapter.

For more information, contact your system administrator or helpdesk operator. TSMBootstrap 6/22/2016 4:54:17 PM 1180 (0x049C)

0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2645) TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1070) TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1254) TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

Exiting with return code 0x80004005 TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493) TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335) TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,561) TSMBootstrap 6/22/2016 4:54:18 PM 1180 (0x049C)

Execution complete. TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493) TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335) TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,561) TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,878) TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

End program: TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

Finalizing logging from process 944 TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

Finalizing logs to root of first available drive TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

Successfully finalized logs to D:\SMSTSLog TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

Cleaning up task sequencing logging configuration. TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

TS::Environment::SharedEnvironment.isInitialized() == true, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tslogging.cpp,694) TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

TS environment is not initialized TSBootShell 6/22/2016 4:54:18 PM 972 (0x03CC)

Share this post


Link to post
Share on other sites

Hi Ingram,

 

We seem to be in the exact same boat !

I have exactly the same issue with a Lenovo E530, the x86 driver injects properly into the WinPE image though, but it still doesn't work to boot.

 

Please let me know if you have managed to resolve this issue as we have a vast number of these to image/ReImage ... somwhere in the region of 170!

 

Cheers

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.