Windows 10: MDT 2013 Deployment

we distribution OS of Chinese and Korean by MDT 2013 deployment, so I want to manually set language and time , but unable to activated when I was changed MDT Rules as the following, what should i do


[Settings]

Priority=Default

Properties=MyCustomProperty

[Default]

:


OSInstall=YES

SkipBDDWelcome=NO

SkipCapture=NO

SkipDeploymentType=NO

DeploymentType=NewComputer

SkipAdminPassword=YES

SkipAppsOnUpgrade=NO

SkipComputerName=YES

SkipProductKey=YES

SkipDomainMembership=YES

SkipComputerBackup=YES

SkipBitLocker=YES

SkipTaskSequence=YES

TaskSequenceID=001

SkipFinalSummary=YES

SkipTimeZone=NO

TimeZoneName=China Standard Time

SkipLocaleSelection=NO

KeyboardLocale=zh-cn

UserLocale=zh-cn

UILanguage=zh-cn

SLShare=\\SCMDTMGMT\log

SLShareDynamicLogging=\\SCMDTMGMT\log\

SkipUserData=YES

SkipSummary=YES

FinishAction=LOGOFF



:)

 

Deployment Issue - MDT 2013 / OptiPlex 790 / Driver Injection


I'm trying to successfully deploy Windows 10 on a Dell OptiPlex 790 in my lab environment in order to push Windows 10 out to several of these PCs currently in production. Despite the fact that Dell does not offer a driver pack for Windows 10 for the 790, an upgrade to Windows 10 using the Windows Update method works fine; however, when I run a LiteTouch install, the keyboard and mouse do not work unless I am using a PS2 keyboard and mouse.

Upon further investigation, I found that the "USB Root Hub" device drivers are not properly installed on the deployed OptiPlex 790. My steps for a solution thus far have produced no meaningful results. I have tried the following:

1. From a working installation of Windows 10 on an OptiPlex 790, performed a full driver backup/export and imported into MDT 2013 Out-of-Box Driver folder for model-specific-injection task sequence. After deployment completed successfully with 0 errors and 0 warnings, the drivers are still not loaded and keyboard/mouse are nonfunctional.

2. Created an application package to silently install Intel Chipset during the LiteTouch OS installation, which includes the proper USB drivers for the OptiPlex 790. Results are the same; yet if I run the install after deployment, the drivers are installed successfully.

I'm just about out of ideas on this one, but I KNOW there has to be something that can work. It doesn't make sense that a manual install of the chipset can produce positive results but the same cannot be said for a LiteTouch deployment.

Any help or useful input on this would be greatly appreciated! Thanks.

 

Importing Win10 into MDT 2013

I was unable to import it using the install that was available for free download. However, I got it working with the download that I got directly from the volume licensing center.

Still having issues capturing an image with it though. Getting a failure after running Litetouch, just before the sysprep phase. I read somewhere that MDT 2013 update 1 preview isn't working with later builds of the tech preview, or the final build. Assuming
we have to wait for another MDT update.

 

MDT 2013 Update 2013 Build 8298 - Sysprep "disconnects" NIC


I made an account to reply back with "Me too!!111".

Our MDT setup has been upgraded though the years from MDT 2008, 2010, 2012, to 2013, update1 and this latest 8298 build and we are experiencing the same issue.

Our MDT WinPE is version 10 with a custom boot that launches an autoIT login screen authenticating the user against AD and pulling the computer name via vbscript LDAP lookup. Authentication changes what a person can/cannot see for deployment. We use the MDT image in our WDS PXE boot.

When using a stock sysprep and capture against a MSDN "Windows 10 Enterprise (x64) - DVD (English)" SHA1 30AD1CDF5D0670F12788005131E24862F6AB8AAB it destroys the system during sysprep due to the generalize flag. I have disabled the tilemodelsvc, updated the system via our WSUS server nether prevent the generalize flag from breaking the guest. I see the network become unavailable almost immediately.

We have tried it in our ESX 5.5 U3, Virtualbox, Physical E6530, E7450. All break at the same spot causing the LTICopyScripts.wsf to not be found (aka network share is lost, drivers are not found, and the system as a whole is butchered). This screen shot is me attempting to load device manager after the deployment error (just before I click the error message about not finding LTICopyScripts.wsf)





I have posted an issue to MS MDT feedback (ID 1803004). Login and provide any additional feedback. It's not bad now that this doesn't work for us since we are not really far behind on drivers but each month and more patches get released my team lags on deploying 10. We are using the deployment tasks to rip out the items we don't need but it would be nice to not have to do it each time.