I'm hoping that someone out there can help me resolve this problem that I am having. I have worked on this for several days now, tring almost anything that I could find in the posts here as well as any other message board.

The problem is this: I am trying to do a PC refresh of an existing XP machine to Windows 7 using the MDT 2010 Update 1 toolkit. I have imported a base OS into the workbench, added applications to the workbench, added out of box drivers, and created a task sequence. I then updated the deployment share.

On the XP machine that I want to "refresh", I have started the LiteTouch.vbs script and it runs through completion in the XP environment. It captures the user state (I opened up Windows explorer and could see files being created under the MiniNT folder of the users profiles) and completes that process and reboots.

Here is where the problem starts. After rebooting and "starting Windows 7", upon getting to the flashy "Microsoft | Solution Accelerators" screen I get a popup error stating "Connection to deployment share (\\servername\DeploymentShare$) cannot be made. Connection OK. Possible cause: Invalid credentials." Then you get three options to Ignore, Abort, Cancel. I believe that the "Ignore" and "Abort" options will put you out into a command window.

So when in that window, I have tried various things to see if I have connectivity as well as the IP settings (just to make sure that I am really communicating on the network). An IPCONFIG/ALL shows that I have indeed pulled a valid IP address from the DHCP server and a ping of the server IP does result in returned traffic. Even a ping by servername returns packets, so it's not a communication problem.

When trying to do a net view servername it returns an "System error 5 occurred Access denied". I don't understand why this is happening since I have the DeploymentShare shared out using the default when the installation created the share "Everyone/Full control" share permissions and the NTFS permissions are "Users, Read, Execute, List, and Special Perm's Create files and folders". The account that I used initially to connect to the share worked just fine as it downloaded all the files to the "refresh" machine without any issues. I even tried creating a local user on the MDT 2010 server and using that account and still no luck.

So if the account that you intially tell MDT 2010 to use to connect to the network shares is ok and working fine, what account is it using to complete this process when it boots into the Windows 7 installation?

Any help would be greatly appreciated as this is driving me nuts!

Thanks in advance to your suggestions and responses.

Hi!

We want to make use of the upgrade scenario to deploy Windows 10 on our Windows 8.1 clients. I downloaded the official Windows 10 media from Volume licensing center and imported it correctly into MDT.

When we try to start the upgrade, it fails with following in the BCD.log

4699421/09/2015 13:42:18LTIApplySetup failed to upgrade OS from  \\<our MDT server>\DeploymentShare$\Operating Systems\Windows 10 Enterprise x64\setup.exe, rc = -1047526908
4699721/09/2015 13:42:19LTIApplyZTI ERROR - Non-zero return code by LTIApply, rc = -1047526908  0xC1900204

So I've tried to start the ISO manually, wich gives a bit more explanation when we have to choose wich kind of upgrade we want:

"you can't keep windows settings, personal files, and apps because you've chosen to install windows 10using a different language than you're currently using."

That explains a lot. We are using Windows 8.1 client machines with the native en-US language, but have chosen to make nl-NL the default language for our users.

When I run "DISM /online /get-intl" we see clearly: Default system UI language : nl-NL.

When I change this to en-US the upgrade will succeed without a problem. But if we want to change it, we need to restart the machine and boot in a pre Windows environment. If we need to do that on every machine in our company the upgrade will take a lot longer than it should be.

I also tried to import the language pack into the ISO without success :-s

Anyone has an idea? Or a solution to bring the default system UI language to en-US? (like gpo?)

As a newbie to MDT, I am trying to craft a better deployment solution than the Acronis Snap Deploy we currently have. I'm using MDT 2013 U1 and sticking only with USB media until the bugs are ironed out, with the goal of using WDS and possibly SCCM in the future. The machines being deployed to are Lenovo ThinkCentre M79 desktops with the official Lenovo drivers download in .CAB files (with AMD A8 CPUs/APUs).

I've tried to save time by initially relying on MDT to intelligently inject the correct drivers and Windows Updates during the image deployment; the Update packages and OOB drivers have been added to the deployment share. The deployment succeeds but neither the updates nor the drivers ever successfully inject into the image.

