Five 2012 servers with DP roles only
I found a possible solution but it didn't work (see below link)
http://prajwaldesai.com/task-sequence-failed-error-code-0x80070002/
The packages are not showing in the smspkgd$ folder including primary Site.
I have removed the DP and deleted the SMS folders.
I have added the DP role on all the site role server and the folders were created successfully
We can't see folders under smspkgx$ folder
I have stopped and restarted the WDS
I can boot to pxe and run the format task but it failed when loading the OS
The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942402
Action output: ... : 0) ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1767) resolvePkgSource(),
HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1810) Apply(),
HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,2019) installer.install(),
HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,2094) ReleaseSource()
for D:\_SMSTaskSequence\Packages\ABB0000B.
The user tries to release a source directory D:\_SMSTaskSequence\Packages\ABB0000B that is either already released or we have not connected to it.
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ),
HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,509)
Installation of image 2 in package ABB0000B failed to complete.
The system cannot find the file specified. (Error: 80070002; Source: Windows).
The operating system reported error 2147942402:
The system cannot find the file specified.
Milestone 11135 31/07/2015 9:42:51 AM H07302 Task Sequence Engine
The task sequence execution engine failed execution of a task sequence.
The operating system reported error 2147942402:
The system cannot find the file specified.
Milestone 11141 31/07/2015 9:42:51 AM H07302 Task Sequence Engine
I have confirmed I the correct account in the DL properties.
Help please
Packages are not supposed to show in any normal SMB share in ConfigMgr 2012 so that's completely normal.
You need to provide the lines before the error code to help see what is going on.
WDS has absolutely nothing to do with happens during a task sequence.
My guess on this is that the unattend.xml file you specified in the Apply OS Image task does not exist in the package you've specified or is misnamed, but as mentioned, without more of the log, that's just a best guess.
Hi Jason
Thank you for the answer. I have created an unattend.xml file . Added to the OS deployment task but the problem continues.
1- we have rebooted the server
2 - I am able to deploy software and one other OS task successfully
3 - we have confirmed BITS , Netframe 3.5 were set up on the sever
below are some logs files
SMSPXE.LOG
1 -68:B5:99:F7:E6:FD, C2E69F08-4397-11E0-9376-2344841CA00C: Updating Device Cached LastAdv Time. Time=03/08/2015 06:03:53 LastAdvID=ABB2001C SMSPXE 3/08/2015 4:03:53 PM 4044 (0x0FCC)
2 - Looking for bootImage ABB00033 SMSPXE 3/08/2015 4:04:11 PM 4044 (0x0FCC)
3 -Report Body: <ReportBody><ClientID>GUID:06
81DFA3-E00E-4307-9E9C-8F85D150267E</ClientID><StateMessage MessageTime="20150803060411.000000+000" SerialNumber="1"><ClientID>GUID:0681DFA3-E00E-4307-9E9C-8F85D150267E</ClientID><Topic ID="PXE Boot
Adv Status" Type="600" IDType="600"/><State ID="100" Criticality="0"/><UserParameters Flags="32" Count="4"><Param>68:B5:99:F7:E6:FD</Param><Param>C2E69F08-4397-11E0-9376-2344841CA00C</Param><Param>ABB2001C</Param><Param>ABB</Param></UserParameters></StateMessage></ReportBody>
SMSPXE 3/08/2015 4:04:11 PM 4044 (0x0FCC)
4 - 68:B5:99:F7:E6:FD, C2E69F08-4397-11E0-9376-2344841CA00C: Updating Device Cached LastAdv Time. Time=03/08/2015 06:04:11 LastAdvID=ABB2001C SMSPXE 3/08/2015 4:04:11 PM 4044 (0x0FCC)
5 - File E:\RemoteInstall\SMSTemp\2015.08.03.15.55.12.01.{ED2E0E6D-C9A1-4834-9C46-D46CBB639DEA}.boot.bcd deleted. SMSPXE 3/08/2015 4:05:23 PM 6896 (0x1AF0)
6 - File E:\RemoteInstall\SMSTemp\2015.08.03.15.55.12.01.{ED2E0E6D-C9A1-4834-9C46-D46CBB639DEA}.boot.bcd.log deleted. SMSPXE 3/08/2015 4:05:23 PM 6896 (0x1AF0)
7 - 68:B5:99:F7:E6:FD, C2E69F08-4397-11E0-9376-2344841CA00C: Not serviced. SMSPXE 3/08/2015 4:06:10 PM 4044 (0x0FCC)
8 - Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777407" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 3/08/2015 4:06:12 PM 4044 (0x0FCC)
9 -68:B5:99:F7:E6:FD, C2E69F08-4397-11E0-9376-2344841CA00C: device is in the database. SMSPXE 3/08/2015 4:06:12 PM 4044 (0x0FCC)
10 - Client boot action reply: <ClientIDReply><
Identification Unknown="0" ItemKey="16777407" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime=""
OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
SMSPXE 3/08/2015 4:06:12 PM 4044 (0x0FCC)
11 -68:B5:99:F7:E6:FD, C2E69F08-4397-11E0-9376-2344841CA00C: no advertisements found SMSPXE 3/08/2015 4:06:12 PM 4044 (0x0FCC)
OS ID IS abb00090
Boot image ID is abb00033
TASK ID is abb00091
deployment id is ?
message ID 10035 in progress waiting for content
in the software centre under installation status tab Downloading (0 complete)
Thank you in advance
11 -68:B5:99:F7:E6:FD, C2E69F08-4397-11E0-9376-2344841CA00C: no advertisements found SMSPXE 3/08/2015 4:06:12 PM 4044 (0x0FCC)
No deployment is found for the given MAC address.
The above is a completely different issue than the one you posted about earlier and should be a completely different thread.
The following have nothing to do with your issue:
"1- we have rebooted the server
2 - I am able to deploy software and one other OS task successfully
3 - we have confirmed BITS , Netframe 3.5 were set up on the sever "
What is package ABB0000B?
Hello,
I have listed those 3 items to show what we have done yesterday
We have some improvement but I will update the forum when we are done testing the OS task.
we have updated the OS properties and these action has created another folder in the smspkge$ folder
http://blog.danovich.com.au/2012/06/19/sccm-2012-access-content-directly-from-distribution-point/
ABB0000B is configuration manager client package
thank you
we have updated the OS properties and these action has created another folder in the smspkge$ folder
Why? There's no reason to do this in ConfigMgr or for task sequences unless you truly want to run TS directly from the DP. It's not enabled by default for a reason though.
Why is your Apply Windows OS task referencing your ConfigMgr client package? That makes no sense but is what is explicitly called out in the first log snippet: "Installation of image 2 in package ABB0000B failed to complete."
Since your task sequence ran, it means that you don't have a problem with WDS.
The SMSPKGD$ is not required by the client. That is not your problem.
What you need to look at are the task sequence log lines just before the ones you posted. Those should tell you why the Apply OS action failed. Can you please post those lines?
Hello
We have found the problem. When I was troubleshooting why the OS task failed (error file not found) I made the mistake of assuming the missing folders under SMSPKGD$ was the root cause of the problem.
missing the xxxx.win file (the OS file)
The second mistake was I removed the DP and put it back. When I reinstalled the role I tick the box "enable this distribution point for prestaged content"
After we turned this option off and redistributed the packages the OS deployment successfully completed the task.
I know now the SMSPKGD$ is not require. But I have managed to populate the folder using the information from the link below
http://blog.danovich.com.au/2012/06/19/sccm-2012-access-content-directly-from-distribution-point/
My tasks are not optimal but I am trying to find tune them now.
I have successfully pushed the OS to a computer.
Thank you for your input.