MDT 2012 - Failure 5456: Unable to determine Destination Disk....
Hi,
I get the following error when deploying windows 7 image to HP z420 workstation:
Failure 5456: Unable to determine destination disk, partition, and/or drive. See BDD.LOG
LiteTouch deployment failed, return code = -2147467259 0x80004005
Failed to run the action: inject drivers
When I deploy this same image with exact same settings to virtual machine or HP Elitebook laptop everything works fine. I have imported all z420 drivers to MDT too.
Any ideas?
Problem solved.
Solution:
“FAILURE (5456): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.”
I was only getting this message using MDT2012, not MDT2010. After digging around I noticed a modified setting — that I did not modify. Not sure why this happened.
Look inside the task sequence, under “Install Operating System”. While my other task sequences are set to “Specific Disk and Partition” this one was set to “Logical drive letter stored in a variable”. When I changed it, the error went away immediately.
http://www.thedecoderwheel.com/?p=1498
Similar Messages
-
I am having trouble trying to capture a new Windows 8 image with WDT 2012.
My Setup -
Server 2012
WDS
MDT 2012
Windows 8 ADK
Hyper-V
I have created a new task and I can get the image to successfully deploy the image to a VM but it seems to fail at the Restore User State task.
Once the install Applications task has finished I added a Suspend task so I could customize the image a little. Upon resuming the task sequence is where the above failure message appears. I can see it gets to the next step (which is 'Restore User State')
but that seems to be where is crashes.
Does anyone have any advice on what I might be doing wrong or what I can do to resolve the above issue?WAIK being installed was probably your issue so I wouldn't bother disabling the restore task. It is used to migrate user data, docs, and settings on refreshes, not new builds. It doesn't affect CopyProfile, just note that data will be migrated on refreshes so
some aspects may change, ie wallpaper, shortcuts, etc but what gets migrated with USMT can also be configured.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
"Unable to determine destination partition, disk or drive" when Media deployment is used
We are heavy users of MDT 2013's "media" deployments -- in fact, once we finish testing a new image build on our lab server, media is created and is the sole method we use to deploy new systems due to many limitations.
We ran into the following issue lately when using USB sticks or hard drives for our deployment media. Deployment of an OS image fails at the "Inject Drivers" stage. The hard disk inside the computer is formatted properly, but the TS fails with
the error "Unable to determine destination partition, disk or drive".
I dug into the logs, and it appears that "Inject drivers" does a check for where the \Drivers folder should be placed. The problem is that most USB hard disks and many higher-end USB sticks show up as "hard drives" rather than "removable
media" when plugged into the machine. Adding another physical disk that appears as a fixed disk with an NTFS partition apparently confuses MDT and you get this error message. I think any "ReadyBoost enabled" USB stick has to show up on the system
as a fixed disk rather than removable, so if you use these you might have this problem.
The only workaround is to explicitly specify the disk number and partition number to use when you invoke "Install Operating System." The drivers step must take this information when determining where to put the driver store.
Is there any other explanation for why this would be happening? We're stuck with media deployment for the foreseeable future, and until Microsoft fixes the problem with handling of split WIM files, we have to use NTFS formatted disks/sticks...this might
be making it harder for the MDT logic to determine where to put the OS.MDT should be smart enough to know that it should Skip USB drives.
However if you have a USB 3 Hard DIsk (not a USB Flash Disk), that might be the problem
1. Try using only Flash Drives.
2. Try plugging the USB Hard Drive into a USB 2.0 port
3. Additionally try not to use USB Hard Drives that are *Larger* that the internal hard drive.
If you still have problems, can you copy your Bdd.log file to a public site like OneDrive and share the link?
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com -
Unable to determine Physical Disk from the VM manager : 3.2.1
Unable to determine Physical Disk from the VM manager :
OVM manager : 3.2.1.516
VM Server : Available disks on vm server
# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 13 104391 83 Linux
/dev/sda2 14 405 3148740 83 Linux
/dev/sda3 406 536 1052257+ 82 Linux swap / Solaris
Disk /dev/sdb: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 9328 74822737+ 83 Linux
/dev/sdb3 9329 9459 1052257+ 82 Linux swap / Solaris
Disk /dev/dm-0: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-0p1 * 1 13 104391 83 Linux
/dev/dm-0p2 14 9328 74822737+ 83 Linux
/dev/dm-0p3 9329 9459 1052257+ 82 Linux swap / Solaris
Disk /dev/dm-1: 106 MB, 106896384 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Disk /dev/dm-2: 76.6 GB, 76618483200 bytes
255 heads, 63 sectors/track, 9315 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3: 1077 MB, 1077511680 bytes
255 heads, 63 sectors/track, 131 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-3 doesn't contain a valid partition table
#thanks for your prompt response.
I am aware of that we can't use any free spaces where the VM is installed.Hence the additional storage added to the server.
1. Install VM Server on 80GB HD ( /dev/sdb)
2. Later, i added 500GB to the storage ( no installation - just the disk ) ( /dev/sda)
Same configuration worked fine in 3.0, now i am not able to identified the additional disk which was added later with 3.2.1. -
MDT 2012 - Update Deploymentshare: Unable to open the specified WIM file
Hi @ all
wie have updated our Litetouch boot image using DISM and know we try to update the deploymentshare but we get the following error.
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
--- End of inner exception stack trace ---
at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
Unable to open the specified WIM file? The image ist is stil in the boot folder.
Anybody an idea or an solution for that problem?
Thank's
AdrianI had installed ADK to utilize the latest and greatest DISM tool. That broke WAIK and the boot.wim could not be found when updating the deployment shares. Thanks for the pointer...
Paul Prindle MCP, A+
That is because WAIK and ADK are unsupported as side-by-side installations.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
How to ask a question that is fixable. -
After downloading Mavericks, tried installing, it told me that I have a damaged disk and to restore from backup. Selected Time Machine's latest backup. Then I was prompted to select backup disk. My only option was the Mac HD icon with a "?" on top of it, unable to verify disk. With the "continue" button grayed out, I hit the back button a few times in an attempt to start over. I went back to the install page and it started installing. 40 minutes later it was up and running. Every thing seemed fine. I tried opening GarageBand, I got the spinning wheel. Then a prompt page asking me to select a language. I selected English and the computer shutdown. It being late and I being frustrated, I decided to wait until morning.
On startup I got the message that I have a damaged disk and to restore from backup. Selected Time Machine's latest backup. Then I was prompted to select backup disk. This time there was no icon or anything to choose from.
I'm wondering if I need to use my original Mac mini, Mac OS X install DVD, or is it time for a trip to the Apple store.
Ideas and options welcome.
ThanksIt sounds as if your hard drive may have failed or may be failing. Boot your computer from the REcovery Disk by holding down the Command+R keys during the boot. From the Recovery drive you can run Disk Utility. Once in DU select your hard drive then run "Repair Disk".
If errors are found and repaired run Repair Disk a second time.
If errors are found and not repaired you are going to need a more robust volume repair utiity such as DiskWarrior, TechTool Pro, or Drive Genius and an external drive to boot from to run the repairs or...
You may be in the market for a new HD -
Unable to capture image using MDT 2012
After running my Sysprep and Capture task using MDT 2012, MDT begins to capture the image and makes it all the way to ~94% and then stops and returns several errors. Any idea as to what may be causing this? Below are the errors returned during the capture
task and the ZTIBackup.log:
Error creating an image of drive C:, re=2
ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM.
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The execution of the group (capture Image) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Create WIM. Execution of task sequence failed.
The system cannot find the file specified. (Error: 00000002; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
ZTIBackup.log:
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context=""
type="1" thread="" file="ZTIBackup">
<![LOG[OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '299999686656' and VolumeName = '' and VolumeSerialNumber = '2A688632']LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Search for Drive: OriginalPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '299999686656' and VolumeName = '' and VolumeSerialNumber = '2A688632']LOG]!><time="14:01:12.000+000" date="08-15-2014"
component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Found Drive: C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDisk is now = C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[BackupDrive not specified searching for backup drive]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[BackupDrive defaulting to Destination Logical Drive: C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Checking to see if we can store the backup locally]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive C: 160595120]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store path = C:\StateStore]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Total used space: 160595120]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Available space at C:\StateStore: 132373320]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store not permitted]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to blank]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to: \\OCS-MDT\CCBShare$\Captures]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Backup file name already set to: CCB01-8_15_14.wim]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Using the backup path: \\OCS-MDT\CCBShare$\Captures\CCB01-8_15_14.wim]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Validating connection to \\OCS-MDT\CCBShare$\Captures]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Already connected to server OCS-MDT as that is where this script is running from.]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[Beginning backup of drive C:]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[About to run command: "\\OCS-MDT\CCBShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\OCS-MDT\CCBShare$\Captures\CCB01-8_15_14.wim" "CCB01CDrive" /flags ENTERPRISE]LOG]!><time="14:01:13.000+000"
date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Command has been started (process ID 1568)]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1568)]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Files/folders excluded from image capture by default:]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~bt]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~ls]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \winpepge.sys]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Windows\CSC]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycled]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycler]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$Recycle.Bin\*]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \System Volume Information]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \pagefile.sys]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \hiberfil.sys]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Turning on VERIFY option for network share]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Scanning files and directories...]LOG]!><time="14:01:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 0% ] Capturing progress ]LOG]!><time="14:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 17 minutes (process ID 1568)]LOG]!><time="14:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 1% ] Capturing progress ]LOG]!><time="14:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 2% ] Capturing progress: 2:22:22 hrs remaining ]LOG]!><time="14:21:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 3% ] Capturing progress: 2:23:19 hrs remaining ]LOG]!><time="14:22:41.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 4% ] Capturing progress: 2:23:01 hrs remaining ]LOG]!><time="14:24:11.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 23 minutes (process ID 1568)]LOG]!><time="14:24:11.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 5% ] Capturing progress: 2:39:46 hrs remaining ]LOG]!><time="14:27:38.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 6% ] Capturing progress: 2:43:14 hrs remaining ]LOG]!><time="14:28:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 7% ] Capturing progress: 2:43:42 hrs remaining ]LOG]!><time="14:30:39.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 29 minutes (process ID 1568)]LOG]!><time="14:30:39.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 8% ] Capturing progress: 2:41:26 hrs remaining ]LOG]!><time="14:32:08.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 9% ] Capturing progress: 2:43:24 hrs remaining ]LOG]!><time="14:34:47.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 10% ] Capturing progress: 2:41:57 hrs remaining ]LOG]!><time="14:36:09.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 35 minutes (process ID 1568)]LOG]!><time="14:36:09.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 11% ] Capturing progress: 2:38:33 hrs remaining ]LOG]!><time="14:37:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 12% ] Capturing progress: 2:35:51 hrs remaining ]LOG]!><time="14:39:18.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 13% ] Capturing progress: 2:33:30 hrs remaining ]LOG]!><time="14:41:00.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 40 minutes (process ID 1568)]LOG]!><time="14:41:00.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 14% ] Capturing progress: 2:30:39 hrs remaining ]LOG]!><time="14:42:28.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 15% ] Capturing progress: 2:28:39 hrs remaining ]LOG]!><time="14:44:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 16% ] Capturing progress: 2:28:06 hrs remaining ]LOG]!><time="14:46:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 45 minutes (process ID 1568)]LOG]!><time="14:46:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 17% ] Capturing progress: 2:30:58 hrs remaining ]LOG]!><time="14:50:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 18% ] Capturing progress: 2:42:16 hrs remaining ]LOG]!><time="14:57:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 56 minutes (process ID 1568)]LOG]!><time="14:57:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 19% ] Capturing progress: 2:55:09 hrs remaining ]LOG]!><time="15:03:37.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 62 minutes (process ID 1568)]LOG]!><time="15:03:37.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 20% ] Capturing progress: 3:03:46 hrs remaining ]LOG]!><time="15:07:09.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 21% ] Capturing progress: 3:10:17 hrs remaining ]LOG]!><time="15:11:41.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 70 minutes (process ID 1568)]LOG]!><time="15:11:41.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 22% ] Capturing progress: 3:12:08 hrs remaining ]LOG]!><time="15:13:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 23% ] Capturing progress: 3:11:13 hrs remaining ]LOG]!><time="15:15:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 24% ] Capturing progress: 3:08:56 hrs remaining ]LOG]!><time="15:17:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 76 minutes (process ID 1568)]LOG]!><time="15:17:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 25% ] Capturing progress: 3:06:17 hrs remaining ]LOG]!><time="15:20:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 26% ] Capturing progress: 3:03:27 hrs remaining ]LOG]!><time="15:22:24.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 81 minutes (process ID 1568)]LOG]!><time="15:22:24.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 27% ] Capturing progress: 3:00:07 hrs remaining ]LOG]!><time="15:24:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 28% ] Capturing progress: 2:56:19 hrs remaining ]LOG]!><time="15:25:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 29% ] Capturing progress: 2:54:19 hrs remaining ]LOG]!><time="15:30:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 89 minutes (process ID 1568)]LOG]!><time="15:30:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 30% ] Capturing progress: 2:52:44 hrs remaining ]LOG]!><time="15:32:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 31% ] Capturing progress: 2:50:14 hrs remaining ]LOG]!><time="15:34:29.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 32% ] Capturing progress: 2:47:25 hrs remaining ]LOG]!><time="15:36:38.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 95 minutes (process ID 1568)]LOG]!><time="15:36:38.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 33% ] Capturing progress: 2:44:17 hrs remaining ]LOG]!><time="15:38:25.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 34% ] Capturing progress: 2:40:58 hrs remaining ]LOG]!><time="15:40:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 35% ] Capturing progress: 2:37:40 hrs remaining ]LOG]!><time="15:42:17.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 101 minutes (process ID 1568)]LOG]!><time="15:42:17.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 36% ] Capturing progress: 2:34:21 hrs remaining ]LOG]!><time="15:44:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 37% ] Capturing progress: 2:31:09 hrs remaining ]LOG]!><time="15:46:18.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 38% ] Capturing progress: 2:28:17 hrs remaining ]LOG]!><time="15:48:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 107 minutes (process ID 1568)]LOG]!><time="15:48:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 39% ] Capturing progress: 2:25:45 hrs remaining ]LOG]!><time="15:51:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 40% ] Capturing progress: 2:23:10 hrs remaining ]LOG]!><time="15:53:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 112 minutes (process ID 1568)]LOG]!><time="15:53:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 41% ] Capturing progress: 2:20:18 hrs remaining ]LOG]!><time="15:54:44.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 42% ] Capturing progress: 2:17:13 hrs remaining ]LOG]!><time="15:56:48.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 43% ] Capturing progress: 2:14:21 hrs remaining ]LOG]!><time="15:59:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 118 minutes (process ID 1568)]LOG]!><time="15:59:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 44% ] Capturing progress: 2:11:48 hrs remaining ]LOG]!><time="16:01:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 45% ] Capturing progress: 2:09:52 hrs remaining ]LOG]!><time="16:07:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 126 minutes (process ID 1568)]LOG]!><time="16:07:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 46% ] Capturing progress: 2:09:09 hrs remaining ]LOG]!><time="16:10:37.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 47% ] Capturing progress: 2:08:08 hrs remaining ]LOG]!><time="16:12:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 131 minutes (process ID 1568)]LOG]!><time="16:12:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 48% ] Capturing progress: 2:06:21 hrs remaining ]LOG]!><time="16:15:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 49% ] Capturing progress: 2:04:12 hrs remaining ]LOG]!><time="16:17:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 136 minutes (process ID 1568)]LOG]!><time="16:17:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 50% ] Capturing progress: 2:01:44 hrs remaining ]LOG]!><time="16:20:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 51% ] Capturing progress: 1:59:26 hrs remaining ]LOG]!><time="16:22:36.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 141 minutes (process ID 1568)]LOG]!><time="16:22:36.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 52% ] Capturing progress: 1:57:05 hrs remaining ]LOG]!><time="16:24:21.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 53% ] Capturing progress: 1:54:22 hrs remaining ]LOG]!><time="16:26:15.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 54% ] Capturing progress: 1:51:34 hrs remaining ]LOG]!><time="16:28:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 147 minutes (process ID 1568)]LOG]!><time="16:28:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 55% ] Capturing progress: 1:48:56 hrs remaining ]LOG]!><time="16:30:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 56% ] Capturing progress: 1:46:05 hrs remaining ]LOG]!><time="16:33:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 152 minutes (process ID 1568)]LOG]!><time="16:33:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 57% ] Capturing progress: 1:43:42 hrs remaining ]LOG]!><time="16:35:25.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 58% ] Capturing progress: 1:41:18 hrs remaining ]LOG]!><time="16:37:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 59% ] Capturing progress: 1:38:41 hrs remaining ]LOG]!><time="16:38:57.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 157 minutes (process ID 1568)]LOG]!><time="16:38:57.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 60% ] Capturing progress: 1:36:02 hrs remaining ]LOG]!><time="16:40:19.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 61% ] Capturing progress: 1:33:11 hrs remaining ]LOG]!><time="16:41:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 62% ] Capturing progress: 1:30:13 hrs remaining ]LOG]!><time="16:43:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 162 minutes (process ID 1568)]LOG]!><time="16:43:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 63% ] Capturing progress: 1:27:20 hrs remaining ]LOG]!><time="16:46:48.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 64% ] Capturing progress: 1:24:48 hrs remaining ]LOG]!><time="16:49:52.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 168 minutes (process ID 1568)]LOG]!><time="16:49:52.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 65% ] Capturing progress: 1:22:51 hrs remaining ]LOG]!><time="16:51:34.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 66% ] Capturing progress: 1:20:36 hrs remaining ]LOG]!><time="16:52:56.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 67% ] Capturing progress: 1:17:48 hrs remaining ]LOG]!><time="16:55:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 174 minutes (process ID 1568)]LOG]!><time="16:55:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 68% ] Capturing progress: 1:15:29 hrs remaining ]LOG]!><time="16:56:51.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 69% ] Capturing progress: 1:12:55 hrs remaining ]LOG]!><time="16:58:32.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 70% ] Capturing progress: 1:10:29 hrs remaining ]LOG]!><time="16:59:44.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 71% ] Capturing progress: 1:07:56 hrs remaining ]LOG]!><time="17:00:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 179 minutes (process ID 1568)]LOG]!><time="17:00:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 72% ] Capturing progress: 1:05:07 hrs remaining ]LOG]!><time="17:02:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 73% ] Capturing progress: 1:02:13 hrs remaining ]LOG]!><time="17:04:24.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 74% ] Capturing progress: 59:21 mins remaining ]LOG]!><time="17:07:21.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 186 minutes (process ID 1568)]LOG]!><time="17:07:21.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 75% ] Capturing progress: 57:19 mins remaining ]LOG]!><time="17:08:59.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 76% ] Capturing progress: 54:21 mins remaining ]LOG]!><time="17:12:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 191 minutes (process ID 1568)]LOG]!><time="17:12:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 77% ] Capturing progress: 52:42 mins remaining ]LOG]!><time="17:14:16.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 78% ] Capturing progress: 50:16 mins remaining ]LOG]!><time="17:16:48.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 79% ] Capturing progress: 48:22 mins remaining ]LOG]!><time="17:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 197 minutes (process ID 1568)]LOG]!><time="17:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 80% ] Capturing progress: 46:27 mins remaining ]LOG]!><time="17:18:47.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 81% ] Capturing progress: 44:11 mins remaining ]LOG]!><time="17:19:20.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 82% ] Capturing progress: 41:31 mins remaining ]LOG]!><time="17:20:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 83% ] Capturing progress: 38:07 mins remaining ]LOG]!><time="17:23:49.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 202 minutes (process ID 1568)]LOG]!><time="17:23:49.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 84% ] Capturing progress: 35:48 mins remaining ]LOG]!><time="17:26:06.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 85% ] Capturing progress: 33:25 mins remaining ]LOG]!><time="17:28:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 207 minutes (process ID 1568)]LOG]!><time="17:28:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 86% ] Capturing progress: 31:18 mins remaining ]LOG]!><time="17:30:54.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 87% ] Capturing progress: 29:37 mins remaining ]LOG]!><time="17:31:54.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 88% ] Capturing progress: 27:55 mins remaining ]LOG]!><time="17:32:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 89% ] Capturing progress: 25:04 mins remaining ]LOG]!><time="17:34:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 213 minutes (process ID 1568)]LOG]!><time="17:34:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 90% ] Capturing progress: 22:52 mins remaining ]LOG]!><time="17:35:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 91% ] Capturing progress: 20:47 mins remaining ]LOG]!><time="17:36:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 92% ] Capturing progress: 18:33 mins remaining ]LOG]!><time="17:37:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 93% ] Capturing progress: 16:14 mins remaining ]LOG]!><time="17:38:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 94% ] Capturing progress: 13:54 mins remaining ]LOG]!><time="17:39:40.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 218 minutes (process ID 1568)]LOG]!><time="17:39:40.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 224 minutes (process ID 1568)]LOG]!><time="17:45:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Return code from command = -1073741819]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Error creating an image of drive C:, rc = -1073741819]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
<![LOG[ZTIBackup COMPLETED. Return Value = -1073741819]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI ERROR - Non-zero return code by ZTIBackup, rc = -1073741819 0xC0000005]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="3" thread=""
file="ZTIBackup">Not sure what's going on here. Possibly a corrupt drive? Or the target drive is full?
Try running the imagex command manually from a F8 cmd window (in WinPE)
"\\OCS-MDT\CCBShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\OCS-MDT\CCBShare$\Captures\CCB01-8_15_14.wim" "CCB01CDrive" /flags ENTERPRISE
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com -
Deployment Failure - thick image - (5627) dism.exe (MDT 2012 Update 1)
I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
Here's a snip of the results
<![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
FAILURE ( 5627 ): 2: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)
Failed to run the action: Install Operating System. Execution has been aborted
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]>
Please advise.
Thanks in advance.I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
Here's a snip of the results
<![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
FAILURE ( 5627 ): 2: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)
Failed to run the action: Install Operating System. Execution has been aborted
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]>
Please advise.
Thanks in advance.
Hi Mathew,
I have the similar error deploying a image (no sysprep) using the standard client task sequence. There are 2 partitions, one 500MB for boot and the other remaining partition is for OS. Do you have solutions to resolve the errors? Greatly appreciate
any advice given. Thanks.
Regards,
Eng Chai
Eng Chai -
User State Migration Data Capture Failure MDT 2012 Update 1
Hello All
Trying to capture data on a Win7 x64 machine so that I can keep the data and restore once the computer is done re-imaging. This is an offline MDT deployment on the same computer. See the error below:
CNAME loop detected. (Error: 000025EB; Source: Windows)
Using MDT 2012 Update 1Lots of good information out there. Even stuff that says it's for MDT 2010 also applies to MDT 2012 Update 1 for the most part. Here's a few to get you started:
http://deployment.xtremeconsulting.com/2009/11/20/understanding-usmt-with-mdt-2010/
http://technet.microsoft.com/en-us/magazine/jj127984.aspx
http://blogs.technet.com/b/mniehaus/archive/2009/07/01/mdt-2010-new-feature-12-usmt-4-0-hardlink-support.aspx
http://www.windows-noob.com/forums/index.php?/topic/3758-usmt-mdt/
http://channel9.msdn.com/Events/MMS/2013/DC-B301 (great video with Johan presenting, focused on USMT 5.0)
You should create a default Standard Client Task Sequence and look at the State Capture and State Restore groups to see what MDT sets up for you by default that you may have removed from your current Task Sequence. But the direct answer to your question,
is that ScanState (part of USMT) is the part that creates a backup. LoadState is the piece that restores it to a machine.
David Coulter | http://DCtheGeek.blogspot.com |
@DCtheGeek -
We are in the process of removing a child domain from the forest and are down to two DCs. These are both Server 2008r2 sp1 servers, one physical and virtual (PDC). When I try to remove a DC (not the PDC emulator) I get the following error:
The operation failed because:
Active Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=mydomain,DC=local to
Active Directory Domain Controller \\V-Svr03.mydomain.local.
The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."
I have checked replication with repadmin /showrepl and all connections were successful. The dcdiag /test:kccEvent test on all servers passed.
Most DCdiag tests are successful. The only failure is on NCSecDesc when running dcdiag /test:NCSecDesc
Testing server: Default-First-Site\DC1-DEV-OFC
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=hookemup,DC=local
......................... DC1-DEV-OFC failed test NCSecDesc
In researching this I find "If you do not plan to add an RODC to the forest, you can disregard this error."
We have not successfully run ADprep /rodcPrep nor do we plan on having any Read-Only DCs, so I think we can ignor this error. We did try running ADprep /rodcPrep but got an LDAP error which I can duplicate if this is important.
Schema and Naming FSMOs are on a DC higher in the forest. RID, PDC, and Infrastructure FSMOs for the child domain are on the Virtual server (PDC).
Any guidance on where to go from here would be greatly appreciated as I have no more hair on my head to pull.Ok... I ran repadmin /showreps /v again and it shows no errors
C:\>repadmin /showreps /v
Default-First-Site\DC1-DEV-OFC
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: b294c59f-8b46-4133-89c5-0f30bfd49607
DSA invocationID: 1054285d-cffe-42b4-8074-e2d44adbb151
==== INBOUND NEIGHBORS ======================================
CN=Configuration,DC=mydomain,DC=local
Default-First-Site\HESTIA via RPC
DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 16381490/OU, 16381490/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\V-SVR03 via RPC
DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 114817/OU, 114817/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\V-SVR01 via RPC
DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 66047/OU, 66047/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\ATHENA via RPC
DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 8098197/OU, 8098197/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
CN=Schema,CN=Configuration,DC=mydomain,DC=local
Default-First-Site\ATHENA via RPC
DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 8097482/OU, 8097482/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\V-SVR01 via RPC
DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 65239/OU, 65239/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\V-SVR03 via RPC
DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 114149/OU, 114149/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\HESTIA via RPC
DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 16381373/OU, 16381373/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
DC=ForestDnsZones,DC=mydomain,DC=local
Default-First-Site\V-SVR01 via RPC
DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 66295/OU, 66295/PU
Last attempt @ 2012-10-29 13:57:48 was successful.
Default-First-Site\ATHENA via RPC
DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 8098367/OU, 8098367/PU
Last attempt @ 2012-10-29 13:58:13 was successful.
Default-First-Site\V-SVR03 via RPC
DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 115032/OU, 115032/PU
Last attempt @ 2012-10-29 13:58:25 was successful.
Default-First-Site\HESTIA via RPC
DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 16381653/OU, 16381653/PU
Last attempt @ 2012-10-29 13:58:34 was successful.
DC=mySUBdomain,DC=local
Default-First-Site\V-SVR03 via RPC
DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 114871/OU, 114871/PU
Last attempt @ 2012-10-29 13:54:02 was successful.
DC=DomainDnsZones,DC=mySUBdomain,DC=local
Default-First-Site\V-SVR03 via RPC
DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 114017/OU, 114017/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
DC=mydomain,DC=local
Default-First-Site\V-SVR03 via RPC
DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
USNs: 114017/OU, 114017/PU
Last attempt @ 2012-10-29 13:52:39 was successful.
Default-First-Site\HESTIA via RPC
DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
USNs: 16381614/OU, 16381614/PU
Last attempt @ 2012-10-29 13:56:52 was successful.
Default-First-Site\V-SVR01 via RPC
DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
USNs: 66325/OU, 66325/PU
Last attempt @ 2012-10-29 13:58:34 was successful.
Default-First-Site\ATHENA via RPC
DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
USNs: 8098385/OU, 8098385/PU
Last attempt @ 2012-10-29 13:58:38 was successful. -
MDT 2012 U1 Blue Screen on task sequence ??
My Customer have MDT 2012 U1, so when he start a task sequence when the task start apply operating system, after the system restart and when the computer install the system the blue screen appear. It is very strange beacause the same task sequence work on
some other model but in this Lenove M82 (3306-G1F) and M82 (M3395-AB4) we have the same error. But on other Lenovo model the same task work very fine. Why?
SMSTS.log
We do not find an available volume to store the local data path TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSNextInstructionPointer=24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a TS execution environment variable _SMSTSNextInstructionPointer=24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSInstructionStackString=22 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a TS execution environment variable _SMSTSInstructionStackString=22 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Save the current environment block TSManager 2014-09-11 08:54:07 1892 (0x0764)
pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to save environment to (80070057) TSManager 2014-09-11 08:54:07 1892 (0x0764)
TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
Unknown error (Error: 80070057; Source: Unknown) TSManager 2014-09-11 08:54:07 1892 (0x0764)
SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to persist execution state. Error 0x(80070057) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to save execution state and environment to local hard disk TSManager 2014-09-11 08:54:07 1892 (0x0764)
Start executing an instruciton. Instruction name: New Computer only. Instruction pointer: 24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSCurrentActionName=New Computer only TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSNextInstructionPointer=24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Evaluating an AND expression TSManager 2014-09-11 08:54:07 1892 (0x0764)
Evaluating a variable condition expression TSManager 2014-09-11 08:54:07 1892 (0x0764)
Variable = DeploymentType TSManager 2014-09-11 08:54:07 1892 (0x0764)
Value = NEWCOMPUTER TSManager 2014-09-11 08:54:07 1892 (0x0764)
Operator = equals TSManager 2014-09-11 08:54:07 1892 (0x0764)
Expand a string: equals TSManager 2014-09-11 08:54:07 1892 (0x0764)
Expand a string: DeploymentType TSManager 2014-09-11 08:54:07 1892 (0x0764)
Expand a string: NEWCOMPUTER TSManager 2014-09-11 08:54:07 1892 (0x0764)
The variable condition expression is evaluated to be TRUE TSManager 2014-09-11 08:54:07 1892 (0x0764)
The AND expression is evaluated to be TRUE TSManager 2014-09-11 08:54:07 1892 (0x0764)
The condition for the group (New Computer only) is evaluated to be true TSManager 2014-09-11 08:54:07 1892 (0x0764)
The group (New Computer only) has been successfully started TSManager 2014-09-11 08:54:07 1892 (0x0764)
Sending status message . . . TSManager 2014-09-11 08:54:07 1892 (0x0764)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2014-09-11 08:54:07 1892 (0x0764)
User did not specify local data drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
Volume D:\ is not a fixed hard drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
Volume X:\ is not a fixed hard drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
Volume Z:\ is not a fixed hard drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
BDD.log
Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Property Debug is now = FALSE LiteTouch 2014-09-11 08:53:34 0 (0x0000)
ZTIUtility!GetAllFixedDrives (Faux) LiteTouch 2014-09-11 08:53:34 0 (0x0000)
ZTIUtility!GetAllFixedDrives = LiteTouch 2014-09-11 08:53:34 0 (0x0000)
No task sequence is in progress. LiteTouch 2014-09-11 08:53:34 0 (0x0000)
New ZTIDisk :
\\MININT-KGJQ3PL\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Found Possible OS TargetDisk:
\\MININT-KGJQ3PL\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2014-09-11 08:53:34 0 (0x0000)
GetPartitions: 0 LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Did not find disk. LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Property SMSTSLocalDataDrive is now = LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Unable to connect to BCDStore. LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Not running within WinPE or WinRE. LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeploymentMethod is now = UNC LiteTouch 2014-09-11 08:53:40 0 (0x0000)
DeploymentMethod = UNC LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeployRoot is now = X:\Deploy LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Using a local or mapped drive, no connection is required. LiteTouch 2014-09-11 08:53:40 0 (0x0000)
DeployRoot = X:\Deploy LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeployDrive is now = X: LiteTouch 2014-09-11 08:53:40 0 (0x0000)
DeployDrive = X: LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property PHASE is now = PREINSTALL LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeploymentType is now = NEWCOMPUTER LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Phase = PREINSTALL LiteTouch 2014-09-11 08:53:40 0 (0x0000)
About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property inifile is now = Bootstrap.ini ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
------------------------- Object Initialization ------------------------- ZTIGather 2014-09-11 08:53:40 0 (0x0000)
------------------------- Initialization ------------------------- ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Synchronizing the environments. ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property DeployRoot is now = X:\Deploy ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property DeployDrive is now = X: ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished synchronizing the environments. ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property definition is now = BDD_Welcome_ENU.xml Wizard 2014-09-11 08:53:40 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 Wizard 2014-09-11 08:53:40 0 (0x0000)
Getting OS info ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property OSCurrentVersion is now = 6.1.7601 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property OSCurrentBuild is now = 7601 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property OSVersion is now = WinPE ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IsServerOS is now = False ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IsServerCoreOS is now = False ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished getting OS info ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Getting HAL information ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Not Wizard = Faux Wizard 2014-09-11 08:53:40 0 (0x0000)
Property WizardComplete is now = N Wizard 2014-09-11 08:53:40 0 (0x0000)
Property HALName is now = acpiapic ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished getting HAL information ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Getting network info ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Checking network adapter: [00000000] Intel(R) 82579LM Gigabit Network Connection ZTIGather 2014-09-11 08:53:40 0 (0x0000)
MAC address = 44:37:E6:D0:8F:EF ZTIGather 2014-09-11 08:53:40 0 (0x0000)
IP Address = 10.26.33.23 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
IP Address = fe80::8d70:f039:f93f:e5e9 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Default Gateway = 10.26.32.1 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IPAddress001 is now = 10.26.33.23 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IPAddress002 is now = fe80::8d70:f039:f93f:e5e9 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property MacAddress001 is now = 44:37:E6:D0:8F:EF ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property DefaultGateway001 is now = 10.26.32.1 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished getting network info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Getting DP info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Unable to determine ConfigMgr distribution point ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Finished getting DP info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Getting WDS server info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Unable to determine WDS server name, probably not booted from WDS. ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Finished getting WDS server info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Property HostName is now = MININT-KGJQ3PL ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Getting asset info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Unable to determine asset tag via WMI. ZTIGather 2014-09-11 08:53:41 0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll) Result : 0 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
RUN: regsvr32.exe /s "X:\Deploy\Tools\x86\Microsoft.BDD.Utility.dll" ZTIGather 2014-09-11 08:53:42 0 (0x0000)
FindFile: The file x64\Microsoft.BDD.Utility.dll could not be found in any standard locations. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll) Result : 1 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
RUN: regsvr32.exe /s "" ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property AssetTag is now = ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SerialNumber is now = MJ24PLX ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Make is now = LENOVO ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Model is now = 3306G1F ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Product is now = MAHOBAY ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property UUID is now = 4C5C19C8-5CD9-11E3-8E8B-153233E31400 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Memory is now = 3891 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Architecture is now = X86 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property ProcessorSpeed is now = 3300 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property CapableArchitecture is now = AMD64 X64 X86 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsLaptop is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsDesktop is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsServer is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsUEFI is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsOnBattery is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsX86 is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsX64 is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsSLAT is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Finished getting asset info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Getting OS SKU info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Unable to determine Windows SKU while in Windows PE. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Determining the Disk and Partition Number from the Logical Drive X:\WINDOWS ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property OriginalArchitecture is now = ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Getting virtualization info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsHypervisorRunning is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsVT is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsNX is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Supports64Bit is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsHyperVRole is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
This computer does not appear to be a virtual machine (BIOS is 'LENOVO - 14c0'). ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsVM is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Finished getting virtualization info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Connection succeeded to MicrosoftVolumeEncryption ZTIGather 2014-09-11 08:53:42 0 (0x0000)
There are no encrypted drives ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsBDE is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Processing the PREINSTALL phase. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Determining the INI file to use. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Finished determining the INI file to use. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Using from [Settings]: Rule Priority = DEFAULT ZTIGather 2014-09-11 08:53:42 0 (0x0000)
------ Processing the [DEFAULT] section ------ ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property DEPLOYROOT is now = \\10.26.32.40\DeploymentShare$ ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: DEPLOYROOT =
\\10.26.32.40\DeploymentShare$ ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property USERID is now = Administrateur ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: USERID = Administrateur ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property USERDOMAIN is now = crdiq03 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: USERDOMAIN = crdiq03 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:43 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property KEYBOARDLOCALEPE is now = 0c0c:00001009 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: KEYBOARDLOCALEPE = 0c0c:00001009 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property SKIPBDDWELCOME is now = YES ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: SKIPBDDWELCOME = YES ZTIGather 2014-09-11 08:53:43 0 (0x0000)
------ Done processing X:\Deploy\Scripts\Bootstrap.ini ------ ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Remapping variables. ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property TaskSequenceID is now = ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property DeploymentType is now = NEWCOMPUTER ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Finished remapping variables. ZTIGather 2014-09-11 08:53:43 0 (0x0000)
ZTIGather processing completed successfully. ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Command completed, return code = 0 LiteTouch 2014-09-11 08:53:43 0 (0x0000)
Property WizardComplete is now = Y Wizard 2014-09-11 08:53:44 0 (0x0000)
About to run command: wpeutil.exe SetKeyboardLayout 0c0c:00001009 LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Command completed, return code = 0 LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Validating connection to \\10.26.32.40\DeploymentShare$ LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Mapped Network UNC Path Z: =
\\10.26.32.40\DeploymentShare$ LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Found Existing UNC Path Z: =
\\10.26.32.40\DeploymentShare$ LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Successfully established connection using supplied credentials. LiteTouch 2014-09-11 08:53:44 0 (0x0000)
About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /nolocalonly LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Property definition is now = WelcomeWiz_Initialize.xml Wizard 2014-09-11 08:53:44 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 Wizard 2014-09-11 08:53:44 0 (0x0000)
Property nolocalonly is now = ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIGather 2014-09-11 08:53:44 0 (0x0000)
------------------------- Object Initialization ------------------------- ZTIGather 2014-09-11 08:53:44 0 (0x0000)
------------------------- Initialization ------------------------- ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Synchronizing the environments. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Property DeployRoot is now = \\10.26.32.40\DeploymentShare$ ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Property DeployDrive is now = X: ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Finished synchronizing the environments. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Skipping local settings gathering because it has already been done. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Processing the PREINSTALL phase. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Determining the INI file to use. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Not Wizard = Faux Wizard 2014-09-11 08:53:44 0 (0x0000)
Property WizardComplete is now = N Wizard 2014-09-11 08:53:44 0 (0x0000)
Using DEFAULT VALUE: Ini file =
\\10.26.32.40\DeploymentShare$\Control\CustomSettings.ini ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Finished determining the INI file to use. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Added new custom property MYCUSTOMPROPERTY ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Using from [Settings]: Rule Priority = DEFAULT ZTIGather 2014-09-11 08:53:45 0 (0x0000)
------ Processing the [DEFAULT] section ------ ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property EVENTSERVICE is now = http://10.26.32.40:9800 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: EVENTSERVICE = http://10.26.32.40:9800 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property OSINSTALL is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: OSINSTALL = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property JOINWORKGROUP is now = GROUPE ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: JOINWORKGROUP = GROUPE ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property TIMEZONE is now = 035 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: TIMEZONE = 035 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property TIMEZONENAME is now = Eastern Standard Time ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: TIMEZONENAME = Eastern Standard Time ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property KEYBOARDLOCALE is now = 0c0c:00001009 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: KEYBOARDLOCALE = 0c0c:00001009 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property USERLOCALE is now = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: USERLOCALE = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property UILANGUAGE is now = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: UILANGUAGE = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPCAPTURE is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPCAPTURE = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:45 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPAPPLICATIONS is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPAPPLICATIONS = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPCOMPUTERBACKUP is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPCOMPUTERBACKUP = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPDOMAINMEMBERSHIP is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPDOMAINMEMBERSHIP = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPCOMPUTERNAME is now = NO ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPCOMPUTERNAME = NO ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPDEPLOYMENTTYPE is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPDEPLOYMENTTYPE = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPUSERDATA is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPUSERDATA = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPPACKAGEDISPLAY is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPPACKAGEDISPLAY = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPLOCALESELECTION is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPLOCALESELECTION = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000Hi,
I agree with Damon.
Might be the ConfigMgr Driver Injector will help you.
This tool will allow you to capture installed drivers on your workstations and then will automatically import them in ConfigMgr 2012.
http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Dell Laptops E7440 & E7240 - Issues with connecting to MDT 2012 deployment share
Hi,
Good afternoon.Need help on this please
-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.
-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.
-Laptops and desktops are on same network .
-For OS deployments we have MDT 2012.
-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible
cause:invalid credentials. Retry : Try again to connect to the deployment share.’
-Have injected all possible network & storage drivers mentioned by Dell & Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.
-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address
in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.
Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.
The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.
-Have also tried combination of network & storage drivers from Dell website (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.
-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .
-This very litetouch iso connects to MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause
this happens even with brand new shipped laptops with your inbuild win 7 OS.
-Have tried all options suggested on internet,tested all the drivers suggested but no luck.
-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc individually as well as in combinations but the issue persists.
-If you google many express similar issues with these laptop models.
Though I used the drivers suggested by various bloggers,nothing worked for me.
Any help on this is appreciated.Thanks in advance.Hi,
I have several E6420, O3010 and since a week also some E7440 and E7240 on site.
I never had issues using the current Dell PE package for MDT.
At the moment my PE contains only the drivers from the Dell PE 3.0 package (WinPE3.0-Drivers-A13-D67JC)
and all my systems mentioned abobe have no issues connecting to the deployment share.
(btw: I have also some older E6400, E6410 and O390 I do no longer support, they
are supported by the pack Dell-WinPE-Drivers-A05.CAB according
to the Dell site, but I just started a deplymenst on a E6410 and is is also workign with just the latest PE pack)
I'd
suggest you start over with your deplyoment share using at least MDT2012 Update 1.
Create a folder "PE" under "Out-of-Box Drivers" and extract latest Dell PE pack and import he drivers there
Create a selection profile e.g. "PE Drivers" and include just the "PE" folder created above
When configuring the Windows PE settings of your deployment share select "PE
Drivers" selection profile for the driver injection in the "Drivers and Patches" to keep the PE image free of not needed drives. -
I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package. The website and the instance of SQL Server with the agent and SSIS package are
on the same windows 2008 r2 server. When the button is operated no exceptions are raised but the SSIS package did not execute.
When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
The job failed. Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
Could someone show me what I need to do to get this to run? Thanks tonnes in advance for any help, RoscoeThis can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
I suggest you try using the SA account for the job as it does not require to poll the AD.
Arthur My Blog -
MDT 2012 'Failed to save Environment to (80070057) Error during Windows 7 x64 Pro Deployment
Hi There,
I've been using MDT for a little while now, but I'm having problems successfully deploying an image to a batch of new laptops. The laptop HDD's are completely blank, and I am PXE booting using an x64 Litetouch Image via WDS. I have successfully captured
my image from a reference laptop (the same model that I'm trying to image), and I am now trying to deploy it using a standard client task sequence.
The 'Install operating System' phase seems to go ok, but then sits for quite some time at the 'Applying Unattend.xml' stage, then eventually, I get a general error 'Task Sequence Failed - 80004005'. I then exit MDT (it doesn't reboot as it should), and let
the laptop boot, which it does, and logs straight on into Windows, but gives me error along the lines of 'can't find the litetouch script', which I assume means MDT hasn't been able to copy it across. The laptop is however joined to our domain, and I pretty
much just have to tick the 'require a password to log on to this computer' box in user accounts, and all looks ok.
So in summary, the image is applying, but the laptop is not rebooting and running the final cleanup scripts.
I have already changed the SATA mode to IDE, instead of AHCI, having read this sometimes causes problems. I also read that systems with UEFI BIOS can also cause problems with MDT, but I'm not sure if this is the case.
I have edited my customsettings.ini, to copy log files back to my server, which it has done for me. Having looked at the logs (with CM Trace), I can see these errors:
Failed to save environment to (80070057)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to persist execution state. Error 0x(80070057)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to save execution state and environment to local hard disk
TSManager 26/03/2014 15:48:09
1820 (0x071C)
The task sequence execution engine can not reboot the machine because we failed to persist execution environment
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Fatal error is returned in check for reboot request of the action (Restart computer).
Unspecified error (Error: 80004005; Source: Windows)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
An error (0x80004005) is encountered in execution of the task sequence
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Task Sequence Engine failed! Code: 80004005
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Any help you can give me would be great, as I'd like to get this process running properly.
Thanks,
SarahYou don't mention what kind of OS this is (Windows 7 Pro x64?)
This is a known issue/FAQ.
I would recommending using MDT 2012 (update 1) for UEFI machines.
Machines with uEFI 2.3.1 only support Windows 8.x.
http://technet.microsoft.com/en-us/library/hh824898.aspx
Recomendation: Convert the BIOS to CSM and/or upgrade to Windows 8.1 :^)
Keith Garner - keithga.wordpress.com -
Unable to determine the sharedness of /dev/sda, /dev/sdb, /dev/sdc on nodes
hello, pls how do i fix this issue, the two scripts ran on first node, but failed on second node, after running cluvfy this is the output:
using cluvfy for storage requirements
Verifying shared storage accessibility
Checking shared storage accessibility...
WARNING:
Unable to determine the sharedness of /dev/sda on nodes:
rac2,rac1
WARNING:
Unable to determine the sharedness of /dev/sdb on nodes:
rac2,rac1
WARNING:
Unable to determine the sharedness of /dev/sdc on nodes:
rac2,rac1
WARNING:
Unable to determine the sharedness of /dev/sdd on nodes:
rac2
Shared storage check failed on nodes "rac2,rac1".
Verification of shared storage accessibility was unsuccessful on all the nodes.
using cluvfy for system requirements
Verifying system requirement
Checking system requirements for 'crs'...
Check: Total memory
Node Name Available Required Comment
rac2 1011.13MB (1035400KB) 1GB (1048576KB) failed
rac1 1011.13MB (1035400KB) 1GB (1048576KB) failed
Result: Total memory check failed.
Check: Free disk space in "/tmp" dir
Node Name Available Required Comment
rac2 1.07GB (1119972KB) 400MB (409600KB) passed
rac1 1.09GB (1141784KB) 400MB (409600KB) passed
Result: Free disk space check passed.
Check: Swap space
Node Name Available Required Comment
rac2 2GB (2096472KB) 1.5GB (1572864KB) passed
rac1 2GB (2096472KB) 1.5GB (1572864KB) passed
Result: Swap space check passed.
Check: System architecture
Node Name Available Required Comment
rac2 i686 i686 passed
rac1 i686 i686 passed
Result: System architecture check passed.
Check: Kernel version
Node Name Available Required Comment
rac2 2.6.18-8.el5 2.6.9 passed
rac1 2.6.18-8.el5 2.6.9 passed
Result: Kernel version check passed.
Check: Package existence for "make-3.81"
Node Name Status Comment
rac2 make-3.81-1.1 passed
rac1 make-3.81-1.1 passed
Result: Package existence check passed for "make-3.81".
Check: Package existence for "binutils-2.17.50.0.6"
Node Name Status Comment
rac2 binutils-2.17.50.0.6-2.el5 passed
rac1 binutils-2.17.50.0.6-2.el5 passed
Result: Package existence check passed for "binutils-2.17.50.0.6".
Check: Package existence for "gcc-4.1.1"
Node Name Status Comment
rac2 gcc-4.1.1-52.el5 passed
rac1 gcc-4.1.1-52.el5 passed
Result: Package existence check passed for "gcc-4.1.1".
Check: Package existence for "libaio-0.3.106"
Node Name Status Comment
rac2 libaio-0.3.106-3.2 passed
rac1 libaio-0.3.106-3.2 passed
Result: Package existence check passed for "libaio-0.3.106".
Check: Package existence for "libaio-devel-0.3.106"
Node Name Status Comment
rac2 libaio-devel-0.3.106-3.2 passed
rac1 libaio-devel-0.3.106-3.2 passed
Result: Package existence check passed for "libaio-devel-0.3.106".
Check: Package existence for "libstdc++-4.1.1"
Node Name Status Comment
rac2 libstdc++-4.1.1-52.el5 passed
rac1 libstdc++-4.1.1-52.el5 passed
Result: Package existence check passed for "libstdc++-4.1.1".
Check: Package existence for "elfutils-libelf-devel-0.125"
Node Name Status Comment
rac2 elfutils-libelf-devel-0.125-3.el5 passed
rac1 elfutils-libelf-devel-0.125-3.el5 passed
Result: Package existence check passed for "elfutils-libelf-devel-0.125".
Check: Package existence for "sysstat-7.0.0"
Node Name Status Comment
rac2 sysstat-7.0.0-3.el5 passed
rac1 sysstat-7.0.0-3.el5 passed
Result: Package existence check passed for "sysstat-7.0.0".
Check: Package existence for "compat-libstdc++-33-3.2.3"
Node Name Status Comment
rac2 missing failed
rac1 missing failed
Result: Package existence check failed for "compat-libstdc++-33-3.2.3".
Check: Package existence for "libgcc-4.1.1"
Node Name Status Comment
rac2 libgcc-4.1.1-52.el5 passed
rac1 libgcc-4.1.1-52.el5 passed
Result: Package existence check passed for "libgcc-4.1.1".
Check: Package existence for "libstdc++-devel-4.1.1"
Node Name Status Comment
rac2 libstdc++-devel-4.1.1-52.el5 passed
rac1 libstdc++-devel-4.1.1-52.el5 passed
Result: Package existence check passed for "libstdc++-devel-4.1.1".
Check: Package existence for "unixODBC-2.2.11"
Node Name Status Comment
rac2 unixODBC-2.2.11-7.1 passed
rac1 unixODBC-2.2.11-7.1 passed
Result: Package existence check passed for "unixODBC-2.2.11".
Check: Package existence for "unixODBC-devel-2.2.11"
Node Name Status Comment
rac2 unixODBC-devel-2.2.11-7.1 passed
rac1 unixODBC-devel-2.2.11-7.1 passed
Result: Package existence check passed for "unixODBC-devel-2.2.11".
Check: Package existence for "glibc-2.5-12"
Node Name Status Comment
rac2 glibc-2.5-12 passed
rac1 glibc-2.5-12 passed
Result: Package existence check passed for "glibc-2.5-12".
Check: Group existence for "dba"
Node Name Status Comment
rac2 exists passed
rac1 exists passed
Result: Group existence check passed for "dba".
Check: Group existence for "oinstall"
Node Name Status Comment
rac2 exists passed
rac1 exists passed
Result: Group existence check passed for "oinstall".
Check: User existence for "nobody"
Node Name Status Comment
rac2 exists passed
rac1 exists passed
Result: User existence check passed for "nobody".
System requirement failed for 'crs'
Verification of system requirement was unsuccessful on all the nodes.
cluvfy check for node connectivity
Verifying node connectivity
Checking node connectivity...
Interface information for node "rac2"
Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address
eth0 192.168.2.102 192.168.2.0 0.0.0.0 192.168.2.1 00:0C:29:4D:18:BA
eth1 192.168.0.102 192.168.0.0 0.0.0.0 192.168.2.1 00:0C:29:4D:18:C4
Interface information for node "rac1"
Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address
eth0 192.168.2.101 192.168.2.0 0.0.0.0 192.168.2.1 00:0C:29:A5:25:87
eth1 192.168.0.101 192.168.0.0 0.0.0.0 192.168.2.1 00:0C:29:A5:25:91
Check: Node connectivity of subnet "192.168.2.0"
Source Destination Connected?
rac2:eth0 rac1:eth0 yes
Result: Node connectivity check passed for subnet "192.168.2.0" with node(s) rac2,rac1.
Check: Node connectivity of subnet "192.168.0.0"
Source Destination Connected?
rac2:eth1 rac1:eth1 yes
Result: Node connectivity check passed for subnet "192.168.0.0" with node(s) rac2,rac1.
Interfaces found on subnet "192.168.2.0" that are likely candidates for a private interconnect:
rac2 eth0:192.168.2.102
rac1 eth0:192.168.2.101
Interfaces found on subnet "192.168.0.0" that are likely candidates for a private interconnect:
rac2 eth1:192.168.0.102
rac1 eth1:192.168.0.101
WARNING:
Could not find a suitable set of interfaces for VIPs.
Result: Node connectivity check passed.
Verification of node connectivity was successful.
Verifying administrative privileges
Checking user equivalence...
Check: User equivalence for user "oracle"
Node Name Comment
rac2 passed
rac1 passed
Result: User equivalence check passed for user "oracle".
Verification of administrative privileges was successful.Hi,
Refer --- *19. Pre-Installation Tasks for Oracle Clusterware* section from the below link:
http://www.oracle.com/technology/pub/articles/hunter_rac11gr1_iscsi_2.html
See this thread also seems to be same with ur issue:
Clusterware (Unable to determine the sharedness of) in VMware 2.0x server
Regards,
Xaheer
Maybe you are looking for
-
I am using apple tv with macbook pro 2012 with os mavrick ...when I play video, my laptop speaker plays sound for that video instead of my TV where apple tv is connected ...why it is like that ?
-
10g Releae 1 move from J-Initiator to JRE
Hello everyone, Hope you folks can help me out on this problem. We are using 10g release 1 - Version 9.0.4 It's installed on unix solaris. The end users access the application through Internet explorer 6 and J-Initiator and webutil. Currently the ope
-
Help! Which firewire for migration
Just bought a new iMac - and didn't know about needing a firewire to transfer info from my old Mac (the cute little egg one). I've been to Best Buy TWICE - first I got a six pin firewire which would work in my old computer but not my new one. Went BA
-
How to sync kalendar with goolge calendar automatically after upgrading to mountain lion?
Hello, after upgrading to OS X Moutain Lion on my MacBook Pro the calendar is not automatically syncronised with my google caledar even the account is set up properly. It seems the calendar has no contact at all my google account. It still works on m
-
Grouping on x-axis in Graphics 6i
Hi, I have a chart with Y-axis as Count and X-axis has 3 sets of groups, MJ,MN,CR. Currently my Graph looks like this : | | | | | | _____________