none
Deployment times are very long for me RRS feed

  • Question

  • Greetings

    I'm currently deploying Windows 10 ENTERPRISE N 1709 with WDS/MDT.

    the deployment is managed with the MDT database (computers and roles etc...).

    Everything is working fine but the deployment is very long and the problem does not seem to come from MDT, let me explain :

    When i deploy windows 10 on a Virtual Machine, it takes about 1 hour.

    When i deploy on a laptop Toshiba TECRA A50C it takes almost 2 hours !

    When i see the logs i notice that the part that takes the most time is not a mdt step, it's the windows black screen that looks like that : https://sospc.name/wp-content/uploads/2015/08/Installation-Windows-10-tutoriel-SOSPC.name-6-1024x576.jpg

    For the laptop, this screen appears during at least 80 minutes, for the virtual machine, at least 30 minutes.

    I would like to know if it's normal that this part of the deployment takes such long time.

    Do you have the same problems with windows 10 ?

    (english is not my mother tongue sorry)

    Thanks.

    Benjamin.

    Thursday, March 8, 2018 3:45 PM

Answers

  • Greetings,

    I have the final point on this problem.

    In fact, i use a powershell script that disables useless Windows 10 services (telemetry, telephony etc...)

    It disables a service called "dmwappushservice"

    I just had to build a new windows 10 reference image with this service not disabled.

    My deployment length went from +1h to 30 minutes !!

    thanks for your help


    • Marked as answer by BenjaminFili Tuesday, November 13, 2018 2:49 PM
    • Edited by BenjaminFili Tuesday, November 13, 2018 2:50 PM
    Tuesday, November 13, 2018 2:49 PM

