MDT 2013 Task Sequence return to command prompt

Hey All,
I created a fresh MDT 2013 share on a 2008 R2 machine that also holds the WDS for PXE.
Right after it applies DISM, it restarts back to a command prompt, my logs don't report any errors. When I type exit, the machine reboots and the task sequence continues as normal. Here is the peice in my dynamic log where it stops logging. Last line is
where it stops and I type exit.
ZTIdrivers processing completed successfully.
ZTIdrivers 11/3/2014 11:11:59 AM
0 (0x0000)
Event 41001 sent: ZTIdrivers processing completed successfully.
ZTIdrivers 11/3/2014 11:11:59 AM
0 (0x0000)
Will boot into Windows PE architecture x64 to match OS being deployed.
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
OSDTargetDriveCache was determined earlier : C:
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
Property OSDTargetDriveCache is now = C: ZTIWinRE
11/3/2014 11:12:00 AM 0 (0x0000)
Property OSDisk is now = C: ZTIWinRE
11/3/2014 11:12:00 AM 0 (0x0000)
WinRE is not enabled, Skip. ZTIWinRE
11/3/2014 11:12:00 AM 0 (0x0000)
ZTIWinRE processing completed successfully.
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
Event 41001 sent: ZTIWinRE processing completed successfully.
ZTIWinRE 11/3/2014 11:12:00 AM
0 (0x0000)
Property PHASE is now = STATERESTORE ZTINextPhase
11/3/2014 11:12:00 AM 0 (0x0000)
ZTINextPhase COMPLETED. Return Value = 0
ZTINextPhase 11/3/2014 11:12:00 AM
0 (0x0000)
ZTINextPhase processing completed successfully.
ZTINextPhase 11/3/2014 11:12:00 AM
0 (0x0000)
Event 41001 sent: ZTINextPhase processing completed successfully.
ZTINextPhase 11/3/2014 11:12:01 AM
0 (0x0000)
A little further along I noticed it changed the state to dirty. But I don't think that's related. Could be wrong.
-G

While in Windows PE, the cmd.exe window will appear in one of two scenarios:
1. The user pressed the F8 key.
or
2. Litetouch.wsf returned some kind of failure during processing. This is weird.
Under what instances would the Litetouch.wsf crash (fail)? Well, the most common scenario is that there are some mixmatched source files in MDT. Updating the deployment share could fix the problem.
The only other way to know for sure is to run the program in a debugging mode. When you first boot up to WinPE, instead of starting the deployment wizard, when you are at the welcome wizard, break out into the cmd.exe prompt (not by pressing F8). Then
run the command:
cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture
At the end of the script we should see an error with a line number.
If we don't see an error then something else is going on.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

SCCM 2012 R2 and MDT 2013 Task Sequence Bugs

Any links that list issues with the default MDT 2013 deploy task sequence: UEFI, local administrator password, Machine OU settings, OS installation partition and computer replace scenario.

Hi,
If you want to file bugs or feature requests, you'll need to go to the MDT and ConfigMgr connect site:
https://connect.microsoft.com/ConfigurationManagervnext/Feedback
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Setting the Administrator password on a MDT Server Task Sequence

I've created a SCCM 2012 R2 CU3 MDT 2013 task sequence using the Server Task Sequence template to deploy Windows Server 2012 R2. I'm not doing a capture but just using the .wim file from the source DVD. The problem I'm having is setting the local admin
password in Apply Windows Settings. It's not taking the password that I've assigned it. I'm not sure how many others have created a Server Task Sequence or not but I'd be interested to know how to get around this problem.

Sorry, in Apply Windows Settings I've selected "Enable the account and specify the local administrator password" and entered the local password there. When the system is imaged and I try to log in locally it gives the the error "The user name
or password is incorrect. Try again." error.
I have checked that the local administrator account is enabled so I know it's not that and I've tried multiple times. I even took one of our client task sequences that I know works, made a copy of it, and added the Server 2012 R2 install to it and get the
same result.

SCCM 2012 SP1 and MDT 2012 Task Sequence Templates, MDT File/Settings Packages

