Have you got the respond to pxe clients ticked in the DP settings?
The MAC address looks "odd". Like with some new PC's with BIOSes that report incorrect smbios GUIDs, SCCM often has a paddy because it's then not unique. It either won't therefore PXE boot because it's already known (when deploying to unknown computers, I prefer that method rather than manually adding to a build group) or it's conflicting.
Try another bit of hardware if you can.
Does it boot if you allocate your task sequence to the unknown PCs collection?
I got somewhere before I left work.
It boots in to wds. And asks for password. I select the task and it says it can't find it.
You may need to distribute the content.
You still have to right click on the task sequence and distribute the content.
I right click my task sequence
Click on Distribute content
Click next on general
Click next on content
When i get to content destation it not show any distrbution points? What am i missing?
Screenshot 2014-06-06 07.46.21.png
So your content is distributed. What error code do you get when try and image the PC? Failing that when in winpe hit F8 (if you have enabled command line support) and type cmtrace, Then close the wizard and you should find a log file on X drive called smsts.log . That should point to the issue.
Have you already deployed it?
Check the deployments tab at the bottom of that screen
Can you grab the SMSTSLog.log file from the client to see why its failing (Press F8 during the deployment and copy the log file to the server via the command prompt)
What is Package CKS00003? From the numbering I'm guessing its either a boot image - or your CCM Client Package?
Check your references tab on the TS and make sure all packages there are deployed and available for TS and PXECode:LocationsList.size() > 0, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,2138) TSPxe 06/06/2014 08:06:51 1324 (0x052C)FALSE, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,1930) TSPxe 06/06/2014 08:06:51 1324 (0x052C) Content location request for CKS00003:6 failed. (Code 0x80040102) TSPxe 06/06/2014 08:06:51 1324 (0x052C) hr, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,2702) TSPxe 06/06/2014 08:06:51 1324 (0x052C) Failed to resolve PackageID=CKS00003 TSPxe 06/06/2014 08:06:51 1324 (0x052C) (*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,3488) TSPxe 06/06/2014 08:06:51 1324 (0x052C) m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1564) TSPxe 06/06/2014 08:06:51 1324 (0x052C) Failed to resolve selected task sequence dependencies. Code(0x80040102) TSPxe 06/06/2014 08:06:51 1324 (0x052C) hrReturn, HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,445) TSPxe 06/06/2014 08:06:51 1324 (0x052C) ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102) TSPxe 06/06/2014 08:06:51 1324 (0x052C) ThreadToResolveAndExecuteTaskSequence returned code 0x80040102 TSPxe 06/06/2014 08:06:51 1176 (0x0498)
There are currently 1 users browsing this thread. (0 members and 1 guests)