Task Sequence Read Error

Hi All,
I've started creating OSD deployment through bootable media. I've injected the Dell PE Driver pack into the Boot Image and then created the ISO. I've then burnt the ISO to usb. All good so far (I think), but then on booting the USB we get past the
loading screen and immediately get an error stating:
'Unable to read Task Sequence Configuration Disk'
At first I thought it was just that it was unable to see the NIC Card, hence why I enjected the Dell PE Driver Pack.
Anyone got any ideas?

Are you plugging the USB stick into a USB2 or 3 port?
If 3, have you included USB3 drivers on the boot image? Bear in mind the versions of WINPE you are using will impact what drivers you need:
3.0
Windows 7 code base. It is included in WAIK 2.0.
3.1
Built from Windows 7 SP1 code base. It is included in Windows Automated
Installation Kit (AIK) Supplement for Windows 7 SP1 available from Microsoft's website.
4.0
Built from Windows 8 code base. It is included in Windows ADK (Windows
Kits 8.0) and available from Microsoft's website.
5.0
Built from Windows 8.1 code base. It is included in Windows ADK (Windows
Kits 8.1) and available from Microsoft's website.

Similar Messages

Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)

Hi there
Patch Tuesday yesterday (10th June2014). As always we deploy new patches first to a test collection where Windows 7 updates automatically apply.
Upon trying to rebuild any of the machines in this test collection, we were presented with the following error message:
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
After searching about this, I found this page from Niall Brady, which explained the problem:
http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/
So I removed some of the machines from the test Windows update collection, and as per the advice in the above link, the error was gone and those machines could be built successfully.
So the problem is there were too many many policies downloaded (apps, packages and most of all updates) for the task sequence ram to store, hence the error.
Now...
...I have a question.
The next logical step to my mind is to patch our OS image with all missing patches, so these do not have to be downloaded at build time. Niall mentions this as one of the resolutions to this issue.
However there seems to be some confusion over whether this would actually make a difference.
I read through this link:
http://social.technet.microsoft.com/Forums/en-US/7e597b44-2586-4063-b6d0-cec48a7c11c7/sccm-2012-task-sequence-failure-0x8007000e?forum=configmanagerosd
There's seems to be no consensus on this.
Is SCCM 2012 clever enough to - when the task sequence is first started - to download ONLY the updates (policies) it detects as NOT present in the OS image...
or
Will it simply try to download policies for ALL items deployed to it, whether the updates are present in the OS image or not?
I will be disappointed if SCCM 2012 SP1 CU2 isn't clever enough to only download policies at build time for the apps, packages and updates it detects as needed.
I'd be grateful for some clarity on this.
Regards,
John, Glasgow.

Hi Jason
Thank you for replying, I appreciate it.
1) We currently have 15 or 16 software update groups for Office updates, dating back a month or two. The latest software update group contains all the patches in the previous software update groups plus the patches released on 10th June. Do you recommend
deleting all but the latest software update group?
2) I'm almost reluctant to ask this, but based on what you have advised, is it the case that when the task sequence executes, it will download policies for each update in each software update group regardless of whether it has already downloaded a policy
for an update in a previous software update group? So in effect it's downloading policies (for updates) it has already downloaded?
3) I'm not clear on why there would be no policy for an image; in Niall Brady's informative page on the 8007000E error, he writes the following:
"The reason it has run of space could be due to four possibilites: too many applications, too many Windows updates, too many Task Sequence steps, too many referenced packages'.
Can you shed some light on why there isn't a policy for an image?
Thanks again for replying,
John.

Capture Media and running Task Sequence gets error 0x80004005 and TSMBAutorun.log error

