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.

OK.  Historically speaking, we did an update from MDT2013/ADK8.1/MDS Lite Touch to MDT2013U2/ADK10/MDS  LiteTouch But the instructions we used are not available.  Everything ran fine until i added a task sequence for win10 and the associated custom settings and did a Update DS and choose 'replace boot images'.  As soon as those images were added, things went downhill.  In an attempt to isolate the cause, I tried to remove WDS at which time my server fell down and couldn't get back up.

So, after failing to restore the server from backup, we rebuilt it and restored the data.  I then installed 2013/8.1/MDS and performed the upgrade following these instructions http://deploymentresearch.com/Research/Post/504/A-Geeks-Guide-for-upgrading-MDT-2013-to-MDT-2013-Update-1

Although i didn't use the powershell, i just started with a reboot and then put reboots in between everything, remove adk8.1, reboot, install adk10, reboot, install MDT2013U2, ...

Then i created a new TS and using the original as a guide, matched it up to the old.  I can provide an image, but i'm not comfortable exporting the xml

I am back to a point where i have the exact same problem as before.  Basically, the [DEFAULT] custom settings are being applied, however the ones specified for the task sequence are not.  I haven't even gotten into the task sequence itself, i'm still doing the steps following selecting the task sequence.  I'm enclosing the relevant customsettings in a code block below but if files would help, i have a cleaned up copy of the full ini file, an image of my task sequence and an image of the screen of my deployment in action.

I'm basically wondering if, for instance, some of the name value pairs have been deprecated or if there's a problem with duplication now that i'm in update 2 or..well...I have no idea, all i know is that the default rules appear to be working, but the specific task sequence ones aren't being applied.

[Settings]
Priority=TaskSequenceID, Default
Properties=SavedJoinDomain

[Default]
WSUSServer=http://wsusServer:8530
UserID=serviceAccount
UserDomain=domainName.com
UserPassword=Password
DomainAdminDomain=domainName.com
DomainAdmin=serviceAccount
DomainAdminPassword=Password
SLShareDynamicLogging=\\deployServer\deploymentShare\ClientLogs\%COMPUTERNAME%
SLShare=\\deployServer\deploymentShare\ClientLogs
_SMSTSOrgName=My Org Name
BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
SkipTimeZone=YES
TimeZone=035
TimeZoneName=Eastern Standard Time
SkipLocaleSelection=YES
KeyboardLocale=en-us
UserLocale=en-us
UILanguage=en-us
SkipProductKey=YES
SkipBitLocker=YES
SkipComputerBackup=YES
EventService=http://deployServer:9800

...

[22]
UserID=serviceAccount
UserDomain=domainName.com
UserPassword=Password
GPOPackPath=baseline
SkipDomainMembership=YES
SkipCapture=NO
SkipAdminPassword=YES
AdminPassword=Password
JoinDomain=domainName.com
DomainAdminDomain=domainName.com
DomainAdmin=serviceAccount
DomainAdminPassword=Password
SkipFinalSummary=YES
FinishAction=RESTART
...

Julio Vaz http://jvaz.wordpress.com

Hello,

I have a problem with my deployment Windows 10 1809.

When I deploy OS with Workgroup, It's Okay and rapid.

Now, I deploy OS with my domain, the deployment it's okay but it's very long for the first boot (phase OOBE). It's block Please Wait for 1 hours ...

But, If I force the restart by pressing the button ON/OFF, He joins the domain directly at startup…

The second problem, sometimes he locks the account domain administrator while this account is disable with my domain.

I use another account for join my domain, which is well written in CustomSettings :

[Settings]
Priority=Model, Default
Properties=MyCustomProperty

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

KeyboardLocale=040C:0000040C
UserLocale=fr-FR
UILanguage=fr-FR
TimeZone=105
TimeZoneName=Romance Standard Time
SkipLocaleSelection=YES
SkipTimeZone=YES

ApplyGPOPack=NO

JoinDomain=ad.fr
DomainAdmin=adminADR
DomainAdminDomain=ad.fr
DomainAdminPassword=********

WSUSServer=https://WSUS.ad.fr:8531

MandatoryApplications001={5a837603-ee2e-412c-80fa-b97a8f47d19f}

[Latitude 5590]
_smstsorgname=Deploiement Latitude 5590
TaskSequenceID=3
DriverSelectionProfile=5590

I did not touch anything in the unattend.xml and Administrator local is disable with GPO of domain. But i use with variable

ApplyGPOPack=NO in my CustomSettings.

I create Object Computer in my OU before the deployment.

LOG BDD :

