Hi Team,

I have accidentally deleted one of the application folder which has all the applications mapped in the MDT TS for capturing WIM files, Is there a way to recover the same without recreating them from the scratch.

Any help would be much appreciated

So I installed MDT and ADK, installed a base image of Win10 Pro, installed all the apps I needed, then went to take a capture and sysprep failed. Here's the setuperr log

2017-11-28 14:19:10, Error                 SYSPRP Package Microsoft.BingNews_4.21.2212.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2017-11-28 14:19:10, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

2017-11-28 14:19:10, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

2017-11-28 14:19:10, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2017-11-28 14:19:10, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2017-11-28 14:19:10, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2
2017-11-28 14:19:10, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2017-11-28 14:19:10, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

It seems to be an issue that has happened before, for a while now. I've read some of the fixes that do not seem to work, without breaking something else, but why should I have to jump through hoops when it was a Microsoft installed problem? This is just really poor customer service. One of your Noobs created a Appx package incorrectly and then you pushed it out to the world. Why don't you fix it Microsoft? BTW, your software scanned my network without my permission, saw my Toshiba printers, then also installed Toshiba updates that are also misconfigured, and install the same way a Bing News.

I am trying to create a custom media image using the MDT, but when I go to update the media content, I keep getting the same error, every time.  I have tried uninstalling MDT, reboot, reinstall; didn't work. Tried removing old media and creating new media. Re-made the custom source image, completely restored computer to prior to installing the whole media toolkit and everything; but still same error as below, the bold italicized and underlined part is where it errors out. Any and all help is very appreciated. Thanks everyone in advance!

Starting MDT Media Update
Opened the media deployment share.
Folders to be copied to the media deployment share: 4
Copied: DS001:\Operating Systems\Custom
Copied: DS001:\Out-of-Box Drivers\Windows 10
Copied: DS001:\Task Sequences\Windows 10\Deployment
Copied: DS001:\Selection Profiles
Copied: DS001:\Operating Systems\Custom with Replace option
Copied: DS001:\Out-of-Box Drivers\Windows 10 with Replace option
Copied: DS001:\Task Sequences\Windows 10\Deployment with Replace option
Copied: DS001:\Selection Profiles with Replace option
Copied standard folders.DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.
Boot images updated.
Setting up x64 boot image.
Boot configuration editing completed.
Reset read-only attributes.

Starting: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe" /image:"C:\Users\Training Support\AppData\Local\Temp\MDTUpdate.10780\Mount" /set-targetpath:X:\ > "C:\Users\Training Support\AppData\Local\Temp\PEManager.10780\PEManager.log" 2>&1

Exit code = 1

Starting: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\OSCDIMG\oscdimg.exe" -u2 -udfver102 -m -o -h -w4 -yo"C:\Program Files\Microsoft Deployment Toolkit\Templates\BootOrder.txt" -bootdata:2#p0,e,b"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\OSCDIMG\etfsboot.com"#pEF,e,b"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\OSCDIMG\efisys.bin" "C:\Media\Content" "C:\Media\LiteTouchMedia.iso" > "C:\Users\Training Support\AppData\Local\Temp\PEManager.10780\PEManager.log" 2>&1

Exit code = 1

Starting: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe" /image:"C:\Users\Training Support\AppData\Local\Temp\MDTUpdate.10780\Mount" /set-targetpath:X:\ > "C:\Users\Training Support\AppData\Local\Temp\PEManager.10780\PEManager.log" 2>&1

Exit code = 1

Starting: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\OSCDIMG\oscdimg.exe" -u2 -udfver102 -m -o -h -w4 -yo"C:\Program Files\Microsoft Deployment Toolkit\Templates\BootOrder.txt" -bootdata:2#p0,e,b"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\OSCDIMG\etfsboot.com"#pEF,e,b"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\OSCDIMG\efisys.bin" "C:\Media\Content" "C:\Media\LiteTouchMedia.iso" > "C:\Users\Training Support\AppData\Local\Temp\PEManager.10780\PEManager.log" 2>&1

Exit code = 1