Hi All,
I've been stuck on this for a while now, trying to figure out why I am getting the following error in the
TSMBAutorun.log file
<![LOG[TSMBAutoRun started]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1">
<![LOG[Unknown system architecture 0]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1">
The Unknown System Architecture is strange, the only reason I think of getting it is that the Motherboard/BIOS is NCR not your normal HP etc..
The OS is Windows 7 x86 Pro of the domain nothing special on it, just trying to capture a image of it with SCCM 2012. Even tired a TS to capture it, but I disabled the Partition Disk, apply OS, as I just wanted the Capture part of it but got the same error
as above and same error in the log file.
Any ideas?

Hi,
<![LOG[Network Access Account is not set]LOG]!><time="10:49:43.907-720" date="04-22-2014" component="TSMBootstrap" context="" type="2" thread="1012" file="tspolicy.h:179">
Open the SCCM console and navigate to this node: Administration>Overview>Site>OperationsSites. Right-click on the SCCM site in the right-hand pane, and select Software Distribution. Click on the
Network Access Account tab, and set the account you want to use.
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.

Failed to Run Task Sequence (error ocurred while retrieving policy for the computer)

Hi, all of sudden we're getting an issue with SCCM when attempting to deploy an image we get a Failed to Run Task Sequence. Used to work previously, now suddenly it isn't working for any.
Full error:
Failed to Run Task Sequence
An Error occurred while retrieving policy for this computer (0x8009310B). For more information....
Log:
Reading Policy Body. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Parsing Policy Body. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Downloading policy body EAB200A4-EAB00066-6F6BCC28. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Preparing Policy Body Request. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Setting transport. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Setting policy location = ttp://<mp>/SMS_MP/.sms_pol?EAB200A4-EAB00066-6F6BCC28.11_00. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Executing Policy Body Request. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
CLibSMSMessageWinHttpTransport::Send: URL: servername.bla.com.au:80 GET /SMS_MP/.sms_pol?EAB200A4-EAB00066-6F6BCC28.11_00 TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Error. Status code 404 returned TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Found a secure policy. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Trying to decode policy. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=8009310b (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,339) TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Decoding in non ssl mode failed. Checking if decoding was really needed. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Failed to verify a properly formed XML. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
oPolicy.RequestPolicy((GetPolicyFlags() & POLICY_SECURE) != 0, (GetPolicyFlags() & POLICY_COMPRESS) != 0), HRESULT=8009310b (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,2067) TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Failed to download policy EAB200A4-EAB00066-6F6BCC28 (Code 0x8009310b). TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
(*iTSPolicyAssignment)->GetObjects(pszClassName, aTSPolicyObjectArray ), HRESULT=8009310b (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,1224) TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
m_pPolicyManager->GetObjects( TS::Policy::TaskSequence::GetClassNameW(), TS::Policy::TaskSequence::GetPolicyCategory(), TS::Policy::TSPolicyAssignment::POLICY_TS_FOR_CD_AND_PXE, aTSPolicyObjectArray ), HRESULT=8009310b (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1205) TSPxe 16/01/2015
2:54:40 PM 1176 (0x0498)
Exiting TSMediaWizardControl::GetPolicy. TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=8009310b (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303) TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Setting wizard error: An error occurred while retrieving policy for this computer (0x8009310B). For more information, contact your system administrator or helpdesk operator. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
WelcomePage::OnWizardNext() TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Skipping Confirmation Page. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Skipping Task Sequence Selection Page. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Skipping Variables Selection Page. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Skipping Resolve Progress Page. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Activating Finish Page. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Initializing the countdown timer. TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Loading bitmap TSPxe 16/01/2015 2:54:40 PM 1124 (0x0464)
Suspending the countdown timer. TSPxe 16/01/2015 2:54:49 PM 1124 (0x0464)
Exiting task sequence wizard. TSPxe 16/01/2015 2:54:51 PM 1124 (0x0464)
Exiting with return code 0x00000000 TSPxe 16/01/2015 2:54:51 PM 1124 (0x0464)
Execution complete. TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258) TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
GetTsRegValue() failed. 0x80070002. TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
End program: TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
Finalizing logging from process 840 TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
Finalizing logs to root of first available drive TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
Successfully finalized logs to C:\SMSTSLog TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)
Cleaning up task sequencing logging configuration. TSBootShell 16/01/2015 2:54:51 PM 856 (0x0358)

CLibSMSMessageWinHttpTransport::Send: URL: servername.bla.com.au:80 GET /SMS_MP/.sms_pol?EAB200A4-EAB00066-6F6BCC28.11_00 TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
Error. Status code 404 returned TSPxe 16/01/2015 2:54:40 PM 1176 (0x0498)
6 (0x0358)
Is the management point still working? Examine mpcontrol.log. Do mplist and mpcert work?
Torsten Meringer | http://www.mssccmfaq.de

Failed Run Task Sequence Error (0x80070570)

Hi,
I Have problem with deployment windows vista enterprise:
Failed to Run Task Sequence
An error occurred while starting the task sequence (0x80070570).For More information, please contact your system administrator or helpdesk operator.
It's possible problem Hardware or in my System Center ?
Thanks

