Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

I'm using MDT 2012 U1 to build and capture a Windows 7 x86 image for deployment with ConfigMgr 2012 SP1. I'm using the standard client task sequence in MDT.
The MDT task sequence consistently fails after the reboot in the "Postinstall" group. The install OS, Copy Scripts, Configure, Inject Drivers, Next Phase, and Restart Computer tasks all execute successfully, then the MDT-initiated reboot
completes successfully. There is nothing else helpful in the SMSTS.LOG, these are the last entries in the log:
Successfully complete the action (Restart Computer) with the exit win32 code 0
Sending status message
Executing in non SMS standalone mode. Ignoring send a task execution status message request
Set a global environment variable _SMSTSLastActionRetCode=0
Set a global environment variable _SMSTSLastActionSucceeded=true
Expand a string %_SMSTSMDataPath%\Logs
Deleting file without retrying
The error message on the reference computer says, "Windows has recovered from an unexpected shutdown" along with "An existing in-progress deployment was found but is not in an expected state. Would you like to ignore this in-progress
deployment and start a new one?"
I have found one post that suggested modifying customsettings.ini with HideShell=Yes, which I tried. It didn't help.
I am not sure why MDT thinks the reboot was unexpected? Has anybody run into this? What steps can I take to narrow down the problem?
Any help/suggestions are appreciated.
Thanks,
FP

Thanks for your reply Phil.
Setuperr.log is empty, zero bytes. Setupact.log looks good to me, it has these entries at the end:
OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [Image_State_Complete]
OOBELdr.exe exiting with code [0x0]...
Process exited with exit code [0x0]
c:\windows\panther\SetupInfo succeeded.
c:\windows\panther\setupinfo.
Windeploy.exe exiting with code [0x0]
SetupSQM Started
Panther path is C:\windows\Panther
SQM not opted in
SetupSQM is finished
Our image environment was created during an MCS Engagement, so we have the solution pack and there are many variables in customsettings.ini. I will need to find out how to narrow this down but I'm not finding a log file that tells me where it's choking...
Any suggestions are appreciated.
Thanks,
FP

Similar Messages

Blue screen error "windows has recovered from a unexpected shutdown"

Hi guys
I am using laptop & everyday it will unexpectedly shutdown and shows Blue screen error "windows has recovered from a unexpected shutdown"...Pls help me to resolve this issue.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: 00000030
BCP2: 00000002
BCP3: 00000000
BCP4: 8F2DA8A5
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062614-23836-01.dmp
C:\Users\Venkateshwara swamy\AppData\Local\Temp\WER-74552-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

It could be some driver compatibility issues.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx
http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Windows has recovered from an unexpected shutdown(blue screen) windows 7 ultimate 64 bit

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF90043C98BEC
BCP2: 0000000000000001
BCP3: FFFFF9600025033E
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\060614-25256-01.dmp
C:\Windows\Temp\WER-31699-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
please help
this happens after i add a 2gb ram

