I am getting these error at the end of my deployment:

FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found

After tracing BDD, LTIApply, ZTIConfigure and comparing it with deployments with no errors, I realised that in ZTIConfigure, the script looks for unattend.xml and it found one in C:\Windows\Panther and it assigns it to OSDAnswerFilePath. It doesnt even grab from the deployment share.

This is from the deployment that has issue.

Found existing unattend.xml at C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Property OSDAnswerFilePath is now = C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Loaded C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Merging \\<host>\DeploymentShare$\Control\HP430G3\Unattend.xml into C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Loaded \\<host>\DeploymentShare$\Control\HP430G3\Unattend.xml for merging	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)

This should be the correct behaviour.

Found unattend.xml at \\VM-DC\DeploymentShare$\Control\W10_1\Unattend.xml, will copy to W:\MININT\Unattend.xml	ZTIConfigure	19/9/2016 9:53:02 PM	0 (0x0000)
Copied \\VM-DC\DeploymentShare$\Control\W10_1\Unattend.xml to W:\MININT\Unattend.xml	ZTIConfigure	19/9/2016 9:53:02 PM	0 (0x0000)
Property OSDAnswerFilePath is now = W:\MININT\Unattend.xml	ZTIConfigure	19/9/2016 9:53:02 PM	0 (0x0000)

*Ignore the different drive letter and differences in TS-ID.

BTW, W: and C: refer to the same location. They both refer to OSDISK and target partition where the wim will be applied to.

At the end of the day, LTIApply only grabs the unattend from %OSDISK%\MININT

Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml	LTIApply	23/9/2016 10:14:39 AM	0 (0x0000)
FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found	LTIApply	23/9/2016 10:14:39 AM	0 (0x0000)

How do i force it to always grab the unattend file from the deployment share and copy to %OSDISK%\MININT?

Hi all - my current TS has a modified page for entering your computer name that states "If the AD object for this name already exists, make sure to move it to COMPUTERS OU now and move it back after you finish".

It would be nice to automate this process to avoid people forgetting - if they forget then GPOs in the OU the AD object is in will break the deployment eg changing admin password.

I've seen suggestions to forcefully move objects to a deployment OU but this is no use for me if we don't know what OU they need to move back to afterwards.  But I can't think of a way to store the original OU info during the process and make the moves.  Any one already do this?

Hi , I am getting this error message when I try to update deployment share for AMD x64. I have MDT in a separate server and WDS in separate server. once the WIM is updated , I map the other server and update the boot image to the WDS to deployment.

This  is the error message.

=== 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.
Loading the existing boot image profile for platform x86.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x86.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x86 ===

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

