I copy the Layout you posted and I could not make it work. When I export the layout and through GPO use it, it works. As soon as I made the most minimal modification, it stops working.

Thank you in advance

This is the Layout I copied from your blog.

<?xml version="1.0" encoding="utf-8"?>
<LayoutModificationTemplate
    xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
    xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
    xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
    xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"
    Version="1">
  <LayoutOptions StartTileGroupsColumnCount="1" />
  <DefaultLayoutOverride>
    <StartLayoutCollection>
  <defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout">
        <start:Group Name="Applications" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout">
          <start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationID="Microsoft.InternetExplorer.Default" />
          <start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationID="Chrome" />
          <start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationID="Microsoft.Windows.Computer" />
        </start:Group>
        <start:Group Name="Apps" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout">
          <start:Tile Size="4x4" Column="0" Row="0" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
          <start:Tile Size="2x2" Column="4" Row="0" AppUserModelID="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
          <start:Tile Size="2x2" Column="4" Row="2" AppUserModelID="Microsoft.WindowsMaps_8wekyb3d8bbwe!App" />
        </start:Group>
      </defaultlayout:StartLayout>
    </StartLayoutCollection>
  </DefaultLayoutOverride>
  <CustomTaskbarLayoutCollection PinListPlacement="Replace">
    <defaultlayout:TaskbarLayout>
      <taskbar:TaskbarPinList>
        <taskbar:DesktopApp DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\File Explorer.lnk" />
        <taskbar:DesktopApp DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Internet Explorer.lnk" />
      </taskbar:TaskbarPinList>
    </defaultlayout:TaskbarLayout>
  </CustomTaskbarLayoutCollection>
</LayoutModificationTemplate>

My MDT server has been working for a year with no issues adding new hardware.

Just got a new laptop - Dell XPS 13 9470 - and I have downloaded the Dell Drivers Pack, created the new Folder in the OOB Drivers folder where the rest of the drivers are. I checked it's hardware name.

I use all the drivers in the PXE so whilst it takes a while to build, I don't need to do it very often. So after adding the new drivers I rebuilt the deployment share from scratch.

However, when I boot the machine up, choose the build I want to apply, and it starts running, it then fails, as it can't find the storage driver.

Help, I need to get this built, and this process above has always worked in the past. Really at a loss as to what I have done wrong.

BDD.log file https://1drv.ms/f/s!Atcjdqx_lmVHk1M3y1v_ue9Zn9_o 

