Hello all,

We recently had a server crap out and along with it all of our deployment info for a small off domain internet cafe of about 20 computers.  Previous admins did not save any of the info so I'm having to start over with MDT 2013.  I have MDT 2013 installed and have imported Win10 Pro x64.  I was able to create a task sequence and deployed it to a VM using VMware player.  I have customized the image and am trying to capture a custom image.  I have created new sysprep and capture task sequences but when I go into the deployment share and run the litetouch.vbs it does not pull up my new task sequences I have created.  I dont have it on a domain and plan on creating a bootable USB for the image.  I've deleted the C:\MININT folder and even tried created a new deployment share with new task sequences but i always get the same three from when I deployed the image.  I'm lost at this point.

Also, I'm new to setting up MDT and capturing an image so apologies if it is something obvious.  Thanks in advance!

I'm trying to build my Windows 7 Enterprise x64 Reference image with MDT. Windows Update keeps failing and I don't know why. I have attached the logfiles from Windows Update and MDT.

https://app.box.com/s/nsrxos3e2c0xrjg5j3rky6fnsle8vk8j

I've been using MDT for a while to deploy various OS by usb media.  Recently, I started getting this working on UEFI - one wim was > 4GB so enabled split wim & that's been working fine.

However, I found that when running a TS (using a differnet wim which isn't split and is <4GB in size) it fails during deployment, digging in the logs showed that it was looking for a .swm file.  So, I figure that turning splitwim on is a single hit - it affects all wims on that deployment.

I then realised I was on Update 1, so yesterday updated to Update 2. 

Since then I've been unable to update my media.

This fails with:

Starting MDT Media Update
Opened the media deployment share.

System.Management.Automation.CmdletInvocationException: Cannot create a file when that file already exists.
 ---> System.IO.IOException: Cannot create a file when that file already exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at Microsoft.BDD.PSSnapIn.GenerateMDTMedia.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()

Going with the "cannot when already exists", I've cleared out the temp folder, the contents of the destination offline media folders and so on, but it still happens.  I've check dism.log - this is splitting the wim fine, and it copies the split wim into the destination fine.  Checking with procmon suggests that it was scanning the drivers folder, so I've stripped all of them out, stripped out the applications folder too (and the packages). 

Still happening.  Tried via PS, same issues (obviously), with the following errors:

VERBOSE: Starting MDT Media Update
VERBOSE: Opened the media deployment share.
Update-MDTMedia : Cannot create a file when that file already exists.
At C:\Users\ashg\AppData\Local\Temp\GenerateMedia.ps1:3 char:1
+ Update-MDTMedia -path "DS001:\Media\MEDIA001" -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Update-MDTMedia], IOException
    + FullyQualifiedErrorId : System.IO.IOException,Microsoft.BDD.PSSnapIn.Gen
   erateMDTMedia

I can't see where I can get any more logging out of the cmdlet - it's already running with verbose & am going round and round in circles now.  I'm on the latest ADK too.

I've run the deployment workbench with /debug, and it's spitting back

12:57:36 : splitWimPath after Trimming: C:\MDTDeploymentShare\Operating Systems\2012R2_nov15\2012R2_nov15.swm

13:03:38 : Saved temp path for wim to be copied finally: C:\Users\ashg\AppData\Local\Temp\b90d68e3-a5e8-41dc-b20c-7298b887c40b

:38 : temp path for wim to be copied : C:\Users\ashg\AppData\Local\Temp\b90d68e3-a5e8-41dc-b20c-7298b887c40b\2012R2_nov15.wim

:38 : temp path for wim to be copied : C:\Users\ashg\AppData\Local\Temp\b90d68e3-a5e8-41dc-b20c-7298b887c40b\2012R2_nov15.wim

:38 : temp path for wim to be copied : C:\Users\ashg\AppData\Local\Temp\b90d68e3-a5e8-41dc-b20c-7298b887c40b\2012R2_nov15.wim