We're setting up SCCM 2012 integrated with MDT 2012 for our OSD. My main issue is finding actual reference material for the MDT task sequence templates when integrated with SCCM. The MDT documentation has a lot of information on variables and task sequences
outside of SCCM integration.
One thing I'd love to find information on is what's actually going on during an MDT Client Task Sequence template. I found this http://social.technet.microsoft.com/Forums/en-US/645a77b2-5be6-431d-818c-57d24b1435cc/understanding-mdt-task-sequence?forum=configmgrosd but
it doesn't delve into the kind of detail I'm looking for. I can dig up information through the MDT reference material on some things, but I just can't find anything out there that actually walks you through an SCCM/MDT task sequence template. For instance,
under State Restore what is being referenced in Install Software with base variable name PACKAGES, vs Install Applications and base variable name COALESCED APPS. And, where are you supposed to put these applications? That's just a specific example, I'm hoping
to find some kind of walkthrough.
Two things I'm hazy on are the MDT packages. What exactly are the MDT Settings Package, and the MDT Files Package? What are they used for? What benefits do you get out of using them? And, how exactly do you use them? I know one of them has something to do
with customsettings.ini, but what's the point of using SCCM with MDT if you still have to muck around in the customsettings.ini file?
Either way, it seems like there are a lot of references to SCCM task sequences, and a lot of references to MDT task sequences. But, not together. Which is a bit annoying since the MDT-integrated task sequence templates are very obviously different than either
SCCM or MDT by itself. Any help would be appreciated, even just information on where to look. Maybe I'm just really bad at finding reference material for SCCM/MDT. Thanks.

When MDT integrated with SCCM, We need the following MDT components to be created:
MDT Boot image
MDT Toolkit Files
MDT Settings
The MDT boot image (for example) gives you extra abilities over the standard ConfigMgr boot image such as the ability to display a HTA Refer here:
http://www.windows-noob.com/forums/index.php?/forum/98-frontends-and-web-services/
MDT Files once created, you will find UDIWizard_Config.Xml file in which you can start User driven Installation OSD using UDI designer.
Refer these links for better understanding:
http://www.windows-noob.com/forums/index.php?/topic/5131-using-sccm-2012-rc-in-a-lab-part-16-integrating-mdt-2012-rc1-with-configuration-manager-2012/
http://www.windows-noob.com/forums/index.php?/topic/5221-using-sccm-2012-rc-in-a-lab-part-17-using-mdt-2012-rc1-within-configuration-manager-2012/
http://www.windows-noob.com/forums/index.php?/topic/5250-using-sccm-2012-rc-in-a-lab-part-18-deploying-a-udi-client-task-sequence-with-mdt-2012-rc1-integrated-in-configuration-manager-2012/
Thanks, Prabha G
Thanks for the quick reply. But, what about the MDT Settings Package? Also, both have a pretty big folder structure for each package. Surely it does more than just provide a couple xml and ini files? I'm not looking for anyone to spoon-feed me the information,
but at least a pointer in the right direction for finding the reference material. It seems for SCCM/MDT integration you have to go all over the place finding scraps of information to put together.
Also, any info on the SCCM/MDT task sequence templates? Thanks.

OSD SCCM 2012 R2: MDT integrated task sequence central logging not working

Hi,
Please advise on making dynamic logging work for SCCM 2012 R2 MDT integrated tasks sequence.
This is what I specified in customsettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
; Copy Logs if en error occurs or when deployment is successfully completed
SLSHARE=\\sccmserver\OSD\Logs\MDT
; Enable Dynamig Logging
SLSHAREDynamicLogging=\\\sccmserver\OSD\Logs\MDTDynLogs\%OSDComputername%
UserID=administrator
UserDomain=ourdomain
UserPassword=ourpassword
Jan Hoedt

I keep on getting access denied though when I connect in a dosprompt with the credentials I can make a connection.
Mapping server share: \\ourdomain.com\share   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 5 seconds.   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 10 seconds.   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 15 seconds.   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 20 seconds.   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:09:04   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:09:05   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 25 seconds.   ZTIValidate   4/03/2014 0:09:05   0 (0x0000)
ERROR - Unable to map a network drive to \\ourdomain.com\share.   ZTIValidate   4/03/2014 0:09:30   0 (0x0000)
An invalid SLShareDynamicLogging value of \\ourdomain.com\share\PackageSources\OSD\Logs\MDT-DynLogs\computername was specified.   ZTIValidate   4/03/2014 0:09:30   0 (0x0000)
Jan Hoedt