LTI beginning deployment LiteTouch 22/01/2019 12:01:05 0 (0x0000)
About to run command: "X:\Deploy\Tools\X64\TsmBootstrap.exe" /env:SAStart LiteTouch 22/01/2019 12:01:05 0 (0x0000)
Property LTIDirty is now = TRUE LiteTouch 22/01/2019 12:01:05 0 (0x0000)
Command completed, return code = -2147021886 LiteTouch 22/01/2019 12:16:44 0 (0x0000)
Property LTIDirty is now = FALSE LiteTouch 22/01/2019 12:16:44 0 (0x0000)
If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation. LiteTouch 22/01/2019 12:16:44 0 (0x0000)
Property OSDTargetDriveCache is now = DIRTY LiteTouch 22/01/2019 12:16:44 0 (0x0000)
LTI initiating task sequence-requested reboot. LiteTouch 22/01/2019 12:16:44 0 (0x0000)
Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS LiteTouch 22/01/2019 13:22:03 0 (0x0000)
Property start is now =  LiteTouch 22/01/2019 13:22:02 0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8450.1000 LiteTouch 22/01/2019 13:22:03 0 (0x0000)

Hi, here is a 3 excellent courses talking about MDT in our Organizations

https://www.linkedin.com/learning/instructors/jesus-octavio-rodriguez-de-santiago

Hi there,

I have problems with automatic domain join using the Windows Deployment Toolkit. Everytime I configure anything it won't work. The NetSetup.txt* put out errors like these:

*["C:\Windows\debug\NetSetup.LOG"]

01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Cracking DNS domain name contoso.corp/ into Netbios on \\WDT-W16SRV1.contoso.corp
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Crack results:     name = CONTOSO\
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Cracking account name CONTOSO\WDT-WZ3$ on \\WDT-W16SRV1.contoso.corp
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Crack results:     Account does not exist
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: ldap_compare_s failed: 0x1 0x6e
01/26/2019 17:34:22:651 NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x6e
01/26/2019 17:34:22:651 NetpProvisionComputerAccount: LDAP creation failed: 0x6e
01/26/2019 17:34:22:651 NetpProvisionComputerAccount: Cannot retry downlevel, specifying OU is not supported
01/26/2019 17:34:22:651 ldap_unbind status: 0x0

..

01/26/2019 17:34:32:682 NetpDisableIDNEncoding: no domain dns available - IDN encoding will NOT be disabled
01/26/2019 17:34:32:682 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0

..

01/26/2019 18:08:41:095 NetpDsGetDcName: trying to find DC in domain 'contoso.corp', flags: 0x40001010

Have anybody any idea? Thanks a lot.

Best regards, crazyyzarc

Hey Guys,

I am trying to roll out WDS to image different machines. I have it setup, its working through PXE boot no problem. I work for an MSP so we have multiple clients with different images, etc. I was fine just using MDT, burning the boot image for said client then booting from the thumb drive and imaging said computer. So now that I am using WDS I have install images, boot images, and its been a while since I have rolled this out. 