Next, I moved to manually injecting the Updates into the image using DISM, using the WSUS Offline 10.0.2 tool to grab all relevant updates for Windows 7 x64 SP1. There's also a local WSUS server that I have used in lieu of using DISM image injection, but the results are the same: the updates inject fine, however the deployment continually fails with error 0x80073713 right at the tail end of the WinPE device setup (after the partitioning, imaging and first reboot), withSetup Applying System Settings appearing on-screen.

I've tinkered with multiple settings in the task sequence to no avail, from removing all Inject Driver references from Preinstall and Postinstall phases, to recreating the boot images on the Share without any Lenovo drivers being injected, to crafting the OOB driver folder structure so I can refer to it with %make%\%model% variables in the customsettings.ini file (the subject of a different post entirely). UEFI and legacy BIOS USB boot options don't matter and different (new) USB drives don't make a difference. The machine is placed in a boot loop and never cleanly exists the deployment process.

Below are snippets of the error logs from the most recent failed deployment. There are many references to .Net 4.0 missing, even though it was present in the WinPE boot image at the time. Are they in reference to .NET 4 updates that are killing it?:

Setupact.log:

2015-09-15 15:12:57, Info                  CSI    00000625 Begin executing advanced installer phase 40 (0x00000028) index 345 (0x0000000000000159) (sequence 386)
    Old component: [l:0]""
    New component: [ml:326{163},l:324{162}]"Microsoft-Windows-OpticalMediaDisc-API, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2015-09-15 15:12:57, Info                  CSI    00000626@2015/9/15:22:12:57.321 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-OpticalMediaDisc-API, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;7128
2015-09-15 15:12:57, Info                  CSI    00000627 End executing advanced installer (sequence 386)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    00000628 Begin executing advanced installer phase 40 (0x00000028) index 346 (0x000000000000015a) (sequence 387)
    Old component: [l:0]""
    New component: [ml:330{165},l:328{164}]"Microsoft-Windows-SnippingTool-Licensing, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2015-09-15 15:12:57, Info                  CSI    00000629@2015/9/15:22:12:57.321 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-SnippingTool-Licensing, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;5420
2015-09-15 15:12:57, Info                  CSI    0000062a End executing advanced installer (sequence 387)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    0000062b Begin executing advanced installer phase 40 (0x00000028) index 347 (0x000000000000015b) (sequence 388)
    Old component: [ml:258{129},l:256{128}]"System.EnterpriseServices, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64"
    New component: [ml:258{129},l:256{128}]"System.EnterpriseServices, Culture=neutral, Version=6.1.7601.18523, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64"
    Install mode: install
    Installer ID: {d4486727-4d36-45a5-bc81-b8935aed1429}
    Installer name: [4]"NGEN"
2015-09-15 15:12:57, Info                  CSI    0000062c@2015/9/15:22:12:57.321 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{d4486727-4d36-45a5-bc81-b8935aed1429};System.EnterpriseServices, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral;0
2015-09-15 15:12:57, Info                  CSI    0000062d End executing advanced installer (sequence 388)
    Completion status: S_OK

2015-09-15 15:12:57, Info                  CSI    0000062e Begin executing advanced installer phase 40 (0x00000028) index 348 (0x000000000000015c) (sequence 389)
    Old component: [l:0]""
    New component: [ml:304{152},l:302{151}]"Networking-MPSSVC-Rules-MCX, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {68ce8d69-26ae-4f9f-bea7-50613e7ab5c1}
    Installer name: [13]"Firewall Rule"
2015-09-15 15:12:57, Info                  CSI    0000062f Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:f00e16ad03f0d0015a01000070037403} pathid: {l:16 b:f00e16ad03f0d0015b01000070037403} path: [l:212{106}]"\SystemRoot\WinSxS\amd64_networking-mpssvc-rules-mcx_31bf3856ad364e35_6.1.7600.16385_none_c359475274391a04" pid: 370 starttime: 130868285622752746 (0x01d0f0032ce895ea)
2015-09-15 15:12:57, Info                  CSI    00000630@2015/9/15:22:12:57.477 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{68ce8d69-26ae-4f9f-bea7-50613e7ab5c1};Networking-MPSSVC-Rules-MCX, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;152836
2015-09-15 15:12:57, Info                  CSI    00000631 End executing advanced installer (sequence 389)
    Completion status: S_OK

