OSD: where is a task sequence in full os stored?

Hi,
Please see http://social.technet.microsoft.com/Forums/en-US/187b13a9-e05c-47a1-9129-66f8e4546a1e/osd-upgrade-bitlockered-os?forum=configmanagersecurity
Regarding that question I'd like to know: the winpe is prestaged to disk, we can boot but not read the task sequence.
So a general question: in OSD (when loaded in full OS) where is the winpe image stored on disk (encrypted in my case) and where is the task sequence stored on disk?
J.
Jan Hoedt

smsts.log says
ConvertBootToLogicalPath failed (0x80070490). Retrying (29)...   TSBootShell   8/05/2014 11:50:28   828 (0x033C)
bGotPath, HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\bootshell\configpath.cpp,42)   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
ConvertBootToLogicalPath failed after retries. Giving up.   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
GetConfigPathFixedDisk(sArcPath, sWinPEFolder), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\bootshell\configpath.cpp,326)   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
Failed to find the current TS configuration path   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
ConfigPath::FindConfigPath(sConfigPath), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootshell.cpp,545)   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
Failed to find the configuration path.
Element not found. (Error: 80070490; Source: Windows)   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
Execution failed with error 80070490.   TSBootShell   8/05/2014 11:50:30   828 (0x033C)
I find the winpe on the first partition and _SMS logs-something (2 folders) underneath the Windows partition in winpe.
That's why I posted this question, if I know where the task sequence is stored, I can be sure of that.
Jan Hoedt

Similar Messages

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.

Offline OSD Failed to Run Task Sequence 0x80004005

hi Folks.. I am getting this error message "
Failed to Run Task Sequence 0x80004005
when trying to do an offline build via DVD generated from SCCM 2012 R2. Its failing on the applying OS step. Pxe boot build works fine. I've put the smsts log file below. Any help/ advice appreciated.