So what I am trying to do and what I have done so far is when you PXE boot from a machine, you select the boot image (that's working somewhat) When I choose the first client which happens to be the first boot image I imported into WDS, it takes me to the different task sequences and I can image a machine no problem. When I choose the 2nd or 3rd boot image (again these are boot images for different clients we support) It makes it to the MDT splash screen but none of the task sequences load. I haven't had any luck googling the issue so I'm asking. 

Hopefully I didn't leave to much out, but please feel free to ask for more information. 

Alex G

Hi @ all

wie have updated our Litetouch boot image using DISM and know we try to update the deploymentshare but we get the following error.  

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

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

Building requested boot image profile.

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
   --- End of inner exception stack trace ---
   at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Unable to open the specified WIM file? The image ist is stil in the boot folder.

Anybody an idea or an solution for that problem?

Thank's

Adrian

My environment

Windows Server 2012 R2 Server duly upgraded and integrated with Contoso. corp Domain
MDT v8456
ADK 1809
Windows PE Add-on for ADK 1809

When the MDT v8456 sends the non-customized image to Windows 10 Pro stations I get the error message that appears in the logo below:

LOG: 

Not Wizard = Falso         Wizard  06/02/2019 18:02:36    0 (0x0000)

Property WizardComplete is now = N    Wizard             06/02/2019 18:02:36    0 (0x0000)

             Open Control File: TaskSequences          Wizard             06/02/2019 18:02:37    0 (0x0000)

Property TaskSequenceID is now = BUILD001     Wizard             06/02/2019 18:02:52    0 (0x0000)

Property TaskSequenceName is now = Windows 10 pro 1809     Wizard  06/02/2019 18:02:53    0 (0x0000)

Property TaskSequenceVersion is now = 1.0       Wizard             06/02/2019 18:02:53    0 (0x0000)

Property TaskSequenceTemplate is now = ClientUpgrade.xml         Wizard  06/02/2019 18:02:53    0 (0x0000)

Task Sequence contains a LTIApply.wsf step, and is not running within WinPE.   Wizard  06/02/2019 18:02:53    0 (0x0000)

Property DeploymentType is now = UPGRADE   Wizard             06/02/2019 18:02:53    0 (0x0000)

Property IsOSUpgrade is now = 1           Wizard             06/02/2019 18:02:53    0 (0x0000)

Property OSGUID is now = {d5bc9d9a-ac12-4ad8-8eb8-cd6114f7cfaf}    Wizard  06/02/2019 18:02:54    0 (0x0000)

Property ImageIndex is now = 1 Wizard  06/02/2019 18:02:54            0 (0x0000)

Property ImageSize is now = 13491        Wizard             06/02/2019 18:02:54    0 (0x0000)

Property ImageFlags is now = Professional          Wizard             06/02/2019 18:02:54    0 (0x0000)

Property ImageBuild is now = 10.0.14393.0        Wizard             06/02/2019 18:02:54    0 (0x0000)

Property ImageProcessor is now = x64  Wizard             06/02/2019 18:02:55    0 (0x0000)

Property ImageLanguage001 is now = pt-BR      Wizard             06/02/2019 18:02:55    0 (0x0000)

InstallFromPath: \\SED-MDT-WS\DeploymentShare$\Operating Systems\Windows 10 Pro x64\Sources\install.wim       Wizard  06/02/2019 18:02:55            0 (0x0000)

Property InstallFromPath is now = \\sed-mdt-ws\deploymentshare$\Operating Systems\Windows 10 Pro x64\sources\install.wim       Wizard  06/02/2019 18:02:55            0 (0x0000)

SourcePath: \\SED-MDT-WS\DeploymentShare$\Operating Systems\Windows 10 Pro x64   Wizard  06/02/2019 18:02:55            0 (0x0000)

Property SourcePath is now = \\SED-MDT-WS\DeploymentShare$\Operating Systems\Windows 10 Pro x64 Wizard  06/02/2019 18:02:55    0 (0x0000)

Found Task Sequence Item: //step[@type='BDD_InstallUpdatesOffline' and @name='Apply Patches']            Wizard  06/02/2019 18:02:56            0 (0x0000)

Found Task Sequence step of type //step[@type='BDD_InstallUpdatesOffline' and @name='Apply Patches'] =        Wizard  06/02/2019 18:02:56            0 (0x0000)

Found Task Sequence Item: //step[@type='BDD_InstallRoles']           Wizard             06/02/2019 18:02:56    0 (0x0000)

Found Task Sequence step of type //step[@type='BDD_InstallRoles'] =       Wizard             06/02/2019 18:02:56    0 (0x0000)

Found Task Sequence Item: //step[@type='BDD_InstallApplication' and ./defaultVarList/variable[@name='ApplicationGUID'] and ./defaultVarList[variable='']]       Wizard  06/02/2019 18:02:56            0 (0x0000)

Found Task Sequence step of type //step[@type='BDD_InstallApplication' and ./defaultVarList/variable[@name='ApplicationGUID'] and ./defaultVarList[variable='']] = Verdadeiro          Wizard             06/02/2019 18:02:56    0 (0x0000)

             Open Control File: Applications Wizard             06/02/2019 18:02:56    0 (0x0000)

Property TSGuid is now = {b4a49bb9-977f-4801-9526-7078612afde7} Wizard  06/02/2019 18:11:24    0 (0x0000)

<Message containing password has been suppressed>             Wizard  06/02/2019 18:11:24    0 (0x0000)

Property BdePin is now =           Wizard  06/02/2019 18:11:24            0 (0x0000)

Property BdeModeSelect1 is now =        Wizard             06/02/2019 18:11:24    0 (0x0000)

Property BdeModeSelect2 is now =        Wizard             06/02/2019 18:11:24    0 (0x0000)

Property WaitForEncryption is now =     Wizard             06/02/2019 18:11:24    0 (0x0000)

Property BdeInstall is now =      Wizard  06/02/2019 18:11:24            0 (0x0000)

Property OSDBitLockerStartupKeyDrive is now =              Wizard  06/02/2019 18:11:24    0 (0x0000)

Property OSDBitLockerWaitForEncryption is now =              Wizard  06/02/2019 18:11:25    0 (0x0000)

Property BdeRecoveryKey is now =        Wizard             06/02/2019 18:11:25    0 (0x0000)

Property BdeInstallSuppress is now = YES           Wizard             06/02/2019 18:11:25    0 (0x0000)

Property WizardComplete is now = Y     Wizard             06/02/2019 18:11:25    0 (0x0000)

------------------------- Object Initialization -------------------------             ZTIGather          06/02/2019 18:11:54    0 (0x0000)

------------------------- Initialization -------------------------             ZTIGather          06/02/2019 18:11:54    0 (0x0000)

Synchronizing the environments.            ZTIGather             06/02/2019 18:11:54    0 (0x0000)

Property DeployRoot is now = \\SED-MDT-WS\DeploymentShare$ ZTIGather          06/02/2019 18:11:54            0 (0x0000)

Property DeployDrive is now = Y:            ZTIGather             06/02/2019 18:11:54    0 (0x0000)

Property ResourceRoot is now = \\SED-MDT-WS\DeploymentShare$ ZTIGather          06/02/2019 18:11:54            0 (0x0000)

Property ResourceDrive is now = Y:        ZTIGather             06/02/2019 18:11:54    0 (0x0000)

Finished synchronizing the environments.           ZTIGather             06/02/2019 18:11:54    0 (0x0000)

Getting OS info ZTIGather          06/02/2019 18:11:55    0 (0x0000)

Property OSCurrentVersion is now = 10.0.17134             ZTIGather          06/02/2019 18:11:55    0 (0x0000)

Property OSCurrentBuild is now = 17134            ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Unknown operating system build number 17134 found, setting OSVersion to 'Other'.      ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Property OSVersion is now = Other        ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Property IsServerOS is now = False         ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Property IsServerCoreOS is now = False ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Finished getting OS info              ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Getting HAL information             ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Property HALName is now = acpiapic     ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Finished getting HAL information           ZTIGather             06/02/2019 18:11:55    0 (0x0000)

Getting network info     ZTIGather          06/02/2019 18:11:55            0 (0x0000)

Checking network adapter: [00000001] Adaptador de Rede 802.11n Broadcom        ZTIGather          06/02/2019 18:11:55            0 (0x0000)

MAC address = 68:94:23:B3:C7:A7         ZTIGather             06/02/2019 18:11:55    0 (0x0000)

IP Address = 10.101.65.178        ZTIGather             06/02/2019 18:11:55    0 (0x0000)

IP Address = fe80::65ab:472:4abc:9c9d ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Default Gateway = 10.101.64.1 ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Property IPAddress001 is now = 10.101.65.178 ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Property IPAddress002 is now = fe80::65ab:472:4abc:9c9d             ZTIGather          06/02/2019 18:11:56    0 (0x0000)

Property MacAddress001 is now = 68:94:23:B3:C7:A7             ZTIGather          06/02/2019 18:11:56    0 (0x0000)

Property DefaultGateway001 is now = 10.101.64.1             ZTIGather          06/02/2019 18:11:56    0 (0x0000)

Finished getting network info    ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Getting DP info ZTIGather          06/02/2019 18:11:56    0 (0x0000)

ConfigMgr distribution point = SED-MDT-WS     ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Property SMSDP is now = SED-MDT-WS ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Finished getting DP info              ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Getting WDS server info             ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Unable to determine WDS server name, probably not booted from WDS.        ZTIGather          06/02/2019 18:11:56            0 (0x0000)

Finished getting WDS server info            ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Property HostName is now = SED-EMPRE36-WS             ZTIGather          06/02/2019 18:11:56    0 (0x0000)

Getting asset info          ZTIGather          06/02/2019 18:11:56            0 (0x0000)

Unable to determine asset tag via WMI.             ZTIGather             06/02/2019 18:11:56    0 (0x0000)

Property AssetTag is now =        ZTIGather             06/02/2019 18:11:57    0 (0x0000)

Property SerialNumber is now = 3G6BSV1          ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property Make is now = Dell Inc.             ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property Model is now = Latitude E5430 non-vPro             ZTIGather          06/02/2019 18:11:58    0 (0x0000)

Property Product is now = 0X15F5          ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property UUID is now = 4C4C4544-0047-3610-8042-B3C04F535631 ZTIGather          06/02/2019 18:11:58    0 (0x0000)

Property Memory is now = 3969            ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property Architecture is now = X64        ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property ProcessorSpeed is now = 2501             ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property CapableArchitecture is now = AMD64 X64 X86             ZTIGather          06/02/2019 18:11:58    0 (0x0000)

Property IsLaptop is now = True              ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property IsDesktop is now = False          ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property IsServer is now = False              ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property IsUEFI is now = False   ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property IsOnBattery is now = False       ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property SupportsX86 is now = True      ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property SupportsX64 is now = True      ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Property SupportsSLAT is now = True     ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Finished getting asset info          ZTIGather             06/02/2019 18:11:58    0 (0x0000)

Getting OS SKU info       ZTIGather          06/02/2019 18:11:59            0 (0x0000)

Property OSSKU is now = PROFESSIONAL            ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Finished getting OS info              ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Determining the Disk and Partition Number from the Logical Drive C:\Windows           ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Getting virtualization info          ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Property IsHypervisorRunning is now = False     ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Property SupportsVT is now = True        ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Property SupportsNX is now = True        ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Property Supports64Bit is now = True    ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Property SupportsHyperVRole is now = True      ZTIGather             06/02/2019 18:11:59    0 (0x0000)

This computer does not appear to be a virtual machine (BIOS is 'DELL   - 1072009').        ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Property IsVM is now = False     ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Finished getting virtualization info         ZTIGather             06/02/2019 18:11:59    0 (0x0000)

Connection succeeded to MicrosoftVolumeEncryption             ZTIGather          06/02/2019 18:12:00    0 (0x0000)

There are no encrypted drives   ZTIGather             06/02/2019 18:12:00    0 (0x0000)

Property IsBDE is now = False    ZTIGather             06/02/2019 18:12:00    0 (0x0000)

Processing the VALIDATION phase.         ZTIGather             06/02/2019 18:12:00    0 (0x0000)

Unexpected response from web service: 407 Proxy Authentication Required

<html><head>

<meta type="copyright" content="Copyright (C) 1996-2015 The Squid Software Foundation and contributors">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<title>ERRO: Acesso negado ao cache</title>

<style type="text/css"><!--

 /*

Stylesheet for Squid Error pages

Adapted from design by Free CSS Templates

http://www.freecsstemplates.org

Released for free under a Creative Commons Attribution 2.5 License

*/

/* Page basics */

* {

             font-family: verdana, sans-serif;

}

html body {

             margin: 0;

             padding: 0;

             background: #efefef;

             font-size: 12px;

             color: #1e1e1e;

}

/* Page displayed title area */

#titles {

             margin-left: 15px;

             padding: 10px;

             padding-left: 100px;

             background: url('http://10.101.165.5/squid/alpa_logo.jpg') no-repeat left;

}