following the following document https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image after figure <g class="gr_ gr_11 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-ins replaceWithoutSep" data-gr-id="11" id="11">12</g> you are asked to amend the WinPE settings the MMC crashes.  with unhandled Exception;

 at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileSystemEnumerableIterator`1.CommonInit()
   at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
   at System.IO.Directory.GetFiles(String path)
   at Microsoft.BDD.Core.DeploymentTools.GetFeaturePacks(String platform, String deploymentSharePath)
   at Microsoft.BDD.Workbench.DeployWindowsPE.RefreshData()
   at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)
   at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Can anyone help?



I am using MDT to deploy a Windows 10 image to a Dell latitude 5570. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty. Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta. It deletes c:\MININT folder so cannot get the BDD.log or the task sequence log.

• Deploying windows 7 works just fine.
• The version of MDT is 2013 Update 2

Hello,

i want a automatic installation of Office 2019 deployed with MDT (as application).

With earlier versions of MS Office i did by : setup.exe /config proplus.ww\config.xml

I think this is not possible anymore with Office 2019.

Until now i can deploy office 2019 with the setup.exe and configuration-Office365-x64.xml

My xml-file is:

With this setup, the volume licensing version is downloaded, and installed.

Problem:

After starting an Office Application, office must still be activated with the same key.

Anybody having a (better?) solution for the deploying Office 2019 with mdt?

Anybody having a solution for the activation-problem?

Thx

MDT 8450, ADK 1809. Noticed during autobuild/capture task, Office 2019 does not rearm and gives an error. This happens no matter if using Windows 10 Enterprise 10 1803 or 1809. Office 2016 works fine on both of these OS's. Manually running OSPPREARM.EXE seems to work fine, at least it gives the rearm successful. Here is a screen from the BDD.log of the error:

Hi,

1. first Dell OptiPlex 7050 model. Added drivers to Out of Box. The image is Windows7 (Dell supports this downgrade).

Deployed without problem corporate image from MDT. Device manager is clean.

2. Knowing that drivers are OK, created Offline Media Key.

3. Deployed from the Key on the same first machine.

PROBLEM: Keyboard, mouse are dead...  During Windows startup lights from mouse and keys gone.

Any ideas what it could be?

Thx.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Hi guys! i bought the new laptop Dell Latitude E6510 and try to install the enterprise image but i got the error:

"A connection to the deployment share could not be made. The deployment will not proceed. The following networking device did not have a driver installed PCI\VEN_8086&DEV_10EA&SUBSYS_040B1028&REV_05."

I look on internet and i found out that it is the intel network card driver missing. So i get the driver from Dell website and i added this drivers in the MDT console.

Then i have updated the deployment share to rebuild the boot images. Everything went fine but i always get this error.

Am I missing something ?

So we are moving to a filtering service in our schools called Securly. We use MS Intune to manage our devices, but Securly is DNS based. I'm still figuring out issues with the root certificate not being pushed out through the profile, but I want to be ready when we do get it running.

So, they give you a little bat file and some instructions, but I am thinking surely this can be done more gracefully with a powershell script. The directions are to create a GPO to copy the bat file, create a scheduled task to run "On an event" 

How might I go about setting the DNS server if the network changes to one outside of of ours?  

Set-DnsClientServerAddress would be the correct command, correct?

Hi Guys,

I get a problem with my MDT server. I have a DELL Latitude 5490 to install windows 10 by MDT. I can get in MDT to select the image which I deployed. It can be installed to the laptop. But when it reboot, there is no boot manager on the boot menu. I have inject the disk driver into the out-of-box driver. Do you have any good ideas to solve it? 

Many thanks. 

Hi All,

I'm configuring deployments for Windows 10 and Server 2016. I've got the majority of the task sequence working, however I'm stuck on the MachineObjectOU attribute. Based off the TaskSequenceID attribute, I want to use different OU paths for the domain join section.

I've added entries in as follows:

[Settings]

Priority=TaskSequenceID,Default
Properties=MyCustomProperty

[000]

MachineObjectOU=OU=LONDON,OU=Desktops,OU=Clients,OU=!Computer Env,DC=domain,DC=com
JoinDomain=domain.com
DomainAdmin=systemdeployment
DomainAdminDomain=domain
DomainAdminPassword=password

[WS16-RDS]

MachineObjectOU=OU=RDS 2016,OU=Servers,OU=!Computer Env, DC=domain,DC=com
JoinDomain=domain.com
DomainAdmin=systemdeployment
DomainAdminDomain=domain
DomainAdminPassword=password

Windows 10 (TSID=000) obviously works fine, unfortunately when it gets to the Server 2016 (TSID=WS16-RDS) it seems to just use the MachineObjectOU variable as defined in the Windows 10 TaskSequenceID.

Is there something I'm missing with the way I'm setting the TaskSeqenceID in the priority order?

Hey everyone,  is there a way to put a MOTD, Disclaimer, Legal Notice, etc. in MDT?  Don't care where it goes, just something that the user has to read/acknowledge before they start clicking task sequences.

Thanks

**I'm fairly new to MDT so please bear with me**

I have captured a working .wim image from a "Gold" Deployment Share with zero errors and works fine.

I then create another Deployment Share and import the captured .wim into the Operating Systems and create the standard vanilla TS setup just to see if the .wim will deploy correctly to a VM (VMWare).  I import the LiteTouchx64.wim into the Boot folder of WDS and away we go. WDS is already configured and working as it should along with DHCP, DC, DNS, etc.

Everything is working fine until right before the last step which is installing some final applications like Firefox.

The weird part is if I hit "Ok" the deployment continues just fine and even finishes with Success Deployment Summary "During the deployment process, 0 errors and 0 warnings were reported"

I did pull up the BDD.log and the only thing I can find related to LTIBootstrap.vbs is stating that "File C:\MININT\Scripts\LTIBootstrap.vbs already exists in Target" -- in fact it says that for all the vbs scripts in C:\MININT\Scripts\____.vbs. That doesn't correlate to the same location however (C:\LTIBootstrap.vbs) as per the error message.

I do see earlier in the BDD.log that it did copy these scripts successfully from my Deployment Share with no issues.

Has anyone else seen this issue and if so how did you fix it? Any guidance or insight is greatly appreciated.

Hi community,

I want to achieve a seemingly simple task: When I build my master image (Windows 10 Education 1803, with Office 2016 and other things), the task sequence correctly runs the step with installing updates via WSUS. However, it seems there are only security updates being installed. Office 2016 updates are completely omitted.

My unsuccsessful attempt to solve this was like this: I let the task sequence import lokal GPOs which are configured to install all reccomended updates and also optional updates then do a restart and then continue with the wsus updates process.

The following happend after the restart: the GPOs are correctly applied and the internal wsus is contacted and the usual update process starts. HOWEVER: it makes no difference. there are no Office 2016 Updates installed and only the same Windows Updates like before.

When i go into the Windows Update settings you can see that the GPOs are not yet applied correctly, since you still have the option to manually change the switch for searching for recommended updates etc. I know this behavior from previous versions where it seems that only after the first initial search for updates via internet the settings are applied in the update settings page.

What is the solution here? What am I doing wrong?

Greetings!

I have a very odd issue that I'm trying to find the root cause.  I have 4 WDS servers setup by location deploying the images from the MDT.  Its works at all locations for most computer makes and models except we bought a new one, Dell OptiPlex 7060 and the task sequence is blank at one location.  I've added the drivers to the MDT and if I add the PC to the database by serial number and specify the task sequence, it images fine.

I can take this same PC to another location and PXE boot to that WDS server and the task sequence appears as expected.  At that location I had the IP helper changed to the other WDS server and I was able to repeat the same result.  I took the computer back to the first location and the task sequence list does not appear.  I then had the IP helper there changed to point to the working location's WDS server an the task sequence was again blank.

I do not have anything set in the MDT database for location at either of these locations.  I validated the same boot image is on each WDS server in question.  The deployment share is setup using DFS-R between locations so they are all the exact same as well.  This is only one model at one physical location that is having this problem.  While I can work around this, any help in finding the root cause would be greatly appreciated!

I am looking to create a customized Windows 10 image. I have installed an MDT 2013 Update 2 server to do the install. Within my image I would like to install Office Click-to-Run 2016. I am using the following article for guidance:

https://technet.microsoft.com/en-us/library/dn314789.aspx

I am using MDT to both deploy and capture the image. When the image finishes capturing I am getting the following warning:

"Unexpected return code while re-arming Office 2016, RC = -1073425660"

Any help in determining if this is an issue and fixing it would be appreciated.

Thanks,

Mike

Solutions Architect

Hello everyone,

I've been playing with my MDT2013 to create a second deployment share to build images. But now I'm getting the following error from my first share used to deploy images:

The task wizard is not even showing.

Here's myBDD.log. I can't figure out what's wrong.Can anyone help?

Hi,

I've done a ReferenceImage in Hyper-V and it has been captured and imported into DeploymentShare.

I relized that either in VM or in hardware (HP ProDesk 400 G4) during Deployment, before StateRestore blank keeps black (no cursor, no ctrl+alt+supr, no ctrl+shift+esc) just thing I can do is turn off power (virtually in Hyper-V VM and phisically in HP ProDesk). Once I power on machine, task sequence finish and it shows no error.

I've only be able to find that if I set CopyProfile to false, black screen it isnt shown. If set CopyProfile to true it happens. I set too some parameters in Unattend.xml as ColorDepth, HorizontalResolution, VerticalResolution and RefreshRate because it was complaining they weren`'t set first time I set CopyProfile to true. Stucks at 21:54 and virtaully power off/on at 22:16.