=== Processing Generic (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\Generic_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

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

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x64 ===


=== Processing complete ===

Please help,

Thanks

Running MDT 2013 Update 2

Installing Windows 7 x64 in a Hyper-V VM on a Windows 10 Host.  I need to capture the WIM of my Gold Image.

If I look in the captures folder in the deployment share, I can see that 1 or 2 GB of the WIM makes it, so it would not seem to be a network and/or permission issue.

Similar solution works in my home lab; the problem occurs on the real server at work.

What would be the most common issues to cause this?

Thanks!

I have been trying to capture a Windows 10 1903 image however I keep getting the below failure when it comes to Sysprep.

I am logged in as the local built in Admin

I have an OOTB .inf driver (VMXNET3) in my MDT share. I generated the LiteTouch boot image to include it, so it gets through the operating system installation just fine. I can't get it to work on the installed image, though. I added an "inject drivers" task to the task sequence during the install phase, immediately following the OS installation, and set it to install all available drivers in the selection profile. It's not working though. Once it reboots after OS install, it can't find the NIC driver. Obviously, putting it in postinstall doesn't work, because it needs to connect to the share, but the LiteTouch .wim that has the NIC driver is no longer loaded.

How am I supposed to install NIC drivers for deployment?

Hello,

I am trying this again because I received no responses to my last post. I have seen a few other posts of this and the solutions they provided have not helped my situation.

This is what I am looking at. I checked the BDD.log and this was what pulled up:

**Full disclosure I pulled these pictures from another post because they match my issues. I use a system called Secure Host Baseline (SHB) to run my windows deployment which makes my rules very long and convoluted. Being that my MDT is on a secure network **I can't copy over information unless I type it by hand**

I have checked to make sure I have no repeating "[Default]" or "[Settings]" throughout my rules. I confirmed that it is calling out the correct task sequence. I have verified everything that I can think of. All I am trying to do is build a WIM file for my Reference image to call out for my deployment build. So, this MDT is getting stuck in a virtual machine....

Any help would be greatly appreciated!

Here is my customsettings.ini

[Settings]
Priority=MACADDRESS,Default
Properties=SetCredProv,CustomStart,RemoveDesktopEdge,HVCIUEFILock,OfficeStart,SHBBuildVer,LocalScriptPath,PSLogpath,SupportHours,SupportPhone,SupportURL,OEMImage,WallpaperImage,LockScreenImage,WinXAdminName,WinXAdminFullName,WinXAdminPassword,SkipWinXAdminPassword,Manufacturer,InstallModel,RenGuest,RenAdmin

[Default]
_SMSTSORGNAME=U.S. Department of Defense
_SMSTSPackageName=SHB v%SHBBuildVer% Build and Capture
SLShare = %WINDIR%\Logs\MDTLogs
PSLogpath = %WINDIR%\Logs\MDTLogs
LocalScriptPath = %WINDIR%\Logs\MDTLogs

OSInstall=YES
HideShell=NO

SkipAdminPassword=YES
AdminPassword= *REDACTED*

SkipApplications=YES
SkipAppsOnUpgrade=YES

SkipBDDWelcome=YES
SkipBitLocker=YES

SkipCapture=YES
DoCapture=YES
SkipComputerName=YES
OSDComputerName=WIN10RS4-REF
SkipComputerBackup=YES
SkipDeploymentType=YES

SkipDomainMembership=YES
JoinWorkgroup=WORKGROUP

SkipLocalSelection=YES
KeyboardLocale=EN-US
UserLocale=EN-US
UILanguage=EN-US

SkipProductKey=YES

SkipRoles=YES

SkipSummary=YES

SkipTimeZone=YES
TimeZoneName=Pacific Standard Time
SkipTaskSequence=YES
TaskSequenceID=SHB-WIN10-REF
SkipUserData=YES
UserDataLocation=NONE

;-------------------------------------- SHB Custom Build Properties -------------------------------------

;Define build version numbers
SHBBuildVer=10.5.0

;Lock Screen and Wallpaper images
LockScreenImage=Lockscreen.jpg
WallpaperImage=DoD_SHB_1920x1200.jpg

;System Properties Branding
Manufacturer = U.S. Department of Defense
OEMImage = oemlogo.bmp
InstallModel = Secure Host Baseline v10.5.0
SupportURL = *REDACTED*
SupportHours = NOVALUE
SupportPhone = NOVALUE

; Setup Local Accounts
SkipWinXAdminPassword=YES
WinXAdminName=xadministrator
WinXAdminFullName=xadministrator
WinXAdminPassword= *REDACTED*

; Rename Guest and Admin Accounts
RenGuest=Visitor
RedAdmin=SHB_Admin

;***************************************************************

;Removes the default Desktop Edge Shortcut Introduced in 1803
RemoveDesktopEdge=NO

;Set to YES to set default credential provider to Smart Card
SetCredProv=YES

;Set NO to skip enforcing HVCI to UEFI Lock.
HVCIUEFILock=NO

;Set YES to Install optional Application McAfee VSE
InstallMcAfee=NO

;Adds Internet Explorer 11 Shortcut to Start Menu
IEShortcut=YES

;Applies Custom Start Menu
CustomStart=YES

;Specify 2016, or 'None' Office tiles to be included in Start Menu. ** If Office is not installed, no Office tiles will be pinned,
;but other custom tiles will still be added. **
OfficeStart=2016

;Enables Cloud/VDI option
VHDOnly=NO

;-----------------------------------------------------------------------------------------------

; Settings below drive the SHB Reference Build and capture task sequence
; based upon the predefined MAC Address below.

[*REDACTED*]
AdminPassword= *REDACTED*
BackupDir=Automated
BackupFile= *REDACTED*
BackupShare=\\*REDACTED*\SHB-DEP$
ComputerBackupLocation=NETWORK
DeploymentType=NEWCOMPUTER
DoCapture=YES
FinishAction=SHUTDOWN
MandatoryApplications001= *REDACTED*
MandatoryApplications002= *REDACTED*
OSDComputerName=SHB_REF
SkipAdminAccount=YES
SkipAdminPassword=YES
SkipApplications=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerBackup=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipFinalSummary=NO
SkipLocaleSelection=YES
SkipPackageDisplay=YES
SkipProductKey=YES
SkipRoles=YES
SkipSummary=YES
SkipTaskSequence=YES
SkipTimeZone=YES
SkipUserData=YES
SkipWinXAdminPassword=YES
TaskSequenceID=SHB-WIN10-REF
UserDomain=SCSPNETOPS01
UserID=MDT
UserPassword= *REDACTED*

and here is my bootstrap.ini

[Settings]
Priority=Default

[Default]
DeployRoot=\\*REDACTED*\SHB-DEP$
UserID=MDT
UserDomain=SCSPNETOPS01

UserPassowrd= *REDACTED*

SkipBDDWelcome=YES

Please help! I just need to rebuild this reference image so I can continue!

I am trying to get the role .net 3.5 installed on a 2019 Server using MDT (6.3.8456.1000) and I am getting an error.  See Pic for error and task sequence setup.

I've been wrestling with this rc = 5 error for a few days now.

I've created a Windows 10 Pro Education x64 (1809) reference machine - its got nothing installed but the latest updates. I've removed win 10 apps and provisioned apps to prep it for WIM capture using MDT. After running the Litetouch script and sysprepping the machine boots to windows PE, gets to the create wim stage and immediately fails with this:

Error creating an image of drive D:, rc = 5
ZTI ERROR - Non Zero return code by ZTIBackup, rc = 5
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM
Access is denied. (Error: 00000005; Source: Windows)
The execution of the group (Capture Image) has failed and the execution has been aborted. An Action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Create WIM. Execution of task sequence failed.
Access is denied. (Error. 00000005; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

MDT is running on windows server 2012 r2 - 1809 ADK and Winpe installed, MDT version is 6.3.8456.1000

I've excluded the Deployment share folder from antivirus and on demand scanning.

I've been lead to believe this is a permissions issue from checking around here and googling. I've checked the MDT account that we've setup can write to the deployment share (it can) and specifically the captures folder of which it can. I regenerated the boot image in MDT and applied it to WDS but received the same error.

I tried changing the bootstrap.ini credentials to a domain admin account (again checked domain admin can write to the share and the captures folder, it can) regenerated the boot image and tried again, received the same error.

Tried the above with domain administrator account and receive the same error.

I saw here: https://social.technet.microsoft.com/Forums/en-US/41dfe8cd-e621-4c39-a7d6-83fa34284e63/cannot-capture-windows-10-1709?forum=mdt about removing the credentials. So I tired removing the credentials which then prompts me to enter credentials before it reboots to create the wim and still receive the same error.

I've added ComputerBackupLocation to the rules and added DeployRoot to the bootstrap.ini but am still receiving the same error.

I've checked that no WIM with the same name exists in captures (it doesn't).

I've gathered the logs (BDD, DISM, Litetouch, all the LTI logs, wizard) and put them in a zipfile on dropbox if needed: https://www.dropbox.com/s/d28i8usarxscswx/Logs.zip?dl=0

Any help anyone can give will be greatly appreciated.

Hello,

May i get some help with my MDT reference Image. 

Im trying to create a reference image of 1903 and capture on Hyper V -

I followed this steps to create setup MDT and WDS etc 

https://gal.vin/2019/05/26/building-windows-10-1903-reference-image-walkthrough/

I built my litetouch iso and setup a vm to capture.

I keep failing at stage of disabling internet service, it cant locate my powershell script to disable internet. 

Not sure what else to do.  i have tried different location same result

Trying to build a clean image with our apps

Below is are rules and custom ini

Rules:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipLocaleSelection=YES
SkipTimeZone=YES
SkipDomainMembership=YES
SkipSummary=YES
SkipFinalSummary=YES
SkipComputerName=YES
SkipUserData=YES

_SMSTSORGNAME=Deploy Share
_SMSTSPackageName=%TaskSequenceName%
DoCapture=YES
ComputerBackupLocation=\\myservername\deploy$\Captures
BackupFile=%TaskSequenceID%_#year(date) & "-" & month(date) & "-" & day(date) & "-" & hour(time) & "-" & minute(time)#.wim
FinishAction=SHUTDOWN
SLShare=\\myserver\deploy$\Logs
EventService=http://myserver:9800

[Settings]
Priority=Default

[Default]
DeployRoot=\\myserver\Deploy$
UserDomain=myserver.local
UserID=myserver
UserPassword=myserver
SkipBDDWelcome=YES

Help would be greatly appreciated

Hi Everyone,

I am a script kiddie (I know literally next to nothing) when it comes to scripting.  I dont really understand cscript and I barely know enough to write simple power shell scripts.

I am trying to have a task sequence option similar to modifying the computer description during deployment.

However this time I need to modify the ManagedBy in AD.  This would add an AD group member to the "ManagedBy" field in Active Directory during the lite touch install for the current computer being imaged.

Can anyone help me getting this figured out.  I'm sure it's simple but I am struggling with it.

Hello,
I want to install Surface Pro 4 devices with MdT 8456 and the Surface deployment accelerator 1.96.0405.

Unfortunately the accelerator requires the version MDT 2013 Update 2 and only seems to work fine with it.

Can I edit the Deploymemt share later with the MDT 8456? So update the share?

What is the best practice for an existing MDT 8456 environment?

greetings Stephan

Hi,

I've made a image using sysprep and DISM.

I've captured the image from my reference machine, and I'm now trying to deploy it to one with identical hardware.

To do this, I've used the following resources: docs.microsoft. com/en-us/windows-hardware/manufacture/desktop/windows-deployment-sample-scripts-sxs#apply-image

and: docs.microsoft. com/en-us/windows-hardware/manufacture/desktop/windows-deployment-sample-scripts-sxs#CreatePartitions-_firmware_.txt

When I run the apply image script, it is saying that it's copying boot files correctly, but when I try to start the machine I get that no boot media was found.

Not really sure where to start looking here, has anyone faced similar issues?

Using WinPE to boot, and Windows Enterprise 2016 LTSP on my machines.

Thanks!

Hi all,

I've been prepping and testing a new MDT (1903) server before it goes into Production. It's a Server 2016 setup with WDS 10.0.14393.2608 and Deployment Workbench 6.3.8456.1000.

On Friday last week, I started a capture before leaving the office for the weekend. I named it, let's say, xyzfriday.wim (actual file name is longer, but doesn't include any special characters).