/* initial title */

#titles h1 {

             color: #000000;

}

#titles h2 {

             color: #000000;

}

/* special event: FTP success page titles */

#titles ftpsuccess {

             background-color:#00ff00;

             width:100%;

}

/* Page displayed body content area */

#content {

             padding: 10px;

             background: #ffffff;

}

/* General text */

p {

}

/* error brief description */

#error p {

}

/* some data which may have caused the problem */

#data {

}

/* the error message received from the system or other software */

#sysmsg {

}

pre {

    font-family:sans-serif;

}

/* special event: FTP / Gopher directory listing */

#dirmsg {

    font-family: courier;

    color: black;

    font-size: 10pt;

}

#dirlisting {

    margin-left: 2%;

    margin-right: 2%;

}

#dirlisting tr.entry td.icon,td.filename,td.size,td.date {

    border-bottom: groove;

}

#dirlisting td.size {

    width: 50px;

    text-align: right;

    padding-right: 5px;

}

/* horizontal lines */

hr {

             margin: 0;

}

/* page displayed footer area */

#footer {

             font-size: 9px;

             padding-left: 10px;

}

body

:lang(fa) { direction: rtl; font-size: 100%; font-family: Tahoma, Roya, sans-serif; float: right; }

:lang(he) { direction: rtl; }