System.Management.Automation.CmdletInvocationException: OSCDIMG failed, rc = 1. ---> System.Exception: OSCDIMG failed, rc = 1.
   at Microsoft.BDD.PSSnapIn.PEManager.CaptureIso(String sourceDir, String captureFile, Boolean supportUEFI)
   at Microsoft.BDD.PSSnapIn.GenerateMDTMedia.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.GenerateMediaProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

I am trying to use Microsoft Deployment Workbench to install some applications. I am running to an issue where I receive the following error, "Application Chrome returned an unexpected return code: 2".  The first app I setup, Acrobat Reader DC, works just fine. Chrome and FireFox both return this error. From what I have been reading, Return code: 2  means that it cannot find the folder or file however I verified and tested over and over that all paths and filenames are correct. Here is what I have tried so far:

1. I am using "Application with source files"
2. Tried both .exe and .msi installers
3. Manually installed successfully using the same UNC path, filenames, and command line switches
4. Tried installing on a Win10 target machine AND the MDT server itself
5. Removed any spaces in filenames
6. Verified both Share and NTFS permissions
7. Disabled UAC and Windows firewall
8. Checked logs however there does not appear to be much detail on the install failures

Please help!!

We are currently search for an easy method to avoid that the Windows installer (Windows Setup) is creating a "Windows Boot Manager" entry in NVRAM. Instead, the system should boot from UEFI Fallback (EFI\BOOT\BOOTX64.EFI). This has already to be done in the Unattended installation.

The reason for this is that the flash chip/EEPROM only has a specific lifetime and we don't know how often it can be erased until the chip dies. The servers are running in a data center and can be rented by customers.

Grüße, Tom

I am trying out deployment with MDT for the first time and created a simple deployment share using Windows 10 Enterprise Evaluation Center Install.wim file (extracted from the ISO file) as the OS, Notepad++ as the application for silent installation and a basic task sequence with a single custom task for installing the Notepad++ application.

When I update the Deployment Share (which is hosted on my OneDrive) - the process gets stuck at the step where it is trying to copy the Background.bmp image to winpe.bmp in local (remains stuck at this step for more than 40-45 mins).

This is the step at which it gets stuck:

"Copying file C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\User_Name\AppData\Local\Temp\MDTUpdate.16916\Mount\Windows\system32\winpe.bmp"

Why is the share not progressing beyond this point? Why would copying an image take so much of time? Most forums cite 40 mins as the longest time it took to update a deployment share - in my case; this step itself takes about 40-45 mins.

How do I solve this issue?

Thanks

Our admin credentials are in the MDT2013 bootstrap.ini file. This means that everyone can see the credentials. I have mad a deploy user which had local admin access en is granted the rights to sign on computers on the domain controllers. That user must have the right user rights to add computers to a domain.

However we want to use that deployment account in the bootstrap.ini so that the administrator account can left of.

i want to replace the line in bootstrap.ini:

When i replace administrator with the deploy account and when the clients boots from WDS the client gives the message after loading the litetouch: a connection with the deploymentshare could not be made.

When i replace the deploy account with the administrator all goes fine again.

What rights does this user needs on the domain to deploy the images thru MDT and WDS?

freddie

I'll try to make this quick. I have been setting up MDT and WDS over the past couple weeks and I finally have everything running great. What i'm asking about isn't even a problem. I think i should say that I have the lite touch install join the pc to the domain and pre-select the OU it should be put in

Like i said, everything runs great and the computer is joined to the domain correctly. The thing is, every time, there is an object created in the root Computer OU. The computer object is always DomainAdmins1, and if i don't delete it, every time i run it it just increments the number, like in the photo:

So far i have just been deleting them and everything still works. I'm just curious if anyone has seen this before and knows why this is happening? And maybe how to prevent it?

Thanks in advance.

mqh7

Hi,

I installed a new Server for LTI deployment. The installed packages are MDT(build 6.3.8456.1000) and ADK 10.1.18362.1 on Server 2019. While i am going to update the deployment share it end up with below error

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
The system cannot find the path specified.

Exit code = 1

DISM /Set-TargetPath failed, rc = 1.
DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.

