Hello,
I have a SCCM server to deploy and capture a Windows Vista image.
I follwed this manual: http://www.windows-noob.com/forums/index.php?showtopic=512
When starting the client, it starts loading the files, says it is initializing the hardware (it detects the network card), then initializing the network connections. En then, the computer reboots!
Someone who can help me?
Thanks.
SCCM OS Deployment: Windows PE reboots without error
December 10th, 2008 1:11pm
Hello,
That is a fine set of instructions, but if your Windows PE reboots without error - what really is the problem?
Like, what are you expecting?
What might have gone wrong?
Have you checked the logs of all the activities to ascertain what might be going wrong?
And do you understand if you have a problem or not?
Basically, it is better to present your scenario in a more technical framework so that we can understand your experience and hopefully provide ideas and sugesstions to help you resolve the issues.
Regards,
Akin
That is a fine set of instructions, but if your Windows PE reboots without error - what really is the problem?
Like, what are you expecting?
What might have gone wrong?
Have you checked the logs of all the activities to ascertain what might be going wrong?
And do you understand if you have a problem or not?
Basically, it is better to present your scenario in a more technical framework so that we can understand your experience and hopefully provide ideas and sugesstions to help you resolve the issues.
Regards,
Akin
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2008 2:59pm
Oke here it comes:
1 X SCCM 2007 on Windows Server 2003 SP2 member om Active Directory. SCCM server runs DHCP.
Followed the instructions of the url in the first post. Added the drivers of the Intel network adapter in my test client machine.
The client boots and gets an IP adres. I made a reservation for this client: 192.168.70.248 (SCCM server: 192.168.70.229, DNS: 192.168.70.243, Gateway: 192.168.70.243)
After the client get an IP adres, it started loading the files for Windows PE. After loading files, i see the Windows Loading bar. After that, i get a screen with System Center configuration Manager 2007 logo in the background. A popup window says: Initialisation hardware devices. After initialization it says: Windows is Starting Up. After that it says: Preparing Network Connections. After that, the client reboots imidiately.
It does not start the Windows Vista installation and capture process as i expected!
1 X SCCM 2007 on Windows Server 2003 SP2 member om Active Directory. SCCM server runs DHCP.
Followed the instructions of the url in the first post. Added the drivers of the Intel network adapter in my test client machine.
The client boots and gets an IP adres. I made a reservation for this client: 192.168.70.248 (SCCM server: 192.168.70.229, DNS: 192.168.70.243, Gateway: 192.168.70.243)
After the client get an IP adres, it started loading the files for Windows PE. After loading files, i see the Windows Loading bar. After that, i get a screen with System Center configuration Manager 2007 logo in the background. A popup window says: Initialisation hardware devices. After initialization it says: Windows is Starting Up. After that it says: Preparing Network Connections. After that, the client reboots imidiately.
It does not start the Windows Vista installation and capture process as i expected!
December 10th, 2008 3:26pm
Hello,
From the same web site where you got instructions to do your OSD there is another set of documents you can use to troubleshoot OSD.
how can I troubleshoot Windows PE booting in SCCM - windows-noob.com/forums
When you have resolved it, let us know how you did it.
Regards,
Akin
From the same web site where you got instructions to do your OSD there is another set of documents you can use to troubleshoot OSD.
how can I troubleshoot Windows PE booting in SCCM - windows-noob.com/forums
When you have resolved it, let us know how you did it.
Regards,
Akin
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2008 3:42pm
I have the same problem with W2008/SCCM2007SP1 on HP hardware. Let you know if I succeeded.
AkinNLD wrote:
Hello,
From the same web site where you got instructions to do your OSD there is another set of documents you can use to troubleshoot OSD.
how can I troubleshoot Windows PE booting in SCCM - windows-noob.com/forums
When you have resolved it, let us know how you did it.
Regards,
Akin
December 10th, 2008 7:31pm
I started Windows PE and pressed F8 key. ipconfig show that my network card drivers loaded succesfully. I also get an IP adres.
The logfile on the harddisk i see some errors:
Error 1: Failed to connect to "\\MANAGEMENT1.SWITCH-TEST.LOCAL\SMSPKGC$\SW100013"
Error 2: Failed to resolve selected task sequence dependencies
Tomorrow i rebuild package SW100013.
I also found out that a reservation for the network card now always works correct.
The logfile on the harddisk i see some errors:
Error 1: Failed to connect to "\\MANAGEMENT1.SWITCH-TEST.LOCAL\SMSPKGC$\SW100013"
Error 2: Failed to resolve selected task sequence dependencies
Tomorrow i rebuild package SW100013.
I also found out that a reservation for the network card now always works correct.
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2008 9:18pm
Most likely it is not getting a DHCP, or the network drivers are not working correctly in WinPE.
Mike-
Mike-
December 11th, 2008 10:44pm
Silly question, but do you have sufficent memory as well? try increasing it and see if that helps.
Free Windows Admin Tool Kit Click here and download it now
January 9th, 2009 9:29pm
I can tell you exactly where your problem is.
You haven't got the correct drivers in your boot image. You'll have to edit your boot image by r-clicking on it and selecting properties. Under the windows PE tab is where you need to add them. Though if you know the right driver by looking in your driver packages you can also r-click on it and select add to boot image and it'll do the same thing. Just make sure you update your distribution points after doing so.
Cheers.
Duren
You haven't got the correct drivers in your boot image. You'll have to edit your boot image by r-clicking on it and selecting properties. Under the windows PE tab is where you need to add them. Though if you know the right driver by looking in your driver packages you can also r-click on it and select add to boot image and it'll do the same thing. Just make sure you update your distribution points after doing so.
Cheers.
Duren
- Proposed as answer by Duren Tuesday, January 20, 2009 8:41 AM
- Marked as answer by John.VMicrosoft employee, Moderator Thursday, February 19, 2009 10:55 PM
January 20th, 2009 11:41am
I can tell you exactly where your problem is.
You haven't got the correct drivers in your boot image. You'll have to edit your boot image by r-clicking on it and selecting properties. Under the windows PE tab is where you need to add them. Though if you know the right driver by looking in your driver packages you can also r-click on it and select add to boot image and it'll do the same thing. Just make sure you update your distribution points after doing so.
Cheers.
Duren
You haven't got the correct drivers in your boot image. You'll have to edit your boot image by r-clicking on it and selecting properties. Under the windows PE tab is where you need to add them. Though if you know the right driver by looking in your driver packages you can also r-click on it and select add to boot image and it'll do the same thing. Just make sure you update your distribution points after doing so.
Cheers.
Duren
- Proposed as answer by Duren Tuesday, January 20, 2009 8:41 AM
- Marked as answer by John.VMicrosoft employee, Moderator Thursday, February 19, 2009 10:55 PM
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2009 11:41am
Hello!
Duren is quite right!
There could be 2 Reasons for this behaviour:
1) you have got too few RAM for Windows PE (it has to have at least 512 MB). If you use a physical machine, it shouldn`t be teh problem :-)
2) you have not the correct drivers (for especially the NIC).
Both things you can find out, if you won`t start with PXE Boot (and WDS). You have to start with a medium withthe SCCM Boot Image on it (bootable CD). IN most cases there would be the correct error message to see.
regards
hemi
January 29th, 2009 8:24am
Hey all
You guys are my final hope... ;)
I have exactly the same problem like Maarten Brand... But:
- Everything seems to be right
--> I added the right drivers
--> My VM got 1024 MB RAM
--> If I enable the cmd and hit F8 everything's fine. I can ping the sccm server, the ad server, I can make ipconfig /release -> /renew, DHCP lease is ok, resolving the ad-name, everything works...
But the client reboots within5 secondsafter WinPE says "Preparing Network connections..."
Does anybody have an other idea?
Greetz
Lukas / alittleouder
EDIT:
<![LOG[LOGGING: Finalize process ID set to 808]LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="tslogging.cpp:1489">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="util.cpp:869">
<![LOG[Debug shell is enabled]LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:974">
<![LOG[Waiting for PNP initialization...]LOG]!><time="18:17:20.140+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:59">
<![LOG[Booted from network (PXE)]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="configpath.cpp:198">
<![LOG[Found config path X:\sms\data\]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:553">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:564">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="18:17:42.656+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:850">
<![LOG[Starting DNS client service.]LOG]!><time="18:17:42.656+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:597">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="18:17:43.156+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="18:17:43.156+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:850">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="18:17:43.187+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="18:17:43.187+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:850">
<![LOG[Successfully launched command shell.]LOG]!><time="18:17:43.187+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:430">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="18:17:43.250+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="tsmbootstrap.cpp:1038">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="18:17:43.265+000" date="02-02-2009" component="TSMBootstrap" context="" type="0" thread="944" file="tsmbootstrap.cpp:1039">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="18:17:43.265+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="util.cpp:869">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="18:17:43.265+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="resourceutils.cpp:152">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="tsmbootstrap.cpp:920">
<![LOG[Executing from PXE in WinPE]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSMBootstrap" context="" type="0" thread="944" file="tsmbootstrap.cpp:935">
<![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSMBootstrap" context="" type="0" thread="944" file="tsmbootstraputil.cpp:1319">
<![LOG[TsPxe.dll loaded]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmbootstraputil.cpp:1329">
<![LOG[Device has PXE booted]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:134">
<![LOG[Variable Key Len: 61]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:141">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="18:17:43.328+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 192.168.0.17 get \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var X:\sms\data\variables.dat]LOG]!><time="18:17:43.328+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:17:43.343+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.0.17 get \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var X:\sms\data\variables.dat]LOG]!><time="18:17:43.343+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.0.17 get \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var X:\sms\data\variables.dat]LOG]!><time="18:17:43.343+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="commandline.cpp:805">
<![LOG[Process completed with exit code 0]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="commandline.cpp:1102">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="fwopen.cpp:146">
<![LOG[Successfully downloaded pxe variable file.]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tspxe.cpp:187">
<![LOG[we are booted using PXE]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmediawizardcontrol.cpp:2223">
<![LOG[we are booted using PXE and we use a generated password]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmediawizardcontrol.cpp:2228">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsremovablemedia.cpp:321">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185)]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="windes.cpp:185">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386)]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsremovablemedia.cpp:386">
<![LOG[Verifying media password.]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmediawizardcontrol.cpp:267">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsremovablemedia.cpp:321">
<![LOG[MSXML 6.0 not available, failing over to lower version.]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="2" thread="944" file="xmlutil.cpp:1529">
<![LOG[spDoc.createInstance(CCM::Utility::XML::c_szCLSIDDomDocument3), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\core\ccmcore\xmlutil.cpp,1535)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="xmlutil.cpp:1535">
<![LOG[CreateXMLDocument(&spDoc), HRESULT=80040154 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1089)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="ccmxml.h:1089">
<![LOG[createNewDocument(), HRESULT=80040154 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1113)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="ccmxml.h:1113">
<![LOG[oXMLDoc.loadFromXML( (LPCWSTR) pbDecryptedBuffer ), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,393)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsremovablemedia.cpp:393">
<![LOG[FALSE, HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,280)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmediawizardcontrol.cpp:280">
<![LOG[Invalid password. Please confirm the media password and enter it again.
The specified network password is not correct. (Error: 80070056; Source: Windows)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="3" thread="944" file="tsmediawizardcontrol.cpp:280">
<![LOG[this->SetPassword(sPxePasswd), HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2233)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmediawizardcontrol.cpp:2233">
<![LOG[Password provided cannot decrypt variables file.]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="3" thread="944" file="tsmediawizardcontrol.cpp:2233">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,936)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmbootstrap.cpp:936">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1105)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmbootstrap.cpp:1105">
<![LOG[Exiting with return code 0x80070056]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmbootstrap.cpp:1117">
<![LOG[Execution complete.]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:624">
<![LOG[Finalizing logging from process 808]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1578">
<![LOG[Successfully finalized logs to X:\SMSTSLog]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1635">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="0" thread="840" file="tslogging.cpp:578">
What is this "Media-Password" ??
Where/how canI set this?
You guys are my final hope... ;)
I have exactly the same problem like Maarten Brand... But:
- Everything seems to be right
--> I added the right drivers
--> My VM got 1024 MB RAM
--> If I enable the cmd and hit F8 everything's fine. I can ping the sccm server, the ad server, I can make ipconfig /release -> /renew, DHCP lease is ok, resolving the ad-name, everything works...
But the client reboots within5 secondsafter WinPE says "Preparing Network connections..."
Does anybody have an other idea?
Greetz
Lukas / alittleouder
EDIT:
<![LOG[LOGGING: Finalize process ID set to 808]LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="tslogging.cpp:1489">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="util.cpp:869">
<![LOG[Debug shell is enabled]LOG]!><time="18:17:20.062+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:974">
<![LOG[Waiting for PNP initialization...]LOG]!><time="18:17:20.140+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:59">
<![LOG[Booted from network (PXE)]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="configpath.cpp:198">
<![LOG[Found config path X:\sms\data\]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:553">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:564">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="18:17:20.234+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="18:17:42.656+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:850">
<![LOG[Starting DNS client service.]LOG]!><time="18:17:42.656+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:597">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="18:17:43.156+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="18:17:43.156+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:850">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="18:17:43.187+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="18:17:43.187+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:850">
<![LOG[Successfully launched command shell.]LOG]!><time="18:17:43.187+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="812" file="bootshell.cpp:430">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="18:17:43.250+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="tsmbootstrap.cpp:1038">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="18:17:43.265+000" date="02-02-2009" component="TSMBootstrap" context="" type="0" thread="944" file="tsmbootstrap.cpp:1039">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="18:17:43.265+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="util.cpp:869">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="18:17:43.265+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="resourceutils.cpp:152">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSMBootstrap" context="" type="1" thread="944" file="tsmbootstrap.cpp:920">
<![LOG[Executing from PXE in WinPE]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSMBootstrap" context="" type="0" thread="944" file="tsmbootstrap.cpp:935">
<![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSMBootstrap" context="" type="0" thread="944" file="tsmbootstraputil.cpp:1319">
<![LOG[TsPxe.dll loaded]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmbootstraputil.cpp:1329">
<![LOG[Device has PXE booted]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:134">
<![LOG[Variable Key Len: 61]LOG]!><time="18:17:43.312+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:141">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="18:17:43.328+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 192.168.0.17 get \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var X:\sms\data\variables.dat]LOG]!><time="18:17:43.328+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:17:43.343+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.0.17 get \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var X:\sms\data\variables.dat]LOG]!><time="18:17:43.343+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.0.17 get \SMSTemp\2009.02.02.17.44.04.0003.{858234FF-7896-4F39-972E-EC6C0F37AB2A}.boot.var X:\sms\data\variables.dat]LOG]!><time="18:17:43.343+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="commandline.cpp:805">
<![LOG[Process completed with exit code 0]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="commandline.cpp:1102">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="fwopen.cpp:146">
<![LOG[Successfully downloaded pxe variable file.]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tspxe.cpp:187">
<![LOG[we are booted using PXE]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmediawizardcontrol.cpp:2223">
<![LOG[we are booted using PXE and we use a generated password]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmediawizardcontrol.cpp:2228">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsremovablemedia.cpp:321">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185)]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="windes.cpp:185">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386)]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsremovablemedia.cpp:386">
<![LOG[Verifying media password.]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmediawizardcontrol.cpp:267">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="18:17:43.375+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsremovablemedia.cpp:321">
<![LOG[MSXML 6.0 not available, failing over to lower version.]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="2" thread="944" file="xmlutil.cpp:1529">
<![LOG[spDoc.createInstance(CCM::Utility::XML::c_szCLSIDDomDocument3), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\core\ccmcore\xmlutil.cpp,1535)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="xmlutil.cpp:1535">
<![LOG[CreateXMLDocument(&spDoc), HRESULT=80040154 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1089)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="ccmxml.h:1089">
<![LOG[createNewDocument(), HRESULT=80040154 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1113)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="ccmxml.h:1113">
<![LOG[oXMLDoc.loadFromXML( (LPCWSTR) pbDecryptedBuffer ), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,393)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsremovablemedia.cpp:393">
<![LOG[FALSE, HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,280)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmediawizardcontrol.cpp:280">
<![LOG[Invalid password. Please confirm the media password and enter it again.
The specified network password is not correct. (Error: 80070056; Source: Windows)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="3" thread="944" file="tsmediawizardcontrol.cpp:280">
<![LOG[this->SetPassword(sPxePasswd), HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2233)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmediawizardcontrol.cpp:2233">
<![LOG[Password provided cannot decrypt variables file.]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="3" thread="944" file="tsmediawizardcontrol.cpp:2233">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,936)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmbootstrap.cpp:936">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80070056 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1105)]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="0" thread="944" file="tsmbootstrap.cpp:1105">
<![LOG[Exiting with return code 0x80070056]LOG]!><time="18:17:43.390+000" date="02-02-2009" component="TSPxe" context="" type="1" thread="944" file="tsmbootstrap.cpp:1117">
<![LOG[Execution complete.]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:624">
<![LOG[Finalizing logging from process 808]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1578">
<![LOG[Successfully finalized logs to X:\SMSTSLog]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1635">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:17:43.406+000" date="02-02-2009" component="TSBootShell" context="" type="0" thread="840" file="tslogging.cpp:578">
What is this "Media-Password" ??
Where/how canI set this?
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2009 8:00pm
The original problem: Your boot image does not have network adapter drivers. Find correct drivers and add them to your boot image.
February 2nd, 2009 8:38pm
Hey
Thanks for your answer...
It's a Virtual-client on a Hyper-V Server. I've added the Hyper-V NIC-Drivers of the "Integration Disc" of Hyper-V.
But I still got the Error from above...
I can't imagine, that there are wrong drivers on the "Integration Disc"... =/
Greetz
alittlelouder
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2009 1:39pm
Hi,
You can configure a PXE password on the Properties of the PXE service point role. (Site Management | Site Name | Site Sytems | <machine name of machine holding PXE service point role> | ConfigMgr PXE service point role | Right Click Properties | Tab General)
What type of OS are you installing in Hyper-V ?, there is an issue with WS2003 X64 and the synthetic network card. (because there are no x64 drivers for that card).
Also can you post the wpeinit.log (x:\windows\system32\)file?
Regards,
Kenneth
You can configure a PXE password on the Properties of the PXE service point role. (Site Management | Site Name | Site Sytems | <machine name of machine holding PXE service point role> | ConfigMgr PXE service point role | Right Click Properties | Tab General)
What type of OS are you installing in Hyper-V ?, there is an issue with WS2003 X64 and the synthetic network card. (because there are no x64 drivers for that card).
Also can you post the wpeinit.log (x:\windows\system32\)file?
Regards,
Kenneth
February 3rd, 2009 3:23pm
Hey
I'm trying to install ax64 Vista SP1 client...
---
In another forum I've read, that I need to install the WinPE-XML-Package to the boot.wim. Right now I'm making a new boot.wim, this time I take the source-File of the Windows AIK 1.1.
I'm going to do following steps:
- Implement XML-Package
- Change targetpath to X:\
- Implement NIC-Drivers
- Rebuild the boot.wim
---
This didn't work, cuz i couldn't add any drivers (Error 80070002)
Greets
Lukas
btw. my log:
--- wpeinit.log ---
Info No unattend file was found; WPEINIT is using default settings to initialize WinPE
Info Spent 8156ms initializing removable media before unattend search
Info ==== Initializing Display Settings ====
Info No display settings specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Computer Name ====
Info Generating a random computer name
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Virtual Memory Paging File ====
Info No WinPE page file setting specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Optional Components ====
Info WinPE optional component 'Microsoft-WinPE-WSH' is present
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Network Access and Applying Configuration ====
Info No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info Service dhcp stop: 0x00000000
Info Service lmhosts stop: 0x00000000
Info Service bfe stop: 0x00000000
Info Service ikeext stop: 0x00000000
Info Service mpssvc stop: 0x00000000
Info Spent 172ms initializing security templates; status 0x00000000
Info Install MS_MSCLIENT: 0x0004a020
Info Install MS_NETBIOS: 0x0004a020
Info Install MS_SMB: 0x0004a020
Info Install MS_TCPIP6: 0x0004a020
Info Install MS_TCPIP: 0x0004a020
Info Spent 5375ms installing network components
Info iSCSI: iBFT ACPI Table is not available on this system
Info Installing device pci\ven_1011&dev_0009&subsys_21140a00&rev_20 X:\WINDOWS\INF\dc21x4vm.inf succeeded
Info Spent 7407ms installing network drivers
Info QueryAdapterStatus: found operational adapter with DHCP address assigned.
Info Spent 0ms confirming network initialization; status 0x00000000
Info STATUS: SUCCESS (0x00000000)
Info ==== Applying Firewall Settings ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Synchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Asynchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Applying Shutdown Settings ====
Info No shutdown setting was specified
Info STATUS: SUCCESS (0x00000001)
I'm trying to install ax64 Vista SP1 client...
---
In another forum I've read, that I need to install the WinPE-XML-Package to the boot.wim. Right now I'm making a new boot.wim, this time I take the source-File of the Windows AIK 1.1.
I'm going to do following steps:
- Implement XML-Package
- Change targetpath to X:\
- Implement NIC-Drivers
- Rebuild the boot.wim
---
This didn't work, cuz i couldn't add any drivers (Error 80070002)
Greets
Lukas
btw. my log:
--- wpeinit.log ---
Info No unattend file was found; WPEINIT is using default settings to initialize WinPE
Info Spent 8156ms initializing removable media before unattend search
Info ==== Initializing Display Settings ====
Info No display settings specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Computer Name ====
Info Generating a random computer name
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Virtual Memory Paging File ====
Info No WinPE page file setting specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Optional Components ====
Info WinPE optional component 'Microsoft-WinPE-WSH' is present
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Network Access and Applying Configuration ====
Info No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info Service dhcp stop: 0x00000000
Info Service lmhosts stop: 0x00000000
Info Service bfe stop: 0x00000000
Info Service ikeext stop: 0x00000000
Info Service mpssvc stop: 0x00000000
Info Spent 172ms initializing security templates; status 0x00000000
Info Install MS_MSCLIENT: 0x0004a020
Info Install MS_NETBIOS: 0x0004a020
Info Install MS_SMB: 0x0004a020
Info Install MS_TCPIP6: 0x0004a020
Info Install MS_TCPIP: 0x0004a020
Info Spent 5375ms installing network components
Info iSCSI: iBFT ACPI Table is not available on this system
Info Installing device pci\ven_1011&dev_0009&subsys_21140a00&rev_20 X:\WINDOWS\INF\dc21x4vm.inf succeeded
Info Spent 7407ms installing network drivers
Info QueryAdapterStatus: found operational adapter with DHCP address assigned.
Info Spent 0ms confirming network initialization; status 0x00000000
Info STATUS: SUCCESS (0x00000000)
Info ==== Applying Firewall Settings ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Synchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Asynchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Applying Shutdown Settings ====
Info No shutdown setting was specified
Info STATUS: SUCCESS (0x00000001)
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2009 4:10pm
Hi,
You don't need to modify your boot.wim. If you use SCCM SP1, you will have the WAIK 1.1. boot image already configured with the correct components. If not, check this:http://www.techlog.org/archive/2008/03/21/how_to_add_waik_11_boot_imagesor thishttp://support.microsoft.com/kb/950782/en-us.
As far as i can see, you have network indeed.
At a certain moment the drivers you specified in your task sequence will be loaded, so do you have the correct drivers in your task sequence as well? (driver package?, and how do you load drivers?)
Did you check the PXE password b.t.w? Just to be sure that isn't the problem.
Regards,
Kenneth
You don't need to modify your boot.wim. If you use SCCM SP1, you will have the WAIK 1.1. boot image already configured with the correct components. If not, check this:http://www.techlog.org/archive/2008/03/21/how_to_add_waik_11_boot_imagesor thishttp://support.microsoft.com/kb/950782/en-us.
As far as i can see, you have network indeed.
At a certain moment the drivers you specified in your task sequence will be loaded, so do you have the correct drivers in your task sequence as well? (driver package?, and how do you load drivers?)
Did you check the PXE password b.t.w? Just to be sure that isn't the problem.
Regards,
Kenneth
February 3rd, 2009 6:02pm
If you don't have a media password set, then valiate your content is not corrupted on your DP. Try redistributing the content (i.e. image ) to the DP and see if it resolves the issue. You may also want to recreate the boot.wim.
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2009 1:53am
I know this thread is quite old, but I have come across this problem twice now and the solution has been the same both times. Our boot image contains the correct network card drivers and we were experiencing a reboot at the same point as Maarten. It turns out that someone in our environment created a package but did not publish it to a distribution point. It was added to the imaging Task Sequence and that was when the problem arose.
It seems that if there are any steps in the imaging Task Sequence that cannot be fulfilled then the Task Sequence does not run at all.
Removing this package from the task sequence fixed the problem, so i suggest looking through all the steps in your task sequence to ensure the packages are up to date and they have been published to a DP on your site server or BDP. Make sure all your DP's have the same version of the package also. Use the Manage Distribution Points wizard to do this.
Hope this helps people out there.
- Proposed as answer by Haffel Wednesday, February 23, 2011 10:01 AM
- Unproposed as answer by Haffel Wednesday, February 23, 2011 10:01 AM
- Proposed as answer by John Stream Saturday, April 16, 2011 1:55 AM
November 11th, 2010 6:58am
I know this thread is quite old, but I have come across this problem twice now and the solution has been the same both times. Our boot image contains the correct network card drivers and we were experiencing a reboot at the same point as Maarten. It turns out that someone in our environment created a package but did not publish it to a distribution point. It was added to the imaging Task Sequence and that was when the problem arose.
It seems that if there are any steps in the imaging Task Sequence that cannot be fulfilled then the Task Sequence does not run at all.
Removing this package from the task sequence fixed the problem, so i suggest looking through all the steps in your task sequence to ensure the packages are up to date and they have been published to a DP on your site server or BDP. Make sure all your DP's have the same version of the package also. Use the Manage Distribution Points wizard to do this.
Hope this helps people out there.
- Proposed as answer by Haffel Wednesday, February 23, 2011 10:01 AM
- Unproposed as answer by Haffel Wednesday, February 23, 2011 10:01 AM
- Proposed as answer by John Stream Saturday, April 16, 2011 1:55 AM
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 6:58am
My issue was a new Driver package was not assigned to the main Distribution point. This was not added to the PXE DP as the drivers were already included in the PE WIM.
April 16th, 2011 4:57am
Hi,
I have an issue in deployment of Windows XP capture image on a machine , its PXE boots successfully but after task squencing starts it didnt find vaild network adaptor and gives and task sequencing error message "failed to find vaild network adaptor for more information contact system administrator or helpdesk opreator" while i using alot of network card .inf files which is compatible with that machine but result is same , in last i ran Intel Driver detect and update utilty from this site "http://www.intel.com/p/en_US/support/detect " and found the compatible network card version of that machine on which i want to deploy the image i downlaod that setup pick its .inf file and load them all to boot image , but still result is same :(
Free Windows Admin Tool Kit Click here and download it now
November 17th, 2011 5:11pm
So this same instance happened to me at work today and I finally decided to try something that I didn't think would have anything to do with it, but I did this just because it bothered me that it was incorrect:
-Using SCCM 2012
-Pushing Windows 7 Enterprise (WIM)
As stated above: When starting the client, it starts loading the files, says it is initializing the hardware (it detects the network card), then initializing the network
connections. Then, the computer reboots.
I went into the BIOS and the date and time was completely off. After changing them to the current date and time, it worked just fine and the image was pushed.
- Edited by Rabidfaux Thursday, January 16, 2014 1:35 AM
January 16th, 2014 4:30am
So this same instance happened to me at work today and I finally decided to try something that I didn't think would have anything to do with it, but I did this just because it bothered me that it was incorrect:
-Using SCCM 2012
-Pushing Windows 7 Enterprise (WIM)
As stated above: When starting the client, it starts loading the files, says it is initializing the hardware (it detects the network card), then initializing the network
connections. Then, the computer reboots.
I went into the BIOS and the date and time was completely off. After changing them to the current date and time, it worked just fine and the image was pushed.
- Edited by Rabidfaux Thursday, January 16, 2014 1:35 AM
Free Windows Admin Tool Kit Click here and download it now
January 16th, 2014 4:30am
Just thought I'd add my solution to the same issue in case it helps anyone as it had me stumped for a while.
Cause: Expired/Non existent PXE certificate in SCCM
Added certificate and the autobuild completed successfully :o)
NB: Don't forget to update the distribution points on the boot image after adding the cert.
- Edited by Ben (IBM) 20 hours 53 minutes ago
January 24th, 2014 9:30am
Just thought I'd add my solution to the same issue in case it helps anyone as it had me stumped for a while.
Cause: Expired/Non existent PXE certificate in SCCM
Added certificate and the autobuild completed successfully :o)
NB: Don't forget to update the distribution points on the boot image after adding the cert.
- Edited by Ben (IBM) Friday, January 24, 2014 3:19 PM
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2014 5:28pm
Just thought I'd add my solution to the same issue in case it helps anyone as it had me stumped for a while.
Cause: Expired/Non existent PXE certificate in SCCM
Added certificate and the autobuild completed successfully :o)
NB: Don't forget to update the distribution points on the boot image after adding the cert.
- Edited by Ben (IBM) Friday, January 24, 2014 3:19 PM
January 24th, 2014 5:28pm
I had to vote this up. We had someone drag in a bunch of old laptops and needed to get them imaged ASAP. I really in hindsight SHOULD have checked out the logfile with CMTrace but the error was exactly what you experienced.
Surprisingly, I had trouble finding this issue on the internet. Turns out it was a BIOS time missmatch which causes a certificate issue I believe. With the correct date the image worked fine.
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2014 9:15am
This topic is archived. No further replies will be accepted.
Other recent topics