--></style>

</head><body id="ERR_CACHE_ACCESS_DENIED">

<div id="titles">

<h1>ERRO</h1>

<h2>Acesso negado ao cache.</h2>

</div>

<hr>

<div id="content">

<p>O seguinte erro foi encontrado ao tentar recuperar a URL: <a href="http://sed-mdt-ws:9800/MDTMonitorEvent/PostEvent?">http://sed-mdt-ws:9800/MDTMonitorEvent/PostEvent?</a></p>

<blockquote id="error">

<p><b>Acesso negado ao cache.</b></p>

</blockquote>

<p>Desculpe. Atualmente, você não tem permissáo para requisitar http://sed-mdt-ws:9800/MDTMonitorEvent/PostEvent? deste cache até que você tenha se autenticado.</p>

<p>Por favor, contate o <a href="mailto:webmaster?subject=CacheErrorInfo%20-%20ERR_CACHE_ACCESS_DENIED&amp;body=CacheHost%3A%20brvolalpapxyp01%0D%0AErrPage%3A%20ERR_CACHE_ACCESS_DENIED%0D%0AErr%3A%20%5Bnone%5D%0D%0ATimeStamp%3A%20Wed,%2006%20Feb%202019%2020%3A12%3A17%20GMT%0D%0A%0D%0AClientIP%3A%2010.101.65.178%0D%0A%0D%0AHTTP%20Request%3A%0D%0AGET%20%2FMDTMonitorEvent%2FPostEvent%3FuniqueID%3D%26computerName%3DSED-EMPRE36-WS%26messageID%3D41000%26severity%3D1%26stepName%3DGather%2520local%2520only%26currentStep%3D1%26totalSteps%3D23%26id%3D4C4C4544-0047-3610-8042-B3C04F535631,68%3A94%3A23%3AB3%3AC7%3AA7%26message%3DProcessing%2520the%2520VALIDATION%2520phase.%26dartIP%3D%26dartPort%3D%26dartTicket%3D%26vmHost%3D%26vmName%3D%20HTTP%2F1.1%0AProxy-Connection%3A%20Keep-Alive%0D%0AAccept%3A%20*%2F*%0D%0AAccept-Language%3A%20pt-BR,pt%3Bq%3D0.5%0D%0AUser-Agent%3A%20Mozilla%2F4.0%20(compatible%3B%20Win32%3B%20WinHttp.WinHttpRequest.5)%0D%0AProxy-Authorization%3A%20NTLM%20TlRMTVNTUAADAAAAGAAYAKoAAAASARIBwgAAABwAHABYAAAAGgAaAHQAAAAcABwAjgAAAAAAAADUAQAABYKIogoA7kIAAAAPCQ0QLPt2sbcBjBVFT1jqEFMARQBEAC0ARQBNAFAAUgBFADMANgAtAFcAUwBBAGQAbQBpAG4AaQBzAHQAcgBhAGQAbwByAFMARQBEAC0ARQBNAFAAUgBFADMANgAtAFcAUwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABca4oJSB8XU7aw9EGgzra8AQEAAAAAAACy4QBCWL7UAWmINmPB45GgAAAAAAIACABBAEwAUABBAAEAHgBCAFIAVgBPAEwAQQBMAFAAQQBQAFgAWQBQADAAMQAEAAIAAAADABIAcwBlAGQALQBwAHIAbwB4AHkABwAIALLhAEJYvtQBBgAEAAIAAAAIADAAMAAAAAAAAAAAAAAAADAAAHMRpyHigs3+d9ZF0AiOzicWUpcmavtKNnjnZh50hKXICgAQAAAAAAAAAAAAAAAAAAAAAAAJADAASABUAFQAUAAvAFMARQBEAC0AUABSAE8AWABZAC4AYQBsAHAAYQAuAGMAbwByAHAAAAAAAAAAAAAAAAAA%0D%0AHost%3A%20sed-mdt-ws%3A9800%0D%0A%0D%0A%0D%0A">administrador do cache</a> se você está tendo dificuldades em se autenticar ou <a href="http://brvolalpapxyp01/cgi-bin/chpasswd.cgi">mude</a> sua senha.</p>