MDT 2013 Windows 8.1 Deployment Starts Prompting For Administrator Login In Middle Of Task Sequence

I have a 8.1 deployment task sequence that automatically logs into the administrator account until about half way through the deployment.
It actually looks like it logs in for a second and then dumps back out to the login prompt.
After this reboot, the problem starts. When I log in manually, I see it is at the installing the Java application step. What could cause this?

Yes, it's possible that the scripts to boot to desktop or the script to remove apps are causing this, but other people use these settings in deployments and didn't mention this as a side effect.
This reg file is supposed to set the Start Menu background to match the desktop wallpaper and set IE to use desktop version, but does not seem to work.
regedit.exe /s 81settings.reg
Windows Registry Editor Version 5.00
[HKEY_USERS\CUSTOM\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent]
"MotionAccentId_v1.00"=dword:000000db
[HKEY_USERS\CUSTOM\Software\Policies\Microsoft\Windows\EdgeUI]
"DisableHelpSticker"=dword:00000001
[HKEY_USERS\CUSTOM\Software\Microsoft\Internet Explorer\Main]
"ApplicationTileImmersiveActivation"=dword:00000000
"AssociationActivationMode"=dword:00000002
================================================
powershell.exe -Command "set-ExecutionPolicy Unrestricted -Force; cpi '%DEPLOYROOT%\Applications\Remove Windows 8.1 Modern Applications\RemoveWindows8Apps.ps1' -destination c:\; c:\RemoveWindows8Apps.ps1; ri c:\*.ps1 -Force; set-ExecutionPolicy Restricted
-Force"
<#
Purpose: Remove built in apps specified in list
Pre-Reqs: Windows 8.1
#>
# Main Routine
# Get log path. Will log to Task Sequence log folder if the script is running in a Task Sequence
# Otherwise log to \windows\temp
try
$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
$logPath = $tsenv.Value("LogPath")
catch
Write-Host "This script is not running in a task sequence"
$logPath = $env:windir + "\temp"
$logFile = "$logPath\$($myInvocation.MyCommand).log"
# Start logging
Start-Transcript $logFile
Write-Host "Logging to $logFile"
# List of Applications that will be removed
$AppsList = "microsoft.windowscommunicationsapps","Microsoft.BingFinance","Microsoft.BingMaps",`
"Microsoft.BingWeather","Microsoft.ZuneVideo","Microsoft.ZuneMusic","Microsoft.Media.PlayReadyClient.2",`
"Microsoft.XboxLIVEGames","Microsoft.HelpAndTips","Microsoft.BingSports",`
"Microsoft.BingNews","Microsoft.BingFoodAndDrink","Microsoft.BingTravel","Microsoft.WindowsReadingList",`
"Microsoft.BingHealthAndFitness","Microsoft.WindowsAlarms","Microsoft.Reader","Microsoft.WindowsCalculator",`
"Microsoft.WindowsScan","Microsoft.WindowsSoundRecorder","Microsoft.SkypeApp"
ForEach ($App in $AppsList)
$Packages = Get-AppxPackage | Where-Object {$_.Name -eq $App}
if ($Packages -ne $null)
Write-Host "Removing Appx Package: $App"
foreach ($Package in $Packages)
Remove-AppxPackage -package $Package.PackageFullName
else
Write-Host "Unable to find package: $App"
$ProvisionedPackage = Get-AppxProvisionedPackage -online | Where-Object {$_.displayName -eq $App}
if ($ProvisionedPackage -ne $null)
Write-Host "Removing Appx Provisioned Package: $App"
remove-AppxProvisionedPackage -online -packagename $ProvisionedPackage.PackageName
else
Write-Host "Unable to find provisioned package: $App"
# Stop logging
====================================================
Install java and turn off updates.
Start /wait jre-8u25-windows-i586.exe INSTALL_SILENT=1 STATIC=0 AUTO_UPDATE=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H WEB_ANALYTICS=0 EULA=0 REBOOT=0
regedit.exe /s disableupdate.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy]
"EnableJavaUpdate"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy]
"EnableJavaUpdate"=dword:00000000

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

MDT Capture Task Sequence not working correctly

Hello All<o:p></o:p>
I need some help to tell me what I am doing wrong. I am using Hyper V and trying to capture a image of Windows 7 x64. From within the OS I run the
Litetouch.wsf from the deployment share. I get the normal MDT Wizard windows. I pick my capture task sequence and everything looks like it is running fine sys prep happens and I but back into windows PE I start to process the rules again and I am taken
back to the Select task sequence screen in WinPE. If I pick the capture task sequence again the deployment fails. <o:p></o:p>

(posting for anyone else that found this page, this was my fix)
I had the same problem as the initial poster apart from what I wanted to capture was a 'real' pc. The reason my 'capture' task sequence wasn't booting into WinPE from the local disk and continuing on with the capture was because the local disk was
being wiped when the boot wim - LiteTouchPE_x64.wim, was being run.
A few weeks prior to me wanting to capture a PC I'd been working out how to stop the occasional error when you boot a PC off the WDS server - “The Task Sequence Has Been Suspended”. I was particularly interested in stopping this error as I want to
remotely start a Win7 install on a PC, this error would stop the install happening but I wouldn't see this error and end up visiting the PC only to find the install hadn't really started. After googling around, I found a page that explains how to edit
the unattend.xml file in the boot image - LiteTouchPE_x64.wim, in the xml file to run the command wscript.exe X:\Deploy\Scripts\LTICleanup.wsf. Sounded good so I done what the page said (myitforum.com/cs2/blogs/cnackers/archive/2010/10/20/microsoft-deployment-toolkit-lite-touch-lti-the-task-sequence-has-been-suspended.aspx)
but it didn't stop the message appearing. In the end I fixed this problem by adding the line 'SkipWizard=YES' in my customsettings.ini file. I didn't remove the LTICleanup.wsf from unattend.xml, it didn't seem to do any harm, that was until I tried
to capture a PC.
When I ran though my 'sysprep and capture' task sequence, the PC would sysprep ok and then reboot, ready to capture it. Instead of the 'capturing a WIM file' sequence I was expecting to see, I, like the original posted got shown the list of available
task sequences window. If you try again to run the capture sequence, it will fail as this has to be started in a running Windows environment, not in WinPE. After several hours wondering what is going wrong, I dawned on me what was going wrong,
the LTICleanup.wsf was being run when the boot image was being run and wiping my disk, a disk that was ready to run an existing task sequence, the capture sequence, no wonder it was failing. Removing the LTICleanup.wsf command from within unattend.xml
or rebuilding the boot image (by running 'Update Deployment Share' within MDT 2010) fixed the problem, the capture now worked.
Hopefully this will help someone else like me who was wondering what was going wrong with a capture.

What determines whether an application gets a green check or a yellow warning sign in the deployment summary screen when using an MDT/UDI task sequence?

I am trying to get Office 2010 to install using a UDI task sequence, and it IS installing, but it has a yellow exclamation point next to it at the summary screen after the task sequence completes, as does another app I am trying to install.
The apps that use an .MSI are fine, and get the green check, but the two apps that use .exe for their installers get the yellow warning sign. I assume this has to do with exit codes or detection rules, but I am very new to SCCM (using 2012 and MDT
2012 Update 1), so I need some help.
Thank you!
EDIT: This probably has to do with the fact that SuccessOrFailureCode being blank. I have been pouring over .vbs scripts and logs, but they all seem to indicate that my application installs just fine, with an exit code of 0. Where does this screen
get the SuccessOrFailureCode?
Like
This
Quote
MultiQuote
Edit

I have some updated info on this problem.
I am trying to install Symantec Endpoint Protection with a custom wrapped .EXE file, and I have created detection rules for the install.
According to AppEnforce.log, SEP is installing and returning an Exit code of '1', and that is being handled with my custom return code handling, which I've defined as a 'success'. However, the deployment summary is still showing a yellow exclamation point
next to the SEP install, and the SuccessOrFailureCode is blank.
Why isn't the SuccessOrFailureCode equal to '1'? Where is the disconnect between the AppEnforce.log and the deployment summary.

MDT 2012 - Task Sequence Not Completing

I'm a complete novice with MDT 2012, but I have had pretty good luck getting a deployment for Server 2008 R2.
I have a reference system, and I do a very vanilla sysprep and capture using the template task sequence with no changes.
My deployment has a few app installs and other configuration items, but nothing too exotic.
My problem is this: during deployment, after applying the system from WinPE, I perform the final reboot. At this point, the expected action is for an autologon to take place, and for the local Administrator account to run c:\Litetouch.vbs, which does some final
cleanup and a few tasks that require the target system to be running.
This isn't happening on my system. And a look at the registry shows that the autologon stuff has not been set up, so it won't ever happen. It's not a matter of having an incorrect account, or a count of 0, none of the autologon registry keys are even present.
In trying to solve this (I believe it worked when I first started!) I've stripped down my deployment to a pair of task sequences that have no customization
at all in either the capture or the deployment task sequences, and still no luck. So I believe that something has changed in my reference system - but I unfortunately can't roll back.
What is driving me a little nuts is that I can't tell when that autologon information is supposed to be inserted in the registry. There is code in Litetouch.wsf that appears to do it, in function PopulateAutoAdminLogon, but I can't come up with a scenario in
which this function gets called. I am guessing that perhaps sysprep does it when creating the WIM, but I can't seem to find good information on that.
I've done a lot of searching on this, and unfortunately the answer space is cluttered with people who have a similar sounding but completely different problem - they want their deployed system to do an autologon, and after deployment their system comes up with
the logon screen instead of doing what they want. I've seen a few people post similar problems to mine, but nobody has received an answer. This one is pretty close, it suggest I might have a group policy item that disables the local admin account, but I don't
think it hits the mark for me.
http://social.technet.microsoft.com/Forums/en-US/mdt/thread/e625aa88-2415-4a2a-9e79-ac6b37119c27
So in a nutshell: when deploying a system using MDT 2012, at what point do the autologon items from unattend.xml stuffed into the registry for use after state restore/reboot in the task sequence? And what can go wrong with that?
- Mark

Same here, can't find any solution though. Did you ever work it out?

MDT 2010 Task Sequence Issue

Hi,
We are facing issue with MDT build.
We have added following new version of application and disable the old version of application in task sequence.
but when we rebuild the system its still installing old version of below applications.
Application Name
Latest Version
Old Version
Cisco AnyConnect
3.1
2.4.0202
Swivel Secure ltd Pinsafe Taskbar 1.4
1.4
1.3.2
If any one facing same issue with MDT build please provide the solution for the same.
Thanks

Thanks for the answer.
We are using MDT 2010 and its a production environment.
We are not able to do any changes in customsettings.ini.
but when add application in TS that time applications.xml and app ApplicationGroups.xml file
was change on this date.

Shell scipt does return to command prompt

I'm trying to run a sql script from the command line. I need the sql to run and then exit to the command prompt. current using
sqlplus -s un/pw@db @fn.sql param1 param2
Where fn.sql is something like
select * from &1
when run, the sql script and parameters are loaded into the buffer but not executed. If I hit / the script executes, then I have to type exit to return to the program. I've tried adding additional /'s and ; to get the script to execute, with no luck. I thought that if used the syntax above, the script would be loaded, executed, and sqlplus exited. Is this not correct? Or do I have a setting set wrong that is preventing the sql from being executed immediately. I need the script to spool to stdout transparently.

Yes, you need to include the exit in your script.
Are you sure that you have no spaces around the / character, because it works fine for me:
/home/oracle/dba/script>cat t.sql
SELECT * FROM &1
exit;
/home/oracle/dba/script>sqlplus -s / @t.sql dual
old 1: SELECT * FROM &1
new 1: SELECT * FROM dual
D
X

MDT 2012, Task Sequence Comments, can I change to have line breaks?

I added comments to a few Task Sequences. They all run into each other, I'd like to be able to type a sentence, press enter, then put another, but when I do this, that's not how it looks in LiteTouch.vbs.

I wanted to do the same thing and could not come up with a nice way to do it. Ended up using the hidden character Alt+0160 to space it out. Looks good now but took some trial and error to get it all lined up.

Server 2012 R2 + MDT 2013 + WINLOAD.EXE error

Hi All,
After watching some videos on MDT 2013 integration with SCCM 2012 I have been testing some builds of Windows Server 2012 R2. The MDT 2013 integration is working well with Database look-ups providing the required rules for customsettings.ini. To coincide
with the tests I am using the MDT 2013 Server Task Sequence Template.
Unfortunately I am hitting an error whereby, when using the MDT Task Sequence the full Operating System fails to start with a:
\Windows\System32\Winload.exe, 0xC000000F, File is Missing or Corrupt
Note: This is happening when the full OS is starting up. This is not a WinPE startup issue.
When I use a non-MDT Task Sequence, i.e. a typical task sequence we use for OSD the build process works OK. We still have MDT database integration working in that Task Sequence however.
Some background info:
As per our normal process we are using a Windows Server 2012 R2 Capture image. The reference machine was build and capture using a partition scheme of (Partition 1 - 500MB + No Drive Letter + Hidden, Partition 2 - 100% of disk - Drive C:\)
This is a new SCCM 2012 R2 implementation and as such we installed CU3 as part of our build process. CU4 is yet to be applied.
Our WinPE Boot Images are WinPE 5 with a build number of 6.3.9600.16384
As we have an existing SCCM 2007 environment I am currently using USB Boot media to kick off the Task Sequence
We are only considering a "New Computer" build scenario. The MDT 2013 Task Sequence already detects that because the "_SMSTSinWinPE" = True.
In both Task sequences the Format and Partition step is as follows:
Disk 0
Standard(MBR)
BDEDrive (Primary) - 499MB, Marked Active with variable BDEDrive assigned
OSDisk (Primary) - 90GB variable OSDisk assigned
In both Task sequences the Apply Operating System step is as follows:
Using Captured Image
Apply operating system from a captured image (Image 2-2)
Apply image to Logical Drive (OSDisk)
In both Task sequences the Apply Data Image step is as follows:
Using Captured Image
Image 1-1 (from the same captured image as shown above)
Apply image to Logical Drive (BDEDrive)
What has been done so far:
Already eliminated driver packs as the problem occurs with and without them
Have monitored the build process (during WinPE that is) to determine what disks and partitions are in play at that stage. The 500MB BDE and 90GB OS Partitions are created as expected. The Apply OS and Apply Data Image steps are applying to the correct partitions.
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /fixmbr + bootrec /fixboot
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /rebuildbcd
I have tried toggling the "OSDPreserveDriveLetter" variable from True to False and back again. Based on my interpretation of the SCCM 2012 R2 + Windows Server 2012 drive letter issue this should be set to True so the capture image drive letters
are preserved.
I have disabled an UEFI Partitioning steps just as a precaution.
There is no Bitlocker steps involved yet.
I have trawled through the SMSTS.LOG. So far it looks OK to me:
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPEandFullOS TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: tsenv.exe "OSDPreserveDriveLetter=True" TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Finished with error code 0 TSEnv 18/02/15 8:09:49 AM 728 (0x02D8)
Process completed with exit code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully completed the action (Set Variable for Drive Letter) with the exit win32 code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
MP server https://SOMETHING24.SOMETHING. Ports 80,443. CRL=false. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting authenticator TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set authenticator in transport TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Sending StatusMessage TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting message signatures. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting the authenticator. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 CCM_POST /ccm_system_AltAuth/request TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
In SSL, but with no client cert TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Request was successful. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Clear local default environment TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Updated security on object D:\_SMSTaskSequence. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Save the current environment block TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully save execution state and environment to local hard disk TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing an instruction. Instruction name: Apply Operating System Image. Instruction pointer: 43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSCurrentActionName=Apply Operating System Image TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a local default variable OSDImageIndex TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing the command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPE TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set command line: "OSDApplyOS.exe" /image:S0200034,2 /target:D: /runfromnet:False ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Found run from net option: 0 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Not a data image ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ApplyOSRetry: ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
TSLaunchMode: UFD ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
'C:\' not a removable drive ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ exists and is a local hard drive. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ is using a valid file system. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Windows target partition is 0-2, driver letter is D:\ ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Verifying boot volume is NTFS. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The machine does not have a local client cache. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ResolveSource flags: 0x00000001 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
SMSTSPersistContent: . The content for package S0200034 will be persisted ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DownloadOnDemand flag is true. Attempting to download content locally for Package S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Locations: Multicast = 0, HTTP = 2, SMB = 0. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Package Flags: 0x01000000 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Multicast is not enabled for the package. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Trying https://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() entered ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Initializing HTTP transport. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Authenticator. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set authenticator in transport ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Media Certificate. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
WinHttp credentials set ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/S0200034 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
In SSL, but with no client cert ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Using thread token for request ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Request was successful. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:displayname><D:getlastmodified>Tue, 10 Feb 2015 04:56:27 GMT</D:getlastmodified><D:getcontentlength>6814100762</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
List of files to be downloaded ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
File: http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() successfully completed ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 0-2147483646 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 2147483647-4294967293 ApplyOperatingSystem 18/02/15 8:10:40 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 4294967294-6442450940 ApplyOperatingSystem 18/02/15 8:11:23 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 6442450941-6814100761 ApplyOperatingSystem 18/02/15 8:12:14 AM 724 (0x02D4)
Downloaded file from http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim to D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
VerifyContentHash: Hash algorithm is 32780 ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
Content successfully downloaded at D:\_SMSTaskSequence\Packages\S0200034. ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Opening image file D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Image file S0200034 version "2015-02-10" will be applied ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Starting to apply image 2 from dos-20150210.wim to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Wiping D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "D:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\System Volume Information for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\_SMSTaskSequence for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Calculating expected free space. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Reporting deletion progress. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Successfully wiped D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image 2 to volume D: ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
The command completed successfully. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully launched command shell. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully applied image to D:\ ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
System root for target OS is D:\Windows, System drive is D: ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
OS Version is 6.3 ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Successfully loaded a source BCD boot system ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
SetupNewOS: Loaded source boot system from target volume "D:\" ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
BootLoader::restore: D:\, C:\ ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Saving bcd store to D:\_SMSTaskSequence\ApplyBootSystem\boot\BCD ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Set command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Executing command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Process completed with exit code 0 ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:12 AM 724 (0x02D4)
Updating MountedDevices key in target system registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OS volume after boot is: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Reading '\DosDevices\D:' value under MountedDevices in WinPE registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272081-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272089-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208a-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208c-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\X:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272095-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272098-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\G:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\H:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\I:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27209b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\J:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720cf-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d5-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720e2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb2720f3-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb272126-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272139-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Data for value '\DosDevices\D:' matches data for value '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Done enumerating. Closing mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Closed mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Deleting MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Creating new MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Writing new values to MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Successfully updated MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Finished updating MountedDevices in target system registry (0x00000000) ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing up known name surrogate reparse points... ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\Documents and Settings] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\History] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Microsoft\Windows\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Cookies] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\use
The fact that our normal Task Sequence works OK eliminates the Capture image and the WinPE boot images. It must be something I have not configured or configured incorrectly in the MDT task sequence.
Any suggestions would be great.
NSutton

Hi,
If I were you, I would Streamline the MDT Task Sequence to find the root cause.
Moreover, please refer to the link below:
How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Fully automated Post OS Task Sequence

I'm trying to find a way to deploy a base OS VM from template and then call MDT to finish the config by running a post os task sequence. I'd like to be able to do this by either passing in paramaters or setting environment variables. I'd rather not get into
the mess of using a database or having lots of sections in the customsettings.ini because this will be pretty dynamic. Is there any way to call a specific task sequence after an OS is on a system without using a database or customsettings.ini?
Thanks,
Rich

You have missed this thread:
Is there any way to launch a specific task sequence from
the command prompt?
And then I quote Johan Arwidmark's answer:
"Sure, all rules can also be added to the commandline, they are just formatted a little bit differently ( : instead of = for the values) ...
\\MDT01\MDTProduction$\Scripts\litetouch.vbs /TaskSequenceID:<whateverID>
/ Johan"
So you can create a vbs or cmd that calls the task sequence
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT 2013 Task Sequence return to command prompt

Similar Messages

Maybe you are looking for