--> System.IO.IOException: Cannot create a file when that file already exists.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

 System.IO.File.Move(String sourceFileName, S

So by the looks of it, it's realised that it needs to split the wim, it copies the wim to my %temp%, splits the original, and then tries to move it back, but cannot.

I have already tried just dropping the .swm files into the deployment workbench, but it then refuses to build the offline media at all.

Argh! Any clues anyone, or is this a bug?

I just got a 64gb USB stick and my intention was to use it as a liteTouch installer for older hardware (basically it had the exact same image, but the out of box driver includes all drivers in my deployment share so it could be used if we needed to re-image older computers).

I created the media, then moved the files to the USB and it booted but I immediately got to the screen asking me for the path to my deployment share. I took the stick and re-fromatted it (identically to the other sticks I use) then transferred the files from my standard media and got the same error. 

The weird thing is when I back out of the litetouch install and go back to the initial screen where I have the option of launching a cmd shell, I can launch that cmd shell navigate the the USB stick find and all deployment files are visible. That makes me think it's not WinPE USB driver issue since the full contents of the USB stick can be seen in other areas (eg. cmd shell, diskpart) and are only invisible to the litetouch install process itself.

Hi everyone, 

"First time Caller, long time listener" as it were.   I am encountering a rather odd issue with MDT 2013 update 2.  Upon domain join, regardless if it's a powershell script that I previously used, or the task sequence to recover to the domain, it breaks the autologon.  I have confirmed this, because I moved the domain join to become the very last step just before the post-apply cleanup, and moved both of those to be the last two steps in the task sequence and I encounter no issues.  

I created a new task sequence from scratch, so I have the necessary reg keys being added to ensure that MDT can do it's thing.   I also captured the image using MDT, so I don't believe my issue is with that either.  So, does anyone have any ideas on what could be happening?  Please note, this behavior does not occur with my Windows 7 images and task sequences, so I am loathe to believe that this is some GPO at work directly, but could be some behavior related to Windows 10, that I am not aware of....   Suggestions or advice would be greatly appreciated!  

Thanks, 

Allyn

I want to build an OS reference machine, and have the installation boot straight into audit mode.

I have found hundreds, if not thousands, of articles, posts, and tutorials on setting the Microsoft-Windows-Deployment | Reseal | Audit mode in the unattend.xml file, but alas, this setting is available in 3 different configuration passes, and not a single post indicates which pass this is to be configured under.

Would somebody be kind enough to clarify this for me? It really pisses me off that so many people will tell you what to do, but won't give enough information to be actually able to do it.

Thanks.

MDT 2013 Update 2 Version 6.3.8330.1000 running on Windows Server 2008 R2 Standard

Due to forthcoming network changes we need to decomission our build lab on a 192.168.240.0/25 subnet.

Our previous working setup was:
WDS Server on 192.168.240.5 which was configured on DHCP option 66.
All clients were on the 192.168.240.0/25 dhcp scope.

Our MDT 2013 Server Deployment Share is on 10.99.1.150 (example).

This has worked fine for years.

Due to the network change we had to utilise WDS on the MDT Server 10.99.1.150 (a VM on vmware esx host) and move our clients on build bench onto a 10.99.20.0/25 dhcp subnet.

The first issue was being unable to get a pxe response, we added 10.99.1.150 to the IP helper on the switch and we can now pxe boot.

Although not configured in DHCP option 67 it automatically uses boot\x64\wdsnbp.com which brings you to the PXE menu, however once you load the boot option from PXE menu it just hangs on the splash screen (black background and blue Windows 2012 style Windows image).

I have booted an older Windows PE image we use for configuring HP Scripting Toolkit which works fine.

However no matter what I try with the Litetouch X64 or Generic x64 I cannot get past that splash screen.
I have tried setting DHCP option 67 to use Boot\x64\pxeboot.com which gives me a blue BCD error as soon as I select the option from PXE Menu.
I have even tried using the driver selection of none and I still can't get past the splash screen.

The Windows PE Image I can boot is 234mb and OS Version 6.3.9600
The Windows PE Images I cannot boot are 400mb+ and OS version 10.0.10586

Could this issue be due to the PXE and clients being on different subnets/VLANS?
Could it be size of the Windows PE Boot Images?

Short of building an old MDT share that I really don't want to do, I cannot see what step to take next.

Any help would be appreciated!

Hi,

My smsts.log files are full of errors containing: (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566)

The task sequences complete without errors and any apparent problems, but the logs are loaded with these and do not point to any descriptive error. What are they stemming from. Snippet from smsts.log

==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Command line: "C:\MININT\Tools\X64\TsmBootstrap.exe"  /env:SAStart TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Succeeded loading resource DLL 'C:\MININT\Tools\X64\00000409\TSRES.DLL' TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Succeeded loading resource DLL 'C:\MININT\Tools\X64\TSRESNLC.DLL' TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Running Task Sequence in standalone. TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Loading the Environment Variables from "C:\MININT\Tools\X64\variables.dat". TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Loading task sequence file TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Loading _SMSTSTaskSequence from C:\MININT\Tools\X64\TS.XML TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
User specified local data drive C: TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
C:\_SMSTaskSequence does not exist TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Creating directory C:\_SMSTaskSequence TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Updated security on object C:\_SMSTaskSequence. TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Updating the local data path in the Task Sequencing Environment. TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Found network adapter "Intel(R) PRO/1000 MT Network Connection" with IP Address 192.168.11.132. TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Command line for extension .exe is "%1" %* TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Set command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Register TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Executing command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Register TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
==========[ TsProgressUI started in process 3844 ]========== TsProgressUI 6/6/2016 3:19:55 PM 3620 (0x0E24)
Command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Register TsProgressUI 6/6/2016 3:19:55 PM 3620 (0x0E24)
Registering COM classes TsProgressUI 6/6/2016 3:19:55 PM 3620 (0x0E24)
sbModulePath = C:\MININT\Tools\X64\TsProgressUI.exe TsProgressUI 6/6/2016 3:19:55 PM 3620 (0x0E24)
Unregistering class objects TsProgressUI 6/6/2016 3:19:55 PM 3620 (0x0E24)
Shutdown complete. TsProgressUI 6/6/2016 3:19:55 PM 3620 (0x0E24)
Process completed with exit code 0 TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Successfully registered TS Progress UI. TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Starting Task Sequence Manager. TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
executing TS Manager not in full media TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
executing TS Manager in c:\minint\tools\x64 TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Command line for extension .exe is "%1" %* TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Set command line: "TsManager.exe" /standalone TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
Executing command line: "TsManager.exe" /standalone TSMBootstrap 6/6/2016 3:19:55 PM 4068 (0x0FE4)
LOGGING: Finalize process ID set to 3836 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Successfully intialized Logging for TS Manager. TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Commandline: "TsManager.exe" /standalone TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
/service parameter found at index: -1 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
/standalone parameter found at index: 16 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
************************************************** TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
TSManager executing in non SMS, standalone mode TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
/noclient parameter found at index: -1 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Successfully registered Task Sequencing COM Interface. TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Executing as a standalone exe TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Initializing TS Environment TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Opening Task Sequencing Environment TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Env variable _SMSTSProtectedPaths set to %OSDStateStorePath%;%_SMSTSClientCache%;%_SMSTSNewClientCachePathToCleanup% TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
!sVolumeID.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,244) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,244) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,244) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,244) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
NOT executing in WinPE TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
_SMSTSReturnToGINA variable set to false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
No SMS client installed or in standalone mode. Skipping remediation check. TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Initializing TS Engine TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Getting TaskSequenceXML from environment TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Parsing task sequence . . . TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Loaded TS from string TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Parsing task sequence to get schema version TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Task sequence version 3.00 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Task sequence schema version is 3.00 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Current supported schema version is 3.10 and 3.00 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Processing get action table request TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Got root node now getting list of all child elements TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
There are 2 first level steps or groups TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Processing group TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Parsing group node: Capture Image TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Description:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
ContinueOnError: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Disable: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
A condition is associated with the step found TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Found and operator. TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
There are 0 operands TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Adding begin group instruction at 0 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
There are 7 first level steps or groups TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Parsing step node: Set Image Build TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Description:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
ContinueOnError: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
SuccessCodeList: 0 3010 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
No condition is associated with the step. TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Disable: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Start in dir:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Run in attribute:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Timeout:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
DefaultVarlist found TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Variable name: VariableName TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Variable name: VariableValue TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Action command line: cscript.exe "%SCRIPTROOT%\ZTISetVariable.wsf" TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Adding instruction at 1 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Parsing step node: Set ImageFlags TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Description:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
ContinueOnError: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
SuccessCodeList: 0 3010 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
No condition is associated with the step. TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Disable: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Start in dir:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Run in attribute:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Timeout:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
DefaultVarlist found TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Variable name: VariableName TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Variable name: VariableValue TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Action command line: cscript.exe "%SCRIPTROOT%\ZTISetVariable.wsf" TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Adding instruction at 2 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Parsing step node: Set Phase TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
Description:  TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
ContinueOnError: false TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
SuccessCodeList: 0 3010 TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566) TSManager 6/6/2016 3:19:55 PM 3840 (0x0F00)

