WIM is not visible after import
-
Thursday, November 08, 2012 12:37 AM
HI All,
I just try to capture the current Win7 x64 bit laptop and found capture successfully and import to OS successfully but i cannot see the image?
This is the settings
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=NO
DoNotCreateExtraPartition=YES
BackupDrive=ALL
ComputerBackupLocation=\\exmelmdt01\D$\CaptureOS
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=NO
SkipBitLocker=NO
This is the image info
D:\DeploymentShare\Tools\x86>imagex /info "D:\DeploymentShare\Operating Systems\
CAPWIN7LAPTOP/capwin7laptop.wim"
ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385
WIM Information:
----------------
Path: D:\DeploymentShare\Operating Systems\CAPWIN7LAPTOP\capwin7laptop.wi
m
GUID: {78503906-d38e-4169-bf63-6cc2a131cf23}
Image Count: 3
Compression: LZX
Part Number: 1/1
Attributes: 0x8
Relative path junction
Available Image Choices:
------------------------
<WIM>
<TOTALBYTES>7386474590</TOTALBYTES>
<IMAGE INDEX="1">
<DIRCOUNT>5</DIRCOUNT>
<FILECOUNT>4</FILECOUNT>
<TOTALBYTES>256186798</TOTALBYTES>
<HARDLINKBYTES>0</HARDLINKBYTES>
<CREATIONTIME>
<HIGHPART>0x01CDBD39</HIGHPART>
<LOWPART>0xCB5F45EA</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CDBD39</HIGHPART>
<LOWPART>0xCB61A74B</LOWPART>
</LASTMODIFICATIONTIME>
<NAME>CAPWIN7LAPTOPCDrive</NAME>
<FLAGS>PROFESSIONAL</FLAGS>
</IMAGE>
<IMAGE INDEX="2">
<DIRCOUNT>16398</DIRCOUNT>
<FILECOUNT>80341</FILECOUNT>
<TOTALBYTES>20521326708</TOTALBYTES>
<HARDLINKBYTES>4852434907</HARDLINKBYTES>
<CREATIONTIME>
<HIGHPART>0x01CDBD3C</HIGHPART>
<LOWPART>0xF407C000</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CDBD3C</HIGHPART>
<LOWPART>0xF621B6FE</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoftr Windowsr Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>CAPWIN7LAPTOPDDrive</NAME>
<FLAGS>PROFESSIONAL</FLAGS>
</IMAGE>
<IMAGE INDEX="3">
<DIRCOUNT>1488</DIRCOUNT>
<FILECOUNT>2314</FILECOUNT>
<TOTALBYTES>1354433148</TOTALBYTES>
<HARDLINKBYTES>131072</HARDLINKBYTES>
<CREATIONTIME>
<HIGHPART>0x01CDBD3D</HIGHPART>
<LOWPART>0x314C0AED</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CDBD3D</HIGHPART>
<LOWPART>0x3150CDAE</LOWPART>
</LASTMODIFICATIONTIME>
<NAME>CAPWIN7LAPTOPEDrive</NAME>
<FLAGS>PROFESSIONAL</FLAGS>
</IMAGE>
</WIM>
D:\DeploymentShare\Tools\x86>Whats wrong?
All Replies
-
Thursday, November 08, 2012 5:09 AM
You've captured it to \\exmelmdt01\D$\CaptureOS
not D:\DeploymentShare\Operating Systems\CAPWIN7LAPTOP\capwin7laptop.wim (that's a different image)
Blog: http://scriptimus.wordpress.com
-
Thursday, November 08, 2012 5:43 AM
HI Andrew,
True, But i was select MOVE and this is the WIM file. I think the issue with multi Partition?
AS
-
Thursday, November 08, 2012 6:13 PM
It looks like it's captured 3 partitions
<WIM>
<TOTALBYTES>7386474590</TOTALBYTES>
<IMAGE INDEX="1">
<NAME>CAPWIN7LAPTOPCDrive</NAME>
</IMAGE>
<IMAGE INDEX="2">
<NAME>CAPWIN7LAPTOPDDrive</NAME>
</IMAGE>
<IMAGE INDEX="3">
<NAME>CAPWIN7LAPTOPEDrive</NAME>
</IMAGE>
</WIM>It looks like the D drive, index 2 was the system partition.
If this doesn't help, then please clarify what results you are expecting to find and what the issue is.
Blog: http://scriptimus.wordpress.com
-
Thursday, November 08, 2012 11:05 PM
HI Andrew,
The issue is this WIM cannot see it after Import. So something not correct with this capture?
Can some one step me how to capture Multi Partition PC with MDT 2012
AS
-
Friday, November 09, 2012 4:01 PM
Note, you can only import a sysprepped imaged into MDT, not a backup.
Are you trying to create a reference image with multiple partitions in order to deploy this to many computers?
Blog: http://scriptimus.wordpress.com
-
Sunday, November 11, 2012 2:36 AM
MDT most likely does not recognize your image properly due to it containing regular data partitions as well.
You should export index number 2 to a new .wim file that will contain just the OS that you've captured and then import that new OS image. You might also need to check your OperatingSystems.xml file in the Control folder to see if there are references to this particular image that you've tried to Import and fails to display in the workbench. I would recommend to delete all entries that relate to the image file that does not show up in the workbench (make sure to make a backup before you edit the file) and delete the file from the DS manually.
Can you tell us how you created this image that you've captured? Since normally the task sequence to capture the OS image does not include regular partitions.
If you want to deploy multiple partitions using MDT, simply create a new .wim file that contains your other partition(s) and deploy these "manually" using dism (if you're using WinPE 6.2/Win8) or ImageX after the OS has been deployed. What I mean with manually is to create a new step in the task sequence that runs the specific command line in order to deploy that image onto a particular partition.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1- Edited by Stephan Schwarz Sunday, November 11, 2012 2:40 AM
-
Monday, November 12, 2012 1:49 AM
Hi All,
"Can you tell us how you created this image that you've captured? Since normally the task sequence to capture the OS image does not include regular partitions."
Now i managed to capture the C: and D: by adding BackupDrive=ALL to my customsettings.ini
In my task sequence I modified the "Format and Partition Disk" step to create a 150GB partition and create a variable for this partition called "DataDisk".
Then I added another command line step after the existing "Install Operating System" step with the following command:
"%DEPLOYROOT%\Tools\x64\Imagex.exe" /apply "%DEPLOYROOT%\Operating Systems\CAPWIN7LAPTOP\CAPWIN7LAPTOP.wim" 2 %DataDisk%
BUT I'm getting the error when when deploying? smsts.log
!--------------------------------------------------------------------------------------------! TSManager 8/11/2012 9:44:30 PM 1500 (0x05DC)
Expand a string: WinPEandFullOS TSManager 8/11/2012 9:44:30 PM 1500 (0x05DC)
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 8/11/2012 9:44:30 PM 1500 (0x05DC)
Process completed with exit code 5 TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
!--------------------------------------------------------------------------------------------! TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Failed to run the action: Install Operating System.
Access is denied. (Error: 00000005; Source: Windows) TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Sending status message . . . TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Set a global environment variable _SMSTSLastActionRetCode=5 TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Clear local default environment TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Let the parent group (Install) decides whether to continue execution TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Access is denied. (Error: 00000005; Source: Windows) TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Sending status message . . . TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Task Sequence Engine failed! Code: enExecutionFail TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
**************************************************************************** TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Task sequence execution failed with error code 80004005 TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Cleaning Up. Removing Authenticator TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Cleaning up task sequence folder TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
-
Monday, November 12, 2012 2:42 AM
Hi,
Please separate the OS and Data image from the .wim file you captured, and only import the OS image into the MDT Workbench. I don't think your second step will cause any issues in how you plan to deploy the Data image, that seems good to me.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1 -
Monday, November 12, 2012 6:09 AM
HI Stephan,
OK, I have followed the following http://kantzy.wordpress.com/2012/01/04/convert-a-multi-partition-windows-xp-ghost-image-to-wim-image-to-deploy-using-mdt/#comments
1. create the new TS to capture D Drive. Now i got two images OS and Ddrive.
2. Import the OS into the osdeployment share
3. Create Ddrive variables as per above
4. login to the laptop and run the ltouch.vbs
Got the following error?
Expand a string: WinPEandFullOS TSManager 8/11/2012 9:44:30 PM 1500 (0x05DC)
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 8/11/2012 9:44:30 PM 1500 (0x05DC)
Process completed with exit code 5 TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
!--------------------------------------------------------------------------------------------! TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Failed to run the action: Install Operating System.
Access is denied. (Error: 00000005; Source: Windows) TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Sending status message . . . TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Set a global environment variable _SMSTSLastActionRetCode=5 TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Clear local default environment TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Let the parent group (Install) decides whether to continue execution TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Access is denied. (Error: 00000005; Source: Windows) TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Sending status message . . . TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 8/11/2012 10:05:26 PM 1500 (0x05DC)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Task Sequence Engine failed! Code: enExecutionFail TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
**************************************************************************** TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Task sequence execution failed with error code 80004005 TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Cleaning Up. Removing Authenticator TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Cleaning up task sequence folder TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Command line for extension .exe is "%1" %* TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Set command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
Executing command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister TSManager 8/11/2012 10:05:27 PM 1500 (0x05DC)
==========[ TsProgressUI started in process 1060 ]========== TsProgressUI 8/11/2012 10:05:27 PM 1048 (0x0418)
What's wrong with my setup?
Note: Laptop is x64 Windows 7 OS so i used this to capture
"%DeployRoot%\Tools\X64\imagex" /capture D: "%ComputerBackupLocation%\XP_D_Drive.wim" "D Drive"
I used this to Deploy
"%DeployRoot%\Tools\X64\imagex" /apply "%DeployRoot%\Operating Systems\Win7_D_Drive\XP_D_Drive.wim" 1 %DDrive%
Do i need to run on "%DeployRoot%\Tools\X86\imagex" ? What is this access denied error Local admin setup?
AS
- Edited by AUSSUPPORT Monday, November 12, 2012 6:14 AM
-
Monday, November 12, 2012 3:49 PM
Please create a zip file containing all log files (you can use F8 in WinPE to open up a command prompt in order to copy the files elsewhere). Also include your task sequence, this would be deploymentshare\tasksequenceID\ts.xml and the customsettings.ini.
Make sure to remove sensitive information before you post this online.
Share the zip file for example with skydrive, or any other file sharing service.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1 -
Wednesday, November 14, 2012 5:38 AM
HI All,
I have managed to Install the OS Drive but when it's failed after trying to install the D Drive?
SMSts.log
Expand a string: WinPEandFullOS TSManager 13/11/2012 8:37:31 PM 1536 (0x0600)
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 13/11/2012 8:37:31 PM 1536 (0x0600)
Process completed with exit code 0 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
!--------------------------------------------------------------------------------------------! TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Successfully complete the action (Install Operating System) with the exit win32 code 0 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Sending status message . . . TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Deleting file without retry TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Clear local default environment TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Updated security on object C:\_SMSTaskSequence. TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSInstructionStackString=42 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a TS execution environment variable _SMSTSInstructionStackString=42 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Save the current environment block TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Successfully save execution state and environment to local hard disk TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Start executing an instruciton. Instruction name: D Drive. Instruction pointer: 44 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSCurrentActionName=D Drive TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a local default variable PackageID TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a local default variable RunAsUser TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a local default variable SMSTSRunCommandLineUserName TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a local default variable SMSTSRunCommandLineUserPassword TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a local default variable LoadProfile TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Expand a string: "%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\DDrive\XP_D_Drive.wim" 1 %DDrive% TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Expand a string: TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Set command line: "%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\DDrive\XP_D_Drive.wim" 1 %DDrive% TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Start executing the command line: "%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\DDrive\XP_D_Drive.wim" 1 %DDrive% TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
!--------------------------------------------------------------------------------------------! TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Expand a string: WinPEandFullOS TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Executing command line: "%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\DDrive\XP_D_Drive.wim" 1 %DDrive% TSManager 13/11/2012 8:58:22 PM 1536 (0x0600)
Process completed with exit code 2 TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
!--------------------------------------------------------------------------------------------! TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Failed to run the action: D Drive.
The system cannot find the file specified. (Error: 00000002; Source: Windows) TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Sending status message . . . TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Set a global environment variable _SMSTSLastActionRetCode=2 TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Clear local default environment TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Let the parent group (Install) decides whether to continue execution TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Failed to run the last action: D Drive. Execution of task sequence failed.
The system cannot find the file specified. (Error: 00000002; Source: Windows) TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Sending status message . . . TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Task Sequence Engine failed! Code: enExecutionFail TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
**************************************************************************** TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Task sequence execution failed with error code 80004005 TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Cleaning Up. Removing Authenticator TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Cleaning up task sequence folder TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Command line for extension .exe is "%1" %* TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Set command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
Executing command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister TSManager 13/11/2012 8:58:23 PM 1536 (0x0600)
==========[ TsProgressUI started in process 1856 ]========== TsProgressUI 13/11/2012 8:58:23 PM 992 (0x03E0)
Command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister TsProgressUI 13/11/2012 8:58:23 PM 992 (0x03E0)
Unregistering COM classes TsProgressUI 13/11/2012 8:58:23 PM 992 (0x03E0)
Unregistering class objects TsProgressUI 13/11/2012 8:58:23 PM 992 (0x03E0)
Shutdown complete. TsProgressUI 13/11/2012 8:58:23 PM 992 (0x03E0)
BDD.LOG
Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml LTIApply 13/11/2012 8:56:00 PM 0 (0x0000)
Copied unattend.xml to C:\Windows\Panther for image apply. LTIApply 13/11/2012 8:56:00 PM 0 (0x0000)
About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch LTIApply 13/11/2012 8:56:00 PM 0 (0x0000)
Command has been started (process ID 792) LTIApply 13/11/2012 8:56:00 PM 0 (0x0000)
Console > Deployment Image Servicing and Management tool LTIApply 13/11/2012 8:56:01 PM 0 (0x0000)
Console > Version: 6.1.7600.16385 LTIApply 13/11/2012 8:56:01 PM 0 (0x0000)
Console > Image Version: 6.1.7600.16385 LTIApply 13/11/2012 8:56:03 PM 0 (0x0000)
Console > The operation completed successfully. LTIApply 13/11/2012 8:58:21 PM 0 (0x0000)
Return code from command = 0 LTIApply 13/11/2012 8:58:22 PM 0 (0x0000)
LTIApply processing completed successfully. LTIApply 13/11/2012 8:58:22 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
Unable to copy log to the network as no SLShare value was specified. LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
CleanStartItems Complete LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
Unregistering TSCore.dll. LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
About to run command: wscript.exe "X:\Deploy\Scripts\LTICleanup.wsf" LiteTouch 13/11/2012 8:58:23 PM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 LTICleanup 13/11/2012 8:58:23 PM 0 (0x0000)
Removing AutoAdminLogon registry entries LTICleanup 13/11/2012 8:58:24 PM 0 (0x0000)
VSSMaxSize not specified using 5% of volume. LTICleanup 13/11/2012 8:58:24 PM 0 (0x0000)
Logs contained 7 errors and 0 warnings. LTICleanup 13/11/2012 8:58:25 PM 0 (0x0000)
-
Wednesday, November 14, 2012 5:42 AM[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
-
Wednesday, November 14, 2012 5:44 AM
ts.xml
https://skydrive.live.com/redir?resid=FA86FA92E71E7D06!217
-
Thursday, November 15, 2012 4:09 AM
can you pls look my issue?Please create a zip file containing all log files (you can use F8 in WinPE to open up a command prompt in order to copy the files elsewhere). Also include your task sequence, this would be deploymentshare\tasksequenceID\ts.xml and the customsettings.ini.
Make sure to remove sensitive information before you post this online.
Share the zip file for example with skydrive, or any other file sharing service.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1 -
Thursday, November 15, 2012 10:16 PM
Hi, I've taken a look at your logfiles and task sequence.
It's now also clear to me why you get these errors.
I'll elaborate; first off, your command to deploy the image is fine.
The issue at hand is that you're trying to deploy this task sequence from within Windows, when this is done the deployment type is set to "REFRESH". During a refresh task sequence, the disk will not be reformatted or repartitioned. You can verify this by opening the task sequence node [Preinstall], the [New Computer Only] node, has the requirement DeploymentType equals NEWCOMPUTER.
Since the Format and Partition disk step is skipped during a refresh, the second partition will not be assigned the drive letter variable "DDrive". This has as a direct result that ImageX will fail to apply your image.
I'm pretty sure your task sequence will complete normally if you execute it from within Windows PE or from a "clean" HDD.
If this needs to work as well during a refresh scenario, for computers that already have a Data partition, you should create 2 times the step "D Drive" (I would name this a bit better, something like "Apply Data Image"). One that has the current command line, and the task sequence variable requirement to have DeploymentType equal NEWCOMPUTER, and another one, that uses fixed drive letters for the "REFRESH" scenario and create a statement that it should only be executed if the DeploymentType equals "Refresh". The only issue you might run into with the second one are the fixed drive letters, that these are not always the same on each PC (for example card readers could mess up the drive letters). In that case I'd use a script that checks the name of the drive label (lets day "Data") and re-assign that drive always a specific drive letter within WinPE.
I hope this makes sense,
Kind regards,
Stephan Schwarz.
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1 -
Thursday, November 15, 2012 11:05 PM
HI Stephan,
Thank you. I also found this custom ini files so if i add that REFRESH to the TS will that work?
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac /lae
SkipAppsOnUpgrade=NO
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipDeploymentType=YESDeploymentType=REFRESH
SkipDomainMembership=YES
JoinDomain=mdt
DomainAdmin=Administrator
DomainAdminDomain=mdt
DomainAdminPassword=MyPassw0rd
SkipUserData=yes
UserDataLocation=AUTOUDShare=\\mdt1\UserData
UDDir=%ComputerName%
SkipComputerBackup=YES
ComputerBackuplocation=AUTO
BackupShare=\\Servername\Backupsharename
BackupDir=%ComputerName%
SkipTaskSequence=YESTaskSequenceID=DEPWIN7PROX86
SkipComputerName=YES
OSDComputerName=%ComputerName%
SkipPackageDisplay=YES
SkipApplications=YES
UserID=Administrator
UserDomain=mdt
UserPassword=MyPassw0rd
SkipBitLocker=YES
SkipSummary=YES -
Friday, November 16, 2012 8:59 AM
If this needs to work as well during a refresh scenario, for computers that already have a Data partition, you should create 2 times the step "D Drive" (I would name this a bit better, something like "Apply Data Image"). One that has the current command line, and the task sequence variable requirement to have DeploymentType equal NEWCOMPUTER, and another one, that uses fixed drive letters for the "REFRESH" scenario and create a statement that it should only be executed if the DeploymentType equals "Refresh". The only issue you might run into with the second one are the fixed drive letters, that these are not always the same on each PC (for example card readers could mess up the drive letters). In that case I'd use a script that checks the name of the drive label (lets day "Data") and re-assign that drive always a specific drive letter within WinPE.
HI Stephen,
Pls give me the steps to follow...
AS
.png)