Today, I came in expecting to see the file in the Captures folder on the server, but there was nothing there. Looking at the machine, it looked like the capture finished. I thought it was weird, so I started a new capture with a new file name, say, abcmonday.wim. Yes, I should have looked in the logs before starting the new capture, but it didn't occur to me at the time.

This new capture completed, and a file appeared in the Captures folder. However, even though the file has the correct time stamp, the file has the name xyzfriday.wim instead of the abcmonday.wim filename.

This time, I looked in the bdd.log in the CMTrace tool and it showed that the Wizard (as listed under Components), accepted the new abcmonday.wim file name prior to capture.

Property BackupFile is now = abcmonday.wim

However, looking further down the log, under the ZTIBackup component, the file name from Friday persisted.

Backup file name already set to: xyzfriday.wim

Each of those lines were the first mention of either file name in bdd.log. ZTIBackup would (obviously) go on to use the xyzfriday.wim file name for the backup path and the dism.exe command to capture the image.

Has anyone seen this happen before or did my Friday capture actually not finish (or start?) properly? I received no warnings or error messages at any stage of this.

Thanks!

Dan

I need some assistance and the guidance, in what is the best deployment of the WDS&MDT servers across two different geographical offices?

The bandwidth is only 100 MBps between the two office location.

• Should I create two different WDS&MDT servers (one in each office location)?
  However, the issue here is that I will need to manually copy the image files across the WAN which can be done via Robocopy after business hours. I assume I can use DFS-R for the OS Image replication. But not sure how to configure this.