Any ideas on this would be great. Even if these messages are just informative.

Thanks

Jason

Hi

How i can rename the task sequence progress bar name.Let me know if we can add company logo as well.

Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

I am doing a build and capture of Windows 10 using MDT 2013u2.

Windows 10 clients both during the build process and after being deployed are asking "Do you want to allow your PC to be discoverable?"  I thought this question was controlled by the NetworkLocation setting in OOBE Unattend.xml.  That value is set to "Work" - but I am still being asked the question about discoverability.  When I deploy the OS using a Task Sequence, I also get this question.  This is not the kind of question my users know how to answer. 

Is there a way to set this value in unattend.xml?  Has networklocation been depreciated?

Hi,

I'm in the middle of an MDT Reference Image capture (added a pause in the tasks list).

I'm using the following xml file :

<gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend"><gs:UserList><gs:User UserID="Current" CopySettingsToDefaultUserAcct="true" CopySettingsToSystemAcct="true"/></gs:UserList><!--System Locale (Non-Unicode support) --><gs:SystemLocale Name="fr-CA" /><!--User Locale--><gs:UserLocale><gs:Locale Name="fr-CA" SetAsCurrent="true"/></gs:UserLocale><!--location--><gs:LocationPreferences><!--Canada--><gs:GeoID Value="39"/></gs:LocationPreferences><!-- Keyboard --><gs:InputPreferences><gs:InputLanguageID Action="add" ID="0c0c:00001009" Default="true"/><gs:InputLanguageID Action="remove" ID="0c0c:00011009"/><gs:InputLanguageID Action="remove" ID="040c:0000040c"/><gs:InputLanguageID Action="remove" ID="0409:00000409"/><gs:InputLanguageID Action="remove" ID="1009:00000409"/><gs:InputLanguageID Action="remove" ID="1009:00001009"/></gs:InputPreferences></gs:GlobalizationServices>