<br>

</div>

<hr>

<div id="footer">

<p>Gerado Wed, 06 Feb 2019 20:12:17 GMT por brvolalpapxyp01 (squid/3.5.23)</p>

<!-- ERR_CACHE_ACCESS_DENIED -->

</div>

</body></html>

             ZTIGather          06/02/2019 18:12:00    0 (0x0000)

Event 41000 sent: Processing the VALIDATION phase.             ZTIGather          06/02/2019 18:12:00    0 (0x0000)

Only gathering local settings (no rules processing).             ZTIGather          06/02/2019 18:12:00    0 (0x0000)

Determining the INI file to use.  ZTIGather             06/02/2019 18:12:00    0 (0x0000)

Using DEFAULT VALUE: Ini file = \\SED-MDT-WS\DeploymentShare$\Control\CustomSettings.ini             ZTIGather          06/02/2019 18:12:00    0 (0x0000)

Finished determining the INI file to use. ZTIGather             06/02/2019 18:12:01    0 (0x0000)

Skipping rules processing.           ZTIGather             06/02/2019 18:12:01    0 (0x0000)

Remapping variables.    ZTIGather          06/02/2019 18:12:01            0 (0x0000)

Property TaskSequenceID is now = BUILD001     ZTIGather             06/02/2019 18:12:01    0 (0x0000)

Property DeploymentType is now = UPGRADE   ZTIGather             06/02/2019 18:12:01    0 (0x0000)

Finished remapping variables.   ZTIGather             06/02/2019 18:12:01    0 (0x0000)

ZTIGather processing completed successfully.    ZTIGather             06/02/2019 18:12:01    0 (0x0000)

Unexpected response from web service: 407 Proxy Authentication Required

<html><head>

<meta type="copyright" content="Copyright (C) 1996-2015 The Squid Software Foundation and contributors">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<title>ERRO: Acesso negado ao cache</title>

<style type="text/css"><!--

 /*

Stylesheet for Squid Error pages

Adapted from design by Free CSS Templates

http://www.freecsstemplates.org

Released for free under a Creative Commons Attribution 2.5 License

*/

/* Page basics */

* {

             font-family: verdana, sans-serif;

}

html body {

             margin: 0;

             padding: 0;

             background: #efefef;

             font-size: 12px;

             color: #1e1e1e;

}

/* Page displayed title area */

Julio Vaz http://jvaz.wordpress.com

Hi,

Is there a way to update bios using mdt ?

Thanks 

I am trying to complete in-place upgrades on various Dell desktops, servers and notebooks and have run into failures that I cannot resolve.

I am using the same process on all computers, but if I try the upgrade on Dell Optiplex 5050s or Precision 5810s the upgrade fails. Both computers have identical software and both are using the same Task Sequesnce. Another unusual problem is if I upgrade from Win 7 to 10, the failure causes a rollback, but with Win 8 to 10 the upgrade completes but none of the post processing runs. This stops our layout, local policy, security settings, etc. from being configured.

I am using MDT 8450

To upgrade the computer, I have a .bat file on the deployment share. For the upgrade, I copy the file locally, right click on the .bat file and choose run as administrator. 

bat file code:

Start "" "\\mdtserver\deploymentshare$\LiteTouch.vbs - Shortcut.lnk"

Links to the bdd and smsts logs for both success and failure are located below.

Failure - https://www.dropbox.com/sh/us7wxxyo6jov1bt/AAAjF5sfpqPJcNpygRt2oR13a?dl=0

Success - https://www.dropbox.com/sh/s19dsihc04jw6ts/AADca8JAPiMJ2Y5tLLyJeD9Ta?dl=0

Thank you for any assistance

I have problems with one device in our environment. 

We use Surface and HP Probook and also Dell Latitude 3390.

Only the Dell I get problems to image with MDT version 8450.

Info :

MDT version 8456

ADK version 1809

Windows 10 build 1809

This information I get form the BDD.Log file