YH
These were driver verified and Related to nvlddmkm.sys nVidia Display Driver. I would install the newest driver available (even if it is the same date as drivers do become corrupt)
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\060714-31793-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03a4c000 PsLoadedModuleList = 0xfffff800`03c8f670
Debug session time: Sat Jun 7 01:23:16.118 2014 (UTC - 4:00)
System Uptime: 0 days 0:03:21.913
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 17c, fffffa8005acab30, fffff8800f327295}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9b295 )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 000000000000017c, Handle value being referenced.
Arg3: fffffa8005acab30, Address of the current process.
Arg4: fffff8800f327295, Address inside the driver that is performing the incorrect reference.
Debugging Details:
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: nvspcaps64.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80003f4f4ec to fffff80003ac1c00
STACK_TEXT:
fffff880`09fe3a38 fffff800`03f4f4ec : 00000000`000000c4 00000000`000000f6 00000000`0000017c fffffa80`05acab30 : nt!KeBugCheckEx
fffff880`09fe3a40 fffff800`03f64bf4 : 00000000`0000017c fffffa80`05acab30 00000000`00000004 fffff800`03aec83b : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`09fe3a80 fffff800`03d1c0e0 : 00000000`00000000 fffff880`09fe3cd0 fffff880`09fe3e00 fffff880`09fe3f88 : nt!VfCheckUserHandle+0x1b4
fffff880`09fe3b60 fffff800`03d76c31 : fffff8a0`0ab06000 00000000`00000002 fffffa80`018c9f30 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x202ae
fffff880`09fe3c30 fffff800`03ac0e93 : 00000000`0000017c 00000000`00000240 00000000`00000000 00000000`00000003 : nt!NtSetValueKey+0xe1
fffff880`09fe3d60 fffff800`03abd450 : fffff800`03f534db fffff880`0f327295 fffff880`09fe4afc 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09fe3f68 fffff800`03f534db : fffff880`0f327295 fffff880`09fe4afc 00000000`00000000 fffff800`03abd450 : nt!KiServiceLinkage
fffff880`09fe3f70 fffff880`0f327295 : 00000000`00000008 fffff880`09fe4031 00000000`00000011 ffffffff`80000d38 : nt!VfZwSetValueKey+0x6b
fffff880`09fe3fc0 00000000`00000008 : fffff880`09fe4031 00000000`00000011 ffffffff`80000d38 fffff880`09fe4afc : nvlddmkm+0x9b295
fffff880`09fe3fc8 fffff880`09fe4031 : 00000000`00000011 ffffffff`80000d38 fffff880`09fe4afc fffff800`00000004 : 0x8
fffff880`09fe3fd0 00000000`00000011 : ffffffff`80000d38 fffff880`09fe4afc fffff800`00000004 00000000`00000000 : 0xfffff880`09fe4031
fffff880`09fe3fd8 ffffffff`80000d38 : fffff880`09fe4afc fffff800`00000004 00000000`00000000 00000000`00000000 : 0x11
fffff880`09fe3fe0 fffff880`09fe4afc : fffff800`00000004 00000000`00000000 00000000`00000000 00000000`0000017c : 0xffffffff`80000d38
fffff880`09fe3fe8 fffff800`00000004 : 00000000`00000000 00000000`00000000 00000000`0000017c 00000000`00120010 : 0xfffff880`09fe4afc
fffff880`09fe3ff0 00000000`00000000 : 00000000`00000000 00000000`0000017c 00000000`00120010 fffff880`09fe4a0a : 0xfffff800`00000004
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+9b295
fffff880`0f327295 488b4dcf mov rcx,qword ptr [rbp-31h]
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: nvlddmkm+9b295
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52b326bc
FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_nvlddmkm+9b295
BUCKET_ID: X64_0xc4_f6_VRF_nvlddmkm+9b295
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_vrf_nvlddmkm+9b295
FAILURE_ID_HASH: {b9cbc4df-f49a-e3ea-a7bf-8726e91f6c99}
Followup: MachineOwner
Other drivers needing updating
nvm62x64.sys 10/17/2008 5:01:06 PM fffff880`04400000 fffff880`04463d80 0x48f8fd12 0x00063d80
anodlwfx.sys 3/6/2009 6:10:08 AM fffff880`041b3000 fffff880`041bc000 0x49b0f680 0x00009000
Wanikiya and Dyami--Team Zigzag

Windows has recovered from an unexpected shut down -- Windows 7 on 64 bit problems

Hi, I know lots of people have had this problem, but I need help --- it seems like since everyone has had this problem since 2009, there should be an easier way to fix it than all the complicated answers I have read so far.
I have a Toshiba Satellite A305; T8100 @ 2.10GHz; 64 bit.
My computer will have an unexpected shut down whenever it is left alone for too long (goes to sleep). I've tried installing the latest drivers.... maybe I am missing something?
Problem signature:
Problem Event Name:    BlueScreen
OS Version:    6.1.7600.2.0.0.256.1
Locale ID:    1033
Additional information about the problem:
BCCode:    100000ea
BCP1:    FFFFFA8005D77060
BCP2:    0000000000000000
BCP3:    0000000000000000
BCP4:    0000000000000000
OS Version:    6_1_7600
Service Pack:    0_0
Product:    256_1
Files that help describe the problem:
C:\Windows\Minidump\030711-55239-01.dmp
C:\Users\Tina\AppData\Local\Temp\WER-141149-0.sysdata.xml

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
Arguments:
Arg1: fffffa8005d77060, Pointer to a stuck thread object. Do .thread then kb on it to find
   the hung location.
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Thu Jul 30 06:23:28 2009 (4A712040)
    CheckSum:         005CC239
    ImageSize:        00617000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> k
Child-SP          RetAddr           Call Site
fffff880`069de588 fffff880`04e95f63 nt!KeBugCheckEx
fffff880`069de590 fffff880`04e96112 dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`069de600 fffff880`048a909a dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`069de640 00000000`00000000 atikmdag +0x3109a
your extremely old ATI catalyst driver is the cause. Update the driver:
http://game.amd.com/us-en/drivers_catalyst.aspx
André
"A programmer is just a tool which converts caffeine into code"
Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221

Windows has recovered from a serious error

Hi all, I've been reading a lot about overclocking and I finally started today. I have set my FSB to 233, and I have been trying to find the lowest voltage I can run it at. 1.6 works fine but I tried going lower. This resulted in a spontaneous reboot. After windows booted back up when I increased the voltage, the windows error reporting dialog came up and said "windows has recovered from a serious error..." So I send the report... and internet explorer opens with a little info. It says the crash was due to a problem with a driver but does not mention a specific driver. does this osund familiar to anyone? are there any drivers i should investigate or replace? thanks a lot for your help!

often with overclocking you will see 'file not found' BSODs on startup. It is reasonable to assume that our overclock may have upset a driver, driver component or driver associated file.
Don't sweat it, as long as your not on that vCore now there should be no damage done to Windows.
Have to admit I've had "Windows has...serious error" before following a vCore increasment on an AMD board.

Wiping a disk with MDT task sequence?

I'm thinking that I could use MDT/WDS to do a secure disk wipe for old computers. Has anyone implemented something like this with MDT?

Take a look at the "Client Replace" Task sequence template supplied with MDT
This Task Sequence is designed to de-commission a client computer, first saving the data to a external network share.
The task sequence also calls the ZTIWipeDisk.wsf script to peform a multi-pass wipe of all partitions.
Then again, if you have machines with sensitive information on them, you should be using disk encryption like Bitlocker to ensure that the data is protected. Simply install a new OS without suspending the old BitLocker protection.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

"Windows has recovered from a critical device failure." UGH!

I get this message a lot, and as you all probably know, it happens unexpectedly, in the middle of the most random activities. I can't think of a single mundane situation on my PC that this crash hasn't reared its ugly head. I can be web surfing, using Outlook, scrolling through a WinAmp playlist, playing a game, opening a document, exploring the file system, setting system settings....anything....but it certainly happens a lot more often when I'm playing games.
I'm beginning to find a small pattern though: this seems to happen much more often if I've just booted up my machine.
Is anyone else noticing that these crashes happen more often shortly after powering on the machine, before the various chips on the motherboard or video card get a chance to "warm up?" I believe this sort of issue is called a "cold-solder" problem, in which silicon-based systems tend to exhibit different behaviors between their cold and hot states.
I tend to lock-up in games only if I launch them soon after powering on my PC. If the PC has been on for an hour or so (and has in essence "burned in" for the night) I have very few problems. The majority of my crashes are in applications that I mess with a lot right after booting up.
Does anyone else witness this sort of behavior from their Radeon 9700 Pro or GNB MAX (and similar) motherboards?
Thanks.
Woland
By the way, I have tried a million different things and none seem to work.
I've replaced the 9700 Pro with a new card.
I've tried with various sound cards and no sound card.
I've got the latest drivers, updates, etc. for Windows XP.
I've tried the base XP drivers for the Radeon 9700.
I've tried the 3.1 and 3.2 Catalyst drivers.
I've updated my BIOS.
I've disabled Hyper-Threading.
I've set AGP aperture to 64.
I've set AGP override to 2X and No Override.
I've set my BIOS to all failsafe settings.
I've reformatted and re-installed Windows XP.
I've tried the latest drivers for various other pieces of hardware.
I've got the latest motherboard drivers.
I've tried various desktop resolutions and bit-depths and refresh rates.
I've upgraded the power supply to 430 Watts.
I've disabled my USB controllers.
I've convinced ATI to give me beta drivers (essentially Catalyst 3.3).
Etc.
Etc.
Etc.
Here's my system:
Windows XP (all the latest updates)
3.06 GHz Intel Pentium 4 Hyper-Threading CPU
MSI GNB MAX FISR (M6565) motherboard (8X AGP, S-ATA, Bluetooth, GBit LAN, etc.) - latest BIOS
ATI Radeon 9700 Pro (many flavors of drivers, now using some beta drivers)
Sound Blaster Audigy 2 Platinum (with internal break-out box) - up to date drivers
2x 512MB Kingston HyperX Dual Channel DDR Memory SIMMs
Western Digital Special Edition Caviar 200GB IDE Hard Drive
Western Digital Caviar 80GB IDE Hard Drive
Sony DRU-500A DVD-RW / DVD+RW Drive
USB 2.0 Controller Enabled (and Disabled)
IEEE1394 Firewire Controller Disabled
Both Onboard IDE Controllers Enabled
Serial ATA Controller Disabled
Floppy Drive Controller Disabled
Parallel and Serial Ports Disabled
Using USB mouse and PS/2 keyboard
ViewSonic GS970 19" monitor
Onboard 10/100/1000 MBit LAN Enabled
Onboard Audio Disabled
Bluetooth Controller Disabled

Probably the Radeon vs E7205 problem.
Try the latest ATI drivers and if that won't solve it try setting the bios to AGP x4 override.

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.

MDT Task Sequence with standard "Create Task Sequence Media" image capture?

Hello,
After much research and a lot of exhausted attempts/hours between two of us we have broken down and decided to ask a very direct question. Is it possible to run an MDT Task Sequence with an image captured within SCCM and not MDT?
Reason for asking is the sequence fails every time with the error:
“Task Sequence: NAME has failed with the error code (0x80070490).”
I should note that there is no smsts log because it fails during the install and comes back with "no OS available" and there is no sccm client on the machine either. From what I could gather the error code is related to the HDD and I have tried
every setting within the task sequence I know of in different combinations to no avail. Which led us to wondering if maybe the whole process isn't even possible since we are using an MDT task sequence with an sccm image capture.
The standard task sequences work fine with the sccm image capture, but as soon as we try to the MDT sequence it fails. ANy advice/information/help on this is much appreciated.

I can't thank you enough, that was exactly it. I should have known that it would be something so simple, I've been going crazy looking through the task sequence properties trying to figure out what I could be missing.
No problem at all, happy to help! I was in the same boat driving myself crazy looking at the task sequence properties. I just happened to stumble upon that setting and decided to give it a shot since I had exhausted seemingly every other avenue.
Also, to answer your other question, in a standard task sequence, you can name the computer by using the collection variable "OSDComputerName". Just right click the collection you have your task sequence deployed to, choose properties, and then the collection
variables tab. Click the starburst, enter the variable name OSDComputerName, uncheck the box for "do not display" (I think that's the setting) and apply your changes. When you run your task sequence again, you'll choose your TS from the list, click next, double
click OSDComputerName (just clicking next will skip it and begin the TS), enter the computer name, click OK, and kick off your TS.
I'm still finding my way around SCCM since it was thrown into my lap with no prior experience so I'm happy to help when someone is stuck. I've been there more times than I can count and others have helped me.

Hyper-v Virtual machine creation as part of MDT task sequence

Hello,
I have an existing MDT 2013 environment where I deploy Server 2008 R2 core with Hyper V role to HP Microservers.
The next step is to use hyper v manager and remotely configure the network and build VMs.
I would like to try and bring this together, and am sure I have seen similar powershell scripts online, but have not been able to find them despite an afternoon/evening of searching.
Ideally what I would like to happen is run a powershell script as part of MDT task to do the following.
1) create switch on hyper v host
2) build two VMs with fixed hard discs
3) VMs to automatically start and either PXE boot, which will connect to my existing automated MDT environment, or load the MDT iso image to initiate OS install.
Is anyone aware of existing scripts which can do this?
Or have any links which could help me achieve this?
Please note i am only using server 2008 r2 OS at present.
Many Thanks

Basically this has a little to nothing to do with MDT.
It's more about having the powershell scripts to do it, here's a good start:
http://blogs.technet.com/b/heyscriptingguy/archive/2013/10/16/powertip-create-a-virtual-switch-in-hyper-v-with-windows-powershell.aspx
http://technet.microsoft.com/en-us/magazine/jj933287.aspx
Once you have the script's tested and working, you can try to incorporate them into your MDT task sequence. Just add an "Run PowerShell Script" and refer to the script as: %DeployRoot%\Applications\Name Of Script\createVM.ps1 or something like that.
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards

SCCM 2012 with MDT: osd, apply wim captured with CM task sequence in MDT task sequence: "cannot find the file specified"

Hi,
Please see titlte. When I try to apply an CM captured WIM via an MDT task sequence, it starts, applies but stops after 15 minutes.
Logfile says it "cannot find the file specified".
Full error: "Installation of image 3 in package mypackage failed to complete. . The system cannot find the file specified. (Error: 80070002, Source: Windows).
Though the image IS there, redistributed it (if it wouldn't be there the task sequence would not start).
Please advise.
J
Update: could it be the fact I'm using an old (SCCM 2012) MDT wim? If I need to recreate the WIM boot image, where do I get the SCCM 2012 R2 boot wims?
Jan Hoedt

See how to manually re-create your boot images
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

2 questions - missing boot image, create mdt task sequence button missing

I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan

"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Lenovo Power Manager Software - MDT Task Sequence

I'm working in an environment which does Operating System Deployment via SCCM 2007 SP2 R2 with MDT 2010 Update 1 Integration. I have an MDT Task Sequence that deploys my captured Windows 7 WIM file to predominantly Lenovo laptops (98% Lenovo fleet too). Part of this Task Sequence uses rules to specifically target drivers and applications to individual models. I'm am having GREAT difficulty in getting the Lenono Power Manager software (V3.31) to install as part of the Task Sequence.
The summary of the story is as follows:
Lenovo Bluetooth software is installing OK (msiexec /i Win32\BTW.msi /t 1033.mst /qb-)
Lenovo Hotkey software is installing OK (SETUP.EXE /S)
I've put logs for the Power Manager installation, and there are no errors i.e. it "seems" to install OK (SETUP.EXE /S)
I can advertise the Power Manager software POST image and it installs and works OK
Applications in the Task Sequence run in the order of Power Manager, Bluetooth, Hotkeys.
That hopefully provides the information for someone to maybe shed some light. It's a little frustrating given that the package actually will successfully install. I'm almost to the point where I want to try and create a collection with rules to populate it with Lenovo laptops and then mandatory install it. It's not a critical application - it would just be nice to have.
Solved!
Go to Solution.

I did some more searching and found this method to do it - http://www.windows-noob.com/forums/index.php?/topic/1231-os-deployment-and-lenovo-computers/. I used the idea of creating a Task Sequence step to copy the files locally, followed by a step to install it from the local files. It worked fine for this. If anyone has a "cleaner" method though, let me know.

How to use two different boot images in the same task sequence

I have a need to use Two boot images in the same task sequence. The reason is I'm deploying ZTI to McAfee encrypted devices which I have already done with McAfee v6 Encryption successfully.
Here's where my problem comes in. We are about to deploy McAfee v7 which means we will have a mix of v6 and v7 in our environment. I must have two special Boot images one with v6 drivers and one with v7 drivers in order for my process to work. I don't see
a way right now to assign more than one boot image to a task sequence. Is there any way to do this?
If I can't do that then I will have to create two task sequences and target collections based on the Endpoint Encryption version to deploy to.
If anyone has suggestions it would be much appreciated. Thank you

Have you tested copying those files to %windir%\system32\drivers during the WinPE session (just enable commandline support to your boot image) to see if they need to be in there before the OS start? Test that and if they don't need to be there during the
boot up of WinPE then:
Create two packages (v6 and v7)
"Run command line", use the package created earlier and just use "copy /Y .\*.* %windir%\system32\drivers" ...again, this should be run according to your needs, variable or some other check like I said

Is it possible to edit a MDT Task Sequence after starting a deployment, between Hyper-V snapshots?

Using a Hyper-V VM, I take snapshots of my base image build between major sections (automatic updates, application installation, scripts and extras, etc.) with the intention of being able to go back to that area and look at it for troubleshooting's sake.
Each of these snapshots is manually taken during a pause in my MDT task sequence (using LTISuspend). I would like to be able to roll back to these snaphots make edits to the task sequence (obviously to sections that haven't yet run), then resume and
see the changes implemented - but I don't know where the task sequence file(s) resides on VM being imaged, or if that can be changed after kicking it off at the very start of the build.
Is it possible to replace the task sequence file (and any other necessary files) that are cached locally on the VM during the imaging process? Where are those files located? Or any other way to implement changes to my task sequence so I wouldn't
have to start the image build completely from scratch?
This build takes about 6 hours. Having to make even the slightest modification causes me to lose an entire day, so this would be golden even if I have to manually edit certain files!

Hi,
Based on my known, you cannot edit the task sequence after starting the deployment.
However, I suggest you ask this issue in MDT forum for more professional solution:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn
from your interaction with us. Thank you for your understanding.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

Similar Messages

Maybe you are looking for