2015-09-15 15:12:57, Info                  CSI    00000632 Begin executing advanced installer phase 40 (0x00000028) index 349 (0x000000000000015d) (sequence 390)
    Old component: [l:0]""
    New component: [ml:318{159},l:316{158}]"Microsoft-Windows-SideShow-License, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2015-09-15 15:12:57, Info                  CSI    00000633@2015/9/15:22:12:57.477 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-SideShow-License, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;5641
2015-09-15 15:12:57, Info                  CSI    00000634 End executing advanced installer (sequence 390)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    00000635 Begin executing advanced installer phase 40 (0x00000028) index 350 (0x000000000000015e) (sequence 391)
    Old component: [l:0]""
    New component: [ml:360{180},l:358{179}]"Microsoft-Windows-TabletPC-CoreInkRecognition-Licensing, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2015-09-15 15:12:57, Info                  CSI    00000636@2015/9/15:22:12:57.493 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-TabletPC-CoreInkRecognition-Licensing, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;5548
2015-09-15 15:12:57, Info                  CSI    00000637 End executing advanced installer (sequence 391)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    00000638 Begin executing advanced installer phase 40 (0x00000028) index 351 (0x000000000000015f) (sequence 392)
    Old component: [l:0]""
    New component: [ml:352{176},l:350{175}]"Microsoft-Windows-TabletPC-MathRecognizer-Licensing, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: [12]"SppInstaller"
2015-09-15 15:12:57, Info                  CSI    00000639@2015/9/15:22:12:57.493 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-TabletPC-MathRecognizer-Licensing, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;5394
2015-09-15 15:12:57, Info                  CSI    0000063a End executing advanced installer (sequence 392)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    0000063b Begin executing advanced installer phase 46 (0x0000002e) index 352 (0x0000000000000160) (sequence 399)
    Old component: [l:0]""
    New component: [ml:360{180},l:358{179}]"microsoft-windows-RemoteFX-UMTS-files-regkeys-component, Culture=neutral, Version=7.1.7601.18880, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
    Installer name: [15]"Generic Command"
2015-09-15 15:12:57, Info                  CSI    0000063c Calling generic command executable (sequence 121 (0x00000079)): [32]"C:\windows\System32\rundll32.exe"
    CmdLine: [209]""C:\windows\System32\rundll32.exe" C:\windows\WinSxS\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_7.1.7601.18880_none_7ed4eaa6a991cef2\RdpGroupPolicyExtension.dll,ExecuteProcessGroupPolicyEx"
2015-09-15 15:12:57, Info                  CSI    0000063d Done with generic command 121 (0x00000079); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:0 ]
2015-09-15 15:12:57, Info                  CSI    0000063e@2015/9/15:22:12:57.540 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};microsoft-windows-RemoteFX-UMTS-files-regkeys-component, Version = 7.1.7601.18880, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;43727
2015-09-15 15:12:57, Info                  CSI    0000063f End executing advanced installer (sequence 399)
    Completion status: S_OK

2015-09-15 15:12:57, Info                  CSI    00000640 Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
    Old component: [l:0]""
    New component: [l:0]""
    Install mode: uninstall
    Installer ID: {51d813ef-83f1-42de-a2ee-89ee4633a7c9}
    Installer name: [25]"RegistryKey SD Applicator"
2015-09-15 15:12:57, Info                  CSI    00000641 End executing advanced installer (sequence 0)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    00000642 Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
    Old component: [l:0]""
    New component: [l:0]""
    Install mode: install
    Installer ID: {51d813ef-83f1-42de-a2ee-89ee4633a7c9}
    Installer name: [25]"RegistryKey SD Applicator"
2015-09-15 15:12:57, Info                  CSI    00000643 End executing advanced installer (sequence 0)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:12:57, Info                  CSI    00000644 Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
    Old component: [l:0]""
    New component: [l:0]""
    Install mode: delta
    Installer ID: {d4486727-4d36-45a5-bc81-b8935aed1429}
    Installer name: [20]"Ngen Service Tickler"
2015-09-15 15:12:57, Info                  CSI    00000645 End executing advanced installer (sequence 0)
    Completion status: S_OK , !! Requested a reboot