I dont see anything weird in logs. Part of BDD.log

Property PHASE is now = STATERESTORE	ZTINextPhase	30/11/2018 21:54:12	0 (0x0000)
ZTINextPhase COMPLETED.  Return Value = 0	ZTINextPhase	30/11/2018 21:54:12	0 (0x0000)
ZTINextPhase processing completed successfully.	ZTINextPhase	30/11/2018 21:54:12	0 (0x0000)
Command completed, return code = -2147021886	LiteTouch	30/11/2018 21:54:13	0 (0x0000)
Property LTIDirty is now = FALSE	LiteTouch	30/11/2018 21:54:13	0 (0x0000)
If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.	LiteTouch	30/11/2018 21:54:13	0 (0x0000)
Property OSDTargetDriveCache is now = DIRTY	LiteTouch	30/11/2018 21:54:13	0 (0x0000)
LTI initiating task sequence-requested reboot.	LiteTouch	30/11/2018 21:54:13	0 (0x0000)
Property start is now = 	LiteTouch	30/11/2018 22:16:06	0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8450.1000	LiteTouch	30/11/2018 22:16:06	0 (0x0000)
ZTIUtility!GetAllFixedDrives (Falso)	LiteTouch	30/11/2018 22:16:06	0 (0x0000)
New ZTIDisk : \\USUARIO-7HCD5DB\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	30/11/2018 22:16:07	0 (0x0000)
New ZTIDiskPartition : \\USUARIO-7HCD5DB\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\USUARIO-7HCD5DB\root\cimv2:Win32_LogicalDisk.DeviceID="C:"	LiteTouch	30/11/2018 22:16:07	0 (0x0000)
New ZTIDisk : \\USUARIO-7HCD5DB\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	30/11/2018 22:16:07	0 (0x0000)
New ZTIDisk : \\USUARIO-7HCD5DB\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	30/11/2018 22:16:07	0 (0x0000)
ZTIUtility!GetAllFixedDrives =   C: 	LiteTouch	30/11/2018 22:16:07	0 (0x0000)
Found existing task sequence state information in C:\_SMSTaskSequence, will continue	LiteTouch	30/11/2018 22:16:07	0 (0x0000)