If I comment out the following line, the keyboards are removed and I'm left with only one (the default one). This would be the expected behavior, but of course my non-unicode default locale would not be fr-CA.

<gs:SystemLocale Name="fr-CA" />

But if this line is not commented out, the keyboards are not removed.

Why would that be ?

Regards,

-homerggg

I know this has been asked plenty of times before but I can't find a solution for my particular case. I am setting up a VM that will be used as a sort of "golden image" that we recapture whenever we update it. When I remote to \\SERVERNAME\deploymentshare$\scripts and try to run LiteTouch.vbs I see the Processing Bootstrap Settings window, then a while after it closes get the error in the title. I can't imagine it being a driver issue, as the VM connects to everything perfectly fine with it's network driver, and that driver is copied on the MDT server.

I've already tried adding "wscript.sleep 2500" to the LiteTouch.wsf to see if the machine was simply too fast, but it didn't help. Any ideas?

Created Win10x64 enterprise reference image and saved to .wim file.  Using bare minimum Task Sequence (i.e. not installling any software or running any scripts etc).  When trying to deploy said .wim file to new machine, the deployment succesfully installs(?).  HOWEVER, after the machine reboots, it gets stuck on 'Getting Ready....'.  Checked bdd.log file and no glaring failures or issues.  Did the shift-f10 thing, and updated registry for Child completion.  No change.  Unit now gets stuck a 'Finalizing your settings'.

Any help would be appreciated....

I went ahead and updated my MDT 2013 Update 1 to Update 2. I had issues upgrading the deploymentshare(s) themselves, but I was able to get through it; however now I am unable to create a new boot file from the deploymentshare itself.

below is the error that I get!

I am creating a test task sequence. Any help is appreciated.

Error while importing Microsoft Deployment Toolkit Task Sequence.

System.FormatException: Input string was not in a correct format.

  at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)

  at System.Version.TryParseComponent(String component, String componentName, VersionResult& result, Int32& parsedComponent)

  at System.Version.TryParseVersion(String version, VersionResult& result)

  at System.Version.Parse(String input)

  at System.Version..ctor(String version)

  at Microsoft.BDD.Core.Utility.GetVersion(String strVersion)

Environment: SCCM 2012 R2 SP1 CU1

Console version 5.0.8239.1206

Site version 5.00.8239.1000

MDT2013 Update1

WADK for Windows 10

Hi guys,

Others already reported this bug for Update 1 but it still exists in Update 2. The "Start in" field of a "Run Command Line" step of a Task Sequence is not processed by the XML parser (the "Start in dir:" entry is missing from the smsts.log) and therefore the computer deployments stop with error because the command of these "Run Command Line" steps cannot be executed. Fortunately since these commands usually launch a batch file therefore work-arounds can be easily applied. This bug didn't exist in the base release of MDT 2013.

We have multiple MDT servers spread across many sites around europe.

We create all MDT deployment task sequences etc at a central site in the UK, then push them out to the multiple sites who then have to put the WinPE image on their local PXE server.

We are in the process of changing how the PXE servers are managed and would like to create a WinPE image in the UK and push it out to all the PXE servers across Europe.

But when the image boots it tries to connect to the UK server and not the local one, is there a way to add an option so that they can select their local MDT server?

Could someone tell me how I can fix this?  I am creating a Development share on my Production MDT server.  I want to deploy GPOpacks, but I notice that the GPOPacks Folder is missing from my Templates folder.  Is there way I can add the functionality for it without having to reinstall the MDT server components as this is a production box?  Is it a simple as creating a GPOPacks folder?