I think the issue with the discrepancy between the local admin account of the machine to be captured and the admin account of MDT.

From the donor machine I can successfully drill into the deployment share\scripts\Litetouch VBS then credentials screen pops up asking to enter the credentials to access the network share this obviously is the MDT admin account  so I enter it and move next, then goes through Bootstrap and asks for credentials again saying "Specify credentials for connecting to network shares". On some documentations this is the local administrator account to be used to access the donor machine after the reboot to continue with the capture process (after the sysprep goes through and machine reboots)

When I enter the donor machine local admin account credentials it says wrong (but looks for the donor machine admin account after the reboot?), only accepts when the MDT server admin account details entered and moves to the next step. Then the machine goes through some process and reboots and I can see the system is trying to access the machine with the same details entered (the MDT administrator account) earlier were I think it should have been the local machines admin account which is not accepted?

The other problem is that the local admin account is disabled but I have enabled it just to see if that was the issue but no luck. Also created an identical account on both the server and client with same passwords, both admins on server AND donor client, then the process just stalls after accepting the credentials. Really driving me nuts.

The interesting thing is that when I do a fresh deployment I can capture that with no issues because the local and server admin accounts are the same (assuming that is the issue)

this only happens when trying to capture an image which wasn't deployed by the MDT server.

Any help would be greatly appreciated 

hello 

I am learning to sysprep using answer file on windows server 2019 but it goes wrong. Error Time zone data missing " " (0x80070002)
But i don't understand why
Sorry my english is not good

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="oobeSystem"><component name="Microsoft-Windows-International-Core" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><AutoLogon><Password><Value>QQBxAGEAbwBAACMARgAuADEAMgAwAFAAYQBzAHMAdwBvAHIAZAA=</Value><PlainText>false</PlainText></Password><Enabled>true</Enabled><LogonCount>1</LogonCount><Username>Administrator</Username></AutoLogon><OOBE><HideEULAPage>true</HideEULAPage><HideLocalAccountScreen>true</HideLocalAccountScreen><HideOEMRegistrationScreen>true</HideOEMRegistrationScreen><HideOnlineAccountScreens>true</HideOnlineAccountScreens><HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE><NetworkLocation>Work</NetworkLocation><ProtectYourPC>3</ProtectYourPC><SkipMachineOOBE>true</SkipMachineOOBE><SkipUserOOBE>true</SkipUserOOBE><UnattendEnableRetailDemo>false</UnattendEnableRetailDemo></OOBE><UserAccounts><AdministratorPassword><Value>QQBxAGEAbwBAACMARgAuADEAMgAwAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value><PlainText>false</PlainText></AdministratorPassword></UserAccounts><TimeZone></TimeZone></component></settings><settings pass="specialize"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><CopyProfile>true</CopyProfile><TimeZone>Pacific Standard Time</TimeZone><ProductKey></ProductKey><ComputerName>*</ComputerName></component></settings><cpi:offlineImage cpi:source="wim:d:/server2019/sources/install.wim#Windows Server 2019 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

!--------------------------------------------------------------------------------------------!	TSManager	02-10-2020 13:57:20	1564 (0x061C)
Expand a string: WinPE	TSManager	02-10-2020 13:57:20	1564 (0x061C)
Executing command line: OSDApplyOS.exe /image:TST00015,%OSDImageIndex% /runfromnet:False with options (0, 4)	TSManager	02-10-2020 13:57:20	1564 (0x061C)
Command line for extension .exe is "%1" %*	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
Set command line: "OSDApplyOS.exe" /image:TST00015,1 /runfromnet:False	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
Found run from net option: 0	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
Not a data image	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
ApplyOSRetry: 	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
TSLaunchMode: PXE	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
OSDUseAlreadyDeployedImage: FALSE	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
Searching for next available volume:	ApplyOperatingSystem	02-10-2020 13:57:20	1144 (0x0478)
  Volume A:\ is not a local hard drive.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
  Volume S:\ is not using the NTFS file system.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
  Volume C:\ is a valid target.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found volume C:\	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Windows target partition is 0-3, driver letter is C:\	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