2015-09-15 15:13:06, Error                 CSI    00000646@2015/9/15:22:13:06.790 (F) d:\w7rtm\base\wcp\componentstore\com\advancedinstallerstore.cpp(487): Error HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) originated in function Windows::COM::CComponentStore::IAdvancedInstallerAwareStore_ResolvePendingTransactions expression: HRESULT_FROM_WIN32(14099L)
[gle=0x80004005]
2015-09-15 15:13:06, Info                  CBS    Failed to add C:\windows\Logs\CBS\CBS.log to WER report because it is missing.  Continuing without it...
2015-09-15 15:13:07, Error                 CSI    00000647 (F) HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) #130# from Windows::COM::CComponentStore_IAdvancedInstallerAwareStore::ResolvePendingTransactions(dwFlags = (DontFailIfPrimitivesPending|IndicatePrimitiveRollback), Progress = NULL, Phase = 0, Disposition = (unknown enumerant 0)[3]" | "0)[gle=0x80073713]
2015-09-15 15:13:07, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2015-09-15 15:13:07, Info                  CBS    Clearing HangDetect value
2015-09-15 15:13:07, Info                  CBS    Saved last global progress. Current: 161, Limit: 161, ExecuteState: CbsExecuteStateResolvePending
2015-09-15 15:13:07, Info                  CBS    Startup: Processing complete. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2015-09-15 15:13:07, Info                  CBS    Restored system sleep block state: 0x80000003
2015-09-15 15:13:07, Info                  CBS    Enabling LKG boot option
2015-09-15 15:13:07, Error      [0x030149] CMI    Callback_CBS_Do_OnlineInstall:Calling startup processing failed 0x80073713
2015-09-15 15:13:07, Info                  CMI    CBS_Core_Finalize:Calling cbs core finalize
2015-09-15 15:13:07, Info                  CMI    CBS_Core_Finalize:Calling cbs core finalize complete
2015-09-15 15:13:07, Error      [0x030153] CMI    Callback_CMI_ConfigInstall: CBS startup processing re-run failed.
2015-09-15 15:13:07, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.]

SetupErr.log

2015-09-15 15:12:52, Error                 CSI    000002f8 (F) Done with generic command 60 (0x0000003c); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 4294967295 (0xffffffff) resulted in success? FALSE
    Process output: [l:117 [117]"ERROR - .NET 4.0 is not installedERROR - CLRCreateInstance call failed, 0x80004001.

ERROR - Initialization failed.

"][gle=0x80004005]
2015-09-15 15:12:52, Error                 CSI    000002fb (F) Done with generic command 61 (0x0000003d); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 4294967295 (0xffffffff) resulted in success? FALSE
    Process output: [l:117 [117]"ERROR - .NET 4.0 is not installedERROR - CLRCreateInstance call failed, 0x80004001.

ERROR - Initialization failed.

"][gle=0x80004005]
2015-09-15 15:12:52, Error      [0x018007] CSI    000002fd (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2015-09-15 15:12:55, Error                 CSI    000004aa@2015/9/15:22:12:55.028 (F) d:\w7rtm\base\wcp\componentstore\com\genericcommands.cpp(522): Error HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND) originated in function CreateProcessAndWaitForCompletion expression: HRESULT_FROM_WIN32((*CreateProcessResult))
[gle=0x80004005]
2015-09-15 15:12:55, Error                 CSI    000004ab (F) Done with generic command 71 (0x00000047); CreateProcess returned 3, CPAW returned HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND)
    Process exit code 0 resulted in success? FALSE
    Process output: [l:0 ][gle=0x80004005]
2015-09-15 15:12:55, Error      [0x018007] CSI    000004ad (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2015-09-15 15:12:55, Error                 CSI    000004e7@2015/9/15:22:12:55.855 (F) d:\w7rtm\base\wcp\componentstore\com\genericcommands.cpp(522): Error HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND) originated in function CreateProcessAndWaitForCompletion expression: HRESULT_FROM_WIN32((*CreateProcessResult))
[gle=0x80004005]
2015-09-15 15:12:55, Error                 CSI    000004e8 (F) Done with generic command 72 (0x00000048); CreateProcess returned 3, CPAW returned HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND)
    Process exit code 0 resulted in success? FALSE
    Process output: [l:0 ][gle=0x80004005]
2015-09-15 15:12:55, Error                 CSI    000004eb@2015/9/15:22:12:55.902 (F) d:\w7rtm\base\wcp\componentstore\com\genericcommands.cpp(522): Error HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND) originated in function CreateProcessAndWaitForCompletion expression: HRESULT_FROM_WIN32((*CreateProcessResult))
[gle=0x80004005]
2015-09-15 15:12:55, Error                 CSI    000004ec (F) Done with generic command 73 (0x00000049); CreateProcess returned 3, CPAW returned HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND)
    Process exit code 0 resulted in success? FALSE
    Process output: [l:0 ][gle=0x80004005]