Hello,

I'm using MDT to create an reference image. (w10 enterprise, on a VMware virtual machine)

I did this successfully with Windows 10 1709.

Recently I imported Windows 10 1803, installed the matching ADK and started from scratch.

I did copy my 1709 TS to create an 1803 reference image.

Before starting the TS to create an reference image I removed offline a number of UWA from the WIM. I did the same before in the process of the 1709 reference image.

During the TS for the creation of the 1803 reference image I have added 2 suspend steps.

During the first one I install some applications, change some registry settings for the local administrator account etc.

Straight after the 1th suspend the TS will reboot the reference machine and perform Windows Update.

During the 2nd suspend I install another application, which will not install during the first suspend as a reboot is apparently pending at the end of the 1th suspend. The application added during the 2nd suspend does restart explorer.exe.

After the 2nd suspend the sysprep and capture should take please, however the sysprep fails.

see below the setupact.log:

If I'm reading it correct, there is no APPX issue. It sounds to me like the unattend.xml, but I've no clue what.

With the same file I had no problem with creating an 1709 image.

Rgds,

Andy

2018-06-18 16:11:18, Info                  SYSPRP ========================================================
2018-06-18 16:11:18, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
2018-06-18 16:11:18, Info                  SYSPRP ========================================================
2018-06-18 16:11:18, Info       [0x0f004d] SYSPRP The time is now 2018-06-18 16:11:18
2018-06-18 16:11:18, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\windows\system32\sysprep\Panther
2018-06-18 16:11:18, Info       [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
2018-06-18 16:11:18, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
2018-06-18 16:11:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET'
2018-06-18 16:11:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
2018-06-18 16:11:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
2018-06-18 16:11:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIT'
2018-06-18 16:11:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
2018-06-18 16:11:18, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
2018-06-18 16:11:18, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
2018-06-18 16:11:18, Info                  SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
2018-06-18 16:11:18, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
2018-06-18 16:11:18, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
2018-06-18 16:11:18, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
2018-06-18 16:11:18, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll
2018-06-18 16:11:19, Info                  SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error
2018-06-18 16:11:19, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'generalize' internal providers.
2018-06-18 16:11:19, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 1
2018-06-18 16:11:19, Info                  SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml, and mode <null>
2018-06-18 16:11:19, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml
2018-06-18 16:11:19, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
2018-06-18 16:11:19, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
2018-06-18 16:11:19, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll
2018-06-18 16:11:19, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.

2018-06-18 16:11:19, Info                  SYSPRP All appx packages were verified to be inbox or alluser installed.

2018-06-18 16:11:19, Info                  SYSPRP ActionPlatform::LaunchModule: Successfully executed 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll without error
2018-06-18 16:11:19, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll
2018-06-18 16:11:19, Info                  SYSPRP ActionPlatform::LaunchModule: Successfully executed 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll without error
2018-06-18 16:11:19, Info       [0x0f004a] SYSPRP WaitThread:Entering spawned waiting thread
2018-06-18 16:11:19, Info                         [sysprep.exe] UnattendFindAnswerFile: Looking at explicitly provided unattend file [C:\windows\system32\sysprep\unattend.xml]...
2018-06-18 16:11:19, Info                         [sysprep.exe] UnattendFindAnswerFile: [C:\windows\system32\sysprep\unattend.xml] meets criteria for an explicitly provided unattend file.
2018-06-18 16:11:19, Info                  SYSPRP SysprepSearchForUnattend: Using unattend file at [C:\windows\system32\sysprep\unattend.xml].
2018-06-18 16:11:20, Info                  SYSPRP SysprepSearchForUnattend: [generalize] pass in unattend file [C:\windows\system32\sysprep\unattend.xml] either doesn't exist or passed validation
2018-06-18 16:11:20, Info                  SYSPRP WinMain:Found unattend file at [C:\windows\system32\sysprep\unattend.xml]; caching...
2018-06-18 16:11:20, Info                  SYSPRP WinMain:Processing unattend file's 'generalize' pass...
2018-06-18 16:11:20, Info                  SYSPRP Sysprep is running a generalize pass with the following unattend file: [%windir%\panther\unattend.xml]
2018-06-18 16:11:20, Info                  CSI     WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffebc43c2b9 @0x7ffebbf120cd @0x7ffebbf28b76 @0x7ffebbf007f1 @0x7ffebbeff5ad @0x7ff73bbc1398)
2018-06-18 16:11:20, Error                 CSI    00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #156# from CWcmScalarInstanceCore::GetCurrentValue(options = 262144, status = '(null)', value = { type: 40972, bytes ( 46 ): 5700310030002d0031003800300033002d00310035004a0075006e0032003000310038002d003000300031000000 })
[gle=0x80004005]
2018-06-18 16:11:20, Error                 CSI    00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #155# from CWcmScalarInstanceCore::PutCurrentValue(options = 0, value = { type: 40972, bytes ( 58 ): 570049004e003100300045005800360034005f005200450046005f003000300031005f00310032004a0075006e00320030003100380000000000 })
[gle=0x80004005]
2018-06-18 16:11:20, Error                 CSI    00000003 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #149# from CChildContextStore::ApplyToNamespace(namespace = @0x1ccbfb61910)[gle=0x80004005]
2018-06-18 16:11:20, Info                  SYSPRP RunUnattendGeneralizePass: Sysprep unattend generalize pass exits; hr = 0x80220008, hrResult = 0x0, bRebootRequired = 0x0
2018-06-18 16:11:20, Error      [0x0f00a7] SYSPRP WinMain:Failed to process unattend file's 'generalize' pass; hr = 0x80220008
2018-06-18 16:11:20, Info       [0x0f004c] SYSPRP WaitThread:Exiting spawned waiting thread
2018-06-18 16:11:20, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
2018-06-18 16:11:20, Info       [0x0f004d] SYSPRP The time is now 2018-06-18 16:11:20

SetupErr.log

2018-06-18 16:11:20, Error                 CSI    00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #156# from CWcmScalarInstanceCore::GetCurrentValue(options = 262144, status = '(null)', value = { type: 40972, bytes ( 46 ): 5700310030002d0031003800300033002d00310035004a0075006e0032003000310038002d003000300031000000 })
[gle=0x80004005]
2018-06-18 16:11:20, Error                 CSI    00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #155# from CWcmScalarInstanceCore::PutCurrentValue(options = 0, value = { type: 40972, bytes ( 58 ): 570049004e003100300045005800360034005f005200450046005f003000300031005f00310032004a0075006e00320030003100380000000000 })
[gle=0x80004005]
2018-06-18 16:11:20, Error                 CSI    00000003 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #149# from CChildContextStore::ApplyToNamespace(namespace = @0x1ccbfb61910)[gle=0x80004005]
2018-06-18 16:11:20, Error      [0x0f00a7] SYSPRP WinMain:Failed to process unattend file's 'generalize' pass; hr = 0x80220008

unattend

.xml