Techies,
The following update to resolve this problem is available for download from the Microsoft Download Center:
Important - This update requires you to manually update theMicrosoft.BDD.Utility.dll files in the MDT, As well In New DeploymentShare.
Please remember to mark the replies as answer | Vote as helpful if they help, It will be easier for others to identify solutions. Thank You!!
What is the correct version of MDT and ADK to support 2004 and backwards?
Also, is there a new ADK WinPE needed for 2004 as well?
Thanks!
So with 1809 I updated my Share and took the ISO to my desktop and have my VM's boot to it.
Now with 2004 and that UEFI fix being added, di I have to have a separate LiteTouch.ISO for 2004 and one for 1809?
I'm just trying to get past the logic on that.
Thanks
I just only started implementing a suspend in my TS's, and pointing to a LiteTouchPE.iso
What must I do with my VM having a suspend when I upgrade the OS on that VM? The LiteTouch I'm sure is referring to the previous OS so I don't believe it will work.
My current VM's are 1803 and I have a standard upgrade TS created to go to 1809. Those VM's that don't have a suspend should work just fine but I'm concerned about those with a suspend shortcut.
Any suggestions?
I had a VM at 1809 and ran Windows Updates to get to 1909. I need it to be at 2004.
When I ran Windows Updates the first time, I got to 1909 easily, but every time now that I try to run it again, it says
'cannot connect to the update service'.
The other questions I have about my MDT Task Sequence is, the Suspend created a Resume button in 1809.
Now if I ever get to 2004, what will happen? Will it still try to read the info from 1809 to do the Capture?
I did it the wrong way, so I've read, but I downloaded the Windows Update Tool and it upgraded my VM to 2004.
When I click on Resume, nothing happens at all. So, I set my VM back to 1909 and I will wait to hear hopefully why
this VM that got upgraded from 1809 to 1909 through Windows Updates now tells me it can't connect the update server.
Thanks
When running Windows Update step in a task sequence(ZTIWindowsUpdate.wsf) on a Windows 10 2004 build, updates are found, but all of them are being skipped. This is not the case with a 1909 based OS. This seems to be linked to InstallationBehavior.CanRequestUserInput, this is setting bInstall to False for every update.
<![LOG[Start Search...]LOG]!><time="16:18:05.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ SKIP - ca3bb521-a8ea-4e26-a563-2ad6e3108b9a - Microsoft Silverlight (KB4481252) - 12 MB]LOG]!><time="16:18:34.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ SKIP - 2221dd34-39bb-4f16-b320-be49fe4a6b95 - Windows Malicious Software Removal Tool x64 - v5.82 (KB890830) - 29 MB]LOG]!><time="16:18:34.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ SKIP - f36bfc14-dc6c-48eb-a76e-c21828bb4ff6 - 2020-06 Security Update for Adobe Flash Player for Windows 10 Version 2004 for x64-based Systems (KB4561600) - 21 MB]LOG]!><time="16:18:34.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ SKIP - 5faf5c4c-fa1d-4adc-9d54-6fd6d21ab0e6 - Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.317.1010.0) - 106 MB]LOG]!><time="16:18:34.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ SKIP - 8ab1c3b3-511d-4e32-a7d8-75722464fa0f - 2020-06 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4557957) - 83 GB]LOG]!><time="16:18:34.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Scan complete, ready to install updates. Count = 0]LOG]!><time="16:18:34.000+000" date="06-09-2020" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
So far I've only tested this in a VM.
Windows 10 Pro x64 build 2004
MDT build 8456
I have windows deployment toolkit installed on a server on my test network. I am trying to teach myself how to configure the rules custom .ini file. I am trying to skip product key, but the target computer is still asking for the product key during deployment. I also tried to skip windows updates, the updates are still running on the target computer during deployment. The command I am using is:
SkipWindowsUpdates=yes
Is the the command correct? Are the commands in the correct place? I have included a screenshot.
Any assistance will be appreciated.
Thank you.
I ran windows updates on a Hyper-V VM which is not on our domain. My VM went from 1809 to 1909 after I ran Updates twice.
I saw the Feature Update to 1909 and that got me to 1909.
I need to be at 2004. So, after running windows updates again, it says it couldn't connect to the update service. Try again later, make sure you're connected to the internet.
I found out that running the MS Update program isn't an acceptable method of upgrading a VM because it won't work properly
in MDT. So I'm just stuck at 1909 and have no idea if something broke when I went to 1909.
Anyone else see this? Any suggestion?
Hello,
I am trying to capture fresh installed W7 Pro and get an error (see below).
The situation. I successfully captured and deployed W7 computers ( French version) on Latest MDT.
Now I am trying to capture freshly installed W7 Pro (En) and it failes. I boot from Lite Touch 64 and tried through PXE of WDS (I have the same Lite Touch image on it). Don't think that the language version matter, but to eliminate doubts I created new capture image frrom W7 En. The same result. Before posting I searched WEB. There are topics on my error but not related to my scenario. W7 Pro doesn't have Bit Locker. I have plenty of space on server and source machine. Where is the glitch? The client is new HP Core 2 Duo box. Thanks. Michael.
<![LOG[ZTI ERROR - Unhandled error returned by LTIApply: (-2147024784 0x80070070)]LOG]!><time="14:14:50.000+000" date="11-03-2010" component="LTIApply" context="" type="3" thread="" file="LTIApply">
Messages from the task sequenc engine:
Gailed to run the action: Apply Windows PE
There is not enough space on the disk. Error: 80070070; Source: Windows
Hi
I'm trying to capture an image of a machine using the 'Capture Machine' task sequence on MDT 2013 Update 2.
But when I go to do it I get 10 errors and 2 warnings:
------------------------------------------------------------------------------------------------------------------------
ZTI ERROR - Unhandled error returned by LITApply: (-2147024784 0x80070070)
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Apply Windows PE.
There is not enough space on the disk (Error: 80070070; 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: Apply Windows PE. execution of task sequence failed.
There is not enough space on the disk. (Error: 80070070; Source: Windows)
Task sequence engine failed Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetnamedSecurityInfo() failed
SetObjectOwner () failed 0x80070005
-------------------------------------------------------------------------------------------------------------------
So I went into DISKPART for Disk 0 and had a look at the partitions:
Partiton 1 Recovery 450MB
Partiton 2 System 100MB
Partition 3 Reserved 128MB
Partiton 4 Primary 57GB
My assumption is that it is trying to install the Windows PE onto Partition 1 first that doesn't have enough space? I can't find anything in the task sequence that lets me change the 'Capture Machine' task sequence to use the whole disk or selected partitions and I know you cannot change partition numbers in DISKPART.
Also, what does it actually mean when it is trying to 'Install Windows PE'?
I can't do a clean install of windows because it is a Zebra Industrial tablet and doing a clean install of windows gets messy because there are no driver downloads on their website, only an installation image. I've tried extracting the drivers from a working tablet into a clean installed one but had no luck. The touch screen or network does not work.
Any ideas and suggestions will be greatly appreciated.
Hi,
I'm currently having issue with MDT deployment. Deployed OS is 1909 and I'm using 1903 ADK.
MS Server 2016 and Deployment Workbench: 6.3.8456.1000.
All the sequences finishes including the last step which is renaming the local admin, then Lite Touch progress bar disappears but the Final Summary doesn't pop-up even though SkipFinalSummary wasn't added on customsettings.ini and the drive to the MDT server is still mapped. If there was an error, with my sequences the Final Summary usually shows up and displays them but the Final Summary doesn't even show-up. When I restart the computer it shows "Dirty Environment".
I have re-created the TS and it is still getting the same error. Other TS on the same Deployment are having no problems. Everything on the TS are installed and done, it just doesn't seem to end properly.
I read that in 2004 you have to run a Fix UEFIDetection.wsf which I downloaded and added in Preinstall and at the end of my TS as Johan has writte. When I run the VM to boot to the BUILD LiteTouch ISO, I get
Failed to save environment (80070057)
Failed to run the action: Fix UEFI Detection
Incorrect function: (Error:0000001 Source Windows)
If I omit the Fix UEFIDetection, I get the error that this fix is supposed to fix.
Does anyone have a solution to this problem?
I left MDT the same version for 1809 (which it says it supposed to work, and I upgraded my ADK and ADK WinePE.
I read many articles/blogs that ADK for 2004 has a bug with UEFI/BIOS and there's a work-around from Johan.
That, for me, fails...and the next thing I found was that people we reverting ADK back to 1809.
That's all great. I created a VM with a Suspend. Now that I launch the Resume, it shows 'Loading Files'
about 4 times, then the VM shuts down.
What is going on? Should I use ADK for 2004 (and PE) or 1809? I can't get it to Capture.
Right after Sysprep finishes, it goes to a black screen and then that's when I get Loading Files over and over.
We recently upgraded our MDT Database from 2008 to 2016 and the new server uses TLS 1.2 only. When attempting to connect to the DB using TCP/IP on a specific port we receive this error in the BDD Logs while retrieving the location settings in bootstrap.ini.
[DBNETLIB][ConnectionOpen SECDoClientHandshake()]SSL Security error
Also, using a custom HTA front end, when trying to retrieve data from the DB we get the same message.
sconn="Provider=SQLOLEDB;OLE DB Services=0;Data Source=SomeServerName\SomeInstance,SomePort;Initial Catalog=SomeDatabase;Network Library=DBMSSOCN;Integrated Security=SSPI"
Searching the web I found that the older SQLOLEDB provider is not capable of supporting TLS 1.2
Does anyone know what is required to make MDT communicate to the DB using TLS 1.2 only?
Sysprep and Capture task sequence fails when it tries to capture Windows 10 Professional.
OS: Windows Server 2008 Enterprise 64bit
MDT (6.3.8450.1000)
Windows Assessment and Deployment Kit - Windows 10
Windows Automated Installation Kit
Operating System deployment did not complete successfully.
Please review the log file to determine the cause of the problem.
During the deployment process, 83 errors and 23 warnings were reported.
Unexpected return code while re-arming Office 2010, RC = -1073425657
Unexpected return code while re-arming Office 2013, RC = -1073425657
Unexpected return code while re-arming Office 2016, RC = -1073425657
Expected image state is IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE, actual image state is
IMAGE_STATE_COMPLETE, sysprep did not succeed.
FAILURE (6192): ERROR - Sysprep did not complete successfully, check
C:\WIN DOWS\system32\sysprep\panther\setupact.log for details
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoo failed.
SetObjectOwnero failed. 0x80070005.
RegoueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoo failed.
SetObjectOwnerO failed. 0x80070005.
RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoo failed.
SetObjectOwnero failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfo() failed.
SetObjectOwnero failed. 0x80070005.
RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoQ failed.
SetObjectOwnero failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsReg Val ue0 is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoo failed.
SetObjectOwnero failed. 0x80070005.
RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoo failed.
SetObjectOwnero failed. 0x80070005.
RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTs RegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfoQ failed.
SetObjectOwnero failed. 0x80070005.
RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Execute Sysprep.
Unknown error (Error: 00001830; Source: Unknown)
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: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 00001830; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecuritylnfo0 failed.
SetObjectOwner() failed. 0x80070005.
RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValueo is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
I have a VM at 1809 and Windows Updates took me to 1909. Now when I run it again, to get to 2004, it says cannot connect to the windows update service.
Is 2004 just not yet available via Windows Updates.....or how is anyone else successfully doing this?
Hi all,
I'm setting up MDT in a new environment, and I've almost got it all worked out (I hope!), minus one holdup.
When I run the deployment TS, everything goes well in the WinPE stages, it installs the OS and then boots to Windows. From here, it just stops. The TaskSequence folder is still in the root, so I know the TS is still running. BDD says look to SMSTS, where I just get these errors in succession:
Failed to create C:\_SMSTaskSequence (3) TSManager 6/19/2020 12:21:58 PM 1076 (0x0434)
Failed to create user-specified local data path C:\_SMSTaskSequence. Error 0x80070003 TSManager 6/19/2020 12:21:58 PM 1076 (0x0434)
I have the SMSTS log, I just can't link it here yet? I guess my account is too new.
The last thing recorded in BDD is the domain join (which it doesn't actually do) and a reboot.
I'm happy to post the BDD if anyone would like it, I just need to finish scrubbing the domain info.
When monitoring, it doesn't show any errors and just hangs at step 54.
TL;DR, MDT is essentially just deploying my custom WIM and then the task sequence freezes.
I have a VM which is not on any domain. Hyper-V is on a server which is on the domain in a GPO-Free OU.
I upgraded my 1809 VM to 1909 smoothly. I then tried to upgrade the VM to 2004 and it said, you do not have a connection to the update service.
I tried this on a physical machine and found out I had to use a MIFI (off our network completely) and then I could get more
Updates for 1909. Apparently 2004 isn't available yet because subsequent updates just said I'm up to date.
So my question is, with my VM's off the Domain, I still get the 'no connection to the update service' message. I'm not sure what to do with the VM to get more updates. The VM's reside on a server which is on the domain.
Any suggestions on allowing these VM's to get past the initial upgrade to 1909 and get more updates without the network error?
Hi,
I'm French and use MDT to get a system image of Windows 10 2004.
I use SW_DVD9_Win_Pro_10_2004_64BIT_English_Pro_Ent_EDU_N_MLF_-2_X22-29752.ISO and the language pack Microsoft-Windows-Client-Language-Pack_x64_fr-fr.cab found in the multi-language iso
I use it in the customsettings.ini :
UILanguage=fr-FR
LanguagePacks001={fd55e77c-40aa-4174-9409-222785d3b710}
And it is well installed.
But I discovered that in the build 2004 the local administrator is named Administrator when in the build 1909 the local administrator was named Administrateur
Did I missed something ?
Or is it normal now ?
Thank you for your help.
Ludovic.