New ZTIDiskPartition : \\MININT-UHHD9CS\root\cimv2:Win32_LogicalDisk.DeviceID="D:"    \\MININT-UHHD9CS\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" LTIApply 2/8/2019 4:21:55 PM 0 (0x0000)
About to run command: "\\WINWDS01\DeploymentShare$\Servicing\X64\DISM.exe"  /Apply-Image /ImageFile:"\\WINWDS01\DeploymentShare$\Operating Systems\Windows 10 Pro Build 1803\Sources\install.wim" /Index:5 /ApplyDir:D: LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
Command has been started (process ID 1952) LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
  Console > Deployment Image Servicing and Management tool LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
  Console > Version: 10.0.17763.1 LTIApply 2/8/2019 4:21:56 PM 0 (0x0000)
  Console > Applying image LTIApply 2/8/2019 4:22:09 PM 0 (0x0000)
  Console >
[                           1.0%                           ]  LTIApply 2/8/2019 4:22:10 PM 0 (0x0000)
  Console >
[=                          2.0%                           ]  LTIApply 2/8/2019 4:22:18 PM 0 (0x0000)
  Console >
[=                          3.0%                           ]  LTIApply 2/8/2019 4:22:23 PM 0 (0x0000)
  Console >
[==                         4.0%                           ]  LTIApply 2/8/2019 4:22:27 PM 0 (0x0000)
  Console >
[==                         5.0%                           ]  LTIApply 2/8/2019 4:22:32 PM 0 (0x0000)
  Console >
[===                        6.0%                           ]  LTIApply 2/8/2019 4:22:38 PM 0 (0x0000)
  Console >
[====                       7.0%                           ]  LTIApply 2/8/2019 4:22:43 PM 0 (0x0000)
  Console >
[====                       8.0%                           ]  LTIApply 2/8/2019 4:22:48 PM 0 (0x0000)
  Console >
[=====                      9.0%                           ]  LTIApply 2/8/2019 4:22:52 PM 0 (0x0000)
  Console >
[=====                      10.0%                          ]  LTIApply 2/8/2019 4:22:58 PM 0 (0x0000)
  Console >
[======                     11.0%                          ]  LTIApply 2/8/2019 4:23:03 PM 0 (0x0000)
  Console >
[======                     12.0%                          ]  LTIApply 2/8/2019 4:23:07 PM 0 (0x0000)
  Console >
[=======                    13.0%                          ]  LTIApply 2/8/2019 4:23:11 PM 0 (0x0000)
  Console >
[========                   14.0%                          ]  LTIApply 2/8/2019 4:23:16 PM 0 (0x0000)
  Console >
[========                   15.0%                          ]  LTIApply 2/8/2019 4:23:21 PM 0 (0x0000)
  Console > Error: 1392 LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
  Console > The file or directory is corrupted and unreadable. LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
  Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
Return code from command = 1392 LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
FAILURE ( 5624 ): 1392: Run DISM:  /Apply-Image /ImageFile:"\\WINWDS01\DeploymentShare$\Operating Systems\Windows 10 Pro Build 1803\Sources\install.wim" /Index:5 /ApplyDir:D: LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
Event 41002 sent: FAILURE ( 5624 ): 1392: Run DISM:  /Apply-Image /ImageFile:"\\WINWDS01\DeploymentShare$\Operating Systems\Windows 10 Pro Build 1803\Sources\install.wim" /Index:5 /ApplyDir:D: LTIApply 2/8/2019 4:23:27 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 2/8/2019 4:23:27 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 2/8/2019 4:23:27 PM 0 (0x0000)
Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Validating connection to \\WinWDS01\DeploymentLogs$ LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Mapping server share: \\WinWDS01\DeploymentLogs$ LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Already connected to server WinWDS01 LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
OSDTargetDriveCache was determined earlier : D: LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Property OSDTargetDriveCache is now = D: LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Property OSDisk is now = D: LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\LiteTouch.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\LiteTouch.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\LTIApply.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\LTIApply.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\LTICopyScripts.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\LTICopyScripts.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\PnpEnum.xml to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\PnpEnum.xml LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\Wizard.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\Wizard.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIBDE.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIBDE.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIConfigure.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIDiskpart.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIDrivers.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIDrivers.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIGather.log LiteTouch 2/8/2019 4:23:28 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTINextPhase.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTINextPhase.log LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIPatches.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIPatches.log LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
Copying D:\MININT\SMSOSD\OSDLOGS\ZTIValidate.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ZTIValidate.log LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
Copying X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\SMSTS.LOG LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
Copying X:\WINDOWS\Debug\Netsetup.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
Copying X:\WINDOWS\System32\wpeinit.log to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\ LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)
Copying log D:\MININT\SMSOSD\OSDLOGS\BDD.log contents to \\WinWDS01\DeploymentLogs$\MININT-UHHD9CS\BDD.LOG LiteTouch 2/8/2019 4:23:29 PM 0 (0x0000)

I'm using the LGPO "DefaultAssociationsConfiguration" option, as well as applying the XML using DISM /online.

The XML appears to take, as the icons for .pdfs are changed to adobe reader icons, but I'm still seeing this prompt, any help is much appreciated.

And here is my XML.

