Windows 10: MDT 2013 Deployment

Discus and support MDT 2013 Deployment in Windows 10 Installation and Upgrade to solve the problem; 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... Discussion in 'Windows 10 Installation and Upgrade' started by 2, Feb 17, 2020.

  1. 2
    2 Win User

    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

    MDT 2013 Deployment [​IMG]

    :)
     

  2. 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.
     
    FunkiNATEr, Feb 17, 2020
    #2
  3. 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.
     
    BostonDerek, Feb 17, 2020
    #3
  4. Nathaniel Win User

    MDT 2013 Deployment

    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)


    MDT 2013 Deployment [​IMG]


    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.
     
    Nathaniel, Feb 17, 2020
    #4
Thema:

MDT 2013 Deployment

Loading...
  1. MDT 2013 Deployment - Similar Threads - MDT 2013 Deployment

  2. SCCM and MDT Deployment - IP Address vs Domain Name

    in Windows 10 Network and Sharing
    SCCM and MDT Deployment - IP Address vs Domain Name: Hello,I have found several answers to why the domain name is not working and that I need to use IP address, When i load my image - it says IP: 192.168.1.2 \boot\x64\images... which is all correct.Then When Microsoft Deployment Toolkit screen displays I get error:A...
  3. MDT is not deploying drivers

    in Windows 10 Drivers and Hardware
    MDT is not deploying drivers: Hello everyone, I wish you a happy new year and the best of health. at work, MDT deploys 1 window 10 pro image to all models of computers. I do that by in task seq. I disabled the default inject driver step and add my custom task step. then named it DriverGroup001 and...
  4. Creating deployment process with WDS/MDT.

    in Windows 10 Installation and Upgrade
    Creating deployment process with WDS/MDT.: Hi, I am a Help Desk Analyst and am being challenged with learning sysAdmin tasks. I've been tasked with setting up a deployment process, and I have been trying for a few weeks now to deploy an image with WDS/MDT. I've searched the internet hard trying to figure it out but...
  5. MDT Fails when deploying 1803 and 1809

    in Windows 10 Installation and Upgrade
    MDT Fails when deploying 1803 and 1809: Dear Colleagues, I would like to ask for your assistance: - I have a Windows Server 2012 R2. 1809 ADK, MDT 6.3.8456.1000, DISM 10.0.17763.1 + WinPE 1809 installed. - Deploying Windows 10 1703 is always succeed. - I have an alternate DeplymentShare on the same server and...
  6. unable to login after a win10 1803 MDT/WDS deployment

    in Windows 10 Installation and Upgrade
    unable to login after a win10 1803 MDT/WDS deployment: I was able to create and deploy a win10 1803 image containing a number of software packages, the deployment ends with no errors, it joins a domain. Everything worked fine with the first set of computers. However it is not working right for some other computers which have...
  7. MDT deployment. Some settings are managed by your system administrator

    in Windows 10 Drivers and Hardware
    MDT deployment. Some settings are managed by your system administrator: After the 1709 update for Windows 10, we have experienced that all new deploments get the error: Some settings are managed by your system administrator in the update menu We use a clean image from Microsoft without any changes and we did not experienced this error before....
  8. MDT 2013 Update 2013 Build 8298 - Sysprep "disconnects" NIC

    in Windows 10 Installation and Upgrade
    MDT 2013 Update 2013 Build 8298 - Sysprep "disconnects" NIC: Hello Guys We have upgraded our MDT 2013 to Update 1 build 8298. And we have quite a few issues that we didn't have before. We have some pretty simple task sequences we use to build images, one for each OS. Currently Windows 7x64, Windows 8.1x64 and Windows...
  9. Deploying Windows 10 using MDT and a OEM key?

    in Windows 10 Installation and Upgrade
    Deploying Windows 10 using MDT and a OEM key?: Hi, First off, I will apologize for the complicated nature of this thread. I have several machines that have OEM licenses of Windows 8.1 Pro. What I would like to do is do the following: 1. Install Windows 8.1 Pro onto them. 2. For each machine, I will need to...
  10. Deployment Issue - MDT 2013 / OptiPlex 790 / Driver Injection

    in Windows 10 Installation and Upgrade
    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...