2015-09-15 15:12:57, Error      [0x018007] CSI    00000601 (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2015-09-15 15:13:06, Error                 CSI    00000646@2015/9/15:22:13:06.790 (F) d:\w7rtm\base\wcp\componentstore\com\advancedinstallerstore.cpp(487): Error HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) originated in function Windows::COM::CComponentStore::IAdvancedInstallerAwareStore_ResolvePendingTransactions expression: HRESULT_FROM_WIN32(14099L)
[gle=0x80004005]
2015-09-15 15:13:07, Error                 CSI    00000647 (F) HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) #130# from Windows::COM::CComponentStore_IAdvancedInstallerAwareStore::ResolvePendingTransactions(dwFlags = (DontFailIfPrimitivesPending|IndicatePrimitiveRollback), Progress = NULL, Phase = 0, Disposition = (unknown enumerant 0)[3]" | "0)[gle=0x80073713]
2015-09-15 15:13:07, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2015-09-15 15:13:07, Error      [0x030149] CMI    Callback_CBS_Do_OnlineInstall:Calling startup processing failed 0x80073713
2015-09-15 15:13:07, Error      [0x030153] CMI    Callback_CMI_ConfigInstall: CBS startup processing re-run failed.

There is obviously something fundamental that I am missing, perhaps with the update selection. Searches through these forums and others haven't found any instances that match my circumstances. Perhaps my task sequence is wrong or an update is killing the Advanced Installer? I am eager to learn and am open to any suggestions about how I can move forward.

Let me know if you would like additional details.

Thanks in advance!

Hi

Not sure if this is the right category, but looking for some help in coming up with the right solution.

Current Scenario

I regularly setup small closed temporary networks consisting of 1 server and up to 15 clients. We initially setup up a server and 1 client. The server (2008 R2) runs as a DC and SQL server and the clients run Windows XP and windows 7. This was then sent to the hardware suppliers from which we rent the hardware when required. They then image the clients and servers when required and wipe them on return. When onsite the first stage is to get the server up and running then network all the clients. We then need to join each client to the domain and take ownership of a shared folder on the client required for our proprietary software to function.

We would like to streamline this into as few steps as possible as not everyone we send on site is tech savy enough to deal with joining to domain and the issues that can arise with the process. we have played around with various scripts etc to try and streamline but these dont always work.

Perhaps some of the experts out there could help and guide us into what direction we should take.. Are there alternative deployment solutions we could use/ scripts for joining domains etc.

Thanks in advance.

Hi

Thanks in advance to anyone who can help.

I have built a brand new Server 2012 / MDT 2013 system.  I have not configured it.  When trying to Update Deployment Share for the first time I get the following error.

-------------------------------------------------

Value cannot be null.
Parameter name: s

-------------------------------------------------

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

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

Building requested boot image profile.

System.Management.Automation.CmdletInvocationException: Value cannot be null.
Parameter name: s ---> System.ArgumentNullException: Value cannot be null.
Parameter name: s
   at System.IO.StringReader..ctor(String s)
   at System.Xml.XmlDocument.LoadXml(String xml)
   at Microsoft.BDD.PSSnapIn.Utility.GetFoldersForSelectionProfile(MDTObject profile, Boolean enabledFoldersOnly)
   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.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

Hi,

I have 2 applications users can decide which one to install during deployment. These two apps are Office 2013 x86 and Office 2013 x64. Right now they can mistakenly choose both so I am wondering if it is possible to avoid that? Is it possible if they choose 32-bit version that 64-bit is automatically unticked and cannot be choose and vice versa?

Thanks,

Hello

I have setup my task sequence to include the Windows Update Post Application Install.

I have set my WsusServer in my customsettings.ini file to go to our internal WSUS server.

This works but it is very slow to install , it looks like it downloads fine at a speed i would expect but to install 50 updates took over 24hours.

I have google'd around and saw someone who said about a proxy etc, so i thought to give this task in the task sequence Run as rights. I entered my details which would have rights to run and now i get the error 

TI ERROR - Unhandled error returned by ZTIWindowsUpdate: Invalid root in registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer". (-2147024891  0x80070005)