All replies

  • On average my network deployments of Windows 10 take about 35 minutes. The majority of the time is when the image is applied, but that's mostly because I'm stuck on a 100 Mbps network connection.

    How do you handle driver injection? Is this slow part during the first time boot? Are you using packages?


    Daniel Vega

    Thursday, March 8, 2018 4:50 PM
  • I would like to hop in here and ask, Dan, that the 35 minutes is solely the OS installing? Once at the desktop, if there are applications being installed, that adds to the deployment time? My images are fairly thick but overall they finish totally in about 40 minutes with the drivers, OS and installs combined.
    Thanks
    Thursday, March 8, 2018 6:17 PM
  • No, that 35 minutes is from start to finish. It takes about 15 minutes for DISM to apply the image (WIM). My image includes Windows, Office and Visual C++ redistributables. The rest of the software is installed during deployment such as browsers, Box, Skype, Adobe Creative Cloud desktop app, Dell tools, etc. I do that so that I can update those apps without having to build a new image. It's about 16 minutes to install all the software, apply some scripts and tweaks depending on which hardware the task sequence is running on.

    Oh yes and that typically includes the BIOS being updated during the TS. 

    https://www.tekuits.com/single-post/2017/10/18/Updated-Parse-Dell-Downloads-Script

    https://garytown.com/dell-bios-update-winpe-model-independent-from-internet


    Daniel Vega


    • Edited by Dan_Vega Thursday, March 8, 2018 7:08 PM BIOS update
    Thursday, March 8, 2018 7:04 PM
  • Very nice. An MS tech told me today that using a VM as my image source is an outdated method anymore. I'm trying to get more details but he suggests that MDT will create the image instead. This is handy for when the OS continues to upgrade. HE said making a VM, updating it, Capturing it, repeat repeat every OS upgrade is an old method to use. I need to find out more info about this.
    Thursday, March 8, 2018 7:12 PM
  • Yeah, I'd like to hear more about that. Maybe he was referring to provisioning, which is viable if you are starting off with an OEM computer that doesn't have a bunch of bloatware installed on it.

    For anyone that's going to build a traditional image, building it on a VM is the best way versus building an image on hardware. 


    Daniel Vega

    Thursday, March 8, 2018 7:25 PM
  • Yep. I don't believe he was referring to an actual physical pc. Somehow MDT creates a WIM to deploy, directly. I'm betting HIS image was bare bones or he had every piece of software set to silent install.
    Thursday, March 8, 2018 7:31 PM
  • Very nice. An MS tech told me today that using a VM as my image source is an outdated method anymore. I'm trying to get more details but he suggests that MDT will create the image instead. This is handy for when the OS continues to upgrade. HE said making a VM, updating it, Capturing it, repeat repeat every OS upgrade is an old method to use. I need to find out more info about this.
    This is considered a thin image and it usually takes longer to deploy because MDT will have to install all applications and Windows Updates since they are not baked into the image.
    Thursday, March 8, 2018 7:47 PM
  • I agree. One of our public main safety apps has so many fine-tunes to it from the desktop that it's best to install it once correctly than chancing it getting messed up. I got interested in what this rep was saying about not needing to create, modify, update (upgrade OS's) on a VM any longer.
    Thursday, March 8, 2018 7:53 PM
  • Hello, thanks for answers.

    In my case, in fact, i'mbuilding back MDT. For the drivers, i used to do the following :

    1) I needed a computer with all updated drivers

    2) I used a software called "DriverBackup V2" that is able to "capture" all the drivers of your computer in .inf format

    3) Import those drivers in MDT.

    The driver injection step takes about 5 minutes

    What annoys me is that the step that takes the most time is not even related to MDT, the "Applying image step" with a progress bar takes 10 minutes and the step after is extremly long.

    Thursday, March 8, 2018 8:05 PM
  • I'm not familiar with 1709 yet but I relate to the black screen. I added a few Panasonic models to MDT for 1703 and right away I saw a black screen with not even what you see. Literally a black screen. After talking to them, they said it is by nature.

    On top of that, with my Dell models, I had to do a few registry changes to avoid the voice-setup for first time boot ups. The voice that talks endlessly saying...we're almost there, don't turn off your pc, hang in there!!! UGH. So, by skipping all of that nonsense, it happens in the background, without the voice prompts. It still takes about as long but it's automated. I wonder if 1709 has fixed that, so there's no 10-15 minute intro of her talking while the pc is being configured. For me, I see only a few extra minutes of the black screen and swirling dots. But I'm also seeing that going from one version of 10 to another is much more of a pain than having gone from 7 to 10 initially.

    Friday, March 9, 2018 7:09 PM
  • You can quiet Cortana, by adding some simple code to your unattend.xml

    <RunSynchronousCommand wcm:action="add">
            <Description>Quiet Cortana</Description>
            <Order>8</Order>
            <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE /v DisableVoice /t REG_DWORD /d 1 /f</Path>
    </RunSynchronousCommand>

    The order number will of course will depend on how many commands there are before this one.


    Daniel Vega

    Friday, March 9, 2018 7:26 PM
  • You can also speed things up by adding a couple tasks to use High Performance settings. You'll need one in Windows PE. I add mine to "New Computer only" in the Preinstall phase and then add it again to the beginning of State Restore. 

    cmd /c PowerCfg.exe /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c


    Daniel Vega

    • Proposed as answer by SCCMF12TWICE Friday, March 9, 2018 8:03 PM
    Friday, March 9, 2018 7:33 PM
  • Dan, that's what I do. I have two lines in my unattend to hush her up and bypass all that setup:

    reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v DelayedDesktopSwitchTimeout /d 0 /t REG_DWORD /f

    reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f

    Friday, March 9, 2018 7:35 PM
  • You can also speed things up by adding a couple tasks to use High Performance settings. You'll need one in Windows PE. I add mine to "New Computer only" in the Preinstall phase and then add it again to the beginning of State Restore. 

    cmd /c PowerCfg.exe /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c


    Daniel Vega

    I've used this method in my environment and can agree that this speeds up our OSD time by 20% - 40% depending on the model. 

    Friday, March 9, 2018 8:04 PM
  • Ironically, for me, I added the power scheme to my TS and timed it with and without the change. After adding the High Performance entry, imaging took 2 minutes longer to complete than without the scheme. Figures.
    Monday, March 12, 2018 3:43 PM
  • Greetings,

    I have the final point on this problem.

    In fact, i use a powershell script that disables useless Windows 10 services (telemetry, telephony etc...)

    It disables a service called "dmwappushservice"

    I just had to build a new windows 10 reference image with this service not disabled.

    My deployment length went from +1h to 30 minutes !!

    thanks for your help


    • Marked as answer by BenjaminFili Tuesday, November 13, 2018 2:49 PM
    • Edited by BenjaminFili Tuesday, November 13, 2018 2:50 PM
    Tuesday, November 13, 2018 2:49 PM
  • Hello

    you disabled all these services on the windows 10 that is hosting the MDT service and it increade your deployment speed?

    Saturday, May 11, 2019 4:14 PM