Apologies for resurrecting an old thread. I could not resist as my solution to this issue was far different than what was posted here or anywhere else.
I had this issue on a machine that had been deploying fine with a standard build TS. At some point, this error began occurring every time I invoked the TS.
As it turns out, one time during my testing, I had powered off the machine via the power button in the midst of the TS's routine. This just caused it to go wackadoodle and left behind some files that upon restarting the TS could not be overwritten (for whatever
reason).
To fix, I had to run diskpart via cmd while in PE for the TS. To do this, cmd support must be on for the TS. Just press F8, diskpart, sel dis 0 and clean. Voila! Should be fixed now. Or at least in my case it was.

UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhet

your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

Failed to Run Task Sequence (Error 0x80070032)

Hello folks
We just setup the productive SCCM environment and successfully staged many clients. But with one we have some trouble.
I have added the Client with the Hostname and MAC address into SCCM
Added the Client into the Collection where the Task Sequence for staging is applied
Made a boot image on CD-ROM and booted up the client
He can successfully connect to the SCCM Server and also get the right ask Sequence
Bevor starting downloading the Vista OS WIM, the following Error occure:
Failed to Run Task Sequence
An error occured while starting the task sequence (0x80070032).
For more information, please contact ....
I used the Boot CD-ROM successfully on other clients without any problem.
The same Task Sequence was working perfect on other clients
All Clients are HP DC7800 SFF Desktops
BIOS Settings are default by all the Clients
Have tested the same Client on the Test SCCM Environment and got the same problem.
Deleted the Client and re-added it into the SCCM Server
Tried to use different network cable on different location
Client successfully get a DHCP IP address
We have all done so far as I have the knowledge. Any help would kindly be appreachate.
Kind regards
Stefan

Hi folks
As seen in another thread (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2592075&SiteID=17) that the local smsts.log file located in x:\windows\temp\smstslog\ will help to analyse whats happen in the background, I have seen the following line in the Log:
The active system partition on a MBR system must be NTFS
and
Failed to prepare the system partition for staging.
The request is not supported. (Error: 80070032; Source: Windows)
and
Failed to stage WinPE. Code(0x80070032)
So, I did the steps informed in the other thread to press F8 durcing the Error and used the following in the DOS Box:
Diskpart
Select Disk 0
Clean
After that steps, the Bootprocess worked perfect. It seams that the Disk was partitioned not that good, that WinPE could handle it.
Hope this helps other for analysing.
Cheers
Stefan

Failed to run task sequence - 80004005. DNS working though.

I seem to be getting a fairly common generic error but with possibly with a slight difference then some of the other problems/answers I have seen. Generally it looks like this is a DNS issue but I am not sure in my case.
Let me 1<sup>st</sup> describe my infrastructure and what I am trying to accomplish. System Center 2012 R2, trying to deploy server 2012. We use PKI on the main MPs/DPs. I have another DP that I will use for OSD content that
won’t use PKI. I am 1<sup>st</sup> attempting to use boot media, vs PXE, to image a computer. I have distributed the content to the DP, created a boot media USB and everything looks good there as far as I can tell. My boot media
selects the PKI MP and we have created the client cert and I direct it to the non-http DP. The process seems to accept the certificate and the boot media creation completes. Next boot off the media on the computer and drop into Windows PE where
I can manually enter the IP information. When I click next the process fails.
Error:
Failed to Run Task Sequence
An error occurred while retrieving policy for this computer (0x80004005).
So starting some of the troubleshooting I F8.
-Can I ping the SCCM site servers? Yes, I can ping, both short and FQDN, the primary, MP, DP.
Looking at the SMSTSLog I see the following lines/errors.
1)Failed to open PXE registry key. Not a PXE boot.
2)Failed to find the source drive where WinPE was booted from
But then the next line is: Executing from Media WinPE
These 2 are at the top of the log and the process seems to continue on with the IP and variable information. These are the lines of information later in the log with the error(s):
-CLibSMSMessageWinHTTPTransport::Send:URL: (my MP)
-In SSL, but with no client cert
-Error. Received 0x80072ee7 from WinHttpSendRequest.
-Hr,HRESULT=80072ee7
-sending with winhttp failed, 80072ee7
-m_pHttp Transport -> (etc….)
-MPKeyInformation.RequestMPKeyInformationForMedia
-Failed to get information of MP: https//(my MP)
So I am wondering where I start. I don’t see that unknown host line that seems to indicate that it is a DNS issue. I see some stuff about the in SSL but with no cert. Does this mean that the cert we had to create isn’t working correctly?
We pretty much followed
http://www.jamesbannanit.com/2012/05/how-to-build-and-capture-in-configuration-manager-2012-using-https/
I have also looked through this
http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx
And I have pretty much everything done there except a network access account. Looking at my settings I am set to, “Use the computer account of the Configuration Manager client” However, my computer I am trying to image is a “WORKGROUP” and not
joining the domain. But.. am I really getting that far in the process? Would I be failing to get policy because of this or does this just come into play when I try to get the OS from the DP?