<?xml version="1.0" encoding="UTF-8"?><DefaultAssociations><Association Identifier=".pdf" ProgId="AcroExch.Document.DC" ApplicationName="Adobe Acrobat Reader DC" /></DefaultAssociations>

/BG

-BrianG (http://supportishere.com)

Hello,

Starting last month out MDT deployments are randomly generating the following errors while running the ZTIWindowsUpdate script.  I cant determine the cause.  I have search for any information and nothing helps so far. Sometimes a PC will work and sometimes it will not.  We have 1 WSUS server.  If updates we use the same WSUS server to manually install the updates after imaging is complete (continue on error).  So I think the WSUS server is healthy.

Has anybody else run into this issue?

Random Error when running MDT task sequence:

Scan complete, ready to install updates. Count = 5

Begin Downloading...

ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate:  (-2145091577  0x80248007)

Event 41002 sent: ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate:  (-2145091577  0x80248007)

Thanks for your help!

-Jason

Hi!

I'm having issues with something I thought should be very smart. The possiblity to choose in the start of a specific deployment if the computer should join our domain or just stay in a workgroup.

If I blank out every domain settings in [W10X64-1803] it will join the workgroup Ive specified, but if not, it will somewhere in postinstall join the domain with name as configured. I want it to stay in the workgroup.

I would also love a tip on how to set specific tasks in the TS for if the computer is in the domain or in the workgroup.

Anyone who has a solution for this?

Under you can see my two CustomSettings.ini files.

CustomSetting:
[Settings]
Priority=DefaultGateway, ByLaptopType, ByDesktopType, Model, SetAlias, Default
Properties=MyCustomProperty, ModelAlias, MakeAlias, MacAlias, SMBIOSBIOSVersion, ComputerLocationName, ComputerTypeName

[DefaultGateway]
10.247.10.1=NORWAY

[NORWAY]
ComputerLocationName=no

[ByLaptopType]
Subsection=Laptop-%IsLaptop%

[Laptop-True]
ComputerTypeName=lt

[ByDesktopType]
Subsection=Desktop-%IsDesktop%

[Desktop-True]
ComputerTypeName=ws

[HP Elite x2 1012 G1 Tablet]
ComputerTypeName=tablet

[Surface Pro 4]
ComputerTypeName=surface

[SetAlias]
UserExit=AliasUserExit.vbs
MakeAlias=#SetMakeAlias()#
ModelAlias=#SetModelAlias()#
SMBIOSBIOSVersion=#SetSMBIOSBIOSVersion()#
MacAlias=#SetMacAlias()#

[MAKE]
DriverSelectionProfile=Nothing
DriverGroup001=%Model%

[Default]
OSDComputername=%ComputerLocationName%-%ComputerTypeName%-
_SMSTSORGNAME=DOMAIN - %TaskSequenceID% on %OSDComputername%

BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
OSInstall=Y
SkipBDDWelcome=YES
KeyboardLocale=nb-NO
UserLocale=nb-NO
UILanguage=nb-NO
AdminPassword=P@ssw0rd
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipApplications=YES
DoCapture=NO
ComputerBackupLocation=\\MDTSERVER\MDTProduction$\captures

SkipFinalSummary=YES
TimeZone=110
TimeZoneName=W. Europe Standard Time
WSUSServer=http://MDTSERVER.DOMAIN.com:8530

Home_page=http://www.DOMAIN.no
EventService=http://MDTSERVER:9800

CustomSettingWG.ini:
[Settings]
Priority=DefaultGateway, ByLaptopType, ByDesktopType, TaskSequenceID, Model, Default
Properties=MyCustomProperty, ComputerLocationName, ComputerTypeName

[Default]
SkipDomainMembership=YES
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join 
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com

[W10X64-1803O]
SkipDomainMembership=YES
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join 
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com

[W10X64-1803]
SkipDomainMembership=NO
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join 
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com
JoinWorkGroup=WORKGROUPNAME

Some screendumpts:

Problem,

I am getting MMC console error while opening deployment Workbench at few locations.

Error:

MMC has detected an error in a snap-in and will unload it

FX:-{ffb8695a-66b4-4929-abb6-15cb8bd2ae3d}

Type 'Microsoft.BDD.Workbench.WrapperException' in assembly

Exception type:

  System.Runtime.serialization.SerializationException

Thanks in Advance

Dinesh Vinay

I'm trying to set up a deployment server for a custom wim of Windows 10 Ent x64 v1809. The Lite touch installation keeps failing. I'm using MDT v6.03 (Build 9600) and my Windows Server 2012 R2. I've tried multiple different solves so far including: 

-stripping my task sequence down to the bare essentials

-removing spaces from the name of my deployment share 

-changing out my custom image for a stock windows iso

-disabling the bios formatting step in the task sequence and using only UEFI

Any help would be appreciated. 

Failure ( 5616 ): 1:Verify BCDBootEx

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Failed to run the action: Install Operating System.

Unknown error (Error: 000015F0; Source: Unknown)

The execution of the group (Install) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Install Operating System. Execution of task sequence failed.

Unknown error (Error: 000015F0; Source; Unknown)

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