=== Completed processing platform x86 ===

=== Making sure the deployment share has the latest x64 tools ===

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim will be used.
WIM file mounted.
The system cannot find the path specified.

Exit code = 1

DISM /Set-TargetPath failed, rc = 1.
DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.

=== Completed processing platform x64 ===


=== Processing complete ===

Thank You

Gaurav

Anyone can explain this error code? What does it mean, because it seems that the Office 365 application is installed eitherway.

MDT Application Office 365 Returned an unexpected return code: 32

See error as listed in the screen dump

Hey Guys,

Have been using a USB thumb stick to image computers but as time has gone on the files have become huge and now it takes a 40 gig USB drive because of all the drivers for different machine types.

Also when ever anything any updates or changes each tech has to re download the 21 gigs and if something is updated and they do not download then files that they are installing could be out dated.

I looked into WDS but that looked like a lot to setup.  Would it be possible to keep all the MDT files on a network share and then some where in the MDT config tell it to look at the network share for Drivers and operating system.

Is this even possible, trying to figure out what options are available.

I have tried copying only the following folders but got an error after MDT Lite touch loaded about could not find files, which makes sense :)
G:\Media\Content\Deploy\Boot

G:\Media\Content\Boot

Thank you for any help you can provide,

Best regards,

John

Hi,

I'm installing Citrix 4.2.100.14 in a MDT task sequence, it hangs until you move the mouse in USB component installation, the log says:

I've seen some information about this problem (http://discussions.citrix.com/topic/316145-citrix-receiver-33-silent-install-hangs-when-installing-from-microsoft-deployment-toolkit-2012-mdt/) and I've applied the "solution" without success. 

Anyone in this situation.

Thanks in advance.

Hi,

Has anyone had an issue importing the the latest 1809 (downloaded from the MVLS site that was re-released in Nov) into MDT? Each time I try to import the OS the progress gets up to 98% and then it fails saying "the system cannot find the path specified".  I do have the 1809 ADK version and also installed the WinPE version for 1809 too.  The MDT version I'm using is 8540.

Importing other versions of Windows 10 works fine.

This is the error I get:

Performing the operation "import" on target "Operating system".
The system cannot find the path specified
The system cannot find the path specified
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the path specified
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
   at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
   at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
   at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopy()
   at Microsoft.BDD.PSSnapIn.ImportOperatingSystem.Import(String sourcePath, String directoryName, Boolean moveDirectory)
Import processing finished.

Any advice or help would be great.  Thanks!

Pre-EOL we had a good process where we would capture missing patches from our Windows 7 reference images and inject them via DISM.  This has let us keep our deployments fairly fresh over the years.

Unfortunately the new ESU updates seem to have put an end to this process.   Trying to inject them, even with the full set of pre-req patches, results in an unattended.xml error.  Has anybody else run into this and does anybody have a good way to manage the ESU patches going forward?

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'm sure this has been asked a hundred times, I just can't find the right answer...

I do have VM's that are created by a user other than admin. I know this is not the actual proper way to create VM's in Hyper-V but I could always modify and use them well.

I am doing an Upgrade TS to take my 1803 to 1809. I repeatedly get the error where sysprep fails with the state:

IMAGE_STATE_UNDEPLOYABLE

I found a "fix" on this site that said to change the regedit to
IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE
and that fixed people's issue. I did that, and sysprep keeps changing that state back to Undeployable.

I also ran the Apps_remover from MS. I still get that same error and I need to upgrade these VM's asap.

Any suggestions would be appreciated.

For some reason my Task Sequences are not showing up in my Selection profiles so I can create Offline media for these awesome new laptops that do not have a NICs. (sarcasm) How do I make the Task Sequences appear?

Version 6.3.8456.1000

I created an extra Wizard screen giving the option to Encrypt during imaging. It writes to AD, or doesn't if you choose NO.

Now, I have several models that encrypt even when you choose NO. I don't think it's anything with MDT because I  haven't
changed anything with that. It may be in my Server Unit who maintains AD, but just wondering if anyone has seen this
behavior with encrypting even when you select not to (which has worked in the past).