Have you seen this thread?
http://social.technet.microsoft.com/Forums/systemcenter/en-US/528c2b54-55ef-4926-bebb-f73ca18a059b/trouble-deploying-windows-7-using-osd-using-pxe-in-sccm-2007-sp2-r3-error-80072ee7?forum=configmgrosd
I have some free manuals http://1drv.ms/1kk6u6j

Task Sequence Command Line to Unregister DLL Not Working...Won't Run As Administrator

Hi All,
I'm trying to unregister a dll by creating a Custom Task Sequence using the command line "%SystemRoot%\System32\regsvr32.exe" /s -u "%CommonProgramFiles%\Microsoft Shared\VGX\vgx.dll"
SCCM is reporting success, however the DLL isn't being unregistered on the client machines. If I manually run the command on a client machine as administrator it works. I have specified that same administrative user in the Custom Task Sequence.
These are Windows 7 machines, so my hunch is it has something to do with UAC, but I'm kind of stumped what to do here but feel like I'm missing something obvious.
Thanks!

Thanks again Jason for sticking with me here. We are running this on 64-bit Windows. Okay, I fixed the command line so it now is: %windir%\sysnative\regsvr32.exe /s -u "%CommonProgramFiles%\Microsoft Shared\VGX\vgx.dll"
Once again, SCCM shows it successfully executed the task sequence, however the dll still didn't unregister.
Any other ideas what might be going on? I really appreciate the help.
Here are the events for the advertisement from old to new in case they help:
Program started for advertisement "SEA2011B" ("SEA000E8" - "*").
Command line: "C:\Windows\SysWOW64\CCM\TSLauncher.exe"
Working directory: C:\Windows\system32\
User context: NT AUTHORITY\SYSTEM
The task sequence execution engine started execution of a task sequence.
The task sequence execution engine successfully completed the action (Run Command Line) in the group () with exit code 0
Action output: =======================[ smsswd.exe ] =======================
PackageID = ''
BaseVar = '', ContinueOnError=''
SwdAction = '0001'
Command line for extension .exe is "%1" %*
Set command line: Run command line
Working dir 'not set'
Executing commandline: Run command line
Process completed with exit code 0
Command line returned 0.
The task sequence execution engine successfully completed a task sequence.

Open task sequence log with cmtrace on error

Hi,
Is there a way to make an SCCM 2012 R2 task sequence automatically open the smsts.log (with cmtrace) when an error occurs?
J.
Jan Hoedt

I would agree with Torstren. The difficult piece would be determining where the smsts.log is, based on where its at in the task sequence. Once you have that it wouldn't be too difficult to place those steps in the
Gather Logs and StateStore on Failure group. The catch will be, even if CMTrace is open, the machine will still reboot after 15 minutes unless the cmd prompt is also open.

One Surface Pro giving 0x8004005 error when looking for task sequence.