!sSystemPart.empty(), HRESULT=80004005 (..\diskvolume.cpp,132)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
System partition not set	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Unable to locate a bootable volume. Attempting to make C:\ bootable.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Volume C:\ is on the boot disk.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Volume C:\ has an NTFS filesystem.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Creating instance of service loader	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Loading service	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Waiting for service to initialize	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for software providers	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS software provider	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsSwProvider	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for packs	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS pack	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsPack	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for volumes	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS software provider	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsSwProvider	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for packs	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS pack	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsPack	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for volumes	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS volume	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsVolumeMF	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for access paths	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS pack	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsPack	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for volumes	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a VDS volume	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsVolumeMF	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for access paths	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found a volume with access path 'C:\'	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for IVdsVolume	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Activating partition	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying for volume plexes	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found volume plex	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Volume plex has 1 extents	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Querying pack for disks	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Found disk	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Checking for match in disk extent 0	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
No match	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Checking for match in disk extent 1	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
No match	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Checking for match in disk extent 2	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
No match	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Checking for match in disk extent 3	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
No match	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Checking for match in disk extent 4	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Match	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
partitionProps.PartitionStyle == VDS_PST_MBR, HRESULT=80004001 (..\diskvolume.cpp,937)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Marking partitions active is only supported for MBR disks.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
ActivateImpl( spVolume, bTest ), HRESULT=80004001 (..\diskvolume.cpp,1645)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Unable to activate partition (0x80004001)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
TS::Utility::CVolume::Activate( sVolume.substr(0, 2) ), HRESULT=80004001 (installcommon.cpp,708)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Failed to make volume C:\ bootable. Code 0x80004001.	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
MakeVolumeBootable( pszVolume ), HRESULT=80004001 (installcommon.cpp,780)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system.
Not implemented (Error: 80004001; Source: Windows)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
ConfigureBootVolume(targetVolume), HRESULT=80004001 (applyos.cpp,499)	ApplyOperatingSystem	02-10-2020 13:57:21	1144 (0x0478)
Process completed with exit code 2147500033	TSManager	02-10-2020 13:57:21	1564 (0x061C)
!--------------------------------------------------------------------------------------------!	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Failed to run the action: Apply Operating System. 
Not implemented (Error: 80004001; Source: Windows)	TSManager	02-10-2020 13:57:21	1564 (0x061C)
MP server http://SCCM.Test.Com. Ports 80,443. CRL=false.	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Setting authenticator	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Sending StatusMessage	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Setting the authenticator.	TSManager	02-10-2020 13:57:21	1564 (0x061C)
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: SCCM.Test.Com:80  CCM_POST /ccm_system/request	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Not in SSL	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Request was successful.	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Set a global environment variable _SMSTSLastActionRetCode=-2147467263	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Set a global environment variable _SMSTSLastActionName=Apply Operating System	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Clear local default environment	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Let the parent group (Install Operating System) decides whether to continue execution	TSManager	02-10-2020 13:57:21	1564 (0x061C)
The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Failed to run the last action: Apply Operating System. Execution of task sequence failed.
Not implemented (Error: 80004001; Source: Windows)	TSManager	02-10-2020 13:57:21	1564 (0x061C)
MP server http://SCCM.Test.Com. Ports 80,443. CRL=false.	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Setting authenticator	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Sending StatusMessage	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Setting the authenticator.	TSManager	02-10-2020 13:57:21	1564 (0x061C)
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: SCCM.Test.Com:80  CCM_POST /ccm_system/request	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Not in SSL	TSManager	02-10-2020 13:57:21	1564 (0x061C)
Request was successful.	TSManager	02-10-2020 13:57:21	1564 (0x061C)

I am working with our GPO group to set some rules. Meanwhile, our two main drives are not getting mapped at logon.