hi. Apologies there is a restriction on the amount of characters for text so can cannot post the entire smsts log.
here is the step its failing on.
<![LOG[Start executing an instruction. Instruction name: Install Operating System. Instruction pointer: 0]LOG]!><time="03:51:00.239+480" date="01-19-2015" component="TSManager" context="" type="1"
thread="716" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Install Operating System]LOG]!><time="03:51:00.239+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716"
file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=0]LOG]!><time="03:51:00.239+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:668">
<![LOG[The group (Install Operating System) has been successfully started]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1" thread="716" file="instruction.cxx:156">
<![LOG[Do not send status message in full media case]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1" thread="716" file="utils.cpp:5763">
<![LOG[User did not specify local data drive]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="utils.cpp:1974">
<![LOG[Volume D:\ is not a fixed hard drive]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1" thread="716" file="utils.cpp:1077">
<![LOG[Volume X:\ is not a fixed hard drive]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1" thread="716" file="utils.cpp:1077">
<![LOG[TSM root drive = ]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1" thread="716" file="utils.cpp:1142">
<![LOG[We do not find an available volume to store the local data path]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1" thread="716" file="utils.cpp:1989">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=1]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=1]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=0]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=0]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:833">
<![LOG[pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0"
thread="716" file="path.cpp:60">
<![LOG[Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,676)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context=""
type="0" thread="716" file="environmentlib.cpp:676">
<![LOG[Failed to save environment to (80070057)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="2" thread="716" file="environmentlib.cpp:697">
<![LOG[TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,842)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager"
context="" type="0" thread="716" file="executionenv.cxx:842">
<![LOG[Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="3" thread="716" file="executionenv.cxx:842">
<![LOG[SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,420)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context=""
type="0" thread="716" file="executionenv.cxx:420">
<![LOG[Failed to persist execution state. Error 0x(80070057)]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="2" thread="716" file="executionenv.cxx:426">
<![LOG[Failed to save execution state and environment to local hard disk]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="2" thread="716" file="engine.cxx:249">
<![LOG[Start executing an instruction. Instruction name: Restart in Windows PE. Instruction pointer: 1]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="1"
thread="716" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Restart in Windows PE]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716"
file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=1]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:668">
<![LOG[Set a local default variable SMSRebootMessage]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:700">
<![LOG[Set a local default variable SMSRebootTimeout]LOG]!><time="03:51:00.255+480" date="01-19-2015" component="TSManager" context="" type="0" thread="716" file="executionenv.cxx:700">
<![LOG[Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog]LOG]!><time="03:51:00.255+480" date="01-19-2015"

OSD: install software DURING task sequence based upon collection membership

Hi,
I'd like to refer to my
previous post as a starting point.
Below again the background of my question. But please advise on a powershell script that runs at the end of a task sequence that:
*enumerates the pc's collection memberships and based upon that lists the software available
*puts this software in a variable and does the installation DURING the task sequence
J.
Background:
At this time, software in our deployment (of Windows 7) is installed AFTER the task sequence is finished.
The software is deployed based upon the computer membership of collections (which get their info from AD groups).
Problem is that users see their pc as finished but don't have all their software. It even takes sometimes more then an hour even when we refresh computer policy after final reboot of the system. That's why we really need a bulletproof solution = installation
of software DURING task sequence.
Jan Hoedt

I found some time to adjust the script. Now I've created something similar for a device. Basically it finds the collections of which the device is a member, finds the targeted applications and creates task sequence variables for those applications.
See for more information:
http://www.petervanderwoude.nl/post/install-computer-targeted-application-during-os-deployment-via-powershell-and-configmgr-2012/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM OSD and MDT 2012 - Task Sequence query

Hi All
I have single server SCCM 2012 R2 server with MDT 2013 successfully integrated. I'm looking to create a 'Sysprep and Capture' type Task Sequence within SCCM, so that this can be done via PXE rather than SCCM's more manual 'Capture Media' method. Just
wondering if anyone has thoughts on this, experience, pointers etc?
Couple of options that look possible are:
MDT Toolkit Package - include in SCCM based Task Sequence. Would it then be fairly easy to mimic ts steps detailed in MDT's existing 'Sysprep and Capture' TS, but within SCCM?
SCCM TS Steps - I've seen there are a number of TS Steps that look like they may enable OS Capture, but if so, bit confused there isn't more documented \ blogged on this kind of TS, would have thought this was a common requirement for a
SCCM TS? (TS Steps of interest within SCCM: 'Prepare Windows for Capture' and 'Capture Operating System Image')
Any assistance much appreciated!
Kind Regards
Andrew

There is a bit of debate about the best way to capture reference images. Check out this good blog that reviews the options:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/163/The-battle-begins-Building-the-perfect-reference-image-for-ConfigMgr-2012.aspx
Having said that, you can certainly create a capture task sequence in SCCM. If you choose to create a new task sequence,you should see a build and capture option. Simply create a build and capture task sequence and then remove the build steps.
You will be left with:
I've used this method in certain cases.
Or as you said, if you are integrated with MDT, you can create an MDT task sequence to do the capture or add MDT steps as needed.
Hopefully that helps!
Jeff

SCCM OSD using MDT task sequence

Hi all,
Is it right if I capture an image from a Windows 7 machine using SCCM capture media, then deploy it to an existing Windows XP(for migration) using "Create a new
Microsoft Deployment task sequence" wizard (this option appears after integrating MDT with SCCM)? I have this scenario but the targeted machine is not getting joined to domain, I suspect the issue is with sysprep as image that we get using sccm capture
media does not sysprep the reference machine.
What do you think?

I checked the logs and I believe the issue is with sysprep, I found the below in the netsetup.log:
12/15/2014 20:18:54:823 NetpChangeMachineName: from 'OSD-PC' to 'OSD-PC' using 'ssc.gov.jo\majmajali' [0x1000]
12/15/2014 20:18:54:823 NetpDsGetDcName: trying to find DC in domain 'SSC', flags: 0x1010
12/15/2014 20:18:54:823 NetpDsGetDcName: found DC '\\DC5' in the specified domain
12/15/2014 20:18:54:823 NetpGetLsaPrimaryDomain: status: 0x0
12/15/2014 20:18:54:823 NetpGetDnsHostName: Read NV Domain: ssc.gov.jo
12/15/2014 20:18:54:838 NetpGetComputerObjectDn: Cracking account name SSC\OSD-PC$ on
\\DC5
12/15/2014 20:18:54:838 NetpGetComputerObjectDn: Crack results: (Account already exists) DN = CN=OSD-PC,CN=Computers,DC=ssc,DC=gov,DC=jo
12/15/2014 20:18:54:838 NetpModifyComputerObjectInDs: Initial attribute values:
12/15/2014 20:18:54:838   DnsHostName = OSD-PC.ssc.gov.jo
12/15/2014 20:18:54:838   ServicePrincipalName = HOST/OSD-PC.ssc.gov.jo RestrictedKrbHost/OSD-PC.ssc.gov.jo HOST/OSD-PC RestrictedKrbHost/OSD-PC
12/15/2014 20:18:54:838 NetpModifyComputerObjectInDs: Computer Object already exists in OU:
12/15/2014 20:18:54:838   DnsHostName = OSD-PC.ssc.gov.jo
12/15/2014 20:18:54:838   ServicePrincipalName = TERMSRV/OSD-PC.ssc.gov.jo RestrictedKrbHost/OSD-PC.ssc.gov.jo HOST/OSD-PC.ssc.gov.jo TERMSRV/OSD-PC RestrictedKrbHost/OSD-PC HOST/OSD-PC
12/15/2014 20:18:54:838 NetpModifyComputerObjectInDs: There are _NO_ modifications to do
12/15/2014 20:18:54:838 ldap_unbind status: 0x0
12/15/2014 20:18:54:838 NetpChangeMachineName: status of setting DnsHostName and SPN: 0x0
The windows XP machine name to be migrated is OSD-Test, but the task sequence is making computer name the same as the reference (OSD-PC) despite task sequence is already configured to migrate that XP machine network and windows configuration (including
hostname).
I believe you are right, I should create build and capture task sequence in MDT, and in the reference machine I run the below command to capture an image:
cscript “\\MDT server\Deploymentshar1$\scripts\litetouch.vbs. After this capture is done the machine will get into oobe (if all is ok). What do you
think?

Task Sequence packages not installing after upgrade to R2

Hi all
As the title suggests, I've upgraded my SCCM 2012 server from SP1 to R2. The OSD Task Sequences reach the stage where the client is installed, and ends after this point. However there are several software packages after this step that it is seemingly skipping
entirely now.
Any idea why this might be?
Thanks

Ok,
After banging my head for a few days with that issue i saw the light at the end of the tunnel ( an not the
train) today.
Long story short, the culprit was the boot image. I upgraded to 6.3 and everything in my TSs is working as
it should.
Here are the details:
The recall my issue, after upgrading SCCM from SP1 to R2, none of the software packages were getting installed
in a Task sequence. A TS runs up to the installation of the SCCM agent and then it quits.
Looking at the log file in C:\Windows\System32\ccm\logs\smstslog I found the following errors:
Resuming Task Sequence in Full OS TSMBootstrap
Failed to get the environment key. TSMBootstrap
Failed to resume task sequence (0x800700EA).
Exiting with return code 0x800700EA TSMBootstrap
Earlier i mentioned that my boot images did not get updated as part of the site upgraded, so i went and updated
them to version 6.3 and after making sure it got deployed in a TS to make it available through PXE, my problem was gone.
this post helped me tremendously to realized that the boot image was the issue:
https://social.technet.microsoft.com/Forums/en-US/a793071d-1a3b-4b68-b6de-6d8c1a1fda0f/failed-to-get-the-environment-key-smstslog?forum=configmanagerosd
Mario.

A custom task sequence to install software is always listed as Operating System on Software Center

Hello,
I have built several custom task sequences to install software in SCCM 2012 R2 CU1 environment, but the type of task sequence is always listed as Operating System on the Software Center. I tried creating a simple task sequence (Task Sequence 1) that contains
a single restart computer step only and tried deploying it to a test machine. This task sequence is also listed as Operating System. This task sequence fails because this is not the one for OS install and I do not specify a boot image for this task sequence.
All task sequences that I have created in SCCM 2012 RTM environment are working as expected. All task sequences that I create in SCCM 2012 R2 CU1 are listed as Operating System regardless of its actual type (I upgraded my environment from CM2012 RTM to CM2012
R2 CU1 last month).
Here is a test task sequence that contains a single step of restart computer. This is not Operating System install but listed as Operating System. Any thoughts?

If you use OSD steps in your task sequence you will get this prompt.
http://social.technet.microsoft.com/Forums/en-US/3eb7569c-0b5a-4b40-86c3-d4f092c70aca/task-sequence-warning?forum=configmanagerosd
Per Mikko:
Using any of following steps (and possibly others as well, I did not check all of them) will change the task sequence type from generic to OSD:
General - Join Domain or Workgroup
General - Restart Computer (Only "The boot image assigned to this task sequence" option)
Disks - Format and Partition Disk
User State - Request State Store
User State - Release State Store
Images - Apply Operating System Image
Images - Setup Windows and ConfigMgr
Daniel Ratliff | http://www.PotentEngineer.com

Non-Deployed Applications in OSD Task Sequence Are Deployed To Collection Members where OSD TS is deployed

Hello,
I have a situation where an application (which is not deployed) that is part of an OSD Task Sequence is being deployed to computers that are in the same collection my TS for OSD is deployed.
For OSD I have created an application to check the BIOS version and upgrade the BIOS if there is a newer one available. The application has numerous deployment types (13) due to various hardware models and the requirement to go to several intermediary BIOS
versions to reach the current newest version. There are dependencies configured to handle these incremental bumps.
The OSD TS is deployed to a collection that contains all windows desktop class operating systems. What I have seen happen once is that one users workstation somehow discovered and installed the BIOS Upgrade package and their BIOS was upgraded on their workstation.
I've checked the logs on several other machines and this same application has been run as well.
The application is configured "Allow this application to be installed from the Install Applications
task sequence action without being deployed" which allows it to be ran from a TS even though it is not deployed.
I have verified the application is not deployed. I have verified there are no superceedence rules configured. As I stated, there are dependencies, but all dependencies are within this one application.
What I do not understand is, how can an application that is not
deployed and is only referenced in an Operating System Deployment Task Sequence able to be ran outside the task sequence?
This is/has occurred with computers imaged with cm2012 and with computers imaged with cm2007 who have now been migrated to cm2012.
I'm fairly sure that it is due to the task sequence and where it is advertised. Computers that are not in this collection do not show the application being applied in the AppEnforce.log. If it is the TS that is causing this, how can something that is designed
to be a "sequence of tasks", allow something to occur out of that sequence?
Current environment is CM2012R2.
Any thoughts to what might be happening?
Thanks

Hello,
After working with Microsoft Support, we were able to resolve the issue.
Turns out there was something (old policies) "stuck" in the SCCM database that was causing this to be advertised outside the task sequence and not visible on the console. While they didn't call this "a bug" since it has happens with CM2007 as well, it definitely
was not normal behavior. Still not sure how that could happen as I'm 99.99% sure I never deployed this to any collection, but that's what they said.
It took several hours of support rooting through the database to figure out what was going on but after some SQL magic it was fixed. Sorry I don't have more specifics regarding the fix. MS basically said "If it happens again you can do this this and this
in the db and voila its fixed". Since I'm likely to cause more damage (messing with the database) then good if it were to happen again I'd contact them.
Anyway, this odd behavior has spooked me and I've reverted back to deploying the TS to the unknown computer collection. As much as it disappoints me to take a step back and cause more work for the guys doing the imaging, the extra safety this grants (if
something like this or worse were to happen) I think is better than an OSD task sequence gone wild.
Thanks,
Mark

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

Service Pack for Proliant installing successfully but returning failure in OSD task sequence

Building bare metal servers with SCCM 2012 SP1 CU2 OSD and running into an issue with HPs where they attempt to install the Service Pack for Proliant 2013.02.0. I am using a package with a program. Here is the program command line:
Hpsum.exe /use_latest /allow_non_bundle_components /current_credential /silent
The application installs successfully but there is a distinct delay and then errors thrown that fails the TS. Setting 'continue on error' is a work around but not what I want to have in the production environment. How can I get around this issue?
This is the same exact package and program that ran perfectly fine in SCCM 2007, but we are seeing this as a new issue since the migration to SCCM 2012.
I'd like to solve this issue as well as get rid of the "Waiting for job status notification....InstallSoftware"
Any suggestions?
SMSTS.LOG
Invoking Execution Manager to install software InstallSoftware
12/3/2013 9:59:49 AM 1568 (0x0620)
Installing software for PackageID='WCD002D2' ProgramID='Silent install' AdvertID='WC120008' has started, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Waiting for installation job to complete.. InstallSoftware
12/3/2013 9:59:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:20 AM 1568 (0x0620)
Launching command shell. OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Windows station: WinSta0 OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Desk"Apple-tab-span" style="white-space:pre;"> OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
executing command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
executed command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:50 AM 1568 (0x0620)
CompleteExecution received InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
CompleteExecution processed InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
Received job completion notification from Execution Manager
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation completed with exit code 0x80070001
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation failed with error (0x80070001)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'=''
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
GetExecRequestMgrInterface successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Releasing job request, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Releasing of Job Request successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
CompleteJob successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
reference count 1 for the source D:\_SMSTaskSequence\Packages\WCD002D2 before releasing
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Released the resolved source D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
pInstall->Install(sPackageID, sProgramName), HRESULT=80070001 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Install Software failed, hr=0x80070001 InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Process completed with exit code 2147942401
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the action: HP Server Pack for ProLiant 2013.02.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
MP server http://MP_server.company.com. Ports 80,443. CRL=false.
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Setting authenticator TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set authenticator in transport TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Sending StatusMessage TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting message signatures. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting the authenticator. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
CLibSMSMessageWinHttpTransport::Send: URL: MP_server.company.com:80 CCM_POST /ccm_system/request
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Request was succesful. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionRetCode=-2147024895
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionSucceeded=false
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Clear local default environment TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Let the parent group (System Management Install) decides whether to continue execution
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
The execution of the group (System Management Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the last action: HP Server Pack for ProLiant 2013.02. Execution of task sequence failed.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)

Hello Guys!
HP ProLiant Support Pack / Service Pack uses different Exit Codes, due to that this software support other operating systems than Windows. Therefore HP has standardized to use other Exit Codes, which Windows Detect as failures.
HPSum Exit Codes:
ExitCode 1 = "Installation Successful"
ExitCode 2 = "Installation Successful, but a reboot is required"
ExitCode 3 = "Installation was canceled, or no components were updated"
EcitCode 9009 = "Installation did not complete. Check the path and make sure that the Installation exists at the specified location"
HP recommends to use following Batch File to workaround this issue for SCCM:
=======================START_BatchFile=============================
:Init
@Echo Off
Cls
:Main
Echo HP Proliant Service Pack Setup
Echo Source : %~dp0
Echo ===============================================================================
Echo Installing the HP Proliant Service Pack Setup
Echo Command: "%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
"%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
:CheckForErrors
Echo HP Proliant Service Pack Stauts:
If "%errorlevel%"=="0" (
     Echo *******************************************************************************
Echo                            INSTALLATION FAILED!
Echo *******************************************************************************
exit 1
If "%errorlevel%"=="1" (
     Echo Installation Successful!
     exit 0
If "%errorlevel%"=="2" (
     Echo Installation Successful, but a reboot is required.
     exit 3010
If "%errorlevel%"=="3" (
     Echo Installation was canceled, or no components were updated
     exit 0
If "%errorlevel%"=="9009" (
     Echo Installation did not complete. Check the path and make sure that the
Echo Installation exists at the specified location:
Echo Path: %~dp0
Exit 1
:End
Echo An unknown status code was returned from the PSP.
Echo This status code is [%errorlevel%]. This will be treated as a success,
Echo but please check the installation to make sure it completedly properly!
Exit 0
=======================STOP_BatchFile=============================
God Luck!
Best Regards Anders Horgen

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

OSD Task Sequence fails with "There are no task sequences available for this computer"

Let me preface this by saying that I have read at least 100 forum posts with people having similar issues. However, none of the solutions in those
posts have worked for me.
The Problem: SCCM 2012 R2 will not image unknown computers.
The task sequence gives the error "There are no task sequences available for this computer." As soon as that error occurs, SCCM places an Unknown entry into the All Systems collection. I have been imaging unknown computers, without fail, for
4 months and no environmental changes have been made. NOTE: I am using USB media, not PXE.
What I've Tried:
Checked for duplicate SMSBIOS GUIDS in the console, none.
Checked for duplicate MAC Addresses in the console, none.
Checked for expired certificates, none.
Recreated Boot Media, twice.
Deleted the Unknown entry and retried, SCCM just recreates the Unknown entry.
Deleted all of my task sequence deployments, and then redeployed them each to All Systems (Only Boot Media and PXE) and to Unknown Systems (Only Boot Media and PXE)
I have also ran the following in the SQL Server Management Studio;
SELECT
* FROM
ResPolicyMap WHERE
machineid = 0 and
PADBID IN
(SELECT
PADBID FROM PolicyAssignment
WHERE BodyHash
IS NULL)
No result
Select
* From
vMacAddresses Where
MacAddresses = '00:00:00:00:00:00'
This displays an entry for every time that I have tried to image the unknown machine attached to the MAC Address with a different ItemKey and SMS_Unique_Identifier for each entry.
Added the machine manually using Import Computer Information, immediately recognized the Task Sequences that I have advertised to the All Systems collection.
Any and all assistance is welcome, I am going on the third straight day of dead ends. Below I have tried my best to post the entire SMSTS Log;

LOGGING: Finalize process ID set to 744
==============================[ TSBootShell.exe ]==============================
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Debug shell is enabled
Waiting for PNP initialization...
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM
WinPE boot path: C:\SOURCES\BOOT.WIM
Booted from removable device
Found config path C:\
Booting from removable media, not restoring bootloaders on hard drive
C:\WinPE does not exist.
C:\_SmsTsWinPE\WinPE does not exist.
Executing command line: wpeinit.exe -winpe
The command completed successfully.
Starting DNS client service.
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
The command completed successfully.
==============================[ TSMBootStrap.exe ]==============================
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL'
Current OS version is 6.2.9200.0
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH
Failed to open PXE registry key. Not a PXE boot.
Media Root = C:\
WinPE boot type: 'Ramdisk:SourceIdentified'
Failed to find the source drive where WinPE was booted from
Executing from Media in WinPE
Verifying Media Layout.
MediaType = BootMedia
PasswordRequired = false
Found network adapter "Intel(R) Ethernet Connection I217-LM" with IP Address XXX.XX.XXX.XXX.
Running Wizard in Interactive mode
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Activating Welcome Page.
Loading bitmap
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Spawned thread 1008 to download policy.
Entering TSMediaWizardControl::GetPolicy.
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}
Setting LogMaxSize to 1000000
Setting LogMaxHistory to 1
Setting LogLevel to 0
Setting LogEnabled to 1
Setting LogDebug to 1
UEFI: false
Loading variables from the Task Sequencing Removable Media.
Loading Media Variables from "C:\sms\data\variables.dat"
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Setting SMSTSMP TS environment variable
Setting _SMSMediaGuid TS environment variable
Setting _SMSTSBootMediaPackageID TS environment variable
Setting _SMSTSBootMediaSourceVersion TS environment variable
Setting _SMSTSBrandingTitle TS environment variable
Setting _SMSTSCertSelection TS environment variable
Setting _SMSTSCertStoreName TS environment variable
Setting _SMSTSDiskLabel1 TS environment variable
Setting _SMSTSHTTPPort TS environment variable
Setting _SMSTSHTTPSPort TS environment variable
Setting _SMSTSIISSSLState TS environment variable
Setting _SMSTSMediaCreatedOnCAS TS environment variable
Setting _SMSTSMediaPFX TS environment variable
Setting _SMSTSMediaSetID TS environment variable
Setting _SMSTSMediaType TS environment variable
Setting _SMSTSPublicRootKey TS environment variable
Setting _SMSTSRootCACerts TS environment variable
Setting _SMSTSSiteCode TS environment variable
Setting _SMSTSSiteSigningCertificate TS environment variable
Setting _SMSTSStandAloneMedia TS environment variable
Setting _SMSTSSupportUnknownMachines TS environment variable
Setting _SMSTSTimezone TS environment variable
Setting _SMSTSUseFirstCert TS environment variable
Setting _SMSTSx64UnknownMachineGUID TS environment variable
Setting _SMSTSx86UnknownMachineGUID TS environment variable
Root CA Public Certs=
Missing root CA environment variable from variables file
Support Unknown Machines: 1
Custom hook from X:\\TSConfig.INI is
No hook is found to be executed before downloading policy
Authenticator from the environment is empty.
Need to create Authenticator Info using PFX
Initialized CStringStream object with string: 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A;2014-07-16T18:15:39Z.
Set media certificate in transport
Set authenticator in transport
CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXX.XXXXXX.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA
Request was successful.
Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider
Default CSP Type is 24
New settings:
site=XXX,XXX, MP=http://XXXX.XXXX.com, ports: http=80,https=443
certificates are received from MP.
Unknown machine GUIDs: 774b17a2-6eeb-44bc-9c94-ce9081f5fe4c 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
MP specific X86 unknown machine GUID is received at run time
MP specific X64 unknown machine GUID is received at run time
Getting MP time information
Set authenticator in transport
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 406, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Current time: 2014-07-16 18:15:39.787 TZ:Pacific Standard Time Bias:0480
Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0
Adjusting the system time: -14400.551 seconds
Time zone info set to: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
New time: 2014-07-16 14:15:39.235
Current time: 2014-07-16 14:15:39.231 TZ: Bias:0300
Downloading policy from http://XXXX.XXXX.com.
Initializing HTTP transport.
Setting URL = http://XXXX.XXXX.com.
Setting Ports = 80,443.
Setting CRL = false.
Setting Server Certificates.
Set authenticator in transport
Setting Media Certificate.
Preparing Client Identity Request.
Setting transport.
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Setting site code = XXX.
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.
Setting SMBIOS GUID = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Adding MAC Address XX:XX:XX:XX:XX:XX.
Executing Client Identity Request.
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 415, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Client GUID = , Netbios name = , State = Known
Using unknown machine GUID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE
Hash computed from CSP: Microsoft Enhanced RSA and AES Cryptographic Provider, AlgID: 32772, HashSize: 20
Computed HardwareID=2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Hardware ID: 2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Preparing the Client DDR Message
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Sending the Client DDR message.
Sending Report
<Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:26717327-194f-4cd6-90ba-309998c058f2</ClientID><ClientVersion>5.00.0000.0000</ClientVersion><NetBIOSName>Unknown</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID></Machine></Identification><ReportDetails><ReportContent>Inventory
Data</ReportContent><ReportType>Full</ReportType><Date>20140716141539.000000+000</Date><Version>1.0</Version><Format>1.1</Format></ReportDetails><InventoryAction ActionType="Predefined"><InventoryActionID>{00000000-0000-0000-0000-000000000003}</InventoryActionID><Description>Discovery</Description><InventoryAc
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
Submitted new client identity: GUID:26717327-194f-4cd6-90ba-309998c058f2
Preparing Policy Assignment Request.
Setting transport.
Setting site code = XXX.
Setting client ID = 74f16942-dd75-437f-8c4b-2a5de4d0e5e5.
Setting site signing Certificate.
Setting SiteSigningCertificateContext
Executing Policy Assignment Request.
Sending RequestAssignments
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 274, uncompressed size 662.
Request client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Response client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Retrieving Policy Assignments:
Successfully read 0 policy assignments.
Retrieving collection variable policy.
Found 0 collection variables.
Retrieving machine variable policy.
Found 0 machine variables.
Setting collection variables in the task sequencing environment.
Setting machine variables in the task sequencing environment.
Exiting TSMediaWizardControl::GetPolicy.
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
No assigned task sequence.
Setting wizard error: There are no task sequences available for this computer.
Skipping Confirmation Page.
Skipping Task Sequence Selection Page.
Skipping Variables Selection Page.
Skipping Resolve Progress Page.
Activating Finish Page.
Loading bitmap
Executing command line: X:\windows\system32\cmd.exe /k
The command completed successfully.
Successfully launched command shell.

Does 2012 OSD get around requirements to get to the MP during the task sequence?

Currently right now I am working in an environment where we are on SCCM 2007, but will be going to 2012 next year. We are in the process of trying to make it so we can build on a secure network that cannot route to any other network. I am prepared to put
a DP out on this same network, but the problem I am running into is that during the task sequence starting, it downloads the task sequence from the MP, not the DP as it is not associated with the package. The MP is not on the same un-routable network. We will
need to have about 6 or so of these, so we do not want to setup 6 MP because now you are looking at not only 6 primary site licenses, but 6 SQL installs (Our environment will not let me get away with doing SQL express for support reasons) which adds up quickly.
Below is a link to exactly what I am speaking about:
http://blogs.technet.com/b/configurationmgr/archive/2009/04/16/configmgr-2007-primary-site-mp-is-used-for-the-task-sequence-even-when-deploying-osd-images-to-secondary-sites.aspx
What I am wondering is if SCCM 2012 OSD was structured differently in a way that access to the MP is no longer necessary during the task sequence process (say for example the task sequence xml is replicated to DPs too)?
Thanks.

My apologizes. I was meaning to say Primary, Secondary Sites. Not MPs. I brought this up to give reference to idea about the boundaries that I am going to have to use to prevent these clients from contacting DPs they they can't route to.
The idea behind getting off the build network and onto a prod is that security requirements from my companies Infosec require that we limit the amount of traffic on production networks. The idea is that the server be built on the build network, disconnected
and brought into prod. The whole time the MP would be the same, but the DP would switch based on the prod network they were brought into as DP will reside in these prod networks which will get flipped over by the boundary for the prod subnets. Once on the
prod network they would be able to contact the MP.
I would love to do stand-alone media, this is one of the first roads I started looking down as I have done them in the past for offline builds, but I need the machine to auto assign its hostname from a external servers that will script the build. The build
process we are trying to put into place will be started from an external website. My first thought was to have it add the machines to a collection and add a variable that would be turned into a task sequence variable during the TS and use it for the hostname
when it attempt to apply the Windows settings. The only way I think I could get this to work would be to write a script that is executed during the task sequence that would match the MAC address of the machine and assign the hostname by calling on another
share that is written to by the external website with the MAC and hostnames. The only problem that I cannot get around is that this build process needs to be fully automated and this is for both virtual and physical. I have no problems mounting a stand-alone
build ISO using a script for VMWare, but the problem starts when I look at the physical and limitations of scripting for both iLo and iDRAC for performing this step. iLo can be done, but iDRAC is limited.
As for a reverse-proxy I will not be able to look at that. They have specific requirements against using reverse-proxies in only specific situations and this it not allowed. I got turned down on this one. This requirement is created by a federal regulation
my company has to follow.

Client in OSD Task Sequence

Hello, I am deploying Windows 7 with a Task Sequence. And all of my applications and client get installed, the only thing I am having issues with is getting the client to check in. We have waited over 12 hours to see if it will finally check
in and still nothing happens. Here is the status of the workstation and the Task Sequence.
Workstation getting upgraded:
Is a fully functional windows 7 machine with client working. Name = LWS-123456
Push the the image with PXE, boots and installs everything without errors. Name = LWS-123456
Task Sequence:
Restart in Windows PE
Partition Disk
Apply Operating System
Apply Windows Settings
Apply Network Settings
Setup Windows and Configuration Manager
Disable IPv6
Standby Timeout None
Disk Timeout None
Display Timeout 180
Disable Hibernate
Disable Firewall
Disable UAC
Restart Computer
Create IT Folder
Install Office 2013
Install Browsers
Install Adobe
Clean up Desktop Links
Restart Computer
Any Ideas on where I am going wrong or what I am missing?
Thank you in advance.

jheinikel - I will have to keep that in mind, I think I have found the issue. I will have to wait till I get back into work tomorrow to test it out and keep you all posted.
Jason - you are on the right path.
Here is the link I had found and I had my Restarts in my TS not set to boot to OS they were booting to WinPE.
http://www.windows-noob.com/forums/index.php?/topic/5618-damaged-client-after-setup-no-self-singed-cert/
This error is common because the "Restart Computer" task defaults to restarting into the WinPE boot image instead
of the full Windows OS. The "Restart Computer" task option "The boot image assigned to this task sequence" will cause it to
reboot into WinPE, while the option "The currently installed default operating system" will cause it to reboot into the full Windows OS being deployed by the Task Sequence. If the option is
not specifically switched from the default setting when the "Restart Computer" task is added to the Task Sequence, then the issue will occur.
I will keep you posted if it works tomorrow or not.
Thank you again.

OSD: where is a task sequence in full os stored?

Similar Messages

Maybe you are looking for