This is only happening with one of many Surface Pro's
I am unsure what would cause this, booting from USB in a hub with USB Network Adapter.
<![LOG[LOGGING: Finalize process ID set to 812]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="tslogging.cpp:1495">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816"
file="bootshell.cpp:1052">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="util.cpp:963">
<![LOG[Debug shell is enabled]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:1063">
<![LOG[Waiting for PNP initialization...]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:60">
<![LOG[RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820"
file="configpath.cpp:186">
<![LOG[WinPE boot path: D:\SOURCES\BOOT.WIM]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="configpath.cpp:211">
<![LOG[Booted from removable device]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="configpath.cpp:241">
<![LOG[Found config path D:\]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:545">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:579">
<![LOG[D:\WinPE does not exist.]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:596">
<![LOG[D:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:610">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:45:23.907+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:939">
<![LOG[Starting DNS client service.]LOG]!><time="19:45:23.907+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:663">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="19:45:24.414+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820"
file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:45:24.414+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:939">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604"
file="tsmbootstrap.cpp:1129">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604"
file="tsmbootstrap.cpp:1130">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="util.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="resourceutils.cpp:169">
<![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604"
file="tsmbootstrap.cpp:963">
<![LOG[Failed to open PXE registry key. Not a PXE boot.]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmbootstrap.cpp:844">
<![LOG[Media Root = D:\]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1000">
<![LOG[WinPE boot type: 'Ramdisk:SourceIdentified']LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmbootstrap.cpp:779">
<![LOG[Failed to find the source drive where WinPE was booted from]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="2" thread="604" file="tsmbootstrap.cpp:1036">
<![LOG[Executing from Media in WinPE]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1041">
<![LOG[Verifying Media Layout.]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:1581">
<![LOG[MediaType = BootMedia]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2565">
<![LOG[PasswordRequired = false]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2591">
<![LOG[Found network adapter "ASIX AX88772 USB2.0 to Fast Ethernet Adapter" with IP Address 10.0.192.203.]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="604" file="tsmbootstraputil.cpp:474">
<![LOG[Running Wizard in Interactive mode]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2766">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:45:24.524+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:247">
<![LOG[Activating Welcome Page.]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:131">
<![LOG[Loading bitmap]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1228">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:340">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:247">
<![LOG[Spawned thread 1020 to download policy.]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawelcomepage.cpp:405">
<![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:527">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="19:47:18.401+480"
date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="environmentscope.cpp:284">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="environmentscope.cpp:659">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="19:47:18.401+480"
date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="environmentscope.cpp:284">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="environmentscope.cpp:659">
<![LOG[Setting LogMaxSize to 1000000]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:555">
<![LOG[Setting LogMaxHistory to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:556">
<![LOG[Setting LogLevel to 0]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:557">
<![LOG[Setting LogEnabled to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:558">
<![LOG[Setting LogDebug to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:559">
<![LOG[UEFI: true]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:569">
<![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:584">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsremovablemedia.cpp:322">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="util.cpp:963">
<![LOG[Setting SMSTSLocationMPs TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaSourceVersion TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBrandingTitle TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertSelection TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertStoreName TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSDiskLabel1 TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaSetID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaType TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSRootCACerts TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSupportUnknownMachines TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSTimezone TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Root CA Public Certs=]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:615">
<![LOG[Missing root CA environment variable from variables file]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:621">
<![LOG[Support Unknown Machines: 1]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:632">
<![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:675">
<![LOG[No hook is found to be executed before downloading policy]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:699">
<![LOG[Authenticator from the environment is empty.]LOG]!><time="19:47:18.448+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:838">
<![LOG[Need to create Authenticator Info using PFX]LOG]!><time="19:47:18.448+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:850">
<![LOG[Initialized CStringStream object with string: 1A069864-04BE-4B67-B83D-10B87060836D;2014-01-18T03:47:18Z.]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="stringstream.cpp:101">
<![LOG[Using user-defined MP locations: http://CA1AP03P.cameco.com]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:911">
<![LOG[Set authenticator in transport]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:7751">
<![LOG[Set media certificates in transport]LOG]!><time="19:47:18.557+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:9558">
<![LOG[IP: 10.0.192.203 10.0.192.0]LOG]!><time="19:47:18.557+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:9579">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: CA1AP03P.cameco.com:80 GET /SMS_MP/.sms_aut?MPLOCATION&ir=10.0.192.203&ip=10.0.192.0]LOG]!><time="19:47:18.573+480" date="01-17-2014" component="TSMBootstrap"
context="" type="1" thread="1020" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:8956">
<![LOG[Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="libcrypt.cpp:1914">
<![LOG[Default CSP Type is 24]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libcrypt.cpp:1915">
<![LOG[New settings:]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:925">
<![LOG[    site=CA1,CA1, MP=http://CA1AP03P.cameco.com, ports: http=80,https=443]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="tsmediawizardcontrol.cpp:927">
<![LOG[    certificates are received from MP.]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:931">
<![LOG[Set authenticator in transport]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:7751">
<![LOG[Preparing Client Identity Request.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:583">
<![LOG[    Setting transport.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:586">
<![LOG[    Setting SourceID = 1A069864-04BE-4B67-B83D-10B87060836D.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="tspolicy.cpp:590">
<![LOG[    Setting site code = CA1.]LOG]!><time="19:47:19.762+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:595">
<![LOG[Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.]LOG]!><time="19:47:19.762+480" date="01-17-2014" component="TSMBootstrap" context=""
type="1" thread="1020" file="utils.cpp:1314">
<![LOG[    Setting SMBIOS GUID = 3F9CD3F3-201B-D0BE-FB7A-B6EE09756535.]LOG]!><time="19:47:20.419+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="tspolicy.cpp:623">
<![LOG[    Adding MAC Address 00:50:B6:4D:18:2D.]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:642">
<![LOG[Executing Client Identity Request.]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:666">
<![LOG[Requesting client identity]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:5760">
<![LOG[Setting message signatures.]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: CA1AP03P.cameco.com:80 CCM_POST /ccm_system/request]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="1"
thread="1020" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:8956">
<![LOG[pNext != NULL, HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,1972)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="libsmsmessaging.cpp:1972">
<![LOG[reply has no message header marker]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="libsmsmessaging.cpp:1972">
<![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="libsmsmessaging.cpp:5868">
<![LOG[Failed to get client identity (80004005)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="libsmsmessaging.cpp:6163">
<![LOG[oClientIdentity.RequestClientIdentity(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,668)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="tspolicy.cpp:668">
<![LOG[Failed to read client identity (Code 0x80004005)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="tspolicy.cpp:668">
<![LOG[TS::Policy::GetClientIdentity (&httpTransport, sSiteCode.c_str(), sMediaGuid.c_str(), sClientGUID, sNetbiosName, bUnknown, sServerName, sServerRemoteName, sImportedClientIdentity), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,965)]LOG]!><time="19:47:20.512+480"
date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:965">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:1378">
<![LOG[pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap"
context="" type="0" thread="1020" file="tsmediawelcomepage.cpp:303">
<![LOG[Setting wizard error: An error occurred while retrieving policy for this computer (0x80004005). For more information, contact your system administrator or helpdesk operator.]LOG]!><time="19:47:20.512+480" date="01-17-2014"
component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:1547">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:340">
<![LOG[Skipping Confirmation Page.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediaconfirmationpage.cpp:170">
<![LOG[Skipping Task Sequence Selection Page.]LOG]!><time="19:47:20.528+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediataskselectionpage.cpp:118">
<![LOG[Skipping Variables Selection Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediavariablesselectionpage.cpp:155">
<![LOG[Skipping Resolve Progress Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediaresolveprogresspage.cpp:96">
<![LOG[Activating Finish Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediafinishpage.cpp:107">
<![LOG[Loading bitmap]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1228">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:939">
<![LOG[Successfully launched command shell.]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:430">

I've seen this on a few of the Surface Pro 3's we got in recently. It is because you need to update the date/time in the OS. The easiest way to do this is to
(1) Make sure you have command support enabled in your boot image.
(2) Before you start your image process from the boot image, press (Fn + F8)
(3) At the command prompt, check your date/time.
(4.a) Type cd x:\windows\system32
(4.b) Type date the current date is displayed, it's most likely off. It will prompt you to change the date using the mm-dd-yy format, change to the current date there, press enter
(4.c) Type the Time the current time is displayed (24 hour time), key in the current time press enter
(5) Start your imaging process, all should be well
Excellent advice!!! For me, even though I had already booted the OS on my SP3, fully updated the firmware and restarted about 6 different times, I still would get a failure when the Boot image started to load. I followed these instructions and I was good to
good. I'm just floored to see that my date and time were off by 3 days and 11 hrs, even though my OS was correct. I'm flabbergasted that this was the case. Thanks for the post! Helped me a lot!

"Errors in Task Sequence" dialog after replicating DS

I'm trying to replicate some scripts in the \Scripts folder from a Server 2008 R2 machine running MDT 2012 (update nothing) at our main office out to other servers running the same version of Windows and MDT at our remote sites. I've found
that after doing this and opening the task sequence using this new script at the remote site I get the "This task sequence contains one or more errors..." message. The wim file has been wiped out from the "Install Operating System"
step. The first time I saw this I fixed it thinking it was a one time glitch. Before I replicated to the second remote site I first opened the ts to make sure the wim file was set, then I closed the MDT console, replicated, opened the ts, same
thing, the wim file was removed. Even if I fix it the next replication once again removes the wim. I've also tried uninstalling / reinstalling the MDT console on the source server at our main office, same thing. Looking at the actual
ts.xml for the task sequence at the remote site I can see that the wim file is set, why is the GUI not picking it up?
Ideas?
Some back story that may be related: the local primary server that I would normally use to replicate out DS content was updated to 2012 Update 1 by a coworker a while back, but not the other local secondary server and not the remote sites.
When I attempted to use my usual replication server yesterday to replicate content I got an error about the versions being different. Fine, I copied the new scripts to the scripts folder, made the ts changes manually, and setup the remote sites
as linked deployment shares on my secondary server, and decided I'd just use that for replication. Now I'm thinking maybe something got scrambled when I attemtpted to replicate a 2012 Update 1 DS to 2012 Update nothing.

My specific question is why is the DS replication removing the wim file from the Install Operating System step?
Both the source and target DS's are the same version and I can see that the ts.xml file for the TS in question is being copied to the target DS over but the GUI is not reading the wim file from the xml. I may be missing something simple here
but I've replicated hundreds of times in the past and never had this issue.

OSD - Failed to run Task Sequence. An error occurred while starting the task sequence (0x8007000E).

Failed to run Task Sequence.
An error occurred while starting the task sequence (0x8007000E)."
While OSD, picks up task sequence but fails in resolving task sequence dependencies. SMSPXE identifies device is not in database (unknown).
SMSTS.log shows
ThreadToResolveAndExecuteTaskSequence failed. Code(0x8007000E)" in SMSTS.LOG, have seen other articles suggesting failure due to lack of storage (RAM) but this task sequence has worked in past.
By the way, if I create a stand alone media, we are able to image the workstation. What has changed in the task sequence such that the workstation is unable to download policies due to lack of storage (RAM) on workstation. Workstation has 2 GB of RAM.

I have found a work around for the issue, even though the computer is unknown, there were software updates targeted to the ALL SYSTEMS collection which applies to All Unknown Computers and therefore to x64 Unknown Computer and x86 Unknown Computer.
We had a SCEP ADR applying definition updates to All Systems, we applied the ADR to a different collection, removed all the SCEP updates to All Systems and successfully re-imaged the workstation. Following article was of great help in identifying the problem
after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log
Thanks Gerry for your assistance.

Error editing task sequence: Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" From XML into WMI

I've started getting an intermittent error editing my Windows 7 OSD task sequence. Sometimes I can open the TS to edit, but when I try to apply changes I get the error. Other times I get the error when trying to open the TS. If I try again
right away, I still get the error, but if I wait a few minutes and try again sometimes it will open the TS.
The error reads:
ConfigMgr Error Object:instance of SMS_Extended Status{Description = "Failed to load dynamic properties for class \"SMS_TaskSequence_ApplyWindowsSettingsAction\" from XML into WMI";Error Code = 2147943746;File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";Line = 3454;Operation = "ExecMethod";ParameterInfo = "SMS_TaskSequencePackage";ProviderName = "WinMgmt";StatusCode = 2147749889;}
Coinciding with this error, I show the following entries in the TaskSequenceProvider.log file:
[PID: 7608] Invoking method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Failed to protect memory buffer, hr=0x80070542
TaskSequenceProvider
Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load node Apply Windows Settings from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "PostInstall" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "Execute Task Sequence" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load XML for the task sequence into WMI 0x80070542 (2147943746)
TaskSequenceProvider
[PID: 7608] Done with method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Setting status complete: status code = 0x80070542; Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI
TaskSequenceProvider
I exported the task sequence and checked in "object.xml" for the "ApplyWindowsSettingsAction", to see if there was something odd in the xml, but I don't find anything that jumps out as being wrong. Here's the section of XML for
that step. I've removed identifying info, and replaced it with a generic term in bold.
<step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply Windows Settings" description="" runIn="WinPE" successCodeList="0" runFromNet="false"><action>osdwinsettings.exe /config</action><defaultVarList><variable name="OSDLocalAdminPassword" property="AdminPassword"></variable><variable name="OSDComputerName" property="ComputerName">%_SMSTSMachineName%</variable><variable name="OSDProductKey" property="ProductKey"></variable><variable name="OSDRandomAdminPassword" property="RandomAdminPassword">false</variable><variable name="OSDRegisteredOrgName" property="RegisteredOrgName">COMPANY NAME</variable><variable name="OSDRegisteredUserName" property="RegisteredUserName">COMPANY NAME</variable><variable name="OSDServerLicenseConnectionLimit" property="ServerLicenseConnectionLimit">5</variable><variable name="OSDTimeZone" property="TimeZone">Central Standard Time</variable></defaultVarList></step><step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply Network Settings" description="" runIn="WinPEandFullOS" successCodeList="0" runFromNet="false"><action>osdnetsettings.exe configure</action><defaultVarList><variable name="OSDDomainName" property="DomainName">DOMAIN.COM</variable><variable name="OSDJoinPassword" property="DomainPassword"></variable><variable name="OSDJoinAccount" property="DomainUsername">DOMAIN ACCOUNT</variable><variable name="OSDEnableTCPIPFiltering" property="EnableTCPIPFiltering" hidden="true">false</variable><variable name="OSDNetworkJoinType" property="NetworkJoinType">0</variable><variable name="OSDAdapterCount" property="NumAdapters" hidden="true">0</variable></defaultVarList></step>
Is there any other log I should check for a clue on this issue? What could be causing this error?

Thanks for sharing that! I tend to save contacting MS support until after I've exhausted other options. I'm always afraid that I'll spend the $500 to open a case and then it turns out to be something simple that I would have found if I had just
kept working on it myself a little longer.
It looks like that link is for an update released in February as KB3023562. I downloaded and installed it. I'll try opening/editing/saving the task sequence a few times today to see if the issue is resolved.
After I had already installed it, I thought to look up that update in configmgr. The update is listed as superseded by 2 other updates. The newest of those is KB3046049, which just installed last night with the other March patches, so it's possible
that I didn't need to install KB3023562 after all.

SCCM 2012 Export Task Sequence fails with generic error message

We have a complex task sequence comprising of more than 50 applications\packages, 1975 drivers, 18 driver packages etc etc. Its long, it's big and it will not export with it's content.
We have several environments for development test and live. I am attempting to export the primary task sequence with all it's dependencies from live so that I can port it over to a new development environment.
I can export the zip file without content and it comes to 92Mb in size. The entire task sequence software set is 50Gb+. When I attempt to export with all dependencies and content the process gets about 60% of the way through and fails with the error
"Error: The filename, directory name, or volume label syntax is incorrect"
Googling the error roughly defines the problem as 'the export process cannot access the defined source path for one of the dependant items'
I wrote a PowerShell script that looks as every application, package, driver, driver package, boot image, os image and software update package in the entire SCCM software library and verifies that each and every package has a valid UNC source directory
that can be reached using test-path.
I also wrote another tool that parsed the entire source software library on the server looking for permissions errors (permissions on the structure set at a directory level rather than inherited), directories that were too long, inaccessible or otherwise
blocked, nothing was found.
It will take a very long time to go through and check each and every dependency by hand - time I do not have at present.
I looked in the TaskSequenceProvider.log as that is supposed to contain messages from the export process and found the messages in there far too high a level to use
=======================
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:00:41.161-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
<![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.339-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:333">
<![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:352">
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
<![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:01:36.036-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="5592" file="wmiprovider.cpp:399">
<![LOG[[1AFF658 PID:3500] Initializing provider for namespace root\sms\site_P01]LOG]!><time="13:02:36.550-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068"
file="wmiprovider.cpp:90">
<![LOG[[1AFF658 PID:3500] Initialization of provider for namespace root\sms\site_P01 succeeded]LOG]!><time="13:02:36.551-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1"
thread="7068" file="wmiprovider.cpp:107">
<![LOG[[PID: 3500] Invoking method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.554-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
<![LOG[[PID: 3500] Done with method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.558-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:02:36.559-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
<![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.428-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
<![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
<![LOG[Setting status complete: status code = 0x0; ]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
<![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:03:36.369-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:399">
====================
Is there any way of increasing the log verbosity? I need to see what item is causing the export to fail.
Is there another log containing the information about the export & what it is doing?
All out builds that use the task sequence complete successfully, we can edit the sequence fine, make changes etc. so no internal corruption we can find.
Any ideas?

Torsten, smsprov.log did indeed prove useful, I could see every package as it was validated. Unfortunately the log was wrapping about every 4 minutes and it takes 3+ hours for the task sequence to reach the fail point so I still cannot see the offending
package as it wraps before I can get to the log.
I will increase the size of the log and see if I can maintain some details to investigate.
There was nothing of note in the event logs, certainly nothing leading me to suspect that WMI might be reaching its limits.
I will keep looking for the cause and will post here when I find it <= positive thinking :)

Task Sequence Read Error

Similar Messages

Maybe you are looking for