If i remove the the run as rights the WSUS post application task works but is very slow as before.

So my question 

1. Why is this very slow to install?

2. Why i get the error when run as rights are entered in the Task Sequence?

Thanks

I need a little help regarding a capture issue in MDT 2013 SP1.  I've been using MDT since 2010 and never encountered this issue.  So here's the rundown.

New company, physical server ; 2012 R2, Installed MDT 2013 SP1 and setup a deployment task.  Works great.
Installed all windows updates etc and went to capture.  Created a Capture Task, updated deployment share, reboot device, network boot, MDT loads, choose capture task, select capture, use default capture path, enter Active Directory credentials, click next, process starts and after about 30 seconds to 1 minute, fails with the following information (tried to add pic but account not verified).  I've done some research, tried some different things, but no dice.  Can anyone lend a hand?

ZTI-ERROR - Unhandled error returned by LTISysprep:  The system cannot find the file specified.
(-2147024894 0x80070002)
Litetouch deployment failed, Return Code = -2147467259 0x80004005

Hello,

I created and captured a Windows 10 Reference Build. During my build process I removed some of the Windows 10 built in Apps using a PS command. I made some changes to the profile. When I bring down the image I am seeing the profile changes are there but the built in Apps are back! I was unable to find a place in the unattended file to remove these apps. So does that mean I need to remove these apps each time I build new computer or do I need to do it a different way?<o:p></o:p>

Thanks

I am trying to load a MDT 2013 Windows 10 Enterprise Image onto Virtualbox, however it fails while applying unattend.xml. The two error messages are:

Failure (5627) 8: Run DISM.exe

Litetouch deployment failed. Return Code = -2147467259 0x800040005

This build works fine on physical hardware. Same error occurs when using VMWare Desktop 10. Any ideas on how to get this build to apply to a VDI?

Hi All,

I'm hoping someone can help with this issue, I will provide a little background before introducing the problem to try and make my situation as clear as possible.

Background

- I have recently upgraded MDT from 2010 to 2013 and integrated Windows Assessment and Deployment Kit for Windows 8.1

- My task sequences are split into two folders (x86 and x64), both of these folders contain a deployment image for our commonly purchased PCs. They have been created using a sysprep and capture which was working swimmingly.

- The first time I imaged two new 64x PCs since the upgrade, MDT went through the installation OK (it took all day which is unusual but it did complete), the speed of installation was going to be my next issue however I was faced with a bigger one.

Problem

We have received two new 64x PCs which I am trying to image, however the deployment wizard errors and cancels at the stage of 'Installing Operating System', with the following error:

Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Incorrect function. (Error: 00000001; Source Windows)
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.
Incorrect function. (Error: 00000001: Source Windows)
Task Sequence Engine Failed! Code: enExecutionFail
Task Sequence execution failed with error code 80004005
Error task sequence manager failed to execute task sequence. Code 0x80004005

This seemed strange as I haven't touched anything since the last successful image. I've been researching the following error and the first thing that I initially tried was to Completely Regenerate the Boot Images when updating the deployment share. Since then I can no longer PXE boot to the 64x WDS, instead it eventually brings up command prompt with X:\windows\system32 that sits on top of the Microsoft Solution Accelorator background, nothing else happens at this point. If I boot to the 32x WDS if does load the deployment wizard where I can actually see the 64 bit task sequence, if however I try to run this I'm prompted with that exact same error above.

The second thing I tried was disabling 'Injecting the drivers' as I thought that the network driver may have been causing a problem and disconnecting me from the deployment share, this however didn't work either.

I'm totally baffled now to be honest and would appreciate anyone helping me out?

Many thanks in advance,

Ad

Brian Hoyt

Hello

I the above possible?

We have our task sequence to bind to active directory, but i can see this binds way before all other install applications task start.

What is the task in the task sequence to move this to the end, if possible ?

Thanks

Trying to boot a new lenovo x1 carbon pc but I get this error:

1. When I read this on google it said I need to update my PE?

2. How can I see what version of PE I have?

3.Will I lose all my drivers if I update my PE?

I updated my MDT to 2013 update 1 and WAIK 10 to be able to deploy windows 10.My workaround for this error is to disable secure boot, and change UEFI mode to Legacy only then I can pxe boot.

4.Do you know any other solution?

My other questions are:

5. Do you know what ROW I can't write in customsettings.ini to create a local account that is not admin and assign it lets say a name and a password? Can the password be random and saved somewhere like ad or a text document? Sometimes people don't have a network when they receive our their new pcs and this could be a solution, to logon to a local account and the remote it.

6. Can I choose to hide a task sequence that will deploy windows 10 but still choose it somehow? I want to test deploy windows 10 without other users being able to choose that task sequence?

7. Is it also possibly to change the pxe language to Swedish keyboard instead of English?

Thank you guys and girl!

Hi. 

I am trying to move a computer to a Staging OU using Maik Koster's webservice

(http://maikkoster.com/moving-computers-in-active-directory-during-mdt-deployments-step-by-step/)

The webservice is running and responding when i navigate to http://MyWebServer/MyWebserviceFolder/mdt.asmx

I added a TS step that calls the script "cscript.exe "%SCRIPTROOT%\Z_MoveComputer_StagingOU.wsf""

but when the step is executed I get the following error:

ZTI ERROR - Unhandled Error Returned by Z_MoveComputer_StagningOU: The Data necesarry to

complete this operation is not yet available.

(-2147483638 0x8000000A)

Litetouch Deployment failed return code = -2147467259 0x80004005

Anybody know's how to get this working? 

Hi,

I followed this article in order to create TS to upgrade OS to Windows 10 with MDT:

https://technet.microsoft.com/en-us/library/mt426643(v=vs.85).aspx

Environment:

OS: Windows 8.1

PC: VM (Hyper-V)

However, when I run Litetouch.vbs deployment starts (Running action: Upgrade Windows) but after few minutes also stops without any error. In logs I can see this:

I manually ran Windows 10 setup.exe from Operating System folder in Deployment Share and OS was installed properly. 

Kind Regards,

I created a new task sequence for a Windows 10 deployment and it stops at the login screen every time.  My Windows 7 tasks work as expected when deployed. In order to complete the deployment for my Windows 10 image,  I need to login as the local admin and the deployment continues from there and finishes without error.   The laptop has already joined my domain at this point in the deployment process, if that means anything. I am sure I am missing something simple for this task but I have yet to find it.  Any help would be appreciated.

Thank you!

Craig

Anyone have a link to download the original MDT 2013 x64 installer (not Update 1)?  The link on Microsoft's site is broken and I haven't had much luck googling it.  Thanks.

Hello,

I'm attempting to automate the Win 10 upgrade process on a lab PC. The PC has been built from a Win 7 Pro x64 image (domain joined, but not activated), and then I have attempted to run the LiteTouch.vbs script from the deployment share scripts folder to update this to Win 10.

The deployment fails silently, but the BDD log reports (last part):

<![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[Property SourcePath is now = \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI upgrade OS using  \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\W10-UPG-TEST\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\W10-UPG-TEST\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Upgrading from \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe using command: "\\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /DynamicUpdate Disable /ImageIndex 1]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /DynamicUpdate Disable /ImageIndex 1]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 3852)]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 3852)]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = -2147024809]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Setup failed to upgrade OS from  \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe, rc = -2147024809]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Requesting reboot for setup.exe to complete Upgrade action]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI ERROR - Non-zero return code by LTIApply, rc = -2147024809  0x80070057]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

The LTIapply log is as follows:

![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1.W10\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[TargetOS is the current SystemDrive]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Open Control File: OperatingSystems]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[------  Upgrading Windows  ------]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Verify we have necessary files locally, if not, copy it]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI upgrade OS using  \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64]LOG]!><time="13:01:53.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\W10-UPG-TEST\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\W10-UPG-TEST\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Upgrading from \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe using command: "\\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /DynamicUpdate Disable /ImageIndex 1]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /DynamicUpdate Disable /ImageIndex 1]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 3852)]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 3852)]LOG]!><time="13:01:54.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = -2147024809]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Setup failed to upgrade OS from  \\ALPHA\DeploymentShare$\Operating Systems\Windows 10 Pro x64\setup.exe, rc = -2147024809]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Requesting reboot for setup.exe to complete Upgrade action]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI ERROR - Non-zero return code by LTIApply, rc = -2147024809  0x80070057]LOG]!><time="13:03:48.000+000" date="09-23-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">

Is there anywhere that gives a list of the LTIApply return codes and their meaning? This seems to be the only indication that gives any useful information.