• Should I create one main WDS&MDT server in the main office?
  However, the issue here is the bandwidth contention issue which can impact the network performance in between the sites when deploying a new image.

So what would be the best practice or the suggested action?

Any help would be greatly appreciated.

/* Server Support Specialist */

good afternoon to all

today i faced a challenge in deploying mdt server. well i want migrate my user data through the network by mdt server. i configured mdt server as well. my clients are running in vmware workstation.i did custom task for mdt server

here i am attaching my custom task.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES

SkipComputerName=YES
OSDComputerName=PC-%SerialNumber%
SkipDomainMembership=YES
JoinWorkGroup=WORKGROUP

SkipTaskSequence=YES
TaskSequenceID=TASK1

SkipTimeZone=YES
TimeZoneName=ArabianStanadardTime
SkipUserData=YES
SkipLocaleSelection=YES

UserLocale=en-US
UlLanguage=en-US
SkipApplication=YES
SkipSummary=YES
SkipBDDWelcome=YES

UserExit=UserExit.vbs
OSDComputerName=#GetOfflineComputerName()#

UserDataLocation=NETWORK
UDShare=\\Desktop-v6kgobc\usmt
UDDir=%OSDComputerName%

ScanStateArgs=/v:5/o/c
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml

LoadStateArgs=/v:5/c/lac

my client machine And server(WDS service) are running in vmware workstation

my mdt server running in physical machine. i shared my deployment folder through workstation.it is accessible to wds server

Trying to create some new Task sequence media USB keys but it keeps failing with the below error.

It work perfectly last week and nothing has changed that I am aware of

Trying to create some new Task sequence media USB keys but it keeps failing with the below error.

It work perfectly last week and nothing has changed that I am aware of