I found something which will map the drives from the registry, but its only for the current user, not new users.

I tried loading the default user dat file hive and make the change but it doesn't take. I had something similar with Panasonic
models where I have a working run-once to turn off Numlock. In this case, I need something to run every time any user logs on.

I have a bat file which disconnects those two drives, then runs a GPUPDATE and placed it in startup, but they don't want that even as a temp work-around.

I am wondering how I can modify a registry key for the CU and all subsequent users who will log on. From what I'm given,
there is a reg change and a PS to run. I can accomplish both in MDT but again it's just for one user:

HKEY_Current_User\Netowrk\*SMBv1 Drive Letter*

               Right click and "Create New" > DWORD > Value = ProviderFlags and Value = 1

and the PS is:

New-ItemProperty -Path ‘HKLM:SYSTEM\CurrentControlSet\Services\Dnscache\Parameters\’ -Name DisableNRPTForAdapterRegistration -PropertyType DWORD -Value 0 -Force

I am using a device that mounts to hi-lo's called a thor vm3. they are currently running 1607 ltsb. the device will image, but after that, it doesn't join to the domain or run any other tasks after the image is laid down. i have checked the logs, but nothing stands out. any suggestions on where to check first? 

also, if 1607 isn't supported, the image wouldn't lay down at all, correct? 

thanks, 

Issue: I was getting the below error message while performing Windows 10 1909 TS deployment through MDT.

Fix: Please make sure you are choosing correct edition of OS in the TS, seems to be we were selected windows 1909 N edition and basically N edition deprecated few features, also Scan management few deprecated since windows 10 1809. So after choose the correct version of windows 10 1909 version we eliminated the first 2 errors. For third error we unselect the Scan management feature from the TS and finally we completed TS without any error.

Thanks, Siva

I have this registry entry below:

HKEY_Current_User\Network\*SMBv1 Drive Letter*

               Right click and "Create New" > DWORD > Value = ProviderFlags and Value = 1

This looks through all the network drives and adds the DWord and Value for each.
However, this is only per user, the initial user. It doesn't apply to all users or future users.

I also have a PS script:

New-ItemProperty -Path ‘HKLM:SYSTEM\CurrentControlSet\Services\Dnscache\Parameters\’ -Name DisableNRPTForAdapterRegistration -PropertyType DWORD -Value 0 -Force

This is all done for the current user. I need something in HKLM that adds that ProviderFlags for all drives for any user.

So far, we can only use 2004 on a pc where one user is using it. With multiple user pcs we can't go there yet. GPO group hasn't found where to add that GPO at sign on like it worked in 1809.

I had a thought of putting a batch file in startup but that is not what they desire. So, I need to modify the registry somewhere
so that all users have that registry change, not just current user. This is all a work-around until a GPO is found for 2004 to map network drives at logon, for every user.

 When creating a new deployment share to a different location (drive or partition) can we just copy the content (the whole structure of the existing Deployment Share) over and have the configured tasks and sequences intact to save us recreating them again on the new location? Because when we create a new DS we just have to go through setting up everything from start.

Is there a way of taking a backup of the current deployment share and restore to the same or different location when needed?

Hi,

When windows7 starts for the first time (Phase = stateRestore), TSmBootstrap.exegives the error: msvcp120.dll is missing from your computer. Actually, I do have "msvcp120.dll" in %deployroot%\Tools\x86\. But it does not copy to C:\MININT\Tools\X86. The same happens with x64 version OS.

After I press "ok" in this error, deployment wizard finishes with error "Welcome wizard failed or was cancelled".

Bdd.log says:

SMS Task Sequencer found at F:\Deploy\Tools\X86, copying to C:\MININT\Tools\X86	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\CcmCore.dll to C:\MININT\Tools\X86\CcmCore.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\CcmUtilLib.dll to C:\MININT\Tools\X86\CcmUtilLib.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\Smsboot.exe to C:\MININT\Tools\X86\Smsboot.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\SmsCore.dll to C:\MININT\Tools\X86\SmsCore.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsCore.dll to C:\MININT\Tools\X86\TsCore.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TSEnv.exe to C:\MININT\Tools\X86\TSEnv.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsManager.exe to C:\MININT\Tools\X86\TsManager.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsmBootstrap.exe to C:\MININT\Tools\X86\TsmBootstrap.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsMessaging.dll to C:\MININT\Tools\X86\TsMessaging.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsProgressUI.exe to C:\MININT\Tools\X86\TsProgressUI.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TSResNlc.dll to C:\MININT\Tools\X86\TSResNlc.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\xprslib.dll to C:\MININT\Tools\X86\xprslib.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\00000409\tsres.dll to C:\MININT\Tools\X86\00000409\tsres.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Control\2\TS.XML to C:\MININT\Tools\X86	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to C:\MININT\Tools\X86\VARIABLES.DAT	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
RUN: regsvr32.exe /s "F:\Deploy\Tools\x86\Microsoft.BDD.Utility.dll"	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
RUN: regsvr32.exe /s "F:\Deploy\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
TargetOS is the current SystemDrive	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAContinue	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
Property LTIDirty is now = TRUE	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
Command completed, return code = -1073741515	LiteTouch	10/6/2015 3:29:36 PM	0 (0x0000)
Litetouch deployment failed, Return Code = -1073741515  0xC0000135	LiteTouch	10/6/2015 3:29:36 PM	0 (0x0000)

Why it doesn't copy proper tools from %deployroot%\Tools\x86\?
What can I do?

Hello.  I'm trying to image a couple of laptops that keep booting back into the Microsoft Deployment Toolkit rather than into the OS and installing applications.  Nothing has changed to the WDS server nor the image since the last successfully imaged machine.  During deployment, the Installation Progress window is taking an abnormally long time during "Applying unattend.xml with DISM.exe."  I could deal with it taking too long, but after that completes and the machine reboots, it's booting back into the Microsoft Deployment Toolkit and giving the message that another deployment is in progress rather than booting into the OS and continuing the deployment of selected applications.  I successfully imaged an identical laptop a few days ago, so model, drivers, etc. should not be a problem for these two problem devices.  Any assistance is greatly appreciated.

We had GPO set for our mapped drives in Win7, all the way up to 1803.

In 2004, our AD group said they pulled down the 2004 Template but we do not get our two needed drives mapped.
They are just drive boxes with X's next to them.

We haven't discovered the location in the template to map those drives and therefore is holding us back from going
to 2004. I'm not sure if there are multiple 2004 templates that need to be pulled down, but our drives are not
mapping. For now, I have a registry change for the HKLM I've added as a step in my TS's.

If anyone is aware of the box to check or whatever is needed in GPO to run at every login and map our drives likes we
did with 1803, I would love to know what that is.

I have an 1809 base image to test with. It has a suspend and a Resume TS on the desktop.

I've upgraded it to 1909. My first question is, will my Resume still work?

Secondly, since I didn't need the ISO to create the 1909 VM, do I still have to have it somewhere in MDT (perhaps to do a capture/deploy properly)?

Any info on this is awesome!

The MDT server is build on the local Admin account therefore the local admin account credentials been used for deployment. The system doesn't agree well with other accounts being used during eployment (even with local admin rights) so I always stick with the original account which is the local admin account.

However the MDT server is now going to be joined into a domain and the local admin account is going to be disabled by the GPO. 

So the question is, what is the most trouble free way of doing this? Creating a domain account and assigning the account as the local admin and then what? Modifying the boot.ini or the customsettings.ini? Because the system always looks for the same credentials in which the system was build on.

OR should we just continue running the MDT server as a stand-alone server without joinin to the domain? In that case we are unable to join the machines to AD during deployment phase as well as being unable to saving the Bitlocker decryption key to AD.

New to MDT 2013/WDS, but after setting up the server today and getting everything in place when I try to PXE boot it gets to the Microsoft Deployment Toolkit screen and asks for credentials.

I enter the credentials in for that deploymentshare folder and get the following: invalid credentials network path not found.

I have tried changing boot.ini and the customize.ini file to reflect this and in all cases I get the same error.  The permissions are right, I even tried removing the $ after the share as someone suggested although I didn't think it would matter.

I can hit F8, ping the dhcp server, the WDS server, i get a valid ip, all dns is correct and still same error.

Added note I can net use mount the share from command line after hitting f8

Any help would be appreciated.

Hi :)

I posted this elsewhere, but this seems like a better place, so I'll try here as well.

With ADK 2004 (build 19041) I create a simple WinPE ISO with WinPE-HTA and WinPE-Scripting packages added - all good. But a HTA in IE9, 10 or 11 mode does not allow simple text field input (IE7 mode works, but has other issues/limitations). Same problem with the ADK preview build 19624, but works just fine in the good old ADK 1903 (18362). Am I missing something here? Here is a script to re-create the problem.

copype amd64 C:\WinPE_x64
dism.exe /mount-wim /wimfile:"c:\winpe_x64\media\sources\boot.wim" /index:1 /mountdir:"c:\winpe_x64\mount"
dism.exe /image:"C:\WinPE_x64\mount" /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-HTA.cab"
dism.exe /image:"C:\WinPE_x64\mount" /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab"
(echo ^<head^>
echo ^<HTA:APPLICATION ^/^>
echo ^<meta http-equiv=^"x-ua-compatible^" content=^"ie=9^" ^/^>
echo ^</head^>
echo ^<body^>
echo ^<input type=^"text^"^>
echo ^</body^>
echo ^</html^>) > "C:\WinPE_x64\mount\SampleHTA.hta"
echo X:\SampleHTA.hta >> "C:\WinPE_x64\mount\Windows\System32\Startnet.cmd"
dism.exe /unmount-wim /mountdir:"C:\WinPE_x64\mount" /commit
MakeWinPEMedia /ISO C:\WinPE_x64 C:\Temp\WinPE.iso

MDT 2012 Server is up and running. I mistakenly deleted a Task Sequence step called "Install Application" that I thought was not needed (I know I should have disabled it and tested).

I have a problem now, when I went to image a computer I did not get application list (This used to work before I deleted the above TS step) with items to check and uncheck for installation.  "Install Application" TS was readded but now when I try to image I get this error:

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

I've tried moving it to different positions on the list (Higher and lower) to no avail, I always get the same error. Please advise.

-Thanks in advance!

Using: Microsoft MDT version 8456, with KB 4564442 applied following install of Windows 10 2004 ADK

Good morning,

I have been using a reliable Build and Capture task sequence for some time, and all versions of Windows 10 up to 1909 have been built and captured successfully, without errors, with the task sequence.  This includes a 1909 build and capture after updating the ADK and then KB4564442 applied with deployment share updates and new ISO generated for booting.

However, whenever I am attempting a build and capture with Windows 10 2004, the task sequence gets to execute sysprep, and this fails.

C:\windows\system32\sysprep\panther\setupact.log points towards MicrosoftWindows.Client.CBS as being the culprit, extract from the log file is below:

2020-07-28 09:45:24, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.
2020-07-28 09:45:24, Error                 SYSPRP Package MicrosoftWindows.Client.CBS_120.2202.130.0_x64__cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2020-07-28 09:45:24, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2020-07-28 09:45:24, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2020-07-28 09:45:24, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2020-07-28 09:45:24, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2020-07-28 09:45:24, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2020-07-28 09:45:24, Error      [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2020-07-28 09:45:24, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

Performing a check on getting the information for the Windows Package shows that it is installed, but pending removal, but also that it'a a system level application.

Clearly that's something newly added in 2004, as checking for this in Windows 10 1909 shows nothing, and no errors during sysprep.

Can anyone please suggest how this can be resolved?